cookie consent for Nuxt
@cookiecrumbs/nuxt unshifts the tag into app.head.script with critical priority, ahead of the Nuxt entry chunk, and auto-imports a useConsent() composable.
the rule
A Nuxt app with a GA or pixel plugin runs it on the client entry. Nothing asks first, and nothing can take it back.
The rule is the same everywhere in the EU and the UK: nothing beyond what is strictly necessary may be stored on or read from a visitor’s device before they have agreed. That is Article 5(3) of the ePrivacy Directive, and the agreement has to meet the GDPR’s definition of consent: freely given, specific, informed and unambiguous, with a refusal that is as easy as the acceptance. The UK keeps the same rule in PECR, with narrow exemptions for low-risk statistics since 5 February 2026. California and the other US state laws work the other way round: no opt-in, but an opt-out link and support for the Global Privacy Control signal.
Three things follow for a website. Analytics, advertising and social scripts have to wait for a choice. The choice has to be recorded in a way you can show later, because Article 7(1) puts the burden of proof on you. And withdrawing has to be as easy as agreeing, which means a control that reopens the banner on every page. A banner that shows two buttons and loads Google Analytics anyway fails the first test, and that is the failure regulators have been fining, from the CNIL’s decisions against Google and SHEIN to the Dutch and Belgian authorities’ sweeps.
how it works
Nuxt manages the document head for you, which is exactly where a consent runtime has to sit. The module puts the tag into app.head.script with tagPriority: "critical", so it is rendered before the Nuxt entry chunk on every page, server-rendered or static. No layout edits, no per-page head calls.
Client plugins are the usual source of early trackers in Nuxt: a gtag plugin, a Pixel plugin, a third-party module that injects its own script. The useConsent() composable gives every one of them isGranted(category) and a way to subscribe to changes, so a plugin can wait and initialise the moment consent arrives. Third-party Nuxt modules that inject scripts get a category on their tag, or their host is neutralised by the block map from the scan.
Three components come with the module: ConsentGate for subtrees, CookieDeclaration for the privacy page, and ManageCookiesLink for the footer. Server routes and middleware can read the consent cookie through the same helpers, so a page can render a placeholder instead of an embed before hydration.
set-up
Five steps. The CLI does most of them, and every one is also a click in the dashboard.
Detects Nuxt, links the site, writes the config.
npx cookiecrumbs login
npx cookiecrumbs initThe site key and environment go in nuxt.config.ts.
npm i @cookiecrumbs/nuxt
// nuxt.config.ts
export default defineNuxtConfig({
modules: ['@cookiecrumbs/nuxt'],
cookiecrumbs: { site: 'pk_live_…', env: 'production' },
});useConsent() exposes status, consent, regime, country, language, version and the accept, reject, open and withdraw actions.
const { isGranted, open } = useConsent();
<ConsentGate category="analytics">
<AnalyticsWidget />
</ConsentGate>A client plugin initialises its tracker only when the category is granted, and again if consent changes later.
// plugins/pixel.client.ts
export default defineNuxtPlugin(() => {
const { isGranted, onChange } = useConsent();
const start = () => { if (isGranted('marketing')) initPixel(); };
start(); onChange(start);
});Scan, sort once per vendor, publish.
npx cookiecrumbs scan --wait
npx cookiecrumbs push --env productionNuxt shops running Google Ads through a gtag plugin get the Consent Mode defaults from the runtime before the plugin loads, so the conversion tag respects the choice without a rewrite.
Google Consent Mode v2 is the signalling layer between the banner and Google’s tags. Before any tag runs, seven signals (ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage) are set to denied for visitors in the EEA, the UK and Switzerland. The moment someone chooses, the runtime updates them and Google’s tags adjust. Since 15 June 2026, Google uses ad_storage as the controlling signal for Ads data, so getting the default right matters more than it used to.
CookieCrumbs sets the defaults synchronously, ahead of any tag manager, updates them on every decision, and ships a Google Tag Manager template so the consent triggers exist without hand-written listeners. In advanced mode, Google’s cookieless pings keep modelled conversions working for the visitors who said no. What it does not do is pretend to be a Google-certified CMP: for AdSense, Ad Manager or AdMob in the EEA you still need one with IAB TCF, and CookieCrumbs is not that today.
watch out
Each one shows up in the first scan as a tracker that fired before consent.
before you ship
Eight lines. The dashboard ticks the last two from real data.
type="text/plain" with a category, or the host is in the block map from the scan.what you get
Two domains, 100 subpages scanned a month per domain, every regulation, the CLI, the SDKs and the MCP server.
Every page, in each consent state, in a real browser. Cookies, pixels, iframes and storage keys, with the page and script that set them. Re-scanned on a schedule.
The cookie declaration writes itself from the result.
Tags stay inert until their category is granted. Reject all is as visible as Accept all. Seven layouts, 25 languages, Consent Mode v2, and the right rule per region.
21 kB, one file, no third-party requests of its own.
Each choice is stored with a timestamp, the banner version and a hash of the texts shown, chained to the record before it. Exports are signed. Hosted in Frankfurt.
Article 7(1), on the free plan.
free check
The homepage HTML, matched against the tracker database. No account, nothing stored. The full scan in the dashboard does the same for every page, in a real browser.
questions
next step
Add the site, run npx cookiecrumbs init in your Nuxt repo, and the consent log starts recording in the EU.