Skip to main content

​
Messaging Operations

Expected delays and rate limits for sending messages

​
Processing Times

  • Messages scheduled through the system require up to 30 minutes for processing and dispatch. Any message has be be scheduled at least 30min into the future
  • No internal rate limits apply to message volumes from Aampe’s infrastructure
  • External delivery tool limits must be observed
High Volume HandlingFor high-volume messaging scenarios, we support message batching configuration to optimize delivery tool integration.

​
Data Processing Windows

Expected delays with with new data beeing available in Aampe Composer for messages and Audience segmentation. User Attribute UpdatesNew user attributes require up to 24 hours from initial ingestion to become available in the Aampe composer for audience segmentation purposes. Example: New custom fields like loyalty_tier or last_purchase_date
Actual processing times may be shorter depending on system loadAll timeframes represent maximum processing windowsIf your use case requires faster processing times feel free to contact us
⌘I