Skip to content

How to track Google Ads campaigns in HubSpot CRM

Google Ads tells you what happened before the click. HubSpot CRM tells you what happened after the lead arrived. The useful question sits between them: which campaigns, ad groups and keywords produced leads, deals, customers and revenue? This guide shows a practical setup that carries campaign context from the ad URL into the CRM record, then turns that context into reports you can act on.

Why connect Google Ads data to HubSpot CRM

A click and a lead are not the same business outcome. Knowing which campaigns generate the most form submissions helps, but knowing which ones generate customers and revenue helps more. When campaign context reaches the CRM, you can compare channels, identify campaigns worth keeping, and spot keywords that deserve more or less budget. You can also see whether paid search is doing the heavy lifting or whether organic search, paid social or another channel deserves a larger share of investment.

How the attribution layer works

The attribution layer is a script placed on the website. When a visitor arrives, the script inspects technical signals to determine where the visit came from. It groups the visit into a channel such as Paid Search, Paid Social or Organic Search and stores that information in the visitor's browser cookie. When the visitor submits a form, the channel information is passed into HubSpot CRM along with the details the visitor entered. A new lead from a Google Ads campaign can therefore arrive with the paid search channel, campaign name, ad group name and landing page already attached.

Four setup steps

The setup has four moving parts: tag the ad URLs, prepare the form, let the attribution layer fill the hidden fields, and confirm the data reaches HubSpot CRM. Each step has a specific job, and skipping one usually breaks the chain.

1. Add UTM parameters to Google Ads URLs

UTM parameters are text appended to the destination URL. They tell the attribution layer which campaign, source, medium, ad group and ad produced the visit. A typical pattern is to set the medium to paid search, the source to Google, the campaign to the Google Ads campaign name, the term to the ad group name and the content to the specific ad. The exact values are yours to choose, but consistency matters more than clever naming. Free UTM builders are available online if you prefer not to assemble the URL by hand.

2. Add hidden fields to lead capture forms

Hidden fields are present in the form but invisible to visitors. They give the attribution layer a place to write campaign context without asking the visitor to supply it. The fields to add are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Most form builders, including HubSpot forms, Gravity Forms, Wix Forms and Webflow Forms, let you drag a hidden field type into the form. Builder-specific instructions are available in the help documentation for each tool.

3. Let the attribution layer fill the fields

Once the script and the hidden fields are in place, the attribution layer begins tracking where visitors come from. When a visitor submits a form, it writes the UTM-derived values into the hidden fields. For example, a visitor arriving from a brand campaign in paid search could produce Channel = Paid search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign and Channel Drilldown 3 = Free account ad. The layer also records the landing page, such as a cloud-storage feature page, and the landing page group, such as the features section.

4. Confirm the data reaches HubSpot CRM

When the form is submitted, the Google Ads data derived from the UTM parameters travels into HubSpot CRM alongside the lead's name, email and other form entries. From there you can build reports with HubSpot's native reporting tools or export the data to a BI tool such as Tableau or Looker for more advanced analysis. The important check is that a test lead shows the expected channel, drilldown and landing page values on the CRM record.

Field and control map

The following map shows how the inputs connect to the fields and the reports they enable. It is a reader aid, not a replacement for the exact form-control contract supplied separately.

Why a normalized attribution layer beats raw UTM capture

Raw UTM capture can work, but it has three common weaknesses. First, it often captures only paid traffic, leaving organic search, organic social and paid social invisible. Second, it may depend on the UTM parameters being present on the page where the form is submitted, so a visitor who lands on the homepage and later completes a form on a contact page can lose the original campaign context. Third, inconsistent tagging produces messy data: one campaign tagged with a capitalized source, another with a lowercase source and another with an ad-platform alias can appear as three separate sources in reports. A normalized layer addresses all three by capturing all traffic, remembering the data in a cookie and grouping inconsistent values into a single channel.

Landing page and section reporting

The layer also records the landing page and the landing page group. That means you can see how a specific page performed and how a whole section, such as a blog, performed. You can zoom into an individual post or step back to compare the blog section against other sections of the site.

Example reports

Once the data is flowing, three reports are especially useful. A leads-by-channel report shows monthly lead volume by channel and gives a high-level view of where demand comes from. A customers-by-campaign report shows new customers by Google Ads campaign, which helps you decide which campaigns to continue. A revenue-by-keyword report shows revenue generated by each keyword, which helps you double down on what works and pause what does not.

Decision checklist before you report

Use this checklist to catch the common gaps before you trust a dashboard. Confirm that every Google Ads campaign URL carries the agreed UTM values. Confirm that every lead capture form includes all six hidden fields. Confirm that a test submission produces the expected channel and drilldown values. Confirm that organic and social traffic also populate the channel fields, not just paid search. Confirm that inconsistent source spellings are normalized rather than appearing as separate channels. Confirm that landing page and landing page group are populated. Confirm that the CRM reports use the same field names the forms write to.

Two different failure modes

Lost attribution and messy attribution are not the same problem. Lost attribution happens when the campaign context never reaches the form, for example because the visitor navigated away from the landing page before submitting. Messy attribution happens when the context arrives but is inconsistent, for example because different teams used different source spellings. The first is a capture problem; the second is a normalization problem. A cookie-based layer addresses the first, and a channel-grouping layer addresses the second. Diagnose which one you have before changing your setup.

Wrap-up

Connecting Google Ads to HubSpot CRM is mostly a matter of carrying the right context from the ad URL to the CRM record. UTM parameters define the context, hidden fields provide the destination, and the attribution layer moves the data across. Once that chain works, reports on leads, customers and revenue become possible, and decisions about which campaigns and keywords to keep become easier to defend.

Field and control map
InputHidden fieldExample valueReport use
UTM MediumChannelPaid searchLeads by channel
UTM SourceChannel Drilldown 1GoogleChannel breakdown
UTM CampaignChannel Drilldown 2Brand campaignCustomers by campaign
UTM TermChannel Drilldown 3Free account adRevenue by keyword
Landing page URLLanding Pageexample.com/features/cloud-storagePage-level performance
Landing page sectionLanding Page GroupfeaturesSection-level performance

Example values are illustrative and use the supplied brand-campaign scenario. They are not a claim about any specific account's performance.

Frequently asked questions

Do I have to use UTM parameters?

Yes, the setup relies on UTM parameters to define the campaign, source, medium, term and content. Without them, the attribution layer has no campaign context to pass into the hidden fields.

Which form builders support hidden fields?

Most form builders do, including HubSpot forms, Gravity Forms, Wix Forms and Webflow Forms. The usual pattern is to drag a hidden field type into the form and name it to match the expected field.

Why do UTM parameters sometimes disappear before form submission?

If the form is submitted on a different page from the one the visitor first landed on, a raw UTM capture method may lose the parameters. A cookie-based layer stores the values in the browser so they survive navigation across pages.

What happens if my UTM source values are inconsistent?

Raw capture can treat capitalized, lowercase and alias spellings as separate sources. A normalized layer groups them into a single channel, which keeps reports readable.

Can I track channels other than Google Ads?

Yes. The same setup captures organic search, organic social, paid social and other channels, so you can compare all lead sources rather than only paid search.