How to track WordPress form submissions as conversions in Google Ads
Browser-based conversion tracking on WordPress forms is fragile: ad blockers, Safari cookie limits and multi-device journeys all quietly drop leads. This guide sets out a server-side approach that records the submission itself, carries the Google Ads identifiers through your CRM, and gives you cleaner data to bid on.
Why server-side tracking beats thank-you pages and Tag Manager events
The usual routes — counting a thank-you page view, or firing an event through Google Tag Manager — depend on a script running inside the visitor's browser. That dependency is where the losses come from. Ad blockers stop the tag loading. Safari's privacy features expire tracking cookies within days, so a click that converts later loses its link. And a visitor who clicks on a work computer but submits the form on a phone leaves the original click disconnected. Server-side tracking changes the direction of travel. Instead of waiting for a browser event and hoping the tag fires, you send the conversion data straight to Google's servers with the lead's details attached. Ad blockers and cookie expiry cannot strip it out, and identity data such as name and email lets Google stitch sessions across devices. Figures sometimes quoted for server-side tracking include an average increase in recorded conversions of around 23% and a reduction in cost per conversion of around 10%, explained by automated bidding having cleaner signals to learn from. Treat any such numbers as directional rather than a promise for your account, and check the current published source before citing them.
Decide when the conversion should fire
Before touching any settings, answer one question: at what moment does a form submission become a conversion worth reporting?
Use this checklist to choose:
- Fire on submission when speed matters and a lead has near-immediate value — for example, a booked consultation or a quote request you always follow up.
- Fire on a CRM milestone when the real signal is downstream — a deal created, an opportunity marked won, or a customer signed. This is slower but closer to revenue.
- Consider both if you want volume data early and value data later; they answer different questions and can coexist as separate conversion actions.
Whichever you pick, the delivery mechanism should be server-side. The difference is only where the trigger lives: on the form submission itself, or on a status change inside your CRM.
Option A: record the conversion the moment the form is submitted
If you want the conversion recorded immediately, a visual workflow tool such as Converly can assemble the flow without custom code. You choose a trigger — one of your WordPress forms being submitted — and an action — sending a conversion to Google Ads. Once the tool's code is on the site, it listens for submissions, pulls the lead's name, email and phone, hashes that data with SHA-256, and forwards it to Google Ads.
It also collects the surrounding signals: GCLID, GBRAID, WBRAID, User Agent and more. Those extra identifiers are what let Google trace the conversion back to the specific campaign, ad and keyword that produced the click. The appeal of this route is that you avoid writing a listener, extracting form values, hashing them and posting to the API by hand.
Option B: record the conversion when a lead becomes a customer
If your WordPress leads already flow into a CRM such as Salesforce or Pipedrive, you can defer the conversion until the lead reaches a meaningful stage. That requires capturing a little extra data at submission time and carrying it through to the CRM.
The four steps below describe that path. The hidden-field names and the identifiers they hold are fixed technical values; keep them exactly as written so the downstream mapping works.
Step 1 — Install the capture script and add hidden fields
Sign up for the tracking tool, add the supplied snippet to your site, then add hidden fields to each WordPress form. The fields to create are: GCLID, WBRAID, GBRAID, User Agent. The major WordPress form plugins — Gravity Forms, WPForms, Contact Form 7, Formidable Forms and Ninja Forms — each let you add a hidden field, usually by dragging one into the form or inserting a hidden-field tag, then giving it the matching name. Plugin-specific instructions are available in the vendor's help documentation. A practical field/control map for this step: Form plugin — the place where the hidden field is created and named. Hidden field name — must match the identifier exactly (GCLID, WBRAID, GBRAID, User Agent). Script placement — site-wide, so it can run on any page that hosts a form. Trial length — confirm current terms with the vendor before relying on it.
Step 2 — Let the script populate the hidden fields
Once the snippet is live, it works in the background. When a visitor arrives from a Google Ads click, it captures the identifiers Google needs for a server-side conversion — GCLID, GBRAID, WBRAID, User Agent and the rest — and stores them in the visitor's browser. At the moment the visitor submits a WordPress form, those values are written into the hidden fields you created, so they travel with the rest of the submission.
Step 3 — Pass the data into your CRM
Because the identifiers are now part of the submission, they can move into your CRM alongside the lead's name, email, phone and any other form answers. Use your form plugin's built-in integration or a connector such as Zapier or Make. The values land on the contact or lead record and stay there until you need them.
Step 4 — Send the conversion back to Google Ads
When the lead reaches the milestone you chose — a deal created, an opportunity won, or any other stage — push the stored data back to Google Ads to record the conversion. Zapier or Make are well suited here: they connect to most CRMs and can fire at whatever moment you define. They also give you a mapping interface so the captured values (GCLID, GBRAID, WBRAID, User Agent and the rest) line up with the corresponding Google Ads fields.
If you attach a value to each conversion — taken from the deal size in your CRM — Google Ads can report revenue per campaign rather than a flat count.
Four failure modes and what each one looks like
It helps to know which problem you are solving, because the fixes differ:
- Ad blockers: the tag never executes, so the visit produces no record at all. Sending the event from your server removes the browser from the path.
- Safari and iOS cookie limits: the click is captured, but the cookie is cleared within a day or two, leaving a later conversion unattached. Matching on identity data replaces the cookie as the connective tissue.
- Cross-device journeys: the ad is clicked on one machine and the form completed on another, and browser storage has no way to join them. Supplying name and email server-side gives Google a thread to follow between the two sessions.
- Duplicate or messy counts: a page refresh can register twice, a slow load can drop the event, and a thank-you page can fire even when the form was abandoned. An event tied to a confirmed submission keeps the count honest.
Three reports worth running once the data is clean
Clean conversion data is only useful if you look at it. These three views cover most of the decisions:
- Conversions by keyword: shows which search terms actually produce leads rather than impressions and clicks. Use it to shift budget toward keywords that convert.
- Conversion value by campaign: possible once you pass deal value from the CRM. An accounting firm illustrates the point — a client from an 'individual tax return' campaign is usually worth far less than one from an 'outsourced CFO' campaign, so counting them equally would mislead. Value-weighted reporting shows which campaigns earn their spend.
- Conversions by geography: breaks results down by country, state, city or postcode. Local-service businesses such as roofers, HVAC contractors or removalists can see whether leads come from areas they actually serve, then apply location bid adjustments to lean into profitable postcodes and pull back from ones that generate clicks but no completed forms.
What good data changes
Accurate conversion data does two jobs. For you, it shows where manual intervention pays — raising bids on keywords or locations that perform. For Google's automated bidding, it provides a trustworthy target to optimise against. Poor data does the reverse: thank-you-page counts and browser events feed the system numbers it cannot rely on, and performance suffers as a result. Whether you fire on submission or from the CRM later, keep the delivery server-side.
Frequently asked questions
Which WordPress form plugins does this work with?
The approach is plugin-agnostic. Gravity Forms, WPForms, Contact Form 7, Formidable Forms and Ninja Forms are all supported, and each lets you add a hidden field with the required name.
Should I send the conversion on submission or wait for the CRM?
Send on submission when a lead has immediate value and you want fast feedback. Wait for a CRM milestone when revenue is the signal you care about. You can run both as separate conversion actions if you want volume and value views.
Why are GCLID, GBRAID, WBRAID and User Agent all needed?
Each identifier covers a different click context. Collecting them together gives Google the best chance of matching the conversion back to the original campaign, ad and keyword, including clicks that arrive through app or web-to-app paths.
Does server-side tracking fix Safari attribution?
It sidesteps the cookie problem. Rather than relying on a cookie that Apple's Intelligent Tracking Prevention may clear within a day or two, the conversion is matched using identity data such as name and email, so a later conversion can still be linked to the original click.