Checklist
Do Meta, TikTok, Microsoft UET and Clarity hear a refusal?
Store M, one DE visit: after Continue without accepting, Microsoft UET kept sending with asc=D. Meta, TikTok and Clarity sent nothing. Not legal advice.
In brief
Store M, one German visit on October 20, 2026. After Continue without accepting, UET kept sending /action with asc=D. Meta, TikTok, and Clarity sent no collector requests in that window. Accept started those three. The Accept run had no UET /action, so asc was not on the wire. Not legal advice.
Not legal advice
This page records what one browser sent on one visit. It is not legal advice.
Short answer
After Continue without accepting on Store M, Meta, TikTok, and Clarity sent no requests to their collectors in that window. Microsoft UET kept sending, and every /action request carried asc=D: 5 on Fresh, 7 before the click, and 6 after it. Google stayed on the store's own collector, with gcs=G100 on the 5 requests after the click, and 0 requests to a Google host. After Accept, Meta sent 2 PageView requests, TikTok sent 6 pixel API requests, and Clarity sent 3 /collect requests. In the Accept run we observed no /action request, so there was no asc value to read.
What each vendor sends on the wire
Vendor doc pages were opened on October 21, 2026.
| Vendor | Consent call | On the request |
|---|---|---|
| Consent Mode, gtag('consent', ...) | gcs and gcd | |
| Microsoft UET | uetq.push('consent', 'default' or 'update', { ad_storage }) | asc on /action: D denied, G granted. These /action rows were D. |
| Microsoft Clarity | clarity('consentv2', { ad_Storage, analytics_Storage }) | Cookieless /collect can continue. Read the state in the Console. |
| Meta | fbq('consent', 'revoke' or 'grant') | No refusal parameter. Watch /tr/. Limited Data Use adds dpo. |
| TikTok | Base code lists holdConsent, grantConsent, and revokeConsent | No refusal parameter. Watch /api/v2/pixel. |
| No consent API | See the Insight Tag page. |
Microsoft's UET page says to push ad_storage: 'denied' by default, then 'update' after the choice. Advanced Consent Mode loads the tag at once and sends anonymized data while denied. Basic mode waits for a grant. For the EEA, the UK, and Switzerland, Microsoft enforces Consent Mode and the default is denied. From October 31, 2025, Clarity requires a consent signal for those regions, and a denied state can still call /collect with no _clck or _clsk. Not legal advice.
TikTok's pixel base code lists holdConsent, grantConsent, and revokeConsent. LinkedIn has no consent API; see LinkedIn Insight Tag before Accept.
How we captured it
Store M was captured on October 20, 2026, 09:44 to 09:56 UTC+8 (October 19, 18:44 to 18:56 PDT), on one German residential IP. Playwright Chromium 148, headless, de-DE, Europe/Berlin, a regular user-agent string, a clean profile per state. Didomi's country override was off, and the banner opened on its own.
The first layer has no refusal button. The refusal control is the top-right link Continuer sans accepter (Continue without accepting).
Each state ran once. Fresh did not click. Accept was at 09:47:13 UTC+8. Continue without accepting was at 09:47:54 UTC+8. Path: home, wait for the banner, click, 12 seconds, one category page, 15 seconds. The netlog has each request's start time and URL parameters. There is no HAR. POST bodies were not read. Images and video on the store host were blocked.
The same Store M capture also feeds our TCF v2.4 tests. This page reports only the vendor requests.
Store M: Fresh, Continue without accepting, Accept
| Vendor | Endpoint | Fresh | After Continue without accepting | After Accept |
|---|---|---|---|---|
| Microsoft UET | bat.bing.com / bat.bing.net /action | 5, all asc=D (consent 4, pageLoad 1) | 6, all asc=D (consent 4, pageLoad 1, pageHide 1). 7 more before the click, also asc=D | No /action request observed in this run. 2 other UET requests. |
| Meta Pixel | www.facebook.com /tr/ | 0 | 0 | 2, ev=PageView. URL had no dpo. |
| TikTok Pixel | analytics.tiktok.com /api/v2/pixel* | 0. Script not loaded. | 0. Script not loaded. | 6 (/api/v2/pixel 4, /api/v2/pixel/act 2). Script requests 6. |
| Microsoft Clarity | *.clarity.ms/collect | 0. Script not loaded. | 0. Script not loaded. | /collect 3. Script requests 4. |
| Store subdomain collector, plus Google hosts | Collector 1, gcs=G100 | Collector 5, gcs=G100. Google hosts 0. | Collector 5, gcs=G111. Google hosts 15 with G111 and 1 with G100. |
Microsoft UET kept sending with asc=D
Fresh had 5 /action requests and Continue without accepting was followed by 6, all asc=D. Both sets had four with evt=consent. Seven before that click were asc=D too. Microsoft's docs say Advanced Consent Mode keeps sending while denied. This capture did not check which mode Store M uses or which script set asc=D. See Bing UET before Accept.
In the Accept run we observed no /action request, so there was no asc value to read. The 2 other UET requests in that run were not /action.
Meta, TikTok and Clarity sent nothing until Accept
Meta /tr/, TikTok /api/v2/pixel, and Clarity /collect were 0 on Fresh and after Continue without accepting. TikTok and Clarity scripts did not load in those states. All three started on Accept. No run showed fbevents.js from a Meta host. On another visit, Clarity kept calling /collect after the refusal.
Google went through the store's own subdomain
The store's own collector carried gcs=G100 on Fresh and after Continue without accepting, and gcs=G111 after Accept, when Google hosts appeared. Read gcs on Consent Mode cookieless ping versus a real event.
Cookies at the end of each run
Names only. An id inside a name is written <id>. Fresh and Continue without accepting ended with cookies on the store domain only. _fbp, _uetsid, _uetvid, and MUID were absent in all three states.
| State | Names |
|---|---|
| Fresh | None for UET, Meta, TikTok, or Clarity. |
| Continue without accepting | None for UET, Meta, TikTok, or Clarity. |
| Accept | _ttp, ttcsid, ttcsid_<id>, _tt_enable_cookie, _clck, _clsk, _ga, _ga_<id>, _gcl_au. |
What the TC String covers on Store M
After Continue without accepting, purpose consents and vendor consents were both 0. After Accept, purposes 1-11 were consented and 9 vendors were consented. TikTok Ad Network (GVL 986) is among the 9 disclosed vendors. Microsoft Advertising (GVL 1126) is not. Meta is not in TCF. Clarity is not in the GVL. The string can cover TikTok. UET, Meta, and Clarity sit outside it, so those three depend on other code on the page.
Check your own site in DevTools
Use a clean profile, in this order: Fresh with no click, then the refusal control, then a new profile for Accept. Preserve the log.
- UET: filter
bat.bingand readascon each/actionURL. - Meta: filter
facebook.com/tr. Note whether it fired and whether the URL containsdpo. - TikTok: filter
analytics.tiktok.com. - Clarity: filter
clarity.ms/collect. In the Console, runclarity('metadata', console.log). This capture did not run that call.
What the browser cannot show
The netlog stops at the browser. It does not show Meta's Conversions API, TikTok's Events API, a UET offline conversion upload, or where the store's collector forwarded the hit. The Meta split is on Meta's browser pixel and the server path.
Two checks, two scopes
Run the free first-load scan to see whether your banner appears and what loads before a choice. The free cookie audit records the first load only. It clicks no button.
The $49 EU audit is paid. It visits from the EU and records Fresh, Reject, and Accept on the same URL.
FAQ
Does the Meta Pixel send a deny signal?
/tr/ has no refusal parameter. Store M sent 0 after Continue without accepting and 2 PageView hits after Accept, with no dpo.
Is `asc=D` after a refusal a failure?
asc=D means that UET request carried a denied state. Whether the send is acceptable depends on the tag setup and on advice for that site. Not legal advice.
Why did Clarity send nothing on Store M when it can run cookieless?
The Clarity script did not load on Store M before Accept, so no /collect request went out. Clarity can still call /collect with no _clck or _clsk. This visit did not.
Does Store M's TC String cover UET?
No. Microsoft Advertising (GVL 1126) is not among Store M's 9 disclosed vendors. UET still sent /action with asc=D after Continue without accepting.
Limits
One run per state, one German exit, two pages each. There is no HAR, and POST bodies were not read, so TikTok and Clarity payloads are unknown. We did not call clarity('metadata') or record a consentv2 call. Accept had no UET /action request. Server paths stay invisible.
Related guides
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.
- Microsoft Learn, Setting up UET for consent mode (accessed 2026-10-21)
- Microsoft Learn, Clarity Consent Mode (accessed 2026-10-21)
- Microsoft Learn, Clarity Consent API v2 (accessed 2026-10-21)
- Meta for Developers, Meta Pixel GDPR and cookie consent (accessed 2026-10-21)
- TikTok For Business, Using cookies with TikTok Pixel (accessed 2026-10-21)
- IAB Europe Global Vendor List v181 (accessed 2026-10-21)
Save a US-baseline technical record
After a DIY check, run a free US-baseline audit: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.