- Published
- Oct 30, 2026
- Reading time
- 11 min read
Google Ads Enhanced Conversions: Audit Missing Data by Path
Diagnose empty enhanced-conversion data despite firing Ads tags. Compare paths, consent, event timing, coverage and matching without exposing customer data.

In this guide (10 sections)
A firing Google Ads conversion tag does not prove that usable enhanced-conversion data accompanied it. When one form works and another does not, compare the paths at the moment the conversion is measured: data availability, approved collection, variable resolution, transmission and the affected action's diagnostics. Keep those observations separate from matching and attributed conversion credit.
A Reddit question in r/GoogleAnalytics asks why enhanced conversions can work on one path and fail on another while GTM Preview looks healthy. A separate GTM question asks whether an enabled setting still proves a migrated setup works. These are older questions with a current practical answer gap, not evidence of a new Google outage or a widespread failure rate.
Identify which checkpoint is missing#
Google describes enhanced conversions as supplemental first-party conversion data used to improve measurement. That makes the following separate findings:
| Checkpoint | Evidence to establish | What it does not establish |
|---|---|---|
| Business action | The intended signup or purchase succeeded | A measurement request was sent |
| Ordinary conversion event | Correct action and destination executed | Supplemental information was present |
| Data availability | Expected permitted information existed when needed | The configured variable resolved it |
| Transmission | The relevant field was sent and was not empty | Google accepted or matched it |
| Destination diagnostics | An explicit status or validation observation | Every tested event received campaign credit |
| Matching and attribution | The actual metric or report exposed by Google | A complete list of identified buyers or causal sales lift |
If the ordinary action itself is inactive or unverified, use the conversion-action status guide. This guide starts with the different problem of supplemental data missing, incomplete or unproven despite apparently working conversion collection.
Compare the conversion paths
Record data availability, collection and transmission for each affected form.
Use the tracking QA checklistOpens a practical guide. No email required.
Start from the exact diagnostic and action#
Open the affected conversion action and retain the precise alert, action filter, date range and observation time. Account-level summaries can combine actions that use different forms, sites or integration owners.
Google's enhanced-conversion diagnostics reference distinguishes missing fields from fields containing empty data. It also separates coverage from match rate. Coverage concerns eligible conversion events with sufficient user-provided data; match rate concerns matching with signed-in Google data. Neither is a count of CRM customers acquired.
Record unavailable information explicitly. A blank chart, an unknown value and a zero are different observations. Google notes that low-volume alerts can be suppressed and that filters affect the diagnostic population. An absent alert therefore cannot certify every conversion path.
Create an investigation record for one action rather than a screenshot labeled “account broken.” Keep the action identifier private; a public or cross-team summary can use an anonymous label such as Action A. Also retain the released site/container version and the last verified working observation, if one exists.
Build a route matrix before editing the tag#
List the real routes into the same conversion action. Typical distinctions include a main-site form versus a landing-page form, an inline success state versus a redirect, or a signed-in checkout versus a guest checkout.
For each route, record:
- the business success boundary;
- the page or application state where permitted information becomes available;
- the implementation responsible for collecting it;
- the event at which the conversion executes;
- the variable's state at that event, without retaining its value;
- applicable consent state and collection controls;
- destination, field-presence observation and diagnostic result;
- released version, browser/device and test time.
This matrix is more useful than a long list of fired tags. It tells you whether two successful-looking tests actually exercise the same implementation.
Choose one working route and one failing route when possible. Hold the conversion action and test conditions consistent. Change only one implementation variable at a time so that an improvement can be connected to a demonstrated correction.
Distinguish absent fields from empty fields#
Google's missing-data explanation describes cases where enhanced-conversion fields are transmitted but contain no data. Possible causes include information collected on an earlier page, signed-in journeys that do not ask for it again, or selectors and JavaScript variables behaving differently across devices.
That is a troubleshooting branch, not proof that redirects or signed-in customers always fail. An approved automatic or integration-managed collection method may have its own supported way of connecting information to a later conversion. Establish what that method actually does on the tested route.
Ask the implementation owner to inspect the variable at the conversion event. It may have resolved correctly during form completion but become empty after a page transition, a form replacement or a different trigger. A value seen elsewhere in Preview does not prove availability at the relevant time.
Record a minimal result such as “expected field absent,” “field empty,” “nonempty field observed” or “validation error reported.” Do not copy actual customer values, encoded payloads or hashed identifiers into the worksheet. Their presence is not permission to circulate them.
Do not solve a timing problem by putting customer information in URL parameters, analytics event labels or a broadly accessible browser-storage workaround. Use the supported collection route, the necessary access controls and the implementation owner's approved data handling.
Check the configuration without reviving old setup rules#
Google's 2026 settings update describes unifying web and leads settings and accepting data from website tags, Data Manager and API connections. It dates those changes to April and June 2026. A tutorial requiring one exclusive method selection may therefore describe an older interface.
Preserve the actual account and action controls shown today. Some setup pages still contain older method-selection subsections alongside a newer migration notice. Do not diagnose a current problem solely because a legacy dropdown is absent, or change an account-wide setting to match a historical screenshot.
The GTM setup reference describes automatic detection, specified page locations and code-based collection. It also describes tag-wide controls and event-specific overrides. Record which route owns the affected action, and inspect whether an override changes what the event receives.
Avoid adding a second implementation merely because the first diagnostic is unclear. That can create a new ownership or duplication problem while leaving the original data boundary unresolved. Test the configured method before choosing a replacement.
Verify consent at event time#
A tag can execute while supplemental collection is restricted. The setup reference says collection and processing depend on accepted terms and, where applicable, the necessary consent permissions. Do not interpret intentionally unavailable information as a defect to bypass.
Use Tag Assistant's consent diagnostics to inspect defaults, subsequent updates and the checks applied to the relevant tag. Record the state at the actual conversion event, rather than only the final banner state after the journey finishes.
A useful test includes the approved granted and denied paths. The goal is to verify that each behaves as intended. If a consent update arrives too late or differs unexpectedly between templates, investigate that sequence with the implementation owner. Do not force permission or send a substitute identifier to improve a coverage percentage.
Keep account terms, visitor choices, tag execution and transmitted fields as separate observations. They answer related but different questions. This technical check does not replace the organization's decisions about permitted collection.
Validate transmission without exposing the contents#
Google's Google-tag validation instructions distinguish an enhanced-conversion parameter carrying information from one present but empty. Inspect the supported diagnostics for the deployed implementation; a request's existence alone does not settle its contents or processing result.
Have an authorized owner verify field presence and validation state in the appropriate local test. In the shared record, preserve the conclusion and relevant event timing rather than the raw payload. Redact customer data, identifiers, tokens and sensitive query strings before sharing screenshots or traces.
If a server-side component is involved, inspect its receiving and outgoing boundaries separately. A successful browser request to your own endpoint does not establish what it forwarded to Google. Likewise, an outgoing request is not an explicit acceptance or matching receipt unless the destination actually provides that evidence.
Recheck the released configuration after Preview succeeds. Keep the corrected preview result, published version and ordinary-browser test distinct. The marketing tracking QA guide covers that broader release boundary and negative testing.
Keep aggregate coverage from hiding a route problem#
Hypothetical example: Action A receives 100 eligible conversion events during a completed window. For this local audit, all events are within the same approved collection conditions. The team checks whether each event has the expected nonempty supplemental field; this is a local field-presence proxy, not Google's coverage or match-rate calculation.
| Route | Events | Nonempty supplemental field observed | Local field-presence share |
|---|---|---|---|
| Main-site form | 40 | 40 | 100% |
| Landing-page form | 30 | 30 | 100% |
| Redirected confirmation | 30 | 0 | 0% |
| Total | 100 | 70 | 70% |
Now suppose the next comparable window has 20 main-site events, 20 landing-page events and 60 redirected confirmations. Each route behaves exactly as before. The aggregate field-presence share falls to 40%, even though none of the routes changed its behavior.
The calculation is 40 observed nonempty fields divided by 100 eligible events. It shows a traffic-mix effect amplifying an existing route gap. It does not establish a new platform failure, Google's match rate, lost attributed conversions or lost revenue.
Investigate the empty route and retain the population definitions. When comparing periods, show route shares alongside the aggregate. Do not average route percentages without their denominators, and do not treat a general account percentage as proof that a particular form works.
Separate implementation repair from reporting impact#
After a demonstrated correction, repeat the same route matrix and negative tests. Retain when the change was released and when the diagnostic was inspected. Do not keep changing tags while waiting for a processing surface to update.
Google's impact-results reference describes later reporting on enhanced-conversion effects. Treat that as a separate measurement stage from a successful implementation test. A local nonempty-field observation does not establish matching, additional credited conversions or a business outcome.
When the diagnostic remains unresolved, send support a concise packet: affected action and scope, exact warning, tested routes, release times, event-time consent observations, redacted field-presence results and the first unproven boundary. Include what has been ruled out. Do not attach a customer-data dump to make the ticket look complete.
For a separate delivery comparison, discuss a scoped AdProof review with campaign dates, timezone, event definitions and comparable exports. The fashion-retail delivery baseline case illustrates measured ad delivery, not enhanced-conversion matching or customer-data collection. AdProof's supported campaign/event/report exports can inform that delivery comparison within the integration and coverage that actually exist; keep customer-data and conversion diagnostics with their owning systems.
Frequently asked questions#
Can ordinary conversions record while enhanced-conversion data is missing?
Yes. Enhanced conversion data supplements the ordinary measurement path. Establish the business action, conversion destination and supplemental information separately rather than assuming one successful checkpoint proves the others.
Does a nonempty field prove Google matched the customer?
No. Presence, validation, destination processing, matching and attribution are separate checks. Retain the actual diagnostic or matching evidence exposed for the action; do not infer a match from a payload or a successful transport request.
Should every conversion have supplemental customer data?
Do not use that as a universal requirement. Check eligibility, the actual conversion route and permitted collection. Preserve intentional restrictions and distinguish them from an unintended empty variable or missing transmission.
Why can the account summary look healthy while one form fails?
The selected population can combine actions and routes with different behavior. Filter the affected action, compare individual paths and record their denominators. Aggregate agreement can conceal a route-specific failure.
Compare the conversion paths
Record data availability, collection and transmission for each affected form.
Use the tracking QA checklistOpens a practical guide. No email required.
