Privacy & Compliance

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 it works

How consent reaches your ads

  1. 01
    Stub first
    A 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.
  2. 02
    Your CMP asks
    Your TCF- or GPP-compatible CMP collects the visitor's choice. Content Ignite and our demand partners must be enabled in its vendor list.
  3. 03
    Our tag reads it
    With consent, ads can be personalised. Without it, or with no CMP, ads are non-personalised. The tag also honours Global Privacy Control (GPC) signals.
  4. 04
    Diagnostics checks it
    Fusion'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.
Building Blocks for Privacy by Design

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.

Content Ignite's four privacy pillars, the principle behind each and what it means in practice
PillarPrincipleIn practice
01. MinimisationLimited. Contextual. Pseudonymous.We don't store personally identifiable information. Contextual audiences are built from page content, with zero PII.
02. ObfuscationHashing. Truncation. Encryption.To estimate unique users we store a hash of identifiers, discarding over 70% of it so it can't be reversed.
03. LimitationTime-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. ConsentRegistered IAB TCF VendorVendor ID 656. The tag reads TCF and GPP consent, and only sets a publisher-provided ID (PPID) when the visitor has given consent.
Who does what

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.

Privacy and consent tasks, what the publisher does and what Content Ignite does
TaskYou, the publisherContent Ignite
Choose a CMPPick 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 pagePut 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 listKeep 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 lawsUse 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 solutionsAccept 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 chainHost 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.

ID solutions and Policy Centre

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.

  1. 01
    Accept the terms
    In Policy Centre, someone at your organisation reads and accepts the provider's terms. Accepting doesn't switch anything on.
  2. 02
    Add the publisher-level integration
    The script that exchanges user information for an ID. Fusion can deploy it for you.
  3. 03
    Add the ad stack integration
    This passes the ID into the bid stream. You can remove either part at any time.
  4. 04
    Pass the user information
    Send 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.
ID and signal integrations in Fusion

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.

FAQ

Consent, CMPs and personal data: questions, answered

How does Content Ignite handle GDPR consent?
Our tag reads the visitor's consent from your CMP through the IAB Transparency and Consent Framework (TCF). With consent, ads can be personalised. If consent was not given or could not be obtained, ads are non-personalised. Content Ignite is a registered TCF vendor and complies with the framework's Specifications and Policies. See our privacy policy.
What is Content Ignite's IAB TCF vendor ID?
656. Check that Content Ignite, and the demand partners we work with, are enabled in your CMP's vendor list. Most CMPs enable all vendors by default, but if you trim the list and leave us out, our consent reads as missing and ads default to non-personalised.
Does Content Ignite support GPP?
Yes. The IAB's Global Privacy Platform (GPP) covers several regional frameworks, including TCF for Europe and for Canada, and California's privacy rules. If you serve those regions, choose a CMP listed as GPP-compatible. When a GPP CMP is on the page, Fusion turns on Prebid's GPP consent management automatically. Our CMP guide includes a GPP stub.
Does Content Ignite provide a CMP?
No. Choosing and implementing a CMP is the publisher's responsibility, and we think you should control your users' privacy, so we don't ship a default one. We can advise, and we can deploy supported CMPs for you through Fusion, which guarantees they load before our tag. See ad-tech vendors.
Why must the CMP stub be directly in the page head?
The stub tells our tag a CMP is coming, so it waits for consent. Scripts in the head don't load in a fixed order, so without a stub the tag sometimes loads first, finds no CMP and serves non-personalised ads. A stub in an external file has the same problem. Put the code inline, before the CMP and our tag. Diagnostics shows whether it is found.
What happens to ad revenue when a visitor doesn't consent?
Ads are still shown, but as non-personalised ads, which usually earn less. Set-up problems that make consent read as missing include a missing stub, a vendor list without Content Ignite, and caching plugins that delay the CMP. Diagnostics tracks the consent rate our tag sees.
Can I use Google's CMP with Content Ignite?
In our experience it doesn't work well. Google's CMP is designed for direct use with Google Publisher Tag. Publishers who used it on its own with a stub found it failed to work correctly. Choose a TCF- or GPP-compatible CMP instead.
Does Content Ignite store personal data?
We don't store personally identifiable information. The tag collects anonymised logs, stored for 5 days and processed into daily summary reports. We keep a hash of identifiers for 5 days to estimate unique users, with over 70% of it discarded so it can't be reversed. See sections 4 and 7 of the privacy policy.
How do UID2, EUID and other ID solutions work with Fusion?
You pass an email address or phone number to our tag through the JS API. The tag passes it, client-side, only to ID providers you have approved in Policy Centre, and only after consent through your CMP. It never reaches Content Ignite's servers. We recommend an experiment when you first switch an ID on, to measure the uplift. See the Policy Centre docs.
Does Content Ignite honour CCPA opt-outs and Global Privacy Control?
Yes. Anyone can opt out of personalised ads from Content Ignite on our responsibility page, and the tag reads and honours Global Privacy Control (GPC) signals. Our high-impact ads also carry an info button that explains the ad and how to opt out.

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.