A practical guide for marketing sales and CRM teams
A revenue signal is a verified outcome recorded after a lead enters the CRM. It shows whether the enquiry became qualified, booked a meeting, created an opportunity, or generated revenue. A lead tells a marketing team that someone responded. A revenue signal shows whether that response produced business value.
This distinction matters because advertising platforms usually see the earliest conversion first. If the only event they receive is a form submission, they can learn which people are likely to submit forms. They cannot automatically see which leads sales accepted, which opportunities moved forward, or which customers paid. Revenue signals close that information gap.
This distinction matters because advertising platforms usually see the earliest conversion first. If the only event they receive is a form submission, they can learn which people are likely to submit forms. They cannot automatically see which leads sales accepted, which opportunities moved forward, or which customers paid. Revenue signals close that information gap.
What counts as a revenue signal
A revenue signal must represent a defined business event. The event should have a clear trigger, a recorded time, and a consistent meaning across marketing and sales. Common examples include a lead passing the qualification rule, a valid meeting being booked, an opportunity being opened with an expected value, and a sale being confirmed.
A vague status such as good lead is not a dependable signal unless the company defines exactly what it means. One salesperson may use it for a contactable lead while another may use it only after a proposal. The signal becomes useful only when the same condition applies to every record.
A revenue signal must represent a defined business event. The event should have a clear trigger, a recorded time, and a consistent meaning across marketing and sales. Common examples include a lead passing the qualification rule, a valid meeting being booked, an opportunity being opened with an expected value, and a sale being confirmed.
A vague status such as good lead is not a dependable signal unless the company defines exactly what it means. One salesperson may use it for a contactable lead while another may use it only after a proposal. The signal becomes useful only when the same condition applies to every record.
Why a lead is not enough
Form submissions are useful because they arrive quickly and are easy to count. They are also incomplete. A person may submit with invalid contact details, live outside the service area, have no buying authority, or be looking for a job rather than a product. These records still increase the lead count.
A campaign can therefore report a low cost per lead while creating little qualified pipeline. If marketing evaluates only the first conversion, it may increase spend on the wrong campaign. Sales then carries the cost of checking and rejecting more enquiries.
Form submissions are useful because they arrive quickly and are easy to count. They are also incomplete. A person may submit with invalid contact details, live outside the service area, have no buying authority, or be looking for a job rather than a product. These records still increase the lead count.
A campaign can therefore report a low cost per lead while creating little qualified pipeline. If marketing evaluates only the first conversion, it may increase spend on the wrong campaign. Sales then carries the cost of checking and rejecting more enquiries.
How revenue signals reach advertising platforms
The CRM must first preserve the available campaign and click identifiers. Sales then records each lifecycle change. When a defined outcome occurs, an event service validates the record and sends the permitted event data to the relevant platform. Delivery responses and errors should be stored so the process can be monitored.
The business should use stable event identifiers, accurate event times, and controlled stage rules. A retry for the same business event should not be treated as a new conversion. Personal information should be handled according to the company consent process, applicable law, and the platform terms.
Choosing Your Conversion Goals: Qualified Lead vs. Converted Lead
Google recommends Qualified Lead and Converted Lead as conversion goals for new Enhanced Conversions for Leads actions.
Qualified Lead
A lead that has been reviewed by your team and confirmed as a genuine fit.
It's more meaningful than simply saying someone submitted a form.
Converted Lead
A further downstream outcome.
For one business, that might mean a closed deal.
For another, it could represent a clearly defined sales outcome further along the funnel.
The important point is to define the stage consistently inside your own sales process.
Why the goal type matters
Using the purpose-built lead conversion goals can provide access to Google's Lead Journey Mapping and lead funnel report.
That gives advertisers visibility into how leads move through stages such as leads, qualified leads, and converted leads.
A generic custom conversion may not provide the same lead-funnel visibility.
Keep Google Ads and CRM terminology aligned
There's also a simple operational principle worth following:
Your Google Ads conversion action names should make sense alongside your CRM stage names.
If your CRM uses "Sales Accepted," don't casually rename that stage "Qualified Lead" in Google Ads unless your team has agreed that the two terms represent the same business event.
Otherwise, marketing and sales can end up using different names for what they believe is the same stage.
Primary vs. Secondary: Validating Before You Commit
When setting up a new Enhanced Conversions for Leads conversion action, Google recommends marking the new conversion action as secondary for the first 2–3 weeks.
The reason is practical.
A secondary conversion action can still appear in reporting, allowing you to inspect the incoming data without immediately making the new action part of the primary bidding optimization signal.
That gives you a time window to check whether:
- Conversion volumes look reasonable
- Conversion timing makes sense
- CRM outcomes are arriving correctly
- Matching appears to be working
- Any implementation errors are showing up in diagnostics
Once you've validated the data, the new conversion action can be moved to primary when appropriate.
If you're migrating from an existing offline conversion setup, Google's migration guidance also recommends allowing sufficient conversion history before switching optimization from the older action to the new one.
The exact migration timing can therefore differ from the initial 2–3 week validation recommendation.
Common Mistakes Specific to Leads Tracking
1. Pre-filtering conversions
Uploading only the leads you assume came from Google Ads instead of allowing Google's systems to determine attribution can undermine the measurement process.
2. Skipping the validation window
Moving a new conversion action directly to primary before confirming that the incoming data is correct can cause unvalidated conversion signals to influence bidding.
3. Using generic custom conversions
Using a generic conversion instead of the Qualified Lead or Converted Lead goal types can mean losing lead-specific reporting capabilities such as Lead Journey Mapping.
4. Mismatched naming conventions
If your CRM calls a stage "Sales Accepted" while Google Ads calls it "Qualified Lead," teams may interpret reports differently even when they believe they're discussing the same stage.
5. Dropping the GCLID
When GCLID is available, don't unnecessarily discard it.
Google recommends continuing to provide GCLIDs where possible because they can strengthen measurement and attribution alongside user-provided data.
6. Leaving consent information unpopulated
Consent information is part of Google's implementation requirements and should be handled according to the applicable Google Ads customer-data policies and your consent setup.
Conclusion
A form submission tells you an ad was compelling enough to get someone to fill something out.
It doesn't tell you whether that person was ever a real prospect.
Enhanced Conversions for Leads is designed to close that gap — connecting the ad interaction Google Ads knows about with the offline outcome your CRM records, using available matching signals such as hashed first-party data and GCLID.
The technical setup is only part of the equation.
The bigger measurement decision is choosing conversion goals that reflect meaningful business outcomes, sending the appropriate conversion data consistently, and giving new conversion actions enough time to validate before they influence optimization.
That is what turns lead tracking from a simple form-counting exercise into a measurement loop that connects advertising with what actually happens in the sales process.
Frequently Asked Questions
What's the difference between Enhanced Conversions for Leads and standard offline conversion import?
Google describes Enhanced Conversions for Leads as an upgraded version of offline conversion import.
It adds hashed first-party customer data to offline conversion data to improve conversion matching and measurement.
Do I need to modify my lead forms to use this?
Not necessarily.
Enhanced Conversions for Leads can use first-party information already collected through an existing lead process, but the exact implementation depends on how your website, CRM, tagging, and Google Ads data flow are configured.
Which conversion goal should I use — Qualified Lead or Converted Lead?
It depends on the outcome you're trying to measure.
Qualified Lead fits a stage where your team has reviewed and qualified the lead.
Converted Lead fits a further downstream outcome, such as a completed sale or another clearly defined conversion stage.
Some businesses may use both as separate conversion actions representing different stages of the funnel.
Should a new leads conversion action be primary or secondary at first?
Secondary.
Google's current implementation checklist recommends keeping a new Enhanced Conversions for Leads conversion action secondary for the first 2–3 weeks so the data can be validated before it is used for optimization.
Do I need to upload every lead, or just the ones I think came from Google Ads?
Google's guidance is to upload the conversions for the tracked event rather than pre-filtering them based on your assumption about Google Ads attribution.
Google's systems determine whether an uploaded conversion can be attributed to an ad interaction.
How does this connect to what my CRM already tracks?
Your CRM remains the system that records the lead's business outcome.
You define which CRM stages correspond to your Google Ads conversion actions, and an ongoing import or integration process sends those outcomes to Google Ads.
The result is a connection between the advertising interaction and what happened to the lead after it entered your sales process.