help with evar allocation and report

Assuming evar1 is visit expiry, not a merch evar, and last touch.

Also assuming that these are the ONLY calls in the visit, that these are all page views, that there are no other page views before/after, and no other custom link calls happening.

I believe your table should look like this

As for the why - an evar will be unspecified only if there is no value set or persisted. So it will only set in the second visit.

Green is set in both visits, plus there are pages after it is set with no value set, so that value will persist for the page views. The last touch allocation means that the last value seen is the one that is going to persist. 

Hi ​@VirginieRe2 ,

With your setup (visit expiry, last touch), the report will look like:

Why (in one line):

• Instances count only when the color is explicitly set,
• Page Views follow the last color that was set (and persisted for the visit),
• Visits count once for each color that appears at least once in that visit (including a visit where the color is never set -> unspecified).

Hey ​@VirginieRe2 

The others have already posted the table that you specified, but I would like to add an alternate table that also reflects the “page” as part of the visualization

Even though you are not setting your eVar1 value on your home page or your marketing pages, your eVar is set to a VISIT expiry… so the value will persist until the end of the visit, or a new value is set.

So in the expanded table, you can see that there are page views associated to your eVar1 on Home and your Marketing Pages, even through there is no instance being set.

In most cases, you wouldn’t want your eVar to be set to Visit, as it pertains specifically to the product, and not any other subsequent pages.

However, IF your eVar is a merchandising eVar, that changes the behaviour significantly, as the value would only then be associated to calls where the s.product includes the specific product.

For example, if I were to send this on product 1:

s.products = “catX;product1;;;;eVar1=blue”;

s.events = “prodView”;

The eVar “blue” will not be associated to any pages beyond the product page… and later, if I were to do “Add to Cart” for product1, I could easily just do:

s.products = “catX;product1”;

s.events = “scAdd”;

eVar1 “blue” would still be associated to this call, even though its not explicitly set, because of the Visit level attribution (specifically against “product1” and no other product.

Let’s say I do an order:

s.products = “catX;product1,catY;product2”;

s.events = “purchase”

Product1 would be associated to eVar1 “blue” and Product2 would be associated to eVar1 “red”