NexTranslate cookie consent case study: 100% of tags wait for consent
In this cookie consent case study, NexTranslate, a translation startup, had GA4, Google Ads and the Meta Pixel firing before visitors made a choice. We rebuilt the setup on GA4, Google Tag Manager, Cookiebot and Consent Mode v2 to the strictest standard across GDPR, CCPA and the DPDP Act, and a test confirmed that 100% of tags now wait for consent.
| Tag | Before | After |
|---|---|---|
| GA4 | Sent | Waits |
| Google Ads | Sent | Waits |
| Meta Pixel | Sent | Waits |
Built to GDPR, CCPA and the DPDP Act · Offer: Tracking Build
Before vs after: what did the browser send before anyone clicked Accept?
Same page, same moment: the banner is open and nothing has been clicked. On the left, the setup NexTranslate started with; on the right, the rebuild. Both panes reconstruct the test results this case describes, laid out the way a browser's network panel shows them.
/collect|googleads|facebook\.com\/tr/| Tag | Request | Status |
|---|---|---|
| GA4 | google-analytics.com/g/collect | Sent |
| Google Ads | googleads.g.doubleclick.net/pagead/… | Sent |
| Meta Pixel | facebook.com/tr | Sent |
| Other marketing tags | Each vendor's endpoint | Sent |
/collect|googleads|facebook\.com\/tr/| Tag | Request | Status |
|---|---|---|
| GA4 | Nothing sent | Waiting for Accept |
| Google Ads | Nothing sent | Waiting for Accept |
| Meta Pixel | Nothing sent | Waiting for Accept |
| Other marketing tags | Nothing sent | Waiting for Accept |
ReconstructionBuilt from the published test results. The hostnames are each tag's documented collection endpoint; no captured traffic is shown.
Sent
The tag reached its vendor before the visitor chose. On the old setup that happened on every page load.
Waiting for Accept
Tag Manager holds the tag. Nothing goes to the vendor until the visitor accepts the matching category.
The filter
Paste /collect|googleads|facebook\.com\/tr/ into Chrome's network filter. Wrapped in slashes, it is read as a regular expression and catches all three tags at once.
Who is NexTranslate, and what did it ask for?
NexTranslate is a translation services startup based in Delaware, and the one client named in our case studies, with its approval. It came to us while building its website, with a short brief: security first.
NexTranslate
- Business
- Translation services startup, Delaware, United States
- Brief
- Data protection laws handled at the highest level, from day one
- Stack
- GA4, Google Tag Manager, Cookiebot, Consent Mode v2
- Laws
- GDPR, CCPA, DPDP Act
- Offer
- Tracking Build
Tags fired without consent
Every tag on the site loaded as soon as a page opened, whether or not the visitor had agreed to tracking. GA4, Google Ads and the Meta Pixel all sent data before anyone made a choice.
Under opt-in laws such as GDPR and the DPDP Act, a tag that fires before the visitor decides is the first thing a consent review flags.
The fix had to clear the strictest of three laws, with one setup.
“Waftr configured our GA4, GTM and Cookiebot setup to the strictest standard across GDPR, CCPA and the DPDP Act, and no marketing tags fire before consent.”
How do Cookiebot, Consent Mode v2 and Tag Manager hold a tag until consent?
We set up consent before rebuilding Tag Manager, because retrofitting consent onto live tags is where most setups break. Each layer then took one job.
- 01
Cookiebot
Shows the banner and records the visitor's choice.
- 02
Consent Mode v2
Carries that choice to GA4 and Google Ads as
ad_storage,analytics_storage,ad_user_dataandad_personalization. - 03
Google Tag Manager
Holds GA4, Google Ads, the Meta Pixel and other marketing tags until the matching consent is granted.
- 04
The test
Page loaded, banner untouched, network checked. No marketing tag sent anything.
Can one consent standard cover GDPR, CCPA and the DPDP Act?
The three laws set different rules for when tracking may start. Rather than tune the banner law by law, the setup applies the strictest rule of the three: no marketing tag runs until the visitor says yes.
- EU and UK
GDPR
Consent has to be freely given, specific, informed and unambiguous, and the ePrivacy rules ask for it before non-essential cookies are set.
Opt-in - California
CCPA
Visitors can opt out of the sale or sharing of their personal information, which can include what tags send to ad platforms.
Opt-out - India
DPDP Act
Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, before personal data is processed.
Opt-in
If you are checking your own cookie banner
Three questions that come up once teams see the log, answered from this rebuild.
How do you test whether tags fire before consent?
Does Consent Mode v2 block the Meta Pixel?
Does the DPDP Act apply to website analytics?
Send us your site and where your visitors are
Pick the regions you sell to and send the site. We reply within one business day with which tags fire before a choice today, and which law sets the bar for your setup.