How to track YouTube Ads in Formstack
A YouTube campaign can send a steady stream of visitors to your site while leaving you unable to say which of them became a lead or a customer. Visit counts do not carry a campaign name into your CRM; a tagged form submission can. This guide walks through tagging the ad URL, preparing a Formstack form to receive attribution values, and using the captured records to compare campaigns and ads on leads, customers and revenue.
What the setup needs to capture
Each Formstack submission should carry a small set of source values next to the lead's name and email: the broad channel, three levels of drilldown covering source, campaign and ad, and the first landing page with its group. With those values attached, reporting can group leads and customers by channel, campaign or ad instead of guessing from traffic totals. The work splits into four parts: tag the ad URL, create the hidden fields, let the attribution layer populate them, then read or forward the captured data.
Step 1: Tag the YouTube ad URL with UTM parameters
UTM parameters are short text values appended to the destination URL so the arrival path travels with the visitor. A plain destination page becomes a tagged URL once they are attached. For YouTube Ads, the suggested pattern is: UTM Medium = paidsocial; UTM Source = youtube; UTM Campaign = the campaign name; UTM Term = the ad name. The labels are yours to choose, but keep them consistent across ads so reports stay readable.
Step 2: Create six hidden fields in Formstack
Open the form you want to modify in Formstack. Drag the Short Answer field type from the left-hand menu into the form six times and configure each one as a hidden field. The six fields 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 Formstack forms is linked in the help center.
Step 3: Let the attribution layer fill the fields
With the fields in place, the attribution layer reads where the visitor came from and writes the matching values into the hidden fields, so each submission arrives with its source already completed. It also records the visitor's first landing page and the group that page belongs to, which is separate from the UTM values.
Worked example: a travel agency's Ireland campaign
Suppose a travel agency runs a YouTube Ad pointing to a page where visitors can book an Ireland holiday package through an agent. With the UTM tags in place, the hidden fields would receive: Channel = Paid social; Channel Drilldown 1 = youtube; Channel Drilldown 2 = holiday package campaign; Channel Drilldown 3 = Ireland ad. On the same record, the landing page field would hold the first page the visitor saw, such as a packages page for Ireland, and the landing page group would hold the broader section, such as packages. The lead now shows both the ad that brought the visitor and the content that first attracted them.
Step 4: Read the captured data in Formstack
In your Formstack account, open the Form Builder and select the Submissions tab. The captured attribution values appear in table format alongside the lead's name, email and other answers. From there you can include the values in new-lead notification emails, or send them to a CRM such as Salesforce, Pipedrive or HubSpot so reports can group leads and customers by campaign.
Field-to-value map
Use the table below to check that each hidden field is present and receives the intended value. The example column follows the travel-agency scenario above; your own values depend on the tags and landing page you use.
Why form-level attribution matters
Three practical reasons support tracking leads and customers at the form level. First, ad-platform data can be incomplete: privacy changes such as those in iOS14 reduced some ad-tracking accuracy, so a click that leads to a form submission may not be logged as a conversion. Second, analytics tools are strongest for online transactions and less complete for service businesses or physical locations, where conversions happen offline. Third, proving return on ad spend needs revenue and customer counts, not only visits. A form submission that carries source data closes that gap.
What a dedicated attribution layer adds
A dedicated attribution layer captures the source of all leads, not only YouTube ones, so paid search and organic channels can be compared on the same footing. It stores UTM values in the visitor's browser, so the data survives a browsing session or a later return to the site. It also records the first landing page and its group, which helps identify which content attracts leads and customers.
Three reports worth building
Once the data reaches a CRM, three report shapes are especially useful. A leads-by-channel report shows monthly lead volume per channel and supports budget shifts. A customers-by-campaign report shows how many customers each YouTube campaign produced, making weak campaigns visible. A revenue-by-ad report shows which ads generated the most money, so spend can follow results. Each report depends on the hidden fields being populated consistently and on the CRM receiving them.
Troubleshooting: separate tagging, field and CRM problems
When attribution values are missing or wrong, identify which of three layers failed before changing anything. Tagging problem: the ad's destination URL lacks UTM parameters, or the labels are spelled differently from your reporting labels. Field problem: the six hidden fields are absent from the exact form receiving the submission, or their names differ in capitalization or spacing from what the attribution layer expects. CRM problem: values appear in the Submissions tab but not in the CRM, which points to field mapping rather than ad tags. A quick test submission from a tagged URL, checked in the Submissions tab, tells you which layer to fix.
| Hidden field | Value it should receive | Example |
|---|---|---|
| Channel | Broad channel grouping | Paid social |
| Channel Drilldown 1 | Traffic source | youtube |
| Channel Drilldown 2 | Campaign name | holiday package campaign |
| Channel Drilldown 3 | Ad name | Ireland ad |
| Landing Page | First page the visitor saw | packages/ireland |
| Landing Page Group | Group the landing page belongs to | packages |
Example values illustrate the mapping; actual values depend on the UTM tags and landing page used.
Frequently asked questions
Do I need UTM parameters if I already use ad-platform conversion tracking?
They serve different purposes. Ad-platform conversion tracking records actions the platform can observe, but privacy changes can leave gaps. UTM parameters travel with the visitor to your form, so the submission itself carries the campaign and ad name into Formstack and your CRM.
Why six hidden fields and not one?
The six fields separate different levels of information: the broad channel, three drilldown levels for source, campaign and ad, the first landing page, and the landing page group. Keeping them separate lets reports group by any level without re-parsing a single combined string.
What happens if a visitor leaves the site and comes back later?
The attribution layer stores the UTM values in the visitor's browser. When the visitor returns and completes a form, the stored source data is still passed through, so the lead is not recorded as direct traffic.
Can I use the same setup for other ad channels?
Yes. The attribution layer captures the source of all leads, so the same hidden fields can record paid search, organic search or organic social traffic. The UTM values change, but the Formstack field structure stays the same.