A Consent Mode v2 audit that records what every tag does in every consent state.

Usually one of three things, and they are separated by testing rather than by reading the CMP dashboard. Ordering: the default consent call lands after the first measurement tag, so that tag runs in an undefined state and the platform discards or misclassifies those hits. Signal mapping: the CMP handles only analytics_storage and ad_storage. If a denied default was declared for the two v2 signals and no update ever lifts them, you have a permanent denial nobody chose, and the ad features that depend on those signals stop. If the two are never sent at all, the tag runs on its own default rather than on the visitor's answer, so the state the tag is in is not the state the banner recorded. Gating: tags that were never wired to consent keep firing regardless. All three look the same in a reporting dashboard. The audit reproduces each state and reports which one you have.

No. This is measurement work, not legal advice. The audit describes what your tags do in each consent state, where signals are missing or contradictory, and what that costs you in data. It does not tell you which consent categories your business is required to collect, whether your banner design meets any regulator's standard, or how your privacy policy should read. Those are questions for your legal counsel. Where we find behavior that looks like a risk, such as tags firing after a rejection, we flag it as a finding for your counsel to assess.

It depends entirely on your traffic mix, your banner and your markets, so any consent loss rate quoted at you before anyone has looked at your data is guesswork. What is measurable is your own split. The audit reports your actual accept, reject and no choice rates from live data, then shows what each state currently produces in GA4 and in your ad platforms. That gives you a real figure for your site rather than an industry average. It also separates the part of the apparent consent loss that is genuinely consent from the part that is an implementation fault, because the second part is recoverable without asking a single additional visitor to accept.

Viewer or Analyst on GA4, read access to the GTM container, and read-only on Google Ads and Meta Events Manager. You get an exact checklist after booking; most teams grant everything in about 10 minutes. Publish access to GTM is only needed if you want us to deploy the fixes, and you can keep that gated behind your own approval.

No. All fixes are built in a separate GTM workspace, tested against live behavior, and validated before publishing. Nothing goes live without your explicit sign-off, and every change is documented so it can be rolled back in minutes.

Any site running GA4 and Google Tag Manager: Shopify, WooCommerce, BigCommerce, Magento, Webflow, WordPress and custom builds, for both ecommerce and lead generation. Server-side GTM and Meta Conversions API setups are part of the review, and if you don't have them yet the report scopes exactly what they would recover.

Then the guarantee applies: fewer than five fixable gaps and the audit costs nothing. You keep the report either way, which is useful proof for your team, your agency or your investors that the numbers hold.

Yes, and quietly. White-label audits with your brand on the report and our delivery underneath, at partner pricing for volume. Mention it on the call and we'll walk through how the handoff works.

The report ends with a prioritized backlog. Take it to your own developers, have us quote it as a fixed project with your $900 credited in full, or put the account on a monthly maintenance plan so tracking stays verified release after release. No obligation on any path.