Skip to content

Capture Google Ads Data in Duda Forms

A Duda form can record more than the details a visitor types. With UTM-tagged ads, hidden attribution fields and browser-side persistence, each submission can also show which campaign, ad group, ad, landing page and broader channel produced the lead.

What the setup is meant to prove

Knowing that a lead arrived is not enough when several campaigns compete for budget. Attribution attached to the submission lets you compare the campaign, ad group, specific ad and entry page behind each enquiry, then direct more spending toward the combinations that produce enquiries and revenue.

The setup has four parts: tag the ads, prepare the form, retain the attribution values during the visit, and use the completed fields after submission.

1. Tag every Google Ads destination consistently

UTM parameters are appended to the destination URL so the receiving system can identify the campaign source. A consistent Google Ads convention is:

  • Medium: paid search
  • Source: Google
  • Campaign: the Google Ads campaign name
  • Term: the ad group name
  • Content: the specific ad

For example, a destination URL can carry paid-search, Google and brand-campaign values in its medium, source and campaign parameters. Apply the same convention across campaigns so later reporting does not fragment one source into several labels.

2. Add the six hidden fields to the form

Add these hidden fields to each lead-capture form, such as a contact or quote-request form:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

These fields stay out of the visitor's way while giving the submitted record a structured place for attribution and entry-page information.

3. Keep the values through the visit and populate the fields

When a visitor arrives from a tagged ad, the attribution values are retained in a browser cookie. If the person then moves through the site and completes a form on a different page, those values can still be written into the hidden fields at submission.

In the worked example, a click on a brand-campaign paid-search ad produces:

  • Channel: Paid search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand campaign
  • Channel Drilldown 3: Free account ad

The first landing page and its page group are captured alongside those channel values. This distinction matters because a raw URL parameter approach can lose the original values when the form is not on the entry page.

4. Use the completed submission

At submission, the attribution fields travel with the visitor-supplied name, company, phone, email and other form answers. The completed record can then be included in a lead-notification email, passed to a CRM such as Salesforce, Pipedrive or Keap, or used in reports comparing campaigns, ad groups, keywords, landing pages and channels.

Capturing non-Google traffic as well creates a fuller picture. A report can compare paid search with organic search, organic social and paid social instead of showing only the leads that came from Google Ads.

Why normalization and landing-page fields improve reporting

Raw UTM values are vulnerable to inconsistent capitalization and naming. Values such as Google.com, google and adwords may all refer to the same source, yet raw reporting can treat them as three sources. Normalizing the values into a consistent Paid Search channel keeps campaign reporting cleaner.

Landing-page capture adds another useful cut. Recording both the exact entry page and its group makes it possible to compare individual articles or product pages with broader site sections such as a blog or features area.

Pre-publish checklist

Before publishing the setup, check that every ad destination uses the same UTM convention, all six hidden fields exist on each lead form, a multi-page visit still populates the fields, inconsistent source spellings resolve to one channel, and the submitted record reaches the intended email or CRM destination with the attribution values intact.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

Hidden-field map
FieldPurpose in the submission
ChannelBroad source category, such as Paid Search
Channel Drilldown 1More specific source, such as Google
Channel Drilldown 2Campaign-level detail
Channel Drilldown 3Ad-level detail
Landing PageFirst page visited
Landing Page GroupSection containing that first page

Use the exact field names listed in the setup so downstream email, CRM and reporting mappings remain consistent.

Frequently asked questions

What happens if a visitor lands on one page and submits a form on another?

No. The attribution values are stored in a browser cookie when the visitor first arrives, so they remain available if the person browses to another page before submitting a form.

Why not simply pass the raw UTM values into the form?

Raw values can split one source into several labels when capitalization or naming differs. Normalizing those values into a consistent channel prevents the same source from appearing as multiple separate sources in reports.

Where can the captured attribution data be used after submission?

The captured fields can be included in the notification email, sent to a CRM, or used in reporting to compare campaigns, ad groups, keywords, landing pages and other channels.