Outbrain S2S Tracking: Postback Setup passo a passo

Server-to-server tracking is the highest-leverage plumbing in an Outbrain account. Capture the click ID, fire the postback, verify the chain — the full setup with the macros table and the failure modes that actually bite.

The OpenAdLibrary Team Ad intelligence & native advertising research

August 21, 2026 · 6 min read

Outbrain server-to-server (S2S) tracking works in three moves: you capture Outbrain's unique click identifier at the landing page by appending the {{ob_click_id}} macro to your tracking URL, you store that ID against the visitor's session, and when a conversion happens your server fires an HTTP request — a postback — to Outbrain's tracking endpoint carrying the stored ID and the conversion event name.

Outbrain matches the ID to the originating click and credits the conversion to the exact campaign, ad, and publisher section. No browser pixel required, which means no losses to ad blockers or Safari's cookie limits, and accurate attribution even when the conversion happens days later in a call center or a CRM.

Why S2S beats pixel-only tracking on native

Native traffic is the worst-case environment for client-side tracking. Your ads run on content sites where ad-blocker usage is high, a large share of clicks are mobile Safari with aggressive tracking prevention, and — if you're running lead-gen or COD offers — the conversion often doesn't happen in a browser at all. A postback is a server-to-server HTTP call, so none of that applies: if your server knows about the conversion, Outbrain finds out about it.

The practical stakes are optimization, not just reporting. Outbrain's bidding and your own placement decisions are only as good as the conversion data feeding them; a pixel silently dropping a chunk of conversions makes profitable publisher sections look unprofitable, and you cut winners.

The standard setup for serious buyers is S2S as the source of truth, with an on-page pixel as a redundancy check — and every major ad tracker supports the Outbrain template out of the box. (One naming note before the walkthrough: Outbrain's advertiser platform is called Amplify, and Outbrain itself merged with Teads — the tracking stack described here is the Amplify side and survived the merger intact.)

Step 1: pass the click ID into your funnel

Outbrain exposes dynamic macros that get replaced with real values at click time. In your ad's tracking URL, append the click identifier — and while you're there, the placement metadata you'll want for optimization later:

https://your-lander.com/offer?ob_click_id={{ob_click_id}}

&publisher={{publisher_name}}

&section={{section_id}}

&campaign={{campaign_id}}

The macros media buyers use most:

Macro

What it passes

Why you want it

{{ob_click_id}}

Unique ID for this click

Required — the join key for the postback

{{publisher_name}}

Publisher the click came from

Placement-level cut decisions

{{section_id}} / {{section_name}}

The specific site section

Outbrain's blocking granularity

{{campaign_id}}

Numeric campaign ID

Clean joins in your tracker

{{ad_id}} / {{ad_title}}

The specific creative

Per-creative conversion analysis

Macro availability evolves, so verify the current list in Outbrain's advertiser documentation before finalizing templates. The parameter names on your side ( ob_click_id=, publisher= ) are yours to choose — only the {{…}} tokens are Outbrain's.

Then make sure the ID survives the funnel. If you run a tracker, its click URL captures everything automatically. If you're tracking first-party, store the click ID in a cookie or session record on landing — and audit any redirects between ad and lander, because a redirect that strips query strings is the single most common reason Outbrain S2S "doesn't work." Our redirect chain glossary entry covers how to trace one.

Step 2: fire the postback

When the conversion event happens — sale, lead, qualified call — your server calls Outbrain's tracking endpoint with the stored click ID and the event name:

https://tr.outbrain.com/pixel?ob_click_id=STORED_CLICK_ID&name=purchase

Two things must line up. First, the name value has to exactly match a conversion event you've created in Amplify's conversion settings as a server-to-server conversion — mismatched event names fail silently, which is the second most common setup failure. Second, the click ID must be the raw value Outbrain handed you, unmodified and untruncated.

The endpoint also accepts parameters for order value and currency so revenue flows into Amplify's ROAS columns; check the current conversion docs for the exact parameter names rather than guessing them.

Configure the event in Amplify first (conversions section → new conversion → server-to-server type), then send a manual test: click your own live ad, capture the ID, curl the postback, and confirm the conversion registers. Dashboard attribution can take a while to appear, so give it time before concluding it failed.

Step 3: verify and QA the whole chain

Run this checklist before trusting the data:

End-to-end test conversion from a real ad click on a real device, not a constructed URL — constructed IDs won't match a click on Outbrain's side.

Check the click ID lands in your tracker or database on every lander variant, mobile included.

Check the funnel's redirects — every hop must forward query parameters.

Confirm the event name in your postback matches Amplify's conversion configuration character-for-character.

HTTPS on the postback call, from your production server, not a staging box that fires test events into your live stats.

Deduplicate if you run pixel and postback in parallel — decide which is canonical for each event type, or your CPA will look better than it is.

Numbers still off after all that? Compare windows: your tracker attributes on click time, Amplify attributes within its conversion window — month-boundary conversions will land in different buckets and torment whoever reconciles the spreadsheet. The general architecture of all this is covered in our conversion tracking primer.

Automating the loop with the Amplify API

The postback closes the data loop; the Amplify API lets you act on it programmatically. Outbrain exposes a REST API for advertisers (authenticate with your Amplify credentials to obtain a token, then send it as a header on subsequent calls — the developer docs cover the current flow) with endpoints for campaign management, budgets, and performance reporting sliced by publisher and section.

The workhorse automation for S2S-instrumented accounts: join your postback conversion data with section-level spend from the reporting API, then push block decisions back — any section spending past a multiple of target CPA with zero conversions gets added to the campaign's blocked list on a schedule. That's the same cut-the-losers discipline Outbrain buying demands manually, running hourly without emotion.

Bulk creative uploads and daily spend syncs into a warehouse are the other two jobs that justify the integration effort.

The same pattern on every native network

Once the Outbrain integration works, you've built a template, not a one-off. Taboola, MGID, Revcontent, and the rest all implement the identical architecture with different vocabulary: a click-ID macro in the tracking URL, a stored identifier, and a network postback endpoint that accepts the ID plus an event name.

The parts that transfer directly are your funnel's parameter hygiene (redirects that preserve query strings), your server-side conversion capture, and your dedupe logic; the parts that change per network are the macro syntax, the endpoint URL, and where events get configured in each console.

Buyers running multi-network usually normalize everything into their tracker's sub-ID schema on day one — same slot always carries the placement, same slot always carries the creative — so cross-network reports line up without translation. Set that convention now, while you have one network, and the second and third integrations become afternoon jobs.

Reading the other side of the tracking chain

Everything above instruments your own funnel — but the same machinery is observable from the outside on everyone else's. Every Outbrain ad in the wild carries its tracking stack in the open: the redirect chain, the tracker domain, the parameters passed to the lander.

OpenAdLibrary captures this at scale — the index holds 108,000+ live Outbrain creatives (July 2026) with over 1.3 million traced landing captures across networks — so you can see which offers competitors route through which trackers and pre-landers, and how long each funnel survives. Longevity is the tell: a funnel that keeps spending for weeks is a funnel whose tracking says it's profitable.

The Outbrain ad spy guide covers the research workflow, and the Outbrain spy tool is where to run it.

Set up in an afternoon, S2S tracking is the highest-leverage plumbing in an Outbrain account: every optimization decision downstream — creative cuts, section blocks, bid changes, scaling calls — inherits its accuracy from this one integration. Get the click ID through the funnel intact, get the event names matched, verify with a real test conversion, and only then start trusting the numbers enough to automate on them.

outbrain s2s tracking postback conversion tracking