Loading the Ambient Data Framework (ADF) and executing all cartridges for every request can be an expensive operation. I noticed in the docs that is possible to exclude certain paths from using the filter in cd_ambient_conf.xml, but what I am looking for is a more fine grained approach, being able to control which cartridges are executed for certain paths.
Obviously if I am developing my own custom cartridges, I can build this into the cartridge logic itself, but I was wondering if it is possible to easily set up for the standard cartridges.