Offline Conversions
Part of Paid search conversion measurement
Reconciling search ad conversions with confirmed sales
Compare Google Ads conversions with confirmed sales using business records, event dates and clear reasons for unmatched totals.
Reconcile search ad conversions with confirmed sales by defining each side's events, aligning dates and matching business records where possible. Do not force the totals to agree. Google Ads reports attributed conversion actions; the sales system records confirmed transactions.
Steps to Reconcile Search Ad Conversions with Confirmed Sales
- Define conversion types in Google AdsCheck if using 'Conversions' or 'All conversions'; segment by conversion action (e.g., form submission, purchase).
- Define confirmed sales in your systemUse consistent criteria—e.g., paid order, won deal—with clear rules for cancellations and returns.
- Build a bridge across systemsUse stable IDs (enquiry, order, deal) and track event status, upload result, and sale outcome.
- Align dates without altering eventsCompare by ad interaction date (Google Ads) and sale date (business system); check time zones and conversion windows.
- Classify discrepanciesCategorise differences: open sale, cancellation, duplicate record, missing event, unattributed outcome.
Define the figures
Identify what the Google Ads figure counts: form submissions, qualified leads, online purchases or imported closed sales. Check whether the report uses Conversions or All conversions, then segment by conversion action. Define a confirmed sale separately: for example, a paid order or won deal, with a consistent rule for cancellations and returns.
A submission count cannot match closed sales one for one: some requests will be rejected, remain open or never purchase. An online purchase action is closer to an order record, but order status and value can change later. Google Ads counts can also reflect counting settings, attribution and, in some cases, modelled or fractional conversions.
Build the bridge from records you hold
Keep a stable enquiry, order or deal ID across the business's own form, commerce and sales records. Where available, retain the event or upload record and its processing result. A working bridge can use these fields:
| Field | Question it answers |
|---|---|
| Internal ID and original event | Which request or order started the path? |
| Event and upload status, if applicable | Was it recorded locally and was an offline upload accepted? |
| Event, upload and sale dates | Which business period contains each stage? |
| Sale status and value | What outcome does the business recognise? |
| Difference reason | Why does the record appear in one stage but not another? |
Do not assume Google Ads provides an individual attributed-conversion row for every sale: its reports are generally aggregate and transaction IDs are not displayed there. A successful offline upload need not become an attributed conversion. Keep unmatched records separate, compare the resulting totals with action-level Google Ads reports, and do not assign a campaign by guesswork.
Key Metrics in Reconciliation
- Platform Action Total
- Number of conversions reported in Google Ads.
- Confirmed-Sale Total
- Number of paid or won deals recorded in business system.
- Matched Records
- Records successfully linked between Google Ads and business system.
- Unmatched Records
- Entries present in one system but not the other; reasons documented.
Pros and Cons of Using Offline Conversion Uploads
- ProsImproves accuracy by linking actual sales to ad interactions; supports better attribution analysis.
- ConsRequires consistent ID tracking; unmatched uploads may not become attributed conversions; no direct transaction ID visibility in reports.
Align dates without changing the event
Google Ads' main conversion columns generally place an attributed action against the ad interaction date. A by conversion time column places it on the date the tracked action occurred. If the tracked action is a form submission, that column still does not show the later sale date. Compare a sale-date view with an imported sale action only when that is the action being measured.
Allow for processing and the time between enquiry and sale. Check the selected conversion window: an outcome outside it will not be attributed to the earlier interaction. Check the Google Ads account time zone against business records. Matching dates and IDs explains some differences, but attribution does not prove that advertising caused each sale.
Classify the differences
Useful initial categories are different event stage, sale still open, cancelled or returned order, duplicate business record, missing event, rejected upload, unattributed outcome and different reporting date. Review underlying records for material categories before changing any total.
For tracked purchases, a unique transaction ID can help Google Ads avoid counting the same order twice for one action. In applicable cases, conversion adjustments can retract a recorded conversion or restate its value. These mechanisms have identifier and timing requirements; the business record still needs its own duplicate and cancellation rules.
Report the platform action total, the confirmed-sale total, records matched within the business system, unmatched records and the main reasons for difference. Label click-date and event-date views clearly. If identifiers or outcomes are missing, call the reconciliation incomplete rather than making the totals match by assumption.
Google Ads Conversions vs Confirmed Sales: Key Differences
- Google Ads ConversionAttributed action based on ad interaction date; may include modelled or fractional conversions; does not show transaction IDs.
- Confirmed SalePaid order or won deal recognised by business system; subject to cancellations, returns, and internal validation rules.
