# Google Ads conversion diagnostics: "setup is incomplete" and "needs attention" explained

Canonical URL: https://www.martechdevs.com/blog/google-ads-conversion-diagnostics

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder, martechdevs

Published: 2025-01-17

Last updated: 2026-09-03

Google Ads conversion warnings need an action-level diagnosis. A campaign can report incomplete setup because its goal configuration needs work, while a conversion action may need attention because of collection, enhanced-conversion data or an upload problem. Open the affected action, identify its source and follow one real outcome through collection, processing and reporting. Installing another tag before doing that can create a second problem.

## First identify which layer raised the warning

Record the exact message, affected conversion action, source, account, last change and where the warning appears. A campaign recommendation, Google tag diagnostic, action tracking status and enhanced-conversions alert are different surfaces.

Start in Goals, Conversions and Summary, then open the affected action or diagnostic details. Google's [conversion-summary guide](https://support.google.com/google-ads/answer/10993988?hl=en) describes the goals, actions and troubleshooting entry points. Use the detail behind a status instead of treating its colour as a root cause.

Confirm the action's source before choosing a test:

- **Website tag:** inspect the Google tag and the specific conversion event or configured URL rule.
- **Imported Analytics event:** inspect the GA4 event, property link and resulting Ads conversion configuration.
- **Offline or CRM outcome:** inspect the source record, upload destination and processing results.
- **App or phone conversion:** use the source-specific implementation and eligibility checks; a web form test does not validate it.

Write down the intended business outcome too. “Demo request accepted by our application” is testable. “Conversion tag installed” leaves open whether the tag fires at the right moment or sends to the right action.

![Google Ads diagnostic workflow separates campaign-goal eligibility, conversion delivery and enhanced-conversion inputs before rechecking processed results](https://www.martechdevs.com/assets/blog/google-ads-conversion-diagnostics.svg)

The diagram is a diagnostic workflow. The status names alone do not establish which branch is failing in your account.

## "Conversion tracking setup is incomplete"

Treat this as a prompt to inspect the setup behind the campaign. Do not assume it has one universal fix or that it proves no conversions are being measured anywhere in the account.

First open the campaign's conversion goals. Check whether it uses account-default goals or a campaign-specific selection, then inspect the actions inside the selected goal. Confirm that the intended outcome exists, belongs to the expected account and has the intended optimisation role.

Google's [primary and secondary action rules](https://support.google.com/google-ads/answer/11461796?hl=en) explain that primary actions participate in bidding when their standard goal is used. Secondary actions are normally observational, but inclusion in a custom goal can make them biddable. Marking an unrelated page view primary just to clear a warning changes the campaign's objective.

Next validate the selected action's source. A GA4 import will not be repaired by pasting a native Ads conversion label onto a page unless you deliberately choose to replace the measurement design. A website action can have a healthy sitewide tag while its outcome event never fires.

Save the goal configuration before changing it. If the intended action is already functioning and used by the campaign, inspect whether the alert refers to another action in the goal. Google's conversion-summary documentation notes that a missing-primary warning can concern a secondary or less important action. Diagnose that scope before rewriting a working goal.

## "Unverified", "Tag inactive" or "Inactive"

For a website action, start a Tag Assistant troubleshooting session from the action's status. Begin at the landing page and complete the actual journey instead of opening the success URL directly. Google provides this workflow for unverified, inactive and needs-attention states in its [Tag Assistant conversion guide](https://support.google.com/google-ads/answer/10989978?hl=en).

Inspect three separate pieces of evidence:

1. The relevant tag or container loads on the pages the journey actually uses.
2. The conversion event fires only after the intended success condition.
3. The event is sent to the correct conversion destination, with the expected fields.

A base tag on the homepage does not prove an outcome event exists. For a code-based website conversion, Google's [Google tag guide](https://support.google.com/google-ads/answer/7548399?hl=en) distinguishes the sitewide tag from the event or phone snippet used for the conversion.

Compare the conversion ID and label against the action being diagnosed. Check for a staging destination accidentally deployed to production, a tag left in an unpublished GTM workspace or a second Ads account's label copied into the event tag. These are investigation hypotheses; confirm them in the payload or configuration before making a change.

If the journey moved recently, test the new URLs. A migration can leave the marketing site tagged while the application, embedded form or replacement checkout uses a different collection path. Google's [sitewide-tagging troubleshooting](https://support.google.com/google-ads/answer/9148089?hl=en) covers destination labels, page coverage, multiple domains, account links and related checks.

Do not click your own paid ad just to make the status change. The supported Tag Assistant workflow can verify the implementation without manufacturing paid traffic. A later attributed conversion in Ads is a separate reporting observation.

## "No recent conversions"

This status does not automatically mean a broken tag. Google's Tag Assistant guide notes that a successfully verified action can display no recent conversions before real conversions arrive. Verification and recent attributed activity are separate conditions.

Check whether the business actually received eligible outcomes during the relevant period. If sales received no demo requests, the absence of attributed demo conversions is not surprising. If sales received 40 and the action received none, trace a few eligible examples through the collection path before blaming low volume.

Also check whether you are looking at the right column. An observational action may be visible in All conversions without contributing to the campaign's primary Conversions total. Do not promote the action into bidding merely to make a familiar column populate.

Compare the conversion window, date range and expected delay. A long sales cycle and a recent campaign produce an immature cohort. Raising budgets to clear a diagnostic message does not establish that the implementation works.

Use the [key events and conversion-goal guide](https://www.martechdevs.com/blog/ga4-key-events) when the uncertainty concerns the selected outcome or its optimisation role, rather than the tag itself.

## "Needs attention" or "Check enhanced conversions"

Open the detailed alert and identify whether the base conversion is being recorded. Enhanced-conversion diagnostics can flag missing or malformed matching data even when the underlying conversion action is active. Google's [web tag diagnostics reference](https://support.google.com/google-ads/answer/11956168?hl=en) distinguishes data-quality states and specific alerts.

Follow the affected field and collection method. Do not interpret “needs attention” as permission to send every available customer attribute.

### Missing user-provided data

Inspect when the permitted input becomes available relative to the conversion event. A common implementation hypothesis is that a form clears its fields before the tag reads them, or that an automatic selector no longer matches after a redesign. Test the exact form and success path.

For an application-owned flow, provide the supported integration with the necessary approved data at the appropriate time. Keep that data out of ordinary analytics parameters, URLs and public logs. Confirm the consent state associated with the event, including changes and saved preferences.

Google's [consent debugging procedure](https://developers.google.com/tag-platform/security/guides/consent-debugging) shows how to inspect defaults, updates and tag behaviour. Fix contradictory or late configuration without overriding the visitor's choice.

### Incorrect formatting or incomplete fields

Compare the payload with the documentation for the path you use. Determine whether the tag or integration hashes the input, or whether the upload expects a preprocessed value. Do not hash twice or assume a field is correct because its output looks like a long string.

Google's web diagnostics describe malformed email or phone inputs and missing required address components. [The field-specific alerts](https://support.google.com/google-ads/answer/11956168?hl=en) identify the affected format. Correct the source mapping and repeat a controlled test with appropriate test data.

A valid-looking hash proves little about semantic correctness. It could represent the wrong person's field, an empty placeholder or a stale value from a previous submission. Verify where the input originated and which conversion it belongs to, without circulating raw customer data in the support ticket.

### Low matching or no recent enhanced-conversion data

Review the eligible population and the diagnostic's stated observation period. A lack of alerts on a very small dataset is not proof of a complete implementation, and a coverage metric is not a revenue-lift measurement.

Separate events that legitimately lack a supported matching field from events that should carry one but do not. Investigate changes by form, application release and collection path. Report that coverage denominator alongside the rate so the team can distinguish improved data delivery from a changed audience mix.

## Account for the 2026 enhanced-conversions changes

Google's current update describes unified enhanced-conversion settings and simultaneous acceptance of supported user-provided data from tags, Data Manager and API connections. It also describes migration of offline conversion and enhanced-conversions-for-leads uploads to the Data Manager API, with qualifications for legacy access. [Read the current settings update](https://support.google.com/google-ads/answer/16884284?hl=en) before implementing an older tutorial.

For an existing integration, record the API, destination action and last successful job. Check actual responses and diagnostic results. Do not assume that a historically working Google Ads API upload path is the right choice for a newly created integration.

The account-level switch and the quality of the delivered record remain separate concerns. An enabled setting cannot repair a wrong outcome timestamp, inconsistent identity or an application that never sends the required data.

## Offline uploads need a processing audit

For a missing CRM conversion, trace one real eligible business record through the system. Check the outcome's occurred-at timestamp and time zone, permitted matching identifier, destination account and action, upload attempt and item-level result.

Google's [offline discrepancy guidance](https://support.google.com/google-ads/answer/13321563?hl=en) covers account mismatches, timing errors, conversion windows and reporting-date differences. Keep the original business time intact. If a record appears to predate its ad interaction, investigate time-zone conversion, clock errors or the wrong matched interaction; do not move the business event to a convenient later date merely to pass validation.

Separate these states in your own delivery log:

- Pending delivery.
- Submitted, with an identifiable job or request.
- Rejected, with a reason and a repair decision.
- Accepted for processing.
- Reflected in the intended report, or unresolved after the relevant processing interval.

The accepted total is not necessarily the attributed total. Google recommends using conversion-time columns when comparing uploaded outcomes with business records, rather than comparing upload dates with the default interaction-date view.

For repeated jobs, preserve a stable business identifier and the intended deduplication fields. A retry should not become a new sale simply because the integration generates a new timestamp or identifier on each attempt. Document any supported adjustment path separately from creating a fresh conversion.

## Multi-source conversion alerts require a separate check

If you use Google's multi-source conversions beta, verify the shared transaction identifier and consistent value units across the website tag and additional data source. The feature matches and deduplicates within one conversion action, not across separate actions. Matched backend values can overwrite the tag's original value. [Google's multi-source documentation](https://support.google.com/google-ads/answer/16542291?hl=en) defines those rules.

A value of `9900` from a source storing cents and `99` from a tag storing dollars is an implementation mismatch. Map the unit intentionally before delivery. Do not assume the destination will infer the currency unit from the number's size.

The initial additional-source trial lasts 14 days. Google's [multi-source diagnostics guide](https://support.google.com/google-ads/answer/16288216?hl=en) states that the additional conversions become biddable afterwards, even if diagnostic alerts remain. Record that date and resolve significant identifier or value errors before the transition.

Matched value updates are disabled during that initial trial. Google's [Data Manager event-processing guide](https://developers.google.com/data-manager/api/devguides/events/google-ads/offline/send-events) says uploaded values only override the tag's reported value after the trial ends. Check the transition date before treating an unchanged trial-period value as an upload failure.

This beta has its own availability and supported-action restrictions. Do not apply its deduplication rules to an ordinary GA4 import or a pair of unrelated conversion actions.

## Test the business trigger, including its failures

A useful test set proves both when the conversion should happen and when it should not. For an accepted demo request, run these cases in the appropriate controlled environment:

- Submit an invalid form: no accepted-lead conversion.
- Receive an application error: no accepted-lead conversion.
- Receive a confirmed success: one intended conversion event with the correct destination.
- Refresh or revisit the success screen: no new business lead created by the tracking implementation.
- Retry a request after an ambiguous response: follow the application's stable success and deduplication rule.
- Repeat the journey with the relevant consent choices: collection matches the documented design.

For purchases, replace the lead definition with the actual transaction and refund rules. For CRM outcomes, include a disqualification or stage reversal if that can occur in the business process.

Save redacted evidence from your own account: the affected action details, trigger sequence, destination, relevant payload fields, upload results and observation times. Public screenshots from another account cannot prove your implementation. Keep any customer identifiers out of shared incident notes.

## Know when to wait and when to keep investigating

Google says diagnostic and tracking-status updates can take 24–48 hours after tag corrections. Its [sitewide troubleshooting guidance](https://support.google.com/google-ads/answer/9148089?hl=en) also notes that low traffic can produce misleading status alerts. Other sources and upload paths have their own processing intervals.

Waiting is reasonable after you have evidence that the intended event reaches the correct destination and you are inside the relevant processing window. Waiting is not a repair for a wrong conversion label, a failed request or an event that fires only in GTM Preview because the container was never published.

Avoid repeatedly changing tags during that interval. Save the release time and test result, then compare like-for-like data when it has processed. Multiple simultaneous changes make it difficult to know which one fixed the issue or introduced a new discrepancy.

Escalate with a compact evidence package if the result remains unexplained: source and destination identifiers, exact diagnostic text, redacted test evidence, occurred-at and submission times, processing responses and the report configuration used to look for the outcome.

## Close the incident with evidence

- [ ] The warning is tied to a specific surface, source and conversion action.
- [ ] The campaign uses the intended goal and optimisation role.
- [ ] Successful and failed business journeys produce the expected events.
- [ ] Destination identifiers, values, currencies and timestamps are correct.
- [ ] Consent and enhanced-conversion inputs follow the approved design.
- [ ] Offline processing and any retry or adjustment behaviour are documented.
- [ ] The relevant status and reports were rechecked after processing.
- [ ] A named owner will repeat the acceptance test after future changes.

An [analytics and tracking review](https://www.martechdevs.com/analytics-tracking) should produce this diagnosis across the website, application, consent layer and advertising account. Ask for evidence of the business event and its delivery, plus an explanation of any remaining reporting difference. Clearing a warning is useful only when the measurement underneath it is correct.

## Frequently asked questions

### Why does Ads say setup is incomplete when Tag Assistant finds my tag?

Finding the base tag does not establish that the intended conversion event fires, reaches the correct action or belongs to the campaign's selected goal. Inspect those layers separately and read the action-level diagnostic details.

### Should I change every action to primary to remove the warning?

No. That changes what campaigns may optimise toward. Confirm the intended business goal, its action and any campaign-specific or custom-goal configuration. Keep comparison and diagnostic actions in their deliberately chosen roles.

### Does no recent conversions mean I need to reinstall the tag?

No. Check real eligible outcome volume, source delivery and reporting settings first. A verified action with no recent attributed activity can legitimately show that status. Reinstalling without evidence can create duplicates.

### Does a good enhanced-conversions status prove revenue is accurate?

No. Data-quality diagnostics do not establish that you chose the correct transaction value, business trigger or acquisition outcome. Reconcile those definitions with application and billing records, then verify the destination's processing.

### How long should I wait after fixing the issue?

Use the processing guidance for the source and diagnostic involved. For tag-status corrections, Google commonly documents 24–48 hours. Save the change and test times; if the event still fails a controlled delivery test, continue debugging immediately rather than waiting for the status label.

## Sources

1. [Google Ads: Manage goals from the conversion summary](https://support.google.com/google-ads/answer/10993988?hl=en)

2. [Google Ads: Primary and secondary conversion actions](https://support.google.com/google-ads/answer/11461796?hl=en)

3. [Google Ads: Use Tag Assistant for conversion actions](https://support.google.com/google-ads/answer/10989978?hl=en)

4. [Google Ads: Use the Google tag for conversion tracking](https://support.google.com/google-ads/answer/7548399?hl=en)

5. [Google Ads: Troubleshoot sitewide tagging](https://support.google.com/google-ads/answer/9148089?hl=en)

6. [Google Ads: Enhanced-conversion web tag diagnostics](https://support.google.com/google-ads/answer/11956168?hl=en)

7. [Google: Troubleshoot consent mode](https://developers.google.com/tag-platform/security/guides/consent-debugging)

8. [Google Ads: Enhanced-conversions settings updates](https://support.google.com/google-ads/answer/16884284?hl=en)

9. [Google Ads: Offline conversion discrepancies](https://support.google.com/google-ads/answer/13321563?hl=en)

10. [Google Ads: Multi-source conversions beta](https://support.google.com/google-ads/answer/16542291?hl=en)

11. [Google Ads: Multi-source conversion diagnostics](https://support.google.com/google-ads/answer/16288216?hl=en)

12. [Google Data Manager: Multi-source event processing](https://developers.google.com/data-manager/api/devguides/events/google-ads/offline/send-events)