Description -
We use a specific naming convention for our Journeys and Messages. Based on these, we can quickly determine if this is an offer or if it's an update. We want to be able to cap the number of offers sent to a customer but not the number of updates sent. As such, we need to be able to set the Caps based on our naming, not just if this is an marketing or transactional email.
Why is this feature important to you -
We cannot scale decentralized marketing without these types of guardrails.
Current Behaviour - can only cap based on marketing or transactional emails.
