Skip to content

How to Track Facebook Ads Performance in NetSuite

Facebook's own dashboard tells you what happened inside the ad platform. It cannot tell you which campaigns produced qualified opportunities, closed deals or repeat revenue in NetSuite. Closing that gap means carrying campaign identity from the ad click, through your website form, into the lead record that NetSuite stores. This guide walks through that chain step by step, shows what each hidden field should contain for a sample click, and explains how to read the resulting reports without overstating what the numbers prove.

Why ad-platform metrics are not enough

A campaign can look healthy on impressions and clicks while producing leads that never qualify. The reverse also happens: a modest campaign may quietly generate high-value customers. Without a link between the ad and the downstream record, both cases stay invisible, and budget decisions rest on guesswork.

Two failure modes matter. If a campaign is profitable and you cannot see it, you under-invest. If it is unprofitable and you cannot see it, spend continues on autopilot. Either way the fix is the same: capture the campaign identity at the moment of conversion and keep it attached to the person record.

What the attribution layer actually does

A small script on your site inspects how each visitor arrived, classifies the visit into a marketing channel such as Organic Search, Paid Social or Paid Search, and stores that classification in a browser cookie. When the visitor submits a form, the stored values are written into hidden fields and travel with the submission into whatever system receives your forms, NetSuite included.

That stored classification is what makes later reporting possible. Typical questions it answers include lead counts by channel, opportunity volume from Facebook, which campaigns produce the most opportunities, close rates compared with other sources, and revenue against ad spend.

Step 1: Install the script and add hidden fields

Place the tracking snippet on your website, either through your site settings or a tag manager. Then add five hidden fields to every lead capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4.

Most form builders let you drag in a hidden field type or mark an existing field as hidden in its settings. Keep the field names exactly as written, because the script matches on those names when it writes values.

Step 2: Put UTM parameters on every Facebook ad URL

UTM parameters are text appended to the destination URL that labels the click. A URL ending in a page path might become something like the page path followed by utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign, joined with ampersands.

A workable convention for Facebook traffic: medium set to paid social, source set to Facebook, campaign set to the campaign name, term set to the ad set name, and content set to the specific ad. Any consistent structure works, but consistency is what makes the reports readable later. Free URL builders can assemble the string for you.

Step 3: Understand what gets written into the fields

When someone arrives from a Facebook ad, the UTM values are saved in the browser cookie so they survive further browsing before the form is submitted. On submission, the script writes the classification into the hidden fields alongside the lead's name, email and phone.

A concrete illustration helps. Suppose a marketer runs ads for a software product and a visitor clicks an ad, reads a few pages, then requests a demo. Depending on the UTM values behind that ad, the fields would read: Channel = Paid Social; Channel Drilldown 1 = Facebook; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = North America Ad Group; Channel Drilldown 4 = Green Ad. The landing page and the landing page group are captured as well, for example a features contact-management page and its /features group.

Step 4: Confirm the data lands in NetSuite

The UTM-derived values arrive in NetSuite together with the lead's contact details. From there, NetSuite's own reporting can group and total them, or a BI tool such as Microsoft Power BI or Google Data Studio can build more elaborate views.

Before trusting any report, open a handful of recently created leads that you know came from a Facebook ad and check that the five fields are populated and correctly spelled. Empty fields usually point to a form that is missing the hidden inputs; mismatched values usually point to inconsistent UTM naming.

What this approach adds beyond Facebook-only tracking

Four capabilities are worth weighing against alternative setups.

First, channels beyond Facebook are classified too, including Organic Search, Organic Social, Referral and Direct, so Facebook results can be compared with everything else rather than viewed in isolation.

Second, the cookie keeps the original UTM values available even when the form is submitted on a different page from the landing page, which reduces under-counting.

Third, inconsistent UTM spelling is normalized. If some campaigns use utm_source=facebook and others use utm_source=facebook.com, the lead is still assigned to Paid Social.

Fourth, landing page URL and landing page group are captured, which lets you judge which content attracts converting visitors.

Three reports worth building first

Leads by channel: a count of leads split by channel. Use it to see Facebook's share of total lead volume next to other sources, and to spot channels that deserve more or less budget.

Customers by campaign: new customers per month, broken out by the Facebook campaign that brought them. This shows which campaigns convert into paying accounts rather than just form fills.

Revenue by campaign: monthly revenue attributed to each originating campaign. In the illustrated example, the chart shows $65,000 of new revenue from Facebook Ads in August; spending less than that amount on the channel in the same period would imply a positive return. Treat that figure as a worked illustration of how to read the report, not as a benchmark for your account.

Setup checklist and failure triage

Work through these checks in order:

  1. Script present on every page that hosts a lead form, not just the homepage.
  2. All five hidden fields exist on every form, spelled exactly as listed.
  3. Every Facebook ad URL carries the same UTM structure.
  4. A test click from a live ad produces a lead with all five fields populated.
  5. NetSuite reports group by the drilldown fields rather than free-text source notes.

If fields are blank, suspect a missing hidden input or a script that is not loading. If fields are populated but reports look wrong, suspect inconsistent UTM values or a report grouped on the wrong field. If only some leads carry data, check whether forms on secondary pages were updated.

Where to go next

Once the pipeline is verified, the useful work shifts from setup to interpretation: comparing channels, pruning campaigns that never convert, and reinvesting in the ones that do. The same captured data supports all three, provided the field names and UTM conventions stay stable over time.

Hidden field values for a sample Facebook ad click
Hidden fieldValue in the exampleComes from
ChannelPaid SocialChannel classification
Channel Drilldown 1Facebookutm_source
Channel Drilldown 2Brand Campaignutm_campaign
Channel Drilldown 3North America Ad Grouputm_term (ad set)
Channel Drilldown 4Green Adutm_content (ad)

Illustrative values only; actual values depend on the UTM parameters placed behind each ad.

Suggested UTM convention for Facebook Ads
ParameterSuggested value
UTM MediumPaid social
UTM SourceFacebook
UTM CampaignCampaign name
UTM TermAd set name
UTM ContentSpecific ad

A convention, not a requirement; any consistent structure works.

Frequently asked questions

Do the hidden fields need exact names?

Yes. The five fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. The script writes into fields by name, so renaming them breaks the connection.

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

The UTM values are stored in a browser cookie when the visitor first arrives, so they remain available and are written into the hidden fields whenever the form is submitted, regardless of which page hosts it.

What if some campaigns use utm_source=facebook and others use utm_source=facebook.com?

Both are still classified as Paid Social, because the classification step is built to tolerate inconsistent UTM usage rather than requiring a single spelling.

Can I report on channels other than Facebook?

Yes. Organic Search, Organic Social, Referral and Direct are classified alongside Paid Social, so Facebook performance can be compared with every other channel in the same report.

Where do the reports get built?

Either in NetSuite's native reporting tools or in a BI tool such as Microsoft Power BI or Google Data Studio connected to the same data.