Messages archive

Messages archive lets you archive, retrieve, and inspect exact copies of sent emails and SMS up to 2 years after they were sent. Whether you're handling a customer complaint, responding to a legal request, or investigating a campaign issue, you can access the original message content directly—no reconstruction or workarounds needed.

Use cases

Missing promotions: When customers report missing offers or non-working coupon codes, support agents retrieve the original email or SMS directly.
Support verification: When players raise questions about communications, support teams verify that messages were sent and review their content. A custom portal integrated via API displays emails and SMS with subject line, preheader, and rendered content.
Legal retention: Banks store and retrieve all outgoing customer communications across email and SMS to meet legal retention requirements. The archive supports security investigations, customer support, and marketing review.
Payment notifications: When customers report missing payment due notifications, support agents retrieve the original email or SMS through a back-office portal integrated via API.

How messages archive works

When a message is sent through a campaign, scenario, or transactional API, the platform automatically stores the exact message content and metadata. The messages are stored for all the projects within an account where the archive is enabled.

All messages are accessible through the platform UI or via the Data API. The archive retains messages for 2 years, after which they're automatically deleted. If a customer profile is anonymized or deleted, their archived messages are removed immediately.

When a message is stored

A message is stored when it's successfully enqueued to a provider API—specifically, when the campaign event status is enqueued. Messages that aren't attempted or aren't accepted by the provider aren't stored. This includes events with status abort, suppressed, or enqueue_failed.

What’s stored per message

Email

Data type	Fields
Metadata	Sent timestamp, sender name, sender email, recipient email address, campaign name, campaign ID, action ID, action name.
Content	Subject line, preheader, email HTML, attachment list (attachment name, size, and file type).

SMS

Data type	Fields
Metadata	Sent timestamp, sender, recipient phone number, campaign name, campaign ID, action ID, action name.
Content	Message text.

Supported channels

Channel	Support level
Browser push	Not supported
Email	Available
MMS	Not supported
Mobile push notifications	Not supported
RCS	Not supported
SMS	Available
WhatsApp	Not supported

Limitations

Retention

Messages are stored for 2 years.
Configurable expiration periods aren't supported.

Privacy and data handling

When a customer profile is anonymized or deleted, all their archived messages are deleted immediately and become inaccessible via the UI and API.
Archived messages are stored exactly as sent, including any personal data embedded in the message content (for example, names, order details, consent page links). When a customer profile is deleted or anonymized, all associated archived messages are permanently removed.

Links and media

Always open links from archived messages in an anonymous window to avoid triggering profile merges or campaign tracking events.

Archived content is stored exactly as the customer received it, including click tracking links and transfer identity functionality. Clicking a link records a campaign click event on the recipient's profile, and links containing transfer identity may trigger profile identification and merging. The open tracking pixel is stripped before storage.

Images are stored as links to the original image storage, not as copies. Images can change or be removed independently of the archive retention period.