Outbrain & Taboola native ads UTM tracking
Outbrain and Taboola serve native content-recommendation ads across publisher sites. Both support UTM parameters on the destination URL plus dynamic tokens (for campaign, ad, and publisher) that they expand at click time. This page gives a recommended UTM structure and explains how to keep the two native networks distinct in reports.
Recommended structure
Tag each network with its own source and a shared native medium so they roll up cleanly:
- utm_source=outbrain or utm_source=taboola
- utm_medium=native (or paid-native, kept consistent)
- utm_campaign=<campaign-name>
- utm_content=<creative/ad identifier>
Dynamic tokens
Taboola supports tokens such as {campaign_name}, {campaign_id}, {site}, and {thumbnail} that it fills in at click time. Outbrain offers similar dynamic parameters for campaign, ad, section, and publisher. Use them to keep campaign and publisher detail without manual edits.
Worked example (Taboola):
https://example.com/?utm_source=taboola&utm_medium=native&utm_campaign={campaign_name}&utm_content={site}
Keeping the two networks distinct
Outbrain and Taboola often run similar creative across overlapping publishers. Distinct utm_source values are the only reliable way to compare them, because the referring publisher domain alone does not tell you which native network served the placement.
How it appears in analytics and logs
A visit with utm_source=outbrain or utm_source=taboola and utm_medium=native confirms a content-recommendation click. Untagged native clicks scatter across many publisher referrers, making the channel hard to total.
Diagnostic use case
Attribute native-ad clicks from Outbrain and Taboola to the right network and campaign, instead of letting recommendation-widget traffic blur into referral or direct.
What WebmasterID can help detect
WebmasterID attributes utm_source=outbrain and utm_source=taboola visits to your native campaigns server-side, so discovery-ad spend is reported as one channel rather than dozens of publisher referrers.
Common mistakes
- Using a single utm_source for both networks and losing the comparison.
- Encoding the publisher token as personal data instead of a generic site label.
- Mixing utm_medium=native and referral for the same channel.
- Forgetting to tag the URL, so native clicks scatter across publisher referrers.
Privacy and accuracy notes
Outbrain/Taboola tokens expand to campaign, ad, and publisher identifiers only. Never encode an individual reader. UTM values are public and stored in logs.
Related pages
- Display ads UTM tracking
Display and programmatic ads need their own medium so banner clicks are not confused with paid search or social. This page shows how to use utm_medium=display consistently and explains how platform click IDs differ from the utm_* parameters generic analytics tools read.
- Criteo retargeting UTM tracking
Criteo runs retargeting and commerce display ads across the open web. Its destination URLs can carry UTM parameters so retargeting clicks are attributed to the campaign rather than to generic display referrals. This page gives a recommended structure and the retargeting-specific caution about crediting visitors who would have returned anyway.
- UTM naming conventions that survive reporting
Most UTM data problems are naming problems. Because tools treat utm_source=Reddit and reddit as different values, inconsistent casing and spelling fragment one campaign across many rows. This page gives a convention — lowercase, hyphenated, documented allow-list — that keeps reports clean.
- Attribution analytics
Roll native-ad clicks up to one channel instead of many publisher referrers.
Sources and verification notes
- Taboola — URL tracking parametersDynamic tracking tokens for Taboola campaigns.
- Outbrain — Tracking and UTM parametersDynamic parameters for Outbrain campaigns.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.