Entry dimension as evars

Hi ​@VirginieRe2,

There’s a lot to unpack here.

First, tracking both a prop (c#) and an eVar (v#) for dimensions is a really old way of tagging a site (from the old Reports and Analytics days, pre-Workspace, when full correlation wasn’t available). It’s really not the recommended approach any longer.

What is the Expiry on your eVar? This could have a lot to do with how the visits is being reported. Honestly, there should be no reason to have any expiry aside from “Hit” on a “page type” eVar… especially since you are supposedly setting it on each page… but actions on the page will pick up the base value (if you have an expiry outside of hit)… my recommendation, if you need this on your actions, set it on your Page Views and Actions specifically…  

If you are seeing “unspecified” in your eVar, there are clearly pages that are not setting a value, and you are seeing unspecified as a result.. you won’t see this on a prop, it just won’t show anything at all… this is the difference between Props and eVars. Now, depending on your metric, this might be coming from actions (if the eVar is set to Hit expiry and is only set on page views?).

To understand where these are happening, you are going to dig into your data, correlate different dimensions to try and figure out where the unspecifieds are being reported.

Next, I am not sure what you mean by “Entry Page Type (v1) report”… eVars don’t have a “Entry” variant… When you are setting a value everywhere, then I would probably just use the Prop… since it should be Hit level anyway, and you will get access to “Entry”, and also, a “page type” shouldn’t exceed 100 characters… so the perfect candidate for a prop…  but having the eVar showing unexpected values (again, we need to know the expiry to confirm some things), shows that there may be a tracking issue that needs to be addressed.

I agree with what Jen said. I too am confused about what you mean by “entry v1” because evars don’t have an entry or exit variant, that’s just for props. 

Some additional questions that can help us figure out what is going on.

Why are you using visit expiry for your page type evar? Every page should have it’s own page type, and assuming you’re using last touch, it’s going to get overwritten on every new page anyway. A hit expiry would make a lot more sense. 

How are your prop and evar being set? Are they both reading from the same property? Are you reading the value from the prop to set the evar? Depending on the specifics of your implementation, there could be reasons why one is being set and the other isn’t. 

I thought Adobe was setting up Entry dimensions for evars as well, like it does for prop.
So thank you for clarifying that it is not.