Connect your ad tech vendors to one tag
Fusion connects the ad tech vendors you already use to your publisher tag: consent management platforms (CMPs), identity providers, ad-block recovery, Google Analytics, Slack and your own Google Ad Manager. You connect each vendor once, choose which sites and ad stacks use it, and Fusion puts its script on the page in the right order, checks consent before any personal data moves, and reports on the result.
From connecting a vendor to it running on your pages
- 01Connect the vendorPick the platform in Integrations. Some ask for account details; others send you to their site to confirm, then back to choose which accounts to connect.
- 02Accept terms if neededVendors that handle personal information, such as email-based ID providers, need their terms accepted in the Policy Centre first.
- 03Add it to your sitesAdd publisher-level vendors (CMPs, IDs, ad-block recovery) in each site's settings, and demand-side parts to an ad stack.
- 04Fusion runs itThe tag loads the vendor's script when it is needed, waits for consent before passing personal information, and reports on the result.
Ad tech vendors that work with Fusion
These sit alongside your demand partners. Each links to its integration page.
| Type | Vendors | What Fusion does | Where you see it |
|---|---|---|---|
| Consent management (CMP) | Sourcepoint, InMobi, Ketch, Cookiebot, Clickio, Prebid consent modules | Puts the CMP on the page before ads are requested. Prebid's GPP consent module switches on automatically when a GPP CMP is on the page | CMP errors, stub status and consent rate in Diagnostics |
| Identity (ID) providers | UID2, EUID, RampID, SharedID, Criteo ID, PanoramaID, Hadron ID, AMX ID, Google PAIR, PPID | Deploys the ID script on the page and passes the ID into the bid stream. You pass email or phone once through the tag; it only goes to a provider after consent | Revenue impact, measured with an experiment |
| Ad-block recovery | Blockthrough | Activates the recovery script correctly on the page | Your ad block rate |
| Contextual and brand safety | Mantis | Adds the vendor's contextual and brand safety signals. Fusion also has its own contextual targeting | Targeting and brand safety for your campaigns |
| Analytics | Google Analytics (GA4) | Joins your GA4 traffic with ad revenue. Map properties by organisation or by site, and filter out traffic such as syndication partners | Revenue Analytics and the Traffic Stats tile in Diagnostics |
| Communication | Slack | Sends Fusion events to the channel you choose: health alerts, ads.txt updates, experiment results, integration expiry and more | Your Slack channel, alongside Alerts |
| Ad servers | Google Ad Manager, EX.CO | Connect your own Google Ad Manager to use it with Fusion's tag, formats, floors and reporting, use ours, or both. EX.CO adds its video platform | Google Ad Manager and unified reporting |
| Fallbacks | Revcontent | Fills slots no paid ad wins with native backfill or your own house ads | Demand Mix |
Who can use each vendor, and where
Integrations are managed at organisation level, so a network with many sites sets each vendor up once.
| Control | What it does |
|---|---|
| Built-in or your own | Use Content Ignite's built-in connections to get started, or connect your own accounts and leave ours out entirely. |
| Filters | Include or exclude organisations and sites for each integration, so only the right option appears when building an ad stack. No picking the wrong account. |
| Organisation hierarchy | Connect once at the top of your organisation and every child organisation can use it, unless you filter it out. |
| Mapping | Store each site's ID for a vendor once, so a shared ad stack uses the right ID on every site. |
| Ads.txt requirements | Attach the ads.txt lines an integration needs, with macros for each site's IDs. Sites see them as go-live requirements, and missing lines are checked daily. |
| Policy Centre | Vendors that handle personal information can't be switched on until their terms are accepted, so nothing is activated without your say-so. |
Where publishers got to on Fusion
Results are for each publisher's whole Fusion set-up.
Ad tech vendor integration questions, answered
Which ad tech vendors can I connect to Fusion?
Should my CMP load through Fusion or directly on my site?
Does Content Ignite provide a CMP?
How do ID providers work in Fusion?
Is personal information shared before the reader consents?
How do I know whether an ID provider is worth it?
What Slack notifications can I get?
Do integrations expire?
How do I check whether a vendor script is slowing my site?
cipt_disable_tech=true to a page URL. It switches off all third-party tech in the publisher and ad stack, including CMPs, ad-block recovery, brand safety scripts and ID solutions, leaving only core ad serving. If the page speeds up, one of them is the cause. See the ad debugging guide.Are you an ad tech vendor or SSP looking to integrate with Fusion? Get in touch.
Bring your vendors. Keep control.
Get a free Revenue Healthcheck: your CMP set-up, ads.txt, tags and header bidding scored and benchmarked against similar publishers.