What is the single most important field in a consent record?

The notice version is the one most often missing and most often decisive. Without it, you can show a choice was recorded but not what wording, purposes, or vendors the choice referred to, which weakens the record badly in a dispute.

How long should consent records be retained?

Tie the period to the relationship length plus the applicable limitation period for claims in your markets, write it into a retention schedule, and apply deletion across every copy, including warehouse exports and backups, when the period ends.

Does a consent banner log prove tags behaved?

No. The log proves the choice as recorded. Proving behaviour needs a production check that tags fired or stayed silent according to that state. Keep evidence of both, and repeat the behaviour check after tag manager changes.

Should rejected consent be stored with the same care as accepted?

Yes. A recorded refusal, with timestamp and version, is what stops a team from re prompting aggressively or accidentally enabling a purpose later. It also demonstrates that refusal was honoured, which regulators treat as part of valid consent design.

Consent for Push Notifications: The Browser Prompt Is Not the Whole Story

October 31, 2026

Push notification permission is handled by the browser, which tempts sites to treat it as separate from consent. What a fair push opt in looks like, and how withdrawal should work.

Push notifications sit in an awkward corner. The permission dialog belongs to the browser, not to your consent banner, so many sites treat push as a separate world with its own rules and prompt shoppers the moment they land, sometimes before they have seen a single product. A permission granted under pressure, or by accident, is worth very little, and browsers have been tightening the rules on exactly that behaviour.

The pattern that works is not complicated: ask at a moment when the shopper can see a reason, in your own interface first, and only trigger the browser prompt when they have said yes to yours. That two step approach gets called soft opt in, and it respects both the person and the permission system they will be living with afterwards.

Timing is most of the ethics

A prompt on arrival asks for a commitment before any value has been shown, and most shoppers refuse, which trains browsers and people alike to treat your site as noise. Worse, a refused browser prompt is hard to reverse, because the browser will not let you simply ask again and again. A store that fires the prompt carelessly spends its one good chance to ask.

Tie the ask to a moment of intent: tracking an order, waiting for a restock, following a price on an item they just viewed. At those moments the exchange is legible. You get a notification you asked for, about a thing you care about. Response rates at those moments are higher and the permissions last longer, because they were never a mistake the shopper is waiting to undo.

Withdrawal has to be findable

Unsubscribing from push is notoriously awkward, because the control lives in browser or device settings, a place many shoppers cannot find. A site that takes withdrawal seriously explains, on its own pages, in plain steps for each major browser, how to turn notifications off, and honours any account level preference not to send. Burying that guidance is a dark pattern with a settings menu as the hiding place.

Record the push permission alongside other consent choices in your own records: when it was granted, what it was granted for, and what categories the shopper agreed to. Order updates and marketing pushes are different promises. Sending a promotional push to someone who agreed only to delivery updates breaks the specific promise they made, and it is the kind of break people screenshot.

Measure complaints, not just subscribers

A push programme judged only on subscriber count and click rate will drift toward pressure. Add the numbers that show the cost: blocks and unsubscribes per campaign, notification permission revocations, and support contacts mentioning notifications. When a campaign doubles clicks and triples blocks, it did not perform. It spent the audience.

Frequency is the usual culprit. Cap it, in writing, and let the cap bind the campaign team during a sale, which is when caps go to die. An audience that trusts a site to send two useful pushes a week is an asset built over a year. It can be burned in one weekend of hourly sale alerts, and browsers make rebuilding it slow by design.

Frequently asked questions

Is browser push permission separate from cookie consent?

Yes, the browser controls the permission itself. That does not make it exempt from consent principles: ask with a clear reason, record what was agreed, and make withdrawal understandable and honoured.

When is the best moment to ask for push permission?

At a moment of visible intent, such as order tracking, a restock alert, or a price watch. Ask in your own interface first and only show the browser prompt after the shopper agrees, because a refused browser prompt is hard to ask again.

How should shoppers be able to withdraw push consent?

Explain the browser or device steps plainly on your own site, and respect account level preferences immediately on your side. Withdrawal buried in settings menus the shopper cannot find is not a fair withdrawal route.

What metrics keep a push programme honest?

Blocks, unsubscribes, and permission revocations per campaign, alongside clicks and subscribers. A campaign that raises clicks and raises blocks faster is consuming the audience rather than growing it.