Track Facebook Ads Through Duda Form Submissions
Visitor counts alone do not show whether paid social is producing enquiries. This guide explains how to attach campaign information to a Duda form submission, so each lead carries the channel, campaign, ad set and individual ad that brought the visitor to the site.
Why visitor data is not enough
Google Analytics can show how many visits arrived from Facebook, but that does not reveal how many of those visits became enquiries. Without lead-level attribution, a campaign that produces clicks but no customers can look identical to one that produces valuable business.
The fix is to preserve campaign details from the first landing page through to the moment a visitor submits a form. When that information travels with the submission, you can judge advertising by leads generated rather than traffic alone.
Setup checklist
Use this sequence before testing a form:
- Confirm every Facebook destination URL carries consistent UTM values.
- Install the attribution code on the Duda site so visitor origin can be detected.
- Add the required hidden fields to each form you want to measure.
- Submit a test form from a tagged link and check that the values appear in the response.
- Decide where the completed record should go: the Duda dashboard, an email notification, a CRM or a spreadsheet.
Skipping the test is the most common failure point. If the landing URL has no UTM parameters, or a hidden field is missing, the submission may be stored without the campaign detail needed for reporting.
1. Tag each ad destination with UTM parameters
UTM parameters are additional text appended to a destination URL. They let you label a visit with the medium, source, campaign, ad set and creative that generated it.
A practical convention for Facebook advertising is:
- Medium: paid social
- Source: Facebook
- Campaign: the campaign name
- Term: the ad set name
- Content: the specific ad
Keep naming consistent across campaigns. If the same campaign is spelled differently in different URLs, reports will split it into separate entries.
2. Install the attribution code on the Duda site
Once the site code is in place, the attribution system can detect where a visitor came from and prepare that information for a form. The code must be added to the Duda website using the provider's installation instructions.
3. Add hidden fields to the form
Hidden fields store attribution values without asking the visitor to complete extra questions. Add fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group.
Those six fields provide a useful map:
- Channel identifies the broad source, such as paid social.
- The three drilldown fields can hold the network, campaign and ad-level detail.
- Landing Page records the first page the lead arrived on.
- Landing Page Group rolls that page up into a broader section, such as a product or integrations area.
4. Check what is written into each submission
After setup, the system writes the detected values into the hidden fields when a form is submitted. For example, a lead arriving from a Facebook brand campaign using a red creative could be recorded as paid social, Facebook, brand campaign and red ad. The same submission would also record the initial landing page and its group.
That example shows why naming matters: the drilldown values are only as clear as the UTM values used on the ad. A vague campaign name produces a vague lead record.
Where to use the captured data
Captured values can be reviewed in the Form Responses area of the Duda dashboard. They can also be included in the notification email sent when a form is submitted, which is useful when enquiries are handled directly from an inbox.
For longer-term analysis, send the fields to a CRM such as Salesforce, HubSpot or Pipedrive, or to a spreadsheet through a tool such as Zapier. A spreadsheet supports charts and graphs, while a CRM supports lead-level reporting alongside other customer data.
Three reports worth building first
Leads by channel gives a monthly overview across paid social, organic search, paid search, organic social and other sources. Use it to decide where budget and effort should shift.
Leads by network separates results across the placements where Meta ads may appear, including Facebook, Instagram and potentially Messenger or WhatsApp. That view helps identify which network is producing enquiries, not just impressions.
Leads by campaign breaks results down by campaign name. This is the clearest check on whether spending is generating enquiries or only clicks and visits that do not convert.
Getting started
Start with one tagged campaign and one form, verify the hidden-field values in a test submission, then expand the same convention to other campaigns. Once the data is flowing, compare leads by channel, network and campaign before changing budgets.
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
| Hidden field | What it records | Example use |
|---|---|---|
| Channel | Broad acquisition channel | Paid Social |
| Channel Drilldown 1 | Network or source detail | |
| Channel Drilldown 2 | Campaign detail | Brand Campaign |
| Channel Drilldown 3 | Ad-level detail | Red Ad |
| Landing Page | First page visited | Product landing page |
| Landing Page Group | Broader page section | Product section |
Example values depend on the UTM parameters used on each ad.