Track YouTube Ads leads in Webflow forms
YouTube Ads can send visitors to a Webflow site, but a visit is not a lead, a customer, or revenue. To judge an ad you need to carry its source information forward to the moment someone submits a form, then join that submission to the eventual customer outcome.
Four steps from ad click to captured lead
A four-step setup connects an ad click to a form submission:
- Tag every YouTube ad destination URL with UTM parameters so the campaign, ad and channel are identifiable on arrival.
- Add six hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. In Webflow, place an Embed element just above the submit button and below the last visible input, then add the hidden-field markup there.
- When a visitor lands, the attribution tool identifies the source and writes the values into those hidden fields at submission time.
- Webflow captures the hidden values together with the visitor-entered details such as name and email.
Checklist before launch: every ad URL is tagged, every lead form has all six hidden fields, a test submission shows populated values, and the values appear in the destination you will report from.
Tagging convention and a worked example
A consistent tagging convention keeps reporting clean. Use paidsocial as the medium, youtube as the source, the campaign name as the campaign, and the ad name as the term. For example, a destination for a Webflow integration page could carry utm_medium=paidsocial, utm_source=youtube and utm_campaign=brand-campaign.
Worked example: a cooking school promotes online baking classes. A viewer clicks the ad, lands on a classes page, and submits a form. The captured fields could read: Channel = Paid social; Channel Drilldown 1 = YouTube; Channel Drilldown 2 = online class campaign; Channel Drilldown 3 = baking basics ad. The landing page and its group are recorded separately, for example a baking-basics class page in a classes group. That separation lets you answer two different questions: which ad produced the lead, and which page first attracted them.
What to do with the captured data
Once captured, the data can be used in several places:
- In Webflow, open Site Settings, then Forms, to view submissions or download them as CSV.
- In a new-lead notification email, so the source is visible as soon as a lead arrives.
- In a CRM such as Salesforce, Pipedrive or HubSpot, where built-in reporting can chart leads and customers by source.
Three reports are especially useful. Leads by channel places every source side by side so YouTube can be compared with organic search, paid search and organic social. Customers by campaign compares campaigns within YouTube month by month, helping you shift spend toward the campaigns producing customers. Revenue by ad shows which creative and message earned the most, supporting return-on-investment decisions.
Two gaps explain why this extra capture matters. Platform conversion reporting can miss conversions when privacy changes limit tracking, and web analytics alone cannot show which leads became customers or what they paid. Joining the form-level source to later customer and revenue records closes that gap.
Cover all channels and return visits
The same capture should cover every channel, not only YouTube, so all leads can be compared on one basis. Because attribution values are stored in the browser, a visitor who leaves and returns can still have the original source passed through on a later form submission. Landing page and landing page group data add a content view: you can see whether a blog, a product page or a class page is attracting the leads that convert.
| Hidden field | What it records | Example value |
|---|---|---|
| Channel | Broad channel | Paid social |
| Channel Drilldown 1 | Source platform | YouTube |
| Channel Drilldown 2 | Campaign | online class campaign |
| Channel Drilldown 3 | Ad | baking basics ad |
| Landing Page | First page visited | classes/baking-basics page |
| Landing Page Group | Group of that page | classes |
Values are populated at form submission from the visitor's arrival data.
Frequently asked questions
Why is visitor traffic not enough to judge YouTube Ads?
Visitor counts alone do not show whether a lead later became a customer or how much revenue followed. Capturing channel, campaign and ad identifiers with the form submission lets that later outcome be joined to the original click in a CRM.
What if someone leaves and returns before submitting a form?
Store the attribution values in the browser so a return visit can still pass the original source through when a form is completed later. Also record the first page visited and its group to see which content attracted the lead.
What UTM convention should YouTube Ads use?
Use a consistent convention: paid social for medium, youtube for source, the campaign name for campaign, and the ad name for term. Consistency matters more than the exact labels, as long as reporting uses the same values.