Sending platforms the results of leads recorded in the CRM (qualified, meeting, sale) teaches bidding systems to look for leads that become customers, not just completed forms. It can be done without exposing unnecessary personal data, with minimised, hashed identifiers and a clear legal basis.
The essentials in a definition
Lead conversion with CRM data consists of sending ad platforms the commercial outcome of each lead, to optimise for quality. It builds on conversions optimised for leads, the conversions API and compliance with the GDPR.
Why connect the CRM to platforms
Optimising for form completion favours volume, not quality. When the platform receives information about what happened later (qualified lead, proposal, sale), it can learn to distinguish good leads from weak ones. This requires linking ad identifiers to the CRM record.
The documentation on conversions optimised for leads and the Google Ads conversions API describe formats and requirements.
The basic flow
When capturing the lead, store the identifier of the click or campaign that originated it. In the CRM, define clear stages (new, qualified, opportunity, won). When the stage changes, send the platform the matching event, with the identifier and the value where one exists. Start with the stage that best indicates quality, and only then add others.
Ensure the team uses the CRM stages consistently.
From CRM to quality-based optimisation
- Store the click identifier
- Define consistent CRM stages
- Send minimised events
- Measure cost per qualified lead and sale
Privacy and minimisation
Send only what is necessary: the ad identifier and the event, without notes or sensitive data. If you use personal data for matching, such as email, apply hashing and do so only with an appropriate legal basis, stated in the privacy policy, in compliance with the GDPR. Record decisions and limit access.
Check platform contracts and terms on the use of this data.
Teaching the platform to tell good leads apart is the best use of the CRM in ads.
Measure the effect
Compare cost per qualified lead and per sale before and after, and confirm that the volume of events is sufficient for optimisation. Track latency between lead and event, since long delays reduce the signal’s usefulness.
Review the process regularly and fix poorly filled stages.
Decision table
| Element | Good practice | Risk |
|---|---|---|
| Identifier | Stored at capture | Losing the link to the ad |
| Stages | Defined and used consistently | Incoherent data |
| Data sent | Minimal and hashed | Excessive data |
| Latency | Short where possible | Late signal |
Common mistakes to avoid
- Optimising only for forms. It favours quantity, not quality.
- Sending excessive data. It raises privacy risk.
- Poorly filled CRM stages. They corrupt the signal.
How to measure the result
Compare cost per qualified lead and per sale, volume of events sent and latency.
Limits and exceptions
Technical and legal requirements change and vary by platform and country, and this content is not legal advice. With few events, optimisation may not improve. Validate the process carefully before depending on it.
Illustrative example
Illustrative example: a services company stores the click identifier on each lead, defines “qualified” and “sale” in the CRM and sends the platform the qualified-lead event, with the identifier, within a few days. After some weeks, cost per qualified lead falls and the sales team notices better quality.
In practice: checkpoints
Run a quarterly review of the flow: sample leads from each source, check that the identifier reached the CRM and that the right events were sent. Agree with sales on the definitions, record changes, and watch for delays that make the signal arrive too late. Keep access to this data limited to those who need it, and delete data you no longer need.
Frequently asked questions
Do I need to send personal data?
Not always; the ad identifier may be enough. If you use personal data, minimise, hash and have a legal basis.
Which event should I send first?
The one that best indicates quality and has enough volume.
What if the sales cycle is long?
Use an intermediate stage as the signal and add the sale later.
Does this require consent?
It depends on the data and the legal basis; inform and follow applicable rules.
What volume is needed?
Enough for the platform to learn; consult the documentation for requirements.
Send platforms CRM outcomes with minimised identifiers and data, consistent stages and a clear legal basis, to optimise for quality rather than volume.
Sources and recommended reading
- Google Ads Help: enhanced conversions
- Google Ads API: conversion management
- General Data Protection Regulation (GDPR)
Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.