Track Lead Source in Keap: Channels, Drilldowns and Landing Pages
Keap can show which marketing channel produced a lead only when that information is captured before form submission and stored on the record. This guide explains the four-part flow: install the attribution snippet, add hidden form fields, populate them from the visitor's arrival data, and use the resulting fields in Keap reports.
The four-stage setup
A useful attribution setup has four stages. First, place the attribution snippet on the website using the method appropriate to the site builder in use. Second, add hidden fields to each relevant form. Third, allow the tool to classify the visit and write the result into those fields when the form is completed. Fourth, send the completed form data to Keap and build reports from the stored values. Keeping those stages separate makes troubleshooting easier: missing data usually points to the snippet, the field mapping, the form submission or the report definition.
Field map for hidden form fields
The core hidden fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Channel gives the broad category, such as Paid Search, Organic Search or Paid Social. The drilldowns add progressively more specific detail, such as the search engine, campaign, ad, referring domain or keyword. Landing page and landing page group fields can be added where page-level reporting is required. Field names should be consistent across forms so Keap receives comparable values.
How the data is captured and retained
When a visitor arrives, technical arrival signals including UTM parameters and referring domain are examined and grouped into channels comparable to those used in analytics tools. The classification is stored in a browser cookie, so a later visit can still be attributed when the person eventually submits a form. At submission, the stored classification is written into the hidden fields, captured by the form tool and passed to Keap. This cookie step matters because the converting visit is not always the first visit.
Worked examples: paid versus organic search
For a paid search visit, Channel may be Paid Search, Drilldown 1 may identify Google, Drilldown 2 may identify the brand campaign and Drilldown 3 may identify the free trial ad. For an organic visit, Channel may be Organic Search, Drilldown 1 may identify Google, Drilldown 2 may identify the Google domain and Drilldown 3 may identify the keyword where available. These examples show why drilldowns are useful: the broad channel alone cannot distinguish campaigns, ads, domains or search terms.
Landing page and landing page group
Landing page data records the first page a lead viewed, while landing page group summarises the section of the site, such as a blog path. Together they support two levels of reporting: performance by site section and performance by individual page. That distinction helps separate a section that consistently generates enquiries from one particular article or campaign page that does so.
Three reports to build first
Once the fields are in Keap, start with three practical reports. Leads by channel shows monthly volume by broad source and can reveal a mismatch between budget and results, for example when most leads arrive through organic search while most spending goes to paid search. Opportunities by Google Ads campaign breaks monthly opportunities down by campaign, making it easier to identify campaigns that create sales work and campaigns that do not. Customers by Facebook Ads network separates results across Facebook, Instagram, Messenger and WhatsApp so budget can follow the networks that produce customers. Each report answers a different decision: where to invest, which campaign to keep, and which network deserves more spend.
Pre-report checklist
Before relying on reports, check that every form uses the same hidden fields, that values are populated on test submissions, that returning visitors retain their original classification, and that Keap stores the fields on the expected record. Then compare a small sample of records against the known arrival route. If the channel is correct but drilldowns are blank, inspect the field mapping; if drilldowns are correct but Keap is blank, inspect the form-to-Keap submission; if both are correct but reports look wrong, inspect the report grouping and date range.
| Field | Purpose | Example use |
|---|---|---|
| Channel | Broad source category | Paid Search or Organic Search |
| Channel Drilldown 1 | First level of detail | |
| Channel Drilldown 2 | Second level of detail | Campaign or referring domain |
| Channel Drilldown 3 | Third level of detail | Ad or keyword where available |
| Channel Drilldown 4 | Fourth level of detail | Additional campaign detail |
| Landing page | First page viewed | Individual blog or campaign page |
| Landing page group | Site section summary | Blog section |
Field names and values are taken from the captured setup; exact form-tool implementation varies by builder.
Frequently asked questions
What is the basic setup sequence?
Add the site snippet, create hidden fields on your form for Channel and its drilldowns, let the attribution tool populate them from the visit, submit through your form tool to Keap, then report on the stored fields.
How do Paid Search and Organic Search differ in the captured data?
Paid Search can be recorded with the search engine, campaign and ad in successive drilldown fields, while Organic Search records the engine, referring domain and keyword where available.
Can landing page information be stored alongside channel data?
Yes. The first landing page and its group, such as a blog section, are also captured so reports can compare site sections and individual pages.