Taboola Conversion Tracking Setup

Four ways exist to install the Taboola pixel and only two are worth using. This covers the fast Realize auto-connect route and the recommended GTM template route, plus the conversion configuration that most setups get wrong — including the one field mismatch that silently breaks everything.

There are four ways to install the Taboola pixel and only two of them are worth using. This guide covers the Realize auto-connect method (fastest, five minutes) and the manual GTM template method (more control, fifteen minutes), then the conversion setup that most people get wrong.

One thing before you start: Taboola's advertiser platform is now called Realize. Most tracking guides still describe the old Backstage interface, and the navigation has changed. Everything below reflects the current UI.

Which method to use

What you need before starting

• A Realize advertiser account with tracking permissions
• Google Tag Manager already installed on your site — check by viewing page source and searching for GTM-
• GTM publish permissions, not just edit
• Your conversion pages identified — thank-you page URL, or the event that fires on success

Step 1: Find your Taboola Account ID

Everything else depends on this number, and it is not the same as your seat ID or your login email.

1. Open Realize and sign in
2. Top left — select the account you will use to track conversions. This matters if you manage several; conversions belong to the account you pick here
3. Left sidebar → click Tracking
4. Your numeric Account ID appears at the top left of the Tracking screen
5. Copy it somewhere — you will paste it into GTM shortly

Step 2A: The fast route — let Realize build the tag

Realize can create the GTM tag for you through a Google OAuth connection. No tag configuration, no copy-pasting code.

1. In Realize, go to Tracking (left sidebar)
2. Select Google Tag Manager as the setup method, click Continue
3. Click Click To Connect
4. A Sign in with Google popup appears — sign in with the account that has GTM access
5. Grant Realize permission to update GTM on your behalf
6. Select the correct Account, Container and Workspace
7. Click Save, or Save & Create Conversion to continue straight into conversion setup
8. Confirm the success message appears in Realize

GTM now contains a Taboola Pixel tag firing on all pages. It is not live yet — you still have to publish the container in GTM. This trips people up constantly.

Step 2B: The recommended route — GTM template

More steps, but you keep full control and no external service touches your container.

Add the template

1. Open Google Tag Manager and select your container (note the GTM-XXXXXXXX ID on the right)
2. Select a workspace — Default Workspace is fine
3. Left navigation → Templates
4. In the Tag Templates section, click Search Gallery
5. Search for Taboola Pixel
6. Click Add to workspace, then confirm with Add

Create the base pixel tag

1. Left navigation → Tags → New (top right)
2. Click the Tag Configuration card
3. Select the Taboola Pixel template you just added
4. Paste your numeric Taboola Account ID
5. Confirm Pixel Type is set to Base Pixel
6. Click the Triggering card → select All Pages
7. Name it something obvious — Taboola — Base Pixel
8. Click Save

The base pixel tracks page views across the entire site. You create it once. Every conversion event you add later depends on it being present, so get this working before moving on.

Alternative: Custom HTML

If the template is unavailable, Realize gives you a raw snippet. In Realize go to Tracking, select Manually as the setup method, click Continue, then hover the code block and click COPY TO CLIPBOARD.

In GTM: Tags → New → Tag Configuration → under Custom, select Custom HTML. Paste the snippet, set the trigger to All Pages, save.

Step 3: Create the conversion in Realize

The pixel collects data. A conversion rule tells Taboola which of that data counts as success. You need both.

1. Realize → Tracking (left sidebar)
2. Click + New Conversion (far right)
3. Select Create conversions using code → Continue
4. Give the conversion a clear name — Lead Form Submit, not Conversion 1
5. Set the Event Name. This is the critical field. Use a lowercase standard event such as lead or make_purchase
6. Decide on Include in total value. Leave it ticked for revenue-generating events; clear it for soft conversions you do not want inflating reported value
7. Skip the Event Code section — GTM handles that
8. Save

Standard event names

Step 4: Build the event tag in GTM

Now connect the conversion you just defined to an actual user action.

Create the trigger

For a thank-you page conversion:

1. GTM → Triggers → New
2. Trigger Configuration → Page View
3. Select Some Page Views
4. Condition: Page URL · contains · /thank-you
5. Name it Trigger — Thank You Page and save

For a form submission without a page change, use a Custom Event trigger matching whatever your site pushes to the data layer, or a Form Submission trigger with appropriate conditions.

Create the event tag

1. GTM → Tags → New
2. Tag Configuration → Taboola Pixel template
3. Enter the same Account ID
4. Set Pixel Type to Event Pixel
5. Enter the Event Name — exactly as typed in Realize
6. For purchases, map revenue, currency and orderid to your data layer variables
7. Triggering → select the trigger you just built
8. Name it Taboola — Lead Event and save

Passing revenue values

For purchase events, sending the order value lets Taboola optimise toward revenue rather than order count — which matters enormously if your order values vary.

Send revenue as a plain number. Currency symbols, commas or spaces cause the value to be dropped silently — the conversion still registers, the value shows as zero, and nothing warns you.

The orderid field also does deduplication work. Without it, a customer refreshing the thank-you page can register multiple conversions for one sale.

Step 5: Test before publishing

Do not skip this. A tag that looks correct in the interface fails often enough to be worth five minutes.

1. In GTM, click Preview (top right)
2. Enter your site URL and connect — Tag Assistant opens in a new tab
3. Load a normal page. Confirm Taboola — Base Pixel appears under Tags Fired
4. Complete a real conversion — submit the form, place a test order
5. On the thank-you page, confirm Taboola — Lead Event fires
6. Click the tag to inspect it. Check the Account ID, the Event Name, and that revenue values are populated rather than undefined
7. Return to GTM and click Submit → Publish

Verify in Realize

Go back to Realize → Tracking. Your conversion should show recent activity. Allow up to a few hours for the first events to appear — it is not instant, and concluding it is broken after ten minutes is premature.

The codeless alternative

If you only need URL-based conversions and do not want to build event tags, Realize supports codeless conversions. You still need the base pixel installed — that part is unavoidable — but conversions can then be defined by URL rule rather than by event.

In Realize → Tracking → + New Conversion, choose the URL-based option and define a rule such as URL contains /thank-you.

Server-to-server, and why you want both

Taboola supports server-to-server conversion reporting alongside the pixel, and their own documentation recommends dual tracking — running both — for more complete data.

The reason is straightforward. Client-side pixels are lost to ad blockers, browser privacy controls, ITP restrictions and users closing the tab before the tag fires. Server-side reporting does not have those failure modes.

Use S2S when you need better coverage, when conversions happen off the website (a phone call, a CRM stage change), or when you are tracking app installs and in-app events through an MMP.

Troubleshooting

What the numbers will look like

Taboola-reported conversions will not match your analytics or your CRM, and that is expected rather than a fault. Attribution models differ, view-through conversions are counted differently, and client-side loss is real.

Pick one source as your source of truth — usually your CRM, because that is where money is — and use Taboola's numbers for optimisation decisions rather than for reporting to a client. A 10% to 30% gap between platform-reported and CRM-confirmed conversions is normal on native.

What matters is that the algorithm receives a consistent, reliable signal. A slightly undercounted conversion that always fires correctly optimises better than a perfectly counted one that fires intermittently.

Final checklist

Taboola renamed its advertiser platform to Realize, and the interface continues to change. Navigation paths reflect the platform as of September 2026 — if a menu has moved, the underlying concepts still apply.