Skip to content

How to capture Google Ads data in WSForm

Paid search visitors usually arrive already looking for what you sell, so the leads it produces can outperform other channels. The gap is knowing which ad, campaign or ad group earned each lead. This guide shows how to tag your Google Ads URLs, add matching hidden fields to a WSForm form, and let Attribution Analytics fill those fields so every submission carries its campaign context into your CRM, analytics or spreadsheet.

Why campaign-level form data matters

Google Ads can bring in prospects who are actively searching for your product or service, and those leads often convert at higher rates than traffic from channels such as Facebook Ads. That advantage only pays off if you can tell which ads, campaigns and ad groups are producing results. Without that link between a form submission and the ad that drove it, you are optimizing on guesswork. The approach below closes that loop by attaching campaign information to each WSForm entry.

Step 1: Tag your Google Ads with UTM parameters

UTM parameters are short text tags appended to the destination URL of an ad. Analytics and attribution tools read them to determine where a visitor originated. For example, a final URL pointing at a WSForm integration page might carry utm_medium=paidsearch, utm_source=google and utm_campaign=brand-campaign.

A practical convention for Google Ads:

  • UTM Medium = Paid search
  • UTM Source = Google
  • UTM Campaign = your Google Ads campaign name
  • UTM Term = the ad group name the ad belongs to
  • UTM Content = the keyword the person searched for, which ValueTrack parameters can insert automatically

You can choose your own values, but keeping them consistent makes later reporting far easier.

Step 2: Add hidden fields to your WSForm forms

Next, place a set of hidden fields in every lead capture form — for instance your Contact Us or Request a Quote form. The fields to include are:

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

Adding hidden fields to an existing WSForm is a straightforward task; follow the platform's own instructions for creating them.

Step 3: Let {{OWNER_PRODUCT_NAME}} populate the fields

With hidden fields in place, Attribution Analytics monitors how visitors reach your site. When someone completes a form, it writes the Google Ads values derived from the UTM parameters into those hidden fields.

Take a marketer at a file-sharing company whose visitor arrives from a Google Ads campaign. Depending on the UTM values used, the fields could be filled as follows: Channel = Paid search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, Channel Drilldown 3 = Free account ad.

Alongside the UTM values, Attribution Analytics also records the visitor's landing page (for example a cloud-storage features page) and the landing page group (such as 'features').

Step 4: Confirm the data lands in WSForm

On submission, WSForm stores the Google Ads values together with whatever the lead typed in — name, email, phone and so on. From there you can:

  • Review entries in the WordPress dashboard, under the WSForm plugin's Entries section
  • Include the values in new-lead notification emails sent by WSForm
  • Forward them to a CRM such as Salesforce, HubSpot or Pipedrive and report on leads and customers per campaign
  • Export to a spreadsheet and chart leads and customers for each Google Ads campaign

Field map: which value goes where

Use this map to sanity-check a test submission. If a field arrives empty, the corresponding UTM parameter was missing from the ad URL or was not persisted to the page where the form was completed.

What Attribution Analytics handles beyond a single page

Four capabilities matter when you evaluate any capture method:

  1. All traffic sources. Beyond Google Ads, {{OWNER_PRODUCT_NAME}} also classifies leads from Organic Social, Referral, Direct, Paid Social and Organic Search, so channel reports cover every lead rather than only paid clicks.
  2. Cross-page persistence. Simpler methods only work when the UTM parameters sit in the URL of the page where the form is submitted. If a visitor lands on your homepage and later completes a form on a Contact Us page, those parameters are gone. {{OWNER_PRODUCT_NAME}} handles this by storing the UTM parameters in a cookie in the visitor's browser, so they are captured by WSForm no matter which page hosts the form.
  3. Cleaner matching. Teams often mix utm_source=google in some campaigns with utm_source=adwords in others, especially when several people or agencies have managed the account over time. {{OWNER_PRODUCT_NAME}} was built to normalize those differences and still credit the lead to Paid Search.
  4. Landing page context. The landing page URL and its group (for example /blog) are recorded too, so you can report on leads from whole sections of the site and drill down to individual posts.

Two reports worth building first

Once the data reaches your CRM or spreadsheet, start with two views.

Leads by Channel breaks monthly lead counts down by source channel. It gives a high-level read on which channels perform best and where budget should go. If most leads come from Organic Search while most of the budget funds Paid Search, that mismatch is worth revisiting.

Customers by Google Ads campaign shows monthly customer counts per campaign. It reveals which campaigns actually produce new customers and therefore deserve more resources.

Setup checklist

Before you rely on the data, confirm each item:

  • Every active Google Ads URL carries the UTM parameters you intend to report on
  • The keyword slot uses ValueTrack so the searched term is inserted automatically
  • All six hidden fields exist on every lead form, not just the main one
  • A test submission from an ad click fills Channel and all three drilldowns
  • A test submission completed on a second page still fills the fields (cookie persistence working)
  • Entries appear in the WSForm Entries list and in notification emails
  • The CRM or spreadsheet receives the field values

Wrapping up

Tagging ads, adding hidden fields and letting Attribution Analytics fill them gives you a per-submission record of the campaign, ad group and keyword behind each lead. Because the same tool also classifies other channels and records landing pages, your reports can cover every lead source rather than paid search alone.

WSForm hidden field to UTM source map
Hidden fieldFilled fromExample value
ChannelTraffic channel classificationPaid search
Channel Drilldown 1utm_sourceGoogle
Channel Drilldown 2utm_campaignBrand campaign
Channel Drilldown 3utm_content / ad-level valueFree account ad
Landing PageFirst landing page URLdropbox.com/features/cloud-storage
Landing Page GroupLanding page sectionfeatures

Example values follow the supplied illustration; your actual values depend on the UTM parameters you set on each ad.

Diagnosing empty hidden fields
SymptomLikely causeCheck
All fields empty on every submissionNo UTM parameters on ad URLsInspect the final URL of a live ad
Fields empty only when form is on another pageUTM capture limited to the landing page URLConfirm cookie persistence is active
Channel empty but drilldowns filledSource value not recognizedCompare utm_source values across campaigns
Keyword slot emptyValueTrack not configured in UTM ContentReview the ad's tracking template

Causes reflect the mechanisms described in the guide; test with a real ad click before concluding a field is broken.

Frequently asked questions

Do the UTM parameters need to be on the page where the form is submitted?

Not with a cookie-based approach. Simpler methods fail when a visitor lands on one page and completes the form on another, because the parameters are no longer in the URL. Storing them in the visitor's browser cookie keeps them available for the submission regardless of page.

What if some campaigns use utm_source=google and others use utm_source=adwords?

A tool designed to normalize UTM differences can still credit both to Paid Search, so mixed conventions from past agencies or team members do not split your reporting.

Where can I see the captured values after a submission?

In the WordPress dashboard under the WSForm plugin's Entries section, in new-lead notification emails, in a connected CRM, or in an exported spreadsheet.

Can I capture the keyword a visitor searched for?

Yes, by placing ValueTrack parameters in the UTM Content slot so Google Ads inserts the searched keyword automatically.