apointoo.
Request access
Google Ads for Healthcare

What an Enhanced Conversions for Leads Audit Can and Cannot Prove

cmsapointoo··9 min read

An enhanced conversions for leads audit can prove several technical and reporting facts, but only when each fact keeps its own label. Configuration, request acceptance, destination processing, Ads-side diagnostics, platform attribution, and business lift are different proof layers. Passing one layer does not pass the next.

For clinics, policy eligibility comes before this ladder. Google’s Customer data policies say conversion information related to sensitive categories cannot be measured with enhanced conversions, and the examples include health or medical information. A successful audit cannot make a health-related clinic event eligible. When that restriction applies, stop the outbound workflow and keep the measurement inside the clinic’s approved environment.

What is the proof-layer ladder?

The ladder is a reporting discipline. It stops an auditor from turning a narrow observation into a broader conclusion. A visible setting proves configuration. An HTTP success proves initial request acceptance. A destination status describes later processing. Ads diagnostics describe setup and matching. Reporting describes what Google attributed. None of those observations creates a counterfactual for revenue lift.

Layer Evidence Permitted conclusion Conclusion it cannot support
0. Policy gate Current policy review for the exact event Continue or stop the technical audit Legal advice or permanent eligibility
1. Configuration Account and conversion-action settings Feature appears enabled for the reviewed scope Data was accepted or attributed
2. Request API response and request ID Data Manager accepted the ingestion request Every record reached Google Ads
3. Destination Final destination status, warnings, and errors Processing result for that request Ads reporting or policy approval
4. Ads diagnostics Conversion-action diagnostics and alerts Observed setup or matching condition Incremental business impact
5. Reporting Attributed conversions and values in Google Ads Platform-reported measurement result Revenue caused by the implementation

The distinction follows the same containment rule used in the Data Manager architecture for clinic forms. Transport, policy, and reporting remain separate decisions even when one team owns all three.

Why does a clinic audit start with a policy gate?

Google’s policy applies to enhanced conversions for leads and prohibits conversion information related to sensitive categories. Health or medical information is one of those categories. This is a use restriction, not a formatting warning. Hashing, generic event names, consent records, accepted account terms, and API access do not create an exception.

Describe the proposed conversion in plain language before opening the Ads interface. State what happened, which page or workflow captured it, what service it concerns, and what information the event represents. If it is related to health or medical information, the audit records a stop. It should not proceed to a test upload.

The detailed guide on hashing and clinic-form eligibility explains that boundary. An audit may still review an eligible non-sensitive use in the same organization, but it must not generalize that result to consultation requests, treatment outcomes, appointment details, or other health-related events.

What can configuration evidence prove after the 2026 transition?

Google’s current settings documentation says enhanced conversions for web and leads use a unified on/off setting. It also says that, from April 2026, Google Ads accepts user-provided data from website tags, Data Manager, and API connections at the same time. A screenshot of that setting can prove what the account displayed on the audit date.

The upload path needs a separate check. Google states that from June 15, 2026, offline conversion imports and enhanced conversions for leads uploads moved to the Data Manager API and were blocked in the Google Ads API. Limited legacy access may remain for allowlisted developer tokens with qualifying request history. Do not describe Google Ads API upload access as the general current route.

Configuration evidence should name the account, conversion action, audit time, visible setting, and uploader. It should also state whether the observed setup is legacy, Data Manager, a website tag, or a combination. A green toggle does not prove that a later request arrived, matched, or appeared in reporting.

What does Data Manager request acceptance establish?

The Data Manager diagnostics guide separates the initial response from destination processing. A successful ingestion request has status code 0, enum value OK, and HTTP 200 OK. It returns a request_id. That evidence proves the service accepted the request envelope for processing.

It does not prove that every record succeeded at the Google Ads destination. Google says diagnostics can be retrieved only for successful requests that were not sent with validate_only set to true. An audit should preserve the request ID, submission time, destination, expected record count, and initial response without storing sensitive payload content in the report.

Keep this evidence in a reconciliation log, as described in the offline conversion outbox report. A retry should retain its event identity so the team can distinguish another delivery attempt from another business conversion.

Why must destination diagnostics be reviewed separately?

Google recommends waiting 30 minutes before the first request-status check and polling with backoff until each destination reaches SUCCESS, PARTIAL_SUCCESS, or FAILURE. Processing may take up to 24 hours. An audit closed at the initial HTTP response ends too early.

A final SUCCESS still requires a warning review. Google defines an error as a complete record rejection and a warning as a case where the record was not rejected but part of its data was ignored. PARTIAL_SUCCESS means some records succeeded and others failed. Record counts must be reconciled against what the clinic expected to send.

This layer answers whether the selected destination processed the request and what it ignored or rejected. It does not answer whether the conversion was eligible under policy, whether matching worked in Ads, or whether the platform later attributed a conversion.

What can Ads-side diagnostics prove?

The enhanced conversions for leads diagnostics report evaluates setup health and identifies implementation problems. Google currently describes four data-quality states: Excellent, Good, Needs attention, and Urgent. Alerts can cover missing tag activity, absent user-provided data, no attempted imports, and no matches.

These statuses are time-bounded observations. Google says alerts normally use the past day of data and may use the past seven days when one day is insufficient. An auditor should record the date range, conversion action, alert text, and any change made in response. A status without its observation window is weak evidence.

“Excellent” means Google sees the setup recording enhanced conversions as expected under its diagnostics. It is not a certificate of policy eligibility, legal compliance, complete CRM capture, accurate revenue, or causal impact. Likewise, “no matches” identifies a measurement problem, not proof that the underlying clinic process produced no leads.

How is Ads attribution different from business causality?

Google describes enhanced conversions for leads as matching hashed customer data from offline conversions with website data and signed-in Google accounts, then attributing matched conversions to ad events. The result can change conversion reporting, including engaged-view and cross-device measurement. That is a platform-attribution result.

Business lift asks a different question: what happened because the implementation or advertising treatment existed? A before-and-after increase can also reflect spend, demand, seasonality, sales follow-up, delayed outcomes, definition changes, or recovered measurement. An implementation audit has no untreated counterfactual, so it cannot assign the increase to one cause.

Report the narrow result honestly. For example: “Google Ads reported more attributed conversions after the reviewed setup became active.” Do not rewrite that sentence as “the setup generated more patients” or “revenue increased because matching improved.” The aggregate show-rate reporting method also keeps observed operational outcomes separate from claims about media causality.

What should the final audit report contain?

A useful report is reproducible. It names each claim, its evidence, its time window, the system that produced it, and what remains unknown. It also records the policy classification before any technical result. Screenshots alone are not enough when their account, date range, or conversion action is missing.

  1. Describe the exact event and record the policy decision.
  2. Capture current enhanced-conversions settings and upload route.
  3. Record initial request status and request ID for synthetic or otherwise approved data.
  4. Retrieve destination status, record counts, warnings, and errors.
  5. Capture Ads diagnostics with their action and observation window.
  6. Reconcile attributed reporting under a fixed date range and definition.
  7. List business outcomes separately and avoid causal language.
  8. Assign an owner and review date to every unresolved item.

Use synthetic test records wherever possible. Do not place patient details, form text, appointment notes, treatment data, or rejected payload content in an agency audit. The report should prove the control without becoming another copy of the clinic record.

Frequently asked questions

Does an HTTP 200 response mean the conversions reached Google Ads?

No. It means Data Manager accepted the ingestion request. Retrieve the later destination status, then review record counts, warnings, and errors. Ads-side diagnostics and reporting are additional layers.

Does an Excellent diagnostic status prove the clinic event is eligible?

No. The status describes setup health observed by Google. It does not override the prohibition on enhanced-conversion measurement for conversion information related to health or medical categories.

Can increased attributed conversions be called revenue lift?

No. Increased Google-attributed conversions describe a reporting result. Revenue lift is a causal business claim and needs a design that addresses the counterfactual and other changes during the period.

Can the audit use a real patient event as a test?

Do not use a health-related event to test eligibility or transport. Start with the policy gate. For a separately approved eligible use, prefer synthetic data and keep the audit record free of patient information.

References

Related articles

What an Enhanced Conversions for Leads Audit Can and Cannot Prove | Apointoo