Skip to content

Send UTM parameters into FastSpring in 4 steps

FastSpring already reports subscription performance such as MRR, ARR and churn. Adding marketing attribution lets you break those same metrics down by the channel and campaign that brought each customer in, so you can see which activity produces trials, customers and revenue — and which does not.

What the attribution layer does

An attribution script installed on your website runs when traffic lands, records how the visitor arrived, and classifies that visit into channels and campaigns such as Paid Search, Organic Search and Referral. That classification is stored in the visitor's browser cookie. When the visitor later signs up, the contact details — name, email and similar fields — are sent to FastSpring together with the stored marketing data. From then on, subscription reporting can be segmented by the channel and campaign behind each customer, not just reported as a single total.

The 4 steps

Step 1 — Tag paid activity. Review every running or scheduled paid campaign, including paid social and bespoke placements, and add UTM parameters to each ad so the landing visit can be recognised. Step 2 — Store the parameters in a cookie. The installed script checks the visitor's URL for UTM parameters and, when found, stores them in the browser cookie. This is what allows the data to persist across multiple page views and sessions. Step 3 — Pass the data at signup. When a visitor completes a signup form, their details plus the stored UTM data are sent into FastSpring. There are two routes: hidden fields added to the form that the script populates before submit, or a small line of code on the form that retrieves the values from the cookie. The cookie route is preferable when signup also offers sign-in with Google or a social account, where hidden fields may not be present. Step 4 — Report by channel and campaign. With attribution fields on the FastSpring record, metrics such as trials, conversions, new customers, MRR, ARR, ARPU, lifetime value and churn can each be broken down by channel or campaign.

Why attribution beats raw UTM capture

Capturing raw UTM parameters alone misses three things. First, not every visitor arrives through a paid ad, so organic arrivals would go unmeasured without channel classification for traffic with no UTMs. Second, URL-only capture fails when a visitor explores the site before signing up on a different page; cookie storage keeps the original campaign attached regardless of which page converts. Third, raw values are messy: the same network tagged as Facebook, facebook and fb would otherwise split into three apparent channels. Normalising variants into a single channel removes manual reconciliation. Landing page data can also be captured, so individual content pieces can be credited with customers in the same way as a paid campaign.

Pre-flight checklist

Use this checklist before trusting channel-level FastSpring reports:

  • Every active paid campaign carries consistent UTM parameters.
  • The attribution script is installed on all landing pages, not just campaign pages.
  • A test visitor arriving from a tagged ad, browsing to a second page, and then signing up produces a FastSpring record with the original channel and campaign.
  • A test visitor arriving with no UTM parameters is still classified by channel.
  • Signup via social or Google sign-in still passes the stored values.
  • Variant spellings of the same source roll up into one channel in reports.
  • At least one report is built for trials, one for new customers and one for MRR, each segmented by channel, to confirm the fields are usable.
Subscription metrics that can be broken down by channel or campaign
ReportSegmented by channel or campaign
New trials added each monthYes
Trial to customer conversion rateYes
New customers added each monthYes
New MRR added each monthYes
New ARR added each monthYes
ARPUYes
Lifetime valueYes
Customer churn rateYes
MRR churn rateYes

Metrics listed in the source as available once attribution data is present in FastSpring; actual availability depends on the implemented integration.

Two ways to pass UTM data at signup
MethodHow it worksBest suited to
Hidden fields in formsScript writes UTM data into hidden fields; values are submitted with the formStandard signup forms
Retrieved from the cookieA line of code on the signup form reads UTM parameters from the cookieForms offering Google or social sign-in

Two delivery methods described in the source for passing stored UTM data into FastSpring at signup.

Frequently asked questions

How do UTM parameters get from an ad click into FastSpring?

Add UTM parameters to paid ads and campaigns, install the attribution script so it reads those parameters from the landing URL and stores them in the visitor's browser cookie, then pass the stored values into FastSpring at signup — either through hidden form fields populated on submit or by retrieving them from the cookie with a line of code on the signup form. Once the values arrive with the contact record, subscription metrics can be segmented by channel and campaign.

What happens for visitors who arrive without UTM parameters?

Yes. When no UTM parameters are present, the attribution logic can still classify how the visitor arrived — for example Organic Search or Organic Social — and send that channel information into FastSpring alongside signup details.

Does the campaign data survive if someone browses before signing up?

Because the values are stored in the browser cookie rather than only in the landing URL, they persist across page views and sessions. A visitor can browse other pages before signing up and the original campaign data is still passed through at signup.

Why normalise UTM values instead of passing them through raw?

Inconsistent tagging — for example Facebook, facebook and fb used for the same network — can otherwise appear as separate channels in reports. Normalising those variants into one channel avoids manual stitching and keeps channel reporting cleaner.

Can content performance be measured the same way as ad performance?

Landing page data can be captured alongside channel and campaign data, so customers generated from individual content pieces can be compared with customers from paid campaigns, helping identify which topics to produce more of.