IMPORTANT NOTE: Effective January 1st, 2025, Outbrain DSP will no longer support Adobe Analytics for conversion tracking due to significant API changes by Adobe. Please transition to the alternative tracking methods described below.
When you run campaigns in Outbrain DSP, it’s important to understand whether users viewing your ads or clicking on them take expected actions afterward so you can assign value to your campaign. For example, you might want to know whether the campaign led a user to view your landing page, download a file, subscribe to a newsletter, add a product to the cart, or purchase a product.
It is very important to set detailed conversion goals before starting a campaign. After you’ve decided what actions you’d like to track, you need to decide how you want to track them.
Outbrain DSP offers a few ways to track conversions on your ad campaigns:
Conversion Type | Tracking Options |
1. Website actions: landing page visits, add to cart, website purchases, etc. | |
2. App installs or other in-app events | |
3. Conversions tracked in Google or Adobe Analytics |
|
How Outbrain DSP Counts Conversions
Outbrain DSP Pixel counts every conversion based on a conversion definition that happens after a user clicks on an Outbrain DSP ad.
Example:
Outbrain DSP Pixel is placed on all pages of example.com
The user clicks on the Outbrain DSP ad and lands on example.com/promotion
Conversion definition is set to track example.com/promotion page visit
The user then clicks on the link on the promotion page and visits example.com/read-more
Another conversion definition is set to track the example.com/read-more page visit
Lastly, the user navigates back to example.com/promotion
In this example, Outbrain DSP will count 2 conversions for that click (one per each unique URL).