URL Dimension | Community
Skip to main content
S
scottt6073095
Level 4
September 10, 2018
Solved

URL Dimension

  • September 10, 2018
  • 1 reply
  • 1913 views

Does URL get captured as an Out Of The Box dimension when I populate the URL field in DTM Global Variables? If yes, do you know what the OOTB dimension name is as I can't find anything.

Also, I was reading this page stumbled upon and realized I could use the OOTB server dimension for my current "domain" dimension I created: server  . However, Does the OOTB dimensions work as an evar, prop or both? What are the downsides versus using custom evars / prop dimensions?

thanks in advance,

Scott

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gigazelle

URL is kind of a weird one. In Adobe Analytics, it's only available in Data Warehouse. Outside of that, it's not available. Because of this, almost every organization uses an eVar that's dedicated to page URL.

When I implement Analytics, I'll almost always use eVar1 as page URL. My typical implementation for it is to set eVar1 in the global variables section to:

%window.location.hostname%%window.location.pathname%

That removes duplicates to different protocols as well as query strings, resulting in a lot less cardinality for the variable. You could also use a second eVar that includes protocol and query strings if they're valuable in your organization.

1 reply

Gigazelle
Adobe Employee
GigazelleAdobe EmployeeAccepted solution
Adobe Employee
September 13, 2018

URL is kind of a weird one. In Adobe Analytics, it's only available in Data Warehouse. Outside of that, it's not available. Because of this, almost every organization uses an eVar that's dedicated to page URL.

When I implement Analytics, I'll almost always use eVar1 as page URL. My typical implementation for it is to set eVar1 in the global variables section to:

%window.location.hostname%%window.location.pathname%

That removes duplicates to different protocols as well as query strings, resulting in a lot less cardinality for the variable. You could also use a second eVar that includes protocol and query strings if they're valuable in your organization.

Terms & ConditionsAccessibility statement

Loading footer...