Skip to content

How to track Google Ads campaigns in Insightly

If you cannot tell which Google Ads campaign produced a lead, you cannot decide which campaigns deserve more budget and which should be paused. This guide shows how to pass campaign, ad group, ad and landing-page data into Insightly so that lead, customer and revenue reports reflect the original click rather than guesswork.

What the setup needs to accomplish

The goal is a complete record on every Insightly lead: the marketing channel, the Google Ads campaign, the ad group, the specific ad and the first landing page. When those values arrive with the lead, reporting can group leads and customers by campaign and compare them with spend.

A practical setup has four moving parts: tagged ad URLs, hidden fields on the form, a capture tool that fills those fields, and an Insightly connection that receives the values. Each part has a distinct failure mode, so test them in order rather than changing everything at once.

How the capture tool works: Attribution Analytics is a snippet of code placed on your website. On each visit it reads technical signals about how the visitor arrived, classifies the visit into a channel such as paid search, organic search or paid social, and stores that classification in a cookie in the visitor's browser. When the visitor later submits a lead form, the tool writes the channel and campaign values into the form's hidden fields, and those values travel with the lead's own details into Insightly.

Step 1: Tag each Google Ads URL with UTM parameters

UTM parameters are extra text appended to the destination URL. They tell the capture tool how the visitor arrived. For Google Ads, the supplied best-practice mapping is:

  • UTM Medium = Paid search
  • UTM Source = Google
  • UTM Campaign = the Google Ads campaign name
  • UTM Term = the ad group name
  • UTM Content = the specific ad

For example, a destination page such as https://roipaths.com/integrations/salesforce would receive a tagged URL beginning with ?utm_medium=paidsearch&. Free URL builders can assemble the full string, but the important discipline is consistency: use the same spelling and capitalization for the same campaign across every ad.

Step 2: Add hidden fields to the lead form

Hidden fields are present in the form but not shown to the visitor. They give the capture tool a place to write the attribution values. Add these six fields:

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

Most form builders let you drag a hidden field type into the form. The exact menu label varies by builder, so check the form builder's documentation if the option is not obvious.

Step 3: Confirm the capture tool fills the fields

When a visitor arrives from a tagged ad and submits the form, the capture tool should populate the hidden fields from the UTM values. A useful test is to imagine a marketer at Dropbox running a brand campaign in paid search. The expected field values would be:

  • Channel = Paid search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Brand campaign
  • Channel Drilldown 3 = Free account ad

The same record should also carry the first landing page, such as dropbox.com/features/cloud-storage, and the landing page group, such as features. If any of these are blank, the problem is usually a missing hidden field or a mismatch between the field name on the form and the field name the capture tool expects.

Step 4: Send the values into Insightly

On form submission, the attribution values, landing-page data and the lead's own details are passed into Insightly. From there, native Insightly reporting can group records by campaign, ad group or ad. A BI tool such as Tableau or Looker can be used for more advanced analysis if one is already in place.

A quick field map helps during setup and troubleshooting:

  • Channel receives the broad category, such as Paid search.
  • Channel Drilldown 1 receives the source, such as Google.
  • Channel Drilldown 2 receives the campaign name.
  • Channel Drilldown 3 receives the ad group or ad identifier, depending on how the UTM Term and UTM Content values are assigned.
  • Landing Page receives the first page the visitor saw.
  • Landing Page Group receives the section of the site that page belongs to.

Reports worth building once the data arrives

Three report families answer the budget question directly. A leads-by-campaign report shows monthly lead volume grouped by the originating campaign and reveals whether optimizations changed lead flow over time. A customers-by-campaign report shows monthly new customers by channel and can expose campaigns that generate many leads but few customers. A revenue-by-campaign report shows monthly revenue by channel and supports a rough return-on-investment comparison against ad spend.

The supplied example chart shows $236,156 in new revenue attributed to paid social ads in March. That figure is a dated illustration, not a current benchmark. The reporting logic still applies: compare attributed revenue with the cost of the channel before deciding whether to continue.

Why a cookie-based capture beats raw URL parameters

The deciding factor is where the attribution values live between the click and the form submission. If they exist only in the URL, they exist only on the page that URL loaded. A visitor who clicks an ad, reads the campaign page, then follows a quote link to a separate form page has left the tagged URL behind; the submission arrives with no campaign attached, and the lead is effectively anonymous.

Cookie storage changes the timeline. The capture tool writes the classification to the visitor's browser on arrival and reads it back at submission, so the form page does not need to be the ad's landing page and the visitor's route through the site does not matter. The attribution is attached to the person, not to the URL. The same tool can also normalize inconsistent source values. If some ads use UTM_Source=Google.com, others use google and others use adwords, raw data produces three separate sources that must be stitched together manually. Normalization assigns all of them to the paid search channel.

The same approach captures non-Google traffic such as organic search, organic social, direct and referral. That matters when SEO, not paid search, is the main lead source. Landing-page and landing-page-group data add a second dimension: you can compare the blog as a whole with individual posts, or compare site sections by leads, customers and revenue.

Pre-launch checklist

Use this checklist before trusting the first report:

  1. Every Google Ads final URL carries the agreed UTM parameters.
  2. The same campaign name is used consistently across ads in that campaign.
  3. All six hidden fields exist on every lead form.
  4. A test submission from a tagged ad produces non-empty values in all six fields.
  5. A test submission from an untagged visit still produces a channel value, such as Direct or Organic search.
  6. Insightly records show the attribution fields on the lead record.
  7. A report grouped by campaign returns the expected test lead.

If a test fails, isolate the stage. Missing UTM values point to the ad URL. Missing hidden fields point to the form. Values present on the form but absent in Insightly point to the connection between the form and the CRM.

Frequently asked questions

Do I need UTM parameters if Google Ads already reports conversions?

Google Ads reports what happens inside its own environment. Insightly needs the source values on the lead record so that leads, opportunities, customers and revenue can be grouped by campaign inside the CRM. UTM parameters supply those values.

What happens if a visitor submits a form on a different page from the ad landing page?

A raw URL-based capture can lose the parameters when the visitor navigates away from the landing page. A cookie-based capture stores the original values and sends them with the form submission regardless of which page hosts the form.

Can I report on traffic that did not come from Google Ads?

Yes. The same hidden fields can receive channel values for organic search, organic social, direct and referral traffic, so reports can compare all sources rather than only paid search.

Which Insightly reporting option should I use?

Native Insightly reporting is sufficient for grouping leads, customers and revenue by campaign, ad group or ad. A BI tool such as Tableau or Looker is an option when more advanced analysis is needed and already available.