Track Google Ads Campaigns in NetSuite: Leads, Customers and Revenue
Google Ads can send plenty of visitors and form fills without sending many customers. If your reporting stops at clicks or sessions, you cannot tell which campaigns deserve more budget and which ones only look busy. This guide shows how to carry Google Ads campaign data into NetSuite so leads, opportunities, customers and revenue can be reviewed together.
Why campaign data needs to reach NetSuite
A campaign that attracts low-intent searches may produce traffic and leads while producing very few customers. When campaign details stay outside NetSuite, sales and marketing teams see only part of the picture. Bringing the campaign name, ad group, ad and landing page into the CRM lets you compare lead volume with closed business and revenue. That comparison is the difference between optimizing for form fills and optimizing for customers.
How a cookie-based attribution layer works
Think of the layer as a translator sitting between the ad click and the CRM record. On arrival, it reads signals about the visit and sorts the visitor into a channel family — paid search, paid social, organic search and so on. That classification, plus the campaign details, is parked in a browser cookie rather than left on the landing page. When the visitor eventually submits a form, the parked values are copied into hidden fields and travel to NetSuite with the name, email and phone number. The resulting lead record can therefore show channel, campaign, ad group and landing page next to the contact details.
Four setup steps
The setup follows a simple sequence: tag the ads, prepare the form, let the attribution layer fill the hidden fields, then confirm the data arrives in NetSuite.
Step 1: Add UTM parameters to Google Ads campaigns
UTM parameters are extra text appended to the destination URL. They tell the attribution layer which campaign, ad group and ad produced the visit. A typical Google Ads mapping is: UTM Medium for paid search, UTM Source for Google, UTM Campaign for the campaign name, UTM Term for the ad group name, and UTM Content for the specific ad. Free online tools can help assemble the tagged URL.
Step 3: Let the attribution layer fill the hidden fields
Once the hidden fields exist, the attribution layer checks where the visitor came from and fills the fields with the values from the UTM parameters when the form is submitted. For example, a visitor arriving from a paid search brand campaign 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 first landing page and the first landing page group.
Step 4: Confirm the data reaches NetSuite
On each form submission, the Google Ads data, landing page data and the lead's name, phone, email and other details are sent into NetSuite. Once the records are there, you can report with native NetSuite tools or connect a BI tool such as Looker or Tableau for more advanced analysis.
Field and control map
Use this map to check that each hidden field receives the value you expect. The left column is the form field; the right column is the value it should carry for a paid search visit.
Example reports you can build
With campaign data in NetSuite, three report families become practical. First, leads by campaign, ad group or ad show monthly lead volume sorted by the originating campaign; over time they reveal the effect of campaign changes. Second, customers by campaign, ad group or ad show monthly new customers grouped by channel; comparing this with the leads report exposes campaigns that generate leads but few customers. Third, revenue by campaign, ad group or ad show monthly revenue by customer channel, which supports return-on-investment comparisons. The captured example in the revenue report shows $236,156 in new revenue from March paid social ads; if the ad spend was below that figure, the campaign produced a positive return.
Why a dedicated attribution layer beats raw UTM capture
Raw UTM capture can work, but it has four practical weaknesses. A dedicated layer addresses each one.
It captures all traffic, not only Google Ads
The layer also records visitors from organic social, organic search, direct and referral sources. Reports can therefore show the source of every lead and customer, not just paid search leads. If SEO brings most of your business, you can see that and invest accordingly.
It remembers the original source across pages
Picture a visitor who clicks a campaign ad, reads the landing page, then follows a "Get a Quote" button to a separate form page. If the campaign tags lived only on the landing page, they are gone by the time the form is submitted, and the lead arrives with no campaign attached. A cookie-based layer sidesteps this: the campaign values travel with the visitor in the browser, so the form page does not need to carry the tags itself. The original source survives any number of page views between the click and the conversion.
It normalizes inconsistent UTM values
The same source can be tagged several ways across campaigns — for instance Google.com, google and adwords all pointing at the same place. Left raw, a report treats those as three distinct sources and someone has to merge them by hand before the numbers mean anything. A dedicated layer reconciles capitalization and similar variations, so every one of those leads lands in the same channel bucket without manual cleanup.
It records landing page and landing page group
Because the layer also stores the first landing page and its group, you can ask which content actually produces business. A whole blog section can be compared against a single article, and both can be measured in leads, customers and revenue rather than page views alone.
Decision checklist before you start
Use this checklist to confirm the setup is ready. If any item is missing, fix it before relying on the reports.
Two different failures to watch for
A missing campaign value and a lost campaign value are not the same problem. A missing value usually means the UTM parameters were never added to the ad or the hidden field was not included in the form. A lost value usually means the parameters were present on the landing page but disappeared before the form was submitted because the form sat on a different page. The first is a tagging gap; the second is a persistence gap. A cookie-based layer solves the second, while the first still requires correct UTM tagging.
Putting it together
Tagging Google Ads, adding hidden fields, letting the attribution layer populate them and confirming the data in NetSuite gives you a reporting chain from campaign to customer. The same setup also captures other channels and landing pages, so you can compare paid search with organic and content-driven leads. That broader view supports better budget decisions than click-level reporting alone.
| Form field | Example value |
|---|---|
| Channel | Paid search |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | Brand campaign |
| Channel Drilldown 3 | Free account ad |
| Landing Page | First landing page URL |
| Landing Page Group | First landing page group |
The example values illustrate a paid search brand campaign; actual values depend on the UTM parameters applied to each ad.
| Check | Why it matters |
|---|---|
| UTM parameters added to every Google Ads ad | Without tags, the campaign cannot be identified |
| Hidden fields present on the lead form | The attribution layer needs a destination for the values |
| Form builder supports hidden field types | Most builders allow drag-and-drop hidden fields |
| Test submission shows campaign data in NetSuite | Confirms the full path from form to CRM |
Checklist items reflect the setup sequence described in the guide; test results depend on the specific form builder and NetSuite configuration.
Frequently asked questions
Do I need UTM parameters if I already use Google Ads?
Yes. UTM parameters are the mechanism that carries the campaign, ad group and ad identity into the form and then into NetSuite. Without them, the attribution layer has no campaign values to pass along.
What happens if a visitor submits a form on a different page from the one they landed on?
With a cookie-based attribution layer, the original campaign values are retained in the browser and still sent with the form. With raw UTM capture, the values are typically lost when the form page does not contain the parameters.
Can I report on channels other than Google Ads?
Yes. The same layer records organic search, organic social, direct and referral visits, so reports can compare paid search with other sources.
What is the difference between a missing campaign value and a lost campaign value?
A missing value usually means the ad was not tagged or the form lacks the hidden field. A lost value means the tag was present on the landing page but did not survive to the form submission page. The first is a tagging gap; the second is a persistence gap.