Setting Up S3 Snapshot Delivery — Partner Checklist

Use this checklist to gather everything MX8 needs to configure your server-side exposure data pipeline. You can share this page directly with your engineering team.

1. Your IAM Role ARN (and AWS Account ID if available)

MX8 uses this to grant your role PutObject permission into your dedicated S3 prefix.

Example format: arn:aws:iam::123456789012:role/UploadRole

2. Hashing details (if sending hashed IPs)

• Algorithm — MD5 is the current default; other algorithms are available on request.

• Output format — hex or base64.

• Salt — are you using one? If yes, share it securely with your MX8 contact.

• A short code snippet showing exactly how you generate the hash.

If you're sending plaintext IPs, skip this step.

3. Expected delivery pattern

• How often will you upload? Daily is recommended; multiple times per day is fine.

• Approximate time window in UTC.

• Approximate daily volume (rows and/or number of files).

4. Retention period

How long should MX8 keep each file's records for matching? The default is 7 days, but this can be extended if your campaign needs a longer lookback window.

5. Column mapping

Tell MX8 which of your CSV columns map to each required field:

• → exposed_ip_address or hashed_ip_address

• → uid

• → brand

Your column names don't need to match MX8's — just let us know the mapping.

6. A sample file

Send a small file (just a few rows) so MX8 can validate the format before you begin production delivery. Make sure it follows the format requirements in Server-Side File Delivery & Format Requirements.

• Creating an S3 Snapshot Exposure Source — how to set up the source in the platform.

• Server-Side File Delivery & Format Requirements — file format specs, naming, and duplicate handling.

• IP Hashing Rules for Exposure Data — algorithm, input formatting, and salt guidance.