Capture Google Ads Data in Typeform
Google Ads reporting tells you how many clicks and sessions a campaign produced, but not how many leads, opportunities or customers came with them. This guide walks through passing campaign data through a Typeform submission and into the sales tools where you can report on it. The setup has four parts: tag the ads, add hidden fields to the form, let a capture layer fill those fields, and confirm the values arrive with the submission.
What you need before you start
You need a Typeform lead form embedded or linked from your site, a way to add hidden fields to that form, and a destination such as a CRM or notification email. You also need a consistent naming convention for your Google Ads campaigns and ad groups. The capture layer described here is a third-party script that reads UTM parameters and landing-page information and writes them into the form. The exact field names in the protected form-controls contract must match the names you create in Typeform; a mismatch means the value has nowhere to land.
Step 1: Tag every Google Ads destination URL
UTM parameters are extra text appended to the URL a visitor lands on. They tell analytics and capture tools where the visit came from. For Google Ads, a practical default is: medium set to paid search, source set to Google, campaign set to the campaign name, term set to the ad group, and content set to the specific ad. A tagged URL might look like the example below, with the parameters separated by ampersands.
https://example.com/landing-page?utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign
Use a URL builder or your ad platform's tracking template to apply the tags consistently. The important discipline is to choose a convention and keep it stable across campaigns and agencies.
Step 2: Add the hidden fields to your Typeform
Create hidden fields in Typeform for each value you want to receive. The protected form-controls contract lists the exact field names and types; use those names exactly. In practice the set covers the channel, three drilldown levels, the landing page and the landing-page group. Hidden fields are not shown to the visitor, but they travel with the submission and can be mapped to CRM properties or included in notification emails.
Step 3: Let the capture layer fill the fields
When the capture script is active, it reads the UTM parameters on the visitor's first landing page and stores them in the browser. When the visitor later submits a Typeform, the script writes the values into the hidden fields. This is the part that solves the navigation problem: a visitor can land on a homepage, click through to a quote page, and still have the original campaign data attached to the form submission.
The script also records the first landing page and a landing-page group. For example, a visitor who first arrived at a features page would carry that page and its group alongside the campaign values.
Worked example: what the hidden fields receive
Suppose a marketer at a file-sharing company runs a brand campaign in paid search and a visitor clicks an ad for a free-account offer. The UTM values are medium=paidsearch, source=google, campaign=brand-campaign, term=free-account-ad-group, and content=free-account-ad. The capture layer would populate the fields as follows:
- Channel = Paid search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand campaign
- Channel Drilldown 3 = Free account ad
- Landing Page = the first page the visitor saw
- Landing Page Group = the section of the site that page belongs to
This example is illustrative; the actual values depend on the tags you apply.
Step 4: Confirm the data arrives with the submission
Submit a test Typeform entry from a tagged URL and check the notification email or the destination record. The hidden-field values should appear next to the lead's name and email. If they are blank, check three things in order: whether the URL actually carried the UTM parameters, whether the hidden field names match the contract exactly, and whether the capture script loaded on the page where the form was submitted. A blank field is usually a naming or loading problem, not a reporting problem.
Once the values arrive, put them to work in three places. Add them to each new lead notification email so you can see at a glance where a lead came from. Send them to your CRM (such as Salesforce, Pipedrive or Microsoft Dynamics) so your sales team can see each lead's origin. And use them to run reports showing which Google Ads campaigns actually generate leads, customers and revenue.
Choosing between raw UTM fields and a capture layer
The decision comes down to two failure modes you want to avoid.
The first is loss on navigation. If you read UTM parameters only from the page where the form is submitted, the values survive only when the visitor converts on the same page they first landed on. A visitor who arrives on a homepage, clicks through to a quote page, and submits there will produce a blank source. A capture layer that stores the values in the browser cookie keeps the original campaign attached regardless of which page the form sits on.
The second is naming drift. Raw capture records whatever string was in the URL, so a source field can end up holding Google.com, google and adwords as three separate values if different people or agencies tagged the ads over time. Reconciling those by hand in a CRM report is tedious and error-prone. A normalization layer that maps known variants to one paid-search channel keeps the report readable.
If your forms always sit on the landing page and one team controls every tag, raw capture may be enough. If either condition fails, a capture layer earns its place.
Landing-page data adds a second reporting axis
A capture layer can also record the first landing page and a landing-page group, which lets you compare content performance alongside campaign performance. You can look at how a blog section performs as a whole and at which individual posts drive the most leads, customers and revenue. That is useful when you want to know whether a campaign worked because of the ad or because of the page it sent people to.
Three reports worth building once the data is flowing
The first report is leads by channel, which gives a high-level view of which acquisition channels produce the most leads each month. The second is opportunities by Google Ads campaign, which shows which campaigns create sales opportunities rather than just clicks. The third is customers by keyword, which requires putting the keyword into the UTM parameters through a tracking template; it shows which search terms produce actual customers and can inform bid adjustments. These reports depend on the CRM or reporting tool receiving the hidden-field values consistently.
Decision checklist
- Are all Google Ads destination URLs tagged with a consistent UTM convention?
- Do the Typeform hidden field names match the protected form-controls contract exactly?
- Does the capture script load on every page where a form can be submitted?
- Have you tested a submission from a tagged URL and confirmed the values in the destination record or notification email?
- Have you agreed how to handle legacy or agency-created UTM variants?
- Do you have a reporting owner who will review leads by channel and by campaign monthly?
Frequently asked questions
Do I need to change my Typeform questions?
No. The campaign data travels in hidden fields, so the visible questions stay the same. You add the hidden fields once and map them to your destination.
What happens if a visitor lands on one page and submits the form on another?
With a capture layer that stores UTM values in the browser, the original campaign data is retained across pages. Without that layer, raw UTM fields are typically lost when the form is on a different page from the landing page.
Can I capture the keyword as well as the campaign?
Yes, if you include the keyword in the UTM parameters, for example through a tracking template. The hidden field then receives the keyword value and you can report customers by keyword.
Why do my reports show several versions of Google as a source?
That usually means the raw UTM values were captured without normalization. Different capitalization or domain forms such as Google.com, google, and adwords become separate sources. A normalization layer can group them under one paid-search channel.