Offline Conversion Import for Google Ads

Define a meaningful business event
Capture permitted matching information
Record the real event time
Validate and import the event
Reconcile results before bidding changes

What problem does an offline conversion import solve?

A form submission does not tell an advertising platform whether the business could serve the person, whether a consultation took place or whether a sale followed. Those decisions often happen in a lead-management system or another internal process. Importing a defined later event can connect campaign reporting with a more useful stage of that process.

Consider a hypothetical commercial cleaning company. It receives a website inquiry, confirms that the property fits its service scope, conducts an assessment and later records a signed agreement. Those are four different events. If advertising reports only the first event, an inexpensive stream of unsuitable inquiries may look better than a smaller stream of appropriate opportunities. This example is illustrative, not a Dappr customer result.

The goal is not to send every internal status change to an advertising account. Choose events that have a consistent business meaning and can be recorded accurately. A salesperson’s informal impression that a conversation sounded promising may be too subjective unless the company defines what qualifies and applies that definition across the team.

Which lead stage should you send?

Write the definition before choosing the platform label. In the cleaning example, a qualified inquiry could mean that staff confirmed the property is within actual coverage, the requested service is offered and the business wants a follow-up assessment. Do not add a criterion such as a signed contract to that stage unless qualification truly happens that late. A closed agreement should remain a separate event.

Google recommends separate conversion actions for different funnel stages so reports can distinguish them. That does not mean all stages should automatically become bidding goals. The person managing the account should decide how each action is used after considering volume, delay, consistency and campaign settings. Counting a form, qualification and sale as interchangeable successes can distort the objective.

Choose a stage that staff can maintain. If a final sale may occur well after the platform’s applicable import window, investigate a meaningful earlier event rather than altering dates to force acceptance. The earlier event still needs to represent something real. A reporting limitation is not permission to relabel a pending opportunity as a completed sale.

What data needs to travel with the event?

A planning record should connect an internal lead identifier, the agreed event type, the actual event timestamp and the matching information required by the selected method. If values are included, document their meaning and currency. An estimated opportunity value, signed contract value and recognized revenue are different measures; the business must approve which one is being sent.

Google’s enhanced conversions for leads uses first-party customer information to supplement offline measurement. Appropriate preparation and hashing are part of the supported process, but hashing does not turn an unrestricted data collection practice into an approved one. Have the responsible privacy and technical reviewers confirm permissions, notices, platform terms and the specific fields involved before implementation.

Keep confidential notes, sensitive documents and unnecessary personal details out of the import. The technical team should map the minimum required fields and protect access to the source and transfer process. This article is a planning guide, not legal advice or a declaration that a particular customer dataset is eligible for sharing.

What has changed in the technical setup?

Current Google documentation describes a unified enhanced-conversions setting beginning in April 2026. It also warns that offline-conversion and enhanced-conversions-for-leads API uploads are moving to the Data Manager API from June 15, with legacy access conditions. A guide written around an older Google Ads API upload path may therefore be unsuitable for a new implementation.

Before choosing a connector or building an integration, inspect the current account, source system and official documentation. Identify who owns the conversion actions, whether account-level or manager-account tracking applies and which supported transfer route is available. Existing use of a CRM does not prove that a particular connector or configuration is ready.

For a Dappr project, CRM work concerns Dappr’s own CRM offering. Compatibility with other systems or a specific automation platform must be reviewed for the proposed scope. Do not treat a platform name in Google’s documentation as confirmation that Dappr implements that third-party product. The useful deliverable at this stage is a documented data flow and a verified implementation choice.

How do you test an import without misleading the reports?

Prepare a limited set of permitted records that can be traced through the source system and the import result. For each one, verify that the event occurred, the timestamp and time zone are correct, the conversion action matches the intended stage and any value uses the agreed definition. Do not fabricate customer events merely to populate a production report.

Distinguish records selected for export, records actually sent, records accepted and events attributed in reporting. These numbers can differ for legitimate reasons or because something is wrong. Keep the results and diagnostics available to the people investigating discrepancies, with appropriate protection for the data involved. A completed transfer job is not sufficient evidence that the reporting is correct.

Use the reporting date basis deliberately. Google’s troubleshooting guidance distinguishes conversion-time reporting from other date views. Compare like with like: the real event date in your source record should be reconciled with the relevant conversion-time view, not casually compared with the upload day or an ad-interaction date. Document the selected columns and conversion action in the test notes.

What prevents duplicates and incorrect updates?

Define what makes a business event unique before scheduling repeated uploads. The source system needs a stable way to recognize the same qualification or sale when a job is retried. Do not create a fresh timestamp every time the record is exported; that would describe a new event time rather than the original business outcome.

Google documents duplicate handling for matching event identifiers and fields, but the business still needs its own reliable export logic. Test retries and partial failures so a temporary outage does not lead to a second, inconsistent event record. Maintain enough history to tell whether an item was never sent, rejected or successfully processed.

Also decide how corrections will be handled. A cancelled agreement or a mistaken value should follow the supported adjustment process for the selected conversion setup. Do not improvise by uploading unrelated negative events or silently editing the source after export without checking whether the advertising record also needs correction. Assign responsibility for resolving these exceptions.

When should imported outcomes influence bidding?

Reporting validation should precede a change to campaign objectives. The account manager needs to understand how consistently the event arrives, how long qualification takes and whether the business definition has remained stable. A sudden change in what counts as qualified can look like a campaign improvement even when customer demand has not changed.

Review the proposed bidding change separately from activating the data transfer. Explain which action will be used, what existing actions remain in reporting and how results will be monitored. This is a consequential advertising decision, so the owner should understand the intended objective and budget implications. No import method guarantees lower acquisition cost or better leads.

Avoid repeatedly changing the definition in response to a few disappointing days. Investigate data quality, operational delay and campaign relevance before deciding what to adjust. Preserve a dated record of changes so later comparisons do not mix different objectives under the same label.

What belongs in the handoff to the person maintaining it?

Document the event definitions, field mapping, transfer owner, schedule, diagnostics location and recovery steps. Include what staff should do when a lead is corrected or reclassified. The marketing team should know whom to contact if imports stop, and the technical team should know which business reports depend on the feed.

A useful recurring review compares a small sample of real outcomes against reported records, checks rejected items and confirms that operational staff still apply the agreed criteria. If the business adds a new service or changes its sales process, revisit the mapping. Automation should support a maintained business definition rather than freezing an outdated one in software.

Bring the current lead stages, approved data fields and account structure to a Dappr discussion. The next step is to assess the intended reporting outcome and what the existing website and CRM workflow can support. Implementation details, permissions and any connector work must be confirmed before promising a finished import process.

Questions before you begin

Does an accepted upload prove that every event matched an ad interaction?

No. Keep transfer acceptance, matching and reporting interpretation separate. Review the applicable diagnostics and reconcile a sample with the source system before making claims about campaign outcomes.

Can we use the upload date as the conversion date?

Use the real time the defined business event occurred, formatted as required by the selected implementation. Upload time describes the transfer and may be later. Substituting it can misrepresent the customer journey and complicate reporting.

Should we send a value for every qualified lead?

Only use a value with a documented, approved meaning. An estimate should not be presented as actual revenue. Review the intended reporting and bidding use before deciding whether and how values belong in the import.