Block scripts until consent — including your own
Cookie Craft doesn’t just gate the big integrations. It controls the direct pixels it manages, the tags in your GTM container, and the custom scripts and iframes you declare — so nothing measures before the matching consent exists.
What Cookie Craft controls
Three routes, one consent state behind all of them.
Direct integrations
GTM, Meta Pixel and TikTok Pixel get base placement and consent-aware loading — the base code loads only after the matching consent.
GTM-managed tags
Tags in your container respect Consent Mode v2 and their own consent checks, so they fire only when the state allows it.
Custom scripts & iframes
Your own marketing scripts, chat widgets, embeds and iframes are held until you assign them to a category and the visitor consents.
No automatic scanner — and why that’s a control, not a gap
Cookie Craft does not auto-discover and classify your cookies. You declare the categories and assign each script yourself. That is a deliberate model: nothing fires because a scanner guessed a category for it. You decide what is strictly necessary, what is analytics and what is advertising — and Cookie Craft enforces exactly that. If auto-discovery is a hard requirement for you, our comparison says so plainly.
How you set it up
01
Declare your categories
Strictly necessary, analytics, advertising — the standard set, ready to use.
02
Assign scripts
Point each integration, GTM tag or custom script at a category. Anything unassigned stays blocked until you place it.
03
Test every path
Reject, accept, granular choice, return visit and withdraw — check each in the Network tab and your tag debuggers.
You classify it. Cookie Craft enforces it.
Real blocking for every script on your site — not just the four big pixels.