Privacy. Data Protection. By Design.
Content Ignite reads your visitors' consent from your consent management platform (CMP) through the IAB's TCF and GPP frameworks, and serves non-personalised ads when consent isn't given. We are a registered IAB Europe TCF vendor (ID 656) and do not store personally identifiable information. ID solutions such as UID2, EUID and RampID only go live after someone at your organisation accepts their terms in Fusion's Policy Centre.
How consent reaches your ads
- 01Stub firstA small stub script, directly in the page head, tells our tag a CMP is coming. The tag then waits for the visitor's choice instead of loading non-personalised ads too early.
- 02Your CMP asksYour TCF- or GPP-compatible CMP collects the visitor's choice. Content Ignite and our demand partners must be enabled in its vendor list.
- 03Our tag reads itWith consent, ads can be personalised. Without it, or with no CMP, ads are non-personalised. The tag also honours Global Privacy Control (GPC) signals.
- 04Diagnostics checks itFusion's Diagnostics report shows stub status, the CMP error rate and the consent rate our tag sees, and flags sites where no CMP is found.
Our Four Pillars to Achieve Privacy By Design.
Content Ignite's overarching goal is to create solutions that consistently meet the highest standards of privacy. Here is what each pillar means in practice.
| Pillar | Principle | In practice |
|---|---|---|
| 01. Minimisation | Limited. Contextual. Pseudonymous. | We don't store personally identifiable information. Contextual audiences are built from page content, with zero PII. |
| 02. Obfuscation | Hashing. Truncation. Encryption. | To estimate unique users we store a hash of identifiers, discarding over 70% of it so it can't be reversed. |
| 03. Limitation | Time-Bound. Expected. Contracted. | Server logs and hashes are stored for 5 days. ID solutions only run after their terms are accepted in Policy Centre. Our Data Processing Addendum sets out processor obligations. |
| 04. Consent | Registered IAB TCF Vendor | Vendor ID 656. The tag reads TCF and GPP consent, and only sets a publisher-provided ID (PPID) when the visitor has given consent. |
Your part, and ours
Responsibility for your CMP sits with you, as the publisher. Here is where we take over, and how Fusion helps with the rest.
| Task | You, the publisher | Content Ignite |
|---|---|---|
| Choose a CMP | Pick one that is TCF- or GPP-compatible (TCF-certified, with a native SDK, for apps). We don't ship a default CMP, so the choice stays yours. | Advise on CMPs, and deploy supported ones (such as Sourcepoint, Cookiebot, InMobi and Clickio) through Fusion, which removes the need for a stub. |
| Get it on the page | Put the stub inline in the page head, before the CMP and our tag. Exclude both from caching plugins such as Rocket Loader. | Diagnostics checks stub status, CMP errors and consent rate every day. |
| Vendor list | Keep Content Ignite and our demand partners enabled. If we're missing, consent reads as missing. | Act as gatekeeper: if a visitor disallows personalisation for Content Ignite, all our demand partners get non-personalised ads. |
| US privacy laws | Use a GPP CMP where you serve visitors covered by US state laws. | Turn on Prebid GPP consent management automatically when a GPP CMP is on the page, honour GPC, and offer an opt-out of personalised ads. |
| ID solutions | Accept the provider's terms in Policy Centre, update your privacy policy if they require it, and pass email or phone through our JS API. | Pass the data client-side, only to providers you approved and only after consent via your CMP. It never reaches our servers. We act as a data processor. |
| Ads.txt and supply chain | Host the lines Fusion lists on your root domain. | Crawl your ads.txt every 5 hours and flag gaps in Ads.txt Insights. We publish our sellers.json. |
Monetising an app? A TCF-certified CMP with a native SDK is required, and consent should be gathered before the Content Ignite Mobile SDK requests its first ad. See privacy and consent for apps.
Identity, only with your approval
ID solutions turn a reader's email address or phone number into an ID that is passed into the bid stream. Any integration that involves personal information is listed in Fusion's Policy Centre, with its terms, and needs explicit approval from someone in your organisation before it can go live on a site. Content Ignite is the "pipes" between you and the ID provider.
- 01Accept the termsIn Policy Centre, someone at your organisation reads and accepts the provider's terms. Accepting doesn't switch anything on.
- 02Add the publisher-level integrationThe script that exchanges user information for an ID. Fusion can deploy it for you.
- 03Add the ad stack integrationThis passes the ID into the bid stream. You can remove either part at any time.
- 04Pass the user informationSend the email or phone number to our tag with the JS API on every page where you have it, such as when a reader is logged in or signs up to a newsletter.
Personal information is passed client-side and never reaches Content Ignite's servers. Some providers require changes to your privacy policy: their terms in Policy Centre say so.
Need a hand with privacy-compliance?
Ensuring privacy control, consumer trust and revenue maximisation
Privacy Audits
Conduct periodic privacy audits through the CI Healthcheck report, providing key insights and recommendations on your privacy strategy
About the HealthcheckCMP Integrations
Recommendations on best practice right through to delivery of your CMP through to page and A/B split-testing on potential new partners
Supported CMPsConsultancy
Access to our Privacy experts from the outset to provide constant help to navigate this complex and changing landscape
Talk to usUK privacy rules for publishers
Consent, CMPs and personal data: questions, answered
How does Content Ignite handle GDPR consent?
What is Content Ignite's IAB TCF vendor ID?
Does Content Ignite support GPP?
Does Content Ignite provide a CMP?
Why must the CMP stub be directly in the page head?
What happens to ad revenue when a visitor doesn't consent?
Can I use Google's CMP with Content Ignite?
Does Content Ignite store personal data?
How do UID2, EUID and other ID solutions work with Fusion?
Does Content Ignite honour CCPA opt-outs and Global Privacy Control?
Is your consent set-up costing you revenue?
Get a free Revenue Healthcheck: CMP errors, ads.txt, tags and Core Web Vitals scored and benchmarked against similar publishers.