Yes, sorry for the redundancy, but I don't understand the answer, so I'm not certain I'm being clear.
To use a hypothetical example, how do I make sure that a mass email project which targets 300,000 recipients doesn't, in a single minute or two, dump 300,000 emails into circulation all at once? Such a vast quantity of emails deployed in such a small amount of time raises a red flag for many ESPs, who may spam a lot of the emails and maybe even blacklist the sender.
My preference is that, when I launch an email through Engage, only 10,000 or 20,000 etc., emails deploy each hour until the full universe is served. Is this a feature inherent in Engage, or is it something I can easily set, and how?
(I've been using the deploy at user's local time feature to limit the rate of deployment, but this isn't optimal when I'm trying to send a large file within 24 hours or so.)
Apologies again for the redundancy and for any misunderstanding. I appreciate your patience and guidance. Thanks.
... View more