Send UTM Parameters into SaaSOptics: A Four-Step Attribution Setup
SaaSOptics gives you billing and customer management reports such as ARR, MRR and churn. Those totals tell you how the business is doing, but they do not tell you which marketing channel or campaign produced each customer. Adding UTM parameters to your campaigns and carrying that data into SaaSOptics customer records closes that gap. This guide walks through the four-step setup, the two ways to move attribution data from a signup form into SaaSOptics, and the reporting questions the resulting records can answer.
Why UTM data belongs in SaaSOptics
SaaSOptics is built around billing and customer management, and its reports provide metrics and insights such as ARR, MRR and churn. Those numbers are useful for a holistic view of performance, but they become more actionable when you can break them down by marketing channel and campaign. With that breakdown, you can see which channels waste budget and which ones produce a return.
The goal is not to replace SaaSOptics reporting. It is to give each customer record enough marketing context that the same reports can be filtered or grouped by the channel and campaign that brought the customer in.
How the attribution layer works
The workflow described here relies on a third-party attribution tool installed on your marketing site. When a visitor arrives, it captures information about how that visitor reached the site, similar to Google Analytics. It then categorizes visitors into channels such as Organic Search, Paid Search, Paid Social, Organic Social and Referral based on the campaign that directed them, and it can also capture organic arrivals.
The data is stored in a cookie in the visitor's browser. When that visitor signs up for your SaaS product, the stored information can be passed into SaaSOptics. The attribution tool is an independent product; this guide describes how it works with SaaSOptics rather than presenting it as part of the SaaSOptics platform.
The four-step setup
The setup follows a simple sequence: tag your campaigns, let the attribution layer store the data, pass it into SaaSOptics at signup, then report on it. Each step has a specific job, and skipping one usually shows up later as missing or incomplete channel data.
Step 1: Add UTM parameters to your ads and campaigns
Start by adding UTM parameters to every ad and marketing campaign you run. That includes paid social campaigns on platforms such as Facebook, Instagram, LinkedIn and Twitter, as well as bespoke campaigns with a trade publication. Wherever you run ads, put UTM parameters behind them.
Once those parameters are in place, the attribution layer can begin measuring how visitors landed on your site and discovered your product.
Step 3: Send the UTM parameters to SaaSOptics at signup
Suppose someone lands on your marketing site and signs up immediately after reading about your product. The UTM parameters and marketing attribution information are sent to SaaSOptics alongside the details the visitor entered into the signup form, such as name, email and company.
There are two ways to make that handoff happen:
- Hidden fields in forms. Add hidden fields to your signup form. When a user completes the form, the attribution layer writes the UTM parameters and other attribution information into those hidden fields, and the whole bundle is sent into SaaSOptics.
- Retrieved from the cookie. Embed a simple line of code on the signup form so the UTM parameters can be read from the attribution cookie. The marketing data is then passed into SaaSOptics when the user clicks Submit. This is the better option when your form includes Signup with Google or Signup with Facebook buttons that let users sign up without manually completing the form.
Use the hidden-field method when every signup goes through a standard form submission. Use the cookie-retrieval method when OAuth-style signup buttons can bypass those fields.
Step 4: Run reports in SaaSOptics and connected tools
SaaSOptics then holds a complete set of customer information, including billing data plus UTM parameters and other attribution information. That means you can run reports in SaaSOptics, or in analytics tools connected to it, showing ARR, MRR, churn rate and similar metrics broken down by the marketing channel and campaign each customer came from.
Examples of the metrics this setup can support include:
- New trials added each month by channel or campaign
- Trial-to-customer conversion rate by channel or campaign
- New customers added each month by channel or campaign
- New MRR added each month by channel or campaign
- New ARR added each month by channel or campaign
- ARPU by channel or campaign
- Lifetime value by channel or campaign
- Customer churn rate by channel or campaign
- MRR churn rate by channel or campaign
What this setup adds beyond raw UTM capture
Other UTM capture tools exist, and a developer could install code to achieve similar functionality. The capabilities below describe how the attribution layer handles the data after capture; they are not a claim that other tools cannot do the same. Four capabilities matter most when the destination is a billing and customer system like SaaSOptics.
It captures traffic without UTM parameters
Not every visitor arrives through a tagged paid campaign. Some come from organic search or organic social, where UTM parameters are not present. The attribution layer still tracks how those users found the product and passes that marketing data into SaaSOptics.
This matters because organic discovery is part of the customer journey and should be measured alongside paid channels rather than left blank.
It remembers the source across page views and sessions
Consider a visitor who clicks a Google ad and lands on a campaign-specific landing page. Instead of signing up there, the visitor clicks Start Free Trial and moves to a separate signup page. A tool that only reads UTM parameters on the page where the signup happens would lose the original source in that scenario.
Storing the parameters in a browser cookie avoids that failure. When the visitor reaches the signup page, the original UTM parameters are still on record and can be passed into SaaSOptics. This accommodates the non-linear way people actually move through a site.
It normalizes inconsistent source values
Raw UTM parameters are often messy. One Facebook campaign might be tagged UTM_Source=Facebook, another UTM_Source=facebook, and a third UTM_Source=fb. This is especially common when different people or agencies have managed the ads over time.
Those inconsistencies are not necessarily a data problem in themselves, but they become one when reporting tools treat the three variants as three separate channels. Someone then has to stitch them together by hand. The attribution layer accounts for these inconsistencies and records them together under Paid Social.
It captures landing page data as well
Content production involves briefs, writing, editing, publishing, marketing and optimization. If the purpose of that content is to generate leads and customers, you need to know whether the effort is paying off.
Capturing landing page data lets you see whether content in general is generating leads, and it also lets you compare individual pieces. Over time, that shows which topics and writing formats lead to higher conversions.
Setup checklist and failure distinctions
Use this checklist to confirm each part of the setup is in place before you rely on the reports.
- Every paid campaign URL carries UTM parameters, including paid social and bespoke publication campaigns.
- The attribution script is installed on the marketing site and is loading on landing pages.
- The signup form either includes hidden fields for attribution data or includes the cookie-retrieval code.
- If the form has Google or Facebook signup buttons, the cookie-retrieval method is used.
- SaaSOptics customer records show channel and campaign values after a test signup.
- Reports can group ARR, MRR and churn by channel or campaign.
Two failures look similar but have different causes. If attribution is missing entirely from a signup, check whether the form is using hidden fields while an OAuth button bypassed them, or whether the cookie was never set because the landing page lacked the script. If attribution is present but split across several channel values, the cause is inconsistent UTM source strings rather than a broken handoff.
Getting started
If you want in-depth reports that combine UTM parameters and marketing data with SaaSOptics billing records, the four-step setup above is the path: tag campaigns, store attribution in a cookie, pass it into SaaSOptics at signup, and report by channel or campaign. The result is a customer record that carries both revenue and acquisition context. A third-party attribution tool supports this workflow; the steps themselves apply to any attribution layer that stores UTM data in a browser cookie and hands it to SaaSOptics at signup.
Frequently asked questions
Should I use hidden fields or cookie retrieval to pass UTM parameters into SaaSOptics?
Use hidden fields when every signup goes through a standard form submission. Use cookie retrieval when the form includes Signup with Google or Signup with Facebook buttons, because those buttons can let users sign up without manually completing the form and therefore without filling the hidden fields.
Can organic traffic be attributed if there are no UTM parameters?
Yes. The attribution layer categorizes visitors into channels such as Organic Search, Paid Search, Paid Social, Organic Social and Referral, and it can capture organic arrivals even when no UTM parameters are present.
What happens if a visitor signs up on a different page from the ad landing page?
The UTM parameters are stored in a browser cookie, so the original source remains available when the visitor reaches the signup page. That data can then be passed into SaaSOptics even though the signup happened on a separate page.
Why do my Facebook campaigns show up as several channels?
Raw UTM source values such as Facebook, facebook and fb can be treated as separate channels by reporting tools. The attribution layer normalizes these variants and records them together under Paid Social.