Working with Blueshift sandbox accounts

The sandbox environment in Blueshift is designed for safe testing and validation of integrations. No real messages are sent, and messaging quotas are not consumed.

Why use a sandbox?

Use a sandbox account to:

• Preview campaigns and safely personalize content
• Validate segmentation and trigger logic
• Explore API workflows without impacting production data
• Test CloudApp integrations and payloads

Sandbox limitations

Message delivery

• Campaign execution is disabled in sandbox accounts (account_mode = sandbox).
• No messages are sent — including Email, SMS, Push, or CloudApp.
• CloudApp endpoints can receive test payloads if configured, but messages are not dispatched downstream.

Quota usage

Messages in sandbox accounts do not count toward your annual messaging quota.

User uploads and segmentation

• You can upload test users and build segments exactly as you would in a production account.
• Segments and triggers can be used for previewing journeys, but will not result in message sends.

Load testing

• The sandbox is not intended for high-volume load testing.
• There is no infrastructure allocation for MTA scaling, API rate guarantees, or throughput validation.
• If you need to test at scale, please get in touch with Blueshift Support to coordinate a suitable test plan.

Best practices

• Use test users and small segments to validate campaign setup.
• Use CloudApp to test webhook payloads and verify endpoint behavior.
• Please don't use a sandbox for any real-time load or deliverability testing.