Duplicate data query

[RohitNa1]

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!

[pradnya_balvir]

Hi @RohitNa1,

Can you please check your eVar settings for "Expire After".

In your case it should be 

• Specific conversion events. Any other conversion events that fire after the specific event designated associate with the eVar.

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: At a page view or visit level. Conversion events beyond the page view or visit do not associate with the eVar. Based on a time period, such as day, week, month, or year. Conversion events beyond the specified time period do not associate with the eVar. The expiration period starts when the variable is set. eVars expire based on the time they were set, to the second (minute, hour, day, month, etc): MINUTE=60 seconds HOUR=3600 seconds (60 minutes) DAY=86400 seconds (24 hours) WEEK=604800 seconds (7 days) MONTH=2678400 seconds (31 days) QUARTER=8035200 seconds (93 days - 3 months of 31 days) YEAR=31536000 seconds (365 days) \ If a visit starts at 7:00 AM on Monday and an eVar is set within that visit at 7:15 AM, expiration is as shown below: Day expiration: eVar expires at 7:15 AM on Tuesday. Week expiration: eVar expires on the following Monday at 7:15 AM. Month expiration: eVar expires 31 days from Monday at 7:15 AM. Specific conversion events. Any other conversion events that fire after the specific event designated associate with the eVar. Never. As long as the visitorID cookie is intact, any amount of time can pass between eVar and event.

[Jennifer_Dungan]

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

• Page 1
  • eVar1 is not set
• Page 2 - Form
  • eVar1 is not set
• Form Submit
  • eVar1 is set to "12345"
  • Instance of eVar is triggered
• Page 3
  • eVar 1 is not set, but maintains the value "12345"
  • Instance of eVar is not triggered, since the value is attributed and not explicitly set
• Page 4
  • eVar 1 is not set, but maintains the value "12345"
  • Instance of eVar is not triggered, since the value is attributed and not explicitly set
• Page 2 - Form
  • eVar 1 is not set, but maintains the value "12345"
  • Instance of eVar is not triggered, since the value is attributed and not explicitly set
• Form Submit
  • eVar1 is set to "56788"
  • Instance of eVar is triggered
• Page 5
  • eVar 1 is not set, but maintains the value "56788"
  • Instance of eVar is not triggered, since the value is attributed and not explicitly set
• Click Action 1
  • eVar 1 is not set, but maintains the value "56788"
  • Instance of eVar is not triggered, since the value is attributed and not explicitly set
• etc

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)

[RohitNa1]

The evar is set to year and if we move to hit level will it resolve ?

[Jennifer_Dungan]

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.

[gokul2112]

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:

1. Check for Clear Variables in Launch: Verify if the eVar is cleared in the launch for the rule where it is defined.
2. Search for eVar in Launch: Ensure that the eVar is defined where it is expected. Ideally, it should only be defined during the request form submission.
3. Check for Multiple Triggers: The rule setting the eVar value might be triggered multiple times. Use the DTM Switch on the website to check if this is happening.
4. Ensure Unique Values: Make sure the eVar generates unique values for each request form submission. could be possible that users are entering the same request form details again and again which is causing instances to increase because same details might generate the same unique value for an eVar.