LanderKit

Templates written in French — fully translatable in minutes

Cookie banners on a landing page: staying GDPR-compliant without wrecking conversion

Published on 23 July 2026 · 7 min read

A poorly designed cookie banner costs you twice: once in conversion, if its design annoys visitors or slows down access to your offer, and once in legal risk, if the "reject" button is smaller or better hidden than the "accept" button. France's data protection authority, the CNIL, formally notified about twenty organizations in 2025 on this exact ground, for roughly €32 million in combined penalties (CNIL source). Good news if you're selling an offer on a single-page landing page: what the research shows about consent banner design broadly lines up with compliance — it's the complexity of the choice on offer, not the mere presence of a banner, that drives visitors away.

What French and EU rules actually require from a cookie banner in 2026

The core rule, hammered home by the CNIL across several enforcement campaigns, fits in one sentence: rejecting cookies must be as easy as accepting them. In practice, the first layer of the banner must show a "Reject all" button at the same visual level and with the same look as the "Accept all" button — not a discreet text link tucked in a corner while "Accept" gets a bright, prominent button. No checkbox can be pre-ticked, non-essential cookies (non-anonymized analytics, advertising, social media) cannot be dropped before an explicit choice is made, and a "Customize" link must give access to the detail of purposes without forcing the visitor to dig through it just to say no. On a landing page that only runs for a few weeks around a single offer, the risk isn't just the fine: a complaint or audit can freeze a campaign mid-launch.

What the research shows about consent banner design

A study by Nouwens, Liccardi, Veale, Karger and Kagal, published in 2020 at the CHI conference, analyzed the banners of the five most-used consent management platforms across 10,000 UK websites, then ran a controlled experiment with 40 participants to measure the effect of eight different designs (see the study on Google Scholar). Three findings matter for a landing page: notification style — bottom banner versus a full-screen blocking overlay — had no measurable effect on the consent rate; removing the reject option from the first layer pushed the acceptance rate up by 22 to 23 percentage points (a practice that's now illegal, but which confirms that friction comes from the choice offered, not the format); and presenting detailed, granular settings at the first layer, instead of a simple accept/reject choice, dropped the consent rate by 8 to 20 percentage points, simply because the decision becomes more cognitively costly.

A study by Utz, Degeling, Fahl, Schaub and Holz, published in 2019 at the ACM CCS conference, tested the position, choice type, and wording of a consent banner under real conditions on a high-traffic German website, with more than 80,000 unique visitors (see the study on Google Scholar). The result lines up with the previous study: banner position (bottom of screen rather than center screen or a blocking overlay) and the presence of a clear choice influenced behavior more than the banner's visual style itself. In other words, both studies point the same way: a discreet bottom banner with a simple binary choice costs no more conversion than an aggressive one — and it's the one that's compliant.

How to design a compliant banner that doesn't penalize your landing page

  1. A bottom banner, never a full-screen blocking overlay — both studies cited show the format doesn't affect the consent rate, so pick the one that doesn't cut into the message match between the ad that generated the click and your landing page headline. A visitor who has to clear a pop-up before seeing your hero has already lost a few precious seconds.
  2. Two buttons of equal visual weight — "Accept all" and "Reject all" at the same size, the same background color or contrast. This is the CNIL's requirement, and per the Nouwens et al. study, this choice carries no measurable downside on the overall acceptance rate compared to a banner that visually favors acceptance.
  3. A binary choice at the first layer, not a list of per-purpose toggles — save category detail (analytics, advertising, social media) for a second layer reachable via "Customize." The Nouwens et al. study puts the consent loss from imposing granular settings upfront at 8 to 20 percentage points.
  4. A technically lightweight CMP — some consent management solutions add several hundred kilobytes of script before the page's first meaningful render, which directly hurts your page load speed. Choose one that loads asynchronously and doesn't block the rest of the page from rendering.
  5. A choice that holds for the whole session — on a single-page landing page where the visitor scrolls down to the form, don't re-show the banner on every interaction or anchor change: that adds needless friction right before the step where you most need a smooth flow, like the contact form.

What you should never do

  • Pre-tick consent checkboxes for non-essential cookies — illegal, and one of the most common grounds for CNIL formal notices.
  • Hide the "reject" button behind a discreet text link while "accept" gets a prominent colored button — this is exactly the design the Nouwens et al. study measured as artificially inflating the acceptance rate, and exactly what the CNIL sanctions.
  • Block page scrolling until the visitor makes a choice, when the only real goal is to force a click on "accept" rather than obtain genuinely free consent.
  • Re-show the banner on every page view of a multi-page site without remembering the previous choice — friction that adds no compliance benefit whatsoever.

One reassuring point if you're launching an offer: on a landing page that only collects strictly necessary cookies (site function, cart, session) and an analytics tool exempted by the CNIL (like Matomo in a compliant configuration), no consent banner is legally required — see our guide on GDPR compliance for your form for the data-collection side of things. The banner only becomes mandatory once you add an advertising pixel, a non-exempt analytics tool, or a social media plugin.

Our 10 LanderKit templates (€89 each, €229 for the full pack) ship without unnecessary third-party scripts by default, so you start from a lightweight base: add only the consent and analytics tool you actually need, without needlessly weighing down a SaaS waitlist page or an e-commerce product page.

FAQ

Frequently asked questions

Does a cookie banner really lower a landing page's conversion rate?

According to two studies (Nouwens et al., 2020, CHI; Utz et al., 2019, ACM CCS), banner format — a bottom banner versus a full-screen blocking overlay — has no measurable effect on visitor behavior. What actually loses consent is the complexity of the choice presented (detailed settings imposed upfront), not the banner's mere presence.

Does the "Reject all" button need to look the same as "Accept all"?

Yes, that's been a CNIL requirement across several enforcement campaigns: both buttons must sit at the same visual level, with the same look. The CNIL sanctioned about twenty organizations in 2025 on this exact ground, for roughly €32 million combined.

Does every landing page need a cookie banner?

No. If the page only sets strictly necessary cookies (site function, cart, session) and an analytics tool exempted by the CNIL, no banner is legally required. It becomes mandatory as soon as you add an advertising pixel, a non-exempt analytics tool, or a social media plugin.

Is a bottom banner better than a full-screen blocking overlay?

A bottom banner, based on the available research. Both formats have an equivalent effect on the consent rate, but a blocking overlay delays access to your landing page's headline and offer, which hurts message match with the ad that brought the visitor there.

Does a consent management platform (CMP) slow down page load?

It depends on the solution: some CMPs add several hundred kilobytes of script before the first meaningful render. Favor an asynchronous load that doesn't block the rest of the page from rendering, especially the hero section.

Read next

Related articles