Taboola Ads attribution, from the native click to the closed deal

It can run alongside it or instead of it. Taboola recommends running the pixel and S2S together, and when the same event for the same click arrives both ways, Taboola keeps the S2S one. LeadJourney's tracking is server-side, so it does not depend on the pixel, and its conversions reach Taboola over S2S, so a conversion the pixel also reports is counted once.

A postback is a pipe: it moves events you already have. The hard part is having the right events. Taboola asks you to store the tblci on the lead in your CRM, untouched (a truncated value is ignored), and have the CRM call the postback with the case-sensitive event name of a Realize conversion when the lead converts. The bulk endpoint answers 204 whatever it received, so a wrong event name fails quietly. LeadJourney captures the Taboola click server-side, follows the lead through your CRM, and sends each mapped stage as its own postback within about 15 minutes of the change, with its revenue. A postback fired from your thank you page only ever knows what your website knows, which is still just the sign up.

Because Realize counts differently, not wrongly. It reports every conversion inside its window, regardless of other touchpoints, so a buyer who also clicked Google and Meta is a Taboola conversion as well. It adds view-through conversions from the 24 hours after an impression, and it dates each conversion on the click, not the day it happened. Your CRM only knows the people who became leads. LeadJourney shows both: Realize's conversions where you buy, and the revenue Taboola clicks actually produced, measured once across every channel.

Yes, that is the point of tracking server-side. The click, the tblci and the visit are recorded on your own domain before an ad blocker, Safari or a declined banner can remove them, at 95%+ accuracy. Realize keeps reporting what the pixel and your postbacks send; LeadJourney shows you the measured numbers.

In LeadJourney, yes. The Taboola click is stored on the visitor's LeadJourney Click ID, so when the same person comes back through Google brand search, a ChatGPT answer or a typed URL and converts, Taboola is still part of that journey. Multi-touch models then share the revenue between Taboola and the channel that closed, instead of handing all of it to the search.

Realize is the name Taboola gave its platform for performance advertisers in February 2025, and Taboola's help center and conversion docs now say Realize throughout. Campaigns, conversions and the tblci click ID are the same ones you know from Taboola Ads, and everything on this page applies to an account you opened before the change.

Any CRM stage or paid order you map: marketing qualified, sales qualified, deal won, a Shopify or Stripe purchase, or all of them. Each one is sent as its own postback under the Event Name of an event-based conversion you created in Realize (the Event Name, not the Conversion Name), with an order ID, and with revenue and currency whenever the value is above 0. Postbacks go out within about 15 minutes of the change, for leads whose journey has a Taboola click, within 30 days of that click. Whether bidding uses it is your setting in Realize: a conversion left out of Total Conversions is reported but not bid on.

Yes, if the tracking code passes the site. Taboola's macros fill in {site}, {site_id}, {campaign_item_id}, {title} and more at click time; put them in your UTM parameters and LeadJourney stores them with the click, so closed revenue reads per publisher site and per item. That is the list to block and the list to bid up. Taboola's default tracking code is utm_source=taboola&utm_medium=referral, so change the medium too, or your analytics files paid native traffic as referrals.

Taboola recommends its Shopify app for putting the pixel on your store, and the pixel runs in the browser. LeadJourney reads the paid order from Shopify and sends it to Taboola as an S2S postback with its value, so an order the pixel missed still reaches Taboola, and the same order is attributed next to Meta, Google and email in one model.

Not natively. HubSpot's ads tool connects Meta, Google, LinkedIn, Microsoft and TikTok ad accounts, and Taboola is not on that list. LeadJourney records the Taboola click itself, follows each lead into HubSpot to the deal next to every other channel, and sends the qualified leads and won deals back over S2S.

In LeadJourney, yes: the journey has no window, so the deal is credited to the campaign that started it regardless of the cycle length. Realize attributes a conversion to clicks from the past 30 days at most, and LeadJourney sends postbacks within the same 30 days, so for a long cycle map an early stage that predicts revenue, such as the qualified lead, as the conversion bidding learns from. The report that matches the late revenue to the ad lives in LeadJourney.

A postback carries the Taboola click ID, the conversion's Event Name, an order ID and, when there is one, the revenue and currency. No email, no phone number, and nothing for a stage you have not mapped. LeadJourney itself processes and stores data in the EU, signs a data processing agreement, and tracks first-party and server-side, so consent decisions are respected rather than worked around.

Your Taboola API client ID and client secret, which your Taboola account manager provides. Paste them into LeadJourney and pick the ad accounts to sync: one set of credentials can reach several. The last 180 days of campaigns and spend are imported, then spend syncs every two hours. Add the LeadJourney script, connect your CRM and map stages to conversions; once the credentials are in hand most accounts are live in about 21 minutes, and our team will do the setup with you on a call if you prefer.

The Taboola integration is part of the platform rather than a paid add on. Plans are priced by ad spend instead of seats, so your whole team and your agency can share one workspace, and every plan starts with a 14 day free trial without a credit card.