Implementing //Connect can be done by adding the code to your site, by Google Ad Manager or by using Google Tag Manager. Learn how in this article.
To traffic your //Connect code via Google Ad Manager, you will need to use a 1x1 ad unit. You can either setup a new 1x1 ad unit, or you can edit an existing one.
There are 7 total sets of instructions in this article as well as additional resources provided:
- How to edit an existing ad unit to include //Connect
- How to create a new ad unit to include //Connect
- The best way to generate the 1x1 ad unit code
- Tips on setting up your line items
- Setting up your line item creative
- Implementing //Signal through a OOP ad unit
- Implementing //Connect via GTM (Google Tag Manager)
- Additional Resources
Implementing an EXISTING 1x1 ad unit
These steps will help you traffic the //Connect code via a line item targeted to an existing 1x1 ad unit. As a best practice, we recommend using a 1x1 ad unit not targeted by any other line item.
1) Use an existing 1x1 ad unit
2) Find the line item targeted to the 1x1 ad unit in Google Ad Manager by navigating in Delivery section or searching for that line item
3) Add the creative that will be set up for the 1x1 line item
4) If you’re using a new creative, use the custom creative type to deliver the the Sovrn //Connect code
5) Be sure to uncheck ‘safe frames’ which is usually checked to enabled by default.
Creating a NEW 1x1 ad unit
1) Create the unique ad units targeted to custom ad unit size 1x1 to enable the desired custom behavior (ex: Sticky ad units, reload, etc.)
IMPORTANT: All other ‘Ad Unit’ settings can be left to default. Do not change anything here.
2) Do not include any refresh functionality. //Connect will take care of that on its own.
3) This new 1x1 ad unit would ideally not be targeted by any other regular line items in your DFP network.
4) For easy reference, we recommend that the code is the same as the name.
Generating the 1x1 ad unit code
These instructions will help you generate DFP GPT ad unit code to place on header & body of site page(s).
1) For //Signal reload functionality you need to start in the Ad Units screen. Open up the ad unit that you want to edit and click "Generate Requests"
2) Select Google Publisher Tag and click Continue.
3) Uncheck ‘enable single request’ for the 1x1 ad unit to be called properly upon reload instead of initial pageview.
4) Leave all the other default options in place all the way to the last screen where you can copy the generated code and paste the header code into the <head> of your web page and body code into the <body> section of your web page.
Creating Ad Manager line items
1) Create Line Item
2) Type = Sponsorship
3) Targeting 1x1 size
4) Start / End Dates
5) $0.00 CPM (Our recommendation is to start at $0.00)
6) Target the 1x1 ad unit created in the previous steps.
7) You can add your creative (where you will paste the 3rd party ad code, ex. Sovrn //Connect) to the line item as a part of your save process.
8) Or you can just save the line item and add the creative separately or at a later time.
Setting up of your Ad Manager line item creatives
1) Set up the creative as third party creative, give it a name, insert the //Connect script tag provided by Sovrn into the creative settings, and uncheck ‘Enable SafeFrames’
2) Once the ad unit code is on the site and the Line item or Order that the line item is organized under is approved, then it should begin delivery typically within the hour
Implementing Signal through an OOP Page Slot
The below instructions are for those delivering //Connect via an Out-of-page (OOP) ad unit. While this is similar to the 1x1 implementation method, there are some small variations that are important to note.
- Even though Out-of-page (OOP) units are usually 1x1 in size, if you’re delivering //Connect through an OOP unit, please ensure you define the size as only OOP in the line item settings.
- In ad unit targeting, select the OOP units you would like to target.
- Having completed all other line item settings (see: the Setting up line items section above), you will then need to add a creative. Please select “Custom” creative from the list.
- When adding the //Connect tag to the Code Snippet section, you will also need to add in at least one macro. You will not be able to save the creative without doing this. The mandatory macro to add is the View impression macro. This is needed for GAM to track line item impressions to the OOP slot. The second macro you may add is the click tracker macro, which is optional. This allows GAM to track clicks. You do not need to track clicks in the //Connect line item as clicks are being tracked on the reloaded creatives instead.
This is how it should look:
Implementing //Connect via GTM (Google Tag Manager)
Another way of implementing the //Connect tag is via GTM.
To deliver your //Connect code via GTM, first go to tagmanager.google.com.
When you are on the Workspace page, click on the Overview Tab and then
“Add a new tag”
On the window that pops up:
click on Tag Configuration
Then on the top right,
click on the search icon and type “HTML”
Select the custom HTML tag type
You are now able to pass the Connect tag.
It should look similar to this:
Then scroll down to choose a triggering method according to your preferences and save.
The last step is to install Google Tag Manager on the page if you have not done it previously.
Simply click the GTM id under the main search bar and follow the instructions.
That’s it! Enjoy.
Here are some reference links from Google for more implementation related information:
- Ad Manager documentation - create an ad unit
- Ad Manager documentation - generate ad tags (ad unit code)
- Ad Manager documentation - create a line item
- Ad Manager documentation - traffic 3rd party creatives
If you need greater help, reach out to our publisher support team for the help that you deserve.