You now have the option to select which report suites you want to copy processing rules to. Thank you for the idea!

There are now two ways to do this. We've added "else" support and "conditional actions," where any action can have its own condition. Thanks for the idea!

With the release of "Conditional Actions" you now have the ability to set many different variables, or take many different actions in a single processing rule, each with their own condition. This means that the processing rule becomes a category all its own. If you disagree and think there is still need for a separate categorization feature, please comment here.

Excellent idea. This is now available.

Excellent idea. This is now available!

Thank you for pointing this out! We've added the report suite name, with the report suite ID in parentheses. The list is now sorted by Report Suite Name.

Thanks for pointing this out, Eli. This is now implemented, as of last night's maintenance release.

Hi Andrew, when repurposing an eVar, Adobe recommends using the reset function on the Conversion Variables page in the Admin Console (see this documentation). Given this functionality, do you think the following steps would work? Create a rule to delete the value of the eVar.Reset the eVar in the Admin console to prevent any existing values from persisting.Use context data for the new values you want in the eVar and create a procesing rule that executes after the rule mentioned in #1 that popula...

This appears to be an oversight. We're checking to make sure and then make the change.