datascale
DEEN
Contact
Ads & Conversion APIs

Outbrain Server-to-Server Tracking: The Setup

Native ads with postback logic. Server-to-server over the click ID is the sturdier path here, not the exception.

Request a setup → Vendor site ↗

Event setup at a glance

Browser tag
Outbrain Pixel
Server-side API
Server-to-Server (S2S) conversion tracking
Recommended path
Server-side only
Deduplication
No

Identifiers

Requiredob_click_id

Event mapping

E-commerce

Purchase

Leads

Lead

Consent constraints

  • The S2S path also fires only with marketing consent; the click ID is persisted only after opt-in.
  • No clear-text PII in postbacks, the click ID alone carries the attribution.

Consent-aware routing assumed. Privacy fit depends on the concrete setup; the legal assessment stays with your privacy team (legal review required).

Implementation methods

  • Persist the click ID from the landing URL in the server container, send conversions as postbacks
  • One path, not both, pixel and S2S in parallel double-count without a dedup anchor

Debugging checklist

  1. Outbrain conversion diagnostics in the dashboard
  2. sGTM preview mode

Common mistakes

  • Click ID lost in consent redirects or URL rewrites, conversions stay unattributed.
  • Pixel and S2S active at the same time, every conversion counts twice.

Runs on (our setups)

Google Tag Manager Server-Sidestape.io

A fit when

  • Native campaigns with conversion goals instead of pure reach.
  • A server container can persist click IDs and send postbacks.

Not a fit when

  • Redirects and URL rewrites cannot be controlled; the click ID dies en route.
  • Outbrain serves as a traffic source only, without conversion measurement.

What this destination is about

Outbrain ticks differently from the social platforms: instead of pixel-plus-API with deduplication, it is an either-or, and the server path over the click ID wins. The discipline sits in URL handling, not event mapping.

How it compares to Meta, Google, and the rest is on the ad platform hub.

For a self-run QA pass: the Consent Mode audit checklist, the CMP QA template, and the consent mapping worksheet.

Sources

Related services

Topical context

  • Outbrain S2S tracking setup
  • Outbrain conversion tracking
  • native ads postback

Do your conversions actually arrive in the ads platforms? The Paid Media Tracking Audit settles it.

Request a Paid Media Audit →
  • Q01
    Why server-only instead of hybrid like Meta?

    Outbrain does not deduplicate over a shared event ID. Two parallel paths therefore mean double counting; the S2S path via the click ID is sturdier on its own than the pixel on its own.

More integrations we work with

← Back to all integrations