Send Google Analytics channel data into Keap
Google Analytics can show which visits a campaign produced, but that alone does not tell you which campaigns produced leads, opportunities, customers or revenue. Capturing arrival and landing-page information on the lead record closes that gap inside Keap.
How the capture works
A small script placed on the website examines the technical signals available when a visitor arrives. It groups that arrival into a channel, stores the result in a browser cookie, and later writes the stored values into hidden form fields. When the form is submitted, those values are sent to Keap alongside the person's name, email, phone and other contact details.
This matters because a visit and a lead are different outcomes. A channel may drive plenty of traffic yet few enquiries, while a smaller channel may produce fewer visits but more qualified opportunities. Keeping the arrival source on the contact record lets Keap reporting join source to downstream results.
Step 1: Add the hidden fields
Before a visitor submits anything, prepare every lead-capture form with hidden fields for:
- Channel
- Channel drilldown 1
- Channel drilldown 2
- Channel drilldown 3
- Landing page
- Landing page group
Form builders that support hidden fields, such as Gravity Forms or Jotform, make this step straightforward. The hidden fields do not need to be completed by the visitor; they are filled automatically at submission time.
Step 2: See what the fields contain
Consider a marketer running a brand campaign in Google Ads with UTM parameters behind the ads. The completed fields might look like this:
- Channel: Paid search
- Channel drilldown 1: Google
- Channel drilldown 2: Brand campaign
- Channel drilldown 3: Olmo Software
- Landing page: olmosoftware.com/features/best-crm
- Landing page group: features
The channel fields explain the route in, while the landing-page fields explain the content that first attracted the visitor. Together they give a fuller picture than either field alone.
What is captured
Channel data captures the arrival route and its detail. For paid search, that detail can include campaign, ad group and keyword. Landing-page data captures the first page the visitor saw and the category that page belongs to. Grouping related pages together is useful: for example, you can total leads across an entire blog, then drill into individual posts to see which ones generated leads and customers.
Four reports to build first
Once the fields are in Keap, build reports in Keap or in an existing business-intelligence tool. Four practical starting points are:
- Leads by channel: monthly lead volume split by arrival channel, to see where enquiries actually originate and whether spend matches that pattern.
- Opportunities by Google Ads campaign: monthly opportunities split by the specific campaign, to identify campaigns worth keeping or pausing.
- Customers by Facebook ads network: customers split across Facebook, Instagram, Messenger and WhatsApp, since the same ad can perform differently on each network.
- Revenue from organic search by search engine: revenue from leads that arrived through organic search, to judge the return from SEO investment.
For each report, compare the outcome count with the channel or campaign behind it. That comparison is the decision point: shift effort toward sources producing opportunities and revenue, and question sources producing only visits.
Pre-launch checklist
Use this checklist before relying on the reports: the six hidden fields are present on every lead form; a test submission reaches Keap with channel and landing-page values filled in; a paid campaign test shows the expected drilldown detail rather than only a broad channel; landing-page groups roll related pages up correctly, such as a whole blog section; and reports count leads, opportunities, customers and revenue separately, so a high-visit channel is not mistaken for a high-value one. Before adopting the workflow, confirm the current trial terms and setup requirements directly with the tool provider.
| Field group | What it records | Use it to answer |
|---|---|---|
| Channel and drilldowns | Arrival route plus campaign, network or keyword detail | Which channel or campaign produced this lead? |
| Landing page | First page the visitor saw | Which content attracted this visitor? |
| Landing page group | Category of that first page | How did a whole content section perform? |
Example values are illustrative and depend on the UTM parameters and page structure in use.
Frequently asked questions
What must be added to a form before channel data can reach Keap?
Add hidden fields for channel, three channel drilldowns, landing page and landing page group to each lead form. The script then completes those fields from the visitor's arrival data, and the submitted values travel into Keap with the contact details.
What is the difference between channel data and landing page data?
Channel answers how the visitor arrived, such as paid search, paid social, organic search or referral, with extra detail underneath. Landing page answers which content first attracted them, recorded as the first page seen and its category or group.
Which reports become possible once the data is in Keap?
Useful starting points are leads by channel, opportunities by Google Ads campaign, customers by Facebook ads network, and revenue from organic search by search engine. Each connects an arrival source to a later business outcome rather than stopping at visits.