Google's Rethink ROI briefing for lead gen: what changed and what to do about it
Google ran its Rethink ROI event in New York for advertisers with lead generation goals, and the Ads Decoded episode recorded there is the clearest summary yet of what Google now expects from a lead gen account. Two product specialists, one on first-party data and one on conversion solutions, walked through the changes. This is what they said, what it means, and what we are doing about it in the accounts we manage.
The message underneath the product names
Strip out the product names and the episode says one thing. A Google tag on the site used to be enough. It is not any more. Google wants more of your first-party data, it wants it arriving through fewer doors, and it wants you bidding on the conversion that actually matters to the business rather than the form fill that is easy to measure.
That is the position we have held for a while. Google's bidding does the buying. The work is in what you feed it and whether you check the result. Nothing in the episode contradicts that; it hands Google's own weight to it.
The products announced or restated fall into four groups.
1. Tagging: one interface, visual event setup, and Tag Gateway
The Google tag and Google Tag Manager now share one management surface, so Ads and Analytics settings are handled in one place. Visual event tagging lets a marketer click through the site and mark events without writing code.
Google's framing is that this frees the marketer from waiting a quarter for IT. That is true, and it is also how tagging hygiene gets lost. If everyone in the company can create a conversion event by clicking on a button, someone has to own the naming, keep a change log and audit the container on a schedule. The presenters said as much. We would go further: a conversion event that nobody can explain should be removed, because Smart Bidding will optimise to it whether or not it means anything.
Google Tag Gateway is the substantive change. Today the tag loads from a Google domain, so the browser sees a third-party script and privacy tooling increasingly treats it as such. Tag Gateway serves the tag from your own domain via your CDN or hosting platform. Google's claim in the episode is that this recovers materially more observed conversions, with a figure of fourteen percent mentioned as the example to put in front of a board. Treat that as Google's number. The mechanism is sound and the setup is a toggle on Cloudflare and a guided flow on most managed platforms, so for most accounts it is the cheapest data improvement available this quarter.
2. Data Manager: the one door, with row-level diagnostics
Google admitted it had a "too many doors" problem. Offline conversion imports, the enhanced conversions for leads API, customer match uploads and Analytics imports each had their own connection. Data Manager is the replacement: one place inside Ads, and shortly Analytics and Display and Video 360, with off-the-shelf connectors to CRMs and to BigQuery, AWS and Snowflake. Upload once and use the same data for measurement and for audiences.
The part that matters operationally is diagnostics. Until now a failed upload told you there was a hashing or formatting problem somewhere. Data Manager now shows the failing rows. Anyone who has debugged an enhanced conversions match rate by exporting a CSV and squinting at email formats will understand why this is the most useful thing in the episode.
Google also said that data sent through Tag Gateway or Data Manager passes through trusted execution environments, and that pre-encrypting identifiers can raise match rates. That is a privacy improvement you get without doing anything, and a match rate improvement you get by doing a little.
3. Enhanced conversions, merged
Enhanced conversions for web and enhanced conversions for leads have been two separate setups with two sets of documentation, and advertisers routinely picked the wrong one. They are being merged into one implementation, available through the tag, the API, or both. Google's advice is to use both channels, because each catches conversions the other misses. Post-adoption, the interface shows the uplift attributed to enhanced conversions for your own account.
4. Bidding and lead quality: journey-aware bidding and lead intent score
Two items are aimed squarely at the lead gen problem of sparse data.
Journey-aware bidding, in beta for Search with Target CPA, uses the shallow conversion, the form fill, as a signal towards the deep one, the closed sale, instead of treating them as unrelated events. It needs no action, but it only applies if you are already bidding on a lower-funnel conversion imported from your CRM. If your account bids on form fills alone, there is no journey for it to be aware of.
Lead intent score, in pilot, assigns each lead a high, medium or low intent rating as it arrives, using Google's signed-in account signals. It is explicitly not used in bidding. It is a prioritisation hint for the sales team.
The honest reading: this is Google offering to close the gap between what lead gen advertisers measure and what they sell, provided the advertiser sends the sale data back. The presenters were direct that the common patterns of "we just send offline conversions" and "offline is too hard so we bid on the form" are both wrong. Send both. Bid on the one that means money.
What we are doing now
These are the changes going into every lead gen account Fire Pixel manages, in this order.
- Tag health audit on a fixed cadence. Every conversion action gets a named owner, a definition and a last-verified date. Anything unexplained is paused.
- Tag Gateway where the hosting allows it. Cloudflare sites first, then managed platforms with guided setup. Observed conversion counts are recorded before and after, per account, so the uplift is ours rather than Google's.
- Enhanced conversions on every lead form, through both tag and API where a CRM feed exists. Match rate is checked in the diagnostics view, not assumed.
- Legacy offline conversion uploads moved to Data Manager. The row-level errors are the reason. A failed hash on a Tuesday is now a fixable line item rather than a mystery on Friday.
- CRM outcomes as the primary bidding conversion wherever volume supports it, so journey-aware bidding has something to work with. Where volume is too thin, the form stays primary and the CRM outcome is imported as a secondary while it accumulates. This is the same logic as the CRM feedback loop.
- Lead intent score used for triage, not truth. When it reaches an account we manage, it goes to the sales team as a call-order hint. The value we send back to Google still comes from the CRM and from unit economics, not from Google's own estimate of intent.
What lead gen companies need to do
If you run Google Ads for leads, whether with us or not, this is the list.
Decide what a conversion is worth before touching any of this. Every product in the episode is a better pipe. A better pipe carrying a form fill valued at nothing still optimises towards nothing. Contribution per sale multiplied by close rate, per lead type, is the number that has to exist first.
Get your CRM outcomes back to Google. This is the change Google is building everything around. Marketing qualified, sales qualified and closed. If the CRM has a Data Manager connector, use it. If it does not, a scheduled export to a sheet or a warehouse is enough to start. Do not wait for the complete dataset; Google's own advice is to start sending what you have and enrich it.
Move the tag to your own domain. Ask whoever runs your hosting or CDN whether Tag Gateway is available. On Cloudflare it is a setting. It is the lowest-effort, highest-return item on the list.
Give tagging an owner. With visual event setup, anyone in marketing can create a conversion. Someone has to be accountable for the container, and the account should be audited monthly. If you want a quick outside view of what your public pages are currently sending, the signal scan checks the parts that are visible.
Stage it, and measure each stage. Crawl, walk, run was said several times in the episode, and it is right. Tag health, then Tag Gateway, then enhanced conversions, then CRM data, then bidding on it. Record the observed conversion count and cost per sale at each step so that the next step can be justified with your numbers.
What to be cautious about
Every item here routes more of your first-party data through Google. That is the price of playing the auction well, and the privacy controls described are real, but the consent basis for sending hashed customer data should be checked with whoever owns compliance before the pipe is opened.
The uplift figures are Google's. The interface will show you an uplift number for your account after adoption; that number is calculated by the company selling the media. Reconcile it against your own CRM and your own bank account. That is the whole job: the machine bids, and someone has to verify the inputs.
FAQ
Is Google Tag Gateway worth doing?
Yes, if your site sits behind a CDN or platform that supports it. It serves the Google tag from your own domain, so browsers and privacy tools treat it as first-party and more conversions get observed. Google quotes an uplift figure; treat that as their number, not yours, and measure it.
Should we bid on the lead intent score?
You cannot. Google has said it is not used in bidding. It is a high, medium or low hint for the sales team on which leads to call first. Your CRM outcome remains the signal that should go back to Google.
Do we need to do all of this at once?
No, and Google's own advice is to stage it. Fix tag health first, then Tag Gateway, then enhanced conversions, then move CRM outcomes through Data Manager. Each step should be measured before the next.