[ MAGENTO / ADOBE COMMERCE ]
Cache-safe by design — the script tag never needs to bust FPC.
Magento's Full Page Cache is the thing that breaks most third-party embeds. CookieJar's tag is a static, visitor-agnostic include — it caches fine, because all the per-visitor logic (region, consent state) runs client-side after the page loads.
- [ Install ]
- 1 layout edit
- [ Full Page Cache ]
- Cache-safe
- [ Script size ]
- < 8KB
- [ Setup time ]
- ~10 min
Install on Magento / Adobe Commerce
Add via Design Configuration
Content → Design → Configuration → edit your storefront's scope → Footer/HTML Head — paste the tag into Miscellaneous HTML for a no-deploy install.
Or ship it as a small module
If your team prefers deploys over admin config, a minimal module adding the tag to the default layout XML works the same way and is easier to track in version control.
Flush and verify
Flush Magento cache (System → Cache Management) after adding it, then verify the banner renders on both cached and freshly-generated page loads.
Why it doesn't fight the cache
Full Page Cache stores the rendered HTML, including the script tag itself — that part is fine to cache because it's identical for every visitor. Region detection and consent state are resolved by the script in the browser, not baked into the server-rendered HTML, so there's nothing here that FPC or a Varnish layer needs to treat specially.
Adobe Commerce Cloud / Fastly
If you're on Adobe Commerce Cloud, Fastly sits in front of Magento with its own CSP and caching rules layered on top of Magento's own. The same cache-safety applies, but double-check your Fastly VCL doesn't strip unrecognized script domains if you run a locked-down CSP there.
[ FAQ ]
Magento / Adobe Commerce questions
Ready to add it to your Magento / Adobe Commerce site?
Free tier covers 5,000 pageviews on 1 domain — no credit card required.