If Google Ads accepts your call-conversion upload but the report is short, reconcile the upload result, matching data and reporting scope separately. Start with a few missing rows. A total such as 82% does not tell you whether the gap comes from timing, ineligible calls, the wrong action or a report filter.
This checklist covers phone-call imports matched using caller and call details. If your integration uploads a GCLID with a later CRM outcome, identify that as a click import first. The two paths have different requirements.
1. Identify what your conversion action measures
| Signal | What it tells you | First diagnostic |
|---|---|---|
| Phone-number click on a website | A visitor activated a link | Test the tag; a tap does not prove a connected call |
| Measured phone call | A tracked call met the action's criteria | Check call reporting, forwarding-number setup and the action's settings |
| Imported qualified call or sale | Your system submitted a later business outcome | Check the source call, import action and individual upload result |
Write down the account ID, exact conversion action and import method before comparing totals. A reporting card for one action cannot explain the missing rows of another.
Google explains the distinction between imported call outcomes and offline conversions from clicks. Sources checked November 3, 2026.
2. Inspect the individual upload results
Open the upload history and download its results. Keep the original file beside the result file so every row can be traced. Separate a preview from an applied import, and a file-level success message from the result attached to the missing record.
Make three queues: rows with explicit errors, rows reported as successful, and rows still unresolved. Repair the first queue according to its actual errors. Investigate the second against the conversion action and report. Avoid resubmitting the entire file with changed timestamps to make the total move.
For a connector, retain the job ID and per-record diagnostics as well as the CRM row ID. If the connector exposes only a batch total, ask it for the missing records' results. A screenshot of an aggregate acceptance rate cannot identify which calls need repair.
3. Reconcile source, account, action and time
- Source eligibility: confirm the call followed the supported measurement path and Google forwarding-number setup. A sales call in your CRM can be real without being attributable to this import.
- Destination account: compare the upload destination with the account that measured the call, particularly when an agency manages several clients.
- Action identity: use the exact action name, including capitalization. Keep a qualified-call action separate from a general calls-from-ads action.
- Caller and start time: compare the source call record with the exported values. Watch for a call-log system exporting local time while the upload process treats it as UTC.
- Timezone: use an explicit offset or supported timezone identifier. Check daylight-saving transitions on the event date.
Google's troubleshooting guide identifies incorrect account, timezone and phone formatting, unsupported call sources, forwarding-number configuration and conversion-window expiry as causes to investigate. Inspect the applicable source requirements instead of assuming every CRM call should match.
Google's call-import troubleshooting checklist.
4. Keep the timing windows separate
Record when the call happened, when the business outcome happened, when the action was created, when the record was uploaded and when you checked the report. Those timestamps answer different questions.
For phone-call imports, Google says conversions within one day of the click may not yet be recordable. Its guide recommends including an extra day of overlapping data in regular imports, with duplicate conversions deduplicated. The same guide separately says to wait at least four hours after creating an action before the first upload.
Those instructions do not promise that every accepted record will appear after a fixed number of hours. Use the action's actual conversion window and current processing diagnostics. A blanket wait can hide a permanent source or formatting error.
Phone-call import preparation and upload instructions. Google's data-freshness guidance also distinguishes conversion types; GA4-import timing should not be applied to every call import.
5. Compare the same reporting scope
Filter the report to the exact action. Compare Conversions and All conversions, then check the campaign's selected goals and the action's primary or secondary setting. Standard goal behavior and custom goals can differ; use the conversion-signal diagnostic to review that setup.
Check the date basis as well as the date range. An ad-interaction report and a report using conversion-time columns can place the same outcome on different days. Include the original interaction period when investigating an older call that qualified later. Remove unrelated filters before concluding the record disappeared.
Google explains conversion-time reporting columns for comparisons with other systems.
If a general call action and an imported qualified-call action cover the same call, adding their totals can count two stages of one enquiry. Decide which outcome the campaign should bid toward, while keeping the other signal available for investigation.
6. Copy a reconciliation worksheet
Download the reconciliation CSV or copy the rows below. Keep the worksheet in your own system. These synthetic rows omit caller numbers and click identifiers. This is an investigation format, not a Google upload template.
row_id,source,conversion_action,call_started_at,converted_at,uploaded_at,upload_result,review_status
call-001,call_asset,Qualified call,2026-11-01T10:00:00+00:00,2026-11-01T10:12:00+00:00,2026-11-02T11:00:00+00:00,success,check_action_and_report_dates
call-002,website_call,Qualified call,2026-11-02T09:00:00+00:00,2026-11-02T09:20:00+00:00,2026-11-02T10:00:00+00:00,review,check_recent_click_processingAdd one status per row: source ineligible, error to repair, recent processing, report-scope mismatch, matched, or unresolved. Keep unresolved rows visible until you have evidence. Do not relabel them as matched to force an expected percentage.
Compare counts only after the same cohort has passed through each stage: recorded source calls → eligible calls → unique uploaded outcomes → successful row results → reported outcomes in the chosen scope. A repeat upload, a repeated caller and a separate qualified sale are different cases.
When the landing journey changes the click identifier, follow the redirect click-data diagnostic and developer handoff. A clean thank-you URL alone does not establish loss; inspect initial capture and storage too.
7. Check the lead journey before changing the traffic
If website calls lose campaign context during redirects, compare the landing URLs with the free URL checker. If the imported outcomes are spam or unqualified enquiries, inspect those visits separately with the traffic audit.
For source cleanup, use the IP exclusion builder and placement builder and read-only PMax audit script. These tools prepare evidence and lists; they do not change whether an imported call matches Google's records. Find all utilities in the free tools hub.
Give bidding a business outcome you trust
AdProtektor helps investigate visitor behavior and protect supported conversion signals through ConversionOS. Pair that evidence with your CRM's definition of a qualified enquiry. Fix matching and reporting first, then evaluate traffic quality with the same event trail.
For CRM outcomes uploaded successfully but absent from reports, follow the offline-conversion diagnostic to separate row results, matching, processing and the selected reporting scope.
If the missing field is a GCLID for a direct ad call, first use the phone-call attribution path guide to distinguish native call imports, website capture and supported provider forwarding.