Taboola Conversion Tracking: How the Pixel, Click ID and S2S Postbacks Fit Together

A plain guide to the pixel, the click ID, cookies and server-to-server postbacks, and how to set them up so Taboola can see which clicks became orders.

Illustration for the Nativize article: Taboola Conversion Tracking: How the Pixel, Click ID and S2S Postbacks Fit Together
On this page
  1. How Taboola conversion tracking works
  2. Taboola pixel tracking: the tracking pixel and tracking code
  3. Taboola tracking parameters and the click ID
  4. Taboola tracking cookie: what it does and why it is not enough
  5. Taboola S2S tracking: sending conversions from your server
  6. Set up Taboola conversion tracking: a worked example
  7. How Nativize handles tracking on advertorials
  8. Common Taboola tracking mistakes
  9. Frequently asked questions
  10. The bottom line
  11. Keep reading

Key takeaways

  • Taboola conversion tracking links a click on a native ad to a purchase, using a pixel in the browser, a postback from your server, or both.
  • The click ID that Taboola adds to your landing page URL is the key piece. If you lose it between the ad click and the order, the conversion cannot be matched.
  • Native traffic usually lands on an advertorial first, so the click ID must survive the jump from the article to the product page and checkout.
  • Run the pixel and S2S together if you can, and make sure the same purchase is never counted twice.
  • Test with a real click and a real order before you spend meaningful budget.

Taboola conversion tracking is how the network learns which ad clicks ended in a purchase. Without it you cannot see cost per order, and Taboola cannot optimise toward buyers. If you come from Meta, the idea is familiar, but native has a twist: people usually click into an advertorial (an ad laid out as an article) before they reach your store, so there is an extra hop where tracking can break. This guide covers the Taboola pixel, the click ID, tracking parameters, cookies and server-to-server (S2S) postbacks. It ends with a setup checklist and the mistakes that most often leave a campaign reporting zero sales when orders are coming in.

How Taboola conversion tracking works

Taboola conversion tracking is the setup that connects a click on a Taboola ad to an action on your site, such as a purchase. It combines a click ID passed in the URL with a pixel in the browser, a server-to-server postback, or both, so Taboola can report and optimise conversions.

The flow has three steps. A reader clicks your ad. Taboola sends them to your landing page and adds a unique click ID to the URL. When the reader later converts, a signal carrying that same click ID goes back to Taboola, so the sale is matched to the click.

There are two ways to send that signal back. The first is a pixel: a small piece of JavaScript on your page that fires in the visitor's browser. The second is S2S, short for server-to-server: your server or shop backend calls a Taboola URL directly when an order is confirmed. Neither needs the other, but they cover different weaknesses.

If you have run Meta ads, think of the pixel as the Meta Pixel and S2S as the Conversions API. The comparison is loose, and the details differ, so treat Taboola's own documentation as the source for exact event names and URL formats.

For background on the platform itself, see how Taboola ads work and the basics of how to run a first campaign.

Taboola pixel tracking: the tracking pixel and tracking code

People search for the Taboola tracking pixel, the Taboola tracking code and Taboola pixel tracking as if they were different things. They are the same thing: a base code snippet that loads on your pages, plus event calls that fire on specific actions.

The two parts of the pixel

  • Base code: loads on every page you want measured, including the advertorial, the product page and the order confirmation page. It records the visit and reads the click ID.
  • Event code: fires on an action, such as add to cart or purchase. For a purchase, you will normally pass the order value and currency too, so Taboola can see revenue.

Where to install it

Most brands install the pixel through Google Tag Manager (GTM), which is a free tool for managing tags without editing site code, or through their shop platform's script settings. Either works. What matters is that the purchase event fires once, on the real confirmation page, and carries the right value.

The pixel's weakness is that it depends on the browser. Ad blockers, privacy settings, a visitor closing the tab early or a slow thank-you page can all stop it from firing.

Taboola tracking parameters and the click ID

Taboola tracking parameters are the extra values added to the end of your landing page URL, after the question mark. You set up the template in the campaign. Taboola then fills in values for each click.

The most important one is the click ID. In the campaign's tracking URL you add a placeholder (a macro, in Taboola's terms, often written like {click_id}) and Taboola swaps it for a unique value on every click. Check Taboola's current documentation for the exact macro name before you build the URL.

Other parameters are optional but useful for your own analytics. Common ones are campaign, site and ad identifiers, and standard UTM parameters (tags such as utm_source and utm_campaign that analytics tools read). Use them consistently so that your reports in GA4 and your order data can be broken down by campaign and by publisher site.

Keep your naming simple and stable. Changing parameter names mid-campaign splits your data into two sets that are hard to compare.

A Taboola tracking cookie is a small file stored in the visitor's browser that helps tie a later action back to an earlier visit. The pixel uses cookies to recognise the visitor between pages.

Cookies are fragile. Browsers restrict some of them, people clear them, and visitors who switch from phone to laptop before buying leave the cookie behind. Consent banners can also block the pixel until the visitor agrees, depending on your setup and the rules where your customers live.

The safer habit is to store the click ID yourself. When the visitor lands, save the click ID from the URL in your own first-party cookie or session, and attach it to the cart or order. Then you still have it when the order is placed, and you can use it for a postback even if the browser pixel never fires.

How dependent is your brand on Meta?Get your Native Ads Readiness Score and Platform Dependency Score in 2 minutes. It is free.

Take the test

Taboola S2S tracking: sending conversions from your server

Taboola S2S tracking, also called a postback, means your server tells Taboola about the conversion. When an order is confirmed, your backend calls a Taboola URL and includes the saved click ID, the event name and, usually, the order value.

It does not rely on the visitor's browser, so ad blockers and closed tabs matter far less. It also lets you send only confirmed orders, which keeps out failed payments. The cost is more setup work: someone has to store the click ID and build the call, often in your shop platform, a tracking tool or custom code.

PixelS2S postback
Where it firesIn the visitor's browserFrom your server or shop backend
Setup effortLow, often through GTMHigher, needs the click ID saved with the order
Affected by ad blockers and cookiesYesMuch less
Can send confirmed orders onlyOnly if you place it carefullyYes, easily
Main riskMissed or double firesMissing click ID, double counting with the pixel
Start with the pixel if...You are launching your first tests, your store runs on a common platform and you want data flowing quickly with little developer time.
Add S2S if...You are spending enough that missed conversions would distort decisions, or you want refunds and failed payments kept out of what Taboola sees.

If you run both, make sure Taboola can tell they describe the same order, and follow its guidance on avoiding duplicates. Otherwise your reported sales will be inflated.

Set up Taboola conversion tracking: a worked example

Here is the process for a made-up product, a posture-support cushion called CushionCo. It is an illustration, not a client case. The brand sends traffic to an advertorial on its own domain, which links to a product page and a checkout.

  1. Define the conversion. For CushionCo it is a completed purchase, with the order value passed along. Add to cart can be a second, softer event.
  2. Create the conversion event in your Taboola account and note the event name you will use. Copy the pixel base code.
  3. Install the base code through GTM on the advertorial, the product page, the cart and the order confirmation page.
  4. Add the purchase event on the confirmation page only, with order value and currency. Make sure it fires once per order, not every time the page is reloaded.
  5. Build the campaign tracking URL for the advertorial. Add the click ID placeholder plus your UTM parameters.
  6. Make sure the click ID survives the advertorial. The call-to-action link to the product page must carry the parameters forward, or your script must save the click ID on landing.
  7. Save the click ID with the cart or order in your shop, so it is available after payment.
  8. If you use S2S, set your backend to call the Taboola postback URL on each confirmed order, with the saved click ID and the order value.
  9. Test with a real click. Open your own ad or tracking URL, go through checkout with a low-value or test order, and confirm the event appears in Taboola and in your shop's order data.
  10. Compare a day or two of Taboola's reported sales against your shop's orders from the same source. Small gaps are normal. Large ones mean something is broken.

If you find the click ID is missing at step 9, go back to step 6. Lost parameters between the advertorial and the product page are the most common cause.

How Nativize handles tracking on advertorials

Nativize builds advertorials from the product page URL, writes each marketing angle as its own page, and exports each one as a self-contained page published on the advertiser's own domain. Several angles can be built in one batch for the same product and then connected to Taboola campaigns.

Tracking tags, whether Google Tag Manager, Meta Pixel, GA4 or the advertiser's own script, are added at export only. That means reviewing drafts never fires real tracking, so test views do not pollute your data. If your Taboola pixel is loaded through GTM or your own script, it goes in at that final step.

Because each angle is a separate page, you can tag each one with its own campaign parameters and compare angles on the same product. That is the main reason clean parameter naming matters for this kind of testing. For more on the page type itself, read the guide to advertorials.

Common Taboola tracking mistakes

  • Dropping the click ID on the advertorial. The link to the product page strips the parameters, so the purchase has nothing to match.
  • Installing the pixel on the product page but not on the advertorial, or the reverse, so part of the journey is invisible.
  • Firing the purchase event on page load of a thank-you page that can be refreshed or revisited, creating duplicate orders in the report.
  • Counting the same sale twice by running both pixel and S2S without a deduplication plan.
  • Sending the wrong value, such as price before discounts, or no currency, so revenue does not match your shop.
  • Changing parameter names during a test, which splits the data.
  • Judging a campaign too soon on attributed sales alone, without checking how the numbers compare with your shop's own orders.
  • Testing in the live account with real traffic instead of making a test order first.

Taboola's numbers will rarely match your shop to the order. Different attribution windows, blocked scripts and refunds all create gaps. Decide which source you trust for profit decisions, and use Taboola's figures mainly for in-platform optimisation. A wider look at this problem is in ecommerce conversion tracking.

Frequently asked questions

What is the difference between the Taboola pixel and S2S tracking?

The pixel runs in the visitor's browser and reports actions as they happen. S2S is a call from your server that reports a conversion using a saved click ID. The pixel is easier to install. S2S is less exposed to ad blockers, cookie limits and closed tabs.

Do I need both the pixel and S2S?

No. Many brands start with the pixel alone. Adding S2S makes sense when missed conversions would affect your decisions. If you use both, follow Taboola's guidance on deduplication so a single order is not counted twice.

Where do I find my Taboola tracking code?

It is in your Taboola Ads account, in the area where you manage pixel and conversion events. Because the interface changes, check Taboola's current help documentation for the exact location and event names.

Why do Taboola's sales not match my store's orders?

Common causes are a lost click ID, blocked or delayed scripts, different attribution windows and refunds or failed payments. Compare a short period, find where the gap starts, and check that the click ID survives from the advertorial to the order.

Do I have to pass UTM parameters too?

They are not required for Taboola to track conversions, but they help your own analytics tools like GA4 split results by campaign and ad. Keep the naming consistent from the start.

The bottom line

Start small. Define one conversion, install the pixel on every page in the journey, carry the click ID from the advertorial to checkout, and run a real test order before you raise budget. Then consider adding S2S for the orders the browser misses. Once tracking is trustworthy, you can compare angles and creatives on real cost per order. If you are still setting up the campaign itself, the Taboola campaign setup guide is the next step, and the Taboola requirements post covers what you need before you launch.

Keep reading

YB

Yash Bhandari

Founder of Nativize.

See if your brand is ready for native ads

Answer 10 quick questions. If you are a fit, you can book a strategy session with a Nativize media buyer.

See if you qualify
Scaling past Meta?Take the test