Skip to content

Connect Google Analytics Source Data to FastSpring in 4 Steps

Google Analytics tells you where traffic came from. It does not, on its own, tell you which visitors became paying customers, what they spend, how long they stay, or how often they leave. To answer those questions you need the acquisition data to travel with each signup into the billing platform, where revenue events already live.

This guide walks through a four-step setup that carries channel, campaign and landing-page information from a visitor's browser into FastSpring. Once the data is there, you can segment subscription metrics by the marketing source that produced each customer.

Why send source data into FastSpring

FastSpring holds the commercial record: plans, trials, payments, recurring revenue and cancellations. Google Analytics holds the acquisition record: which channel, campaign and page brought a visitor in. Neither system alone can attribute revenue to a source.

Joining the two lets you ask questions such as how many customers came from a given ad platform, what the average monthly recurring revenue is for customers from one network versus another, and what churn looks like for visitors who arrived through organic search. The setup described here is a way to make that join happen at signup time, rather than trying to reconcile two unrelated datasets after the fact.

How the capture mechanism works

A small script on your site inspects the technical signals a visitor arrives with and classifies the visit into a channel, such as paid social, paid search or referral. That classification, plus supporting detail, is written to a cookie in the visitor's browser.

When the visitor completes a signup, the stored values are copied into hidden form fields and submitted alongside the details the visitor typed. FastSpring receives both sets of data at the same moment, so the new record carries its own acquisition context.

A useful mental model is a label attached at the door and read at the till. The label is created when the visitor first lands; it is read when they sign up; and the till — FastSpring — stores it next to the transaction.

Step 1 — Add hidden fields to your signup forms

Create six hidden fields on each signup form. The exact field names matter because they are what the capture script looks for when it writes values in. The six fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group; the table below explains what each one carries. Match whatever spelling your form and capture script actually use for the drilldown fields, and keep it consistent across forms. If your signup flow includes Google or Facebook sign-in, a visitor can create an account without submitting a form. In that case, hidden fields will not fire. The alternative is a short JavaScript routine that reads the cookie and sends the values to FastSpring when the account is created. A help article on pulling attribution data from the cookie covers that approach.

Step 2 — Let the script fill the fields automatically

With the fields in place, the capture script reads the visitor's origin and, at form submission, writes the appropriate values into the hidden inputs. No manual entry is required from the visitor.

A worked example makes the mapping concrete. Suppose a visitor reaches your site from a brand campaign in paid search. Depending on the UTM parameters behind the ad, the fields would be populated as follows:

  • Channel = Paid search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Brand campaign
  • Channel Drilldown 3 = the brand term used in the ad
  • Landing Page = the first page the visitor saw, e.g. /blog/best-crm-software
  • Landing Page Group = the page's category, e.g. /blog

The first three drilldown levels are the ones that let you move from a broad channel view down to a specific campaign or keyword. The landing-page pair works the same way for content: the group aggregates a section, while the individual page isolates a single asset.

Step 3 — Confirm the data reaches FastSpring

On submission, the cookie values and the visitor's typed details are sent to FastSpring together. The new customer or trial record should then show the channel and landing-page fields alongside the usual contact and billing information.

Before building reports, verify one test signup end to end. Submit a form from a link carrying known UTM parameters, then open the resulting record in FastSpring and check that each of the six fields holds the value you expect. If a field is blank, the usual causes are a mismatched field name, a script that is not loading on the form page, or a signup path that bypasses the form entirely.

Step 4 — Build reports by channel and campaign

Once the fields are populated, FastSpring's reporting can segment subscription metrics by the customer's marketing channel or campaign of origin. The metrics that become available 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

You can build these views in FastSpring's own reporting tools, or pass the data to a connected analytics or business-intelligence tool for deeper analysis.

What actually gets passed into FastSpring

Two families of data are carried, and it helps to think of them as answering two different questions.

Channel data answers "how did they find us?" It records the top-level channel — organic search, paid search, paid social, referral, direct and similar — plus the drilldown detail beneath it. For paid search, for example, the drilldowns can carry the campaign, ad group and keyword.

Landing-page data answers "what did they find compelling?" It records the first page the visitor saw, such as a specific blog post, together with that page's category. The category is what lets you roll many pages up into one section and judge the section as a whole, while the individual page lets you zoom in on a single asset's performance.

Questions you can answer about channels

With channel data inside FastSpring, you can build reports that answer:

  • How many signups came from a given ad platform?
  • What is the signup-to-customer conversion rate for leads from that platform?
  • How many customers has that platform produced?
  • How much MRR or ARR has it generated?
  • What is the lifetime value of its customers, and how does that compare with other channels?
  • What is the overall return on ad spend, measured as revenue generated against spend?

These are the questions that turn a channel from a cost line into a comparable investment. A channel with a high signup count but a low conversion rate and low lifetime value looks very different from one with fewer signups but stronger retention.

Questions you can answer about content

Because the landing page and its group are captured too, the same reporting can be turned on your content:

  • How many signups did the blog produce?
  • Which individual posts delivered the most signups?
  • Which posts convert readers into customers?
  • What return does the blogging effort generate?

The group field is what makes section-level judgments possible. A blog section might attract a large volume of visitors and signups while converting only a small share into customers. Seeing that pattern lets you decide whether to keep investing in the section or move resources elsewhere — a decision that is hard to make from traffic numbers alone.

Setup checklist

  • [ ] Six hidden fields created on every signup form, with names matching the capture script
  • [ ] Field spelling consistent across forms, including the drilldown fields
  • [ ] Capture script loading on all pages that host a signup form
  • [ ] JavaScript path in place for Google and Facebook sign-in flows that skip the form
  • [ ] One test signup submitted with known UTM parameters
  • [ ] All six fields verified on the resulting FastSpring record
  • [ ] At least one channel report and one content report built
  • [ ] Reporting tool or connected BI destination chosen for deeper analysis

Getting started

Connecting acquisition data to FastSpring is a small amount of setup that changes what your revenue reporting can show. Once channel and landing-page values arrive with each signup, every subscription metric becomes sliceable by source — and content, SEO and advertising can be judged on the customers and revenue they produce rather than on traffic alone. If you are evaluating a capture tool for this job, check that it writes the six field values your forms expect, that it handles social sign-in flows, and that you can verify a test signup end to end before relying on the reports.

Step 1 — Add hidden fields to your signup forms
FieldWhat it carries
ChannelThe top-level source category, e.g. paid search, paid social, referral, direct
Channel Drilldown 1First level of detail within the channel, e.g. the network
Channel Drilldown 2Second level, e.g. the campaign
Channel Drilldown 3Third level, e.g. the ad group, keyword or brand term
Landing PageThe first page the visitor saw, e.g. /blog/best-crm-software
Landing Page GroupThe category of that page, e.g. /blog

Frequently asked questions

Can't I just read this from Google Analytics?

Google Analytics can show you traffic, sessions and goals, but it does not hold your billing events. It cannot tell you what a customer pays, how their subscription value changes, or when they churn. Those facts live in FastSpring. Attribution by revenue requires the acquisition data to be present in the billing system, which is what this setup achieves.

What if visitors sign up with Google or Facebook and never see a form?

Hidden fields only fire when a form is submitted. For social sign-in flows, use a short JavaScript routine that reads the stored cookie values and sends them to FastSpring at account creation. A help article on pulling attribution data from the cookie describes that method.

A field is arriving blank in FastSpring. Where should I look first?

Check three things in order: that the field name on the form matches exactly what the script writes, that the script is loading on the page where the form lives, and that the signup path actually submits a form rather than creating the account through a social sign-in. A single test signup with known UTM parameters will usually reveal which of the three is the cause.

Which visit gets recorded — the first one or the one just before signup?

The landing page recorded is the first page the visitor saw, and the channel classification is based on where that visitor arrived from. The landing-page group is the category of that same first page. This gives you a first-touch view of acquisition rather than a last-click view.

Do I have to build reports inside FastSpring?

No. You can use FastSpring's own reporting tools, or pass the data to a connected analytics or business-intelligence platform for more detailed analysis. The choice depends on how much modelling and visualisation you need beyond the built-in reports.