Creating a segment that uses "starts with" rather than "equals" and having approximately 100 rules to set up this way on different dimensions, I'm really wishing I could change all of the "equals" at once!

In your implementation, do you:Use generic success events and create calculated metrics for specific conversions using an eVar? (e.g. 1 eVar tied to 1 form fill completion event and utilize calculated metrics to get total events by form version)Create a unique success event per set variable? (e.g. 1 eVar tied to multiple form completion events, one for each version of the form)A mix of both?What are the advantages and disadvantages you find in the method you use? I know for example we have to cr...

In each classification table, there are 2 groups of unclassified data. One group is activity with no variable set and the other is activity on a set variable that hasn't been classified. As an example, direct traffic without s.Campaign variable and campaign traffic with an s.Campaign variable that has not been defined by processing rules or a SAINT upload yet. In fully processed data, these can be distinguished by adding classifications to the null (or ~none~) variable. For example, set the clas...

I have classified the null values for the s.campaign variable with "Direct Traffic" in one of my classification fields. This works flawlessly in Analysis Workspace as well as data feeds, but it does not seem to work with Data Warehouse exports. All unclassified and direct traffic gets grouped together in exports if I try to use the classification to breakdown some other variable. My "Direct Traffic" classification doesn't show up.Is this expected, does Data Warehouse somehow read this classifica...

I was very excited about this feature, but I think it does not provide any value as is. There's never a scenario where I only need to breakdown the top 5 items, so I am stuck in the old method of manually breaking down each second level line item by the 3rd variable for anything beyond 5 items. It would be great if this could be increased to up to 25 at least. Ideally the breakdowns would be applied to the full table (including new values after it is built!) This may be a separate issue, but onc...