Adding the snippet
Webflow exposes site-wide custom code on eligible workspace or site plans. Paste the snippet into the head section so it is present early, then publish: custom code is evaluated on the published site rather than solely in the Designer preview. Plan names and dashboard locations change, so this instruction was verified against Webflow documentation on 19 September 2026 and should be rechecked before publication.
Site-wide head
<script
src="https://strongprivacy.com/embed/v1.js"
data-site-id="YOUR_SITE_ID"
data-api-base="https://strongprivacy.com"
data-privacy-url="/privacy"
data-platform="custom"
defer
></script>Custom code requires an eligible current plan. If the site-wide head field is unavailable, check Webflow’s current plan documentation rather than assuming an old plan name still applies.
Webflow consent APIs and CMP integrations
Pick one consent system
Webflow does not currently provide a complete native consent-management platform for every site. It provides consent-related APIs and supports Marketplace CMP integrations. If an integration already presents a banner or controls Webflow tracking, map the handoff and choose one system of record before adding another runtime.
Embeds are the usual finding
Webflow sites lean on embeds: a YouTube video, Typeform, map or chat widget. Each can initiate third-party requests. Use a locally hosted placeholder and explain what activation loads; a click can be a narrowly scoped request for that embed where applicable, but is not blanket consent to unrelated processing.
Common questions
Why is my snippet not appearing on the site?
Custom code takes effect on publish rather than in the designer or on a staging preview. Publish, then check the rendered page source.
Can I gate Webflow’s own analytics?
Use Webflow’s current tracking-consent controls or a supported CMP integration, then verify the network outcome in each state. A third-party banner rendering on the page does not automatically control Webflow’s own tracking.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- Webflow Browser API: consent management
Vendor documentation
Checked
- Webflow: custom code in head and body tags
Vendor documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.