How to track leads from YouTube Ads in Fluent Forms
Website analytics can count visits, but it rarely tells you which YouTube ad produced a lead, and almost never which ad produced a paying customer. This guide shows how to pass YouTube campaign data through a Fluent Forms submission so each entry carries its own source, then push that data into a CRM where leads, customers and revenue can be reported by channel, campaign and ad.
What you are actually building
The setup has four moving parts: UTM tags on the ad's destination URL, matching hidden fields on the Fluent Forms form, a script that reads the tags and fills those fields, and a destination (WordPress entries, notification email or CRM) where the combined record can be reported on. Each part depends on the one before it, so a mistake in the UTM naming shows up later as a blank or mislabelled report column.
Step 1: Tag the YouTube ad URLs
UTM parameters are short key-value pairs appended to the URL a viewer lands on after clicking your ad. A plain destination such as https://roipaths.com/integrations/fluent-forms becomes a tagged URL once the parameters are added, for example with utm_medium=paidsocial, utm_source=youtube and utm_campaign=brand-campaign. The values are yours to choose, but consistency matters more than cleverness. A common convention for YouTube Ads is:
- UTM Medium = paidsocial
- UTM Source = youtube
- UTM Campaign = the campaign name
- UTM Term = the ad name
Decide the naming pattern before you launch, because every report downstream inherits it.
Step 2: Add six hidden fields in Fluent Forms
In the WordPress admin, open Fluent Forms from the left-hand menu, click Edit under the form you want to use, and drag the Hidden Field field type into the form six times. The six fields to create are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. A fuller walkthrough of adding hidden fields to Fluent Forms is available in the help documentation.
Step 3: Let the attribution script fill the fields
Once the UTM tags are live and the attribution script is installed, it identifies where each visitor came from, including YouTube Ads, and writes the result into the hidden fields on the form. The values written depend on the UTM parameters behind the ad.
Take a gym running YouTube ads for workout routines made with a fitness influencer, Jane Rose. A visitor who clicks the ad and submits the form would produce entries like these:
- Channel = Paid social
- Channel Drilldown 1 = YouTube
- Channel Drilldown 2 = influencer collaboration campaign
- Channel Drilldown 3 = Jane Rose ad 1
The script also records the visitor's first landing page, such as sydneygym.com/workouts/influencer-collaborations/jane-rose, and its category, such as /workouts.
Step 4: Confirm the data lands in Fluent Forms
On submission, the hidden field values are stored alongside whatever the visitor typed, such as name, email and company. From there you have three practical routes:
- Read the record in WordPress under Fluent Forms → Entries, selecting the form from the drop-down.
- Let the new lead notification email include the attribution fields.
- Forward the data to a CRM such as Salesforce, Pipedrive or HubSpot, where its reporting tools can break results down further.
Before trusting the numbers, submit a test entry from a tagged URL and check that all six fields populate as expected.
Why ad-platform numbers alone are not enough
Two different gaps make form-level capture worth the effort. First, ad platform conversion data is not always accurate, particularly after privacy changes such as those in iOS14; a click that leads to a form submission can go uncounted, so the platform may understate how well an ad performed. Second, website analytics is good at counting visitors but cannot follow a lead that closes offline, so it cannot tell you how many customers you gained. To judge whether YouTube Ads are making money, you need lead and customer counts tied to the ad that produced them, which is what capturing the data in Fluent Forms and passing it to a CRM provides.
What good attribution capture adds
Three capabilities separate a reliable setup from a fragile one. Coverage: leads arrive from paid social, paid search, organic search, referral and other channels, so tracking every source gives a complete picture rather than a YouTube-only slice. Persistence: methods that read UTM values only on the submission page lose the data if the visitor browses elsewhere first, whereas storing the details in the visitor's browser cookie carries attribution through to a later form. Landing page context: recording the first landing page and its group shows which parts of the site, such as blog posts or product pages, are drawing the leads in.
Three reports worth running
Once the data reaches a CRM, the useful reports are the ones that change a decision.
Leads by channel shows monthly lead volume across every channel. If organic search is producing most leads while most of the budget goes to paid social, the split is worth revisiting.
Customers by campaign breaks new customers down by the YouTube campaign they came from, so budget can move toward campaigns that actually convert and away from those that do not.
Revenue by ad shows how much revenue each ad generated per month, which informs both ROI assessment and future creative and messaging choices.
Pre-launch checklist
Run through these before spending on the campaign:
- Every YouTube ad URL carries utm_source=youtube and a consistent utm_medium value.
- Campaign and ad names in the UTM tags match the names you will filter reports by.
- The form contains all six hidden fields, spelled exactly as above.
- A test submission from a tagged URL fills Channel, all three drilldowns, Landing Page and Landing Page Group.
- A second test that navigates to another page before submitting still carries the original attribution.
- The CRM mapping places each hidden field in a reportable field, not a free-text note.
Getting started
If the gap between ad spend and reported leads has been hard to close, capturing YouTube Ads data in Fluent Forms and passing it to a CRM is a practical fix. Attribution information travels with each lead, so campaigns and ads that generate the most leads and customers become visible. Trial length, setup time and pricing are set by the provider and should be confirmed on the current signup page before you commit.
| Hidden field | Filled from | Example value |
|---|---|---|
| Channel | UTM Medium | Paid social |
| Channel Drilldown 1 | UTM Source | YouTube |
| Channel Drilldown 2 | UTM Campaign | influencer collaboration campaign |
| Channel Drilldown 3 | UTM Term | Jane Rose ad 1 |
| Landing Page | First page visited | sydneygym.com/workouts/influencer-collaborations/jane-rose |
| Landing Page Group | Landing page category | /workouts |
Example values come from a hypothetical gym scenario used to illustrate the mapping; your own values depend on the UTM parameters you set.
Frequently asked questions
Do I need a CRM, or can I just read entries in Fluent Forms?
Reading entries in WordPress works for checking individual leads, and the notification email can include the attribution fields. A CRM becomes necessary when you want to report leads, customers and revenue by channel, campaign or ad across many records.
What happens if a visitor lands on a tagged page but submits the form somewhere else?
With attribution data stored in the visitor's browser cookie, the original source details still pass through to the form on the later page. Methods that only read UTM values on the submission page would lose them.
Why do Google Ads and Google Analytics numbers differ from my form data?
Ad platform conversion tracking can miss form submissions, especially after privacy changes such as iOS14, so it may undercount. Website analytics counts visitors but cannot see leads that close offline, so it cannot report customer numbers. Form-level capture tied to a CRM fills both gaps.
Which UTM values should I use for YouTube Ads?
A common convention is utm_medium=paidsocial, utm_source=youtube, utm_campaign for the campaign name and utm_term for the ad name. The important thing is to keep the pattern consistent so reports stay readable.