Few visitors accept cookies and Google Ads shows a fraction of your leads: what should you do, and what should you not?
Short answer
Compare with real leads, use Consent Mode and enhanced conversions, record outcomes in your own systems and keep the banner fair.
Measure the gap against real leads, switch on the features that fill part of it legitimately, and do not solve it by making refusal hard. A banner designed to push people into accepting can create legal risk and is the wrong fix for a measurement problem.
First, confirm the size of the gap. Count real leads in your CRM or inbox for a week and compare with what Google Ads reports. If your account shows a third of your leads, that is the size of the blind spot.
Second, use what Google offers for the visitors who decline. Consent Mode lets Google tags adjust to the choice, and in advanced mode Google can model some of the missing conversions. Enhanced conversions use hashed form details, collected with the visitor's consent where required. Check Google's current documentation for what each does and requires.
Third, record outcomes outside the browser. Leads that arrive by phone, form or booking can be recorded in your own systems and sent back as offline conversions with the click ID or hashed details, within the rules for what you may send. This does not depend on cookie acceptance in the same way.
Fourth, check where the visitors are. Rules differ by region. If your business is local and your audience is in a place with different rules, your adviser may recommend a different banner type for each region. Do not copy what another business does without checking.
Fifth, make the banner clear and fair. Equal prominence for accept and decline, plain wording, no pre-ticked boxes. Clear design can improve acceptance honestly, but pushing people with tricks can backfire with regulators and with trust.
Sixth, report honestly. Tell whoever reads the numbers that the platform shows a sample, and use your own lead counts as the reference. Optimising on a partial sample is fine if you know it is partial.
A made-up example, invented for illustration: a roofer sees 12 leads a week in Google Ads and 30 in the inbox. After adding enhanced conversions and sending booked jobs back from the CRM, reported conversions rise, and the roofer judges by inbox and bookings, not the dashboard.
DataCops serves the banner from your own domain with Google Consent Mode v2 on by default, sends the sale from your CRM to Google Ads with the click ID or hashed details, and logs what was skipped for declined visitors. It does not count people who said no, which is the point.
What share of your real leads does Google Ads show today?
DataCops in short
For this question: DataCops serves the banner from your own domain with Consent Mode v2 on by default and sends the sale from your CRM to Google Ads, logging what was skipped for declined visitors.
DataCops is a tool whose first-party consent manager, built on IAB TCF v2.2 with Google Consent Mode v2 on by default, is served from your own domain so blockers are less likely to stop it, and which sits in one script with first-party analytics, a bot verdict on every visit and server-side conversions that skip web events marked as declined.
How DataCops does it
- A banner from your own domain. TCF 2.2, with Google Consent Mode v2 on by default: all four signals start denied and update when the visitor chooses.
- The choice is checked again on the server. DataCops skips web events marked as declined before every send, and logs the skip.
- Shown where the law asks. EU, EEA, UK and Swiss visitors get an opt-in gate; elsewhere collection runs by default.
- One script. First-party analytics (a GA4 alternative), the consent manager and server-side conversions share one script and one DNS record.
- A log of every send. A delivery log row per conversion, sent, held, skipped or failed.
Best for: advertisers with EU, UK or Swiss traffic who want a consent banner that loads reliably, and consent, analytics and ad conversions in one script.
Ads Warmup: tell the ads who pays
Ads Warmup, DataCops' flagship feature, sends customers you already have to Meta, Google Ads and TikTok before a new campaign spends: upload a CSV (only email is required, up to 20,000 rows), see a 0 to 10 match score per person, pick the event, and send. Rows are dated when you send, and Google Ads credits only people who clicked a Google ad. Preview is free; sending needs a paid plan. Check your own consent basis for the list first. See Ads Warmup.
Ways to do this job
| Option | Best for |
|---|---|
| DataCops | Consent, analytics and server-side conversions in one script |
| A standalone consent platform | Banners and consent records, nothing else |
| Consent Mode in Google Tag Manager | Passing consent state to Google tags, if you build it yourself |
When not to use DataCops
- You need a legal opinion. DataCops gives you a banner and a record. It is not legal advice and does not make you compliant; you decide your consent basis.
- You only need a banner and run no ads. A basic consent banner is enough if you run no ads and no conversions.
Sources and further reading
More on this: first-party consent manager, and the complete guide to offline conversion tracking.
Not legal advice. Your adviser decides which banner type fits each region.