Track Contact Form 7 submissions as Google Ads conversions with server-side tracking
A form submission is only useful for Ads optimisation if Google can match it back to the click that started the visit. Server-side tracking does that by sending the conversion directly from your server, carrying the click identifiers captured at landing, rather than depending on a browser script firing on a thank-you page.
Why browser-based tracking loses conversions
Browser tracking has three common failure modes. Ad blockers can prevent the Google tag from running at all. Safari and iOS privacy features can delete tracking cookies within a couple of days, breaking the link if the visitor converts later. And a click on a phone followed by a submission on a laptop creates two sessions that browser tracking cannot join. Server-side sending avoids the browser as the delivery mechanism: the event is dispatched from your server to Google, so blockers and short-lived cookies do not stop it, and identity data such as email can link a later conversion back to the original click across devices.
Choose when to fire the conversion
Choose the timing that matches the value you want Google to optimise for. Firing on submission gives fast feedback on lead volume. Firing when a lead becomes a customer gives feedback on revenue quality, but requires the identifiers to survive the journey through your CRM. Both routes start the same way: capture the click identifiers at landing and attach them to the form submission.
Step 1: Capture identifiers and store them in hidden fields
Install the capture script on your site, then add hidden fields to each Contact Form 7 form for GCLID, WBRAID, GBRAID and User Agent. In Contact Form 7's shortcode editor, each hidden field is added with a single shortcode line, for example [hidden gclid] for the GCLID field. After a visitor arrives from a Google Ads click, the script stores those identifiers in the browser. When the visitor submits the form, the script writes the stored values into the hidden fields so they are captured alongside the name, email, phone number and other answers.
Step 2: Pass the identifiers to your CRM
Contact Form 7 does not connect natively to a CRM, so pass the submission onward with a webhook plugin or an automation platform such as Zapier or Make. Make sure the hidden-field values are included in the payload, not just the visible answers. The identifiers then sit on the contact or lead record in Salesforce, Pipedrive, HubSpot or your chosen CRM, ready for a later conversion send.
Step 3: Send the conversion to Google Ads
For immediate tracking, a visual automation tool such as Converly can watch for a Contact Form 7 submission, extract the lead details, hash them with SHA-256, and send the conversion plus the captured GCLID, GBRAID, WBRAID and User Agent to Google Ads without custom code. For delayed tracking, use Zapier or Make to trigger the Google Ads conversion when a CRM milestone is reached, mapping the stored identifiers to the correct Google Ads fields. If you send conversion value from the CRM deal as well, Google can optimise for value rather than raw lead count.
Why server-side events are cleaner
Server-side events fire only on a successful submission, not on a page load, so they avoid double counting from refreshes, lost events from slow loads, and dropped connections mid-load. That makes Ads conversion counts line up more closely with real lead numbers in the CRM, which in turn gives bidding algorithms cleaner data. Captured evidence cited in the original guide reported an average 23% increase in recorded conversions and a 10% reduction in cost per conversion with server-side tracking; treat those figures as dated, unverified reference points rather than a promise for your account.
Three reports to run once conversions flow
Conversions by keyword shows which search terms produce actual leads, not just clicks, so budget can shift toward profitable terms. Conversion value by campaign, using the deal value passed from your CRM, shows which campaigns generate revenue rather than volume alone, which matters when different services have very different customer values. Conversions by geography shows which regions produce leads, down to postcode level for local services, and can inform location bid adjustments toward areas that convert and away from areas that only generate clicks.
Pre-launch checklist
Before going live, check that each form has all four hidden fields, submit a test form after clicking a test ad, confirm the identifiers appear in the CRM record, and confirm the conversion appears in Google Ads exactly once. Repeat the test for a delayed milestone if you fire on deal creation or a won deal, and verify that conversion value arrives when you pass it.
| Situation | What breaks | Server-side fix |
|---|---|---|
| Ad blocker active | Browser tag never fires | Conversion sent from your server, not the browser |
| Safari or iOS, conversion days later | Tracking cookie deleted within a couple of days | Email and stored identifiers link the later conversion to the click |
| Click on phone, submit on laptop | Sessions cannot be joined | Identity data lets Google stitch the visits together |
| Thank-you page refresh or slow load | Double counting or lost events | Event fires only on successful submission |
Comparison of failure modes described in the guide; figures are dated unverified captured evidence.
Frequently asked questions
Why might thank-you-page or Tag Manager tracking miss form conversions?
Browser-based methods can miss conversions when ad blockers stop scripts, Safari or iOS removes tracking cookies within a couple of days, or a visitor starts on one device and submits on another. Sending the conversion from your server avoids relying on the browser to fire it.
What hidden fields are needed in Contact Form 7?
Add hidden fields for GCLID, WBRAID, GBRAID and User Agent to the form. A site script captures those identifiers after a Google Ads click, stores them in the browser, and writes them into the hidden fields when the form is submitted, so they travel with the lead data to your CRM.
When should the Google Ads conversion be sent?
You can fire immediately on successful submission, or wait until a later CRM milestone such as a deal being created, won, or the lead becoming a paying customer. The second option lets you also pass conversion value from the CRM deal.
How does the captured data reach a CRM?
Contact Form 7 has no native CRM integration, so use a webhook plugin or an automation tool such as Zapier or Make to pass the submission, including the captured identifiers, to Salesforce, Pipedrive, HubSpot or another CRM.