Connecting a Destination for Stored Messages

You can set up Stored Messages if you are an Iterable member with the Manage Integrations permission.

# In this article

# Setup overview

To connect Stored Messages to your cloud storage bucket, first make sure your cloud storage destination is set up to connect to Iterable and ready to begin storing messages.

For AWS S3, share the setup guide for Setting up Stored Messages for AWS S3 with your AWS administrator.

Once your destination is ready, connect it to your Iterable project by following the instructions below.

You can only set up a single cloud storage destination per project, but you can store messages from multiple channels/mediums in the same destination, and you can store messages from all projects in the same destination.

# Adding a destination

To add a destination for Stored Messages, follow these steps:

1. Log in to Iterable and go to Integrations > Stored Messages.

2. Click Connect a Destination.

3. Select your destination storage and click Continue.

   • Currently available: AWS S3
   • Coming soon: Azure Blob Storage, Google Cloud Storage

4. Enter your cloud storage credentials, which vary by destination:

   • AWS S3 (see Setting up Stored Messages for AWS S3):
     • Role ARN
     • Role session name
     • Region
     • S3 bucket name

   

5. Select the Mediums you wish to store messages for: Email, SMS, and/or Push.

   TIP

   You can only configure one destination per project. If you plan to store messages from multiple channels/mediums, they’re all stored in the same destination.

6. Check the box to confirm the PII acknowledgement:

   I confirm that my cloud storage bucket is set to private to prevent exposure of customer data, including sensitive personally identifiable information (PII).

   • This is a required acknowledgement.
   • Messages sent from the Iterable platform may contain sensitive personally identifiable information.
   • Iterable is not responsible for data security in your destination.

7. Click Create Destination.

Once you’ve created your destination, Iterable begins storing exact message copies in your destination in about 15 minutes.

# Editing a destination

Once you’ve set up Stored Messages, you can go back and make changes to your destination’s configuration as needed.

Changing a destination takes up to 15 minutes to process.

To edit your destination:

1. Log in to Iterable and go to Integrations > Stored Messages.
2. Click Edit Destination.
3. Update the cloud storage details and Mediums selection as needed.
4. Click Save Destination.
5. In the confirmation, again click Save Destination.

Changes can take up to 15 minutes to implement.

# Deleting a destination

You can delete a Stored Messages destination if you no longer need the storage or if you are migrating to a new destination.

1. Log in to Iterable and go to Integrations > Stored Messages.
2. Click Edit Destination in the top right.
3. Scroll down if needed, and click Delete Destination at the bottom of the page.
4. In the confirmation, again click Delete Destination.
5. You'll have one final confirmation. Click Delete Destination a third time to confirm deletion.

Changes can take up to 15 minutes to implement. Messages stop storing when the deletion is complete.

# Accessing your stored messages archive

To view your stored messages archive, access the cloud storage bucket where the data is stored. To learn about the file naming conventions and JSON payload structures, see Stored Message JSON Payloads.