Capture Google Ads data in Tally Forms
Visitor counts alone do not show whether advertising is producing enquiries. By attaching campaign information to every Tally Forms submission, you can connect a named lead to the campaign, ad group, keyword and landing page that brought that person to the site.
Why form-level attribution matters
Google Ads can drive enquiries, but a visit is not the same as a lead. Analytics may show how many people arrived from advertising, yet it does not by itself attach a submitted name, email or company to the campaign that produced it.
The workflow below closes that gap in four stages: tag the ads, add hidden fields to the form, let attribution fill those fields at submission time, and then use the completed record in Tally, email notifications, a CRM or a spreadsheet.
Step 1: Tag Google Ads URLs with UTM parameters
Start by appending UTM parameters to the destination URL in Google Ads. These are extra URL elements that identify the source, medium, campaign and related details for each click.
A consistent convention for paid search is:
- UTM Medium: Paid search
- UTM Source: Google
- UTM Campaign: the Google Ads campaign name
- UTM Term: the ad group name
- UTM Content: the searched keyword, which can be inserted automatically with ValueTrack parameters
Consistency matters more than the exact labels. If one manager uses google and another uses adwords, later reporting becomes harder to interpret, even though normalisation can help.
Step 2: Add hidden fields to Tally Forms
Next, add hidden fields to each lead-capture form, such as a contact or quote-request form. Visitors do not need to see or complete these fields; they are reserved for attribution values.
Add these six fields:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Check that every form you want to measure has the same field names. A missing field on one form will create a gap in the data even if the ads are tagged correctly.
Step 3: Let attribution fill the hidden fields
When a visitor arrives, the attribution tool records the UTM values and the first landing page. It stores them in a browser cookie, so the values survive normal browsing across the site. When the visitor later submits a Tally form, the tool writes the stored values into the hidden fields.
Consider a visitor who clicks a brand campaign ad, lands on a features page, browses elsewhere, and then submits a form. The completed record could show:
- Channel: Paid search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand campaign
- Channel Drilldown 3: Free account ad
- Landing Page: the features page URL
- Landing Page Group: features
That example shows why cookie persistence matters. A method that only reads UTM parameters from the page containing the form would miss the campaign when the form is completed on a different page from the landing page.
Step 4: Use the captured data in Tally, email, CRM and spreadsheets
On submission, the hidden-field values are stored with the details the visitor entered, such as name, email, phone number and company. You can then view them in the Tally Submissions section, include them in lead notification emails, forward them to a CRM such as Salesforce, HubSpot or Pipedrive, or export them to a spreadsheet for charts and graphs.
Use this checklist before relying on the reports:
- Confirm UTM values are present on every Google Ads destination URL.
- Confirm all six hidden fields exist on every measured Tally form.
- Submit a test form after clicking a tagged ad and check each field.
- Submit a test form after navigating to a different page and check that the original campaign values remain.
- Confirm the values appear in Tally, email notifications and the destination CRM or spreadsheet.
The same approach also covers non-Google arrivals, including organic search, organic social, paid social, referral and direct traffic. Landing-page capture adds another useful cut: you can compare pages such as blog posts by the leads and customers they generate, not just by visits.
Three useful reports once attribution is captured
Three reports make the data practical.
Leads by Channel shows monthly lead volume split by channel. It gives a high-level view of where enquiries originate and can prompt a budget review if, for example, most leads come from organic search while most spending goes to paid search.
Customers by Google Ads Campaign shows monthly customer volume split by campaign. This separates campaigns that produce customers from campaigns that only produce clicks.
Revenue by Keyword is available when the attribution data is sent to a CRM that also tracks closed deals. It shows revenue by bidding keyword, helping you shift budget toward terms that produce income rather than only enquiries.
Wrap up
In short, UTM tagging identifies the ad, hidden fields provide a place to store the result, and cookie-based attribution carries the values from the landing page to the form submission. Together they let you report leads, customers and revenue by campaign, keyword and landing page, while also covering other traffic sources.
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
| UTM element | Recommended paid-search value | What it identifies |
|---|---|---|
| UTM Medium | Paid search | Channel |
| UTM Source | Platform or source | |
| UTM Campaign | Google Ads campaign name | Campaign |
| UTM Term | Ad group name | Ad group |
| UTM Content | Searched keyword via ValueTrack | Keyword |
Values are a recommended convention, not a fixed platform rule.
| Hidden field | Purpose |
|---|---|
| Channel | Broad traffic channel |
| Channel Drilldown 1 | Source detail, such as Google |
| Channel Drilldown 2 | Campaign detail |
| Channel Drilldown 3 | Ad or finer campaign detail |
| Landing Page | First page URL visited |
| Landing Page Group | Section or group of the landing page |
Field names should match exactly across forms.
Frequently asked questions
Will attribution still work if someone lands on one page and submits the form on another?
No. The attribution data is stored in a browser cookie when the visitor first arrives, so it can still be written into the form even if the submission happens on a later page.
Does this only cover Google Ads traffic?
No. In addition to paid search, the same setup can record arrivals from organic search, organic social, paid social, referral and direct visits, giving a fuller picture of lead sources.
What happens if different campaigns use google in one place and adwords in another?
Yes. The normalisation step maps variant source values such as google and adwords to the same Paid Search channel, so reports are not split by inconsistent naming.