Cookieless Line Item Tester — GAM 135050247

TCF stub active — __tcfapi is defined before GPT with a real no-consent TC string from berlingske.dk. GPT reads this during its init. In TC string mode we do NOT override limitedAds manually — if GPT doesn't trigger lrm=50 from the TC string, the OMG LI should win. That confirms the fix.

Configuration

🔓 Full Bypass: __tcfapi overridden to gdprApplies=false, limitedAds=false, NPA=0. GAM sees no GDPR restriction at all. If LI still doesn't win → the issue is structural (nvt=1 / ad unit path / LI targeting mismatch), NOT CMP/lrm.
ℹ TC string mode: GPT reads the no-consent TC string and decides limitedAds itself. If the OMG LI wins here → confirms production fix works once CMP emits a TC string.
⚠ lrm=50 forced ON — simulates production traffic with no TCF signal at all. LI should NOT win.
Full Bypass: overrides __tcfapi to say GDPR doesn't apply + forces limitedAds=false + NPA=0. Eliminates every privacy signal. If the LI still doesn't win here → the problem is structural (ad unit path, nvt=1, or LI targeting mismatch) — not CMP/lrm. TC string mode: most realistic production test. Force lrm=50 OFF: belt-and-suspenders. Force lrm=50 ON: confirms LI is blocked when lrm is active.

Ad Slot

Debug Log

Waiting…
Network tab: filter securepubads.g.doubleclick.net/gampad/ads — check prev_scp for KVPs and these params: ltd=1 = lrm=50 active | nvt=1 = non-validated traffic (test domain not authorized) | npa=1 = non-personalized ads | gdpr=1 = GDPR applies. In Full Bypass mode, ltd, gdpr, and npa should all be absent or 0.