Expand my Community achievements bar.

SOLVED

how to create segment for values stores in eVar

Avatar

Level 4

I have another question concerning the tracking of the dimension “Transaction Value” in Adobe Analytics. The dimension items. like “3000” or “10000”, depending on what credit volume a customer requests in his product application for the private credit. These values are captured as discrete values, which means I currently can’t (or just don’t know how to) build segments like this:

 

Hits

Transaction Value is less than or equal to 3000

reddy_y11_0-1649908728026.png

 

The operand returns the distinct count of the transaction value instances but not the actual count of values that match this criteria. Is this because the value is captured in the dimension(1. screenshot of eVar) and not in an event? It seems like we can’t calculate further values with it because of eVar type is "text string". If we change it to "counter" and then create segment , then we can see the correct results ? or need to pass the values in a event?

please suggest me 

reddy_y11_0-1649905556431.png

1. screenshot of eVar

segment created as follows

reddy_y11_1-1649905723778.png

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Your desired segment condition "Transaction Value is less than or equal to 3000" doesn't work because eVar values are always stored as strings. So while you're reading a number 3000, AA only recognises it as the string "3000" and so it cannot perform any math on it.

eVar counters won't work because, as the name suggests, they are used to count, kinda like a hit counter. So you can't specify your own value to the eVar.

So yes, your best option is to use numeric events to track Transaction Values.

One other option is to classify your eVar's values into buckets. Fortunately, Classification Rule Builder supports regular expressions, so that should make the buckets fairly easy to specify.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Your desired segment condition "Transaction Value is less than or equal to 3000" doesn't work because eVar values are always stored as strings. So while you're reading a number 3000, AA only recognises it as the string "3000" and so it cannot perform any math on it.

eVar counters won't work because, as the name suggests, they are used to count, kinda like a hit counter. So you can't specify your own value to the eVar.

So yes, your best option is to use numeric events to track Transaction Values.

One other option is to classify your eVar's values into buckets. Fortunately, Classification Rule Builder supports regular expressions, so that should make the buckets fairly easy to specify.