Skip to content

Capture Google Ads data in Avada forms

Form submissions alone do not show which campaign, ad or keyword produced a lead. Adding attribution fields to an Avada form connects each submission to the paid-search visit that preceded it, making it possible to compare campaigns by leads, customers and revenue rather than clicks alone.

Why downstream attribution changes budget decisions

Visitors and completed forms are useful starting points, but they do not reveal whether a campaign produced profitable customers. Consider a fencing business spending $2,000 on each of two campaigns. The Pool Fencing campaign brings 200 visitors and 20 leads, while Backyard Fencing brings 100 visitors and 10 leads. On those measures alone, Pool Fencing looks stronger.

Adding downstream results changes the picture. The table shows Pool Fencing producing 2 customers and $8,000 in revenue, and Backyard Fencing producing 5 customers and $25,000. Note on source figures: the captured narrative conflicts with that table. It states Backyard customers as 5 compared with Pool as 4, conversion as 25% versus roughly 13%, average customer value as $200 per customer compared with $150, customer acquisition cost as $200 compared with $250, and return on ad spend as 100% compared with 60%. Those narrative figures are preserved here as captured, and they do not align with the table totals, so do not treat either set as reconciled. The lesson remains that budget decisions need customer and revenue attribution, not only traffic and form completions.

Step 1: Tag Google Ads destinations consistently

Use a consistent UTM convention so campaign, ad group and ad can be distinguished later. A practical mapping for Google Ads is:

  • UTM Medium: Paid Search
  • UTM Source: Google
  • UTM Campaign: the campaign name
  • UTM Term: the ad group name
  • UTM Content: the specific ad

Apply those values to the destination URL. For example, a campaign URL can carry paid-search, Google and campaign values as query parameters. Consistency matters more than the exact labels, provided the same convention is used across campaigns.

Step 2: Add six hidden attribution fields

Add six hidden fields to the Avada form:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

In WordPress, open the form, choose the element control, select Hidden Field, and configure each field according to the attribution setup instructions. Hidden fields keep the form visually unchanged while allowing the submission to carry attribution values.

Step 3: Let attribution populate the fields at submission

When a tagged visitor submits the form, the attribution tool populates the hidden fields from the stored visit data. In a copywriting-firm example, the fields could record Paid Search as the channel, Google as the first drilldown, the new-client campaign as the second drilldown, and a discounted-rate ad as the third drilldown. The visitor's name, email and other entered details are submitted alongside those values.

Checklist before launch:

  • Confirm every Google Ads destination uses the same UTM convention
  • Confirm all six hidden fields are present on each lead form
  • Submit a test form from a tagged campaign URL
  • Check that channel, drilldowns and landing-page fields are populated
  • Test a visit that moves to a different page before submitting
  • Confirm the values appear in the form entry, notification or CRM record

Step 4: Use the captured data in entries, notifications and CRM records

Captured values can be reviewed in the WordPress dashboard under Avada Forms, included in a lead notification email, sent to a CRM such as Salesforce, Pipedrive or HubSpot, or used in reports comparing campaigns by leads and customers.

Four distinctions make this approach more reliable than storing raw UTM parameters alone:

  • It records all traffic sources, not only Google Ads, including Organic Search, Paid Social and Organic Social.
  • It stores attribution in a browser cookie, so moving between pages before submitting does not erase the original visit data.
  • It normalises inconsistent source values, such as different capitalisation or domain variants, into a consistent channel.
  • It also records the first landing page and its category, allowing content groups and individual pages to be compared.

Three reports to build from the captured fields

Three reports make the captured fields immediately useful:

  • Leads by Channel: monthly lead volume by source channel, useful for checking whether spend matches the channels producing demand.
  • Customers by Google Ads Campaign: monthly customer volume by campaign, useful for identifying campaigns worth expanding or closing.
  • Revenue by Keyword: revenue from new customers grouped by the keyword that triggered the ad, useful for directing more budget toward proven search terms.

Together, these views move reporting from campaign activity to commercial outcomes.

Summary

With UTM tagging, hidden fields and stored attribution in place, each Avada submission can identify the campaign, ad and keyword behind the lead while also supporting broader channel and landing-page reporting. {{OWNER_TRIAL_TERMS}}

Fencing campaign comparison
MeasurePool Fencing CampaignBackyard Fencing Campaign
Spend$2,000$2,000
Visitors200100
Leads2010
Customers25
Revenue$8,000$25,000

Illustrative example figures from the captured source. Narrative derived figures in the source conflict with these table totals and are flagged in section s1.

Frequently asked questions

What if a visitor lands on one page but submits the form on another?

No. The attribution data is stored in a browser cookie when the visitor first arrives, so it can still be written into the form even if the submission happens on a later page.

Why not simply store the raw UTM values?

Raw values can fragment reporting when the same source is written in different ways. Normalising them into a consistent channel, such as Paid Search, makes campaign reporting easier to read and compare.

Can this approach record sources other than Google Ads?

Yes. The same hidden-field approach can record other sources, including Organic Search, Paid Social and Organic Social, so reports are not limited to paid search.

Pool Fencing CampaignBackyard Fencing Campaign
Spend$2,000$2,000
Visitors200100
Goal Completions2010
Pool Fencing CampaignBackyard Fencing Campaign
Spend$2,000$2,000
Visitors200100
Leads2010
Customers25
Revenue$8,000$25,000