Track the source of leads in Avada forms
When a visitor submits an Avada form, the submission can carry more than the details they typed in. With attribution tracking in place, each lead also arrives with the channel that brought them to the site, the campaign or network behind that visit, and the page where they first landed. That makes it possible to compare channels, campaigns and content sections by the leads they actually generate, rather than by clicks or visits alone.
Set up hidden fields in three steps
Install the attribution code on the site, then add hidden fields to each Avada form. The fields used in this workflow are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Because they stay invisible, visitors see no extra questions and the form experience does not change.
Once the code and fields are in place, the tool records where each visitor came from and writes that information into the hidden fields. When the form is submitted, Avada captures those values alongside the visitor's own details, such as name, phone number or company name.
Checklist before you rely on the data:
- Code installed on every page where forms appear
- All five hidden fields added to each form
- A test submission shows populated channel values
- Notification emails include the attribution fields if you want them in your inbox
- CRM or spreadsheet mapping matches the hidden-field names
What the captured data means
Channel data describes how the visitor reached the site. For a paid social visit, the channel might be Paid Social, with the first drilldown naming the network, the second naming the campaign, and the third naming the advertiser or keyword that triggered the ad. For an organic search visit, the channel might be Organic Search, with drilldowns naming the search engine, the domain used, and the keyword or business name through which the site was discovered, where available.
Landing page data adds a second dimension: the first page the lead viewed and the group that page belongs to. A blog article URL, for example, can be grouped under the blog section, so reports can show which content areas and individual pieces attract leads.
A useful distinction: channel fields answer 'which route brought this lead in?', while landing page fields answer 'which content did they arrive on?'. Reporting is much clearer when both are captured, because a strong channel can still be paired with weak landing content, and vice versa.
Ways to use the data after capture
View submissions in WordPress under Avada > Forms, add the attribution fields to lead notification emails, send the values to a CRM such as Salesforce, Pipedrive or HubSpot, or transfer them to a spreadsheet or Google Sheet for basic reporting.
Three reports are especially useful once the data reaches a CRM:
- Leads by channel: monthly lead counts for Organic Search, Paid Search and Paid Social, to see which channels deliver the most leads.
- Leads by Google Ads campaign: monthly leads broken down by campaign, to separate campaigns that convert from those that only collect clicks.
- Leads by social network: monthly leads per platform, such as Facebook, Twitter and LinkedIn, to focus effort where social leads actually come from.
Getting started
If you want lead-source visibility inside Avada forms, the core work is small: install the tracking code, add the hidden fields, and test one submission end to end. After that, every new lead carries its channel, drilldown detail and landing page into WordPress, email notifications, your CRM or a spreadsheet.
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
| Field | What it tells you | Example use |
|---|---|---|
| Channel | Broad route that brought the visitor | Compare Organic Search, Paid Search and Paid Social leads |
| Channel Drilldown 1 | Network or search engine | Split social leads by platform or search leads by engine |
| Channel Drilldown 2 | Campaign or domain | Compare campaigns or search domains |
| Channel Drilldown 3 | Advertiser, keyword or discovery term | Identify which term or brand drove the lead |
| Landing page and group | First page viewed and its section | Compare blog versus other content sections |
Examples are illustrative patterns from the captured workflow, not live account data.