PROVIDER - Danish CMP and consent records

Cookie Information

Cookie Information is a Copenhagen-based consent management platform founded in 2011 that scans a site, groups cookies into four categories, and emits TCF v2.2 and Consent Mode signals for EU traffic sites.

Compliance & Legal Denmark 2026.11.20
3.9pts

Detailed Notes

Pros 5 items

1 script covers the whole site, so consent logic lives in a single place and template changes do not require editing per-page checks
Scan results are grouped into 4 purpose categories (necessary, functional, statistics, marketing) and turned into a cookie inventory you can audit
2 ad signals are emitted together, IAB TCF v2.2 strings for programmatic pipes and Consent Mode states for the Google stack
3 step rollout (automatic scan, human review of categories, banner publish) that most small sites finish within a few working days
Consent records export in 2 structured formats with timestamps and decision evidence, ready to hand to an auditor

Cons 4 items

Chinese interface and Chinese support are limited, so banner copy and policy text for Chinese audiences need independent translation and review
The scanner misses some lazily loaded, dynamically injected, and iframe-level scripts, so the inventory still needs human verification
Consent rate comparison and version analysis sit in the higher tiers, and costs climb quickly as the number of domains grows
Complex trigger logic in a tag manager needs front-end help, and debugging a mis-fire is slow for operations staff alone

Service Overview

Founded in 2011 and headquartered in Copenhagen, Denmark, Cookie Information builds its product and its compliance documentation around the decision order set by GDPR and the ePrivacy Directive. In the Compliance & Legal category it is one of the few consent management platforms that starts from an automatic scan and only then decides what the banner should say.

That order is the inverse of most banner tools. Most tools hand you configurable copy and leave the script inventory to manual upkeep. Cookie Information first crawls the third-party scripts a page actually loads, files each cookie under necessary, functional, statistics, or marketing, and publishes the banner only after a human confirms the categories. The consequence is that the cookie statement on the policy page is no longer a written promise, because any script change surfaces as an item waiting for review.

For sites whose traffic is mostly European, the payoff of that order is an evidence trail. Every choice lands in a timestamped record, and the dashboard can break consent rate down by country, device, and banner version. On the advertising side, IAB TCF v2.2 and Google Consent Mode both receive signals derived from the same consent state, so delivery does not quietly diverge from what the visitor actually allowed.

Key Strengths

  • Scan first, declare second: the crawler exposes every third-party script a page really loads, so nobody has to maintain the inventory from memory and the gap between policy text and live behaviour shows up automatically.
  • Two ad signals from one state: TCF v2.2 covers the EU programmatic path while Consent Mode covers Google conversion and remarketing, both derived from the same record, so the two systems cannot contradict each other.
  • Consent rate is an observable metric: the dashboard splits consent rate by country, device, and banner version, so a copy or layout change can be judged against a baseline instead of intuition.
  • Multilingual banners with regional switching: built-in copy templates load the matching language per visitor region, with opt-in as the EU default and looser defaults where the operator allows it, instead of one banner for the whole world.
  • Exportable audit material: records export in structured form with scope, timestamp, and decision basis, which shortens the handover to legal when a customer or a regulator asks for proof.

Product Ecosystem

Platform capabilities

Scanning, categorisation, banner, and records live in one console. Scans rerun on a schedule and any newly detected third-party script is flagged for confirmation, so the operator either declares it or disables it in the tag manager. The banner supports both category-level and vendor-level grants, which means a two-button accept-and-reject layout as well as a granular checkbox layout. The records side keeps every choice and can filter by date range before export.

Consent statistics are where this product separates from a plain banner widget. The console compares consent rate across banner versions, and combined with traffic structure that comparison tells you whether a rewrite earned more consent or simply met a different audience.

Integrations

Two families of signals leave the platform. IAB TCF vendor consent strings feed programmatic pipes, where ad platforms decide whether personalised bidding is allowed. Consent Mode states feed Google Analytics and Google Ads, and a missing state degrades conversion modelling into coarse estimates rather than measured ones.

On the site side a single injected script handles the work, so a tag manager only needs purpose-based triggers instead of per-tag conditionals. A secondary module maps the scanned inventory onto policy and data processing text, which reduces the common failure of a policy page that has not been updated in months.

Typical scenarios

The most common combination is European traffic plus ad monetisation: a publisher needs to satisfy consent rules and keep revenue, so the reject path has to be decisive while visitors who do want to consent should not face a wall of nested dialogs. The second common pattern is a B2B marketing site that only needs evidence and policy consistency, with almost no advertising integration to configure.

Limitations

  • Chinese interface and support are limited, so Chinese-language sites must translate and legally review banner copy instead of reusing templates
  • The scanner misses some lazily loaded, dynamically injected, and iframe-level scripts, and treating it as fully managed leaves residual risk
  • Consent rate comparison and version analysis sit in higher tiers, and multi-domain portfolios should price the whole estate before committing
  • Complex tag manager triggers need front-end involvement, and a mis-fire is hard for a marketing operator to diagnose alone

Use Cases

  • Content and media sites with EU traffic (★★★★★): consent rate drives ad fill, and the scan plus TCF pairing serves compliance and revenue at once
  • Multilingual B2B sites (★★★★☆): evidence and policy consistency are the whole requirement, and multilingual banners with record export cover it
  • Cross-border e-commerce stores (★★★★☆): value scales with the EU share of visitors, but a large domain estate needs a cost model first
  • Sites operated by mainland China entities (★★★): usable, yet interface and legal text still need localisation and an owner on the operations side
  • Domestic-only sites (★★): there is no equivalent consent regime in mainland China, so a basic privacy policy usually covers the requirement

Pricing

Item Price Notes
Base subscription Monthly, starting in the tens of US dollars Tiered by site count and monthly sessions, see official quote
Enterprise tier Annual, custom quote Adds multi-site management, audit material, and custom integrations
Additional site Purchased per domain Common for multi-brand groups, unit price falls with volume
Implementation and localisation Project quote Chinese copy, policy mapping, and similar work is scoped separately

The ranges above are for estimation only, and the official quote governs. Price the two dimensions together, site count and monthly sessions, because most consent platforms step up a tier once traffic crosses a threshold, and counting domains alone tends to understate the bill.

FAQ

How much page code has to change to install it?

One script in the template head plus purpose bindings in the tag manager is normally enough, with no per-page edits. The real work is reviewing the scan output, deciding which scripts belong to statistics and which to marketing, because that choice defines whether the default banner state is defensible.

What if the scan output does not match the scripts on the page?

The live behaviour wins. A scan result is a finding, and the fix is to declare the script or remove it, never to soften the policy text. For iframes and late injection, check the browser network panel once and add the entries manually if needed.

How much ad revenue is lost after adding a consent banner?

It depends on the banner design and the default state. Reject-by-default with a prominent reject button usually produces a lower consent rate and lower programmatic revenue, while layered copy and vendor-level grants tend to do better. Roll out to a traffic slice first and use the version comparison to size the impact before going full.

How do I cover both EU and US traffic?

Switch the grant model by visitor region. EU visitors get opt-in, while some US states can run opt-out logic, with copy and consent type combinations changing accordingly. Keep the two rule sets out of a single default configuration, or an EU visitor can end up seeing an opt-out banner.

Code Examples

Load analytics and marketing scripts from the consent state

// Check purpose consent before injecting scripts; keys come from the environment, never from the page
document.addEventListener("DOMContentLoaded", function () {
  const cmp = window.CookieInformation;
  if (!cmp) return;

  const statisticsAllowed = cmp.getConsentGivenFor("cookie_cat_statistic");
  const marketingAllowed = cmp.getConsentGivenFor("cookie_cat_marketing");

  if (statisticsAllowed) {
    loadScript("https://analytics.example.com/collect.js", { siteId: "$ENV_ANALYTICS_ID" });
  }
  if (marketingAllowed) {
    loadScript("https://ads.example.com/pixel.js", { advertiserId: "$ENV_ADS_ID" });
  }
});

Keep the check in your own business script rather than trusting a default banner state, otherwise first-visit sessions pull marketing tags without permission.

Verify the CMP and the TCF interface are present in production

#!/usr/bin/env python3
# Spot-check that the CMP script is deployed and the standard TCF interface exists
import re
import sys
import urllib.request

URL = "https://example.com/"
API_KEY = "$ENV_CMP_API_KEY"  # placeholder, read from the environment in real use

req = urllib.request.Request(URL, headers={"User-Agent": "Mozilla/5.0", "X-Api-Key": API_KEY})
html = urllib.request.urlopen(req, timeout=20).read().decode("utf-8", "replace")

checks = {
    "cmp_script": bool(re.search(r"cookieinformation\.com", html, re.I)),
    "tcf_stub": bool(re.search(r"__tcfapi", html)),
}
print(checks)
sys.exit(0 if all(checks.values()) else 1)

__tcfapi is the standard TCF global, and ad platforms cannot read a consent string from a page that never exposes it.

Community & Resources

Visit Cookie Information Website → https://cookieinformation.com/
Visit Website ↗