Business guide
Google Ads offline conversions: connect eligible leads to real outcomes
Scope Google Ads outcome imports using supported matching, reliable CRM statuses and current Data Manager options without attributing every job to ads.

Choose a business outcome that improves your advertising evidence
Google Ads can measure more than the initial website enquiry when an eligible later outcome is imported correctly. A service business may care about qualified enquiries or accepted quotes because a cheap form submission can still be unsuitable work. Define the event with the people handling the leads before selecting an import method or asking a developer to connect systems.
Document the point at which the outcome occurs and whether its value is fixed, estimated or based on the actual job. Keep qualification separate from winning the work so the report remains understandable. Also review which conversion actions influence campaign decisions. Sending every stage without a counting strategy can make several events from one enquiry look like several independent customer acquisitions.
Keep the supported matching information with the lead
Standard click-based imports rely on eligible click information such as a Google click ID. Capture supported identifiers accurately through the approved website and lead process where permitted, and preserve them with the relevant enquiry. Do not change their case, truncate them or manufacture a value when an organic lead has none. Matching evidence belongs to a particular journey, not every record sharing a customer name.
Enhanced conversions for leads can use supported first-party customer information with the required configuration and policy obligations. This is different from placing an email address in a normal analytics event. The exact fields, permissions and technical steps depend on the selected Google workflow. Treat them as a scoped measurement project rather than copying a generic snippet into the form.
- Eligible lead
Preserve supported matching information and the internal lead reference.
- Verified outcome
Apply the agreed qualified or won definition.
- Supported import
Use the current Google connection and required data format.
- Diagnostics
Check accepted, unmatched and rejected records before trusting attribution.
Check current Data Manager options before building
Google’s guidance dates the migration of offline and enhanced-conversions-for-leads uploads to the Data Manager API from 15 June 2026. It also describes restricted legacy access for integrations with qualifying prior upload history. For a new connection, assess Data Manager and supported connectors; do not assume an old Google Ads API tutorial still provides available access. Confirm existing integrations individually before changing them.
Agree who controls the Ads account and lead source, who can authorise data sharing and who checks failed imports. Google recommends including available GCLIDs with uploads wherever possible. Enhanced conversions for leads adds supported first-party matching, subject to setup and policy requirements. Ask your supplier which supported connection it will maintain and how the business can inspect the results.
Plan permissions, duplicates and rejected records
Review customer-data terms, relevant consent and disclosure requirements before sharing first-party data with Google. Hashing is a technical processing step, not permission to reuse information for any purpose. Keep customer contact details out of ordinary analytics parameters, and do not upload the contents of private enquiry messages or job notes when they are not required for supported matching.
Use a consistent event reference or supported deduplication approach and track what has been sent. Retries should not create extra outcomes. Review rejection reasons, time windows, timestamp formatting and connection failures against the current import instructions. If a quote is cancelled or its value changes, assess the supported correction process rather than silently leaving incorrect outcomes in the report.
- Define the conversion action, outcome time and value basis.
- Preserve only supported matching evidence with the correct lead.
- Use current Data Manager or supported connection guidance.
- Monitor duplicate, rejection, correction and attribution diagnostics.
Compare the platform report with the business record
An accepted upload does not guarantee a match or establish that advertising caused the sale. Compare a sample of imported outcomes with the CRM and inspect the platform’s attribution rules. Keep organic, referral and unknown leads visible in the business report. Google Ads should receive eligible measurement data, not become the only place the business knows whether work was won.
My software integration service can scope this connection around your existing website, CRM and Ads account. Implementation and testing need agreement on tools, access and customer-data handling. This guide describes the design considerations, not a claim that a ready-made integration is already included with every website. Dependable lead records are the foundation for meaningful advertising feedback.
