Skip to content

Send UTM Parameters Into Zuora and Report Subscription Metrics by Campaign

Overall subscription figures show how a business is performing, but they do not show which marketing activity produced the customers behind those figures. Passing campaign data into Zuora alongside each signup makes it possible to split measures such as churn, monthly recurring revenue and annual recurring revenue by channel and campaign, and to judge which sources bring stronger customers.

How campaign data reaches Zuora

A website script observes how a visitor arrived and which pages they viewed, then groups that visit under a marketing channel or campaign. Categories can include direct, organic search, paid search and referral traffic. The classification and any UTM values are held in the visitor's browser cookie. When the visitor submits a registration or signup form, that stored marketing information is forwarded into Zuora together with the form details such as name, email address and company. Once inside Zuora, subscription reporting can be segmented by the channel or campaign that originated the customer.

Four-step checklist

Tagging comes first: add UTM parameters to paid social placements, search advertising and other promoted campaigns, including partner and trade-publication activity. Wider tagging improves accuracy because the script relies on those URL values to identify the origin of a visit. Next, the script scans incoming URLs for UTM data and saves what it finds in a cookie. At conversion, the data is handed to Zuora in one of two ways. Hidden form fields can be populated automatically so the values travel with the submission. Alternatively, a small script on the form can read the values back from the cookie, which also covers signups completed through social login buttons where no conventional form is filled in. Finally, Zuora reports can combine standard subscription measures with the channel and campaign fields.

Reports this enables in Zuora

With campaign fields present on customer records, reports can show new trials per month by channel or campaign, trial-to-customer conversion by channel or campaign, new customers per month by channel or campaign, new monthly and annual recurring revenue by channel or campaign, average revenue per user by channel or campaign, lifetime value by channel or campaign, customer churn by channel or campaign, and recurring-revenue churn by channel or campaign. Use these breakdowns to compare quality, not just volume: a channel that adds many trials but converts poorly or churns quickly will look different from a smaller channel whose customers stay and expand.

Why cookie-based capture beats raw UTM capture

Raw UTM capture alone leaves several gaps. It misses visits without tags, so organic arrivals can go unclassified. It also fails when the signup page differs from the landing page, because many tools only read parameters present on the conversion page itself. Cookie storage solves that journey problem: a person who clicks an ad, reads several articles and signs up days later still carries the original campaign attribution. Normalisation is the next gap. Different team members or agencies often tag the same platform differently, for example varying capitalisation or using an abbreviation, which fragments one channel into multiple report rows. Cleaning those variants into a single channel prevents manual merging. Landing page capture adds a further layer, letting teams see which individual content pieces generate leads and which topics convert best, rather than judging content only by page views.

Verification checklist before you trust the reports

Before relying on the data, run a practical check. Confirm every active campaign uses a consistent tagging convention, submit a test signup from a tagged link and verify the values appear in Zuora, repeat the test from an untagged organic visit, and confirm the original campaign still attaches after navigating to a different signup page. Then build one report per key metric, segmented by channel and campaign, and review whether inconsistent source values have been consolidated. If you are evaluating a tool for this workflow, ask the vendor to state its current trial terms and pricing in writing before you commit.

Frequently asked questions

What is the basic flow for getting UTM data into Zuora?

Tag every campaign consistently, install the tracking script so it reads UTM values from landing URLs and stores them in a visitor cookie, then pass those values through hidden form fields or retrieve them from the cookie at signup so they arrive in Zuora with the lead record.

Does the data survive browsing before signup?

Yes. Because the values are kept in a cookie rather than read only from the signup page URL, a visitor can land from a campaign, browse other pages, and still have the original campaign data attached when they later convert.

What happens if a visitor has no UTM parameters?

No. When a visitor arrives without UTM tags, the script can still classify the visit using other signals, for example organic search or organic social, so the signup is not left unclassified.

Why normalise UTM values before reporting?

Inconsistent tagging such as different capitalisation or abbreviations for the same platform can split one channel into several in reports. Normalising those values before they reach Zuora avoids manual stitching later.