One Tag

One ad tag to replace your Google Publisher Tag and Prebid code

One Tag is the Fusion publisher tag: a single asynchronous script that replaces Google Publisher Tag and Prebid code on your site. Add it to your site's head once, after your CMP stub. Ad units are then placed with CSS selectors, and header bidding, floors, refresh and targeting are managed in Fusion, so changing your ads never needs a code release.

Replacing Google Publisher Tag

Every slot defined in code, or one tag

With GPT, each ad slot needs a definition in your head and a display script in its container. With One Tag, both go: your containers stay, and Fusion targets them by ID.

Before: Google Publisher Tag

<head>
  <script async
    src="//securepubads.g.doubleclick.net/tag/js/gpt.js"
  ></script>
  <script>
    googletag.cmd.push(function () {
      googletag.defineSlot('/1234/example.com/unit_1',
        [300, 250], 'div-gpt-ad-1')
        .addService(googletag.pubads());
      googletag.enableServices();
    });
  </script>
</head>

<div id="div-gpt-ad-1">
  <script>googletag.display('div-gpt-ad-1');</script>
</div>
<!-- …repeated for every ad slot -->

After: One Tag

<head>
  <!-- your CMP stub first, then: -->
  <script src="https://cdn.tagdeliver.com/cipt/12345.js"
          async="async"></script>
</head>

<div id="div-gpt-ad-1"></div>
<!-- target "#div-gpt-ad-1" in Fusion. That's it. -->
How One Tag works

Three steps, then no more ad code

  1. 01
    Add the tag to your head
    Place your publisher tag in the head of every page, after your CMP stub. It is unique to your site, loads asynchronously and is served from a global CDN.
  2. 02
    Point ad units at your page
    Each ad unit targets a CSS selector: an existing GPT container ID, a class, or every third paragraph of an article. Your existing ad containers can be reused as they are.
  3. 03
    Manage everything in Fusion
    Demand, floors, refresh, in-view loading and targeting are set in the platform and pushed to the live tag automatically. Try a change on one section first with URL path targeting, or A/B test it with Experiments.
Ways to deploy

Tag on page is fastest

Every method runs the same tag. What changes is how long it takes to reach the page, and slower ads earn less.

Comparison of ways to deploy the One Tag: tag on page, WordPress plugin, Google Tag Manager, ad server and organisation tag
MethodHow it worksSpeedBest for
Tag on pageRecommendedPaste the tag in your site's head, after your CMP stub, onceFastest: no extra hops before ads loadAny site where you can edit the head
WordPress pluginInstall the Content Ignite plugin and enter your publisher IDSame as tag on pageWordPress sites
Google Tag ManagerFire the tag from a GTM containerAdds latency before the tag loadsSites where code changes are slow to get released
Ad server (1x1)Serve the tag from Google Ad Manager in a single-serve 1x1 unitSlowest: the ad server call comes firstShort tests, or when nothing else is possible
Organisation tagOne tag across a network of sites that loads each site's tag by domainOne extra network hopLarge networks managed centrally

Whichever method you use: keep your CMP stub inline in the head before the tag, and exclude the tag and your CMP from script deferral and bundling tools.

FAQ

One Tag questions, answered

What is One Tag?
One Tag is Content Ignite's publisher ad tag for the Fusion platform. It is a single asynchronous JavaScript tag that runs every ad unit, demand partner and setting on your site. You add it once to your site's head, and from then on ad placements, header bidding, floors, refresh and targeting are configured in Fusion instead of in your site code.
How does one tag place ads without code for every ad slot?
With Google Publisher Tag, every slot is defined in your page code and needs its own display call. One Tag uses CSS selectors instead: a unit can target an existing div ID, a class, or a pattern such as every third paragraph of an article. Selectors, sizes and ad products are all set in Fusion, so adding or moving a unit is a platform change, not a development release.
How do I replace Google Publisher Tag with One Tag?
Swap the gpt.js script in your head for your Fusion publisher tag, then remove or comment out the googletag slot definitions and the display scripts inside your ad containers. Keep the containers themselves, and enter their IDs in Fusion as unit targets so ads appear in the same places. Because the containers stay, you can switch back at any time.
Where should the tag go, and will it slow my site down?
Put the tag directly in your site's head, after your CMP stub. It loads asynchronously from a global CDN (typically around 40ms to deliver), so it doesn't block your content, and ads can load only as they come into view. Keep the tag and your CMP out of script deferral tools such as Cloudflare Rocket Loader, which delay ads and can break consent. You can track the effect on Core Web Vitals in the Insights Hub.
Can I deploy the tag through Google Tag Manager or WordPress?
Yes. There is a Content Ignite WordPress plugin, and the tag can also be fired from Google Tag Manager or served from your ad server in a 1x1 unit. Placing it directly in the head is recommended, because Tag Manager and ad-server delivery add latency before ads load, and slower ads earn less.
Does One Tag work with my own Google Ad Manager and SSPs?
Yes. The tag can run your Google Ad Manager and SSP contracts, ours, or both, with one ad server taking a second look at anything the other leaves unfilled. Your existing ad containers and line items can stay as they are, and "Fusion Mapped" keeps your GAM ad unit structure unchanged. See Google Ad Manager for the options.
How do I test a change before rolling it out?
Changes made in Fusion are pushed to the live tag automatically. To limit a change to part of your site first, use URL path targeting to run a new config on one section or a single article, or set up an experiment to A/B test it against your current set-up on live traffic.
How does One Tag handle consent?
The tag reads consent from your TCF-certified CMP and serves non-personalised ads if consent was not given or could not be obtained. It also honours Global Privacy Control (GPC) signals. Place your CMP stub inline in the head, before the CMP and the tag, or deploy your CMP through Fusion so the order is handled for you. See privacy and compliance.

Swap your ad code for one tag.

Get a free revenue healthcheck, or sign up and be live within days.