Google is developing two different ways to reduce friction in advertising operations: stronger conversion inputs for advertisers and conversational analysis for publishers. One beta supplements website conversion actions with backend records; the other brings a Gemini-powered assistant into Google Ad Manager.
The tools do not form a single workflow, and the supplied reports do not describe an integration between them. Together, however, they illustrate a broader operating model: improve the evidence used to judge performance, then make that evidence easier to investigate and act on.
Two tools address different parts of the advertising cycle
The distinction between the products matters. CrushPress.AI reported that Google’s supplemental conversion data beta is intended for advertisers using eligible website conversion actions in Google Ads. Ask Ad Manager, meanwhile, was reported as a conversational assistant for publishers working in Google Ad Manager.
| Area | Supplemental conversion data | Ask Ad Manager |
|---|---|---|
| Primary user | Advertisers measuring website conversions | Publishers managing advertising inventory and delivery |
| Core problem | Conversions that website tags may not capture | Time spent building reports, investigating delivery and navigating the platform |
| Main input | Backend transaction records from systems such as CRMs, order databases and ecommerce platforms | Natural-language questions evaluated against the publisher’s Ad Manager data |
| Reported outcome | A more complete conversion action for measurement and optimization | Tailored answers, reports, recommendations and platform guidance |
| Important boundary | Enhances rather than replaces website tagging | Assists analysis and operations rather than repairing conversion collection |
This comparison prevents a common category error. Better conversion capture cannot diagnose every publisher delivery issue, while a conversational reporting interface cannot recover a transaction that never reached an eligible conversion action. Each tool works on a different constraint.
Supplemental data strengthens the measurement foundation
According to CrushPress.AI’s report, the Google Ads beta lets an advertiser attach an additional data source to an existing website conversion action through Google Ads Data Manager or the Data Manager API. Backend conversion records are combined with signals collected by Google tags, allowing the same conversion action to support campaign measurement and optimization.
The reported purpose is recovery, not replacement. Browser restrictions, privacy settings or ad blockers can prevent some tag-based signals from being captured. Transactional systems may retain evidence of those completed outcomes, so supplying that evidence can make measurement more resilient and give automated bidding a more complete input set.
That benefit depends on record quality. The report states that every upload must include a transaction ID and the conversion date and time, plus at least one attribution identifier such as hashed customer data or a Google click identifier. Google reportedly uses transaction IDs to deduplicate tag and backend records within the same conversion action.
The reported eligibility limits are equally significant. The beta applies to website conversion actions implemented with Google tags or Google Tag Manager; Google Analytics imports and URL-based conversion actions are excluded. Google also advises adding the supplemental source to the existing action instead of creating another action, which could introduce double-counting across campaign goals. Prompt uploads and conversion values formatted consistently with the tag’s currency were also reported as recommended practices.
Ask Ad Manager compresses the path from question to diagnosis
Ask Ad Manager tackles a different bottleneck: extracting usable answers from a complex publisher platform. CrushPress.AI described it as a Gemini-powered beta that lets Google Ad Manager users ask questions in ordinary language and receive responses grounded in their own Ad Manager data.
The reported capabilities span three recurring tasks. The assistant can investigate why line items are underdelivering and suggest possible causes or next steps. It can produce requested metrics, benchmarks and customized reports without requiring the user to construct each report manually. It can also direct a user to relevant Ad Manager pages while applying filters and settings derived from the conversation.
The practical shift is from interface-led work to question-led work. Instead of beginning with menus, report fields and filters, a publisher can begin with the business or delivery question. The assistant then helps translate that question into platform activity. This may reduce operational effort, but the source does not establish that every answer or recommendation will be correct. As a general operating discipline, consequential findings should still be checked against the underlying report and campaign configuration.
The report also attributes a wider roadmap to Google. Planned additions include developer tools such as REST APIs and an MCP server, along with specialized agents that could help publishers and agencies explore inventory, negotiate deals and execute campaigns. Those items are forward-looking plans, not capabilities established by the reported beta.
Key takeaways
- The conversion beta improves the data entering an eligible Google Ads conversion action; Ask Ad Manager improves how publishers interrogate and use their Ad Manager data.
- Supplemental conversion data depends on reliable transaction IDs, timestamps, attribution identifiers and consistent values, as well as correct conversion-action configuration.
- Deduplication is central to the measurement design because tag and backend systems may describe the same transaction.
- Conversational analysis can shorten reporting and troubleshooting work, but important recommendations still warrant validation against source data and settings.
- Both features were reported as betas, while the APIs, MCP server and specialized Ad Manager agents remain part of Google’s stated roadmap.
A practical evaluation framework for advertising teams
Teams evaluating the conversion beta should first determine whether their conversion actions use an eligible implementation. They can then assess whether backend systems retain the required identifiers, timestamps and values, and whether transaction IDs remain consistent across the tag and transactional record. This is not merely an integration exercise: weak identity matching, inconsistent currency formatting or duplicate campaign goals can undermine the additional data.
Publishers assessing Ask Ad Manager should judge it against concrete operational questions. Useful tests include whether it can reproduce a trusted report, identify a known delivery issue and navigate to the correct filtered view. The relevant measure is not how fluent the conversation sounds, but whether it reduces investigation time without obscuring the evidence behind an answer.
Across both products, data discipline remains the connecting requirement. More complete records can improve the basis for optimization, while a conversational layer can make platform data more accessible. Neither advantage removes the need for clear conversion definitions, dependable identifiers, reviewable reports and accountable decisions.
If Google’s reported direction continues, advertising work will increasingly combine first-party data connections with agent-assisted operations. The teams best positioned to benefit will be those that treat reliable data and human verification as prerequisites for automation, not as cleanup work after deployment.
References
- CrushPress.AI — Unlock Enhanced Ad Performance with Google’s New Conversion Beta
- CrushPress.AI — Discover the Power of Google’s New AI Agent for Ad Manager
Leave a Reply