Hello,
If an eVar is set to a particular value, e.g.
eVar132="some-value"
and then later in the visit, this same evar132 is explicitly set to "some-value", will this be counted as two instances of the eVar, even though their values are the same?
I ask because some of my eVars have what seem to me to be wildly inflated instance counts. These variables are set to a single value per visit and not changed.
Thanks.
mp
Solved! Go to Solution.
Views
Replies
Total Likes
Yes, that is how instances of eVars works....
I am going to assume your eVar is set to a Visit level attribution... so let's look at an example:
Instance of eVarX is not meant to be a counter of unique values, it is a counter of when the eVar is actually set... as opposed to the eVar persisting its value due to its expiry setting.
You may be setting the eVar to a single value, and not changing it... but it sounds like your eVar is likely being set on every page with the same value.
If you see your eVar in the tracking call, that means it's being set, and it will have an Instance associated with it.
For example, something like a campaign tracking... when a url contains ?cid=123 (I track "123" into an eVar)... on that first page, I will see eVarX = "123" in my actual tracking call... but on the following pages, I won't see that value being "sent", but the value is still there, being applied to each hit in the Adobe processing rules.
If I was tracking something like a user id in my eVar, I will likely be setting it on every page, because I don't know what page the user will enter my site from, this will mean that every page counts the Instance of... if I want to get a count of unique user ids, I would create calculated metric using "Approximate Count Distinct" function:
Yes, that is how instances of eVars works....
I am going to assume your eVar is set to a Visit level attribution... so let's look at an example:
Instance of eVarX is not meant to be a counter of unique values, it is a counter of when the eVar is actually set... as opposed to the eVar persisting its value due to its expiry setting.
You may be setting the eVar to a single value, and not changing it... but it sounds like your eVar is likely being set on every page with the same value.
If you see your eVar in the tracking call, that means it's being set, and it will have an Instance associated with it.
For example, something like a campaign tracking... when a url contains ?cid=123 (I track "123" into an eVar)... on that first page, I will see eVarX = "123" in my actual tracking call... but on the following pages, I won't see that value being "sent", but the value is still there, being applied to each hit in the Adobe processing rules.
If I was tracking something like a user id in my eVar, I will likely be setting it on every page, because I don't know what page the user will enter my site from, this will mean that every page counts the Instance of... if I want to get a count of unique user ids, I would create calculated metric using "Approximate Count Distinct" function:
Thank you very much for your answer. Also, thanks for the tip on Approximate Count Distinct. I will look into that.
mp
You're very welcome
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies