Cross production sandbox email send exclusion

[MauriP]

Hi,

We have a case where we need to make sure that a customer does not receive more than 1 email/sms per day sent via journey/campaign in AJO.

Challenge is that the customer can be customer for two different BUs in the company and the BUs have separate production sandboxes (within same Org). What would be the best way to do cross prod sandbox message exclusion?

Cheers,

M

[Mohan_Dugganab]

• Frequency capping, suppression lists, and journeys are sandbox-scoped
• Profiles and experience events are NOT shared across production sandboxes

As such, there has to be a middleware built in which will centrally track message sends across all sandboxes and enforce cross-BU frequency decisions before delivery.

[Pulkit_Jain_]

@MauriP AJO sandboxes are fully isolated, i.e, Journeys and campaigns cannot see data from any other sandbox. This means message Feedback, tracking Events, profile attributes, etc., do not sync between sandboxes automatically.

Solution: 

Since two BUs share the same IMS org, you can use shared profile-level “last message sent timestamp” fields stored in a profile-enabled dataset.

• Sandbox A journey writes to the profile after each send.
• Sandbox B journey checks the same profile fields.
• Suppress if the message was already sent today.

This should work instantly, across all sandboxes, and requires no cross-sandbox system dataset access.

[Mayank_Gandhi]

@MauriP 

You cannot natively share AJO frequency caps across two separate production sandboxes today. Business Rules (frequency capping) are evaluated per sandbox, and engineering explicitly flags cross‑sandbox frequency capping as “not available / not planned” for AJO right now.
So you have two realistic patterns:

1. Architect to a single prod sandbox per BU (best, if you can consolidate) and use AJO Business Rules (global + local rule sets) to cap 1 email/SMS per day per profile across all journeys/campaigns.
2. If you must stay with two prod sandboxes, implement a shared external counter service + custom actions / RT‑CDP logic to maintain a cross‑sandbox “contacts today” counter and pre‑exclude profiles in each sandbox.