Michael, I'll restate to make sure I understand. (By the way, thanks for providing the use case!) You're trying to filter out specific products. For non-list variables, you can use a hit segment for this, but for lists that doesn't work because there are multiple values in a hit. I'm not saying we should do this, but for the sake of understanding, if we implemented a product container in the segment builder, and you filtered out specific products, would that meet the need? You want the rest of t...

Excellent recommendations, Michael. How often do you make changes to processing rules? Perhaps more related to what you wrote, how often do you view processing rules without making changes, and what are you trying to find when you view them?

Thanks for submitting this, Lee. We're discussing ways to remove the prop/eVar mapping requirement, but there are a few technical steps we need to take to get there. Lightening the implementation effort is the key driver for those discussions.

Really good point, @AndyW. I'd like to restate this to make sure I understand it. Do you want to disallow users from sharing workbooks unless they've got permission to do so? You would have one group of users who can share, and another group that can't.

Hi Arif, Request #1 is in progress (we're working on adding funnel visualizations now). If I understand your second request, it's about clarifying whether Lock Selected Items or Lock Selected Positions is active. My understanding is that only one can be active at a time, and it's not very clear which is selected with the current design. Excellent feedback.

We've considered this many times, but have found that a full regex engine could add processing delays. Is it fair to say that the key points of regex are the following? Match a pattern, including wildcards, number and alpha-character matchingReplace some portion of the string with somethingExtract a portion of the stirng for use elsewhere

This is solved with AppMeasurement 1.4.1 and the visitor ID service.

This is solved with AppMeasurement 1.4.1 and the visitor ID service.

This is solved with AppMeasurement 1.4.1 and the Visitor ID service.

Excellent idea. This is now available.