props/evars once set up for a report suite can be used for whatever you want. but i would strongly recommend not to mix it up, unless you run out of props/evars. i mean, try to use the same prop/evar for the same intent and name it accordingly.
i would recommend to use the same props/evars over all different report suites. this way, you can use segments, calculated metrics, workspace projects over different report suites without any problems.
there was a similar question with a good answer from adam:
Yes, you would see old data if you repurposed an eVar. However, you can force an eVar to expire all existing values in the admin console so if you do repurpose an eVar, you won't get weird persisting values.
I did see a report for eVar12 under custom conversion ->custom conversion11-20 folder. But the thing is, it is counted by a metric, it can be visit or visits those metrics. I guess the issue is I defined this eVar as string, it was considered as dimension. So I can not count it, even count by category. In this case, I want to track 2 info, #of time load contact us page and in which division. how should I implement the eVar12? Should I use event? Should I define eVar as a counter instead of a text?
Actually I need to create something to track the load of "contact us" page and also need to track the source of the contact us page ( from different division ). I created a page load rule for load of the "contact us" page, and used an eVar12 as string to grab the division value when the rule fired. I tested the code, eVar12 was set successfully. Then I don't know how to create report for my eVar12. To show how many times this page was loaded and categorized with Division value ( the value in eVar12 ). Anyone can give me some guidance?