Track Google Ads Campaigns in Salesforce
You can judge a Google Ads campaign properly only when its results are visible alongside the leads, opportunities and customers it creates in Salesforce. The workflow below links each CRM record back to the campaign, ad group and ad that brought the visitor to the site, while also capturing the first page they landed on.
How the attribution flow works
A small website script identifies where a visitor came from using the same kinds of signals analytics tools examine. It sorts the visit into a channel such as paid search, paid social, organic search or referral, and keeps that classification in a browser cookie. When the visitor later submits a lead form, the script writes the channel, its drill-down details and the landing page into hidden form fields. Your form system then sends those values into Salesforce together with the details the visitor typed, such as name, email, company and phone. From that point, every lead, opportunity and customer record can be traced back to the campaign that originated it, and Salesforce reports can show which campaigns return a positive return and which do not.
Four steps to set it up
Work through these four steps in order. Skipping the tagging or hidden-field steps breaks the chain between the click and the CRM record.
1. Tag every ad URL with UTM parameters
Append UTM parameters to the destination URL for each ad. These are extra text fragments added to the end of the URL. A consistent convention for Google Ads is: UTM Medium set to Paid search; UTM Source set to Google; UTM Campaign set to the campaign name; UTM Term set to the ad group name; and UTM Content set to the specific ad. Free URL builders can help assemble the final links, but consistency across campaigns matters more than the particular builder used.
2. Add hidden fields to your forms
Add hidden fields to each lead-capture form. Visitors do not see them, but form and attribution tools can read and populate them. The fields needed are: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; and Landing Page Group. Most form builders let you drag a hidden-field type into the form; the exact steps differ by builder.
3. Populate the hidden fields from the visit
Once the fields exist, the attribution code watches incoming visits and fills the hidden fields when a form is submitted, using the values carried in the UTM parameters. Consider a marketer whose brand campaign in paid search sends a visitor to the site. The fields would be populated as: Channel = Paid search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand campaign; Channel Drilldown 3 = Free account ad. The code also records the visitor's first landing page, for example a features page for cloud storage, and its group, for example features. That landing-page pair shows which part of the site first attracted the visitor, not merely the page where the form happened to sit.
4. Send the data into Salesforce and report
On submission, the form sends the campaign data, landing-page data and the lead's own details into Salesforce in one record. You can then report natively in Salesforce, or pass the data to a business-intelligence tool such as Tableau or Looker for more advanced analysis.
Why this beats passing raw UTM values alone
Capturing only Google Ads visits leaves a blind spot. The same setup also classifies organic search, organic social, referral and direct visits, so a CRM report can show the origin of every lead. That matters when search-engine optimisation is quietly outperforming paid search: without the full picture, budget would keep flowing to the weaker channel. The cookie-based memory is the second advantage. A visitor may click an ad, read a landing page, then move to a separate quote-request page to convert. Because the UTM values were stored at arrival, they survive that journey instead of disappearing when the parameters are absent from the form page. Third, the channel layer cleans up inconsistent tagging. If some campaigns use one capitalisation or domain variant for the source and others use a different spelling, raw values would split one source into several. Normalising them into a single paid-search channel prevents that fragmentation. Finally, landing-page capture adds a content dimension: you can see whether a blog section as a whole, or an individual article, is generating leads, customers and revenue.
Reports you can build once the data flows
Three reports illustrate the payoff. Leads by channel breaks monthly lead volume down by origin, letting you compare paid search against organic search and paid social before deciding whether to keep investing or move budget. Customers by campaign shows monthly customer volume per Google Ads campaign, and viewing it over time reveals whether optimisation changes are actually moving the number. Revenue by keyword shows which bidding terms produce income, so you can raise bids where visibility is affordable and profitable, and pull back where it is not. Use these as a checklist when building your own dashboards: one view per channel, one per campaign, one per keyword, each tied to a downstream outcome rather than clicks alone.
Wrap up
In short, tagging ads consistently, adding hidden fields, letting attribution code populate them from the original visit, and sending the result into Salesforce gives you campaign-level accountability inside the CRM. Because the same mechanism covers non-paid channels and landing pages, you can compare every source on equal terms and direct investment toward what genuinely grows the business. Before committing budget, check the current plan details and any trial conditions offered on this site.
| UTM parameter | Value to use for Google Ads |
|---|---|
| UTM Medium | Paid search |
| UTM Source | |
| UTM Campaign | Name of the Google Ads campaign |
| UTM Term | Name of the ad group the ad belongs to |
| UTM Content | The specific ad |
General best-practice convention; you may structure parameters differently provided the mapping to channel drill-downs stays consistent.
| Hidden field | What it stores |
|---|---|
| Channel | Broad origin, such as paid search |
| Channel Drilldown 1 | Source detail, such as Google |
| Channel Drilldown 2 | Campaign detail |
| Channel Drilldown 3 | Ad detail |
| Landing Page | First page the visitor landed on |
| Landing Page Group | Section of that landing page |
Fields are invisible to visitors but present on the form so attribution tooling can populate them.
| Report | Question it answers |
|---|---|
| Leads by channel | How does paid search compare with organic search and paid social each month? |
| Customers by campaign | Which Google Ads campaigns produce customers, and how is that changing over time? |
| Revenue by keyword | Which bidding terms are profitable enough to justify higher bids? |
Requires channel, campaign and keyword data to be present on Salesforce records.
Frequently asked questions
Do UTM parameters need to be present on the form page itself?
No. The attribution code stores the campaign information in a browser cookie when the visitor first arrives, so it can still be passed when the form is completed on a later page.
Why not pass raw UTM values straight into Salesforce?
Raw values can fragment reporting when the same source is written in different forms, such as different capitalisation or domain variants. A channel layer normalises those variants into one consistent channel, such as paid search.
What reports become possible once the data is in Salesforce?
You can group by channel to compare paid search with organic search or paid social, by campaign to see customer volume over time, and by keyword to see which terms produce revenue.