Skip to content

Track leads and customers from AI in Gravity Forms

Mentions in an AI answer and a visit from an AI tool are only the start of the story. The useful question is whether that visit became a form submission, then a customer, then revenue. Capturing referral data at the moment of submission connects those steps, so AI can be compared fairly with organic search, paid search and paid social.

Why submission-level attribution matters

Visibility tools can show mentions or citations, and analytics can show a session arrived from an AI tool. Neither reliably answers how many of those sessions submitted a form, converted to a paying customer, or produced revenue. Storing the referral context on the lead itself closes that gap, because the channel travels with the contact into downstream reporting.

Set up the hidden fields

First, install the attribution snippet on the website using the provider's installation instructions. Second, open each lead-capture form in Gravity Forms and add hidden fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Give each field a clear label and default value, and enable dynamic population so the attribution tool can fill it at submission time. Third, test a submission and check the entry to confirm the fields were populated rather than left blank.

How the data reaches the entry

On arrival, the attribution tool examines referral signals comparable to those used by web analytics, assigns a channel such as AI Referral, Organic Search, Paid Search or Paid Social, and stores that context in the browser. If the same visitor later completes a form, the tool writes the stored channel, tool, referring domain and landing-page details into the hidden fields. Gravity Forms then saves those values alongside the name, email and other answers the visitor entered.

Use the data after submission

The completed entry can be viewed on the Entries page, included in lead notification emails, or passed to a CRM or spreadsheet. Once the fields are available downstream, reporting can separate AI-driven demand from other channels and follow it through to customer and revenue outcomes. A CRM report, a spreadsheet pivot, or a connected tool such as Tableau, Looker Studio or Microsoft Power BI can all be used for that analysis.

A worked example

Consider a visitor who asks ChatGPT for an architect for a heritage renovation, clicks through, and submits an enquiry form. Channel would be AI Referral, Drilldown 1 would name ChatGPT, Drilldown 2 would record chatgpt.com, and Drilldown 3 would be None. The landing page might be a heritage-renovations project page, with its group recorded as /projects. That combination shows both the AI tool involved and the content that earned the visit, which helps guide future AEO and GEO work.

Four reports to run first

Leads by Channel shows monthly lead volume split across AI Referral, Organic Search, Paid Search, Paid Social and other channels, making AI's share of demand visible. Customers by AI Tool splits new customers by ChatGPT, Claude, Gemini or another referring tool, revealing which tools produce buyers rather than only visits. Close Rate by Channel compares how often leads from each channel become customers; AI leads may arrive already informed by an earlier conversation, so a higher close rate would justify valuing them more highly. Revenue from AI by Landing Page shows customers and revenue per page, identifying the content AI tools cite and send buyers to, and suggesting what to create more of.

A short quality checklist

Before relying on the reports, check that every key form has the six hidden fields, that dynamic population is enabled, and that a test entry contains plausible channel and landing-page values. Then confirm the fields survive routing to the CRM or spreadsheet and that channel names are consistent across forms. Start with leads by channel, add customers by AI tool, and only then interpret close rate and revenue, since those later measures depend on accurate customer and deal data being joined back to the original lead.

Bottom line

Submission-level AI attribution turns a vague question about AI visibility into measurable pipeline and revenue evidence. With the hidden fields in place, teams can see which AI tools send leads, which of those leads close, and which pages earn the revenue. Before committing budget, check the current plan options, any trial period and the applicable terms directly with the provider, since availability and pricing can change.

Captured fields at a glance
FieldWhat it recordsAI-referral example
ChannelBroad referral channelAI Referral
Channel Drilldown 1Specific AI toolChatGPT
Channel Drilldown 2Referring domainchatgpt.com
Channel Drilldown 3Deeper referral detailNone
Landing PageFirst page visitedA heritage-renovations project page
Landing Page GroupSection of the landing page/projects

Drilldown 3 is None for AI referrals because no deeper level is captured.

Frequently asked questions

What do I need to set up in Gravity Forms?

Add the attribution snippet to the site, then add six hidden, dynamically populated fields to each lead form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. When a visitor later submits, the stored referral details are written into those fields and saved with the entry.

What does each captured field mean?

Channel records the broad source, such as AI Referral. Drilldown 1 names the AI tool, Drilldown 2 records the referring domain, and Drilldown 3 is None for AI referrals because there is no deeper level to capture. Landing Page records the first page visited and Landing Page Group rolls that page into its section, such as /projects.

How do I turn the captured data into reports?

Send the entry data to a CRM or spreadsheet, or connect a reporting tool such as Tableau, Looker Studio or Microsoft Power BI. From there you can break leads, customers, close rate and revenue down by channel, AI tool and landing page.