How to track Facebook Ads in Keap
Facebook's own dashboard can tell you how many clicks and form fills an ad produced. It cannot tell you which of those leads became an opportunity, closed as a customer, or generated revenue — that record lives in Keap. Closing that gap means carrying the ad's identity all the way from the landing page into the contact record, so the campaign name is sitting next to the deal value when you report.
This guide walks through the four setup steps, shows exactly which hidden field receives which piece of ad data, and explains what each resulting report is good for. It also covers the three most common reasons a campaign shows up blank, so you can tell a form problem apart from a tagging problem.
Why Keap alone doesn't answer the ad question
A contact created in Keap usually knows its name, email and phone. What it rarely knows is the path that produced it. Without that, you can count leads but not compare them: a Facebook lead and an organic search lead look identical in the database, even though they cost very different amounts to acquire.
The fix is to attach attribution data at the moment of form submission. A small script on your site reads how the visitor arrived, sorts them into a marketing channel, and stores the result in the browser. When the form is submitted, that stored value is written into hidden fields and travels with the contact into Keap. From there, ordinary reporting on those fields answers questions like:
- How many leads did Facebook Ads produce, and how does that compare with SEO or Google Ads?
- Which campaigns and ad sets generated the most opportunities?
- What is the close rate on Facebook-sourced opportunities versus other sources?
- How much revenue came from Facebook Ads, and does it exceed total ad spend plus creative and agency costs?
Step 1: Install the tracking script and add hidden fields
Sign up for the trial, then place the provided snippet on your website following the installation guide. The snippet needs to load on every page a visitor might land on or submit a form from — not just the landing pages you use for ads.
Next, add these five hidden fields to your lead capture forms. The names matter, because the script looks for them:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Channel Drilldown 4
Most form builders let you drag in a hidden field type, or mark an existing field as hidden in its settings. Keap forms have their own instructions; if you use Gravity Forms, Wix Forms, Webflow or a similar tool, follow the equivalent guide for that builder.
Before moving on, submit a test form yourself and confirm all five fields arrive in Keap as contact fields. A hidden field that exists on the page but is not mapped to a Keap field will silently drop its value.
Step 2: Tag every Facebook ad URL with UTM parameters
UTM parameters are short text labels appended to the destination URL. They are how the ad identifies itself to your website. A tagged link looks like the destination path followed by a question mark and key-value pairs, for example a medium of paidsocial, a source of facebook and a campaign name of brand-campaign.
The convention below is the one that maps cleanly onto the five hidden fields. Pick it once and apply it consistently across every ad:
- utm_medium = Paid social
- utm_source = Facebook
- utm_campaign = the campaign name
- utm_term = the ad set name
- utm_content = the specific ad
Free UTM builders exist if you would rather not type the query string by hand. The important discipline is naming: use the same spelling and capitalisation for the same campaign every time, so reports group correctly rather than splitting one campaign into three rows.
Step 3: How ad data lands in the hidden fields
When someone clicks a tagged ad, the script reads the parameters and stores them in a cookie in that visitor's browser. The cookie is what makes the setup survive browsing: a visitor can read three blog posts and submit a form on a completely different page, and the original ad data still goes through.
At submission, the stored values are written into the hidden fields alongside the lead's name and email. Take a hypothetical marketer promoting a CRM product. A visitor clicks one of their ads, browses the site, then requests a demo. If the ad carried the standard tags, the contact would be classified as Paid Social, with the campaign, ad set and ad names sitting in their drilldown fields — see the mapping table below for the exact field-to-parameter pairing.
Two further values are captured: the landing page URL (for instance a deal-management feature page) and the landing page group (for instance /features). Those tell you which content attracted the lead, separately from which ad brought them.
Step 4: Confirm the data reaches Keap and choose a reporting route
The channel values travel into Keap together with the contact's name, phone and email. Once they are there, you have two reporting routes.
Use Keap's native reporting when you want quick answers inside the tool you already work in — counts and groupings by channel or campaign. Export the data when you need cross-channel charts, blended spend figures or a dashboard shared with people who do not log into Keap; a BI tool such as Google Data Studio or Power BI can build those from the export.
Whichever route you pick, verify first. Open a contact created from a test ad click and check that Channel reads Paid Social and that the drilldowns contain the campaign, ad set and ad names you expect.
Which hidden field receives which value
The mapping below is the practical core of the setup. If a report column is empty, this table is the first place to look — it shows which UTM key feeds which field, and therefore which tag is missing when a value does not appear.
A useful habit is to keep this mapping next to your ad naming document. When someone proposes a new parameter or a different naming scheme, you can see immediately whether it will land in a field Keap can report on, or disappear.
What this approach adds beyond a single ad tag
Passing UTM values straight into a form field is possible without a script, but it only works when the form is on the page the ad points to. Four properties make the cookie-based approach more durable:
- It captures other channels too. Direct, referral, organic social and organic search leads get classified as well, so Facebook numbers have a real comparison base rather than sitting alone.
- It remembers. Because values are stored in the browser, the form's page does not have to match the landing page.
- It normalises inconsistencies. Variants such as a source of facebook in one campaign and facebook.com in another are reconciled to the same channel instead of creating a phantom second source.
- It captures landing page data. The full landing page URL and its group are recorded, so you can see which content attracts leads and customers, not just which ad.
Three reports worth building first
Once the fields are populated, start with three views. Each answers a different decision.
Leads by channel. A count of leads split by channel, colour-coded, gives you the share each source contributes. Use it to sanity-check that Facebook is being classified as Paid Social at all, and to see how it stacks up against the rest of your mix.
Customers by campaign. New customers per month, broken down by originating campaign, shows which campaigns actually convert rather than merely attract. Budget and optimisation time should follow the campaigns that appear here, not the ones with the cheapest clicks.
Revenue by campaign. Revenue per month by originating campaign is the closest thing to a return figure. Compare it against everything you spent to run those ads — media, agency fees, creative production — and a campaign that returns more than it costs is worth continuing. The same view broken down per campaign tells you which to scale and which to stop.
When a campaign shows up blank: three different failures
A missing campaign name in Keap can come from three unrelated causes, and fixing the wrong one wastes time. Work through them in this order.
- The field is not reaching Keap. The hidden field exists on the form but is not mapped to a contact field, or the form was published before the field was added. Symptom: every contact shows an empty value, including test submissions you tagged yourself.
- The tag is missing or malformed. The ad's URL has no utm_campaign, or uses a different key. Symptom: Channel and Channel Drilldown 1 populate, but Drilldown 2 is empty for that campaign only.
- The cookie did not persist. The visitor blocked cookies, or submitted on a different domain or subdomain from the one the script runs on. Symptom: intermittent gaps that cluster around certain browsers or certain entry paths.
Testing one tagged link end to end — click, browse to a second page, submit, then inspect the contact — distinguishes all three in a single pass.
Getting started
The setup is four steps: install the script and add five hidden fields, tag your ad URLs consistently, let the cookie carry the values into the form, and confirm the data arrives in Keap before you build reports on it. Done once, it keeps classifying leads from every channel, not only the paid ones.
A trial is available if you want to test the flow against your own forms before committing.
| Hidden field | Fed by | Example value from the worked demo |
|---|---|---|
| Channel | Marketing channel classification | Paid Social |
| Channel Drilldown 1 | utm_source | |
| Channel Drilldown 2 | utm_campaign | Brand Campaign |
| Channel Drilldown 3 | utm_term | North America Ad Set |
| Channel Drilldown 4 | utm_content | Green Ad |
| Landing page | Page the visitor first landed on | keap.com/features/deal-management |
| Landing page group | Group of the landing page | /features |
Example values come from the guide's illustrative demo, not from a live account. The landing page and landing page group are captured in addition to the five hidden fields.
| Symptom | Likely cause | Where to check |
|---|---|---|
| Every contact has an empty value, including your own tagged test | Hidden field not mapped to a Keap contact field, or form published before the field was added | Form field settings and Keap field mapping |
| Channel and Drilldown 1 populate but Drilldown 2 is empty for one campaign | Missing or differently spelled utm_campaign on that ad's URL | The ad's destination URL |
| Gaps appear intermittently across browsers or entry paths | Cookie blocked, or form submitted on a different domain from the script | Browser cookie settings and domain coverage |
Ordered diagnostic checklist; the three causes are independent and can co-occur.
Frequently asked questions
Do I have to use exactly those five hidden field names?
Yes — the script writes to fields by those names: Channel, Channel Drilldown 1 through 4. Rename them and the values have nowhere to go. You can relabel what users see, but the underlying field names must match.
What if a visitor submits a form on a page other than the ad's landing page?
That is the normal case and it still works. The parameters are held in a cookie in the visitor's browser, so the form's location does not matter as long as it is on the same site the script runs on.
Does this only track Facebook traffic?
No. Leads arriving from direct, referral, organic social and organic search are also classified, which is what makes a Facebook-versus-everything-else comparison possible.
What happens if my UTM tags are inconsistent between campaigns?
Variants such as facebook and facebook.com are reconciled to the same channel rather than creating a duplicate source. Consistent naming still matters for campaign-level grouping, where a misspelling will split a campaign into separate rows.
Can I report on this outside Keap?
Yes. Keap's native reporting handles in-tool views, and exporting the data lets you build dashboards in a BI tool such as Google Data Studio or Power BI.