Why Are Offline Conversion Diagnostics Empty in a Clinic’s Google Ads Client Account?

An empty offline conversion diagnostics result in a Google Ads client account does not prove that the clinic’s import process stopped. Google returns these API summaries only when the customer ID used for the query matches the customer recently used to import the conversions. With cross-account conversion tracking, that customer may be the manager account rather than the serving client.

Trace the conversion account and import request before changing code or sending events again. Another account may contain the recent summaries. Keep diagnostics, Ads reporting, business outcomes, and conversion policy eligibility separate.

Which customer ID returns offline diagnostics?

Google’s API documentation sets a specific restriction. The customer_id supplied to a search or searchStream request must be the same customer recently used to import conversions. A query under another linked account does not inherit the summaries merely because the login can access both accounts.

The credential path answers who may issue the request. The customer ID selects the account resource being queried. Access to a manager and its clients does not combine their diagnostics.

The API exposes an account-level resource, offline_conversion_upload_client_summary, and a conversion-action resource, offline_conversion_upload_conversion_action_summary. The second narrows the view to one action. Both use the same customer scope.

The guide to placing clinic conversion actions in a client or manager account explains the related ownership decision. That decision is broader than this diagnostic question, but it provides the account map needed before a query is run.

Why can cross-account tracking leave the client account empty?

Cross-account conversion tracking lets a manager create conversion actions and share them with managed accounts. Google shows the selected conversion account in the managed account settings. A client can use its own account-specific actions or a manager’s cross-account actions, but it cannot use both arrangements at the same time.

When the manager is the conversion customer used for the import, a search under the serving client may return no offline diagnostics. Google’s developer guide gives this exact example and directs the operator to send the diagnostic query with the manager account’s customer ID.

Do not respond by copying the conversion action into the client. That changes ownership and can change campaign goal behavior. Google warns that switching between client and manager conversion accounts can affect which default goals campaigns use. Diagnose the existing arrangement before proposing a migration.

Operational inference: record three IDs in the incident note: the serving account, the selected Google Ads conversion account, and the customer used by the import request. If those values are not documented, retrieve configuration evidence first. Do not guess from the account name.

What should a valid summary contain?

The account-level summary reports a status plus total, successful, and pending event counts. It also includes alerts grouped by offline conversion error. Google says these top-level fields cover the most recent full calendar day of imports, so they are not a permanent ledger of everything the clinic has ever sent.

The resource also contains daily and job summaries. Daily summaries give successful, failed, and pending counts for the last seven days. Job summaries cover the seven most recent import requests, grouped by job_id. Rows are separate for import clients such as the API and web interface.

Pending events need time. Google’s documentation says they may take up to 24 hours to complete. A pending count inside the correct account is therefore a different condition from an empty result under the wrong account. Preserve those states instead of turning both into a generic “missing conversions” alert.

The offline conversion outbox reporting guide describes the local evidence that should sit beside Google’s aggregate diagnostics. A local event ledger and Google’s account summary answer different questions. Neither should expose clinic payloads to make troubleshooting easier.

Can the import client create another false lead?

Yes. Google returns separate summary rows for different import clients. Recent imports through the API and the web interface can therefore appear under different client values. Looking only at one row may make the other path seem inactive.

A NO_RECENT_UPLOADS status for the API client can indicate that the API process stopped recently. It does not say that no one imported through another supported client. Compare the expected sender with the client field, last upload time, daily summaries, and job summaries before assigning a cause.

Operational inference: monitor the expected customer ID, conversion action, and import client. Accepting any recent row can hide a stopped integration behind a manual upload. Querying only the child can report failure while the manager holds the data.

Keep this monitoring tenant specific. A manager may serve several clients, but a successful row for one conversion action is not evidence for another clinic. Use account and action identifiers, not patient details, to bind each check to the intended tenant.

What is the safest troubleshooting sequence?

Start with read-only evidence. The goal is to locate the summary, not to produce another upload. Another request does not correct a diagnostic query aimed at the wrong customer and makes the timeline harder to interpret.

1. Record the serving client account and the affected conversion action.
2. Check the Google Ads Conversion Account setting for that client.
3. Identify the customer ID used by the recent import process.
4. Query the account-level summary under that same customer ID.
5. Query the conversion-action summary for the exact action.
6. Compare the returned import client with the expected sender.
7. Inspect alerts, daily summaries, job summaries, and pending counts.
8. Wait for pending processing where applicable before escalating.

If the manager query returns the expected summary, the empty client result has been explained by scope. If neither account returns a row, check whether the customer ID, conversion action, import client, and recent time window are correct. Only then investigate the sender process.

Do not change goals, move conversion actions, or upload another event solely to make a diagnostic query return data. Those actions alter system state and answer a different question. The smallest safe correction may be changing the monitoring query to use the existing import customer.

What does an empty diagnostic result fail to prove?

An empty result does not prove that no request reached Google. It may reflect the wrong customer, action, client, or recent-history window. Use request records and the approved local ledger to establish transport history.

It also does not prove that a conversion appeared in Google Ads reporting. Diagnostics describe import health. Reporting depends on other processing and attribution behavior. The article on what an Enhanced Conversions for Leads audit can prove separates request acceptance, diagnostics, reporting, and business effect.

Finally, a nonempty result is not proof of a booking or an attended appointment. Counts in an import summary concern processed events. The clinic’s operational system remains responsible for the meaning and status of an appointment, while Ads reports its own configured conversion actions.

The same distinction applies to columns. A conversion can be present in All conversions but absent from Conversions because of goal and action settings. That reporting configuration is separate from whether the diagnostic summary exists.

How is diagnostics scope different from conversion policy eligibility?

The two manifest sources explain diagnostic retrieval and cross-account conversion tracking. They do not determine whether a clinic may upload a particular event or data field. Finding the correct manager summary establishes where Google exposed recent import health. It does not grant permission to send healthcare data.

Run eligibility review before implementation and whenever the event, destination, data fields, consent path, or campaign changes. Keep medical conditions, treatment details, appointment notes, patient identifiers, and clinical free text out of diagnostic logs. If the proposed conversion is not approved for the selected Google product and applicable obligations, stop the upload path even if the API configuration works.

Policy boundary: diagnostics answer whether Google reports recent processing information for a scoped import. Eligibility answers whether the organization may collect and send that event to that destination. Evidence for the first question cannot answer the second.

This distinction also prevents a dangerous shortcut. An operator should not move an ineligible event to another account, rename it, or hash its fields to make the diagnostic problem disappear. Account scope changes visibility and ownership. It does not change the underlying data or its permitted use.

What evidence should the operator retain?

Keep the serving, conversion, and import customer IDs, plus action ID, import client, query time, status, counts, alerts, and relevant job IDs. Record whether the query returned no row, zero counts, or pending counts.

Do not retain raw payloads in the incident report. Use opaque local event references where correlation is necessary. Restrict access to account configuration and diagnostic evidence, and remove screenshots that expose unrelated clients in a manager account.

Operational inference: close the scope diagnosis only after the same documented query can be repeated under the correct customer and returns the expected recent summary or a clearly explained no-data state. Close reporting and eligibility reviews under their own acceptance criteria.

Frequently asked questions

Does an empty client-account query mean imports stopped?

No. Under cross-account conversion tracking, the manager used for imports may contain the diagnostics. Query the customer ID used by the import before investigating the sender.

Can I retrieve manager diagnostics while querying the child customer ID?

Google’s restriction says the query customer must match the customer recently used for imports. Access to both accounts does not make their diagnostic resources interchangeable.

Should I resend the conversion to create a diagnostic row?

No. First inspect local request evidence, account scope, import client, and pending state. Another upload does not fix a query aimed at the wrong customer.

Do healthy diagnostics make a clinic conversion eligible?

No. Diagnostics describe recent import processing within a Google Ads account scope. Policy, privacy, consent, contractual, and healthcare eligibility require a separate review of the actual event and data.

References

• Google Ads API, “Monitor offline data diagnostics”, retrieved August 16, 2026, https://developers.google.com/google-ads/api/docs/conversions/upload-summaries
• Google Ads Help, “Manager Accounts (MCC): Set up cross-account conversion tracking”, retrieved August 16, 2026, https://support.google.com/google-ads/answer/3061730?hl=en