How Qualified Lead Data Can Be Sent Back to Google Ads

The click identifier

Every Google Ads click carries a GCLID. It is a long string that uniquely identifies the click. To send any outcome back later, you need this identifier attached to the lead from the start. If it is missing, the outcome has no way to connect to the ad spend that produced it.

The GCLID is usually available in the page URL after the click or in a first party cookie. The reliable approach is to capture it at form submission time and write it into a hidden field or the dataLayer so your form handler can pass it along.

Storing it on the lead record

Once the form is submitted, the GCLID should be stored as a field on the CRM lead record. Treat it like a required field for any lead that came from paid ads. Without it stored cleanly, you cannot send outcomes back later no matter how good the rest of your setup is.

Defining the stages worth sending

Not every pipeline stage is worth sending back. Sending too many low value stages adds noise. The stages that carry real signal are usually qualified lead, appointment booked and closed customer. Each can be its own conversion action with its own value.

• Qualified lead: the lead fits your service and area.
• Appointment booked: the lead scheduled a real conversation.
• Closed customer: the lead became revenue.

Conversion actions in Google Ads

Before you can import anything, you create the conversion actions in Google Ads. Each stage you want to send back gets its own action with a name, a source set to import and a value if relevant. The names you use here must match what you send in the import, otherwise the data will not map.

Offline conversion imports

The import itself is a file or API call that contains the GCLID, the conversion name, the conversion time and optionally a value and a currency. Google matches the GCLID to the original click within its attribution window and records the conversion against that click.

Manual uploads work for testing. For ongoing use, an automated integration that fires when a lead changes stage is far more reliable. It removes manual steps and keeps the timing accurate, which matters because the conversion time affects attribution.

Enhanced conversions for leads

Where the GCLID is missing or unreliable, enhanced conversions for leads can help. This sends hashed user data such as email or phone back to Google, which matches it to the click. It is not a replacement for GCLID capture, but it improves match rates when the click identifier is incomplete.

If you use both, make sure they are not double counting the same outcome. Each conversion should be sent through one path, not several.

Data quality

The value of this whole setup depends on data quality. If stages are updated inconsistently, if the GCLID is missing on some leads or if the conversion time is wrong, the signal you send back is noisy. Noisy signal can be worse than no signal because the algorithm trusts it.

Testing

Test with a single lead before rolling out. Submit a form from a real ad click, move the lead through your stages, and confirm each offline conversion appears in Google Ads with the correct name and time. If something is missing, the failure is almost always in the GCLID capture or the stage mapping.

Common implementation mistakes

• GCLID not captured on mobile traffic where the URL is stripped.
• Stage names in the import do not match the conversion action names.
• Sending the conversion with the wrong timestamp, which breaks attribution.
• Double counting a stage because two workflows fire on the same change.
• Forgetting to set the conversion source to import, so the action never accepts uploads.