Do you want to use the Outbrain Pixel without altering the HTML of your pages? If you use Google Tag Manager, you can implement our Pixel as a tag!
Already have the pixel installed? Check out how to set up a conversion for Time on Page and a Button Click.
Implementing the Pixel
You can implement the pixel via the Google Tag Manager Community Template Gallery. To do so, open Google Tag Manager and select Templates on the left hand side.
Next, in the Tag Templates section, click Search Gallery to access the Template Gallery.
Locate the Outbrain Pixel on the list and click on it to proceed.
Click the Add to Workplace button to add the template to your Workplace.
Now that the template is installed, you’ll need to create a new tag for the Outbrain Pixel. Start by by clicking on “New Tag” in your Tag Manager account and select “Tag Configuration”.
Under the Custom tag type, Click ‘Outbrain Pixel’.
On the next screen, add your Outbrain Marketer ID. You can find your Marketer Id on the Amplify Dashboard. It’s the alphanumeric chain that appears in the URL when you are viewing your dashboard. You can also locate it via the Pixel code. Navigate to the Conversions page and click on the “View Outbrain Pixel” button. Then you can copy your Marketer Id from the code snippet (It is a string of numbers and letters named “OB_ADV_ID”)
Lastly, set the Triggering to All Pages (Page View). This will allow the tag to fire on all pages. Click the Save button once complete.
Note that you will still need to define specific conversions in your Outbrain dashboard.
Implementing Event Based Conversions
To install event conversions via Google Tag Manager, begin by clicking on “New Tag” in your Tag Manager account and select “Tag Configuration”.
Head to the Custom Tag Type and Click “Custom HTML.”
Paste the event conversion code into the field below. Be sure to house the code within
<script> ,</script> tags.
For example, if you want to fire a conversion after a user stays on the page for 10 seconds, you can set it up like this:
We do not recommend appending the additional code into 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 incorrect 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.
For example, if the action was written as follows, you can set the ‘Click ID’ to targetlink1.
If you’re unable to locate “Click ID ” or “Click Class” in the Variables drop-down, you can configure which variables to show under “Variables” in the main dashboard.
Once you have created and saved your conversion points, use our Outbrain Pixel Tracker to test the pixel fire and implementation.
Want to implement our Pixel in Floodlight? Check out our guide!
For any further questions, feel free to reach out to our helpful team at firstname.lastname@example.org.