<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Immanuel Schranz</title>
    <description>The latest articles on DEV Community by Immanuel Schranz (@immsch).</description>
    <link>https://dev.to/immsch</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4241194%2F17d6398c-6889-40e6-9fd3-370ac1fc8c63.png</url>
      <title>DEV Community: Immanuel Schranz</title>
      <link>https://dev.to/immsch</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/immsch"/>
    <language>en</language>
    <item>
      <title>What EU regulators actually look at in a cookie banner</title>
      <dc:creator>Immanuel Schranz</dc:creator>
      <pubDate>Sat, 21 Nov 2026 19:25:34 +0000</pubDate>
      <link>https://dev.to/immsch/what-eu-regulators-actually-look-at-in-a-cookie-banner-37e9</link>
      <guid>https://dev.to/immsch/what-eu-regulators-actually-look-at-in-a-cookie-banner-37e9</guid>
      <description>&lt;p&gt;I spent the last few weeks looking at cookie banners on a lot of small&lt;br&gt;
business websites. Almost all of them had one. Very few would survive a&lt;br&gt;
careful look.&lt;/p&gt;

&lt;p&gt;The good news: you don't have to guess what "careful" means. In January&lt;br&gt;
2023 the European Data Protection Board published the report of its Cookie&lt;br&gt;
Banner Taskforce, where the national authorities wrote down which banner&lt;br&gt;
designs they look at and how they see them. It's short and readable. Below&lt;br&gt;
are the points from it you can actually check on your own site, plus a&lt;br&gt;
couple from the EDPB consent guidelines. For each one: what it means and&lt;br&gt;
how to look for it in five minutes.&lt;/p&gt;

&lt;p&gt;Quick disclaimer: I'm a developer, not a lawyer. The report itself says&lt;br&gt;
the authorities decide case by case. Treat this as a list of things to&lt;br&gt;
look at, not a verdict.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Is there a way to say no on the first screen?
&lt;/h3&gt;

&lt;p&gt;If the banner offers "Accept all" and the only way to refuse is hidden&lt;br&gt;
behind "Settings", that's the first thing the report talks about (paras 6&lt;br&gt;
to 8). The vast majority of authorities saw a banner with no reject option&lt;br&gt;
on any layer as not giving valid consent. Whether reject has to be on the&lt;br&gt;
very first layer is where they differ, but "Reject all" next to "Accept&lt;br&gt;
all" is the safe and common answer.&lt;/p&gt;

&lt;p&gt;Check: open your site in a private window. Can you refuse with one click,&lt;br&gt;
without opening anything else?&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Does "reject" look like a button?
&lt;/h3&gt;

&lt;p&gt;A big coloured "Accept all" button next to a small grey "continue without&lt;br&gt;
accepting" link in the text is the classic. The report names a reject&lt;br&gt;
option that only exists as a link inside the banner text, without enough&lt;br&gt;
visual weight, as an example where consent isn't valid (paras 13 and 14).&lt;br&gt;
Same if reject sits outside the banner, for example only in the footer.&lt;/p&gt;

&lt;p&gt;Check: squint at the banner. Do both choices look like things you can&lt;br&gt;
click, with roughly the same visual weight?&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Can you read it?
&lt;/h3&gt;

&lt;p&gt;Colours and contrast are judged case by case (paras 15 to 19), but the&lt;br&gt;
report calls out the obvious case: a reject button whose text barely&lt;br&gt;
stands out from the background. A handy yardstick is WCAG: 4.5:1 for&lt;br&gt;
normal text, 3:1 for large text.&lt;/p&gt;

&lt;p&gt;Check: right-click the reject button, Inspect, and look at the contrast&lt;br&gt;
ratio Chrome shows in the colour picker. Most banner tools let you set&lt;br&gt;
the button colours; giving reject the same style as accept fixes this and&lt;br&gt;
point 2 at once.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Are any boxes ticked by default?
&lt;/h3&gt;

&lt;p&gt;Open the settings layer. If "Statistics" or "Marketing" is already&lt;br&gt;
switched on, that's a pre-ticked box, and pre-ticked boxes don't count as&lt;br&gt;
consent (paras 9 and 10, and the CJEU Planet49 ruling). Only strictly&lt;br&gt;
necessary cookies can be on by default, usually shown as a locked switch.&lt;/p&gt;

&lt;p&gt;Check: click "Settings" and look at every toggle before touching anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Does it say "legitimate interest" anywhere?
&lt;/h3&gt;

&lt;p&gt;Common in banners that use the IAB framework: next to each purpose&lt;br&gt;
there's a second toggle labelled "legitimate interest", switched on. For&lt;br&gt;
setting or reading cookies, legitimate interest isn't a basis you can use,&lt;br&gt;
consent is (paras 20 to 25, Art. 5(3) of the ePrivacy Directive).&lt;/p&gt;

&lt;p&gt;Check: in the settings, look for the words "legitimate interest" or&lt;br&gt;
"berechtigtes Interesse". If they're there, your banner tool usually has a&lt;br&gt;
switch to turn them off for cookie purposes.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Can people change their mind later?
&lt;/h3&gt;

&lt;p&gt;After clicking "Accept all", the banner disappears. Now try to undo that.&lt;br&gt;
The report expects an easy way to withdraw, like a small floating icon or&lt;br&gt;
a link at a place people know, such as the footer (paras 31 to 35), and&lt;br&gt;
the GDPR says withdrawing must be as easy as giving consent (Art. 7(3)).&lt;/p&gt;

&lt;p&gt;Check: accept everything, go to another page, and try to reopen the&lt;br&gt;
cookie settings without clearing your browser data. If you have to dig&lt;br&gt;
through the privacy policy, it's probably not "as easy".&lt;/p&gt;

&lt;h3&gt;
  
  
  7. "By continuing to browse, you agree..."
&lt;/h3&gt;

&lt;p&gt;Still around more than you'd think. Scrolling or simply using the site is&lt;br&gt;
not a clear affirmative action, so it can't be consent (EDPB consent&lt;br&gt;
guidelines 05/2020, para 86). The same goes for wording that suggests the&lt;br&gt;
site can only be used if you accept (para 13 of the report).&lt;/p&gt;

&lt;p&gt;Check: read your banner text out loud. If it says or implies that using&lt;br&gt;
the site means agreeing, rewrite that sentence.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Does it say what the cookies are for?
&lt;/h3&gt;

&lt;p&gt;Consent has to be informed. A banner that just says "We use cookies" and&lt;br&gt;
nothing else doesn't tell anyone what they're agreeing to (paras 12 and&lt;br&gt;
13). It doesn't need to be long, "for statistics and advertising" already&lt;br&gt;
answers the question.&lt;/p&gt;

&lt;p&gt;Check: could someone tell from the first layer alone what happens if they&lt;br&gt;
click accept?&lt;/p&gt;

&lt;h3&gt;
  
  
  9. And the boring part: does reject actually block anything?
&lt;/h3&gt;

&lt;p&gt;All of the above is about how the banner looks. None of it matters if&lt;br&gt;
the analytics tag fires before anyone clicks, or keeps firing after&lt;br&gt;
"Reject". That's Art. 5(3) of the ePrivacy Directive, and it's the most&lt;br&gt;
common problem I see.&lt;/p&gt;

&lt;p&gt;Check: private window, DevTools, Network tab, reload, don't touch the&lt;br&gt;
banner. Anything going to google-analytics, facebook, tiktok and friends&lt;br&gt;
at this point loads without consent. Then click reject and reload again.&lt;/p&gt;

&lt;h3&gt;
  
  
  One thing this list can't do
&lt;/h3&gt;

&lt;p&gt;From the outside you can't tell whether a cookie is really "strictly&lt;br&gt;
necessary" or just labelled that way (paras 26 to 30). That part needs&lt;br&gt;
someone who knows what each cookie does.&lt;/p&gt;

&lt;h3&gt;
  
  
  If you'd rather not click through this by hand
&lt;/h3&gt;

&lt;p&gt;Doing these checks on one site takes maybe ten minutes. Doing them again&lt;br&gt;
after every plugin update is the annoying part. I built a scanner that&lt;br&gt;
goes through all of the points above automatically, including opening the&lt;br&gt;
settings and coming back after accepting, and shows the exact setting to&lt;br&gt;
change. The list of what it checks, with the paragraph numbers, is here&lt;br&gt;
if you want to compare notes:&lt;br&gt;
&lt;a href="https://konformia.at/en/guides/cookie-banner-requirements?q=devto-banner" rel="noopener noreferrer"&gt;https://konformia.at/en/guides/cookie-banner-requirements&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>privacy</category>
      <category>javascript</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I checked 848 EU websites: 56 % load trackers before you consent</title>
      <dc:creator>Immanuel Schranz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:28:14 +0000</pubDate>
      <link>https://dev.to/immsch/i-checked-848-eu-websites-56-load-trackers-before-you-consent-2dh4</link>
      <guid>https://dev.to/immsch/i-checked-848-eu-websites-56-load-trackers-before-you-consent-2dh4</guid>
      <description>&lt;p&gt;Cookie banners are everywhere in the EU. I wanted to know how many of them actually hold anything back, so I loaded 848 websites from 14 EU countries and recorded every request before anyone touched the banner.&lt;/p&gt;

&lt;h2&gt;
  
  
  Results
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;473 of 848 (56 %)&lt;/strong&gt; loaded analytics or advertising services, such as the Meta Pixel or Google Analytics, before consent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;487 of 848 (57 %)&lt;/strong&gt; loaded Google Fonts from Google's servers before consent.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I opened 20 hits per number again by hand. Method, limits and the full numbers: &lt;a href="https://konformia.at/en/cookie-study?q=devto" rel="noopener noreferrer"&gt;https://konformia.at/en/cookie-study&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the banner looks fine but isn't
&lt;/h2&gt;

&lt;p&gt;Most of these sites have a cookie banner. It often blocks the analytics tags, but not the fonts, maps or embeds that come with the theme, because those load outside the banner's control. Each Google Fonts request sends the visitor's IP address to Google.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check your own site in two minutes
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open DevTools, Network tab, tick "Disable cache".&lt;/li&gt;
&lt;li&gt;Reload in a private window and don't click the banner.&lt;/li&gt;
&lt;li&gt;Filter for &lt;code&gt;google-analytics&lt;/code&gt;, &lt;code&gt;facebook&lt;/code&gt;, &lt;code&gt;fonts.googleapis&lt;/code&gt;. Anything there loaded before consent.&lt;/li&gt;
&lt;li&gt;Click "Reject", reload, and look again.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you'd rather not do that page by page, I built a free check that does it across the whole site and names the fix for your system: &lt;a href="https://konformia.at/en/cookie-study?q=devto" rel="noopener noreferrer"&gt;https://konformia.at/en/cookie-study&lt;/a&gt; (no sign-up).&lt;/p&gt;

&lt;p&gt;I'm a solo dev from Vienna. Questions about the method are more than welcome in the comments.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>How to check if Google Consent Mode v2 is actually working (gcs and gcd explained)</title>
      <dc:creator>Immanuel Schranz</dc:creator>
      <pubDate>Thu, 12 Nov 2026 13:41:18 +0000</pubDate>
      <link>https://dev.to/immsch/how-to-check-if-google-consent-mode-v2-is-actually-working-gcs-and-gcd-explained-19o7</link>
      <guid>https://dev.to/immsch/how-to-check-if-google-consent-mode-v2-is-actually-working-gcs-and-gcd-explained-19o7</guid>
      <description>&lt;p&gt;A cookie banner can show "Reject" and still tell Google's tags "granted".&lt;br&gt;
The banner looks fine, the choice is saved, and nobody notices, because the&lt;br&gt;
only place the truth shows up is two query parameters on every Google&lt;br&gt;
measurement request: gcs and gcd.&lt;/p&gt;

&lt;p&gt;Here is how to read them in about two minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Catch a request before anyone clicks
&lt;/h2&gt;

&lt;p&gt;Open the site in a private window, open DevTools (F12), go to the Network&lt;br&gt;
tab, filter for "collect" and reload. Do not touch the banner.&lt;/p&gt;

&lt;p&gt;Every request to Google Analytics carries a gcs parameter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;G100: ad and analytics storage denied&lt;/li&gt;
&lt;li&gt;G111: both granted&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before the visitor has chosen anything, G111 should never appear. If it&lt;br&gt;
does, the default in your consent setup says "granted".&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Read gcd for the v2 signals
&lt;/h2&gt;

&lt;p&gt;gcd starts with 13, then one letter per signal, in this order:&lt;br&gt;
ad_storage, analytics_storage, ad_user_data, ad_personalization.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;l: not set&lt;/li&gt;
&lt;li&gt;p: denied&lt;/li&gt;
&lt;li&gt;t: granted&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An l on the last two positions means the two signals added with v2 are&lt;br&gt;
missing. Google has required them for users in the EEA since March 2024 if&lt;br&gt;
you use Google Ads for measurement, audiences or remarketing.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Click "Reject" and look again
&lt;/h2&gt;

&lt;p&gt;Filter for "collect" again. gcs should stay G100, or in basic mode no&lt;br&gt;
request is sent at all. No _ga cookie should appear.&lt;/p&gt;

&lt;h2&gt;
  
  
  The usual causes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The default in the banner's Tag Manager template is "granted", or the
configured region does not include the visitor's country.&lt;/li&gt;
&lt;li&gt;A second copy of the Google tag sits in the theme, a plugin or a shop app.
It never got the default and sends with no consent state at all.&lt;/li&gt;
&lt;li&gt;v2 is not switched on in the banner tool, or the Tag Manager template is
outdated.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Fix order: default to "denied" for all four signals before any other Google&lt;br&gt;
tag, switch on v2 in the banner tool, load each Google tag once (ideally&lt;br&gt;
through Tag Manager), then measure again after "Reject".&lt;/p&gt;

&lt;p&gt;Consent Mode only covers Google tags. Meta Pixel, TikTok and the rest have&lt;br&gt;
to be held back by the banner tool itself.&lt;/p&gt;

&lt;p&gt;If you would rather not do this by hand on every page: I built a scanner&lt;br&gt;
that loads the page in a fresh browser, reads gcs and gcd on every Google&lt;br&gt;
request, clicks "Reject" and measures again. Free check here:&lt;br&gt;
&lt;a href="https://konformia.at/en/guides/google-consent-mode-v2?q=devto" rel="noopener noreferrer"&gt;https://konformia.at/en/guides/google-consent-mode-v2&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>analytics</category>
      <category>privacy</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
