Migrate Make.com scenarios to n8n: audit + PRD checklist
Migrate Make.com scenarios to n8n without breaking production. Use this audit + PRD checklist to inventory modules, credentials, errors, and rebuild safely.
Google Ads offline conversion uploads not showing
Google Ads offline conversion uploads not showing? Use this checklist to verify customer ID, conversion action, windows, schedules, and where to validate results.
TABLE OF CONTENTS
If your Google Ads offline conversion uploads show “success” but don’t appear in the account, the issue is usually one of five things: you’re uploading into the wrong customer ID, the conversion action doesn’t exist in that account, the timestamps/window don’t qualify, another scheduled upload is overriding or duplicating the same action, or you’re looking in the wrong place in the UI.
This guide walks through a fast diagnostic flow to confirm where the data is breaking and what to change.
Quick diagnostic flow (10 minutes)
- Confirm you’re in the right Google Ads customer ID (and MCC)
- Confirm the conversion action exists in that customer ID
- Confirm the upload type matches your setup (GCLID vs enhanced conversions for leads)
- Check conversion time + attribution window rules
- Check for scheduled uploads and duplicates (pause legacy schedules)
- Validate where you should see the import (and when it should appear)
1) Confirm you’re uploading into the right Google Ads account
Offline conversions can “upload successfully” to a Google Ads account while you’re checking a different account (especially with an MCC + multiple child accounts).
Checklist:
- Verify the customer ID used by your upload (API request or UI account selector)
- Confirm you’re not uploading into an “overall” account while checking a “brand/line-of-business” account (or the reverse)
- If you use an MCC, confirm the upload request is scoped to the correct child account
If your account structure has multiple similar names, write down the exact customer ID you intend to upload into and keep it next to your upload logs.
2) Confirm the conversion action exists in that same customer ID
A common root cause is a conversion action mismatch:
- The upload references a conversion action that exists in a different account
- The conversion action name is similar but not identical
- The conversion action was deleted, replaced, or renamed
What to do:
- In Google Ads go to Goals → Conversions (or Goals → Summary → Conversion actions, depending on your UI)
- Find the exact conversion action you are uploading into
- Confirm it’s in the same customer ID you’re uploading to
If you’re uploading via API and see errors like “no conversion action found,” this is almost always the explanation: the conversion action is not owned by the customer ID you’re uploading into.
3) Confirm the upload method matches your tracking setup
There are multiple offline conversion approaches. If your implementation and your expectation don’t match, “success” can be misleading.
Common setups:
- Click-based imports (GCLID / GBRAID / WBRAID): best when you store click identifiers at lead time.
- Enhanced conversions for leads: best when you match on first-party data (email, phone) rather than click IDs.
Make sure you know which one you’re using and where that identifier is captured (form, CRM, webhook, spreadsheet, etc.).
4) Check conversion time + conversion window rules
Offline imports follow time rules. If your conversion time is outside the conversion window, the upload may not be counted the way you expect.
Verify:
- The conversion time you upload is the time the offline conversion happened, not the time you processed the upload
- Your conversion action’s conversion window is long enough for your sales cycle
- You’re not uploading conversions tied to clicks older than what Google can match (for click-based imports)
If your business takes weeks to close, set a longer conversion window for the conversion action you’re optimizing against.
5) Check scheduled uploads and duplicates (and pause legacy schedules)
If you inherit an account, it’s common to find old scheduled uploads still configured.
Problems that show up:
- A legacy schedule uploads the same conversion action and causes confusion about what is “new”
- A schedule is pointed at a different customer/account
- Duplicate uploads (same identifier + same conversion time + same action) get dropped
Decision point:
- If there is an old schedule you don’t trust, pause it first, then run one clean test upload so you can observe results without two systems competing.
6) Validate where you should see the import (and when)
Google Ads has multiple places to look:
- Goals / conversion actions reporting
- Uploads status screens
- Campaign reporting filtered by a specific conversion action
What to do:
- Filter your reporting to only the conversion action you’re testing
- Narrow the date range (for example, last 14 days)
- Confirm you’re not accidentally viewing a different conversion action or account
If you’re testing with a single conversion, keep the test tight: one action, one upload batch, one date range, one account.
Common causes recap
- Wrong customer ID / wrong account selected
- Conversion action mismatch (exists in another account)
- Upload method mismatch (GCLID vs enhanced conversions for leads)
- Conversion time/window mismatch
- Conflicting scheduled uploads or duplicate imports
- UI/report filters hiding the conversions you expect to see
Get help fixing your Google Ads offline conversion setup
Tracking down why offline conversions don't appear usually breaks at one of the six points above. Book a ZoomFlow session — one of our consultants can walk through your account structure, upload logs, and conversion action configuration live and help you isolate the problem in a single call.
Related Posts
How to extract Quo call recordings to Airtable (without AI credit burn)
How to extract Quo call recordings to Airtable while cutting Zapier AI credit burn — using Claude API prompts, structured JSON, and safer field mapping.
Donation form year parsing errors (Bloomerang → HubSpot): fix
HubSpot rejecting a bad campaign year from your donation form name? Here’s how to avoid multiple 4-digit numbers, parse the right year, and prevent failures.
