Hugo Carvalho Site

Starting August 17, 2026, Google Ads says eligible clinic campaigns that are limited by budget and use a target-based bid strategy can perform more consistently toward their stated target. A Target ROAS campaign that has historically exceeded its target may therefore experience performance changes if it remains in scope. Google does not automatically change the campaign’s budget or target. The advertiser must decide whether the existing target still represents the current business goal.

Which clinic campaigns are in scope

The announcement applies to campaigns that are limited by budget and use a target-based bid strategy, such as Target CPA or Target ROAS. Eligible campaign types listed by Google are Search, Shopping, Performance Max, Demand Gen, and Travel. A campaign must meet the relevant conditions; simply using Target ROAS does not place every clinic campaign in scope.

App, Video reach, and Video view campaigns continue with their previous behavior. Hotel and Display campaigns already use the newer behavior. Multichannel Performance Max and Demand Gen campaigns may also see changes in how spend is distributed across channels as the system works toward the selected target.

Google says notifications can be triggered for campaigns that were limited by budget at any point during the prior 12 months and use an impacted strategy. A campaign appearing in the review tool does not necessarily mean it is currently affected.

Operational inference: check current campaign status rather than relying only on an email, notification, or tool listing.

What more consistent performance toward target means

A bidding target is an instruction to the strategy, not merely a reporting benchmark. Google says the updated systems will behave more predictably around that instruction, including when a campaign’s budget changes. If actual historic performance has been materially better than the configured target, the system may move performance closer to the target after the rollout.

Operational inference: for Target ROAS, compare the campaign’s configured target with the actual return produced over a representative period. A large gap can indicate that the written target no longer expresses the outcome the business expects. The rollout does not itself determine which return is commercially acceptable for a clinic.

Google’s announcement warns that campaigns historically overachieving their targets may see performance volatility if no action is taken. It does not promise a specific increase in spend, conversion volume, value, or profitability. Those outcomes depend on auctions, budget, conversion inputs, campaign mix, market conditions, and the target chosen by the advertiser.

Google will not change the target or budget automatically

The official guidance is explicit: Google will not automatically change campaign targets or budgets as part of this update. If the current target accurately reflects the advertiser’s goal, Google says no change is required. If an overperforming campaign should preserve its current performance level, the advertiser can review the target and use Google’s Target Adjustment Tool where available.

The tool is available in Google Ads for eligible campaigns. For campaigns managed by Search Ads 360, Google says the tool is not available in Google Ads and adjustments should be made in Search Ads 360. Tool availability is not an instruction to change a setting. It provides a review path for the advertiser’s own decision.

Operational inference: do not accept a suggested target merely because it appears in an interface. The accountable decision is whether the target represents the clinic’s current value model, capacity, margin, and growth objective. The clinic value-based bidding readiness guide provides a broader checklist for that decision.

Decide whether the existing Target ROAS is still truthful

Operational inference for this section: start with the business constraint, then evaluate the setting. Document the target currently configured, actual ROAS over a representative period, conversion value definition, budget status, lag, and any material changes in service mix or capacity. Compare those facts with the return the clinic now needs.

Keep the target when it is still the intended operating goal and the clinic accepts that bidding may move closer to it. Consider changing it when the historic target is stale, was set as a loose floor, or conflicts with the current economic requirement. Do not use a short period with unusual volume as the sole basis for a new target.

ROAS also depends on the value supplied to Google Ads. Revenue, expected revenue, and contribution margin are different measures. A campaign can appear to meet a revenue-based target while failing a margin-based constraint. For a practical distinction, see revenue versus contribution margin in dental lead values.

Capture a clean baseline before August 17

Operational inference for this section: before changing any setting, export or record a baseline with campaign ID, campaign type, bid strategy, target ROAS, daily budget, current limited-by-budget status, recent spend, conversion value, ROAS, conversion volume, and the date range used. Record conversion lag and major tracking incidents beside the figures.

Use a period long enough to represent ordinary demand and the clinic’s conversion cycle. Segment only where it helps explain the campaign’s actual operating state. For Performance Max or Demand Gen, capture available channel distribution because Google notes that multichannel allocation can shift under the new behavior.

Keep the baseline free of person-level lead or appointment information. Campaign totals, configuration values, dates, and aggregate outcomes are sufficient. If the report’s conversion columns disagree, resolve the goal and inclusion settings first with the guide to missing clinic bookings from the Conversions column.

Make one governed change at a time

Operational inference for this section: if the business approves a target change, record the old target, new target, reason, approving owner, timestamp, and expected observation window. Avoid changing target, budget, conversion actions, value rules, and creative simultaneously. Multiple concurrent changes make the rollout’s effect difficult to distinguish from the advertiser’s own intervention.

A budget increase deserves separate approval. The platform update may make target behavior more consistent when budgets change, but it does not authorize additional spend. Capacity also matters for clinics: extra eligible demand is not useful if appointment availability, follow-up, or service delivery cannot absorb it.

If no target change is approved, record that the current setting was reviewed and intentionally retained. That creates a clearer operational history than silence and prevents a later assumption that Google changed the value automatically.

Monitor performance after the rollout

Operational inference for this section: compare post-rollout performance with the saved baseline at consistent intervals. Review budget status, actual ROAS versus target, spend, conversion value, conversion count, and channel distribution where relevant. Allow for normal conversion delay before drawing conclusions.

Do not attribute every movement after August 17 to the bidding update. Auction demand, seasonality, clinic capacity, creative changes, landing pages, tracking outages, and conversion-definition changes can produce the same symptoms. Annotate those events and investigate material deviations against campaign change history.

If a measurement outage occurred, do not compensate by changing the bidding target without first addressing the data issue. Google’s data exclusion feature has narrow documented uses; the clinic conversion tracking outage guide explains how to separate incident response from ordinary bidding decisions.

Check the conversion value before judging Target ROAS

Target ROAS can only optimize against the conversion values available to the strategy.

Operational inference for this section: confirm which actions are primary, which appear only in All conversions, and whether the value model reflects the outcome named in the campaign goal. A booking request, attended appointment, and collected revenue are not interchangeable.

Operational inference: reconcile the reporting cohort before comparing Google Ads ROAS with a clinic finance report. Use the original lead or event cohort consistently, account for conversion lag, and document exclusions. The original lead cohort reporting guide explains why mixing event-date and lead-date totals can create a false performance change.

Do not upload medical details or person-level context to make values more precise. The bidding review needs an approved aggregate or generic business value model that complies with applicable Google policies, privacy duties, and internal governance.

A decision checklist for August 17

Operational inference: use this checklist to separate Google’s announced scope from the clinic’s own target and budget decision.

• Is the campaign currently limited by budget, and was it limited during the prior 12 months?
• Does it use Target ROAS or another target-based strategy covered by the update?
• Is its campaign type listed as eligible, already transitioned, or continuing previous behavior?
• Does the configured target still represent the clinic’s approved current goal?
• Is actual historic performance materially better than that target?
• Are conversion values, goal inclusion, lag, and recent tracking incidents understood?
• Has any proposed target or budget change received explicit approval?
• Is a dated baseline available for post-rollout comparison?

Frequently asked questions

Will Google raise my clinic’s daily budget on August 17?

No. Google says it will not automatically change campaign budgets or targets as part of this update. Any budget increase remains an advertiser decision.

Must every Target ROAS clinic campaign change its target?

No. The change concerns eligible campaigns that are limited by budget. Google says no action is required when the current target accurately reflects the advertiser’s goal.

Why could an overperforming campaign change?

The system will work more consistently toward the stated target. If actual historic performance was materially better than that target, performance may move closer to the configured instruction and may be volatile during the transition.

Does appearing in the Target Adjustment Tool prove the campaign is currently affected?

No. Google says the list can include campaigns that were limited by budget at any point in the previous 12 months and use an impacted strategy. Confirm current status and settings directly.

References

• Google Ads Help: Upcoming changes to target-based bidding for campaigns limited by budget, accessed August 16, 2026.

Use a RETRACTION conversion adjustment when a previously uploaded clinic conversion was canceled and should no longer count. A retraction removes the conversion count and sets its value to zero. Use RESTATEMENT only when the conversion remains valid but its value must change. Prefer the original order_id, submit the adjustment through the Google Ads account that manages the conversion action, and treat a retraction as final. The ability to send an API request does not make health-related data eligible for upload.

What a retraction changes in Google Ads

Google Ads supports two distinct conversion adjustment types. A retraction tells Google Ads that the original conversion should be removed. Google sets its value to zero and removes it from the conversion count. That change can affect reporting fields based on conversion count, conversion value, cost per acquisition, and return on ad spend.

A restatement keeps the conversion but replaces its value. It is appropriate when the business outcome still happened and only the reported value was wrong. It does not reduce the conversion count. Choosing between the two is therefore an accounting decision about the original event, not a cosmetic reporting preference.

For a canceled booking that was previously counted as a completed offline conversion, retraction is the matching operation if the clinic’s defined conversion no longer occurred. If the booking remained valid but its commercial value changed, restatement may be the matching operation. The conversion definition should be documented before either adjustment is sent.

Confirm that the cancellation is final before retracting

Google warns that a retracted conversion cannot later be adjusted. A conversion restated to zero is also closed to later adjustment. Subsequent attempts are ignored without an error, so an operator should not assume that a successful request means a second correction was applied.

Operational inference: retract only after the clinic’s source system has reached a final administrative state under its own documented rules. A temporary reschedule, pending review, duplicate flag, or payment dispute is not automatically the same as a final cancellation. The Ads operator should receive a simple approved status and an opaque event identifier, not clinical notes or other sensitive details used to reach that status.

Operational inference: keep the cancellation reason in the clinic’s internal record and send only the fields Google Ads needs to locate and adjust the original conversion. This separation supports reconciliation without expanding the advertising payload. For a durable implementation pattern, see the offline conversion outbox reporting guide.

Prefer the original order ID

The Google Ads API documentation recommends identifying the original conversion with order_id. It is more durable than matching a Google click identifier and conversion time. The order ID must be the same opaque identifier sent with the original conversion, not a newly generated ID for the cancellation.

If the original conversion did not contain an order ID, an eligible offline conversion can be matched with its GCLID and conversion time. GBRAID adjustments require an order ID, and the documented adjustment flow does not support WBRAID. For a WEBPAGE conversion action, an order ID is required. It is also required whenever the original conversion was uploaded with one.

Operational inference: use an opaque order ID that does not encode a person’s name, phone number, email address, diagnosis, treatment, appointment notes, or procedure. It should function only as a stable reconciliation key. If the original pipeline cannot produce that key reliably, fix the identifier contract before automating cancellations.

Submit through the account managing the conversion action

The adjustment must be uploaded by the Google Ads account that manages the conversion action. In cross-account conversion tracking, that may be a manager account rather than the individual clinic account. Sending through the wrong account can produce NO_CONVERSION_ACTION_FOUND even when the action is visible elsewhere in the account hierarchy.

The API documentation limits adjustments to conversion actions whose type is SALESFORCE, UPLOAD_CLICKS, or WEBPAGE. The conversion must already have been recorded. A newly created action can also need four to six hours before uploads are accepted. A CONVERSION_NOT_FOUND response can mean the original conversion was never imported, was discarded, or cannot be matched with the supplied identifier and time.

Operational inference: before changing the pipeline, compare the conversion action owner, action type, original identifier, and original upload result. The offline conversion diagnostics guide covers the account-boundary checks that commonly explain an empty client view.

A minimal retraction workflow

Operational inference: the following sequence turns the documented adjustment requirements into a reviewable clinic workflow.

1. Confirm that the original event appears as an accepted conversion and record the managing customer ID and conversion action.
2. Confirm that the cancellation is final according to the clinic’s approved administrative definition.
3. Retrieve the original opaque order_id. Use GCLID plus conversion time only where the documented rules permit that match.
4. Create a RETRACTION adjustment with the adjustment time and the original conversion reference.
5. Upload from the account managing the conversion action and keep partial failure enabled so individual row errors are returned.
6. Store the request result and reconcile the adjusted reporting after Google Ads processing time.

Operational inference: make the operation idempotent in the clinic’s outbox. One approved cancellation should create one adjustment attempt record, with retries tied to the same event and identifier. This reduces duplicate requests and preserves an audit trail without copying sensitive source-system fields into advertising logs.

Verify the adjustment instead of trusting the request alone

The API requires partial failure mode for these uploads.

Operational inference: inspect each returned result and error rather than treating the HTTP response as proof that every row succeeded. Keep the Google request ID, managing customer ID, conversion action reference, opaque order ID, adjustment type, adjustment time, and per-row outcome. Those fields are enough for most technical reconciliation and do not require clinical context.

Google says adjustment reporting generally appears on a timing similar to regular conversion data.

Operational inference: after processing, confirm that the specific conversion is no longer counted and that its value is zero. Then verify the expected effect in the reporting columns used by the campaign. If an event appears under All conversions but not Conversions, review action inclusion and goal configuration using the clinic conversion-column troubleshooting guide.

Operational inference: do not test a retraction against a real conversion that might need to be restored. Use a controlled eligible test event and document its expected lifecycle. Because retraction is effectively irreversible, a production proof should focus on the final accepted cancellation, request result, and reporting reconciliation.

Platform capability does not decide health-data eligibility

The Google Ads API documents how eligible conversions can be adjusted. That technical capability is not permission to upload health or medical information. Google’s Customer data policies prohibit conversion information related to sensitive categories, including health and medical information, for the products covered by that policy, such as enhanced conversions, store sales uploads, and Google-engaged audiences.

The mapped sources document conversion adjustment through Google Ads tools and the Google Ads API. They do not establish that Data Manager supports this adjustment operation, so this article does not recommend or claim a Data Manager adjustment path. It also does not conclude that every administrative clinic conversion is eligible. Eligibility depends on the exact product, event definition, data fields, consent and legal basis, account configuration, and current Google policy.

Operational inference: use a generic business event only after that separate review, and exclude medical details from identifiers, values, labels, logs, and upload payloads. Hashing does not change the nature of sensitive data. See how to audit enhanced conversions for leads without overclaiming proof for a related measurement boundary.

Common failure modes

• Wrong adjustment type: a restatement changes value but leaves the conversion count in place.
• Wrong account: the upload runs from a client account while a manager account controls the action.
• New identifier: the cancellation receives a different order ID and cannot match the original conversion.
• Missing original conversion: the source event was rejected, discarded, or never uploaded.
• Unsupported action type: the action is outside the API’s documented adjustment types.
• Premature retry: an operator retries before checking row-level errors and creates a misleading local state.
• Sensitive payload: an implementation copies clinical or identifying fields that are unnecessary for reconciliation.

Frequently asked questions

Can a retracted conversion be restored?

No documented adjustment restores it. Google says a retracted conversion cannot be adjusted further, and later attempts are ignored without an error. Treat approval of the retraction as a final control point.

Should a canceled booking be restated to zero?

Use retraction when the conversion should no longer count. Restatement changes value only. Google also says a conversion restated to zero cannot be adjusted again, so zero is not a reversible holding state.

Is order ID always required?

It is required for WEBPAGE actions, for GBRAID adjustments, and when the original conversion used an order ID. Some eligible offline conversions without an order ID can be matched by GCLID and conversion time.

Does a successful API call prove policy compliance?

No. It proves only that the request met the technical processing rules reported by the API. Product eligibility, sensitive-data restrictions, privacy duties, and the clinic’s own governance require separate review.

References

• Google Ads Help: About conversion adjustments, accessed August 16, 2026.
• Google Ads API: Upload conversion adjustments, accessed August 16, 2026.
• Google Ads policies: Customer data policies, accessed August 16, 2026.

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