Integrating Ad Servers¶
Google Ad Manager (GAM)¶
By connecting to your own GAM account, you can choose to use our tech for its high-impact ad formats and our easy-to-use management and reporting platform while remaining in complete control of demand.
Google Ad Manager currently only has a single level of access that a platform can request from a user, and that is complete access to an account.
Unfortunately, this makes it seem that we are accessing more than we require, but there are currently no other options. What we actually do with our access is explained below
You have two connection types to choose from when connecting to GAM:
Reporting & Management (recommended)
This option allows us to create all the ad units needed for our ads to serve, shortcutting a chunk of manual work by your team. Each new ad unit you create in our platform can then be created in your GAM as needed. We will also handle the complex MCM flow and site approval process, all requirements of Google to allow the serving of ads; you can therefore be confident that once everything is ticked off in our UI, that you are 100% set up to successfully serve ads. We will also pull in your reporting data each morning, allowing you to see everything in one place inside our platform blended with our own reporting data.
Would rather keep our access to the bare minimum? No problem. We will not pull any reports or attempt to automate any part of your account set up other than syncing the required ad units. You will continue to see basic summaries of ad impressions per ad unit for billing but benefit from the time savings of ad unit set-up.
What exactly do we do inside your GAM account?¶
As part of our core "Restricted" integration, we create ad units. That's it. Our tag requires a parent ad unit (often the domain name of the publisher) and child ad units of a certain set-up. For example, we need a child unit for each config such as
1234 is the config id. These must be present with correct naming to work.
As simple as this sounds, we do all this intelligently and efficiently. Our integration works tirelessly behind the scenes to ensure that upon every change you make, the required GAM units are present and correct so your publisher tag can serve ads without issue.
What we do not do is touch anything to do with ad serving, you can attach your own placements as needed and target demand in any way you see fit to ensure your partnership with Content Ignite does not affect the processes you already have in place as an organisation.
Op for our full integration, and benefit from even more automation:
You and your customers will be able to trigger Googles Multiple Customer Management (MCM) flow. This is a required link between you and your customer for non-owned sites. It tells Google that the publisher has granted you permission to monetize their site. This involves creating a company in your GAM and sending out an invite to your publisher. The publisher then needs to accept the invite. Our full integration allows a user to send the invite to themselves and handles the set up in your GAM automatically, setting the required MCM id at the tag config level on completion and submitting the seller_id in order to complete the supply chain object (part of the ad industries bid transparency specification and required by many partners). That's a lot of steps that you'd have to remember to avoid disruption to ad serving!
Once MCM is complete, the publishers domain needs to be submitted and approved by Google. MCM acceptance is detected automatically and site submission is handled immediately, no input needed! Your publisher will be informed of the status of this process through out, including any issue that arise so you can work through it with them
It is critical that you target demand in some way, to allow ads to show. This can be done by targeting line items to the parent ad unit, or by assigning the units to placements and targeting those. There are many ways to target demand that ultimately comes down to preference and the way you have structured your GAM. The method does not matter (one of the many benefits of Content Ignite SaaS), so long as it is in place.
SaaS without GAM Integration¶
For those with trust issues (we get it, especially given Google access roles), you can opt for the fully manual route. Where the set-up of ad units is left to you and your Ad Ops team.
Ad unit set up can take two forms:
- A single unit - This is simple to set up, but limits your reporting
- A child unit for each tag config - By far the best set up, but without the API integration, it could be time consuming to implement
Our tag will always take the given parent ad unit you provide, and attempt to fetch from the child unit named after the tag config that target matched against it. For example, if you have an in-image unit set up via config 678, we will attempt to call, for example:
If that child unit is not found in your GAM account, Google will assume serving from the next parent up:
/1234/example.com/. This means you can get away with a simple set up, but you do forfeit reporting down to the tag config level (which might be fine if you are only running one unit with us).
Be warned that as we roll out new features, GAM setup requirements may change and you will need to make changes to accommodate this. Additionally, we can not provide support to these types of setups.
By going down the manual route, you will lose out on:
- Being able to enter ads.txt requirements and having our system inform publishers of missing lines as well as seeing a network-wide health report on ads.txt completeness
- Having units sync automatically as new tag configs are added (ensuring ads always have what they need to serve to the page while efficiently only creating units that we know will get used)
- Having unit requirements update automatically as new features and units are rolled out
- Auto-synchronisation of audience keys
- The full support of our expert team to help if any issues do arise
- Speedy single platform rollout of new publishers
- MCM handling
- Site approval handling
We don't require much in the way of set-up in your GAM account, other than the parent ad unit, you are left to target demand in any way you see fit!
One requirement to consider is native ads inside our adhesion and in-image units:
To prevent large native ads from rendering inside your adhesion or in-image unit, you need to limit the sizing via native templates inside your GAM. These are targeted to just Content Ignite placements, so they won't affect your wider network.
The steps are as follows:
- Inside GAM, head to Delivery > Native
- Click “New native ad” and select “Single ad"
- Select “Guided design editor"
- Select ad size “728x90” and click continue
- Click continue again
- Use the inventory section to target just the Content Ignite in-image inventory (in-image and adhesion placements if used)
- For device category, select Desktop and Tablet
- Name the template at the top of the page (e.g. Content Ignite Native In-Image - Desktop)
- Hit “Save and activate"
- Repeat steps once more, but this time select “320x50” for the size and “Smartphone" and "Feature phone" for the device category
Our video instream unit is built for pre-, mid- and post-roll ads only and does not support display "bumper" ads. Ensure "Inventory format” is set to "In-stream video and audio” only inside your line-items.
MCM - Linked Account¶
Googles Multiple Customer Management (MCM) is a required link between a GAM360 integration and an organisation for non-owned sites. It tells Google that the publisher has granted the integration permission to monetize their site.
Don't worry if you do not have an existing GAM account to link to, the invite that gets sent out will allow you to create a new one or pick an existing one. This is a quick process to set up, and does not require any knowledge of GAM, in fact, once you have accepted the invite and set up your account, you needn't ever use it again.
In the Content Ignite platform each organisation can link to a single MCM agreement, where each MCM agreement can link only to a single organisation.
You can share an MCM connection through organisation hierarchy, child organisations will have the ability to select the parents MCM at the tag config level, giving you the flexibility to structure your publishers as needed.
MCM also ties in tightly with the Supply Chain Object (SCO), an industry technology aimed at increasing transparency in the bid request. More and more buyers will require this to be in place to bid, so it is highly important to have in place to protect from revenue loss.
How do we decide when and where to apply MCM?¶
MCM is a requirement of GAM360 accounts, so if you are using Content Ignites ad demand, or connect in a GAM360 account for SaaS usage, you will need to have MCM in place.
However, MCM only applies to non-owned sites. Under publisher settings you can mark a publisher as "Owned and Operated" (O&O) by a particular organisation. This gives us the ability to deduce the correct MCM requirements.
For example, if you use Content Ignite demand, your site will not be marked as O&O by Content Ignite, so we know to apply MCM. If you were a SaaS user with organisation "X" connecting in their own GAM360 account, MCM would apply by default, but if O&O is also set to "X" then MCM can be bypassed as it does not apply.
If there is MCM connected to the current organisation, and the parent organisation, you will be given the option to choose which applies when selecting the ad server during tag config set up.
The current MCM connected to the logged in organisation can be viewed from the "Integrations" section. Selecting "Manage" allows users to send out a new invite to connect in a new MCM. Users who have owner access to an integration can change an organisations MCM link to any non-assigned MCM agreement where all tags will be updated accordingly.