vendor/outbrain · ecosystem evidence

Outbrain pixels need ob_adv_id or ob_click_id

Noscript pixels send ob_adv_id. S2S conversions send ob_click_id. Outbrain documents the Marketer ID in GTM rather than this query, so the pack is ecosystem evidence.

What this pack matches

Hosts: tr.outbrain.com
Paths: /pixel
Vendor docs: www.outbrain.com/help/advertisers/outbrain-pixel-gtm/

Rules

Codes are stable. A finding in CI, MCP, or the playground lands on the same id.

Field	Required	What it checks	Rule ids	Source
`ob_adv_id`	optional	It is the Outbrain Advertiser ID. Generated noscript pixels send it. Outbrain documents the Marketer ID in GTM rather than this query, so the rule is ecosystem evidence. Fix: Set `ob_adv_id` to the Advertiser ID from Amplify Tracking.	`vendor.outbrain.param.ob_adv_id.empty`	docs
`ob_click_id`	optional	It is the click identifier S2S conversions send instead of `ob_adv_id`. Fix: Set `ob_click_id` to the `ob_click_id` captured from the landing URL.	`vendor.outbrain.param.ob_click_id.empty`	docs
`identifier_required`	required	The pixel has neither `ob_adv_id` nor `ob_click_id`. Generated fires carry one of the two. Fix: Send `ob_adv_id` for a noscript or page-view pixel, or `ob_click_id` for an S2S conversion.	`vendor.outbrain.identifier_required`	docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack vendor/outbrain

Try this failing payload in the playground. Outbrain pixel missing ob_adv_id.

https://tr.outbrain.com/pixel?ev=PAGE_VIEW&noscript=1

cargo install pixellint · npm install pixellint