This record is generated by AI from the cited source. How AI is used
Caps how many times a user can receive a specific periodic or event-triggered campaign within a defined sliding time window.
- Platform
- MoEngage
- Capability
- Arbitration, frequency & send-time rules · Decisioning
- Vendor's name
- Limit Messages for Periodic and Triggered Campaigns
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- GAAug 2026First recorded 27 Sep 2026 · recorded from the source history · vendor release notes · moengage.com ↗ · archived copy, 26 Oct 2026 ↗
Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work
Arbitration, frequency & send-time rules on other platforms latest first
- BrazeMessage PrioritizationGA15 Oct 2026
- HightouchAI Decisioning exact send-time selectionGAOct 2026
- KlaviyoQuiet hours for campaign sendsGA10 Sep 2026
- Adobe AJOPlacement-level frequency capping in DecisioningGA24 Aug 2026
- BrazeWorkspace quiet hoursPreview20 Aug 2026
- Adobe AJOSend using waves for orchestrated campaignsGA18 Aug 2026
- Adobe AJOQuiet Hours for orchestrated campaignsGA18 Aug 2026
- HubSpotPer-brand email frequency capsGAAug 2026
- KlaviyoMinute-level gradual send schedulingGA16 Jul 2026
- IterableDefault Quiet Hours for SMSGA9 Jun 2026
All Arbitration, frequency & send-time rules changes →
More from MoEngage in Arbitration, frequency & send-time rules
- Frequency capping for inbound channelsGAFeb 2026