Cookie Consent & CMP Integration

Flint works with your existing Consent Management Platform (CMP) so cookie consent is handled consistently across your main site and Flint-hosted pages.

When you publish Flint pages via reverse proxy (subfolder hosting), your pages live under your main domain — for example, yoursite.com/lp/campaign. Because they share the same domain as your primary site:

• •Consent persists automatically. A visitor who accepts cookies on your homepage carries that consent to Flint pages. No duplicate banners.
• •Your CMP stays in control. Flint does not inject its own consent layer. Your CMP governs all tracking across your CMS-hosted pages and Flint pages alike.

1. 1.Open the Flint editor and click Settings (top-left).
2. 2.Select Site Settings, then scroll to Custom Code > Head.
3. 3.Paste your CMP script tag — the same snippet you use on your main site. Common CMPs: Cookiebot, OneTrust, Didomi, CookieYes.
4. 4.Click Save, then Publish.

Because your main site and Flint pages share the same root domain under reverse proxy, the CMP's consent cookie (typically first-party) is readable across all pages. No additional configuration needed.

If you host Flint pages on a subdomain (for example, pages.yoursite.com), consent cookies set on yoursite.com are still accessible as long as your CMP sets cookies on the root domain (.yoursite.com). Check your CMP's domain settings to confirm. See Hosting Options for a full comparison of subfolder vs. subdomain setups.

• •Flint does not set any tracking cookies on your visitors' browsers.
• •All analytics and tracking scripts you add via Custom Code or Analytics & Tag Manager are subject to your CMP's consent rules, the same as on your main site.
• •If you use Google Tag Manager, configure it to fire tags only after consent, the same way you do on your primary site.