Taboola Integration

Taboola is where content meets scale. Your offer in the recommendation slots of premium publisher sites, in front of readers who are already engaged with the content above the widget. Native done well can produce conversion volumes that hold their own against search and social, but it lives or dies on the combination of headline, thumbnail, and the landing page they hand off to. Reading the signal on which combinations are actually working, at the publisher-site level where blocking and bid adjustments happen, is where most native operations win or lose.

The Routy integration with Taboola pulls performance data into Routy on a continuous schedule and sends downstream conversions back through Taboola's Conversions API. The publisher-site level reporting that's at the heart of native optimisation sits in the same view as the rest of your traffic, and the bidding signal Taboola gets back is based on real outcomes rather than just pixel events.

After connecting, the following becomes available in your Routy reports:

• Spend at the campaign, ad, and publisher-site level, which is where most native bid adjustments and blocking decisions actually get made
• Impressions, clicks, click-through rate, and Taboola's platform-specific engagement metrics
• Server-side conversion uploads through the Taboola Conversions API, with deduplication against the Taboola Pixel
• Granular conversion attribution that ties every conversion Routy tracks back to the Taboola campaign, ad, and the specific publisher site behind the click

Plus, having Taboola data sit next to your search, social, and other channels in the same dashboard means cross-channel decisions get made on consistent attribution. The CPA you see for a Taboola placement is calculated the same way as the CPA you see for a Google or Meta click, which is the only way the comparison is useful.

You connect your Taboola account through Taboola's authentication flow. Once connected, performance data pulls from the Taboola Backstage API on a regular schedule, and conversion events get posted back through the Conversions API as Routy sees conversions matching Taboola clicks.

A few things worth knowing before you connect:

• The publisher-site level data is what most experienced native buyers actually use to optimise, and the integration surfaces it down to that level. Block lists, bid modifiers, and site-specific decisions can all be made from the data Routy pulls in.
• Taboola's data refresh cadence is good but not real-time — performance data typically updates every few hours. The Conversions API events post much faster than that, usually within minutes.
• Taboola's reporting depth varies by campaign type. Smart Bid campaigns expose more granular data than some of the older bidding modes, so if you're running on the older modes, the integration will report whatever Taboola makes available, which is less than a Smart Bid campaign produces.

Native traffic, done well, is one of the most competitive paid channels in the affiliate world. The buyers who win at native do so by reading site-level signal fast and acting on it: blocking sites that don't convert, scaling sites that do, rotating creatives before they fatigue, and adjusting bids by placement on a near-daily basis. That operational tempo is only possible if the data is current, granular, and sitting in the same place as the conversion data.

Connecting Routy puts Taboola's data on the same operational footing as your other channels, with the publisher-site granularity that native buyers actually need. The Conversions API uploads also help on the bidding side: Taboola's algorithms get a stream of real outcome data and start steering spend toward the placements that genuinely convert, rather than the ones that just generate clicks. Combined, the reporting clarity and the cleaner bidding signal tend to make native operations measurably more efficient, particularly on creative-led campaigns where the right combination can scale fast when caught early.