simple explanation for different values prop and evar?

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

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.

Hello, everyone,

Thank you so much for your help.

The setting of eVar can be found in the attachment

hi vitalin58577727​

in short: the value of the prop is only stored on the hit where you set the prop. on the other hand the evar keeps the value until the end of the visit (not only on the single hit).

if you send a screenshot of your reporting, we might give you more details about the difference in the numbers

as said I ask the StatusCoder page and save it in two different variables.

ich versuche die Variable StatusCode in zwei verschiedene Variablen zu speichern.

StatusCode -> prop26

StatusCode -> eVar41

es kommen  unterschiedliche Werte raus. es müssen auch unterschiedliche Werte rauskommen, aber wie erklärt sich das?

Danke im Voraus.

Thank you very much for the explanation.

Unfortunately, I do not always fully understand that.

I understand that there are different variables to handle them differently.

Can you give me an example?

Let's take userA to the pageA

UserA -> PageA>PageB>PageC-PageD

Prop26 - ->PageA(200)->PageB(200)->PageC(404)->PageeD(200)

eVar41- ->PageA(200)->PageB()->PageC(404)->PageeD()

occurencies - Prop26(4)

occurencies -eVar41(2)

Is that how it works?

because I don't quite understand that.

German

Vielen Dank für die Erklärung.

Leider verstehe ich das immer nocht nicht ganz.

Ich verstehe das es verschiedene Variablen sind um diese anders zu behandeln sind.

Kannst du mir einen Beispiel geben?

Nehmen wir BenutzerA kommt auf die SeiteA

BenutzerA -> SeiteA>SeiteB>SeiteC-SeiteD

Prop26 -    ->SeiteA(200) ->SeiteB(200) ->SeiteC(404)-> SeiteD(200)

eVar41-     ->SeiteA(200) ->SeiteB()       ->SeiteC(404)-> SeiteD()

occurencies ->Prop26(4)

occurencies ->eVar41(2)

Stimmt das so in etwa?

denn ich verstehe das nicht ganz.

Mir geht um die Unterscheidung wann ich was nutzen soll und kann.

there are a lot of websites describing the difference, eg here: Traffic Props and Conversion eVars

I suggest you have a look at those pages, I think it will solve your questions (and more)

Die Frage wurde nicht beantwortet aber für den Leser wird das so dargestellt.

Klar habe ich die Links zu dem Unterschied von prop und evar gelesen und noch weitere Seiten gefunden die das erklären.

Das habe ich vorher schon alles gemacht.

Gib es keine einfache Antwort auf meine Frage?

Ist die Frage zu kompliziert oder ist die Antwort nicht möglich?

Hi vitalin58577727​

I try to answer your question in short, even if it's not possible to fully answer the question - there are too many special cases.

basically, a prop is a variable set on a single hit and only valid for the single hit. a prop are mainly used for pathing and the "entry"/"exit" values.

(remark: special cases for "list props", "pagename" and some other default variables)

an evar is used for merchandising. that means, a value is set on a single hit and saved for later use. eg. if a user is searching on your page for the word "book" and later buy something, you can break down for the (last) search term.

but: there are a lot of options in the backend which can influence how and how long an evar keeps the values. i skip it here because that would take too much of work (and I'm sure you already read about that)

lets go back to your example and try to figure out how it "might" work:

UserA -> PageA>PageB>PageC-PageD

Prop26 - ->PageA(200)->PageB(200)->PageC(404)->PageeD(200)

eVar41- ->PageA(200)->PageB()->PageC(404)->PageeD()

if you really set the prop26 and eVar26 on each hit, the "occurencies" should be the same.

but as written before, youre settings for the evar indicate that you are using a "merchandising evar" which is a very special case of an evar. just google for this evar type...

the might understand the idea of prop/evar with this example:

page A / prop26: 200 / evar41: 200

page B / prop26: -- / evar41: --

page C / prop26: 404 / evar41: 404

page D / prop26: 200 / evar41: 200

in this case (with an "usual" evar and expiry visit) the result would look like this (occurnecies)

prop26 / 200 -> 2 / 404 -> 1

evar41 / 200 -> 3 / 404 -> 1

the reason for the difference is that the evar "keeps" the value for the hit (occurencies) where no new value is set.

i hope that helps...