Outbrain Integration

Outbrain places your offer in the content recommendation slots of major publisher sites — the spots readers click on when they've finished the article they came for. It's one of the larger native ad networks alongside Taboola, with significant publisher inventory and depth of reporting at the placement level. The difference between a profitable Outbrain campaign and an unprofitable one usually comes down to how quickly you can identify which publisher sections are converting and which are just collecting clicks.

The Routy integration with Outbrain pulls performance data into Routy on a continuous schedule and sends downstream conversions back through the Outbrain Conversions API. The placement-level data that drives native optimisation ends up in the same view as the rest of your traffic, and Outbrain's algorithm gets real outcome signal to work with.

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

• Spend at the campaign, ad, and publisher-section level, which is where most native optimisation actually happens
• Impressions, clicks, click-through rate, and Outbrain's platform-specific engagement metrics
• Server-side conversion uploads through the Outbrain Conversions API, with deduplication against the Outbrain Pixel
• Section-level conversion attribution that ties every conversion Routy tracks back to the Outbrain campaign, ad, and specific publisher section behind the click

Plus, having Outbrain data next to your search, social, and other channels in the same dashboard means the cross-channel comparison is honest. The same conversion event, with the same value, attributed under the same rules, regardless of whether it came from native, search, or social.

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

A few things worth knowing before you connect:

• The section-level granularity is what experienced native buyers actually use to manage bids and block lists. The integration pulls that data and makes it usable in Routy reports.
• Outbrain's data refresh cadence is good but not real-time — performance data typically updates every few hours. Conversion uploads through the Conversions API post much faster, usually within minutes.
• Some of Outbrain's older campaign types expose less data than newer ones. The integration reports whatever the API returns for each campaign type, so if you're running on a legacy campaign structure, the data will be less granular than a current one.

Native ad buying is operationally intense. The right way to run it involves checking section-level performance daily, blocking sites that aren't producing, scaling sites that are, rotating creatives on a tight schedule, and adjusting bids by placement constantly. That tempo only works if the data is current, granular, and sitting in the same place as the conversion data. When the workflow involves exporting from Outbrain, joining to a conversion export, building a pivot table, and acting on the result, the operational rhythm slows to a crawl and the campaigns suffer for it.

Connecting Routy fixes that workflow. The placement-level data is already joined to the conversion data, the daily review takes minutes instead of half a morning, and the decisions about what to block or scale get made faster. The Conversions API uploads also feed Outbrain's bidding cleaner signal, so the algorithm starts steering spend toward placements that actually convert, which compounds over time. The result is usually a meaningful improvement in cost per acquisition, particularly on campaigns where the creative-to-landing-page combination is being actively iterated.