Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
UTMs into Adobe Analytics
There are probably other ways to do it, but I've done this using processing rules.
I actually have three different UTM values to capture. So, I set up three evars with the settings I need and then used the processing rules to fill in the appropriate values. I overwrite the value of "evar" with QSP, and then I put the utm type in that small box on the right.
The evar settings you just set up like normal evars with whatever attribution and expiry you need.
Agree with @MandyGeorge
what I typically do is merge the UTM params together into the Analytics campaign value, so you can use them as Tracking Code dimension.
Key there is to use a unique separator that is not used in any of the UTM param values, such as ":_:" or similar.
Also, when filling the s.campaign dimension, make sure to always have the same number of values set, even if a campaign does not use UTM param xy.
This could be your data element for the aggregated s.campaign value.
[UPDATE] added @Jennifer_Dungan 's input in Option B when no fixed positions are needed anymore and a prefix is used instead
@Jennifer_Dungan Option A is great if you want to export data to Excel
// Option A: fixed positions
const searchParams = new URLSearchParams(window.location.search);
const utmParams = ["utm_source", "utm_medium", "utm_campaign", "utm_content", "utm_term"];
const utmValues = utmParams.map(param => searchParams.get(param) || "");
// if there is at least one value set, return the concatenated string of all parameters
if (utmValues.some(param => param)) {
// source:_:medium:_:campaign:_:content:_:term
const delimiter = ":_:";
console.log(utmValues.join(delimiter));
}
// ------------------------------------------------------------
// Option B: prefixing each parameter with its name and ditch not set params
const searchParams = new URLSearchParams(window.location.search);
const utmParams = {
us: searchParams.get("utm_source"),
um: searchParams.get("utm_medium"),
ucmp: searchParams.get("utm_campaign"),
ucnt: searchParams.get("utm_content"),
ut: searchParams.get("utm_term")
};
// generate pipe separated string of all parameters with name and values, excluding empty values
console.log(Object.entries(utmParams)
.filter(([key, value]) => value)
.map(([key, value]) => `${key}:${value}`)
.join("|")
);
This way, the structure with the delimiter dictates which values were set when you are looking at the Tracking Code dimension.
At the same time, I would strongly recommend capturing the individual UTM params in separate eVars with the same expiration as your Tracking Code dimension.
Cheers from Switzerland!
Related Conversations
