Skip to content

Track Wix Forms Submissions as Google Ads Conversions

A Wix form submission is only useful to Google Ads if the ad click can be tied back to the lead. Browser-only tracking often loses that link. This guide shows two server-side paths — count the conversion at form submit, or wait until the lead becomes a customer in your CRM — and the checks that keep the numbers honest.

Why browser-only conversion tracking loses Wix form leads

Thank-you-page tracking and Google Tag Manager events depend on the Google Tag loading inside the visitor's browser. That dependency creates predictable gaps:

  • Ad blockers stop the tag from loading, so the form submission is never seen.
  • Privacy features in browsers such as Safari limit how long tracking cookies survive, so a click on Monday and a conversion on Friday may not connect.
  • A visitor may click on a work computer and submit the form later on a phone or home computer.
  • A double-click on Submit, a stray thank-you-page visit, or a dropped connection can create duplicate or missing conversions.

Server-side tracking moves the conversion send out of the browser. The identifiers and identity data travel to Google's servers directly, where ad blockers and cookie expiry are less able to interfere. Google's own published figures, as cited in the original article, describe an average 23% increase in recorded conversions and a 10% reduction in cost per conversion when server-side tracking is used. Treat those figures as a dated reference point, not a guarantee for your account.

Choose when a Wix form submission becomes a conversion

There are two workable timings, and the right one depends on what you sell.

Count at form submit. Use this when the form submission itself is the meaningful action — a quote request, a demo booking, a newsletter signup that sales treats as a lead. A purpose-built form-to-Google-Ads connector such as Converly can watch for the Wix form submission and send the conversion immediately. It pulls the lead's name, email, and phone number, hashes them, and forwards the Google Ads identifiers along with the conversion.

Count at a CRM milestone. Use this when a form submission is only the start of a sales cycle and you want Google Ads to learn from closed revenue, not raw leads. Capture the identifiers with the form, push them into your CRM, and trigger the conversion when a deal is created or marked closed won.

A simple decision checklist:

  1. Does a form submission alone justify ad spend? If yes, count at submit.
  2. Do you need to distinguish a lead from a paying customer? If yes, count at the CRM milestone.
  3. Do you have a CRM that can store the identifiers on the contact record? If not, fix that before choosing the CRM path.
  4. Do you need conversion value in reporting? If yes, the CRM path is the one that can carry deal value back to Google Ads.

The CRM path, step by step

1. Install the capture snippet and add hidden fields. Place the capture snippet on the Wix site (in Wix, Settings > Custom Code > Add Custom Code). Then add four fields to the Wix form: GCLID, WBRAID, GBRAID, and User Agent. Wix Forms does not natively support hidden fields, so the exact workaround depends on the builder. In Wix Classic Forms you add four regular Short Answer fields with the labels the snippet expects, then use Dev Mode to set their initial visibility to hidden. Wix's newer form builder and Wix Studio differ again; the capture tool's help documentation covers all three variants and the exact label names.

2. Let the snippet write the values. When a visitor arrives from a Google Ads click, the snippet captures the identifiers and stores them in the browser. On form submission, the values are written into the hidden fields and travel with the rest of the submission.

3. Send the submission to your CRM. Wix Forms does not ship with deep native CRM integrations, but submissions can be pushed to Salesforce, HubSpot, Pipedrive, ActiveCampaign, Zoho, and others through Wix's Zapier integration. The identifiers land on the contact or lead record alongside name, email, and phone.

4. Trigger the conversion at the right milestone. When the lead reaches the milestone you care about — a new deal, a closed-won opportunity — use Zapier or Make to send the conversion to Google Ads. Both tools connect to most CRMs and let you map the captured identifiers back to the correct Google Ads fields.

A field/control map for the CRM path:

What each tracking failure looks like

Not every missing conversion has the same cause. Use this distinction when auditing your setup:

  • Ad blocker: the Google Tag never loads, so nothing the visitor does is recorded. Server-side sends bypass this.
  • Safari cookie expiry: the click is recorded but the link is gone by the time the form is submitted days later. Server-side identity matching can still connect the two.
  • Cross-device journey: the click happens on one device and the form on another. Browser cookies cannot bridge that; server-side identity data can.
  • Double submit: the visitor clicks Submit twice or resubmits after an error. A submit-button trigger records multiple conversions; a successful-submission trigger records one.
  • Thank-you-page false positive: someone reaches the page without submitting the form. Page-view tracking counts a conversion that never happened.
  • Dropped connection: the form submits but the thank-you page never loads. Page-view tracking misses the conversion entirely.

Three reports worth running once conversions are flowing

Accurate conversion data is only useful if you act on it. These three views turn the data into budget decisions.

Conversions by keyword. Most advertisers bid on a spread of keywords across campaigns. This report shows which keywords produce conversions rather than just clicks, so you can move budget toward the ones that pay.

Conversion value by campaign. If you send deal value from your CRM, you can see actual revenue per campaign. A tour operator, for example, may find that a private luxury safari campaign returns far more per client than a group safari campaign. Treating those two as equal hides the more profitable one. Value data makes the comparison visible.

Conversions by geography. Businesses that earn locally — wedding planners, caterers, florists — can break conversions down by country, state, city, or postcode. If clicks are coming from outside your service area, you are paying for leads you cannot serve. Google's Location Bid Adjustments then let you bid more in postcodes that produce customers and pull back where they do not.

What to check before you call it done

Server-side conversion sending gives both your manual bid adjustments and Google's automated bidding better input. But the quality of that input depends on the capture being correct. Before you rely on the numbers, confirm:

  • The four hidden fields exist on every Wix form you care about, with the exact labels the snippet expects.
  • A test ad click produces values in those fields on submission.
  • The CRM record shows the identifiers on the contact or lead.
  • The conversion trigger fires at the milestone you chose, not at both submit and milestone.
  • Conversion value is mapped when you want revenue-based reporting.

If you are still tracking thank-you-page visits or firing browser events through Google Tag Manager, the data going into Google Ads is incomplete, and bidding decisions will reflect that.

Wix Forms to Google Ads field map
FieldWritten byTravels toPurpose
GCLIDCapture snippetWix form, CRM, Google AdsGoogle Click ID for the ad click
GBRAIDCapture snippetWix form, CRM, Google AdsGoogle Ads identifier
WBRAIDCapture snippetWix form, CRM, Google AdsGoogle Ads identifier
User AgentCapture snippetWix form, CRM, Google AdsBrowser context for matching

Field names are exact. The snippet writes values only when a visitor arrives from a Google Ads click; organic visitors will not populate them.

The CRM path, step by step
StageWhat is captured or sentWhere it lives
Ad clickGCLID, GBRAID, WBRAID, User AgentBrowser storage via the snippet
Form submitThe four field values plus name, email, phoneWix form submission
CRM syncSame values on the contact/lead recordCRM via Zapier
MilestoneConversion with identifiers and optional valueGoogle Ads via Zapier or Make

Frequently asked questions

Do I need to write code to track Wix Forms submissions in Google Ads?

Not with the approaches described here. The capture snippet is installed once, and the hidden-field workaround uses Wix's form settings and Dev Mode rather than custom JavaScript. The conversion send is handled by Converly, Zapier, or Make.

Can I count the same lead twice — once at form submit and once at closed won?

You can, but you should not. Pick one milestone per conversion action so Google Ads learns from a single, consistent signal. If you need both a lead count and a revenue count, use separate conversion actions with different names and values.

Why are my Wix form conversions lower than my CRM lead count?

The most common causes are ad blockers preventing the tag from loading, Safari cookie expiry between click and submit, and cross-device journeys. Server-side sending addresses all three. A second cause is a trigger that fires on button click rather than successful submission, which can also inflate or distort counts.

Does Wix Forms connect directly to Salesforce or HubSpot?

Wix Forms does not ship with deep native CRM integrations. Submissions are typically pushed to Salesforce, HubSpot, Pipedrive, ActiveCampaign, Zoho, and others through Wix's Zapier integration.