Track YouTube Ads leads in Duda forms
YouTube Ads reporting shows views and clicks, but most businesses need to know whether those clicks became leads, customers, and revenue. This guide explains how UTM parameters and hidden form fields can carry campaign information through to a Duda form submission, so each lead can be reviewed in context.
Why clicks alone do not prove value
Views and clicks describe attention, not business outcomes. For a non-eCommerce business, the missing link is usually what happens after the click: a form submission, a qualified lead, a closed customer, and any revenue that follows. Privacy changes affecting platform tracking can widen that gap, because some conversions may not be counted in the ad platform. A form-level attribution record helps close it by attaching campaign context to the lead itself.
Four-step setup
- Add UTM parameters to each ad destination. UTM parameters are small text additions to a URL that identify how a visitor arrived. A consistent pattern for YouTube Ads is: UTM Medium = paidsocial, UTM Source = youtube, UTM Campaign = the campaign name, and UTM Term = the ad name. Keep naming consistent across campaigns so reports group correctly. 2. Add hidden fields to every relevant Duda form, including contact and quote-request forms. The fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. In Duda, select the form, open the settings icon in the top-right of the form box, choose Edit HTML/CSS, and add the required HTML from the help document. 3. Let the attribution tool populate the fields. When a visitor submits a form, the tool writes the stored attribution values into the hidden fields. Because UTM values are kept in a browser cookie, the data can persist while the visitor browses or returns later. 4. Capture the submission. Duda stores the hidden-field values alongside the visitor's own entries, such as name and email. You can then review responses, include the values in a lead-notification email, or transfer the record to a CRM for reporting.
Worked example: a family-law ad
Consider a family-law firm promoting its services with a YouTube ad. A visitor clicks the ad, browses the site, and later completes a contact form. If the ad URL used the suggested UTM pattern, the submission could carry: Channel = Paid social; Channel Drilldown 1 = youtube; Channel Drilldown 2 = family law services; Channel Drilldown 3 = divorce attorney ad. That record lets the firm distinguish a lead driven by that specific ad from a lead driven by organic search or another channel, instead of treating all form submissions as identical.
Reports worth building
Once attribution values travel with each submission, three reports become practical. Leads by channel shows how many leads each channel produced, which can reveal a mismatch between spending and results — for example, heavy paid-social spend alongside a lead volume dominated by organic search. Customers by campaign compares YouTube campaigns by the customers they generated, separating campaigns that convert from those that only generate views and clicks. Revenue by ad breaks down revenue from new customers by the ad they came from, making it easier to direct further investment toward high-performing ads and reduce customer acquisition cost. The same captured data can also show which landing pages and landing-page groups generate leads, including content such as a blog.
Pre-publish checklist
Before publishing, check that every YouTube ad destination carries the UTM pattern, that each Duda form contains all six hidden fields, that a test submission captures the expected channel and landing-page values, and that the values appear in the response view, notification email, or CRM record you intend to use. If you plan to evaluate a dedicated attribution tool, confirm its current trial terms, pricing, and setup requirements directly with that provider before committing.
| Field | Purpose |
|---|---|
| Channel | Broad channel, such as Paid social |
| Channel Drilldown 1 | Source detail, such as youtube |
| Channel Drilldown 2 | Campaign or service detail |
| Channel Drilldown 3 | Ad-level detail |
| Landing Page | First page the visitor landed on |
| Landing Page Group | Group the landing page belongs to |
Field list as specified for Duda forms; values are populated at submission.
| UTM parameter | Suggested value |
|---|---|
| UTM Medium | paidsocial |
| UTM Source | youtube |
| UTM Campaign | Name of your campaign |
| UTM Term | Name of your ad |
Suggested pattern; values can be personalised if naming stays consistent.
| Report | Question it answers |
|---|---|
| Leads by channel | Which channels produce the most leads? |
| Customers by campaign | Which YouTube campaigns produce customers? |
| Revenue by ad | Which ads produce the most revenue? |
Reports depend on attribution data being captured with each submission and transferred to a reporting tool.
Frequently asked questions
What are the four steps to connect YouTube Ads data to a Duda form?
Add UTM parameters to the destination URL behind each YouTube ad, add the specified hidden fields to the Duda form, let the attribution tool write channel and landing-page values into those fields at submission, and then review, email, or transfer the captured submission.
Which hidden fields should a Duda form include?
The fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group.
What UTM values are suggested for YouTube Ads?
A suggested pattern is UTM Medium = paidsocial, UTM Source = youtube, UTM Campaign = the campaign name, and UTM Term = the ad name. You can personalise values, but consistency matters for reporting.
Why are views and clicks not enough to judge YouTube Ads?
Views and clicks do not show how many leads or customers resulted. Privacy changes can also make platform counts incomplete, and standard web analytics generally does not connect a form lead to later customer or revenue outcomes for non-eCommerce businesses.
Does attribution data survive a return visit?
UTM values are stored in a browser cookie, so attribution data can persist while a visitor browses or returns later and is then passed through when the form is submitted.
What can you do with the captured attribution data?
Review responses in Duda, include the fields in a new-lead notification email, or transfer the submission to a CRM such as Salesforce, Pipedrive, or HubSpot for reporting.