simple explanation for different values prop and evar? | Community
Skip to main content
V
vitalin58577727
New Participant
December 14, 2018
Solved

simple explanation for different values prop and evar?

  • December 14, 2018
  • 13 replies
  • 16370 views

Hello, everyone,

maybe someone can help me?

In order to understand what prop and evar are, I have read some here.

https://webanalyseaufdeutsch.de/2012/01/17/traffic-variables-variablen-in-sitecatalyst-i/

https://webanalyseaufdeutsch.de/2012/01/17/traffic-variables-variablen-in-sitecatalyst-i/

but to better understand and touch this I have a variable which is stored in two different variables.

There is a variable on the page for the status code of the page:

So I have stored the respective status 1x in a prop and 1x in an evar.

And absolutely different values come out.

Can anyone explain this to me?

Hallo alle zusammen,

vielleicht kann mir jemand helfen?

Um zu verstehen was prop und evar sind, habe ich hier einiges gelesen.

https://webanalyseaufdeutsch.de/2012/01/17/traffic-variables-variablen-in-sitecatalyst-i/

https://webanalyseaufdeutsch.de/2012/01/17/traffic-variables-variablen-in-sitecatalyst-i/

Um das jedoch noch besser zu verstehen und das anfassen zu können habe ich eine Variable welche in zwei unterschiedliche Variablen gespeichert.

Es gib auf der Seite eine Variable für den StatusCode der Seite:

Also habe ich den jeweiligen Status 1x in eine prop und 1x in eine evar gespeichert.

Und es kommen absolut unterschiedliche Werte raus.

Kann mir das jemand erklären?

Best answer by Urs_Boller

Hi vitalin58577727​

you have several problems in your setup:

1) prop vs. evar:

a prop only saves the value on a single hit when you set the value! that means your occurencies should be the amount of times you send the prop to the database (reportsuite).

an eVar keeps the value as long as you defined. to see an equal metric (counter when eVar is set) take the corresponding "Instance" metric. adding "eVar41 Instances" will show you the amount of times the eVar appears in the server call. But since eVar keep the value (in the database/reporting) you can see the the counter for those hits as well using "occurencies". that means this metric shows you athe amount of times where the eVar is set OR the database still knows the vaule.

I recommend the following article about the difference of "instances vs. occurencies":

- Compare page views, instances, and occurrences

- https://webanalyseaufdeutsch.de/2017/10/03/die-occurences-metrik/

2) eVar settings

Having a closer look at your aVar I saw that you set it as "merchandising eVar". this is kind of a soecial eVar and might not be what you want.

13 replies

Show previous replies
V
vitalin58577727Author
New Participant
December 17, 2018

Hello, everyone,

Thank you so much for your help.

The setting of eVar can be found in the attachment

Urs_Boller
Urs_Boller
New Participant
December 14, 2018

hi @vitalin58777

what metric are you loking at? pageViews, visits? and do you set the value in each hit, page view or just once per visit?

I assume that the difference is based on how the eVars keep their value. eVars can (based on report suite settings) keep the value forever, while props loose the value after the hit. therefore a difference in data is expected based on settings for eVar, how you collect data and how you report (which metric).

maybe you can give more information on collect/eVar settings and a report screenshot and we might give you an explanation.

Alexis_Cazes_
Alexis_Cazes_
New Participant
December 14, 2018

If for the same hit(server call) a different value is set then you should look at your implementation to check same value is set at code level and same value is present in server call.

If it is the same and still different value then check there is no VISTA ruless or processing rules that affect either of these variables.

Make sure eVar is not a merchandising eVar and has last toucj allocation

Terms & ConditionsAccessibility statement

Loading footer...