Track Leadpages form submissions as Google Ads conversions
If your landing pages collect leads but Google Ads cannot reliably see those submissions, bidding decisions will be based on incomplete data. This guide explains two server-side approaches: report the conversion when the form is submitted, or wait until the lead reaches a more valuable milestone such as becoming a customer. It also shows how to preserve the Google Click ID through the form and CRM so the later conversion can be matched to the original ad click.
Why browser tracking misses conversions
Standard browser-based tracking asks the visitor's browser to load the Google Tag and report what happens on the page. That chain breaks in common situations. Ad blockers can stop the tag from loading at all. Safari and other privacy-focused browsers can limit how long tracking persists, so a click today and a submission several days later may not be connected. A person who clicks on a phone and submits later from a laptop also creates two separate browser sessions that browser tracking cannot join.
Server-side tracking changes the path. Instead of relying on the browser to report a page view, your system sends the conversion directly to Google with lead details such as name, email, phone, and the Google Click ID. That direct message is not blocked by ad blockers or browser privacy settings, and it gives Google enough information to match the conversion to the original click even after a delay or across devices.
Use this decision check before choosing a setup:
- Do you value every form submission, or only submissions that become deals or customers?
- Can your CRM store an extra click identifier on each contact record?
- Do you need conversion value attached, or is a count enough?
- Will you act on keyword, campaign, and geography reports once the data arrives?
Option 1: Report the conversion when the form is submitted
Use this route when a completed form is the outcome you want Google Ads to optimize for. A visual automation tool watches for a new Leadpages submission, extracts the lead's name, email, and phone number, hashes those details with SHA-256, and sends them to Google Ads together with the Google Click ID and other attribution signals.
The practical advantage is that you avoid building the trigger, tag, variable, and hashing logic yourself. You select the submission trigger, choose the Google Ads conversion action, and let the tool handle the server-side send. Because the conversion fires only after a real submission succeeds, it also avoids the duplicate counts that can occur when a thank-you page loads or a submit button is clicked before a form error is fixed.
Option 2: Report the conversion when the lead becomes a customer
Use this route when a form submission is only an early signal and the meaningful outcome happens later, for example when a deal is created or a lead becomes a paying customer. Leadpages stores submissions in its Leads area, but the click identifier must travel with the lead so it is still available at that later milestone.
Follow these steps:
- Add the attribution tool's code to the tracking code section of your Leadpages site.
- In the form builder, open the Fields tab and add a hidden field. Give it an identifier such as gclid, tick "This is a hidden field," and set its required default value to [gclid].
- When a visitor arrives from a Google Ads click, the tool reads the Google Click ID from the URL and stores it in the browser, so it survives browsing and a return visit.
- On submission, the tool writes that identifier into the hidden field, so it is captured alongside name, email, and phone.
- Sync the identifier to your CRM using a native Leadpages integration or an automation tool, and store it on the contact record.
- At the milestone you choose, use an automation tool such as Zapier or Make to map the stored identifier into Google Ads and send the conversion, optionally with a value taken from the contact or deal record.
What accurate data lets you do next
Accurate conversion data helps in two ways. For your own decisions, it shows which keywords, campaigns, and locations actually produce leads and customers rather than clicks that go nowhere. For automated bidding, it gives Google's algorithms a fuller picture of what converts, which can improve how ads are shown. The source article reports Google figures of a 23% average increase in recorded conversions and a 10% reduction in cost per conversion with server-side tracking; treat those as reported benchmarks to verify against your own account data, not as a guaranteed result.
Three reports are especially useful once server-side conversions are flowing:
- Conversions by keyword: identify which search terms generate leads and shift budget toward them.
- Conversion value by campaign: attach a value from the CRM so campaigns producing higher-value customers receive more budget.
- Conversions by geography: compare leads by country, state, city, or postcode, then use location bid adjustments to bid more where conversions occur and less where spend produces no leads.
| Approach | When the conversion is sent | What must be captured | Best fit |
|---|---|---|---|
| Submission-time server-side sending | Immediately after a successful form submission | Name, email, phone, Google Click ID, and attribution signals | You want Google Ads to optimize for every qualified submission |
| Customer-stage server-side sending | When a deal is created, closes, or the lead becomes a customer | Google Click ID stored on the CRM contact record, plus optional conversion value | Only later-stage outcomes are valuable enough to report |
Comparison based on the two workflows described in the source article; tool availability varies by owner configuration.
| Report | Question it answers | Action it supports |
|---|---|---|
| Conversions by keyword | Which search terms produce leads? | Shift budget toward productive keywords |
| Conversion value by campaign | Which campaigns produce the most valuable customers? | Allocate budget by revenue, not just lead count |
| Conversions by geography | Which regions produce leads? | Use location bid adjustments by postcode or region |
Reports require conversions to be flowing into Google Ads; value reporting additionally requires a value field in the CRM.
Frequently asked questions
Why does browser tracking miss Leadpages conversions?
Browser-based methods depend on the Google Tag loading and running in the visitor's browser. Ad blockers can prevent that, Safari privacy limits can break the link after about a day, and a click on one device followed by a submission on another cannot be tied together. Server-side sending passes lead details directly to Google, so those browser barriers do not block the conversion record.
Should I send the conversion on form submission or when the lead becomes a customer?
Choose submission-time sending if you want Google Ads to learn from every qualified form submission as soon as it happens. Choose customer-stage sending if a form submission alone is not valuable enough and you want to report only when a deal is created, closes, or becomes a paying customer. The second route requires carrying the click identifier through to the CRM contact record first.
What are the steps to carry the GCLID from Leadpages to Google Ads?
Add the attribution tool's code to the Leadpages tracking code section, create a hidden form field named for the Google Click ID with the required default placeholder, let the tool populate that field on submission, then sync the stored identifier to your CRM. From there an automation tool can map it into Google Ads at the milestone you choose.
Why can thank-you page tracking double-count conversions?
Counting a thank-you page view or a submit-button click can create duplicates: a visitor may trigger the event, fix a form error, and submit again, producing two conversions for one lead. Server-side tracking that fires only on a genuine successful submission avoids that pattern.