Solved

URL Parsing in Tag for Analytics

Forum|Forum|2 years ago
June 16, 2023
2 replies
3172 views

Good afternoon.

I would like to know how to parse the URL in the TAG and send it in separate variables to Analytics.

Thanks.

Analytics

Best answer by Jennifer_Dungan

I generally use Custom Code Data Elements for that... how good are you with JavaScript, and how complex are your parsing rules?

If you just want a simple part 1, part 2, part 3, etc IF it exists, then you could so something like:

var pathName = _satellite.getVar('urlpath');
pathName = pathName.replace(/\/*$/, "").replace(/^\/*/, "");
var pathNameArray = pathName.split('/');
var urlPart = "";

if (pathNameArray[0]){
    urlPart = pathNameArray[0];
}

return urlPart;

The first part just gets the Path Name from another Data Element for Path Name (or you could pull that using JS, but if you already have it, might as well use it)

The second line just removes the leading and trailing / from your path (when you split the path, you won't end up with empty objects)

Next, we are going to split the URL into an array on "/" - basically making each part of the URL it's own object.

All of the above code will be in each Data Element... the next part has the variations.

First, we just initiate a urlPart variable, so that when we run the return statement, the variable is defined, and if you happen to be on the home page, with no path parts, it will just be an empty value, or when you are pulling part 3, and you only have 2 parts, again, it returns an empty string.

Now, for each Data Element, we want to check IF there is a URL part at the position, arrays are zero-indexed... so "0" is actually part 1, "1" is actually part 2, etc

If there is a value in the part, set the urlPart variable to the value.

Jennifer_Dungan

Accepted solution

Community Advisor and Adobe Champion

I generally use Custom Code Data Elements for that... how good are you with JavaScript, and how complex are your parsing rules?

If you just want a simple part 1, part 2, part 3, etc IF it exists, then you could so something like:

var pathName = _satellite.getVar('urlpath');
pathName = pathName.replace(/\/*$/, "").replace(/^\/*/, "");
var pathNameArray = pathName.split('/');
var urlPart = "";

if (pathNameArray[0]){
    urlPart = pathNameArray[0];
}

return urlPart;

The first part just gets the Path Name from another Data Element for Path Name (or you could pull that using JS, but if you already have it, might as well use it)

The second line just removes the leading and trailing / from your path (when you split the path, you won't end up with empty objects)

Next, we are going to split the URL into an array on "/" - basically making each part of the URL it's own object.

All of the above code will be in each Data Element... the next part has the variations.

First, we just initiate a urlPart variable, so that when we run the return statement, the variable is defined, and if you happen to be on the home page, with no path parts, it will just be an empty value, or when you are pulling part 3, and you only have 2 parts, again, it returns an empty string.

Now, for each Data Element, we want to check IF there is a URL part at the position, arrays are zero-indexed... so "0" is actually part 1, "1" is actually part 2, etc

If there is a value in the part, set the urlPart variable to the value.

yuhuisg

Community Advisor

Use the Core > Page Info data element. It can parse out any part of the URL, even specific query parameters. No coding required!

Jennifer_Dungan

Community Advisor and Adobe Champion

Core > Page Info (Pathname) gets the path as one single element... it doesn't parse it into separate parts.. unless I am misunderstanding the question....

It sounded to me like they want "part 1" of the path going to eVarX, and "part 2" of the path going to eVarY, and so on.....since they said:

and send it in separate variables to Analytics

but maybe they just mean into parts like "domain" and "path"... in which case, yes, the Core > Page Info is sufficient.

yuhuisg

Community Advisor

I interpreted the original question to be parse the parts of a URL, i.e. hostname, pathname, query, fragment.

@afonsoamorim please clarify what are the parts that you want to parse. If it is the pathname that you want to parse, i.e. split by "/", consider tracking the entire pathname to your eVar, then use Classifications Rule Builder to split out the parts.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded