What Is Offline Conversion Tracking? The Complete Guide to Connecting Ad Clicks to Real Revenue
Understand how an ad click becomes a reported sale, what data you need, how to check results, and where TUOCA can automate the recurring upload work.
Offline conversion tracking connects outcomes in your business systems to your advertising. You send an ad platform a record of something that happened after the initial lead—such as qualification, a signed contract, or a completed job—along with information it can use to match that outcome to an ad interaction.
“Offline” does not necessarily mean in person. A deal closed over email and recorded in your CRM can be an offline conversion because your website tracking did not record the sale.
If you have ever looked at a campaign full of leads and wondered how many actually became customers, this is the missing connection. You can start with a manual import. When keeping those imports current becomes a recurring job, TUOCA (The Upload Offline Conversions App) is built to automate that work through automated relays.
Follow one lead from ad click to completed job
Here is an illustrative plumbing job, not a customer result:
| Stage | What happens | What you need to preserve |
|---|---|---|
| Monday: ad click | Someone visits your site from an ad. | Available advertising identifiers and the original interaction context. |
| Monday: inquiry | They call about a leaking water heater. | The lead record and its link to that advertising information. |
| Wednesday: completed job | Your team finishes a $1,800 replacement. | The job ID, completion time, value, and customer details needed to connect it to the lead. |
| Thursday: import | You send the completed-job event to the ad platform. | The matching information plus the actual Wednesday event time—not Thursday’s upload time. |
| After processing | The platform evaluates eligibility and attribution. | Upload results and the report for the conversion action you selected. |
A recorded phone call and a completed job answer different questions. Call tracking may already tell Google Ads that a call happened. The later import tells it what happened because of that call. You do not need to replace a working call-tracking setup to add this information.
The awkward part is often that the call tracker holds the advertising information while the job system holds the revenue. Fusion Relays address that particular problem: matching a later conversion to an earlier lead using shared phone or email information, then combining the conversion details with the lead’s attribution data. The records still need usable matching fields and a supported source pairing; software cannot invent missing attribution.
Choose an outcome you can define consistently
Before choosing an upload method, finish this sentence: “We want to report a conversion when _____.”
Good answers are specific: “sales marks the lead qualified,” “the customer signs the contract,” or “the invoice is paid.” “Something changes in the CRM” leaves too much room for accidental uploads.
Ask the person who maintains that system:
- Which field proves the event happened?
- Which timestamp records that event, rather than the record’s latest edit?
- What value should accompany it: booked revenue, collected revenue, or an explicitly defined estimate?
- Can the event be reversed, refunded, or corrected later?
You can track more than one stage, but name them separately. Google distinguishes qualified and converted leads. A qualified lead and a paid invoice should not become indistinguishable rows in a single “Lead” action.
For a long sales cycle, an earlier meaningful milestone can provide a timely signal. Do not rename an appointment “revenue” just because the final sale arrives too late to import.
What data do you actually need?
Think of an import as two connected pieces: which lead this belongs to and what happened to that lead. Exact fields vary by platform and import method.
| Piece | Example | Practical check |
|---|---|---|
| Matching information | A captured Google click ID, or eligible customer data for enhanced conversions. | Does it belong to this lead, and does your chosen method accept it? |
| Conversion event | Completed job | Does everyone use the same business definition? |
| Event time and timezone | The actual job completion timestamp. | Is this the event time, not export time or record creation time? |
| Value and currency | 1800.00, USD | Is it the intended amount, with no duplicated deposits or invoices? |
| Stable record identifier | A job or transaction ID. | Will the same event retain the same identity when exported again? |
| Permission and data handling | Required consent signals and permitted customer data use. | Have you checked the destination’s policies and your collection process? |
Customer-data matching has prerequisites. For Google’s enhanced conversions for leads, a website tag can collect user-provided information to support matching; Google requires a GCLID when you are not using a tag to collect that information. It recommends including available GCLIDs even with the tag. See Google’s tag and upload requirements.
Hashing an email does not, by itself, establish permission to use it. Nor does it make an otherwise ineligible conversion eligible.
Three different clocks can affect an import
It is easy to confuse these:
- Attribution window: how far after an eligible ad interaction the conversion may occur and still receive credit.
- Upload deadline: how late the platform will accept the import.
- Source lookback: how much historical data your connector fetches on a run.
Increasing a connector’s lookback does not extend the ad platform’s deadline. Google’s published limits reject standard offline imports uploaded more than 90 days after the associated last click, and enhanced conversions for leads uploaded more than 63 days after that click. Other eligibility rules still apply. Source: Google import guidelines.
If you close jobs months after the first inquiry, decide how you will measure earlier milestones before investing time in an upload workflow. See conversion windows versus lookback windows.
How to tell whether it worked
Start with a small group of real, eligible events that you can trace back to your source system. Keep the source IDs, expected count, event dates, and total value. Then check the journey in stages:
Did the source produce the right records? A technically valid upload can still contain canceled jobs or the wrong revenue field.
Did the destination accept them? Read row-level failures where available. A successful connection or scheduled run is not proof that every record was accepted.
Did eligible events appear in reporting? Allow processing time, select the right account and conversion action, and check the report’s date basis. In Google Ads, use “All conv. (by conv. time)” to check by the event date. Standard reporting can associate conversions with the earlier ad interaction. Google’s import reporting guidance.
Are campaigns using the intended signal? Recording a conversion and choosing it for bidding are separate decisions. Do not assume a new import automatically changes your campaigns’ goals.
Expect to investigate differences between your CRM totals and attributed totals. Your CRM can contain organic customers, events outside the allowed window, and records without usable matching information. Offline tracking improves the information available; it does not promise that every sale will match or that performance will improve by a fixed percentage.
When does dedicated upload software make sense?
A manual file can be enough for an occasional batch. A native connector can be enough when it sends the exact event and fields you need. Check those options before adding another tool.
TUOCA is useful when the ongoing work becomes the problem: choosing eligible records, mapping fields, running uploads regularly, and finding out what happened afterward. An automated relay gives that recurring workflow a home instead of leaving it in someone’s spreadsheet routine.
If your revenue and attribution are in separate systems, start with Fusion. If one source already contains the complete record, start with automated relays. Review the integrations and confirm your exact source, event, and destination before subscribing. Platform eligibility and your source data still determine what can be attributed.
Your next step
You do not need to connect every system at once. Pick one outcome, one source, and one destination. Confirm that a small batch can make the full journey before expanding it.
For Google Ads, follow the offline conversion setup guide. If you are still deciding what to measure, return to the learning center and work through the Understand path. If recurring uploads are already taking time, explore a TUOCA relay alongside that first test.