Job consent-mode-banner-signals-reach-tags · revised 11 October 2026
Make your cookie banner's choices reach your Google tags in the right order
Consent defaults load before any tag, a banner choice updates them, and Tag Assistant shows the same states you agreed with your own policy.
You might be seeing
- Tag Assistant shows an empty Consent tab or tags reading consent before a default was set
- Analytics events are missing in DebugView for visitors who have not accepted
No passwords, keys, card details or admin invites needed to start.
What usually happened
The consent banner and the Google tags are not connected in the right order. Google documents that default consent states must be set before any tag that sends measurement data, that the banner must send an update when the visitor chooses, and that the choice must be stored and re-sent on later pages. A banner that only shows a message does none of this.
Who it’s for: A site owner or marketer with a consent banner already installed who cannot tell whether Google tags actually read its choices.
Usually starts when: The banner is on the site, but tags fire before a choice is made, ignore the choice, or Tag Assistant reports no consent state.
The result: On the live site, Tag Assistant shows consent defaults set to the states you supplied before the first tag, an update to the states in your written accept column after a visitor accepts, the states in your written reject column after a visitor rejects, the stored choice re-sent on a return visit, and the agreed tags behaving as their consent settings say.
Check whether this job fits
This is a technical fit check, not legal advice. Answer without sharing visitor data.
Checks you can run yourself
Look at the consent state in Tag Assistant
Open Tag Assistant on your site and look at the Consent tab for the earliest consent event before you touch the banner.
Look for: An empty tab means no consent signals are sent. An error saying consent was set too late, after a tag had already fired, means the order is wrong.
What you get
- The corrected consent set-up prepared in a workspace for your approval
- Tag Assistant screenshots for first visit, accept, reject and a return visit
- A one-page table of each tag, its consent settings and what it did in each test
Included
- One site, one banner or consent tool already installed, one written table of the states you supply for the four Google consent types: default, after accept and after reject
- Check the order: default first, then the Google tag or Tag Manager, then the banner, then updates
- Connect the banner to the four Google consent types through its Tag Manager template or the documented gtag commands
- Set the consent settings on the tags you name and test accept, reject and return-visit paths
Not included
- Legal advice, deciding what your default states should be, or whether your banner meets any law or regulation
- Writing banner text, choosing a consent tool or auditing cookies
- Region-specific rules for more than the single default you supply, which are quoted separately
- Third-party tags whose vendor does not read Google consent signals
- Any promise about modelled data, conversions or ad performance
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
On a first visit with no choice made, Tag Assistant shows consent defaults for all four Google consent types, set to your agreed default states, before any other tag fires.
Evidence: Tag Assistant screenshot of the earliest Consent event and its API call.
After accepting all, the most recent Consent event shows each type at the state in your written accept column; after rejecting, it shows each type at the state in your written reject column, including any type whose default was granted but whose reject state is denied.
Evidence: Tag Assistant screenshots of the update event for both paths, next to your written table.
On a second page load in the same browser after accepting, and again after rejecting, Tag Assistant shows the default consent event followed by an update to the stored choice, without the banner being used again.
Evidence: Tag Assistant Consent tab screenshots (On-page Default and On-page Update) for the return visit after each choice.
Each named tag fires or is blocked in Tag Assistant exactly as its consent settings state for first visit, accept, reject and return visit.
Evidence: The tag table with a screenshot of the Tags tab for each path.
Sign-off. You check the screenshots against your written policy table, sign off in writing and publish yourself. Payment follows sign-off.
If it fails. If any test path fails, you do not pay for this fixed scope. If the consent tool cannot send updates, we explain what is needed and stop or re-quote in writing.
When it fits, and when we stop
It fits when
- A consent banner or consent management tool is already installed and you can tell us, in writing, the default, accept and reject states your own policy requires
- The site uses Google Tag Manager or the Google tag, with scoped access available
- A test browser can accept and reject cookies on the live site or staging copy
We stop and tell you if
- No one can state the default, accept and reject states you want; we do not choose them for you
- The consent tool cannot send consent updates and you will not replace it
- The request is really a legal review of the banner
What could go wrong
Everything is a named Tag Manager version or a listed site-code change, so you can republish the earlier version or remove the change.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A wrong default state silently collects or blocks more data than your policy intends. | The states are supplied by you in writing, and acceptance compares Tag Assistant to that table. |
| The tests make real visitors' data collection change. | Changes are prepared in a workspace and tested before publication. |
A separate reviewer repeats the four test paths and checks that the states match the ones you supplied. The decision about what the states should be stays with you.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the default, accept and reject states, the tags in scope and the access route in writing
- Record the current order of consent defaults, tags and banner in Tag Assistant
- Correct the order and connect the banner to the four consent types
- Set consent checks on the named tags and test first visit, accept, reject and return visit
- Independent review of the screenshots and the tag table
- Hand over a named version, saved with the Approve role, for your person to publish
This is a one-off job, not a subscription or emergency cover. We confirm eligibility, the price, a start window and a delivery date before you accept. Work starts only after the agreed inputs and the least access the job needs are in place. Fees charged by Google, Meta, your host or any tool you use are not included. No charge or booking is created by an enquiry.
Need to keep it working?
A standing monthly check can repeat the four test paths after site or banner changes.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Google's consent mode guide and Tag Assistant troubleshooting guide describe the order and the checks, so a developer can do this in-house. developers.google.com
- Many consent tools ship a Tag Manager template; ask yours whether it supports Google consent mode.
Questions
Does this make my site compliant?
No. This is technical wiring. Whether your defaults and banner satisfy any rule is a legal question for you and your adviser.
Why do my own test events not show in DebugView?
Google notes that events will not appear if consent mode is active and the user has not consented to analytics cookies, so tests are run on the accept path.
Send an enquiry
Send us
- The name of the consent tool, if any, and whether you use Tag Manager
- For each of the four Google consent types, the state you want before a visitor chooses, after accept and after reject, as set by your own policy
- No logins and no visitor data.
Later, once you agree
- Approve access to the Tag Manager container (Google describes Approve as able to create versions and make edits but not publish) and, if the tool has a settings panel, a scoped admin role, granted to the identity we agree with you before work starts
- The list of tags to cover and the vendors you know do not read Google consent
- Your named person who will publish
You own the website, the Google and Meta accounts, the tag manager container and all the data. We ask for the lowest role that lets us do the job. Before any work starts we agree with you in writing which identity receives that role; you grant it and can remove it at any time. We never ask for your passwords. You keep the right to publish: we prepare changes and you publish them.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “consent-mode-banner-signals-reach-tags” as the subject.