Google Ads offline conversions not showing in the conversions report after an upload

Google Ads Offline Conversions Not Showing: 10 Proven Causes and Fixes

You uploaded offline conversions to Google Ads, through the Data Manager API, the old Google Ads API, a CSV file or a CRM, and the numbers are wrong. Google Ads offline conversions not showing is rarely one mysterious bug. It is almost always one of ten specific things, and the fastest way to find yours is to check them in the right order, because the common and quick to confirm causes sit near the top. This post is only about Google Ads, not Meta or TikTok.Work down the list below. The checks cover every common reason for Google Ads offline conversions not showing, ordered so the quickest wins come first, and for each one you get a way to confirm it and the fix, so you are never guessing.

Check in this order

  1. The upload was rejected or partly rejected.
  2. It is still processing.
  3. You are looking at the wrong dates.
  4. The click was too recent when you uploaded.
  5. The click was too old for the window.
  6. There is nothing to match on, or only email or phone was sent.
  7. It went to the wrong conversion action.
  8. The time was sent without a time zone.
  9. Consent was denied or missing.
  10. A duplicate transactionId.
If you would rather be pointed straight at the likely cause, answer a few questions in the debugger first.Find the likely causeEvery check runs in your browser.

Why Google Ads offline conversions not showing happens, cause by cause

1. The upload was rejected, or partly rejected

A rejected or partly rejected upload is the most frequent reason for Google Ads offline conversions not showing, so rule it out first. A 200 response only means Google received the request, not that it accepted every conversion. With the Data Manager API one bad field can fail the whole request under fast fail, and in other cases some rows are dropped while the rest pass, so a partial upload quietly loses conversions. Confirm it by checking the request status and diagnostics, or the uploads page in Google Ads, rather than trusting the HTTP code. Those show the counts actually processed along with any errors and warnings. Fix the field the status points to and resend. If you have the raw error text, paste the error into the error explainer to see what it means in plain words. If you are still on the old Google Ads API and see CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE, that is a specific block with its own fix, covered in this guide, and the longer term answer is to move to the Data Manager API, which the migration guide walks through field by field.

2. It is still processing

Offline conversions do not appear the moment the upload succeeds. Google says processing typically takes less than 12 hours, and uploads keyed on gbraid or wbraid can take up to 72 hours. It is easy to call them missing while they are simply still in the pipeline. Confirm it by noting when you uploaded and waiting out that window before treating anything as wrong. Fix: give it the full processing time, up to 72 hours for gbraid and wbraid, before you start investigating the other causes.

3. You are looking at the wrong dates

Looking at the wrong date range is one of the biggest causes of Google Ads offline conversions not showing when nothing is actually broken. Google Ads attributes an offline conversion to the date of the click, not the date of the sale. A deal that closes today from a click three weeks ago lands three weeks back in your report, so a date range set to the last few days looks empty even though the conversion recorded correctly. Confirm it by widening the date range to cover when the original clicks happened, not when the sales closed. Fix: add the “by conv. time” columns, such as Conversions (by conv. time), which show conversions on the day they were counted rather than the day of the click, so you can see recent uploads land.

4. The click was too recent when you uploaded

Google will not record a conversion whose click happened less than 6 hours before the upload. Systems that upload quickly after a lead comes in can trip this constantly, losing the fastest conversions. Confirm it by comparing each click time to the time you uploaded. Fix: retry after at least 6 hours have passed since the click, or build that delay into your upload schedule. You can check your click and upload times in the debugger to see which conversions were too fresh.

5. The click was too old for the window

There is a limit at the other end too. Google keeps a gclid for 90 days, and a conversion whose click falls outside the conversion action’s click-through window will not record. Infrequent uploads, such as a monthly batch, are where this bites, because by upload time some clicks have aged out. Confirm it by checking the gap between each click and the upload against 90 days and against your conversion window. Fix: upload more often, ideally daily, so conversions reach Google well inside the window. If you are unsure which conversions aged out, check your click and upload times in the debugger.

6. There is nothing to match on, or only email or phone was sent

A conversion needs something Google can tie to a click. One with no usable identifier cannot attribute at all, and one sent with only hashed email or phone can match only when Google can connect that person to a click, which never covers every row. Confirm it by checking whether each conversion carries a click ID, and expect a number of “Unknown clicks”, which are normal and expected for email and phone matching. Fix: capture and send the click ID (gclid, gbraid or wbraid) wherever you can, and treat email or phone as a fallback that lifts the match rate, not as the main key.

7. It went to the wrong conversion action

The conversions may be recording perfectly well, just against a conversion action your campaigns do not use, or one that is not set to count in the Conversions column. Either way the number you are watching stays flat. Confirm it by checking which conversion action received the upload and how that action is configured. Fix: send to the conversion action your campaigns actually optimize toward, and make sure it is set to be included in Conversions so it appears in the reports you watch.

8. The time was sent without a time zone

If a conversion timestamp has no time zone offset, Google can read it as a moment earlier than it really was, and it will reject a conversion that appears to happen before its own click. These rejections are easy to miss because only the affected rows fail. Confirm it by checking that every timestamp you send carries a time zone offset. Fix: send the time in the correct format with an explicit offset, so the conversion always lands after the click.

9. Consent was denied or missing

Consent signals affect whether a conversion can be used for matching. If they are sent as denied, or no consent is sent for users in the EEA and the UK, matching can be dropped and the conversion never shows. Confirm it by checking the consent fields on your upload. Fix: send the correct consent signals, granted where you have consent, for the regions that require them.

10. A duplicate transactionId

Google deduplicates on transactionId. It uses the first event it receives for a given transaction and treats later events with the same ID as adjustments, not as new conversions, so a reused ID silently suppresses what looks like a second sale. Confirm it by checking for repeated transactionId values across your uploads. Fix: send a unique transactionId per conversion, and reuse an ID only when you deliberately intend to adjust an existing conversion rather than add a new one.

Still stuck?

If you have worked down all ten causes and Google Ads offline conversions not showing is still your problem, narrow it with the tool, then read the bigger picture. In most accounts the issue comes down to timing or dates, both fixable without touching your upload code. For how offline conversions now reach Google and what changed, see Google Data Manager API for offline conversions. More single error fixes are on the debug hub. Google’s own reference is its help article on discrepancies and errors in offline conversion imports.

Frequently asked questions

How long should I wait before worrying that Google Ads offline conversions are not showing?

Give it the full processing window first. Google says offline conversions typically process in under 12 hours, and up to 72 hours for conversions keyed on gbraid or wbraid. Only treat them as missing after that time has passed.

The upload said success but nothing shows. Why?

A success response means the request was accepted, not that every conversion matched and recorded. Check the request status and diagnostics, widen the date range to the click dates, and expect some unknown clicks that cannot be attributed.

Why is the count lower than the number of sales I sent?

Only conversions Google can tie to a Google click will show. Sales from other channels, clicks outside the window, and email or phone only records that cannot be matched all drop out, so the attributed count is normally lower than the total sent.

Can I upload the conversions again after fixing the problem?

Yes. Resend the corrected conversions. Google deduplicates on transactionId and uses the first event it received, treating later events with the same ID as adjustments, so send corrected rows with care around that ID.