GDPR, GPC & Do Not Track aware
PixelFlow reads your cookie banner and honours privacy signals, so your tracking follows the choices your visitors make. Whether your site complies with the law is still your responsibility.
Free trial. No card, no tag manager.
Respects your visitor’s cookie choice, with no work on your side
PixelFlow does not show its own cookie banner. It reads the choice from the banner you already use, so tracking runs when a visitor accepts and stays off when they decline or their browser sends a do-not-track signal. If they ignore the banner, local law decides what happens next. It is built into the script and on by default.
It reads the choice from the banner you already use, and all major banners are supported. If a visitor ignores the banner, local law decides: in ask-first countries PixelFlow holds the events in memory and only sends them if the visitor accepts, and everywhere else it keeps tracking until the visitor explicitly declines. If your site has no banner and no consent setup at all, nothing changes. It is enabled by default and can be switched off per site with the Consent mode switch in the dashboard.
We use cookies
Tracking only starts after you choose.
Decline
Accept
Pixel off until opt-in
On after consent
Accept: tracks as normal
Browser pixel and Conversions API both run, with the identifiers Meta needs.
Decline or do-not-track: stays off
No cookie is set, no events are sent, and PixelFlow’s identifiers for that visitor are deleted.
No banner at all: nothing changes
PixelFlow waits a couple of seconds, sees no consent setup, and tracks under your normal triggers.
What PixelFlow does, and what stays with you
PixelFlow handles
Reads the accept or decline from the banner you already use
Holds events in ask-first regions until the visitor accepts, and deletes them if no answer comes
Honours Global Privacy Control and do-not-track signals
Remembers each visitor’s choice, including changes of mind
You stay responsible for
Choosing and configuring a banner that asks for marketing cookies
Deciding which regions need consent for your business
A privacy policy that names Meta and explains what you track
Accepting Meta’s data terms and testing your setup after changes
Works with the banner you already have
Reads the choice from
CookieYes
Cookiebot
Complianz
OneTrust
Squarespace
Google Consent Mode v2
Iubenda · Termly · Usercentrics · Osano · Cookie Script via Consent Mode
Nothing to install inside the banner. Run it as you normally would and PixelFlow reads the decision, including later changes of mind.
CookieYes
Reads the visitor’s choice, including later changes.
Cookiebot
Reads the visitor’s choice and accept or decline clicks.
Complianz
Reads the marketing-cookies choice. Works on free plans too.
OneTrust and Squarespace
OneTrust cookie-category choices, including later changes. Squarespace’s built-in banner on Squarespace sites.
Google Consent Mode v2 banners
Iubenda, Termly, Usercentrics, Osano, Cookie Script and more, through the standard Google consent signal. Check the banner has its Consent Mode option enabled, or verify with Google Tag Assistant. Visitors must be able to accept marketing cookies, not only analytics.
<button onclick=
window.pixelFlow.consent(’granted’)>
Accept
</button>
// visitor declined or withdrew
window.pixelFlow.consent(’denied’)
One line for a custom banner
Built your own banner, or use one PixelFlow does not recognise? Call window.pixelFlow.consent with granted or denied from your banner’s buttons, at the moment the visitor decides and again if they change their mind. PixelFlow remembers the choice for about six months, so you do not need to call it on every page.
Ask first, or track until told to stop
Anna
Germany · ask first
Held
sent on accept, deleted if no answer
Tom
Texas · track until declined
Tracking
stops from the moment he declines
While the banner is still unanswered, the visitor’s location decides what happens. You do not configure this, and it follows the visitor, not where your company is registered.
Ask-first regions
The EU, the EEA (Iceland, Liechtenstein, Norway), the UK, Switzerland, Brazil, South Korea, Japan and Quebec. PixelFlow waits for an accept before tracking.
Track-until-declined regions
The United States and most other countries, and Canada outside Quebec. Tracking can start before the banner is answered, and a later decline stops new events from that moment.
What happens to held events
In ask-first regions events are held in memory and sent with their original times if the visitor accepts. If the answer never comes they are deleted and never sent.
Unknown location
Treated as ask-first, the more cautious default.
How location is detected
From edge and CDN location signals when available, otherwise an IP lookup on PixelFlow’s own servers using a local database. The IP address is never sent to a third party.
These are PixelFlow’s defaults, based on how each region is commonly treated. They are not legal advice, laws change, and it is up to you to confirm they suit your business.
GPC wins over everything, even Accept all
Some browsers and extensions, Brave for example, send Global Privacy Control, a built-in do-not-sell-or-share signal, with every visit. With Consent mode enabled PixelFlow honours it everywhere in the world, and it overrides an Accept click on your banner. Tracking stays off for that visit.
Sec-GPC: 1
Brave
Banner: Accept all
overridden
Tracking
Off for this visit
Honoured worldwide
Not only where GPC is law. If the browser sends it, PixelFlow stays off.
Overrides an accept
An Accept all click does not switch tracking back on for a GPC browser.
US sites, expect this
Some visitors will stay untracked after accepting the banner. That is GPC working, not a setup problem.
One per-site switch, on by default
Everything here is controlled by a single setting called Consent mode, enabled by default for every site. Enabled means PixelFlow honours cookie banners, Google Consent Mode, your consent calls and GPC. Disabled means it ignores all of them, including GPC, and sends events normally; bot blocking still applies. Turning it off is your decision, so only do that where you have confirmed you are allowed to track without consent. You will find it on the Overview card, the Sites table and the Edit site screen. When testing, accept your own banner first, including marketing cookies, or the event you are checking may never fire.
Consent mode
Enabled · default for every site
Cookie banners
Google Consent Mode
window.pixelFlow.consent()
Global Privacy Control
_pf_consent
183 days
decision
accepted
source
cookiebot
time
2026-09-04 10:02
version
1
visitor id
none
Nothing until they decide
While PixelFlow is waiting for a decision it stores nothing on the device. After a real decision it sets one first-party cookie, _pf_consent, holding the decision, which tool it came from, when it was made and a format version, for about six months. It contains no visitor ID and cannot identify anyone. PixelFlow’s tracking identifiers are only created once tracking is allowed. The WordPress plugin follows the same rules through the WP Consent API, and server-side WooCommerce events such as Purchase follow the same accept or decline decision as browser events.
FAQ
Everything you need to know about consent, GDPR and privacy signals.
Does using PixelFlow make my site GDPR compliant?
No tool can. Consent mode makes your tracking respect the choices your visitors make and the signals their browsers send. You remain the data controller and are responsible for your banner, your privacy policy, your lawful basis for tracking and staying current with the law where you operate.
Does PixelFlow show a cookie banner?
No. PixelFlow only reads the choice from your existing banner or from your window.pixelFlow.consent call. Choosing and running a banner stays up to you.
Will I see fewer events with Consent mode enabled?
In ask-first regions, possibly: visitors who decline or never answer are not tracked, which is their choice working as intended. In track-until-declined regions like most US traffic the difference is usually small: only explicit declines and GPC browsers stop tracking.
What happens when a visitor changes their mind?
The newest choice applies from that moment. A decline after an accept stops new events and deletes PixelFlow’s identifiers; an accept after a decline starts tracking fresh. Events already sent are not deleted automatically.
I already load PixelFlow only after consent in GTM, Webflow or Framer. Do I still need that?
It keeps working and you can keep it, but it is no longer required because PixelFlow now waits on its own. New sites can install PixelFlow normally next to a supported banner.
What does PixelFlow store on the visitor’s device?
While waiting for a decision, nothing. After a real decision, one first-party cookie, _pf_consent, holding the decision, its source, its time and a format version, for about six months. It contains no visitor ID.
Smarter, server-side tracking
Start sending accurate conversions today - no tag manager, no code, no developer required.
Compatible with
