Track Forminator submissions as Google Ads conversions with server-side tracking
A Forminator submission can be linked back to the Google Ads click that started the journey, even when ad blockers, short-lived browser cookies, or a switch of device would otherwise break the connection. The practical choice is timing: send the conversion as soon as the form is submitted, or store the click identifiers with the lead and send the conversion only when that lead reaches a later sales milestone.
Why browser tracking loses conversions
Browser-based tracking asks the visitor's browser to load a tag and report what happened. That chain breaks in common situations. Ad blockers can stop the tag loading at all, with estimates in the captured material putting ad-blocker use at over 30% of internet users. Safari's Intelligent Tracking Prevention can clear tracking cookies after only a couple of days, so a click on Monday may no longer be linkable to a conversion the following Friday. A person may also click on a phone and complete a form later on a laptop, leaving two sessions that browser tracking cannot join.
Server-side tracking changes the route. The conversion information is sent directly to Google's servers rather than relying on a script firing in the browser. Captured material reports an average 23% increase in recorded conversions and a 10% reduction in cost per conversion from this approach, attributed to more complete data for Google's bidding algorithms. Browser methods are described as potentially missing up to 30% of actual conversions.
Option 1: fire the conversion on form submission
Decide first which event should count. If a submitted form is the desired outcome, a purpose-built server-side tool such as Converly can be configured with a visual flow: a Forminator submission as the trigger and a Google Ads conversion as the action. It extracts the person's name, email and phone number, secures those details with SHA-256, and sends them onward together with click context such as GCLID, GBRAID, WBRAID and User Agent. That context helps Google match the conversion to the campaign, ad and keyword originally clicked. The alternative described is custom JavaScript in Google Tag Manager to listen for submission, extract and hash contact details, and post to Google's API, characterised as a multi-day project for a skilled developer.
If only customers should count, the identifiers need to travel with the lead into the CRM and be sent later. That second route is detailed below.
Option 2: fire the conversion when the lead becomes a customer
Follow this sequence when the conversion should wait for a CRM milestone:
- Install the capture snippet in the website head, in the same position as other tracking scripts, and add hidden fields to the relevant Forminator forms.
- Use four fields: GCLID, WBRAID, GBRAID and User Agent. In Forminator, add each as a regular Input field with the expected label, then apply the forminator-hidden CSS class so it does not appear on the rendered form.
- When a visitor arrives from a Google Ads click, the capture code stores the identifiers in the browser. On form submission, it writes those values into the hidden fields so they are captured with the lead's name, email, phone number and other entered details.
- Send the submission to the CRM. Forminator integrations named in the captured material include HubSpot, ActiveCampaign, Mailchimp and AWeber, with a Zapier add-on for other systems. Salesforce, HubSpot and Pipedrive are named as example CRMs for the later-milestone route.
- When the lead reaches the chosen milestone, such as a deal being created or an opportunity marked closed won, send the stored identifiers back to Google Ads as a conversion. Zapier and Make are named for this step, with a visual mapping screen for matching captured values to the Google Ads fields.
Checklist before going live: confirm every form has all four hidden fields, submit a test form from a Google Ads click, verify the identifiers appear on the CRM record, trigger the milestone in a test record, and confirm a single conversion is recorded in Google Ads.
What server-side tracking fixes beyond ad blockers
Beyond recovering missed conversions, server-side events are cleaner. Browser tracking can double-count after a page refresh, lose events when a connection drops during loading, or miss data when pages load slowly. A server-side conversion is triggered only after a form is actually and successfully submitted, so Google Ads counts align more closely with real lead numbers in the CRM.
Identity data also helps across time and devices. Using the lead's email as a stable identifier can reconnect a click and a conversion separated by days, and sending name and email directly can stitch together phone and computer sessions that browser tracking treats as unrelated.
Three reports to run after setup
Once conversions carry reliable click context, three reports become practical:
- Conversions by keyword: shows which keywords produce conversions rather than only impressions and clicks, helping budget move toward profitable terms across campaigns.
- Conversion value by campaign: when value is passed from the CRM deal or opportunity, revenue can be compared by campaign. This matters because customers differ in value, for example a one-off website build versus a longer social media management engagement.
- Conversions by geography: breaks conversions down by country, state, city or postcode. For local services such as landscaping, pest control, locksmiths and plumbing, this reveals whether leads cluster in profitable service areas. Location Bid Adjustments can then raise bids in postcodes that produce paying customers and reduce or remove bids where clicks never become forms.
Use these reports for both manual decisions, such as keyword and location bid changes, and to give automated bidding more accurate conversion data to learn from.
Wrap up
Choose the timing that matches the outcome you want Google Ads to optimise for, capture the click identifiers at submission, and send the conversion server-side. Firing on submission suits lead volume; waiting for a CRM milestone suits revenue quality. Either way, avoid relying on thank-you-page visits or browser-fired events as the primary measure, because the missed and messy data they produce will be reflected in campaign performance.
| Situation | What breaks | Server-side response |
|---|---|---|
| Ad blocker active | Google Tag does not fire in the browser | Conversion data is sent directly to Google's servers |
| Safari or iOS privacy limits | Tracking cookies cleared after a couple of days | Email is used as a stable identifier across the delay |
| Click on phone, conversion on laptop | Sessions cannot be joined in the browser | Identity data sent to Google stitches the visits together |
| Page refresh or dropped connection | Duplicate, missing or messy browser events | Conversion triggers only on successful form submission |
Browser-based methods are described as potentially missing up to 30% of conversions; server-side tracking is reported to average a 23% increase in recorded conversions and 10% reduction in cost per conversion.
Frequently asked questions
Why can thank-you-page tracking miss conversions?
Browser-based methods can miss conversions when scripts are blocked, cookies expire quickly, or the click and conversion happen on different devices. Sending the event from the server avoids dependence on the visitor's browser, so the recorded conversion is more complete.
How are hidden fields set up in Forminator?
Add regular Input fields labelled for GCLID, WBRAID, GBRAID and User Agent, then apply the forminator-hidden class so they are not visible on the rendered form.
Should the conversion fire on submission or later?
Fire immediately on submission if a form submission is the outcome you want Google Ads to optimise for. Wait for a later CRM milestone, such as a created deal or closed-won opportunity, if only paying customers should count.