Direct answer: Track qualified leads from Google Ads to CRM by preserving the supported click identifier with the form submission, creating a stable lead record, recording qualification and revenue stages, and importing eligible outcomes back through Google's supported conversion workflow. Validate consent, timestamps, identifiers and deduplication before using the data for bidding.
Key takeaways
- A form submission is a lead event, not proof of qualification.
- Preserve identifiers at capture; they cannot reliably be reconstructed later.
- Use one conversion definition and stable lead ID across systems.
- Test imports before allowing automated bidding to rely on them.
Prerequisites and ownership
Define qualified lead, opportunity and sale with sales. Confirm the CRM fields, time zone, conversion names, consent basis and who can upload data. Review the current Google Ads conversion guidance because supported methods and requirements change.
Capture the acquisition record
- Use consistent UTM parameters for reporting.
- Preserve the supported advertising click identifier from the landing session.
- Submit it server-side with landing page, timestamp and lead ID.
- Store original source separately from later touches.
- Handle direct calls or messages with their own documented matching process.
Map CRM stages to evidence
| Stage | Suggested evidence |
|---|---|
| Lead | Valid recorded enquiry |
| Qualified | Agreed fit criteria and next step |
| Opportunity | Sales-accepted deal with owner |
| Sale | Verified commercial outcome |
Do not let manual convenience turn every contacted lead into a qualified lead. Record rejection reasons and stage timestamps.
Send eligible outcomes back
Choose a supported CRM integration, data manager or offline import method. Map one CRM event to one advertising conversion action, use the required timestamp and identifiers, and prevent repeat uploads from creating duplicate conversions. Start with observation and reconciliation before optimisation.
Quality-assurance checklist
- Landing test preserves identifier and UTMs.
- CRM record receives the same stable lead ID.
- Timezone and conversion time are correct.
- Duplicate submission and repeat stage updates are controlled.
- Import diagnostics are reviewed.
- Platform totals are compared with CRM cohorts, not expected to match exactly.
Experience and limitations
This guide describes an implementation pattern, not a guarantee of measurement completeness. Browser controls, consent, cross-device activity, unsupported identifiers and CRM delays can reduce match coverage. Verify the live Google documentation and your legal basis before deployment.