Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cookiechimp.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Add a GDPR, ePrivacy and CCPA compliant cookie consent banner to your Framer site. CookieChimp installs as a single line of custom code in your Framer project settings — no plugins, no rebuild required.
1

Copy your CookieChimp snippet

Log in to your CookieChimp dashboard and copy your website's JS snippet:
<script src="https://cookiechimp.com/widget/abc123.js"></script>
Replace abc123 with your website's unique CookieChimp ID.
2

Add the snippet to your Framer project

  1. Open your project in the Framer editor.
  2. Click the Settings icon (cog) in the top-left, then choose Site Settings.
  3. Open the General tab and scroll down to Custom Code.
  4. Paste the CookieChimp snippet into the Start of <head> tag field. Pasting it here (rather than “End of <body>”) ensures the script runs before any tracking pixels load.
  5. Click Save, then Publish your site from the top-right of the editor.
The CookieChimp script needs to be the first script in the <head> section so it can block other scripts before they run and set cookies without consent. If other scripts are added before, they may set cookies and other storage items before consent is granted.
3

Block scripts & cookies

To stay compliant with GDPR and other privacy regulations, you need to actively block non-essential scripts and cookies until the user gives consent. See our Scripts Management Section for full details.
Framer ships built-in integrations for Google Analytics, Google Tag Manager, Meta Pixel and others, which inject their own scripts. If you’ve enabled these in Site Settings → Analytics & SEO, prefer routing them through CookieChimp instead — either disable Framer’s built-in version and re-add via Custom Code with type="text/plain" and data-category, or route them through GTM and use our Google Tag Manager guide.
4

Allow users to update their preferences

CookieChimp provides a floating privacy icon (Privacy Trigger) that lets users manage cookie preferences at any time. Enable it in the banner settings.To open the preferences modal from a custom button or link, add the data attribute data-cc="show-preferencesModal":
<button type="button" data-cc="show-preferencesModal">
  Manage cookie preferences
</button>
In Framer, you can wire any button to open the preferences modal by adding an Embed layer with HTML, or by using the Link field with the URL #cc-preferences if you’ve configured that as a trigger. For most cases, enabling CookieChimp’s built-in floating Privacy Trigger is enough.

​
Troubleshooting

  • Banner doesn’t appear on the published site — make sure your published Framer domain (e.g. your-site.framer.website and any custom domain) is allowed in Account Settings → Additional Domains in your CookieChimp dashboard.
  • Banner appears in preview but not on the live site — Framer requires you to Publish after any change to Site Settings. The editor preview uses a separate environment.
  • Snippet field is missing in Site Settings — Custom Code is available on Framer’s paid plans. The free plan does not allow head injection.
  • Enable Debug mode from the CookieChimp dashboard and check the browser JS console for errors.
If you encounter any issues or need further assistance, please reach out to us via our chat.
Yes. CookieChimp runs in the <head> of every page Framer renders, including CMS-driven blog posts, collection pages and dynamic routes. No per-page setup is needed.
No. The CookieChimp script is under 30KB gzipped, loads asynchronously and is served from a global CDN. It doesn't block rendering and won't meaningfully affect your Lighthouse scores.
CookieChimp has a free tier suitable for low-traffic sites, with paid plans for higher traffic and additional features. See pricing.