Consent
Pixel Tracking does not show a cookie banner. It reads the answer from the banner you use, and loads each tag only once the visitor has allowed that tag’s category. Server events follow the same answer.
Where the answer comes from
Section titled “Where the answer comes from”Tags wait for the first source that answers, in this order:
- Brainrune Cookie Consent (Cookie Consent)
- WP Consent API, for any banner connected to it
- The cookie or script left by ConsentMagic, Cookiebot, CookieYes, Borlabs Cookie or Complianz
A source that is missing is not a refusal; the next one is asked. If the Cookie Consent script is missing from a cached page, the visitor’s choice is still read from its brl_consent cookie. A choice made under an older policy version counts as no choice.
The Consent source panel on the Consent tab shows which source actually answered on your site. The header of every screen also shows a Consent pill: detected or none.
Consent settings
Section titled “Consent settings”On the Consent tab, Consent source panel:
- Consent handling: Wait for consent (default) or Load tags without asking.
- When no source answers: Do not load the tags (default) or Load the tags.
Category per platform
Section titled “Category per platform”Each platform needs one consent category. Set it in the Consent panel of the platform card, or in the row on the Dashboard. The Category map panel on the Consent tab lists all of them, read only, with a link to each card.
| Platform | Default category |
|---|---|
| GA4, Microsoft Clarity, Umami | Analytics |
| Meta, TikTok, Google Ads, Tag Manager, Microsoft Ads, Pinterest, Snapchat, Reddit, LinkedIn, OpenAI Ads | Marketing |
The list of categories comes from your consent banner. With Cookie Consent it is Necessary, Analytics, Marketing, and Preferences and External media when those are switched on.
Umami is the exception: it sets no cookies, so it loads without waiting unless you turn on Wait for consent anyway on its card.
When the visitor changes their mind
Section titled “When the visitor changes their mind”Tags that are waiting start as soon as consent arrives, without a page reload. When the visitor withdraws consent, Pixel Tracking tells the pixels already on the page: Meta gets a consent revoke, TikTok stops using cookies, and Clarity gets its consent update.
Server events
Section titled “Server events”A server event leaves after the visitor has left, so it cannot read their cookie. The Server-side panel on the Consent tab has two switches, both on by default:
- Apply the consent stored on the order: the decision recorded at checkout is the one that applies when the event is sent. A refused event shows as No consent on the Server tab.
- Advanced matching: allows first-party identifiers, such as a hashed email, in server payloads.
The attribution cookie also waits for marketing consent.
Google Consent Mode v2
Section titled “Google Consent Mode v2”Google Consent Mode v2 is set by your consent banner, not by Pixel Tracking. Cookie Consent prints the Consent Mode default before any Google tag loads, then sends an update with the visitor’s choice. See Google Consent Mode v2.
Pixel Tracking adds its own gate on top: the GA4, Google Ads and Tag Manager tags it loads also wait for their category, like every other tag.
With Cookie Consent
Section titled “With Cookie Consent”Install Cookie Consent next to Pixel Tracking and there is nothing to connect. Pixel Tracking reads the answer on its own: pixels wait for a yes, Google Consent Mode follows, and server events respect the same choice. Cookie Consent’s Dashboard also checks that Pixel Tracking is set to wait.