BASE CMS
Documentation Home
  • Getting Started
  • Content Management
    • Searching for Content
    • Adding and Editing Content
      • Attribution
    • Scheduling
      • Troubleshooting
    • The WYSIWYG Editor
    • Embedding Content
      • Third-party content
      • Images
      • Custom (IFrames)
    • Content Types
      • Contacts
      • Documents & Whitepapers
      • Media Gallery
      • Page
      • Promotion
      • Video
    • Content States
    • Retrieving Deleted Content
    • Taxonomy
    • Media
      • Supported File Types
      • Image Specs
      • Why are my images uploading sideways?
    • Engagement Report
      • How to Access
      • Company Details
      • Content Overview and Share
      • Content Effectiveness
      • Appearances in Categories and Channels
    • Gated Content
      • Wufoo
  • Print Issue Management
    • Publications
      • Updating Magazine/Publication Links & Info
    • Issues
    • Scheduling Content to Magazines
  • Newsletter Management
    • New Framework
      • Newsletter Structure
      • Scheduling Content to Newsletters
      • Previewing Newsletters
      • Modifying Newsletter Templates
      • Adding Newsletter Revisions
      • Campaign Deployment
        • Using BASE for ESP Integration
          • Initial Omeda Requirements
        • Extracting the HTML for deployment
    • Legacy Framework
      • Block Structure
      • Scheduling Content to Newsletters
      • Previewing Newsletters
      • Modifying Newsletter Templates
      • Campaign Deployment
        • Initial Omeda Integration Requirements
        • Extracting the HTML for Deployment
      • Adding Newsletter Revisions
      • Digital Editions
  • Administration
    • Google Tag Manager
      • Adroll Pixel
  • Contract Management
    • Types of Contracts
      • Contributor Agreement
      • Contributor Work-For-Hire
      • Internal
      • Photo Release
      • Work-For-Hire
    • People
Powered by GitBook
On this page
  1. Administration
  2. Google Tag Manager

Adroll Pixel

Adroll pixels are a common marketing strategy put in place on a majority of our existing websites via Google Tag Manager. Instructions on how to implement can be found here.

PreviousGoogle Tag ManagerNextTypes of Contracts

Last updated 4 years ago

  1. Login to

  2. Find associated site/container. We'll use bioopticsworld.com as an example here:

3. Click on "Add a new tag"

4. Name the tag whatever you feel is appropriate (in this case we used "Adroll") then click on the area that says "Choose a tag type to begin setup"

5. There are many different options for tags. In this case, GTM has what we need built right into the interface - "Adroll Smart Pixel", which makes this a very painless addition. In other cases, you have the ability to custom tags using the "Custom HTML" option, and can be a little more creative with how scripts are implemented. In this case, we'll just select "Adroll Smart Pixel":

6. Fill in the two fields "Advertisable ID" and "Pixel ID" with the corresponding IDs found in the provided adroll script, which should look something like this:

7. Scroll down and click on the "Choose a Trigger" area

In this case, we want the adroll pixel to fire on every page on page view, so we're going to choose "All Pages":

9. Once that's done, click "Save" in the upper-right corner. From here, you can choose to "Preview" the workspace changes, or "Submit" the workspace changes. If you'd like to check your tag and make sure it's firing, click "Preview", open a new tab, and go to the website. You should see a window at the bottom of the screen that displays the tag info:

10. When the tag is confirmed as firing properly, switch back over to GTM and "Submit" your workspace changes

Feel free to add a version name and description as you choose, such as any ID or ticket numbers, or a description of what's being accomplished with the created tag.

8. Triggers are exactly what they sound like - they depict when the tag is triggered to fire on the website. With the right trigger, we can have tags fire only on specific pages by following a URI rule (If uri includes "/blogs/", for example, the page would only fire on pages with "Blogs" in the URI, etc.). We can use the same logic to exclude certain pages as well, and we can even go so far as to dictate whether or not the tag fires on DOM Ready, Page View, or Window Loaded. More on that can be found here:

https://support.google.com/tagmanager/topic/7679384
https://tagmanager.google.com