For platforms to learn from real sales and not just enquiries, you need to send back what happened afterwards: who bought, how much and when. Closing this loop within 24 hours has become one of the best-return measurement improvements for lead-generation businesses.
The essentials in a definition
Offline conversions in a cycle is the process of regularly sending the platforms the sales that happen outside the site (phone, store, CRM), tied to the originating click or contact. It reduces the gap between the sale and platform learning to 24 hours or less, improving optimisation. The conversion import options and measurement guide the setup.
Why close the loop
A completed form is not a sale. Between the two there is qualification, a proposal and closing. Without that information, the algorithm treats all leads as equal and seeks volume.
By returning each lead’s status to the platform, it learns to tell those who close from those who do not, and starts looking for people like the former.
What to send and when
Ideally one event per relevant stage: qualified lead, proposal sent, sale closed, with an associated value. The faster the better: learning benefits from the most recent data. A 24-hour delay is usually a good compromise.
For long cycles, start with an intermediate stage that correlates with closing, instead of waiting months for the final sale.
Closing the loop between CRM and ads
- Store the click identifier on the lead
- Define the stages and the value of each
- Send events to the platform within 24 hours
- Check matching and maintain the process
How to connect the CRM
Store the click identifier (or other authorised matching data) when the lead is created. When the status changes in the CRM, send the event to the platform by integration or regular upload. Check format, date and consent.
Start with the highest-volume channel and widen later. A spreadsheet uploaded weekly is already better than nothing.
The algorithm learns from what we tell it about the end of the story.
Checking and maintaining
Compare conversions sent with conversions accepted. Track the match rate and investigate drops. Update the process if the CRM or forms change.
Document the criteria for each stage. If what the sales team considers qualified changes, the algorithm’s training changes too.
Decision table
| Stage | Action | Caution |
|---|---|---|
| Capture the identifier | Store the click or contact identifier on the lead | Consent and legal basis |
| Record the sale | Update the lead status in the CRM | Consistent status and date |
| Export | Generate the file or use the automatic link | Correct format and time zone |
| Import | Send to the platform and validate | Acceptance windows and duplicates |
Common mistakes to avoid
- Importing weeks late. The platform learns from obsolete information; automate the frequency.
- Not storing the identifier. Without it, the sale cannot be tied to the ad.
- Sending unnecessary personal data. Send only what the platform requires.
How to measure the result
Measure the average gap between sale and sending, the share of leads with an identifier and the percentage of sales imported successfully.
Limits and exceptions
Importing offline conversions requires click identifiers and consent, and it is not always possible: phone sales without a form, long journeys or poorly recorded data limit the link. Platforms have acceptance windows, and delayed data are worth less. If you cannot tie the sale to the click, use alternatives (codes, source survey, tests) and improve recording before automating.
Illustrative example
Illustrative example: a services company closes sales by phone. It starts storing the click identifier in the form and marking the completed sale in the CRM. Every morning, an automated process sends the previous day’s sales to the platform. Within six weeks, optimisation favours ads that generate sales rather than just forms, and cost per sale falls.
Frequently asked questions
Do I need a specific CRM?
Any system that records statuses and allows export or integration will do to start.
Can I upload manually?
You can. A weekly upload already brings benefit, but automation is preferable.
What about GDPR?
Send only authorised data, with a legal basis and transparency. Check with whoever handles data protection.
Which identifiers should I store?
The click or campaign identifier where available, and permitted contact data, with consent.
Do I need a CRM?
It helps a lot; in small accounts, an organised sheet can serve at first, provided it has the identifier and status.
Sending offline sales to the platforms every day, tied to the originating click, teaches algorithms to optimise for real sales rather than forms.
Sources and recommended reading
- Google Ads API: conversion management
- Google Ads Help: conversion measurement
- General Data Protection Regulation (GDPR)
Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.