Framer makes it easy to publish a good-looking site quickly, and easy to add analytics to it. What it does not do on its own is hold that analytics back until a visitor has agreed. When we asked Framer's AI to add Google Analytics to a test site, it could not do it itself and pointed us to the site settings, where the tag would load for every visitor.
This guide adds a consent banner to a Framer site with one script, and moves your tracking behind it.
Step 1: Add your Framer site to Consentify
Publish the site so you have its address, then create a free Consentify account and add that address as a domain. The script only loads on domains you have added, so add your custom domain as well if you use one.
Step 2: Add the script in Settings, Code
In Framer, open Settings, go to Code and click Add script. Fill in the dialog like this:
- Name: Consentify, or anything you will recognise.
- Placement: Start of
<head>. The default is End of<body>, which is too late: by then other scripts may already have run. - Page: All.
- Run: Once. Framer moves between pages without a full reload, so the script stays loaded. Running it on every page visit would start it again on each navigation.
- Code: your script tag from the Consentify dashboard.
<script async src="https://www.consentify.app/api/gateway?token=YOUR_TOKEN"></script>Framer's help centre has more on custom code. Publish the site when you are done.
Step 3: Move your tracking into Consentify
Remove any Google Analytics ID, Google Tag Manager container or pixel you have added to Framer's own settings or as separate custom code. Then add the same IDs under Integrations in the Consentify dashboard. Consentify loads each one only after the visitor has accepted that category, and sends the Google Consent Mode v2 signals for you.
This step is the one that makes the banner mean something. A tag that stays in Framer's settings keeps loading for every visitor, whatever they answer.
What about Framer's own cookie banner?
Framer has a cookie banner component on its paid plans. It is built around Google Tag Manager: you connect a GTM container, and the visitor's choices are passed on as Consent Mode signals. That works well if every tool you use lives in GTM and respects Consent Mode. Consentify is the simpler route when you want each tool held back until consent without setting up triggers in Tag Manager, a cookie declaration that stays current, and a record of every consent decision.
Step 4: Check that it works
Open the published site in a private window. The banner should appear, and nothing should be tracking yet. Move between a couple of pages and check that the banner does not come back after you have chosen. Then run the address through the free GDPR scan, which lists everything that starts before consent.
Agencies that build client sites in Framer can manage all of them from one Consentify dashboard. Our website launch checklist covers the rest of what to check before a client site goes live.