Offline conversion tracking: connect a lead to the sale that follows
Define the lead-to-sale record, preserve eligible matching data, and verify imported outcomes without confusing acceptance with advertising credit.
By Mika Garcia · Published
In this article
Track the outcome that happens after the form
Offline conversion tracking connects an advertising interaction with an outcome recorded outside the original website conversion. That outcome might be a qualified opportunity, a signed agreement or a payment after a sales conversation. The word offline describes the measurement handoff; it does not require a paper transaction.
A submitted form is often an intermediate signal. If campaigns produce equally priced leads but very different numbers of paying customers, optimizing only to forms can hide that difference. Define which later outcome would improve the decision before choosing an import mechanism.
Keep qualified leads, won deals and collected payments separate. They can all be useful stages, but a signed contract and a settled charge do not necessarily have the same timestamp or value.
Define a record that survives the handoff
Create an event contract between the lead system and the destination sender. Include a stable lead or account reference, the business stage, the time that stage actually occurred, value and currency where meaningful, and the eligible matching data captured under your collection policy.
Keep original event time separate from export time. A sale completed on Monday and uploaded on Thursday should not silently become a Thursday sale. Record timezone handling and how amended or cancelled outcomes will be represented.
Assign an owner to the status change. A spreadsheet export, a CRM automation and a payment webhook can all describe parts of the same journey. Without ownership, a retry or a second system can create another conversion instead of updating the same evidence.
A lead-to-sale event contract
1. Lead
Stable reference
Preserve the original acquisition context.
2. Outcome
Stage + event time
Record what happened and when.
3. Delivery
Destination + response
Track the import separately.
Follow a lead without inflating its value
Consider an illustrative lead L-104. It submits a form on October 1, becomes qualified on October 3 and pays $800 on October 9. The same stable reference connects the three records, while each stage keeps its own event name and timestamp.
If the team reports collected revenue, only the payment contributes $800 to that revenue measure. Assigning $800 to the form and another $800 to qualification would not create $2,400 of collected revenue. If proxy values are used for bidding, label them as modeled stage values and keep them out of the cash reconciliation.
A later $100 refund changes the observed collected amount to $700 under a signed-cash policy. Whether and how that adjustment can be sent to the advertising destination depends on its supported correction mechanism. Do not assume an ordinary second purchase event is a refund.
One lead, several milestones
October 1
Form submitted
An intermediate action, not $800 received.
October 3
Qualified
A defined quality stage.
October 9
$800 paid
The financial outcome in this example.
Use Google’s current import guidance
Google’s documentation describes offline imports and recommends enhanced conversions for leads for new adopters. Its current migration notice directs offline and enhanced-lead API uploads toward Data Manager API, with legacy access subject to eligibility. Check the current documentation and your integration provider before building or changing a sender.
Do not copy an old endpoint tutorial just because its screenshots resemble your account. The business event contract can remain stable while authentication, upload methods and diagnostics change. Verify the supported method independently from the article’s conceptual example.
Separate eligible, exported, accepted and attributed
For a sample reporting period, count outcomes eligible for export, outcomes actually exported, accepted records and attributed outcomes separately. Investigate the difference at each stage. A missing match is different from a rejected payload, and both differ from a sale not yet old enough to appear in a report.
Keep a small exception list with the business identifier, failure reason, action taken and next review date. Retrying a permanent configuration error without changing anything is not a measurement strategy. Fix the cause, then verify the corrected record.
In DATALYR, use the documented source and conversion-delivery workflow relevant to your setup. This conceptual guide is not a claim that every CRM, call platform or offline event has an automatic native connection.
Judge lead quality on mature cohorts
Compare campaigns using a consistent follow-up period. A campaign launched yesterday has had less time to close than one launched a month ago. Record the observation window and distinguish pending leads from lost opportunities.
Use the result to investigate quality, follow-up and conversion lag before changing spend. Importing later outcomes provides better evidence about the journey, but it does not by itself prove that advertising caused the sale.