Skip to content

Send UTM parameters into Paddle for channel-level revenue reporting

Subscription tools show totals for trials, customers, MRR and churn, but those totals do not reveal which acquisition channel produced them. Passing UTM and channel data into Paddle at signup lets you break those metrics down by the campaign and channel that brought each customer in.

How arrival data reaches Paddle

A visitor arrives from an ad, search result, social post or referral. The arrival details — including any UTM parameters in the initial URL — are categorised into channels such as Paid Search, Paid Social, Organic Search and Referral, similar to analytics tools, and stored in the browser. When that visitor later completes signup, the stored channel data travels into Paddle alongside the name, email and other details they entered. You can then segment revenue reporting to see which channels and campaigns drive customers and revenue.

Four steps to capture UTM parameters in Paddle

  1. Tag every paid campaign. Append UTM parameters to paid social, search and trade-publication ads so the landing visit can be identified.
  2. Store the arrival data in a cookie. Once the tracking script is on the site, it reads UTM parameters from URLs and saves them in the visitor's browser.
  3. Pass the data at signup. The stored marketing data is sent into Paddle with the user's signup information.
  4. Report by channel and campaign. Use the attached data to break down subscription performance.

Two ways to pass the data at signup

Hidden fields in forms: add hidden fields to the signup form and write the stored data into them. When the user submits the form, that data reaches Paddle with the other form entries. Retrieved from the cookie: add a small line of code to the form to read the stored data and pass it along. This is the better option when Signup with Google or Signup with Facebook lets users bypass manual form entry.

What you can report once the data is attached

Once channel data is attached to each Paddle customer, you can compare performance across acquisition sources instead of looking only at blended totals. Useful breakdowns include new trials by channel or campaign, trial-to-customer conversion, new customers, new MRR and new ARR, ARPU, lifetime value, customer churn rate and MRR churn rate.

Why categorised channel data beats raw UTM values alone

Captures all traffic: visitors without UTM parameters, such as those arriving from Organic Search or Organic Social, can still be detected and categorised, so organic acquisition is not invisible in Paddle. Remembers data across pages and sessions: a visitor may land on a features page from an ad and sign up later on a separate app signup page. Because the data is stored in the browser, it does not disappear when they leave the landing page. Provides cleaner data: inconsistent tagging — for example Facebook, facebook and fb — can otherwise appear as three separate channels. Normalising those variants into Paid Social avoids manual reconciliation in reports. Captures landing page data: the landing page URL and subdirectory are also recorded, so you can see which content areas, such as a blog, generate signups, customers and revenue.

Example: landing page and signup page are different

Worked example: a visitor clicks a Google ad to a features page, browses, then moves to a separate signup page to start a trial. The UTM data from the first page is still stored in the browser, so it is attached to the Paddle record even though the signup happens elsewhere. In Paddle, that trial can then be counted under the original campaign rather than as unattributed or direct traffic.

Pre-launch checklist

Before you rely on channel reporting, check that every paid campaign is tagged, that the stored data survives navigation to the signup page, that both manual and social signup paths pass the data, and that variant UTM values roll up into one channel. Then confirm a test signup appears in Paddle with the expected channel, campaign and landing page.

Choosing how to pass UTM data at signup
Signup pathHow data is passedBest for
Hidden fields in formsStored data is written into hidden fields and submitted with name, email and other form entriesManual signup forms
Retrieved from the cookieA line of code reads the stored data and passes it into PaddleForms with Signup with Google or Signup with Facebook

Two passing methods described in the source; choose based on whether social signup bypasses the form.

Frequently asked questions

How do UTM parameters get into Paddle?

Add UTM parameters to paid campaigns, store the arrival data in the visitor's browser, pass it with the signup details into Paddle, then segment subscription reports by channel and campaign.

Which signup method should I use to pass the data?

Use hidden fields when the signup form is completed manually. Retrieve the stored data from the cookie when social signup options may bypass the form, so attribution is not lost.

Why store UTM data in a cookie instead of reading the URL at signup?

Storing arrival data in the browser preserves it across page views and sessions. That matters when a visitor lands on a features page and later signs up on a separate app page.

Why normalise UTM values before reporting?

Raw values such as Facebook, facebook and fb can split one channel into several reports. Normalising those variants into a single channel such as Paid Social gives cleaner segmentation.