SOLVED
URL Parsing in Tag for Analytics
1 Accepted Solution
Correct answer by
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.
Correct answer by
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.
As @yuhuisg pointed out, you can create Data Elements using Core > Page Info to get lots of things relating to the page:
URL - gets the full URL (https://www.domain.com/something/x)
Hostname - gets the domain of the url (www.domain.com)
Pathname - gets the path (/something/x)
Protocol - gets the protocol (http: or https:)
Referrer - gets the referrer value from the header of the page
Title - gets the doctitle (the SEO title, what shows in the tab, etc) of the page
So in your case, starting with Pathname is likely the option you want... but parsing out values... well that all depends on the structure of the URL, how complex you want to make the parsing, etc...
Trying to extract parts of an email which is encoded into the URL, in particular trying to parse the local part (or username) of the email when this can support many different formats and character will make this ask more difficult....
Your sample used first.last@domain.com and you want to split the username into first and last... but there may not always be a ., it might have a - (first-last) or an _ (first_last) or nothing at all (firstlast or flast).... there may be no consistency on which to properly parse such information...
There is a data element to collect query parameters as well.... now, those will be captured one by one, so if you are using UTMs you probably have the 5 standard parameters to capture...
If you want these to be passed to Adobe's "campaign" dimension, then you will have to concatenate the values from the various Data Elements into the format of your choice....
I personally would use a Custom Code Data Element to bring all the UTM Data Elements in, then check if they have values, then build them together into the format I want/need...
If you just add them directly into the campaign variable like so:
When you don't have any UTMs, you will end up with a series of underscores "____" being passed, which likely isn't what you want.
Related Conversations
