Track Google Ads Campaigns in Sage CRM: A Practical Setup Guide
If your Sage CRM pipeline contains leads from Google Ads but you cannot say which campaign, ad group or ad produced them, you are making budget decisions on incomplete evidence. This guide shows a four-step setup that carries campaign data from the ad click through to the Sage CRM record, then turns that data into lead, customer and revenue reports. It also explains where simpler UTM capture tends to break and how a cookie-based approach avoids those gaps.
Why campaign-level source data matters in Sage CRM
Sage CRM already holds the commercial outcome: the lead, the opportunity, the customer and the revenue. What it often lacks is a dependable record of the marketing source that produced each one. When that source is captured at the point of form submission, you can compare campaigns on outcomes rather than clicks alone. You can see which campaigns generate leads that never become customers, and which produce revenue that justifies continued spend. The same records also support reporting through Sage CRM's native tools or through BI tools such as Looker or Tableau when deeper analysis is needed.
How a cookie-based capture layer works
The workflow described here relies on a cookie-based capture layer. A small piece of code is placed on your website. On each visit it inspects technical signals to determine the visitor's origin, groups that origin into a channel such as paid search, paid social or organic search, and stores the result in a cookie in the visitor's browser. When the visitor submits a lead form, the stored values are written into hidden fields and travel with the lead into Sage CRM. A new lead from a Google Ads campaign can therefore arrive with the channel, campaign name, ad group name and landing page already populated. Confirm that your chosen capture layer offers the same cookie persistence and field mapping before following the steps below.
The four-step setup
The sequence below is the core of the workflow. Each step depends on the one before it, so complete them in order and test the chain before relying on the reports.
Step 1: Tag your Google Ads URLs with UTM parameters
UTM parameters are text appended to the destination URL so that the source of a visit can be identified. For a page such as https://roipaths.com/integrations/salesforce, a tagged URL adds parameters after a question mark, for example a utm_medium value of paidsearch. The exact structure is your choice, but the following mapping is a practical convention for Google Ads:
- 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
Free URL-building tools can help assemble these strings consistently. Consistency matters more than the specific labels you choose, because inconsistent labels are what make later reporting unreliable.
Step 2: Add hidden fields to your lead forms
Hidden fields are form inputs that visitors never see but that still submit values. Add the following six fields to each lead capture form:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
In most form builders this is a drag-and-drop operation: place a hidden field type into the form and give it the matching name. Builder-specific instructions are available in your capture tool's own help documentation for hidden fields.
Step 3: Let the capture layer populate those fields
Once the hidden fields exist, the capture layer fills them from the visitor's stored attribution data at submission time. A worked example makes the mapping concrete. Suppose a visitor reaches your site through a brand campaign in paid search and later submits a form. The fields would be populated as follows:
- Channel = Paid search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand campaign
- Channel Drilldown 3 = Free account ad
Alongside the UTM-derived values, the visitor's first landing page (for example, a cloud-storage feature page) and the first landing page group (for example, features) are also recorded. This is where the cookie matters: the values reflect the visit that started the journey, not merely the page where the form happened to be submitted.
Step 4: Confirm the data lands in Sage CRM
On submission, the Google Ads data, the landing-page data and the lead's contact details are written into the Sage CRM record. From that point the attribution fields behave like any other CRM field: they can be filtered, grouped and reported on. Before building dashboards, open a handful of recently created leads and confirm that the channel and drilldown fields are populated as expected. A lead with an empty channel field usually points to a missing hidden field or a form that was not updated.
Three reports worth building first
With the fields populated, three report families give the clearest view of performance.
Leads by campaign, ad group or ad. A monthly count of new leads grouped by originating campaign shows how volume shifts over time and whether optimisation changes had the intended effect.
Customers by campaign, ad group or ad. A monthly count of new customers grouped by source is most useful when read beside the lead report. A campaign that produces many leads but few customers is a candidate for review or retirement.
Revenue by campaign, ad group or ad. A monthly revenue total grouped by source supports return-on-investment assessment. In the illustrative chart supplied with the original guide, paid social ads were shown generating $236,156 in new revenue in March. That figure is a dated illustration from the original material, not a current benchmark; treat it as an example of the calculation and check your own figures against current spend.
Where raw UTM capture falls short
Capturing UTM parameters directly is a common alternative. It works in simple cases but has four recurring weaknesses that matter in a CRM context.
It covers only tagged traffic
Raw UTM capture records only visits that carry parameters. Visitors arriving through direct, referral, organic search or organic social are invisible, so any comparison between Google Ads and other channels is incomplete. A capture layer that classifies all traffic lets you see the full mix and allocate budget accordingly, which is especially important when organic search, not paid search, is the dominant source.
It forgets across pages
A raw UTM approach generally assumes the tagged URL is still in view when the form is submitted, because the parameters are read from the current page address. That assumption breaks the moment a visitor wanders. Picture a prospect who clicks a pricing ad, reads the pricing page, then follows an in-page link to a separate demo-request form two clicks later. The address bar on that form page carries no campaign parameters, so the submission arrives with no campaign attached. Cookie-based capture sidesteps the problem entirely: the attribution is written to the browser on arrival and read back at submission, so the number of intervening pages makes no difference.
It produces inconsistent labels
Raw parameters reflect whatever the person who built the URL typed. One campaign may use a source value of Google.com, another google, another adwords. Reported separately, these appear as three distinct sources that must be merged by hand before any comparison is valid. Normalising the values at capture time assigns all three to the same channel and keeps reports accurate.
It misses landing-page context
Knowing which page a visitor first saw adds a dimension that campaign labels alone cannot provide. Recording both the landing page and its group lets you assess a whole content section, such as a blog, and then drill into individual posts. That answers questions such as how many leads and customers a particular article or feature page contributed.
Pre-launch checklist
Use this list to verify the chain before trusting the reports.
- Every Google Ads final URL carries the agreed UTM set, with consistent casing and spelling.
- All six hidden fields exist on every lead capture form, named exactly as intended.
- A test submission from a tagged ad produces a Sage CRM lead with channel, drilldowns and landing page populated.
- A test submission after navigating through two or more pages still carries the original campaign data.
- A test submission from an untagged source is classified into a non-paid channel rather than left blank.
- The first reports group by campaign and by channel, and reconcile against a manual count of recent leads.
Bringing it together
The value of this setup is not the tagging itself but the decision it enables. Once campaign, ad group, ad and landing-page data sit alongside leads, customers and revenue in Sage CRM, you can compare channels on outcomes and direct spend toward what actually converts. The same records also reveal the contribution of non-Google channels, so the picture is complete rather than partial. You can evaluate whether the setup fits your team before committing.
Frequently asked questions
Do I have to use the suggested UTM values?
No. The medium, source, campaign, term and content values can follow whatever convention suits your team. What matters is that the convention is applied consistently across every ad, because inconsistent labels are the main cause of fragmented reporting.
What happens if a visitor submits a form on a different page from the one they landed on?
With a cookie-based capture layer, the original attribution is retained and written into the hidden fields at submission. With raw UTM capture, the parameters are typically lost once the visitor leaves the tagged page.
Can I report on leads that did not come from Google Ads?
Yes, provided the capture layer classifies all traffic rather than only tagged visits. Direct, referral, organic search and organic social visits can then be grouped alongside paid search, giving a complete channel comparison.
Which Sage CRM reporting tools can I use?
The attribution fields are ordinary CRM fields, so native reporting tools can group and filter them. For more advanced analysis, the data can also be exported to BI tools such as Looker or Tableau.