Track Google Ads Campaigns in FastSpring: Setup and Reporting Guide
If your Google Ads dashboard shows clicks and leads but your FastSpring account cannot tell you which campaigns produced paying customers, you are making budget decisions with half the picture. This guide explains how to carry Google Ads campaign data into FastSpring so you can compare campaigns by customers and revenue, not just form completions.
Why customer and revenue tracking matters more than lead counts
A lead-count report can make one campaign look efficient while another looks weak. The difference appears when you follow each lead through to purchase. Consider a B2B SaaS company running two Google Ads campaigns: one for task management software and one for project management software. A visitor-and-lead report might show equal spend and similar lead volume, which suggests the campaigns are comparable. A customer-and-revenue report can show a very different outcome.
The campaign comparison tables below preserve the original example figures. Read them as an illustration of why downstream data changes the decision, not as a benchmark for your own account. The first table shows spend, visitors, and goal completions. The second adds leads, customers, and revenue.
[table0001]
[table0002]
With only the first table, the task management campaign appears more efficient because it produced more visitors and goal completions for the same spend. With the second table, the project management campaign produced more customers and far more revenue. The lesson is not that one campaign type always wins; it is that spend and lead volume alone cannot tell you which campaign deserves more budget.
When you can see campaign performance through to customers and revenue, you can evaluate the real economics. The supplied example highlights several useful comparisons: customer count, trial-to-customer conversion, average customer value, and cost per customer. Each of these depends on having the campaign source attached to the customer record, not just to the initial visit.
A note on the figures: the original article's bullet list of derived metrics does not agree with its own table. The bullets state 12 customers for the project management campaign, a 60% versus 14% conversion rate, average customer value of $2,083 versus $1,142, and cost per customer of $416 versus $714. The table shows 2 versus 5 customers and $8,000 versus $25,000 in revenue. Because the two sets cannot both be right, the derived metrics below are recomputed from the table rather than repeated from the bullets. From the table: conversion from 10 leads is 10% (task) versus 50% (project); average customer value is $4,000 versus $5,000; and cost per customer is $1,000 versus $400. Treat these as arithmetic on the illustrative table, not as a benchmark.
The four-step capture sequence
The workflow has four stages: tag the ad URLs, let the attribution tool recognize and store the campaign data, pass that data into FastSpring when a form is submitted, and report on the results. Each stage has a distinct failure mode, so treat them as a checklist rather than a single setup task.
- Add UTM parameters to every Google Ads campaign URL. UTM parameters are extra text appended to the destination URL. A typical structure for a Google Ads campaign uses utm_medium for the channel, utm_source for the platform, utm_campaign for the campaign name, utm_term for the ad group, and utm_content for the specific ad. The exact values are yours to choose, but consistent naming across campaigns is what makes later reporting possible.
- Let the attribution tool scan for those parameters and store the result in a cookie in the visitor's browser. When the tool finds the expected UTM parameters, it assigns the visitor to a channel such as Paid Search and keeps that information available for later form submissions.
- Send the stored data into FastSpring when the visitor completes a form. There are two supported methods. Hidden fields in forms give the attribution tool a place to write the campaign data automatically; when the form is submitted, that data travels with the name, company, email address, and other form entries. Retrieving from the cookie uses a short JavaScript line during registration to read the stored UTM parameters and pass them into FastSpring. The cookie method is useful when users sign up through a Google or Facebook account and therefore do not complete a traditional form.
- Build reports in FastSpring or in connected analytics tools. Once campaign data sits alongside each customer, you can report new customers by campaign, new revenue by ad group, average revenue per customer by ad, customer lifetime value by channel or campaign, and churn rate by channel or campaign. The supplied source also points to syncing FastSpring data into tools such as Profitwell and Chartmogul for more detailed analysis; those destinations should be treated as optional integrations to verify in your own account.
A field and control map for the capture step
Use this map to decide what each UTM parameter is for and which FastSpring capture method fits your signup flow.
UTM parameter roles:
- utm_medium identifies the channel, for example paid search.
- utm_source identifies the platform, for example Google.
- utm_campaign carries the Google Ads campaign name.
- utm_term carries the ad group name.
- utm_content carries the specific ad identifier.
Capture method decision:
- Choose hidden fields when your signup form is the primary conversion point and you can add fields that the attribution tool populates automatically.
- Choose cookie retrieval when users may register through a Google or Facebook account and skip a standard form, or when you need the stored parameters read during a registration flow.
Reporting fields to preserve:
- Campaign, ad group, keyword or term, and ad content should remain available on the customer record.
- Landing page and landing page category are also useful because they let you compare a whole content section against individual posts.
A practical checklist before launch:
- Every active Google Ads campaign URL carries the same UTM naming pattern.
- The attribution tool is installed on all pages where a visitor might land.
- The chosen capture method is tested with a real form submission or registration path.
- FastSpring records show the campaign field populated on a test customer.
- At least one report groups customers or revenue by campaign.
What the attribution layer adds beyond raw UTM values
Handing raw UTM strings straight to FastSpring is possible, but it leaves three gaps that a dedicated attribution layer is designed to close.
Persistence across the journey. Raw UTM capture depends on the parameters being present at the moment of conversion. Picture a visitor who clicks a paid ad, reads the landing page, then navigates to a separate signup page before converting. The original query string is no longer in the address bar, so a naive setup records nothing. A cookie-based layer writes the campaign details on arrival and reads them back at signup, so the source survives the page change.
Consistency of source values. Teams tag ads over months, and the source field drifts: one batch uses a full domain, another a bare lowercase word, another an older term like adwords. Passed through raw, those become three separate rows in a report that should be one. A layer that maps known variants onto a single channel (for example, Paid Search) collapses them before they reach FastSpring, so you compare channels rather than spellings.
Coverage beyond paid search. A tool that records every visit, not only tagged ad clicks, can also attribute organic search, organic social, and direct traffic. That matters when you want to compare paid acquisition against the channels it competes with for budget, rather than judging ads in isolation.
The supplied source also describes landing page capture. Recording both the specific landing page and its category lets you view performance at the section level or at the individual post level. That is useful when you want to know whether a blog section as a whole contributes to customer acquisition or whether one article is doing the work.
Failure distinctions: what went wrong when the data is missing
Missing campaign data usually comes from one of four places, and each has a different fix.
- No campaign value on the customer record: check whether the UTM parameters were present on the landing URL and whether the attribution tool was loaded on that page.
- Campaign value present on the first page but absent at signup: check whether the capture method reads from the stored cookie rather than relying on the signup page URL.
- Several source values for the same platform: check for capitalization and naming inconsistencies in utm_source and normalize them before comparing campaigns.
- Reports show customers but not revenue: check that the revenue field is joined to the same customer record that carries the campaign data, and that the report groups by the campaign field rather than by a visit-level field.
A quick diagnostic order is: confirm the click URL, confirm the stored cookie, confirm the form or registration handoff, then confirm the report grouping. Working in that order prevents you from changing report settings when the real gap is an untagged ad.
Reports worth building first
Start with reports that answer budget questions directly. New customers by campaign shows which campaigns bring in accounts. New revenue by ad group shows which targeting themes produce value. Average revenue per customer by ad shows whether a specific creative attracts higher-value buyers. Customer lifetime value by channel or campaign and churn rate by channel or campaign show whether the customers acquired are durable. These reports are more useful when the campaign field is stored on the customer record and the revenue field is joined to that same record.
If you use an external analytics tool, treat the connection as a separate integration to validate. The supplied source mentions Profitwell and Chartmogul as examples of tools that can receive FastSpring data for deeper reporting; availability and setup details should be checked against your own accounts.
| Metric | Task Management Campaign | Project Management Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Illustrative example from the original article. Figures are not a benchmark and should not be treated as current performance data.
| Metric | Task Management Campaign | Project Management Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |
Illustrative example from the original article. Figures are not a benchmark and should not be treated as current performance data.
Frequently asked questions
Do I need UTM parameters if I already use Google Ads conversion tracking?
Google Ads conversion tracking tells you that a conversion happened, but it does not automatically attach the campaign name to the customer record inside FastSpring. UTM parameters provide the campaign, ad group, and ad identifiers that the attribution layer stores and passes into FastSpring. The two systems answer different questions: conversion tracking measures the event, while UTM-based capture connects the event to a specific customer and revenue record.
What is the difference between hidden fields and cookie retrieval?
Hidden fields are form elements that the attribution tool fills automatically; when the visitor submits the form, the campaign data is sent to FastSpring with the other form entries. Cookie retrieval reads the stored UTM parameters during registration using a short JavaScript line. Hidden fields suit standard signup forms, while cookie retrieval suits flows where the user registers through a Google or Facebook account and does not complete a traditional form.
Why do my reports show several different Google sources?
Raw UTM values can vary in capitalization and wording, such as a capitalized source name, a lowercase version, or a legacy term. If those raw values are passed through without normalization, each variation can appear as a separate source. An attribution layer that recognizes these variations and assigns them to a single channel reduces the manual work of stitching sources together.
Can I see which blog posts produce customers?
Yes, if the attribution setup records both the landing page and the landing page category. The specific page identifies the individual post, while the category identifies the section, such as a blog. That lets you compare the performance of a whole content section against individual articles.
| Task Management Campaign | Project Management Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
| Task Management Campaign | Project Management Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |