How to pass UTM parameters between pages?

Capturing and passing UTM parameters to another page might seem like a simple task, but in reality, it often involves dealing with bugs, issues, and poorly written JavaScript code that you can easily find on the internet.

Why you need to do this?

Capturing UTM parameters and passing them to another page is a common practice. Typically, we capture and store these parameters to associate them with leads or send them to other services, such as internal analytics, CRM, or email services, which trigger specific workflows.

With utmup.com, you can do it more quickly and easily than ever.

🔧 Step 1: Create an Account

Go to utmup.com, sign up for a free account, and add your website domain in the dashboard.

🧩 Step 2: Integrate the Tracker

Follow the integration guide to install the UTMUP tracking script on your website.

✅ Step 3: Done!

Once the tracker is integrated, UTM parameters will be automatically captured and made available through the utmup JavaScript object.

---

How It Works?

When customer visits your website, for example:

yourwebsite.com/?utm_source=fbads&utm_content=NewYear1

The UTMUP tracker saves all UTM parameters in the customer’s browser. After that, you can retrieve all parameters, just call function:

window.utmup.values(); 

// Example output:
// { 
//   "ga_client_id": "123456.78910", 
//   "first_source": "fbads", 
//   "first_content": "NewYear1",
//   ...
//   "last_source": "fbads", 
//   "last_content": "NewYear1",
//   ...
// }

When this customer visits your website with different UTM parameters:

yourwebsite.com/?utm_source=google&utm_content=MarryChristmas

The UTMUP tracker does not change first_source, first_content, and other first_* values — it only updates the last_ UTM parameters:

window.utmup.values(); 

// Example output:
// { 
//   "ga_client_id": "123456.78910", 
//   "first_source": "fbads", 
//   "first_content": "NewYear1",
//   ...
//   "last_source": "google", 
//   "last_content": "MarryChristmas", // <<< updated
//   ...
// }

All tracking parameters you can find in the docs.