Track YouTube Ads in Keap: capture campaign data on every lead
You can spend on YouTube Ads and still not know which campaigns create leads, customers or revenue if the campaign information is lost between the click and the form submission. This guide explains a four-step setup that preserves that information and stores it on each Keap contact, so reporting can start from the contact record rather than from visit counts alone.
Why visits alone do not prove ad value
Google Analytics and similar tools can show that an ad produced a visit, but a visit is not a lead, a customer or revenue. If a visitor browses several pages, leaves, returns later, or submits a form on a different page, the original campaign context can disappear unless it is deliberately stored and passed forward.
The approach below closes that gap in four stages: tag the ad, store the source in the browser, copy it into form fields at submission, and let the form submission carry it into Keap. Once those values sit on the contact record, Keap reporting can group outcomes by channel, campaign, ad and landing page.
Step 1: Tag every YouTube ad destination
Add tracking parameters to the destination URL behind each YouTube ad. These are small text additions at the end of the URL that label the medium, source, campaign and ad.
A practical convention for YouTube Ads is:
- UTM Medium = paidsocial
- UTM Source = youtube
- UTM Campaign = the campaign name
- UTM Term = the ad name
For example, a destination could end with utm_medium=paidsocial, utm_source=youtube and utm_campaign=brand-campaign. Keep naming consistent across campaigns, because Keap reports will group by whatever values you supply. A tracking template in the ad platform helps apply the same pattern to every ad instead of typing each URL by hand.
Step 2: Install the snippet and add hidden fields to forms
Install the attribution snippet on your website using the instructions for your site builder, then add hidden fields to each form that should capture source data. The fields described for this workflow are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4.
Most form builders let you add hidden fields by dragging them into the form. Check each form individually: a field added to one form will not automatically appear on another. Also confirm that the field names in your form match the fields you intend to map in Keap, so the values are not captured and then discarded.
Pre-launch checklist:
- Snippet installed on every page where a tracked visitor can land
- Hidden fields present on every lead form, not only the homepage form
- Field names match the intended Keap contact fields
- A test submission produces values in every hidden field
Step 3: Let the stored source populate the hidden fields
When a visitor arrives, the snippet classifies the source into a channel, such as Paid Social, Paid Search or Organic Search, and stores that classification in the browser. Storing it matters because the visitor may look at several pages before deciding to submit a form.
At submission, the stored values are written into the hidden fields. For a YouTube Ads visitor, an illustrative mapping is:
- Channel = Paid Social
- Channel Drilldown 1 = YouTube
- Channel Drilldown 2 = Brand Campaign
- Channel Drilldown 3 = Green Ad
The exact drilldown values depend on the UTM values placed behind the ad. The snippet can also capture the initial landing page and its page group, which makes it possible to see which content, such as a blog post, preceded the lead.
Step 4: Send the values into Keap with the submission
On form submission, the hidden-field values are sent alongside the contact details. With Keap forms, that transfer happens as part of the submission and the values can be viewed on the contact record.
If you use a separate form tool, use the same route you already use to create Keap contacts, whether that is a native integration or a dedicated integration tool, and make sure the hidden fields are included in the data you forward. Test with a separate form tool as well as with Keap forms, because the forwarding step is where values are most often dropped.
Failure distinction to check: if the contact arrives in Keap but the channel fields are blank, the problem is usually in the form or forwarding layer, not in the ad tagging. If the hidden fields are blank on the form itself, check the snippet installation and browser storage. If the fields contain values but the wrong campaign, check the UTM convention on the ad.
Three reports to build once the data is in Keap
Because the same capture applies to every lead, not only YouTube Ads leads, three reports become straightforward once the data is in Keap.
Leads by channel shows monthly lead volume split by source channel. Comparing that view with spend helps reveal whether budget is concentrated where leads actually originate.
Customers by campaign shows monthly customer volume split by YouTube campaign. That view supports shifting budget toward campaigns that produce customers and pausing campaigns that do not.
Revenue by ad shows monthly revenue attributed to each ad. That view supports putting more budget behind ads that generate revenue and pausing ads that do not.
A useful decision sequence is to start with leads by channel to check overall mix, then customers by campaign to check quality, and finally revenue by ad before changing budgets. A campaign can look strong on leads and weak on customers, so the later views prevent a volume-only decision.
Wrap up
Tagging alone does not create attribution. The complete chain is tagging, browser storage, hidden fields, form submission and Keap contact data. When each link is tested, every new contact carries the channel, campaign and ad context needed for reporting, and budget decisions can be based on leads, customers and revenue rather than visits alone.
| UTM parameter | Suggested YouTube Ads value | Purpose in Keap reporting |
|---|---|---|
| UTM Medium | paidsocial | Groups the ad under Paid Social |
| UTM Source | youtube | Identifies YouTube as the platform |
| UTM Campaign | Campaign name | Groups results by campaign |
| UTM Term | Ad name | Groups results by individual ad |
Values are a suggested convention from the captured guide; consistency across ads is required for grouping.
| Hidden field | Illustrative YouTube Ads value | What it identifies |
|---|---|---|
| Channel | Paid Social | Broad channel |
| Channel Drilldown 1 | YouTube | Platform |
| Channel Drilldown 2 | Brand Campaign | Campaign |
| Channel Drilldown 3 | Green Ad | Individual ad |
Illustrative values depend on the UTM parameters placed behind the ad.
Frequently asked questions
Why is website traffic data not enough to judge YouTube Ads?
Standard web analytics shows visits, not downstream leads or customers. Capturing campaign parameters at landing, persisting them in the browser, then passing them through form fields into Keap connects a contact record to the campaign, ad and landing page that produced it.
What UTM values should I use for YouTube Ads?
Use a consistent convention: medium for the paid channel type, source for the platform, campaign for the campaign name, and term for the individual ad. Consistency matters more than the exact labels, because reports group by these values.
Does the setup differ between Keap forms and other form tools?
With Keap forms, the hidden-field values travel with the submission and appear on the contact record. With a separate form tool, forward the same fields through your existing Keap integration or integration tool so they land on the contact record in the same way.