How to Set Up Offline Conversions in Google Ads: Complete Setup Guide
To set up Google Ads offline conversions, choose the business outcome you want to measure, configure an offline conversion action, preserve eligible matching information with your leads, and connect an import method. Then verify a small batch before relying on it for campaign decisions.
The first decision is not which CSV template to download. It is whether your lead records contain the information needed for your chosen measurement method. This guide gets that foundation ready. TUOCA’s automated relays can then take on the recurring upload work for supported sources and destinations.
1. Decide what counts as a conversion
Choose one specific event for your first setup. For example: “A lead becomes qualified after our team confirms the service area and job type,” or “An invoice is paid.” Identify the source field that proves it happened and the timestamp that belongs to that event.
An illustrative starting definition:
| Decision | Example |
|---|---|
| Event | Completed plumbing job |
| Source condition | Job status is completed; canceled jobs excluded |
| Event time | Job completion time, with timezone |
| Value | Final job amount in USD |
| Record identity | Stable job ID |
| Later corrections | Review refunds or value changes separately from new jobs |
A lead, a qualified lead, and a sale represent different stages. Use separate actions when measuring separate stages, and decide deliberately which stage campaigns should optimize toward. Google’s qualified and converted lead guidance explains those goal categories.
2. Choose the matching path your data can support
Google recommends enhanced conversions for leads for new offline measurement setups. It adds user-provided data to help match outcomes. That does not mean you can export an arbitrary list of email addresses and skip the rest of the setup. See Google’s offline import FAQ.
| Your situation | What to prepare |
|---|---|
| You already preserve GCLIDs with leads | Verify that the ID survives into the conversion record. Keep existing IDs when adding enhanced conversions. |
| Your website collects customer information for enhanced conversions for leads | Configure the Google tag or Tag Manager implementation to collect the appropriate user-provided data, and make that same information available in the later import. |
| You have customer data but no tag collecting it | Google requires a GCLID for this path. Do not assume a hashed email alone fixes the missing setup. |
| You have neither eligible identifiers nor usable customer-data measurement | Fix collection for future leads first. You cannot manufacture the missing original click ID from a customer name or UTM parameter. |
For enhanced conversions for leads, follow Google’s current tag and upload requirements, including applicable customer-data policies and consent requirements. Configure normalization and hashing according to the import method; avoid hashing an already-hashed field again.
A GCLID-only import does not require a website conversion tag merely to upload the offline event. It does require a working way to capture and retain that click ID. That distinction matters when someone tells you “offline conversions don’t need a tag.”
3. Test the handoff from your website to your business system
Enable auto-tagging in Google Ads and verify that your landing-page redirects preserve advertising parameters. Your form or call-tracking setup must associate the identifier with the actual lead, and your CRM must retain that association through the later outcome.
For forms, check the entire journey: landing page → form submission → saved lead → completed job or deal. A hidden field appearing in the browser is not enough if the CRM discards it. For calls, verify your call-tracking provider’s installation, session attribution, and exported fields; do not assume the presence of a call record proves a GCLID was captured.
Use a controlled collection test to inspect the saved fields. A synthetic test identifier can test field transport, but it cannot produce a valid attributed conversion. Reserve the actual import check for real, eligible events.
Google’s GCLID setup instructions cover capture and storage; our GCLID capture guide explains the handoff. Preserve the identifier exactly, including case.
4. Create the offline conversion action
In Google Ads, open Goals → Summary → Create conversion action → Conversions offline. Add a data source, or choose to configure it later, then define the conversion category and action. A conversion action without an import connection is only part of the setup.
Name it so someone else can understand it in a report: Completed job is more useful than Offline conversion 2. For an agency, confirm which account owns conversion measurement before creating actions. A manager account connection alone does not establish cross-account conversion tracking.
These steps follow Google’s current setup instructions; follow the prompts shown in your account if labels differ.
Review the settings intentionally:
| Setting | Decision to make |
|---|---|
| Value | Use the event’s actual value where appropriate. If using an estimate, define it clearly and keep it separate from measured revenue. |
| Counting | Use One when one lead per interaction is the intended measure; use Every when distinct sales should each count. |
| Attribution window | Make it fit the real delay between the ad interaction and this event, within Google’s supported limits. |
| Campaign goal / primary status | Confirm whether the action should inform bidding now or be observed while you validate it. Review campaign-specific goals too. |
“One” is not a duplicate-cleaning strategy. It can suppress legitimate repeat sales; “Every” does not authorize sending the same job repeatedly as new events. See Google’s counting options.
5. Connect the import method and check timing
For an initial file import, use the current template and field mapping provided by your selected Google Ads Data Manager connection. Do not copy a legacy click-only file layout into an enhanced conversions for leads workflow. Google’s import guidelines identify Data Manager file requirements.
Prepare a small set of records with a known source ID, event time, matching information, and value. Check the account and conversion action before applying it. Keep the original source records so you can reconcile the result.
Three timing checks prevent wasted troubleshooting:
- Action readiness: Google advises waiting 4–6 hours after creating a conversion action before uploading to it. Uploading sooner can delay reporting. Setup guidance.
- Import deadline: Standard offline imports have a 90-day limit from the associated last click; enhanced conversions for leads have a 63-day limit. Adding an email does not extend an expired window. Import FAQ.
- Source coverage: A connector’s historical fetch range may be shorter than the platform’s maximum eligibility period. Verify what the chosen connection will actually retrieve before expecting a backfill.
For a custom API integration, check Google’s current migration requirements before using an older tutorial. The current Google documentation directs offline conversion and enhanced lead uploads toward the Data Manager API and describes restrictions on legacy Google Ads API access.
6. Verify the first batch before expanding it
Write down the number of eligible records and their expected total value before uploading. Then compare those expectations with the import result and reporting.
| What you see | What to check next |
|---|---|
| Rejected rows | Read the specific error; inspect action ownership, identifiers, dates, timezone, and field mapping. |
| Accepted import, no immediate report entry | Allow processing time, then check the correct account, action, and date basis. |
| Report differs from the CRM | Separate all business outcomes from the subset eligible for advertising attribution. Check counts and filters before assuming data loss. |
| Value is missing or wrong | Inspect the mapped source field and currency; distinguish absent values from genuine zero-value events. |
| One event appears through multiple workflows | Check whether a native connector, manual file, and automation are sending the same outcome. |
Use All conv. (by conv. time) to inspect imports by when the event happened. An upload is not necessarily reported against its upload date. Google’s reporting instructions explain the distinction. For the next task, use our first-upload guide; if the result still differs, follow conversions not showing.
7. Turn a successful test into a repeatable workflow
Once one batch works, the recurring task is predictable: find newly eligible outcomes, preserve the same event identities, map the fields consistently, send them promptly, and inspect failures. Decide who owns that process before the first spreadsheet becomes stale.
This is the work TUOCA is designed to take off your plate. An automated relay connects a supported source and destination with configured filters, mappings, and a schedule. You still choose what the event means and prepare the Google Ads action; the relay handles the recurring transfer.
If the source containing revenue does not contain the original attribution data, explore a Fusion Relay. It can match conversion records to earlier leads through shared phone or email information. Confirm your source pairing and matching fields before treating it as the solution to missing data.
A native connector may already meet a simple need. TUOCA becomes worth considering when you need a dedicated workflow for recurring uploads or connecting separately stored attribution and revenue. Review supported integration workflows, then compare plans. Neither a relay nor any other uploader changes Google’s attribution rules or deadlines.
For other setup and troubleshooting paths, return to the learning center.