Follow a safe demonstration from domain registration to visitor consent. This simulation does not publish a real deployment or use your plan allowance.
4 guided stages1 stable script tag0 production changes
STAGE 1
Configure the deployment
CFT binds the installation to one hostname and stores its managed settings.
Adjust the values, then create the simulated deployment.
STAGE 2
Install the site-specific script
Place the generated tag before the closing </body> tag on every page.
Managed loader
Complete all three installation checks to continue.
STAGE 3
Test the visitor experience
Try each decision and watch which optional services are allowed to run.
https://shop.example.com
Northstar GoodsShop Stories Account
NEW SEASON
Useful things, made thoughtfully.
Your privacy choices
We use essential technologies to operate this site. With your permission, we also use optional technologies. Read our policy.
Powered by CFT
Cookie preferences
Essential technologies are always active.
EssentialAlways active
AnalyticsBlocked
MarketingBlocked
PreferencesBlocked
Consent eventWaiting for visitor choice...
STAGE 4
Manage the live deployment
The installation tag stays unchanged while managed configuration updates propagate.
shop.example.comActive deployment
What updates?
Policy URL, color, categories, and active status are read by the managed loader.
What stays fixed?
The site ID and installed script tag do not change.
What remains local?
Visitor choices stay in first-party browser storage in this product stage.
This is a simulation. Publish does not change a production website.Open your CFT account
HOW THE REQUEST FLOWS
One installation, managed configuration
1. Your websiteLoads its unique site ID
→
2. CFT loaderChecks the registered hostname
→
3. Consent bannerCollects a visitor decision
→
4. Optional scriptsRun only when permitted
Important: CFT assists with technical consent controls. Site owners are responsible for identifying vendors, categorizing scripts, maintaining policy content, and determining their legal obligations.