Track Taboola Conversions Using S2S Postbacks

Server to Server (S2S) conversion tracking allows you to track multiple conversions, without installing the Taboola Pixel. These conversions can be, for example, mobile app installs and post-install events - such as signups and purchases - that happen after a user clicks on your Taboola campaign creatives.

Conversion tracking helps you gather important insights about actions users are taking on your app or website, and gives you the ability to measure the impact, return on your ad spend, and to optimize your campaigns accordingly.

What Can I Track Using S2S Conversion Tracking?

Using S2S conversion tracking, you can track any type of user interaction in your app or website that you would like to optimize in Taboola’s Backstage. You can also represent your multi-conversion funnel using S2S tracking. For example:

Downloads - You can track downloads of your app from places like the App Store (iOS) or Google Play (Android).
In-app Events - You can track many post-install events, such as when a user reaches a certain level in an app or makes a post-install purchase.

Add S2S Tracking to your Taboola Campaign.

After a user clicks on your content, Taboola will notify your server’s with a click value.

You will need to add the Taboola {click_id} macro into your Taboola campaign tracking code. This will populate with a value that is sent to your site or to your 3rd party platform.

When a conversion is made by the relevant user, the {click_id} value is included in a postback URL which sends the conversion information to Taboola to be reflected in Backstage reporting.

In Backstage:

  1. Go to the Campaign Management page.
  2. Then click +New Campaign or edit an existing campaign.
  3. In the Campaign page, go to the Tracking section at the bottom of the page.
  4. Add a parameter to your Tracking Code that is set to equal “{click_id}” as conversion cannot be recorded without it. The parameter you use should allow you to record this value and later populate it in your postback URL to attribute the conversion. This can also be added as a parameter at the item level. You can learn more about how to add URL parameters here.

It is vital to NOT alter the {click_id} macro, otherwise your Conversions will not be tracked.

Create S2S Conversions

Note: To check if you are already sending events to Backstage, and to save time, you can use the Active tab as a shortcut. Learn more here.

  1. To define conversions with S2S tracking, go to the Taboola Pixel menu, and select Conversions. Here you can view existing conversions or set up and define new conversions that came from either the Taboola Pixel or S2S tracking. Note that you do not need to implement the pixel to track conversions with S2S.
  2. Click New Conversion to set up and start tracking a new conversion.
  3. Select the conversion Type as Event.
  4. Select either Popular or Custom, and then fill in all of the relevant fields. See Tracking and Reporting Conversions for additional information. Make note of the value in your Event Name field as this is will be used in the next step.

Important Note: The code you see here is NOT relevant for S2S and should be ignored. Please use the postback URL in the next step.

Instead of the event code from the Conversion, use a postback URL for tracking conversions. Postback URLs sit in your server’s backend and will fire only for events related to Taboola. Create a new postback URL for each conversion created in Backstage. The highlighted values below should be changed to the respective values below.
https://trc.taboola.com/actions-handler/log/3/s2s-action?click-id=CLICK_ID&name=EVENT_NAME

  • CLICK_ID– Replace with a macro that will populate with the Click ID generated on the Taboola user’s click. Taboola macros should NOT be used as this macro will be specific to your internal technology. This macro should populate with the same value created by the {click_id} macro implemented in your campaign’s tracking code to tie the conversion to this initial click.

  • EVENT_NAME - Replace with the corresponding Event Name value in Backstage