The connection that matters
A conversion is useful to your campaign only when it can be connected to the original interaction. Taboola’s server-to-server postback uses a click ID and a matching event name; revenue, currency, and order references can add context.
Map the journey before adding tags
Start with the outcome you want to measure: a completed purchase, a submitted enquiry, or a qualified lead. Identify the system that knows when that outcome is real. For a purchase, this may be the shop backend. For a lead, it may be your CRM.
Then follow one example journey. Can the click information survive the landing page, checkout, and handover to that system? A postback cannot repair an identifier that was lost earlier.
Agree on event ownership
Choose which system owns each conversion and when it should report it. Document how cancelled orders, repeated notifications, and retries are handled. This gives your team a consistent reference when platform totals differ from backend records.
Verify before optimizing
Check event names, values, and currencies against a real test record. Keep the diagnostic information needed to investigate failures without retaining unnecessary personal data. Apply the visitor’s consent choices throughout the flow.
Our Taboola service covers implementation, verification, and documentation so the integration can be maintained after launch.
Technical source: official documentation
Explore the service