Cookie Consent does not send a consent signal to any tool by itself: your own callback code sends every Google, Microsoft Clarity, Meta, TikTok, and HubSpot signal. Copy the callback for each tool from its recipe, check the category each signal follows, and hold embedded content until consent with the placeholder pattern.

Google Consent Mode updates come from user_consent_saved with "user_consent_saved_on_page_load": true, and that callback sends denied for each refused category. The Microsoft Clarity, Meta, TikTok, and HubSpot grants come from scripts_specific_loaded with "callbacks_force": true. That callback only grants signals, so a vendor keeps its default for a visitor who declines, and from the next page load for one who withdraws. Copy both callbacks, and the default each vendor takes, from Map Categories to Vendor Consent Signals.

Keep vendor <noscript> fallbacks out of your pages, because they fire for visitors with JavaScript turned off, who never see the consent banner. A platform consent banner next to Cookie Consent stores a second, separate answer, so keep one consent banner where the platform allows it. On Wix, keep the Wix consent banner on when you use Wix Analytics or Marketing Integrations. On BigCommerce, run either its consent banner or Cookie Consent, never both. Keep the BigCommerce consent banner, and remove Cookie Consent, when the trackers you need live in the control panel integrations. Turn off a second consent banner with 2 Cookie Banners Appear on Your Site.

Look up the signal each category grants, then send Google Consent Mode v2 from the callback. The recipes for Microsoft Clarity, the Meta Pixel, the TikTok Pixel, and HubSpot apply the same mapping to the consent command of each vendor.

Page What it covers
Map Categories to Vendor Consent Signals Which signal each category sets, and the 2 callbacks that send them.
Set Up Google Consent Mode v2 Denied defaults as the first script in <head>, the untagged Google tag, the update from the callback, and the check in Tag Assistant.

Hold embedded content until consent

Hold YouTube videos and other iframes, which Cookie Consent does not block by itself, with the placeholder pattern.

Page What it covers
Block Embeds and Iframes Until Consent A placeholder, a tagged script that loads the iframe on consent, and a button that opens the Preferences Center.

Vendor recipes for marketing and analytics tools

Find the category, the markup, and the host to check for each tool this manual covers. For Microsoft Clarity, the Meta Pixel, the TikTok Pixel, and HubSpot, choose between tagging the vendor code and loading it untagged; every Clarity setup sends consentv2 either way.

Page What it covers
Vendor Recipes for Free Cookie Consent 9 recipes for Google Analytics 4, Google Ads, Microsoft Clarity, the LinkedIn Insight Tag, the Meta Pixel, the TikTok Pixel, HubSpot, YouTube, and Calendly.