Skip to content

How to send UTM parameters into Chargify

Subscription dashboards tell you how the business is doing overall. They rarely tell you which campaign produced the customer. Chargify holds the billing relationship, so the natural place to answer that question is the customer record itself — provided the marketing source travels with the person from first visit to signup. This guide walks through tagging, cookie-based capture, the two ways to hand data to Chargify, and the reports that become possible once channel and campaign sit alongside MRR, ARR and churn.

Why billing data alone is not enough

MRR, ARR and churn are useful macro indicators, but they describe the whole book of business at once. To judge acquisition, you need those same numbers sliced by the channel and campaign that produced each account. Chargify can report on subscription metrics, yet it can only group by marketing source if that source was written onto the customer in the first place. The work therefore happens before the report: capture the source at signup, store it on the record, then segment.

What the tracking script does

A small script on the site inspects how each visitor arrived, including whether the landing URL carried UTM parameters. It sorts the visit into a marketing channel and campaign — Paid Search, Paid Social, Organic Search and others — and keeps that classification in the visitor's browser. When the visitor later completes a signup form, the stored attribution is submitted together with the details the person typed, such as first name, last name and contact information. From that point the record in Chargify can be segmented by source.

Step 1: Tag every paid destination

Start with the ads and campaigns already running. Any paid placement that sends traffic to your site needs UTM parameters on its destination URL, including social platform ads and one-off campaigns arranged with trade publications. Untagged placements will still produce signups, but the channel and campaign behind them cannot be reconstructed afterwards. Tag first, then verify a sample link resolves with the parameters intact.

Step 3: Choose how the data reaches Chargify

There are two delivery routes, and the right one depends on how people sign up.

  • Hidden form fields. Add hidden fields to the signup form and the script writes the UTM parameters and other attribution values into them. On submit, those values travel to Chargify with the rest of the form data — name, email, company and anything else you collect.
  • Read from the cookie. A short line of JavaScript pulls the values out of the stored cookie at signup time and passes them along. This route matters when visitors can register with a Google or social account, because there is no form for hidden fields to sit in.

Many products need both: hidden fields for the standard form, cookie retrieval for the social signup path.

Step 4: Report by channel and campaign

Once attribution is on each customer record, Chargify can group the usual subscription metrics by marketing source instead of showing them only in aggregate. The reporting set includes new trials per month by channel or campaign, trial-to-customer conversion rate, new customers per month, new MRR and new ARR per month, ARPU, lifetime value, customer churn rate and MRR churn rate — each split by channel or campaign.

Where raw UTM capture falls short

Capturing the raw parameter string is the minimum, not the finish line. Four gaps tend to appear in practice.

  • Organic traffic carries no UTM parameters at all, so a purely parameter-based setup records nothing for visitors arriving from organic search, referrals or direct visits. Channel classification can still identify those sources.
  • Parameters are frequently lost between the ad landing page and the signup page. If capture only works when the parameters are present on the signup page itself, a two-page journey silently drops the source. Cookie storage removes that dependency.
  • Source values drift. Different teams and agencies may tag the same platform with different spellings or abbreviations, which raw reporting treats as separate channels requiring manual stitching. Normalising those variants into one channel grouping keeps reports readable.
  • Content performance is invisible. Recording the landing page and landing page category alongside the campaign shows whether blog and content work actually contributes signups.

Worked example: variant spellings, one channel

Imagine a team running three LinkedIn campaigns. One URL uses a capitalised source value, a second uses all lowercase, and a third uses a short abbreviation. A raw parameter report in Chargify shows three separate channels, each holding a slice of the trials and MRR, and someone has to reconcile them by hand before the numbers can be trusted. When normalisation is applied at capture time, all three visits resolve to a single Paid Social grouping, so the trial count, conversion rate and new MRR for that channel appear on one line. The lesson generalises: agree the channel taxonomy before tagging, and let the capture layer enforce it rather than relying on every person who builds a URL.

Pre-launch checklist

  • Every paid placement, including social ads and publication campaigns, carries UTM parameters.
  • The tracking script is installed site-wide, not only on the signup page.
  • A test journey that starts on a landing page and finishes on a separate signup page still carries the source through.
  • Hidden fields exist on the standard signup form and are mapped into Chargify.
  • The cookie-retrieval route is wired for Google and social signups.
  • Channel naming rules are agreed, so variant spellings collapse into one group.
  • A first report is checked for a suspiciously large Direct or unknown bucket, which usually signals a broken capture path.
Choosing a capture method by signup situation
Signup situationRecommended methodWhat it prevents
Standard form with name, email and company fieldsHidden fields populated by the scriptAttribution arriving without the rest of the form submission
Google or social account signup with no formRead values from the cookie at signupSource being lost because there are no fields to fill
Ad landing page separate from signup pageCookie storage plus either delivery routeParameters disappearing between pages
Organic search, referral or direct arrivalChannel classification rather than raw parametersAn empty source field for non-paid traffic
Multiple teams tagging the same platform differentlyNormalisation into a single channel groupOne channel split into several report rows

Describes the capture and delivery routes covered in this guide; the specific field names and mappings depend on your own form and Chargify configuration.

Subscription metrics available once channel data is attached
MetricSplit by
New trials added each monthChannel or campaign
Trial to customer conversion rateChannel or campaign
New customers added each monthChannel or campaign
New MRR added each monthChannel or campaign
New ARR added each monthChannel or campaign
ARPUChannel or campaign
Lifetime valueChannel or campaign
Customer churn rateChannel or campaign
MRR churn rateChannel or campaign

Reflects the reporting set described in this guide; available report types and groupings depend on your Chargify plan and configuration.

Frequently asked questions

Do I need UTM parameters on organic traffic?

No. Organic arrivals usually have no parameters in the URL, which is why channel classification matters: organic search, referral and direct visits can still be identified and attached to the record. Tagging is for the paid placements you control.

What happens if the ad lands on a page other than the signup page?

Nothing is lost, provided the source is stored in the visitor's browser at landing time. The values are read back when the signup happens, wherever on the site that occurs. A setup that only reads parameters from the current URL would lose them in this scenario.

How do signups via Google or social accounts get attributed?

There is no form to hold hidden fields in that flow, so the values are pulled from the stored cookie at signup time and passed along with the account creation.

Why do my reports show several versions of the same channel?

Inconsistent tagging produces variants such as capitalised, lowercase and abbreviated source values. Raw reporting treats each as a separate channel. Normalising variants into one channel group at capture time keeps the report consolidated.

Can I see which landing pages produce customers?

Yes, when the landing page and landing page category are captured alongside the campaign. That lets you compare content-driven arrivals against paid ones in the same reporting view.