Skip to content

Track Google Ads campaigns in Close CRM

You can connect paid-search activity to leads, opportunities and customers by carrying campaign context from the ad click through the website form and into Close CRM. The workflow below uses UTM tags, hidden form fields and an attribution script, then turns the stored values into campaign, keyword and revenue reports.

Tag every ad with a consistent UTM convention

Start with the destination URL for each ad and append UTM parameters so the click carries identifiable context. A consistent convention for Google Ads 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. Consistency matters more than the exact labels, because later reporting groups records by these values. Free UTM builders can help assemble the URLs, but the naming rules should be documented before launch.

Add six hidden fields to lead forms

Add six invisible fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Visitors do not see or complete them. Most form builders provide a hidden-field type that can be dragged into the form; the exact steps differ by builder, so follow the instructions for the tool you use. Test that the fields are present on every form variant, including mobile layouts, before sending paid traffic.

Let the script populate the fields and pass them to Close

Place a small attribution script on the website. On a visit it reads the incoming traffic context, classifies the visitor into a channel such as paid search, paid social or organic search, and stores that classification in a browser cookie. When a form is submitted, the script writes the stored values into the hidden fields. The form tool then captures those values alongside the person's name, email and phone and passes the complete record into Close CRM.

Worked example: reading a populated lead

For a brand-campaign click, the populated record might show paid search as the channel, Google as the first drilldown, the brand campaign as the second, and a named ad as the third. The same submission also records the first landing page and its group, for example a features page under a features group. That combination lets you distinguish a campaign that produced a lead from the page that converted it.

Why cookie-based attribution beats raw UTM capture

Capturing only raw UTM values has three practical weaknesses. First, it usually requires the tags to remain on the submission page, so a visitor who browses before converting can lose the context. Second, inconsistent spellings create duplicate sources in reports. Third, it says nothing about non-Google traffic or the landing page. A cookie-based attribution layer addresses all three: it persists across pages, normalises recognised variants into one channel, covers other channels, and records the landing page and its group.

Three reports to build once data reaches Close

Leads by channel gives a portfolio view across paid search, paid social, organic search and other sources, helping you decide where to invest next. Customers by campaign shows which Google Ads campaigns produce closed business rather than only enquiries, so strong performers can receive more budget and weak ones can be paused. Revenue by keyword, combined with spend from Google Ads, reveals which keywords return a positive return and deserve further investment. Landing-page reporting adds another cut: totals by page group show which site sections generate leads, and totals by individual page show which articles or product pages convert.

Pre-launch checklist

Before trusting the reports, run a checklist on a test lead: confirm the UTM convention is applied to every ad, all six hidden fields exist on every form, a click from a tagged ad populates the fields correctly, a lead that browses to another page before submitting still carries the original context, variant spellings collapse into one channel, and the record arrives in Close with the lead details intact. Re-check after any form redesign, because hidden fields are easy to drop accidentally.

Hidden-field map
FieldWhat it storesReporting use
ChannelBroad source category, such as paid searchLeads by channel
Channel Drilldown 1Source, such as GoogleSource comparison
Channel Drilldown 2Campaign nameCustomers by campaign
Channel Drilldown 3Ad or ad-group detailAd-level drilldown
Landing PageFirst page the visitor reachedPage-level conversion
Landing Page GroupSection of that page, such as features or blogSection-level conversion

Field names are the six hidden fields required by the workflow; values depend on the UTM convention in use.

Frequently asked questions

What is the shortest setup sequence?

Add consistent UTM tags to every ad, place the six hidden fields on each lead form, let the attribution script populate them on a visit, and pass the submitted values through your form tool into Close CRM. Once the fields arrive with the lead, Close reporting can group results by channel, campaign, ad group, keyword, landing page or landing-page group.

Why can raw UTM capture miss a lead?

Raw UTM capture usually needs the tags to still be present on the submission page. If a visitor lands on the homepage and later submits on a quote page, the tags can be lost. Storing the attribution in a browser cookie preserves it across pages until submission.

Why do inconsistent UTM values distort reports?

Variations such as Google.com, google and adwords can split one source into several report rows. A normalising layer that maps recognised variants to one channel prevents that fragmentation and makes channel totals comparable.