Expand my Community achievements bar.

SOLVED

eVar dimension value has Zero Instance

Avatar

Level 5

Hi Team,

I am wondering, how an eVar dimension value will have Zero instance & other metrics are getting values against it. Please help me how to resolve this? I am seeing this in Adobe workspace. Its a normal eVar variable not merchandising vartiable.

dinesh_b_kumar__1-1617867343936.png

This is the definition of eVar variable. @HemanginiS , @jeff_bloomer 

dinesh_b_kumar__0-1617950305654.png

Below is the JS code snippet.

 

if(s.events.indexOf('scOpen')>-1){
var random = ""+ Math.random()*10000000000;
var cartId = random.split('.')[0];
s.eVarXX= cartId;
}

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor and Adobe Champion

@dinesh_kumar_r - The output you're displaying is making me question the implementation of that variable in the actual call.  You're saying it's a traditional eVar, but like @HemanginiS, my instincts would tell me it's been implemented as a Merchandising variable.  Both details will help understand the problem, but the link @HemanginiS is a good reference point.

Jeff Bloomer

View solution in original post

3 Replies

Avatar

Employee

Hi @dinesh_kumar_r ,

Is this a Merchandising eVar?

The “instances” metric works differently on Merchandising eVars. If you use “Product Syntax”, you should not see any instances for the eVar at all. If you use “Conversion Variable Syntax”, you should only see instances for cases, where all three (eVar, binding event and s.products) are set at the same time.
You can also refer this document for details: https://experienceleague.adobe.com/docs/analytics/components/dimensions/evar-merchandising.html?lang...

Avatar

Correct answer by
Community Advisor and Adobe Champion

@dinesh_kumar_r - The output you're displaying is making me question the implementation of that variable in the actual call.  You're saying it's a traditional eVar, but like @HemanginiS, my instincts would tell me it's been implemented as a Merchandising variable.  Both details will help understand the problem, but the link @HemanginiS is a good reference point.

Jeff Bloomer