[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-slug_blog_3_1":3,"blog-slug_blog_web-analytics-and-consent_1000_1":40},{"article":4,"articles":15,"meta":33,"languages":39},{"id":5,"title":6,"excerpt":7,"locale":8,"slug":9,"authorSlug":10,"automaticTranslated":11,"publishedAt":12,"updatedAt":13,"doFollowLinks":11,"showIndex":11,"showCallToActions":11,"articleType":14},3060,"The EU wants to kill cookie banners","The EU wants to end annoying cookie pop-ups by letting users set their consent once in their browser. If passed, websites will have to respect those choices.","en","the-eu-wants-to-kill-cookie-banners-by-moving-consent-to-your-browser","iron-brands",false,"2025-11-20T05:40:14.356Z","2025-11-20T06:13:15.812Z","blog",[4,16,26],{"id":17,"title":18,"excerpt":19,"locale":8,"slug":20,"authorSlug":10,"automaticTranslated":11,"publishedAt":21,"updatedAt":22,"ctaTitle":23,"ctaDescription":24,"doFollowLinks":11,"showIndex":25,"showCallToActions":11,"articleType":14},3019,"Google is tracking you (even when you use DuckDuckGo)","Google tracks users even on DuckDuckGo via Analytics and embeds. A new study shows how deep Google’s web tracking really goes.","google-is-tracking-you-even-when-you-use-duck-duck-go","2025-07-14T08:56:41.709Z","2025-07-14T11:26:01.386Z","If you care about privacy, you don't use Google Analytics","Ditch the tracking, keep the insights. Try Simple Analytics.",true,{"id":27,"title":28,"excerpt":29,"locale":8,"slug":30,"authorSlug":10,"automaticTranslated":11,"publishedAt":31,"updatedAt":32,"doFollowLinks":11,"showIndex":11,"showCallToActions":11,"articleType":14},3018," German court rules Meta’s tracking tech violates GDPR","German court rules Meta’s tracking tech violates GDPR, allowing lawsuits without proof of harm. Big risks ahead for sites using Meta pixels.","german-court-rules-meta-s-tracking-tech-violates-gdpr","2025-07-10T08:20:51.111Z","2025-07-10T12:16:26.327Z",{"pagination":34},{"page":35,"pageSize":36,"pageCount":37,"total":38},1,3,362,1084,{},{"article":41},{"contentHtml":42,"content":43,"inlineMedia":44,"id":46,"title":47,"excerpt":48,"locale":8,"slug":49,"authorSlug":50,"automaticTranslated":11,"publishedAt":51,"updatedAt":52,"doFollowLinks":11,"showIndex":25,"showCallToActions":25,"articleType":14,"languages":53},"\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Last week \u003CNuxtLink to=\"/blog/cookies-101\"  >we discussed cookies\u003C/NuxtLink> and their regulation under EU law and mentioned how \u003Cstrong>non-essential cookies require consent\u003C/strong>. These are the sort of cookies that power cookie-based web analytics services such as Google Analytics and Adobe Analytics. Today we will dig more into consent and what it means for web analytics specifically.\u003C/ContentEditable>\n\u003Col class=\"counters\">\u003Cli>\u003CNuxtLink to=\"#what-does-cookie-consent-look-like\">What does cookie consent look like?\u003C/NuxtLink>\u003Col>\u003Cli>\u003CNuxtLink to=\"#consent-is-unambiguous\">Consent is unambiguous\u003C/NuxtLink>\u003C/li>\u003C/ol>\u003C/li>\u003Cli>\u003CNuxtLink to=\"#consent-is-specific\">Consent is specific\u003C/NuxtLink>\u003Col>\u003Cli>\u003CNuxtLink to=\"#consent-is-informed\">Consent is informed\u003C/NuxtLink>\u003C/li>\u003Cli>\u003CNuxtLink to=\"#consent-can-be-withdrawn\">Consent can be withdrawn\u003C/NuxtLink>\u003C/li>\u003Cli>\u003CNuxtLink to=\"#consent-is-freely-given\">Consent is freely given\u003C/NuxtLink>\u003C/li>\u003C/ol>\u003C/li>\u003Cli>\u003CNuxtLink to=\"#what-are-the-most-common-issues-with-consent\">What are the most common issues with consent?\u003C/NuxtLink>\u003Col>\u003Cli>\u003CNuxtLink to=\"#deceptive-banners\">Deceptive banners\u003C/NuxtLink>\u003C/li>\u003Cli>\u003CNuxtLink to=\"#cookie-walls\">Cookie walls\u003C/NuxtLink>\u003C/li>\u003C/ol>\u003C/li>\u003Cli>\u003CNuxtLink to=\"#conclusions\">Conclusions\u003C/NuxtLink>\u003C/li>\u003C/ol>\u003CCtaTwo />\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Let's dive in!\u003C/ContentEditable>\n\u003CContentEditable  id=\"a-tldr-on-consent-and-cookies\" parent=\"\" tag=\"h2\" :articleId=\"2425\">A \u003Cem>tl;dr\u003C/em> on consent and cookies\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Before we head in, let’s go through a high-level overview of consent and cookies:\u003C/ContentEditable>\n\u003Cul>\n\u003Cli>Web analytics cookies \u003Cstrong>always need consent\u003C/strong> because they are non-seential.\u003C/li>\n\u003Cli>GDPR consent is only valid when it \u003Cstrong>meets specific criteria\u003C/strong>: it is \u003Cem>freely given, specific, informed, unambiguous,\u003C/em> and \u003Cem>possible to withdraw\u003C/em>.\u003C/li>\n\u003C/ul>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">So: analytics cookies require consent, and this consent needs to meet certain standards. This means that your cookie banner needs to be designed a certain way. But there is more to it, and while most of the rules are uncontroversial, some are hotly debated in the legal community.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Let’s dive in!\u003C/ContentEditable>\n\u003CContentEditable  id=\"what-does-cookie-consent-look-like\" parent=\"\" tag=\"h2\" :articleId=\"2425\">What does cookie consent look like?\u003C/ContentEditable>\n\u003CContentEditable  id=\"consent-is-unambiguous\" parent=\"\" tag=\"h3\" :articleId=\"2425\">Consent is unambiguous\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">In a nutshell, the GDPR’s requirement for unambiguous consent means that only \u003Cstrong>active, opt-in consent\u003C/strong> is valid. There is no such thing as an implicit or opt-out consent under the GDPR.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">The rule of opt-in consent has important consequences for cookie banners. A well designed cookie banner uses \u003Cstrong>affirmative wording\u003C/strong> such as \u003Cem>“I accept cookies”\u003C/em> or \u003Cem>“I consent to the use of cookies”\u003C/em>. This is different from merely \u003Cem>acknowledging\u003C/em> or \u003Cem>understanding\u003C/em> that cookies will be used.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Additionally, a well-designed website does not write cookies until users \u003Cstrong>make a choice\u003C/strong>. Ignoring a banner or clicking a “close” button to dismiss it never, ever constitutes or implies consent.\u003C/ContentEditable>\n\u003CContentEditable  id=\"consent-is-specific\" parent=\"\" tag=\"h2\" :articleId=\"2425\">Consent is specific\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Consent is only valid when given for a specific purpose. This entails that consent must be \u003Cstrong>granular\u003C/strong>: when the same cookies are used for multiple purposes, then you need multiple consents- one for each purpose.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">In practice, the best way to collect granular consent is to \u003Cstrong>use your web analytics cookies for web analytics only\u003C/strong>. This allows you to collect a separate consent for other cookies such as user authentication cookies, and to write essential cookies without user consent (which is absolutely fine under the law).\u003C/ContentEditable>\n\u003CContentEditable  id=\"consent-is-informed\" parent=\"\" tag=\"h3\" :articleId=\"2425\">Consent is informed\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">This requirement is intuitive: if I don’t know what I am consenting to, then I am not really consenting in any meaningful way. I do not necessarily need to understand all the tiny technicalities about your web analytics, but I do need to understand \u003Cstrong>the facts that really matter\u003C/strong> for my decision: who takes my data, what data they take, for what purpose, and with what potential consequences.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">In practice, this means that a cookie banner should:\u003C/ContentEditable>\n\u003Cul>\n\u003Cli>Tell the user what the cookies are for.\u003C/li>\n\u003Cli>Use clear, accessible, accurate language.\u003C/li>\n\u003Cli>Tell the user with whom their personal data will be shared. For Google Analytics, this includes Google and its advertising partners.\u003C/li>\n\u003C/ul>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">This information needs to be concise and in plain English. In practice, it is usually a good idea to deliver the most crucial information through the cookie banner and link to a cookie policy with more in-depth information.\u003C/ContentEditable>\n\u003CContentEditable  id=\"consent-can-be-withdrawn\" parent=\"\" tag=\"h3\" :articleId=\"2425\">Consent can be withdrawn\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Consent is revocable. You should allow users to \u003Cstrong>review their cookie preferences\u003C/strong> and easily opt out of any cookies they might have agreed to.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Please note that the withdrawal of consent sometimes comes with a \u003Cstrong>request for erasure\u003C/strong>. In that scenario, you get a deadline for deleting all the data from the requestor. This means all the web analytics data that relates to their cookies and the unique ID they contain.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Most companies don’t think about this stuff when they set up their web analytics and have no clue what to do when they get a request for erasure. We can’t go into too much depth here, but an organization should, at the very least:\u003C/ContentEditable>\n\u003Cul>\n\u003Cli>\u003Cstrong>establish a clear procedure\u003C/strong> for handling requests\u003C/li>\n\u003Cli>ensure it can easily \u003Cstrong>retrieve and delete data\u003C/strong> from individual users. For web analytics, this means being able to filter data points by unique IDs.\u003C/li>\n\u003C/ul>\n\u003CContentEditable  id=\"consent-is-freely-given\" parent=\"\" tag=\"h3\" :articleId=\"2425\">Consent is freely given\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">The GDPR requires every consent to be \u003Cstrong>freely given\u003C/strong>. This is why your hospital cannot collect consent to the use of your data as a requirement to provide health care, and why employers should refrain from having employees sign GDPR consent forms. You have no meaningful choice when witholding consent means dying or losing your job.\u003C/ContentEditable>\n\u003CContentEditable  id=\"what-are-the-most-common-issues-with-consent\" parent=\"\" tag=\"h2\" :articleId=\"2425\">What are the most common issues with consent?\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Two compliance issues have surfaced lately with web analytics. \u003Cstrong>Deceptive cookie banners\u003C/strong> are found all over the Internet and try to nudge users towards accepting cookies they do not really want, while \u003Cstrong>cookie walls\u003C/strong> require visitors to pay to get rid of cookies.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Both of these issues are fairly controversial in the privacy community. Let's see what the fuss is all about, and what it means for web analytics\u003C/ContentEditable>\n\u003CContentEditable  id=\"deceptive-banners\" parent=\"\" tag=\"h3\" :articleId=\"2425\">Deceptive banners\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Accepting cookies is always easy as pie, but rejecting them usually requires you to jump through hoops. This is a deliberate design choice: many banners nudge users into accepting cookies by making the rejection process to be as annoying, confusing and time consuming as possible. Visitors often give in because they don’t have the time or patience to figure their way out of every cookie banner they see.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Deceptive designs look like a good solution for websites. After all, the user clicked “I accept”, so everything should be fine. Right? Not quite. If consent was extorted through deception and exhaustion, then it is neither free nor unambiguous.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Thankfully, the European Data Protection Board \u003CNuxtLink to=\"/blog/eu-task-force-cracks-down-on-cookie-banners\"  >took a stance\u003C/NuxtLink> against deceptive cookie banners. Its stance is not unanimous but is shared by the vast majority of enforcers. We are starting to see \u003CNuxtLink to=\"/blog/german-authority-cookie-banners\"  >some serious enforcement\u003C/NuxtLink>, too.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Bottom line: if you \u003Cem>really\u003C/em> need to use cookie-based analytics, be on the right side of the law and \u003Cstrong>make your cookies easy to reject\u003C/strong>. Make sure that the “reject all” button is clearly visible, clearly worded, and available on the first level of the banner’s interface!\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">(And yes, this means that many users \u003Cem>will\u003C/em> reject your cookies.)\u003C/ContentEditable>\n\u003CContentEditable  id=\"cookie-walls\" parent=\"\" tag=\"h3\" :articleId=\"2425\">Cookie walls\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Some cookie banners do not include a “reject all cookies” button and offer a different choice instead: users can either accept cookies, or sign up for a paid subscription that allows them to browse the site without cookies. In other words: pay with your money, pay with your data, or leave. These banners are referred to as \u003Cstrong>cookie walls\u003C/strong> and are typically used by digital newspapers.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Cookie walls entail a \u003Cstrong>commodification of personal data\u003C/strong> that a part of the privacy community considers undesirable at best and unlawful at worst. Proponents of cookie walls say that publishers cannot provide content for free and need ad revenue to keep up the work. Critics of cookie walls point to contextual advertising as an alternative source of revenue for publishers and observe that a \u003Cstrong>fundamental right\u003C/strong> such as data protection cannot be commodified (they are right, by the way).\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">In practice, your mileage with a cookie wall may vary depending on your jurisdiction. For instance, cookie walls are used by many German news outlets because regulators tend to be somewhat lenient on that front.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">We really dislike cookie walls, but if you \u003Cem>really\u003C/em> want to implement one, it might be prudent to \u003Cstrong>wait for a while\u003C/strong>. Meta took a page from news outlets and implemented a \u003Cstrong>pay-or-ok\u003C/strong> subscription schemes in an attempt to justify its aggressive surveillance-based advertising. European regulators will soon need to take a stance on Meta's approach, and once they do, their position on cookie walls will probably become clearer as well.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">(By the way: pay-or-ok is a really big deal for the future on the GDPR! If you are curious about this crucial privacy topic, feel free to check out \u003CNuxtLink to=\"/blog/meta-subscriptions-under-attack\"  >our blog\u003C/NuxtLink> on Meta subscriptions.)\u003C/ContentEditable>\n\u003CContentEditable  id=\"conclusions\" parent=\"\" tag=\"h2\" :articleId=\"2425\">Conclusions\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Overall, consent rules for web analytics are fairly stringent in the EU. This creates a problem for cookie-based analytics: strategies that lead to good opt-in rates for cookies, are likely to violate the law. Websites are stuck between a rock and a hard place, as they have to \u003Cstrong>choose between low opt-in rates or a compliance risk\u003C/strong>.\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">This is why many companies are moving towards \u003Cstrong>cookieless analytics\u003C/strong> solutions. And we are proud to offer the most privacy-friendly one!\u003C/ContentEditable>\n\u003CContentEditable  parent=\"\" tag=\"p\" :articleId=\"2425\">Simple Analytics is the cookieless web analytics solution that \u003Cstrong>collects no personal data\u003C/strong>. This makes it trivial to comply with the GDPR and other privacy legislations. Our service is also easy to learn and navigate, thanks to our intuitive UI and handy AI assistant. If this sounds good to you, feel free to give us a try!\u003C/ContentEditable>\n","Last week [we discussed cookies](https://www.simpleanalytics.com/blog/cookies-101) and their regulation under EU law and mentioned how **non-essential cookies require consent**. These are the sort of cookies that power cookie-based web analytics services such as Google Analytics and Adobe Analytics. Today we will dig more into consent and what it means for web analytics specifically.\n\nLet's dive in!\n\n## A _tl;dr_ on consent and cookies\nBefore we head in, let’s go through a high-level overview of consent and cookies:\n- Web analytics cookies **always need consent** because they are non-seential.\n- GDPR consent is only valid when it **meets specific criteria**: it is _freely given, specific, informed, unambiguous,_ and _possible to withdraw_.\n\nSo: analytics cookies require consent, and this consent needs to meet certain standards. This means that your cookie banner needs to be designed a certain way. But there is more to it, and while most of the rules are uncontroversial, some are hotly debated in the legal community.\n\nLet’s dive in!\n## What does cookie consent look like?\n### Consent is unambiguous\nIn a nutshell, the GDPR’s requirement for unambiguous consent means that only **active, opt-in consent** is valid. There is no such thing as an implicit or opt-out consent under the GDPR.\n\nThe rule of opt-in consent has important consequences for cookie banners. A well designed cookie banner uses **affirmative wording** such as _“I accept cookies”_ or _“I consent to the use of cookies”_. This is different from merely _acknowledging_ or _understanding_ that cookies will be used.\n\nAdditionally, a well-designed website does not write cookies until users **make a choice**. Ignoring a banner or clicking a “close” button to dismiss it never, ever constitutes or implies consent.\n## Consent is specific\nConsent is only valid when given for a specific purpose. This entails that consent must be **granular**: when the same cookies are used for multiple purposes, then you need multiple consents- one for each purpose.\n\nIn practice, the best way to collect granular consent is to **use your web analytics cookies for web analytics only**. This allows you to collect a separate consent for other cookies such as user authentication cookies, and to write essential cookies without user consent (which is absolutely fine under the law).\n\n### Consent is informed\nThis requirement is intuitive: if I don’t know what I am consenting to, then I am not really consenting in any meaningful way. I do not necessarily need to understand all the tiny technicalities about your web analytics, but I do need to understand **the facts that really matter** for my decision: who takes my data, what data they take, for what purpose, and with what potential consequences.\n\nIn practice, this means that a cookie banner should:\n- Tell the user what the cookies are for.\n- Use clear, accessible, accurate language.\n- Tell the user with whom their personal data will be shared. For Google Analytics, this includes Google and its advertising partners.\n\nThis information needs to be concise and in plain English. In practice, it is usually a good idea to deliver the most crucial information through the cookie banner and link to a cookie policy with more in-depth information.\n\n### Consent can be withdrawn\nConsent is revocable. You should allow users to **review their cookie preferences** and easily opt out of any cookies they might have agreed to.\n\nPlease note that the withdrawal of consent sometimes comes with a **request for erasure**. In that scenario, you get a deadline for deleting all the data from the requestor. This means all the web analytics data that relates to their cookies and the unique ID they contain.\n\nMost companies don’t think about this stuff when they set up their web analytics and have no clue what to do when they get a request for erasure. We can’t go into too much depth here, but an organization should, at the very least:\n- **establish a clear procedure** for handling requests\n- ensure it can easily **retrieve and delete data** from individual users. For web analytics, this means being able to filter data points by unique IDs.\n\n### Consent is freely given\nThe GDPR requires every consent to be **freely given**. This is why your hospital cannot collect consent to the use of your data as a requirement to provide health care, and why employers should refrain from having employees sign GDPR consent forms. You have no meaningful choice when witholding consent means dying or losing your job.\n\n## What are the most common issues with consent?\nTwo compliance issues have surfaced lately with web analytics. **Deceptive cookie banners** are found all over the Internet and try to nudge users towards accepting cookies they do not really want, while **cookie walls** require visitors to pay to get rid of cookies.\n\nBoth of these issues are fairly controversial in the privacy community. Let's see what the fuss is all about, and what it means for web analytics\n\n### Deceptive banners\nAccepting cookies is always easy as pie, but rejecting them usually requires you to jump through hoops. This is a deliberate design choice: many banners nudge users into accepting cookies by making the rejection process to be as annoying, confusing and time consuming as possible. Visitors often give in because they don’t have the time or patience to figure their way out of every cookie banner they see.\n\nDeceptive designs look like a good solution for websites. After all, the user clicked “I accept”, so everything should be fine. Right? Not quite. If consent was extorted through deception and exhaustion, then it is neither free nor unambiguous.\n\nThankfully, the European Data Protection Board [took a stance](https://www.simpleanalytics.com/blog/eu-task-force-cracks-down-on-cookie-banners) against deceptive cookie banners. Its stance is not unanimous but is shared by the vast majority of enforcers. We are starting to see [some serious enforcement](https://www.simpleanalytics.com/blog/german-authority-cookie-banners), too.\n\nBottom line: if you _really_ need to use cookie-based analytics, be on the right side of the law and **make your cookies easy to reject**. Make sure that the “reject all” button is clearly visible, clearly worded, and available on the first level of the banner’s interface!\n\n(And yes, this means that many users _will_ reject your cookies.)\n\n### Cookie walls\nSome cookie banners do not include a “reject all cookies” button and offer a different choice instead: users can either accept cookies, or sign up for a paid subscription that allows them to browse the site without cookies. In other words: pay with your money, pay with your data, or leave. These banners are referred to as **cookie walls** and are typically used by digital newspapers.\n\nCookie walls entail a **commodification of personal data** that a part of the privacy community considers undesirable at best and unlawful at worst. Proponents of cookie walls say that publishers cannot provide content for free and need ad revenue to keep up the work. Critics of cookie walls point to contextual advertising as an alternative source of revenue for publishers and observe that a **fundamental right** such as data protection cannot be commodified (they are right, by the way).\n\nIn practice, your mileage with a cookie wall may vary depending on your jurisdiction. For instance, cookie walls are used by many German news outlets because regulators tend to be somewhat lenient on that front.\n\nWe really dislike cookie walls, but if you _really_ want to implement one, it might be prudent to **wait for a while**. Meta took a page from news outlets and implemented a **pay-or-ok** subscription schemes in an attempt to justify its aggressive surveillance-based advertising. European regulators will soon need to take a stance on Meta's approach, and once they do, their position on cookie walls will probably become clearer as well.\n\n(By the way: pay-or-ok is a really big deal for the future on the GDPR! If you are curious about this crucial privacy topic, feel free to check out [our blog](https://www.simpleanalytics.com/blog/meta-subscriptions-under-attack) on Meta subscriptions.)\n\n## Conclusions\nOverall, consent rules for web analytics are fairly stringent in the EU. This creates a problem for cookie-based analytics: strategies that lead to good opt-in rates for cookies, are likely to violate the law. Websites are stuck between a rock and a hard place, as they have to **choose between low opt-in rates or a compliance risk**.\n\nThis is why many companies are moving towards **cookieless analytics** solutions. And we are proud to offer the most privacy-friendly one!\n\nSimple Analytics is the cookieless web analytics solution that **collects no personal data**. This makes it trivial to comply with the GDPR and other privacy legislations. Our service is also easy to learn and navigate, thanks to our intuitive UI and handy AI assistant. If this sounds good to you, feel free to give us a try!",{"data":45},null,2425,"Web Analytics and Consent","GDPR consent is complicated. Here is how it works for web analytics","web-analytics-and-consent","carlo-cilento","2024-04-16T11:51:22.747Z","2025-04-02T13:35:46.291Z",{"en":54,"de":55,"fr":57,"it":59,"es":61,"nl":63},{"slug":49},{"slug":56},"webanalyse-und-zustimmung",{"slug":58},"analyse-du-web-et-consentement",{"slug":60},"analisi-web-e-consenso",{"slug":62},"analitica-web-y-consentimiento",{"slug":64},"webanalyses-en-toestemming"]