Skip to content

Track Avada Forms submissions as Google Ads conversions

If your Avada form is where enquiries arrive, your Google Ads reporting is only as reliable as the link between a click and that submission. This guide explains two server-side routes: sending the conversion at submission, or waiting until the lead becomes a customer. It also covers the reports that become useful once that link is in place.

Why browser-based tracking loses conversions

Counting a thank-you page visit is the quickest setup, but it is a fragile proxy. Ad blockers can stop the tag loading at all. Browser privacy features in Safari and Firefox can cut tracking off after roughly a day, breaking the link between a click today and a form submitted days later. A phone click followed by a laptop submission also splits the journey across devices, with no browser link between them. Captured evidence in the source puts the shortfall at up to 30% of real conversions. A page URL also carries no name, email or phone, yet Google Ads expects lead details with each conversion.

Server-side tracking changes the direction of the message. Instead of hoping a browser tag is still present when something happens on screen, your server sends the lead details directly to Google. Ad blockers and browser privacy settings cannot block that message. Google figures cited in the source show a typical 23% average increase in recorded conversions and a 10% reduction in cost per conversion, because bidding algorithms receive more complete data about who converts.

Option 1: Send the conversion when the form is submitted

Choose this route when a form submission is itself the conversion you want to optimise for. A visual builder can watch for a new Avada submission, extract name, email and phone, hash each value with SHA-256, and post the package to Google Ads without custom tag-manager code. It also captures the GCLID, IP address, user agent and other signals that help Google match the event to the exact campaign, ad and keyword.

Decision check before you build:

  • Is a submitted lead valuable enough on its own, or only once qualified?
  • Do you already have a CRM stage you trust as the conversion point?
  • Can you supply name, email and phone on the form for hashed matching?
  • Do you need conversion value attached, which usually comes from a deal record?

If the submission alone is the goal, the immediate route is simpler. If only paying customers count, use the delayed route below.

Option 2: Send the conversion when the lead becomes a customer

This route preserves the click identifier until the commercial outcome is known. The workflow has four stages.

  1. Install the capture tool and add a hidden field. Add the tool's site code, then in Avada Fusion Builder add a Hidden Field element to the form with Field Name set to gclid. That exact name is what the tool looks for when writing the Google Click ID into the submission.
  1. Let the tool store the GCLID. When a visitor arrives from a Google Ads click, the tool reads the GCLID from the URL and stores it in the browser, so it persists while they browse or return another day. On submission, it writes the stored value into the hidden field.
  1. Carry the GCLID into your CRM. The value is saved with the other form fields. Avada keeps submissions under Forms > Form Entries in WordPress admin, and a connector such as Zapier or Make can push the lead, GCLID included, onto the CRM contact record.
  1. Send the conversion at the right stage. Most CRMs do not connect to Google Ads directly, so use Zapier or Make between them. Trigger the send when a lead is qualified, a deal is created, or the customer pays, whichever stage best represents real value for your business.

Three reports to run once conversions flow

Conversions by keyword shows which search terms produce leads rather than only impressions and clicks. For example, a recruiter bidding on executive search in one campaign and temporary staffing in another can see which term earns its budget.

Conversion value by campaign attaches revenue from the deal or opportunity record to each conversion. When one campaign returns $2,000 and another $20,000, shifting budget becomes a clear decision rather than a guess, because clients are rarely worth the same amount.

Conversions by geography breaks results down from country or state to individual postcode. That view suits locally served businesses such as recruiters, law practices and accounting firms. Use Location Bid Adjustments to bid more in postcodes that convert and reduce or stop bidding where clicks come from outside your service area.

Wrap up

Accurate conversion data does two jobs at once. It tells you which keywords and locations deserve more spend, and it gives automated bidding a clearer picture of your ideal lead so ads reach similar people at a lower cost per lead. Start by deciding whether submission or customer status is your conversion point, capture the GCLID from the first visit, and only then connect the CRM stage to Google Ads.

Frequently asked questions

Why do thank-you page and tag-manager methods miss Avada form conversions?

Browser-based methods can miss conversions when ad blockers prevent tags loading, browser privacy limits tracking after about a day, or a visitor clicks on one device and submits on another. Sending the conversion directly from the server avoids reliance on the browser tag remaining present.

How do I send a conversion later, when a lead becomes a customer?

Capture the Google Click ID in a hidden field named gclid when the form is submitted, store it with the lead in your CRM, then use an automation connector to send the conversion to Google Ads when the lead reaches a chosen stage such as qualification, deal creation, or becoming a paying customer.

What lead data is needed for server-side matching?

Name, email and phone are hashed with SHA-256 as required by Google, together with the GCLID, IP address, user agent and other matching signals, so Google can match the submission to the campaign, ad and keyword that produced the click.