Outbrain Ads

Datafly Signal delivers conversion events to Outbrain server-to-server for native advertising attribution, campaign optimisation, and audience targeting across premium publisher networks.

Why route Outbrain through Datafly Signal

Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Outbrain optimises against are not filtered by the browser.
Email is hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Outbrain receives match keys rather than raw personal data.
Client IP and user agent are preserved. Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Outbrain attributes the event to the right session.
Click identifiers are captured and replayed. Signal stores clickid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Presets for Retail and Lead Generation. The mapping starts from a working configuration for your vertical instead of a blank field map.
One consent decision governs every destination. Outbrain is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Before configuring Outbrain in Signal, you need:

An Outbrain Amplify account with API access
Your Marketer ID
An API token for the Amplify API

Get your Outbrain credentials

Sign in to Outbrain Amplify.
Your Marketer ID is shown in the URL of the dashboard and on the account settings page.
Generate an API token under Account settings → API access (or request one from your Outbrain account manager if not visible).

See Outbrain’s developer documentation for details.

Configure the integration in Signal

In the Management UI, go to Integrations → Add Integration.
Select Outbrain Ads from the catalogue.
Give the integration a name (for your reference).
Fill in the required fields:

Field	Required	Description
`marketer_id`	Yes	Outbrain marketer ID.
`api_token`	Yes	Outbrain Amplify API token.

Choose which pipeline(s) this integration should run on.
Select consent categories (defaults to marketing).
Click Save.

API endpoint

GET https://tr.outbrain.com/unifiedPixel

Allow egress to tr.outbrain.com from the network your delivery workers run on.

Event mapping

Signal event	Outbrain event
`page`	`page_view`
`Product Viewed`	`view_content`
`Product Added`	`add_to_cart`
`Order Completed`	`purchase`

To customise, edit the integration’s Field Mappings.

Identity

Signal sends the following identity signals to Outbrain, subject to consent and availability:

Capability	Notes
Click ID	`ob_click_id` from the URL
Hashed email	SHA-256 (lowercase, trimmed)
Outbrain user ID	Where available via the Outbrain sync
Client IP / User-Agent	Forwarded from the original request

This integration is gated on the marketing canonical consent category.

Verify it’s working

In the Management UI, open Pipelines → your pipeline → Live Events and trigger a test event.
The event appears in the live feed; inspect the payload.
Check the Conversions view in the Outbrain Amplify dashboard.

Troubleshooting

Events not attributed to a campaign. Confirm Datafly.js is capturing ob_click_id from the landing URL and that the user reached the conversion in the same session.

401 Unauthorized. Regenerate the API token in Outbrain and update the integration.