How universal consent works, start to finish.
Universal consent means one central record of every yes and no a person gives you, read by every system you run and updated the moment it changes.
Your banner only sees one of those channels. Most companies collect consent well and carry it badly.
Here's a plain walk through what happens when it works, plus the one arrival almost nobody has planned for.
Step 1: Someone answers
They land on your site. Or open your app. Or tick a box on a paper form at your counter. Or reply STOP to a text.
All four are consent events. All four count in law, and only the first one usually gets built properly.
Step 2: The answer goes to one place
Rather than saving into whichever tool caught it, the answer gets written to a single central record.
Stored alongside it: who they are, what they agreed to, when, which channel, and which law applied to them at that moment.
That last field does a lot of quiet work. It's how you answer "was this lawful?" two years later.
Step 3: Everything else gets told
The record pushes the update out. Email tool, CRM, ad accounts, analytics, warehouse.
Push beats pull here. If a system has to ask, there's a window where it's happily acting on an old answer.
A gym chain is a good example. Someone cancels marketing in the app on Saturday. If the front desk system only refreshes on Monday, the reminder text still goes out Sunday morning.
Step 4: They change their mind
They withdraw. The same route runs again, and everything falls into line.
GDPR expects this. Taking consent back has to be as easy as giving it, which in practice means the same number of taps.
The arrival nobody planned for
Now the part that catches teams out.
Some browsers send an opt-out before your page has finished loading. These are called Universal Opt-Out Mechanisms.
Colorado publishes an official list of which ones legally count. Global Privacy Control is the only one on it, and controllers have had to honour it since 1 July 2024.
Ignore that signal and show a banner instead, and the banner won't save you. You asked a question that was already answered.
How to tell if you've got it
Try answering three questions about a real customer, right now, in under a minute.
What did they agree to? When? And which of your systems currently believe something different?
If the third one makes you wince, you don't have universal consent yet. You have a banner and some optimism.
One thing to fix this week
Pick your slowest system and find out how long it takes to hear about a withdrawal.
Not how long it should take. Time it with a real test user. The number is almost always worse than the team's guess, and it's the easiest thing to put in front of a budget holder.
Full detail here: how universal consent works
(Seers AI runs this central record for you, GPC signals included: )

Comments
Post a Comment