How to Capture UTM Parameters in NetSuite
NetSuite does not automatically know which campaign brought a lead to your website. To report leads, opportunities, customers and revenue by channel, the attribution data must be captured on the website and submitted with the form that creates the lead.
1. Install the website tracking code
Install a small tracking snippet on the website, either directly through the CMS settings or through a tag manager such as Google Tag Manager. The snippet runs when a visitor arrives and determines which channel brought them to the site, using the same kinds of signals analytics software examines.
2. Add hidden fields to lead forms
Add hidden fields to each lead-capture form. In most form builders, including Gravity Forms, WP Forms, Typeform and Jotform, this is done by dragging a hidden field type into the form and naming it to match the attribution data you want to receive.
3. Let the code populate the fields at submission
When a visitor arrives from a campaign, the tracking code reads the UTM parameters and saves them in a cookie in the visitor's browser. That cookie keeps the data available while the visitor browses, leaves and returns, or moves to a different page. When a form is submitted, the code writes the saved values into the hidden fields.
Worked example: a paid search visit
For example, a visitor clicking a Google Ads campaign for an ERP product could produce Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign and Channel Drilldown 3 = Netsuite. The first landing page and its group, such as a features page under Features, are captured alongside those channel values.
4. Pass the data into NetSuite with the lead
On submission, the hidden-field values travel into NetSuite with the details the lead entered, such as name, email and phone. Once stored, they can be used in NetSuite reports or a connected BI tool to compare channels by lead volume, opportunity conversion and closed-won deals.
Why channel data is more useful than raw UTM values alone
Raw UTM capture has three practical weaknesses. First, it misses traffic without UTM parameters, including Organic Search, Organic Social, Referral and Direct. Second, it usually requires the parameters to still be in the URL when the form is submitted, so they are lost when the form sits on a different page from the landing page. Third, inconsistent tagging creates messy reporting: Facebook, facebook and fb would otherwise be counted separately instead of being grouped as Paid Social. Capturing the landing page and landing page group also shows whether content such as a blog is generating leads, not just whether a campaign is.
Reports to build once the data is in NetSuite
Leads by Channel shows monthly lead volume across paid and organic sources, helping you shift budget toward channels that actually produce leads. Leads by Facebook Ads Network separates Facebook, Instagram, Messenger and other networks within the same platform. Customers by Google Ads Campaign connects campaigns to customers rather than clicks. Revenue by Keyword, where keywords are added to UTM parameters through Google Ads tracking templates, shows which search terms produce revenue.
Pre-launch checklist
Before going live, check that the snippet loads on every page, that each form contains all six hidden fields, that a test visit with UTM parameters populates them correctly, that a visit without UTM parameters still records a channel, and that submitted test leads arrive in NetSuite with the attribution fields completed. If you are evaluating a hosted tracking service, confirm its current trial terms, plan limits and data-retention policy directly with that provider before you commit.
| Hidden field | What it records | Reporting use |
|---|---|---|
| Channel | Broad source category, such as Paid Search or Paid Social | Leads and revenue by channel |
| Channel Drilldown 1 | First level of detail, such as Google | Performance by platform or network |
| Channel Drilldown 2 | Second level of detail, such as a campaign | Performance by campaign |
| Channel Drilldown 3 | Third level of detail, such as a product or keyword group | Finer campaign breakdowns |
| Landing Page | First page the visitor landed on | Which pages start converting journeys |
| Landing Page Group | Category of the first landing page, such as Features or Blog | Content performance by section |
Field names are reproduced exactly as supplied in the source.
Frequently asked questions
Does capturing UTM parameters cover every lead source?
No. Raw UTM capture only covers visits where UTM parameters are present in the URL. A channel-based approach also classifies Organic Search, Organic Social, Referral and Direct visits, so reporting is not limited to paid campaigns.
What happens if a visitor lands on one page and submits a form on another?
Storing the attribution data in a browser cookie means it remains available when a form is completed on a later page, after browsing or after leaving and returning. URL-only capture loses the parameters when the landing page and form page differ.
Why normalise UTM values instead of sending them raw?
Normalising source values before they reach NetSuite prevents variants such as Facebook, facebook and fb from appearing as three separate sources in reports. The visitor is assigned to the correct channel, for example Paid Social, despite those inconsistencies.