Event Stream Overview

Export granular data for independent analysis with Sailthru Connect. Gain insights about your audience and how users respond to marketing messaging sent via Sailthru.

Available Data Sets

The Sailthru Connect data sets documentation shows all the information provided by each data set. Each bullet point in the following lists is linked to the full table.

Event Data

Lookup Data

Bucket Structure

Your bucket structure will look different depending on the type of event/lookup data.

Data exported into your bucket will adhere to the following pattern for event data tables:

s3://[bucketname]/[table_name]/dt=[yyyymmdd]/client_id=[client_id]/[exportfilename].csv

For example:
s3://example-bucket/campaign_click/dt=20190926/client_id=0000/part-1ae5f73f.csv

Data exported into your bucket will adhere to the following pattern for lookup data tables:

s3://[bucketname]/[table_name]/dt=[yyyymmdd]/hr=[hh]client_id=[client_id]/[exportfilename].csv

For example:

s3://example-bucket/campaign/dt=20191001/hr=00/client_id=0000/part-1ae5f73f.csv

Note: Sailthru recommends that you avoid adding your own objects into this bucket. The intention is to avoid unexpected issues with the export process or inadvertently giving Sailthru access to non-Sailthru data.

Bucket Policy

Since Sailthru is establishing a connection to your S3 bucket, you must set up a bucket policy which includes a bucket policy on your side.

Configuring Your S3 Bucket Policy

  1. Configure a dedicated S3 bucket to Sailthru. This bucket can be located in any AWS region.
  2. Apply a bucket policy giving Sailthru the appropriate write access. Below is a sample policy with an export bucket called EXAMPLE_BUCKET (this can be copy-and-pasted, and you only need to change the bucket name to your own):
    {
    
        "Version": "2012-10-17",
    
        "Statement": [
            {
    
                "Sid": "bucket permissions",
    
                "Effect": "Allow",
    
                "Principal": {
    
                    "AWS": "arn:aws:iam::099647660399:root"
    
                },
    
                "Action": "s3:ListBucket",
    
                "Resource": "arn:aws:s3:::EXAMPLE_BUCKET"
    
             },
    
            {
    
                "Sid": "object permissions",
    
                "Effect": "Allow",
    
                "Principal": {
    
                    "AWS": "arn:aws:iam::099647660399:root"
    
                },
    
                "Action": [
    
                    "s3:PutObject",
    
                    "s3:DeleteObject"
    
                ],
    
                "Resource": "arn:aws:s3:::EXAMPLE_BUCKET/*"
    
            }
    
        ]
    
    }

Configuring Sailthru Connect to use your S3 Bucket

Log in to Sailthru and configure your S3 bucket in the Settings > Setup > Integrations view. Enter your S3 bucket name in the “Sailthru Connect S3 Bucket”.

 

What happens after the connection is set

Once you’ve saved your S3 bucket, and having implemented the proper policy, two processes will start up.

First, data will start flowing within 2 hours to stream event data to your bucket. After the stream starts, more data will be streamed every hour.

Second, a connection validation will be run intermittently. We will upload-then-delete a file named _ACCESS_CONFIRMATION which can be safely ignored. This will be a top-level file, located at s3://example_bucket/_ACCESS_CONFIRMATION.

Top