I'd say use one eVar for storing options like yes or no and one associated event. That way you would be able to see what you are looking for? You can also breakdown your eVar with page dimension or use segments for detailed view.
I'd say use one eVar for storing options like yes or no and one associated event. That way you would be able to see what you are looking for? You can also breakdown your eVar with page dimension or use segments for detailed view.
I agree with @Isha__Gupta that an evar is the best method to use. You can capture the actual values, yes/no. But unless you have another reason for capturing it in a metric too, you should just be able to use the 'evar instances' metric associated with the evar to get the count. As long as it isn't a merchandising evar, the instances will show you the number of times that it fired.
