I agree with Jen that we do need some more information to be certain. Is your evar5 a page type, the same as your prop5? And is it capturing the page type on each hit or is it capturing only one value per visit (the entry value)?    Props, in addition to their regular version, have entry and exit ve...

I agree with Jen about needing to click into the block in order for the commands to appear. Think of these blocks like pivot tables. If you've clicked outside of the table, then there's no commands available because what you've selected doesn't have any options. Once you click on the cell where you ...

If we're talking about taking this data outside of workspace to accomplish it, I agree with Jen, data feeds are the far better option. You do need to have the right environment for them and there is a bit of initial setup work, but once you have them, there is a lot that you can do with them beyond ...

To be honest, I don't think either one is going to give you what your looking for. Visitor = 1 is just insisting that there is one unique visitor. Visit = 1 is insisting that there is one visit, but it doesn't necessarily have to be their first visit.    There is a dimension called visit number. Thi...

There isn't a set number of days for the alert look back, at least not that Adobe has shared with users. It is possible that over the next week or so it should pick up the fact that the data is an expected value. Unfortunaly it isn't recommended to use date ranges in alerts, otherwise that would be ...

I'm not that familiar with getting data into Qualtrics. Have you clicked on 'other' to see what options that gives you?

If you have regular Adobe Analytics or Customer Journey Analytics, right now, there are three levels of segments that you can create - hit, visit, and visitor. Those are the only options. Meaning that you can't group items together using other dimensions.   If you want to find high engaged accounts ...

I agree with @Jennifer_Dungan. If you copy and pasted then the value should be the same, but there's always the possibility of a bug. Reaching out to support and providing them the information about the classification should allow them to look into it and see what is going on. 

Are either of your reports using a segment/filter?   Are both reports using the same dimension? I'm not sure if that's what you mean by 'identical field value.' If you have different dimensions, if one doesn't fire as often as the other, there could be fewer visits attributed to it in total.

No, you can't do regex with processing rules. With processing rules you can only concatenate values, not parse them out. If you're looking to use regex to pull out individual values, you can do that using classifications. Right now you will need to use the legacy classification rule builder to do so...