Home / Blog / How to explain cookie consent to a non-technical client

How to explain cookie consent to a non-technical client

Skip the acronyms. A cookie banner asks visitors for permission before tracking them, the law requires it for most sites, and you handle the whole thing. Three plain sentences beat a ten-minute lecture on the GDPR every time.

Lead with the plain version

Start here: "Some tools on your website remember things about visitors. The law says visitors have to agree before that happens, so we show them a small banner that asks. You do not have to think about it after we set it up." That covers what a cookie is, what consent is, and what the banner does, in language a busy owner can absorb in ten seconds. Every sentence after this one is detail, and most clients do not need it.

Answer "do we really need this?" once

Clients assume small sites are exempt. They are not. The rule that matters most: it applies based on where visitors are, not how big the business is. A five-page site with Google Analytics and an embedded map has the same obligations as a big one. Frame it as standard practice rather than a special problem: every professional site has one, the way every shop has a lock on the door. That framing also makes the cost feel like maintenance, not an optional extra.

Explain what you handle so they relax

The client's real question is "what do I have to do?" The answer should be as close to nothing as you can honestly make it. Tell them you install the banner, configure what loads before and after consent, write the cookie list, and keep it updated when they add tools. The one thing they must do is tell you before adding new marketing tools, embedded videos, or booking widgets, because those add trackers you need to know about. One responsibility, stated clearly, is easier to follow than a compliance lecture.

Keep the follow-up email short

After the call, send three bullets: what was installed, what the visitor sees, and the one thing you need from them (tell you about new tools). Link the cookie policy page you wrote. Clients who get a short summary stop worrying; clients who get a twelve-page compliance memo forward it to nobody and worry anyway. Your job is to make this boring, because boring means it is handled.

Get a free consent audit of your website

Free consent audit