I need some advice regarding an issue with eVars.
Whenever a request form is submitted, we generate a unique alphanumeric eVar. When a second form is submitted, a new unique eVar is created.
We expected that each eVar would have only one instance, but we are seeing multiple instances for each unique eVar.
The problem is that for each unique eVar, we're observing more than one instance, which shouldn't be happening. Does anyone have any ideas on how to debug this?
Thanks!
Views
Replies
Total Likes
Hi @RohitNa1,
Can you please check your eVar settings for "Expire After".
In your case it should be
Expire After | Specifies a time period, or event, after which the eVar value expires (no longer receives credit for success events). If a success event occurs after eVar expiration, the None value receives credit for the event (no eVar was active). If you select an event as an expiration value, the variable expires only if the event occurs. If the event does not occur, the variable never expires. The available expiration options can be classified under four main categories:
|
I agree this sounds like the eVar is set to the wrong expiry.
eVars default to Visit level expiry, so what you are likely seeing is this:
Visit
So your form submits are in fact setting unique values, but those values are carried forward to all subsequent hits (page views and other actions).
It sounds like you just need the expiry to be set to Hit (set and only available on the form submit)
Views
Replies
Total Likes
The evar is set to year and if we move to hit level will it resolve ?
Views
Replies
Total Likes
Well, right now, every time a for is submitted, that values it maintained for all hits following that form submission for that user, for an entire year (or until they submit again).
I'm guessing that you are not trying to do some fancy attribution following that form submission around for a year?
I would first double check that no one is actually relying on that attribution (I suspect no, but better to be safe), and when you do switch it to "Hit" also Reset the values:
Don't worry, this will go back to "Don't Recent" after the save, this just allows you to force all the values that are already set for a year to be cleared.
For now however, even without changing your settings, if you pair your eVar with the "Instance" for that eVar, that should limit it down to just the Hit (i.e. where the unique value was actually set).
So if the eVar is called "Form Submission ID", then the corresponding metric will be called "Form Submission ID Instance", you can even create a segment of this combination to use with other metrics... so if you needed to see UVs for instance, you can create a segment of:
HIT [
Form Submission ID exists
AND
Form Submission ID Instance exists
]
This will look for an ID to be set, but only on the hits where the instance was set.
Hi @RohitNa1 ,
Instances are created whenever an eVar value is set in the image request. If you notice an increase in eVar instances, it indicates that the eVar value is being set somewhere. To debug this issue, follow these steps:
Views
Replies
Total Likes