Media buyer tool 3 · Postback URL Tester for Outbrain
Test your Outbrain postback URL before the next conversion goes missing.
The advertiser's server or tracker sends a GET to Outbrain's unifiedPixel endpoint when a conversion happens, with the ob_click_id it stored from the landing URL. Below: Outbrain's postback format and macros as Outbrain's own docs give them, the ways a Outbrain postback usually breaks, and the tester, pre-filled with an example of the postback your tracker fires back to the traffic source. Edit it to match yours and run the check.
Nothing you enter leaves your browser.
Outbrain's postback format
https://tr.outbrain.com/unifiedPixel?ob_click_id=UNIQUE_CLICK_ID_VALUE&name=EVENT_BASED_CONVERSION_NAME
Outbrain's click-ID macro: UNIQUE_CLICK_ID_VALUE. Source: How do I set up server-to-server integrations? (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.
Outbrain macros
| Macro | Meaning |
|---|---|
| {{ob_click_id}} | Outbrain macro in the campaign Track box that populates the user's unique click ID |
| OutbrainClickId={{ob_click_id}} | the Track box entry shown in the docs |
| UNIQUE_CLICK_ID_VALUE | postback placeholder for the stored click ID |
| EVENT_BASED_CONVERSION_NAME | postback placeholder for the event name |
| ORDER_ID | placeholder for &orderId= |
| ORDER_VALUE | placeholder for &orderValue= |
| CURRENCY | placeholder for ¤cy= |
Parameter names on the receiving side
ob_click_id: required; the stored click IDname: required; event-based conversion name, case-sensitiveorderId: optional order IDorderValue: optional order valuecurrency: optional currencytimestamp: optional; docs list formats such as yyyy-MM-dd HH:mm:ss
How a Outbrain postback usually breaks
{{ob_click_id}} altered or missing in the Track box
Outbrain appends a unique click ID on every click and the Track box entry carries {{ob_click_id}}; the macro itself must stay as written.
Fix: Keep {{ob_click_id}} exactly, only rename the left-hand parameter if needed.
Click ID not stored server-side
Your server has to store the click ID per user so it can be sent at conversion time; without it the postback has no ob_click_id.
Fix: Capture the landing parameter and persist it with the lead/order.
Event name mismatch
name is required and event names are case-sensitive.
Fix: Use the exact event-based conversion name configured in Outbrain.
Wrong HTTP method
The postback request should be a GET.
Fix: Send GET, not POST.
Test your Outbrain postback
Pre-filled with an example: Outbrain's documented postback with example tracker tokens in place of UNIQUE_CLICK_ID_VALUE and the order value. Outbrain doesn't name them; use your tracker's own. Paste your own URL over it; the check runs in this page and fires nothing.
Not Outbrain's own macros: {click_id} (your tracker (example token)); {payout} (your tracker (example token)).
Want me to trace one real campaign?
This tool checks the postback URL and offer link you pasted from what you typed. It can't see your ad accounts, tracker, network or live traffic. If the result shows gaps, I'll look at one real campaign for free: I trace it from ad click to payout and back, and within 48 hours I send you a written report on where money or data leaks silently, the fix for each, and the tests that prove it's fixed.
In the review I fire a test conversion end to end on one real campaign and check it lands once, with the right payout, in your tracker and in your traffic source. You get the fix for every place it doesn't.
Shilpa Goel, [email protected]
This is an engineering checklist, not a security audit, legal, compliance or investment advice.
Not affiliated with or endorsed by Meta, Google, TikTok or any network or tracker named here.