Track UTM Parameters in Woopra: Four Steps to Channel and Campaign Reporting
Woopra can show how people use your product, but it does not capture UTM parameters and other marketing attribution data out of the box. It uses its own URL tagging approach, such as woo_campaign, while most organisations already tag campaigns with UTM parameters for tools including Google Analytics. The workflow below bridges that gap so acquisition results in Woopra can be broken down by channel and campaign.
Why Woopra needs help with UTM data
Woopra is a customer journey and product analytics tool that makes product-use reporting straightforward. Its limitation for marketing analysis is attribution: UTM parameters and related marketing data are not captured automatically. If your advertising already relies on UTM tags, you need a way to carry those tags from the landing page through to signup and into Woopra.
The capture tool described in the source works as site code. It examines technical information about each arriving visitor, determines where they came from, groups them into channels such as Paid Social or Organic Search, and stores that categorised information in a browser cookie. When the visitor later completes a form, the UTM parameters and other attribution data can be passed into backend tools including Woopra. Once inside Woopra, the data supports questions about customers from Facebook Ads, retention by Facebook Ads versus Google Ads, revenue from Facebook campaigns, and overall advertising return on investment.
Four steps to analyse UTM parameters in Woopra
Step 1: Tag every campaign. Add UTM parameters to each advertisement and campaign so the capture tool can identify the source of traffic. Cover social platforms such as Facebook, Twitter and LinkedIn, search engines such as Google and Bing, and any bespoke campaigns.
Step 2: Install the capture code. After signup, add the small code snippet supplied for your site. It is installed in the same general way as analytics or other marketing code: through a header or settings option in a content management system such as Wix or WordPress, or directly through a tag manager such as Google Tag Manager. Help documentation is available for the specific setup.
Step 3: Send the data into Woopra. Once installed, the tool watches how visitors arrive, categorises each visitor into channels such as Paid Search or Organic Search, and stores the result in a cookie. There are two ways to move that stored data into Woopra:
- Hidden form fields: add hidden fields to forms so the tool can write UTM parameters and other attribution data into them. On submission, that data travels to Woopra alongside the visitor's name, email and other submitted information.
- Cookie recapture: add a line of JavaScript to retrieve UTM parameters and other attribution data from the cookie and send it into Woopra. This suits signups that bypass a form, such as Sign up with Google or Sign up with Facebook buttons.
Step 4: Build Woopra reports. With attribution data present, create reports that show acquisition measures including signups, activations and customers by marketing channel and campaign. Practical checks include signups from Facebook Ads, the Google Ads campaign driving the most signups, activated users from LinkedIn Ads, retention for Facebook Ads versus Google Ads, and customers attributed to blogging or search engine optimisation efforts.
What to look for beyond raw UTM capture
Capturing raw UTM parameters is only part of the task. The source identifies four additional benefits worth checking before you choose a method.
Captures all traffic: channel information is collected even when a visitor arrived without UTM parameters, for example through Organic Search, Organic Social, Referral or Direct. That means reports can account for all signups and customers, not only those from tagged campaigns.
Remembers the data: many UTM methods read parameters from the URL on the page where a form is completed. That fails when a visitor lands on a campaign page, reads and explores, then clicks Create an Account and completes the form on a different page. Cookie storage preserves the original parameters across that navigation, so they are still passed into Woopra.
Provides cleaner data: UTM values often vary by person or agency. Facebook, facebook and fb may be intended as the same source but would look like three sources if raw values were reported. Normalising variants into the correct channel, such as Paid Social, avoids misleading splits.
Captures landing page data: alongside UTM and channel data, the tool also collects the landing page and its category, such as a blog path and the /blog category. That lets you compare performance by site section and drill into individual content pieces, for example whether a particular blog post drives signups and customers.
Pre-launch checklist
Use this checklist before building your first Woopra report:
- Confirm every paid and bespoke campaign carries consistent UTM parameters.
- Confirm the capture code is present on the site through your content management system header settings or tag manager.
- Decide between hidden form fields and cookie recapture based on whether signup requires a form or can happen through a social sign-in button.
- Test a journey that starts on a tagged landing page and finishes on a different signup page, then verify the original attribution data reaches Woopra.
- Check that inconsistent source spellings are normalised into one channel rather than reported as separate sources.
- Verify that untagged traffic such as Organic Search, Organic Social, Referral and Direct is also categorised.
- Confirm landing page and landing page category are captured if you want content-level reporting.
For the trial offer, the owner-confirmed term is {{OWNER_TRIAL_DURATION}}. The attribution tool to be recommended is {{OWNER_ATTRIBUTION_TOOL}}.
Frequently asked questions
Does Woopra capture UTM parameters automatically?
No. The source describes Woopra as using its own URL tagging system, such as woo_campaign, rather than capturing UTM parameters out of the box. That is why an additional capture step is needed if your campaigns already use UTM tags for other tools such as Google Analytics.
Which method should I use to send attribution data into Woopra?
Use hidden fields when signups go through a form, because the attribution data can then travel with the submitted name, email and other form information. Use cookie recapture with a line of JavaScript when people can sign up without completing a form, for example with Sign up with Google or Sign up with Facebook buttons.
What happens if a visitor signs up on a different page from the one they landed on?
Storing the data in a browser cookie means it can survive navigation to a different page. A visitor who lands on a campaign page and later clicks Create an Account to reach a separate signup page does not lose the original UTM data, unlike methods that read parameters only from the URL on the form page.
Why normalise UTM values instead of sending raw values?
Raw values can create false splits. For example, Facebook, facebook and fb may appear as three sources in a report. Normalising those variants into one channel, such as Paid Social, prevents the same source from being counted separately.