Free Cookie Consent Banner Generator

Integrate optional scripts before publishing

Paste the generated snippet once per page, before optional integrations. Remove the original executable tags for optional scripts. Change them to inert markup, using one of your enabled categories:

<script type="text/plain" data-fpt-category="analytics" data-src="https://your-analytics-provider.example/script.js"></script>

<script type="text/plain" data-fpt-category="analytics">
  // Your provider-specific initialization code goes here.
</script>

The example URL is a placeholder. Replace it with your real provider URL. Add the external loader before initialization; marked classic scripts run in document order, with each external script’s load event awaited before the next script is inserted. A failed external load stops later scripts in that category and emits fpt:consenterror. Your provider may still require its own ready callback. Module scripts and complex tag managers require custom integration.

Only marked scripts are gated. The code does not intercept normal script tags, tracking pixels, iframe embeds, plugins, server requests or cookies set elsewhere. Keep those disabled until the relevant category is granted. A Content Security Policy may require nonces or separate approved script/style files; adapt the snippet to your policy.

Read choices and react to changes

window.FPTConsent.getConsent(); // necessary, enabled categories, decided
window.FPTConsent.open();       // reopen category settings
window.FPTConsent.withdraw();   // reject optional categories

document.addEventListener("fpt:consentchange", function (event) {
  const choices = event.detail;
  // Start/stop your own integrations according to these choices.
});

The API is available after the snippet runs. Marked scripts added later are also observed. Choices are shared across tabs on the same origin. A change of version, category list or an expired choice disables optional scripts on the next load. Revoking a granted category reloads the page; arrange form-save flows accordingly.

Check your actual integration

In a clean browser profile, inspect requests and storage before making a choice. Reject optional categories and confirm that their resources remain blocked. Enable each category separately, reload to check persistence, then withdraw and confirm the resources stay blocked after the reload. Review retention, disclosure and deletion behavior for each provider.

Consent must reflect the actual deployment. For current UK guidance on consent controls, withdrawal and retention, consult the ICO’s practical consent guidance. Other jurisdictions and technologies may require different handling.