Skip to content

Send UTM Parameters Into Recurly and Report Subscription Performance by Campaign

Recurly can report subscription metrics, but it needs marketing origin data attached to each customer. This guide explains how to capture UTM parameters and broader channel data on a website, carry them through to signup, and then break down trials, customers, revenue and churn by the campaign that produced them.

The goal: connect campaign origin to subscription value

Recurly already handles billing and customer management, including reports for measures such as MRR, ARR and churn. The missing piece is origin: without channel or campaign data on the customer record, those reports cannot show which marketing activity produced valuable subscribers.

The workflow has four stages:

  • Tag paid activity so the arriving visit carries UTM parameters.
  • Store those parameters, plus classified channel data, in a browser cookie when the visit begins.
  • Attach the stored data to the signup submission sent to Recurly.
  • Segment subscription reports by channel, campaign or landing page.

A useful decision check is to confirm that each stage works before relying on reports: the ad link contains the parameters, the cookie is set on the landing page, the signup submission includes the stored values, and the resulting Recurly record can be grouped in a test report.

Step 1: Tag campaigns and preserve the values in a cookie

Start with the campaigns that need measurement. Add UTM parameters to advertising on social platforms such as Facebook, Twitter and LinkedIn, search advertising on Google and Bing, and bespoke placements such as trade publications.

Tagging alone is not enough if the signup happens later on another page. The attribution script therefore reads the parameters from the arrival URL and stores them in a cookie. That cookie preserves the original campaign information while the visitor browses, including when a landing page leads to a separate trial or signup page.

For example, a visitor may click a Google ad, read a campaign landing page, then select a trial button and complete signup elsewhere. Because the original parameters were stored at arrival, they can still accompany the eventual signup instead of disappearing when the URL changes.

Step 2: Attach stored data to the signup submission

When the visitor submits signup details, include the stored marketing data alongside ordinary form information such as name, email address and company name.

There are two practical routes:

  • Hidden fields in forms: the stored values are written into hidden fields, then submitted with the rest of the form.
  • Cookie retrieval with JavaScript: a small script reads the stored values during submission. This route is especially useful for Signup with Google or Signup with Facebook, where no conventional form is completed.

Choose hidden fields for standard forms because the data travels with the submission itself. Choose cookie retrieval when the sign-up flow bypasses the form, then test that the values still reach the Recurly record.

Step 3: Report subscription metrics by channel and campaign

Once origin data is present in Recurly, subscription reporting can be segmented instead of viewed only as a single total. Useful breakdowns include:

  • New trials by channel or campaign
  • Trial-to-customer conversion by channel or campaign
  • New customers by channel or campaign
  • New MRR and new ARR by channel or campaign
  • ARPU by channel or campaign
  • Lifetime value by channel or campaign
  • Customer churn and MRR churn by channel or campaign

These views help answer practical questions such as which paid social campaign produces the highest average MRR, or whether customers from organic search retain better than customers from a particular advertising channel.

Why classified channel data beats raw UTM values alone

Raw UTM capture has three common weaknesses. First, it misses traffic that has no UTM parameters, such as Organic Search, Organic Social, Referral and Direct visits. Classifying every visit means every customer has an origin, not only customers from tagged paid campaigns.

Second, raw parameters are often lost when signup occurs on a different page from the landing page. Cookie storage solves that by retaining the arrival data across page views and sessions.

Third, inconsistent tagging creates fragmented reporting. The same social source might appear as Facebook, facebook or fb depending on who built the campaign. Normalising those variants into a consistent channel such as Paid Social avoids having to stitch duplicate sources together manually.

Landing-page capture adds another layer: recording the landing page and its category shows whether particular content, including blog posts or detailed guides, contributes to leads and customers.

Choosing how to pass the data
SituationPreferred routeWhat to verify
Standard signup formHidden fieldsStored values are populated before submission and appear on the Recurly record.
Signup with Google or FacebookJavaScript cookie retrievalValues are read at sign-up even though no form is completed.
Visitor arrives from an untagged channelClassified channel dataOrganic, referral or direct origin is recorded rather than left blank.

Both routes carry the stored marketing data into Recurly with the signup submission.

Frequently asked questions

How do UTM parameters reach Recurly?

Add UTM parameters to paid campaigns, install the attribution script so it stores the values in a browser cookie on arrival, then pass those stored values with the signup form submission into Recurly. After that, subscription reports can be segmented by channel or campaign.

Does this only work for paid campaigns?

Yes. Channel classification also covers visits without UTM parameters, including Organic Search, Organic Social, Referral and Direct, so non-paid customers are not left unclassified.

Which submission method should I use?

Use hidden form fields populated from the stored data for normal forms. For social sign-up buttons that bypass a form, retrieve the stored values with JavaScript at sign-up and include them in the submission.

Why not report on raw UTM values alone?

Raw values can create duplicate sources when capitalization or abbreviations differ, such as Facebook, facebook and fb. Normalising them into a consistent channel such as Paid Social makes reporting cleaner.