Skip to content

Track Google Ads campaigns in Keap: a 4-step setup

Visitor counts alone do not show whether paid search produces leads, opportunities, or customers. Connecting campaign attribution to Keap lets you report on downstream outcomes by channel and campaign, and compare paid search with organic and other sources before deciding where to spend more.

How the data flow works

An attribution snippet on the site examines where a visitor came from, groups that origin into a channel such as Paid Search, Organic Search, Paid Social, or Direct, and stores the result in a browser cookie. When the visitor submits a form, the stored channel details travel with the form data — name, email, company, and similar fields — into Keap. A resulting contact record can therefore show both who the lead is and which campaign, ad group, and ad brought them in.

Four steps to connect Google Ads data with Keap

Step 1 — Tag every ad URL with UTM parameters. UTM parameters are extra text appended to the destination URL. For Google Ads, use a consistent convention: medium set to paid search, source set to Google, campaign set to the campaign name, term set to the ad group name, and content set to the specific ad. A URL builder can help assemble these consistently.

Step 2 — Add hidden fields to each lead-capture form. Hidden fields are not visible to visitors; they simply receive values programmatically. Add Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders, including Keap forms, Gravity Forms, Jotform, and Typeform, let you drag in a hidden-field type.

Step 3 — Let the attribution tool fill those fields at submission. The values come from the UTM parameters captured earlier. For example, a visitor arriving from a brand campaign in paid search might produce: Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, Channel Drilldown 3 = Free account ad. The first landing page and its group — for example, a features page under the features group — are captured at the same time.

Step 4 — Confirm the data lands in Keap. On each form submission, Keap receives the attribution values together with the lead's contact details. From there, use Keap's native reporting, or a BI tool such as Tableau or Looker for more advanced analysis.

Setup checklist: every ad tagged with the same UTM convention; all six hidden fields present on every form; a test submission checked in Keap for channel, drilldowns, and landing page; inconsistent source spellings reviewed before reporting.

Why this approach beats capturing raw UTM parameters alone

Captures all traffic, not only paid search. Organic Search, Organic Social, Paid Social, and Direct leads are attributed too, so budget decisions can be compared across channels — for instance, shifting spend if most leads arrive organically while most budget goes to ads.

Remembers attribution across pages. Because the data is held in a cookie, a visitor who lands on the homepage from an ad and submits a form on a later page still carries the original campaign data into Keap.

Produces cleaner data. Variants such as different capitalisations or spellings of the same source are mapped to a single channel instead of appearing as separate sources that need manual reconciliation.

Records landing pages. Capturing the first landing page and its group lets you report which content areas — for example, a blog as a whole, or individual posts within it — generate leads and customers.

Three reports to build once the data is in Keap

Leads by channel: count leads each month broken down by channel to see where demand originates and where to prioritise effort, such as investing more in SEO if organic search dominates.

Customers by campaign: count customers each month by the Google Ads campaign that produced them, to identify which campaigns deserve more investment.

Revenue by campaign, ad group, or ad: total revenue by the keyword or campaign that brought in each customer, to guide bid increases on the strongest performers.

Wrap up

Once attribution reaches Keap, you can report on leads, customers, and revenue by campaign instead of relying on clicks and visits alone, and you can compare paid search against every other channel on the same basis. Before committing to a tool, check its current trial terms, pricing, and setup requirements directly, and confirm that the hidden-field workflow fits the forms you already use.

Frequently asked questions

Why can UTM parameters disappear before a form is submitted?

Raw UTM capture only works when the parameters are still present on the form page. If a visitor lands on the homepage from an ad, navigates elsewhere, and then submits a form on a different page, the parameters can be lost. Storing attribution in a browser cookie preserves it across pages until submission.

Why do raw UTM values create messy reports?

Raw values can vary in capitalisation and format — for example, different spellings of the same source — and then appear as separate sources in reports. A channel-mapping tool normalises those variants into one channel, such as Paid Search, so reporting does not need manual stitching.

What is the shortest setup sequence?

Add UTM parameters to each ad, add the six hidden fields to the form, let the attribution tool populate those fields on submission, and then confirm the values arrive in Keap alongside the lead details. After that, build reports by channel, campaign, or revenue.