Connect CookiePilot where your tags actually run
Use these guides to install CookiePilot on websites, stores and Google Tag Manager setups. Each page separates what is built into the product from the configuration you still need to check in your CMS, theme or tag container.
Platforms and stores
Start with the place where tags are loaded: CMS, store theme or GTM. Then set Consent Mode defaults to denied and test the public journey, especially product, cart, checkout and lead forms.
Google Tag Manager
Install CookiePilot as a Consent Initialization tag, with the Consent Mode stub placed before the GTM container.
Open guide
WordPress
The WordPress plugin connects the domain, edits the banner and enables Consent Mode without manual theme edits.
Open guide
WooCommerce
WooCommerce works with CookiePilot when cart cookies stay necessary and WooCommerce order attribution does not set sbjs cookies before consent.
Open guide
Vendor presets and tag behaviour
Vendor presets explain consent categories, common requests and cookies. They help teams configure analytics and marketing tags without pretending to replace legal review.
Google Analytics 4
GA4 usually belongs to analytics and should wait for analytics_storage granted, except for cookieless Consent Mode pings.
Open guide
Google Ads
Google Ads needs ad_storage, ad_user_data and ad_personalization to match the visitor's choice.
Open guide
Google Tag Manager
GTM is the deployment layer. CookiePilot publishes consent updates and GTM rules should start vendors after consent.
Open guide
Meta Pixel
Meta Pixel should be treated as marketing and blocked until marketing consent.
Open guide
TikTok Pixel
TikTok Pixel is marketing. It should start only after marketing consent.
Open guide
Hotjar
Hotjar usually belongs to analytics or preferences depending on usage. It should not write _hj cookies before consent.
Open guide
Klaviyo
Klaviyo in ecommerce usually mixes analytics and marketing. Forms and user identification should wait for the right consent.
Open guide