Consent banner

A consent banner is the panel asking a visitor whether tracking and advertising scripts may run before those scripts run. It is the mechanism by which your tracking setup obtains permission, and the reason most of them fail is not the wording. It is that the scripts have already loaded by the time the panel appears.

In short

• The banner has to appear before the scripts, not alongside them.
• Refusing has to be as easy as accepting, or the consent is not freely given.
• What the visitor chose has to be recorded, or it cannot be demonstrated later.
• Declining reduces your reporting totals without making the direction useless.

What the banner is actually for

The banner exists to turn an assumption into a decision.

Analytics, advertising and remarketing scripts collect information about identifiable people. Loading them the moment a page opens takes permission that was never asked for. The banner asks, and the asking has to happen at a point where the answer can still change what loads, which is before anything non-essential runs.

That timing is the whole design. A banner that appears while the tags are already firing is a notification of something that happened, and it is surprisingly common, because the usual way a banner gets added is by installing one on top of a site whose tags were placed years earlier by somebody else.

It is also why this is a development question wearing the clothes of a design one. Choosing a banner tool takes an afternoon. Making certain that nothing fires before the tool has an answer means going through every tag on the site, finding out how each one was added and by whom, and moving the ones that were hard coded into the template. That is the part skipped when a banner is added in a hurry, and it is the only part that changes what actually happens in the visitor’s browser.

What has to be true for the consent to count

Four properties separate consent from decoration.

• It is asked before the scripts run. Non-essential tags stay blocked until a choice is made.
• Refusing is as easy as accepting. Two buttons of equal weight, in the same place. A refusal buried in a settings panel is not a real option.
• It is specific. The visitor can tell what they are agreeing to, and categories such as analytics and advertising are separated instead of bundled into one switch.
• It is recorded. A timestamp, the version of the notice shown, and the choice made, stored somewhere you can retrieve it.

A fifth property is often forgotten: consent has to be withdrawable. Somebody who accepted in March should be able to change their mind in July without clearing their browser, which usually means a small permanent link in the footer.

Where the Philippine rules sit

The Philippines has the Data Privacy Act, administered by the National Privacy Commission, and it expects consent to be freely given, specific and informed. Tracking for advertising falls inside it, which is why retargeting setups need the mechanism to be real, not presentational.

Two consequences follow that people miss. Consent has to be asked for before the scripts run rather than assumed from a notice somebody may scroll past. And the rights involved go further than switching tracking off, including the right to ask what you hold and to have it removed, which means somebody at the business has to be able to answer that request when it arrives.

If you also sell to customers in Europe, GDPR applies to those customers and it is stricter. Building to the stricter standard once is usually simpler than maintaining two behaviours.

None of this requires a legal department. It requires knowing which scripts your site loads, being able to hold them until somebody answers, and publishing a privacy policy that describes what you actually do, not what a template said. Most sites fail on the first of the three, because nobody has looked at the tag list in years and at least one of the entries was added for a campaign that finished.

What it does to your numbers

Expect the totals to fall, and expect the fall to be uneven.

Visitors who decline are not recorded, so Google Analytics 4 reports fewer sessions than the server saw. The shortfall is not distributed evenly. It varies by device, by browser, by traffic source and by the kind of page somebody landed on, which means the shape of your reports shifts slightly as well as the size.

None of that makes the reporting useless. It makes it a sample and not a census, and the correct response is the one that was always correct: compare a period against your own earlier periods, on the same setup, and stop treating any single total as a count of human beings. Google and Meta both now expect a consent signal to be passed to them, and setups that never send one increasingly report less than setups that ask properly and pass the answer along.

The faults that make a banner decorative

Five appear again and again, and each is fixable in an afternoon.

• The tags fire first. The banner is installed, the choice is stored, and nothing is actually blocked while the question is on screen.
• There is only an accept button. Sometimes with a small close icon, which most people read as agreement.
• Nothing is recorded. The banner remembers not to ask again and stores no evidence of what was chosen.
• The text is borrowed. Legal language describing another country’s regime, naming authorities that have no bearing on the visitor reading it.
• There is no way back. A visitor who accepted once has no route to change their answer, so withdrawal is theoretically available and practically not.

Test yours the way an auditor would. Open the site in a fresh browser, decline, and check whether the analytics and advertising requests still leave your browser. That single check settles whether the banner is doing anything.

Words you will hear

• Cookie. A small file a site stores in a browser, often used to recognise a returning visitor.
• Essential cookies. The ones a site cannot function without, such as a basket or a login, which do not require consent.
• Consent mode. A Google mechanism for passing the visitor’s choice to Google tags so they adjust their behaviour instead of disappearing.
• Consent record. The stored evidence of what a visitor chose and when.
• Withdrawal. The route by which somebody changes an answer they already gave.

A consent banner is one of the few things on a website that is either working or theatre, with very little in between. Block the tags until the answer arrives, give refusal the same prominence as agreement, keep the record, and accept that your reporting is now describing the people who agreed to be described.