Daily Email Volume Cap Across Domains

[Silvio6]

Hi! the client needs a control mechanism in AJO to ensure that total daily email volume sent from 2 different domains does not exceed 2.8 million emails per day, across all active journeys or campaigns.

So the client must avoid surpassing the daily safe-send threshold to protect deliverability and reputation.

Without this control, multiple journeys could exceed the daily limit, risking ISP throttling, spam reputation issues, and IP warming failures.

Thanks!

[SatheeskannaK]

Hi @Silvio6,

The limitation being observed requires a comprehensive solution that transcends platform-level technical fixes. Rather than implementing restrictive configurations at the Adobe Journey Optimizer (AJO) platform level—such as setting a maximum number of messages a specific subdomain can send per day—the core challenge must be addressed through a refined data strategy and communication governance framework.

This strategic approach must encompass several critical components:

1. Who Are We Talking To? (Audience & Segmentation): We need to take a hard look at who we define as our target audience and how we segment them. We have to make sure the subdomains and content we're sending make total sense for the people receiving them. Trying to throttle sends with tech often just means we aren't being disciplined enough about who should get the message in the first place.
2. What’s Important? (Journey & Campaign Priority): Let’s inventory every customer journey and marketing campaign and rank them. We need to prioritize based on how valuable they are (think ROI, where the customer is in their lifecycle) and what kind of message they are (transactional, which is crucial, versus just a promotion). This clear list helps us manage volume and guarantees that important service messages get through before a regular promo email.
3. No More Customer Fatigue (Holistic Frequency Capping): Frequency capping isn't just a system safety net; it’s a key tool for giving customers a better experience. We have to set dynamic limits that apply across all our channels (email, SMS, push, etc.) and all subdomains. The goal is a total message limit per customer, stopping burnout and protecting our brand. This needs to be managed centrally by our data team, not set haphazardly across a bunch of different campaigns.
4. Cutting the Clutter (Integrated Communication Review): A joint team (marketing, data pros, and tech ops) needs to systematically review every single communication going out across all subdomains. We want to stop sending duplicate messages, make sure our brand voice is consistent, and confirm that every single message has a clear, high-value purpose in the customer's journey. Making every send count automatically cuts down on the need for tons of low-impact messages.

Implementing limitations at the subdomain level merely masks the underlying strategic issue: a lack of centralized communication intelligence and prioritization. The real solution lies in leveraging the data strategy to intelligently determine which communication makes sense for a given customer at a given time, thereby self-regulating the volume far more effectively than an arbitrary platform-level cap.

A smart IP warming plan needs to proactively cover these bases:

• Why This Subdomain? (Allocation and Justification): We need a crystal-clear reason for every new subdomain and what kind of content goes through it (e.g., transactional alerts, Product X news, general marketing). Sticking strictly to this rule is how we build and keep a great sending reputation.
• Slow and Steady Wins the Race (Volume Ramp-Up): We must carefully model the increase in volume, making sure to factor in the new IP/subdomain combo alongside our current volumes. The transition has to be smooth to avoid a sudden, weird spike that could make major mailbox providers flag us.
• Keeping a Watchful Eye (Reputation Management): We need a robust, constant monitoring system to track deliverability, engagement (opens, clicks), and, most critically, spam complaints for each subdomain separately. Any drop-off should trigger an immediate operational review and volume adjustment.
• Planning for the Future (Long-Term Roadmap): The IP warming phase has to grow into a full roadmap that prepares us for future growth and portfolio expansion. This forward-thinking approach will prevent us from running into these volume issues again, ensuring we have a scalable sending architecture and high inbox placement rates.

The decision to use multiple subdomains is a strategic one, and the resulting communication volume must be managed strategically through a unified data and audience framework, not defensively through platform-level rate limits. The IP warming phase is the ideal moment to install this high-level strategic governance to ensure a successful and scalable communication infrastructure.