Your call-conversion upload succeeded. Did the records actually work?
How to brief a reliable call-measurement handoff after Google’s November Data Manager API update, without mistaking receipt for attribution.
In this article
How to brief a reliable call-measurement handoff after Google’s November Data Manager API update, without mistaking receipt for attribution.
Know what Google announced on 4 November.
Google announced Data Manager API support for Google Ads call conversions and record-level diagnostic indexes on 4 November 2026. The announcement distinguishes receiving an ingestion request from successfully processing every event. It also says attribution using the new lead_id and existing match_id identifiers was not yet available at announcement time; an identifier being accepted is not the same as attribution being supported.
The buyer question is straightforward: when a supplier says call reporting is connected, what evidence will demonstrate that the agreed events were processed? Our recommendation is a small acceptance plan that follows a record from its source through diagnostics to the intended reporting view. Do not treat a green upload response as that entire plan.
Define the outcome without exposing the conversation.
In an illustrative property agency, a phone call could mean an accidental dial, a rental enquiry or a relevant viewing request. Agree what the marketing event represents before building the connection. Keep the definition separate from the person’s private conversation and from any later claim that the enquiry became a sale.
Identify the data owner, technical owner and report reviewer. Ask which system holds the call time and permitted identifiers, how permissions are checked, and which fields must never enter the advertising payload. For healthcare and counselling, a measurement brief should not become a route for sending symptoms, diagnoses or session notes to an ad platform.
- Specify the conversion action and the business meaning of the event.
- Keep a restricted reconciliation reference rather than copying raw call content into logs.
- Document consent, retention and permitted identifiers before implementation.
Make partial failure visible.
Ask the implementation team to retain the order of submitted records and a safe way to reconcile diagnostic positions to the originating event. The platform’s record indexes are useful only if the team can identify the affected input without searching an uncontrolled export of customer information.
Have the technical owner separate rejected records from warnings, transient delivery failures and unresolved matching questions. Define a correction process and an audit trail before enabling retries. Replaying an entire batch because one item failed can create a different reconciliation problem; follow the current API’s retry and identity rules rather than inventing them in a spreadsheet.
Use an acceptance note that a business owner can understand.
An illustrative acceptance note might say: the test event was sent, its diagnostic status was checked, its destination was reviewed, and one intentionally invalid test record produced a visible failure. These are proposed checks, not a report of AdzUp testing a client account. The note should also state what remains unverified, such as later attribution or a full reporting window.
Before changing bidding decisions, compare the business’s call log totals with the measurement definitions and reporting delays. A cleaner technical connection does not guarantee more leads. Its immediate value is a more defensible account of what was sent, what failed and what the report can reasonably mean.
What would this
look like for you?
Define a useful enquiry and the next conversation your team can actually deliver. Explore our lead generation service, or tell us what you are working on so we can discuss the scope.
Put the thinking into practice.
Sources & further reading
Platform references support the factual background. The planning recommendations are AdzUp’s editorial interpretation.
A useful read.
A clearer next move?
Keep exploring, or bring your questions to AdzUp.


