Skip to content

Track SEO Leads and Customers in Keap

Visitor counts alone do not show whether organic search creates enquiries, sales, or revenue. This guide explains how to attach channel and landing-page information to every form submission, send it into Keap, and report on the results.

Why form-level attribution matters

Analytics platforms can show sessions from search, but they usually stop before a visitor becomes a named contact. The missing link is form data: when a person submits a form, the record should also carry how they arrived and which page first brought them to the site. Once that information is stored on the Keap contact, reporting can move from traffic to pipeline and revenue.

Set up the capture fields

Install the attribution snippet on the website, then add six hidden fields to each relevant form: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; and Landing Page Group. Most form builders let you insert a hidden field directly or hide an existing field in its settings. Check every form that should create a Keap lead, including contact and quote-request forms, rather than only the homepage form.

How the data reaches Keap

On arrival, the tool classifies the visit into a channel such as Organic Search or Paid Social and stores that classification in the browser. At submission, it populates the hidden fields. The form tool then captures those values together with the details the visitor typed, such as name and email. If Keap's own form builder is used, the values flow directly into Keap. With a third-party builder, use its native Keap integration or an intermediary such as Zapier. After delivery, Keap holds both the contact details and the acquisition context on the same record.

What each field tells you

Two groups of fields answer different questions. Channel fields explain discovery: the broad channel, the source, the referring domain, and, when available, the search term. Landing-page fields explain content: the exact first page and its group, such as a blog or templates section. For example, a search visit might be recorded as Paid Search, Google, www.google.com, and a Sydney real-estate query, with a blog article as the landing page and /blog as its group. That combination lets a team separate search-engine context from the content that earned the visit.

Three reports to build first

Use three starting reports. First, Leads by Channel compares monthly lead volume across Organic Search, Paid Search, Paid Social, and other channels, showing whether SEO enquiries are growing as content and links increase. Second, Customers from Organic Search by Landing Page Group counts new customers by sections such as Home, Blog, and Services, revealing which site areas produce buyers rather than only traffic. Third, Revenue from Organic Search by Landing Page connects customers and revenue to individual pages, helping prioritize the content to expand or improve. Run the reports monthly and compare periods before changing the content plan.

Example: using template pages to prove SEO value

A captured example from an HR software company illustrates the decision value. Free HR templates were published as individual landing pages and drew tens of thousands of monthly visits, but traffic alone did not prove conversion. Channel, landing page, and landing-page-group values were passed with demo requests into the CRM, allowing the team to report leads, customer conversion, and revenue by template. The reported outcome was a 2.4x rise in new leads at near-zero cost per lead, followed by expansion of the template library and a reported 4x growth in monthly leads. Treat those figures as dated, unverified captured evidence from that account, not as a general promise.

Quick verification checklist

Before relying on the reports, submit a test form from an organic-search visit and confirm all six fields arrive in Keap. Then check a paid or social visit to ensure channels are not blended. Finally, confirm that landing-page groups match the site structure. If a field is blank, inspect the form's hidden-field names and the delivery integration first; the reporting layer cannot recover acquisition data that was never submitted.

Hidden-field map
FieldQuestion it answers
ChannelWhich broad channel brought the visitor?
Channel Drilldown 1Which source, such as Google?
Channel Drilldown 2Which referring domain?
Channel Drilldown 3Which search term, when available?
Landing PageWhich exact page did the visitor land on?
Landing Page GroupWhich site section contains that page?

Field names are the six hidden fields listed in the setup step.