Skip to main content
All CollectionsReporting & TrackingConversion Tracking
Implementing Outbrain DSP Pixel Using Google Tag Manager (Custom HTML)
Implementing Outbrain DSP Pixel Using Google Tag Manager (Custom HTML)
Updated over a month ago

Do you want to use the Outbrain DSP Pixel without manually altering the HTML of your pages? With Google Tag Manager, you can implement our DSP Pixel directly.

How To Implement Outbrain DSP Pixel

1. Navigate to the Google Tag Manager.

2. Select your website from the list and click on the Add a new tag button.

3. Give it a name (for example, Outbrain DSP Pixel), click on the Tag Configuration field, and select the Custom HTML option.

4. Paste in the Outbrain DSP Pixel code. You can find the code in the Engagement Tracking section within the DSP dashboard by clicking on the View tag button.

5. Remove the part between <noscript> and </noscript> with tagnames included.

6. Make sure that the Outbrain DSP Pixel triggers on All Pages.


7. Click the Save button.

PLEASE NOTE: You must still define specific conversion definitions in the Outbrain DSP dashboard. To learn more about conversion definitions, click here.

How To Implement Event-Based Conversion Definitions

1. To implement an event-based conversion definition JS snippet via Google Tag Manager, begin by clicking on the New Tag button again.

2. After giving the event-based conversion definition a custom name, head again to the Custom Tag Type and select the Custom HTML option.

Custom HTML

3. Go to the Conversions section within the Outbrain DSP dashboard, find a previously added event-based conversion definition, and copy the JS tag.

4. Paste the tag code into the field below.

For example, if you want to fire a conversion after a user visits a page, you can set it up like this:

5. Remove the part between <noscript> and </noscript> with tagnames included.

We do not recommend appending the additional code to the base code and triggering it on a specific action. This will cause a time lag from the action to the pixel fire, and you may experience inaccurate conversion data.

If you want to fire a conversion after a button has been clicked, follow the same steps above and choose All Elements as the trigger type. Have the trigger fire on Some clicks and enter the Click ID or Click Class that the action is associated with.

Did this answer your question?