Hi community, regarding counter evars, short use case: increment a counter evar by 1 if a user swipes a menu either to the left or right in mobile view. It has been setup with two different direct calls (for swipe direction left or right) and each time the respective evar is incremented by 1, (in custom code s.evarX = "+1"). Now the idea is to use these two evars and breakdown visitors in containers based on how much they swipe. First of, if this evar is dropped on a freeform table the "occurences" column will show how many times that evar was incremented by 1 during the selected timespan right? By doing that we see a reasonable amount of occurences on mobile devices at least. The problem arises when trying to make a segment that for example says that if the value of the evar for a mobile device visit is greater than 10 (the user swiped more than 10 times), no matter what the segment builder cant seem to find any visitors where there´s even a value exists in these evars, so what have we missed?
Not sure if occurrences is sufficient for the use you are mentioning unless you are sure to set the evar to expire on each hit.
As an alternative, to reduce evars and allow cleaner reporting, have you considered just one evar for direction and then an event for when someone has swiped in the app? Then it would look like dragging a single evar onto a table with a breakdown of "Left" vs "Right" and a specifically named metric just for app swipes.
In fact, you could avoid adding any evars by sticking the direction into another evar with information on the page/panel being viewed. That is, if they swiped right from page 3 to page 2, a developer could put into a pagename variable the value of "Page2<delimiter>R", or if someone swiped left from page 4 to page 5 "Page5<delimiter>L". Then using classifications on this variable, you could break it apart at the delimiter for normal reporting. So the left side of the delimiter can be grouped into a classified pagename and the right can be classified into a swipe direction variable.