One script in Project Settings. Nothing third party runs until your visitor agrees.
Free scan · no account · results in about a minute
Framer changed custom code from two big text boxes to a list of named scripts, each with its own placement and a choice between running once or on every page visit. That is better, but it means a script can look installed in the editor and never reach a real visitor. Ours goes in the head, set to run once, and you confirm it with a scan rather than by looking at the preview.
Framer sites load fast, and a consent script that arrives late has already lost. Everything third party waits for a real choice.
Custom code applies to the published site, not the preview URL.
Once it is in, scan the site again. The scan reads the page the way a browser does, so it tells you what is still reaching the network before consent rather than what should be.
Start free on FramerOnce. Framer sites are single page applications, so the runtime stays loaded as somebody navigates. Re-running it on every route change would re-check a decision that has not changed.
It is around 10KB compressed from a CDN. It is deliberately a blocking script rather than a deferred one, because a consent blocker that loads late has already lost.
Yes. It lives in Project Settings, not in the canvas, so redesigning pages does not disturb it.
Unlimited pages, unlimited visitors, 24 months of consent records in the EU. Less per site as you add more, which is how agencies actually buy this.
Start your free trial