I am thinking about using in our Adobe Campaign a kind of 'Email Pressure' limitation, in the sense of setting a total maximun number of emails that can be received by an individual contact daily and/or weekly. When that limit is reached, any subsequent delivery would need to be cancelled to that recipient.
The logic to follow seems quite simple, as it looks to me that counting the records in the broadLog on a given period and take a decision based on that looks like a good process, but at the same time I don't think this is feasible for each and every contact when the email is launched as would affect the performance too badly. So I thought about using a simpler approach with flags at recipient schema level, and use Typology rules to look at those flags and take the decision before the email is sent. In this case then the challenge would be how to update those flags as close to real time as possible so they would work with recurring campaigns that run close in time.
So, the question is, do you think a regular workflow (every x minutes) would do the job without overloading the system? Any other method to update those flags upon a delivery is made that I don't know of and you think would work?
I don't understand well why the "Constant" value on the Threshold type in the Pressure tab of your typology rule can't manage what you intend to do. Otherwise, do you have studied the factory possibilities in the Pressure rule definition:
Honestly, it's the first time I see that functionality you have mentioned in Adobe Campaign, that's why I was thinking about developing it. Do you know where can I get more info or documentation about it?