eVar not overwriting with new value | Community
Skip to main content
Level 4
November 8, 2019
Solved

eVar not overwriting with new value

  • November 8, 2019
  • 2 replies
  • 3723 views

Hi everyone,

I have a page where a customer can make amendments to their product which changes the price. I have a data element changed rule that fires on change of the price and saves it to an eVar.

When I review the values for the eVar in my report I have many more values than I do customers. It looks like rather than overwriting the value of the eVar with the new value, it's saving every value.

Is this expected behaviour or do I need to do something different either in the configuration of the eVar or my DTM rule firing on the page?

Many thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by PratheepArunRaj

Dear Philip,

Any set value in the eVar will be captured for sure. If you use 'Occurrence' every eVar you set will be displayed at the Reports Interface.

And, yes, eVars by default have Last Touch Attribution for all the Conversion Events. If your visitor selects the Price $500, changed to $600 and then to $700 to trigger the purchase event. $500, $600, and $700 will be captured against the 'Occurrence' metric and only $700 will be captured against the 'Order' metric. So, the Last Touch Attribution is for Conversion Metric / Success Event selected during the time. 

Thank You, Arun.

 

2 replies

Adobe Employee
July 14, 2020

Hi Philip.

 

Any value which will be assigned to an eVar will be saved and shown in the reports as well. This is an expected behavior.

PratheepArunRaj
Community Advisor and Adobe Champion
PratheepArunRajCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
July 14, 2020

Dear Philip,

Any set value in the eVar will be captured for sure. If you use 'Occurrence' every eVar you set will be displayed at the Reports Interface.

And, yes, eVars by default have Last Touch Attribution for all the Conversion Events. If your visitor selects the Price $500, changed to $600 and then to $700 to trigger the purchase event. $500, $600, and $700 will be captured against the 'Occurrence' metric and only $700 will be captured against the 'Order' metric. So, the Last Touch Attribution is for Conversion Metric / Success Event selected during the time. 

Thank You, Arun.

 

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
Level 4
July 20, 2020
Hi Arun! Many thanks for the response. I'm using the visits and unique visitors metrics to break down my reports. Would this display the same behaviour as occurrences?