im not sure what to answer: on one hand i love the new layout since it is easier for non-technical users to read the reportson the other hand it is a mess for me: if i look at a report i too often have problems to see what dimension i took (especially when i have an evar/prop with the same name)i al...

ok, this can get a bit tricky - never tried it out (but it is on my todo list so very interested if it works...)create the following 4 segments:1) his segment where evarX-Instance equals 12) hit segment where evarX-Instance equals 1 and hit-depth equals 13) visit segment (before sequence) where „eva...

annaurban​ do you mean you only want the first instances of the evar ever? means if there is a second evar instance in the same visit, it should not count/include the second hit?

you need a „hit“ segment with condition „[evar] instances“ is „greater than or equal„ to „1“where [evar] ist the name of the evar you are looking forthis way you get only the hit‘s where the evar is set

if you want „visitors“ who saw a page at least once in ANY visit, try this1) visitors with page view:“visitor“ (not visit) with (“hit container“: „page“ contains „SpecialPage“)2) visitors who never saw that page:“visitor“ with „exclude“ segment 1)hope this helps

just a guess: your data-json from "populating the data" looks strange at the end (some brackets and chars too much). is this just a copy&paste problem or have you checked the "populating data request" with the API Explorer?

i use to make a copy of the oringinal dashboard with name and tag "shared". i then share the copied dashboard which gives me the opportunity to always "redo" the user savings.only bad thing: if someone has a schedule over the copy the schedule gets lost ... not perfect but a nice work around ...

and if you really want the total of server calls, better go to "admin" -> "billing"  

be careful! as far as i know this works only for props not evars! if you want to know the server calls where an evar is set, you should take "[evarxy] instances"this is due to the reason that most evars persist longer than 1 hit and therefore you have an "occurrency" on the next hit even the evar is...

yes, a page view is a server call.but a server call is not necessary a page view have a look here: Server Call