​

Data Exports

​

Datasets

​

Supported storage

• Amazon S3. Provide the bucket, region and an access key.
• Google Cloud Storage. Create an HMAC key for a service account with the Storage Object Creator role on the bucket, and choose gcs as the provider.
• S3-compatible storage such as Cloudflare R2, MinIO or Backblaze B2. Choose s3 and set the endpoint, for example https://<account-id>.r2.cloudflarestorage.com. The endpoint must use HTTPS and resolve to a public address.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::acme-exports/sequenzy/*"
    }
  ]
}

​

File layout

<prefix>/email_events/date=2026-09-30/email_events-<fromMs>-<toMs>-0000.jsonl.gz
<prefix>/sms_events/date=2026-09-30/sms_events-<fromMs>-<toMs>-0000.jsonl.gz
<prefix>/custom_events/date=2026-09-30/custom_events-<fromMs>-<toMs>-0000.jsonl.gz
<prefix>/subscribers/date=2026-09-30/subscribers-0000.jsonl.gz
<prefix>/subscribers/date=2026-09-30/_SUCCESS

• Each file is gzip-compressed JSON, one object per line, up to 50,000 lines.
• date= folders are Hive-style partitions, so warehouses can prune by day.
• Event files cover a window of recorded time (fromMs exclusive, toMs inclusive, in epoch milliseconds). A delayed bounce lands in the window in which Sequenzy recorded it, so nothing is missed behind an earlier window.
• The subscriber snapshot is complete when _SUCCESS exists. Load a day’s snapshot only after that marker appears.

​

Delivery guarantees

• At least once. If a run fails partway, the retry rewrites the same window with the same file names. In rare cases, such as a changed file count after a retry, a row can appear twice. Deduplicate on id.
• No gaps. A window only advances after every file in it is written. Exports trail real time by about two minutes so late writes are included.
• Retries. Failed runs retry automatically, backing off from the export frequency up to every 6 hours. The dashboard, API and CLI show the last error until a run succeeds.
• Ordering. Rows inside a file are ordered by recorded time. Use occurred_at for analysis.

​

Row schemas

​

email_events

​

sms_events

​

custom_events

​

subscribers

​

Load into your warehouse

CREATE STAGE sequenzy_stage
  URL = 's3://acme-exports/sequenzy/'
  STORAGE_INTEGRATION = my_s3_integration
  FILE_FORMAT = (TYPE = JSON COMPRESSION = GZIP);

CREATE TABLE email_events (raw VARIANT, file STRING);

-- Run on a schedule, or wrap in a Snowpipe with AUTO_INGEST = TRUE
COPY INTO email_events (raw, file)
FROM (SELECT $1, METADATA$FILENAME FROM @sequenzy_stage/email_events/);

SELECT raw:event_type::string AS event_type, COUNT(DISTINCT raw:id)
FROM email_events
GROUP BY 1;

CREATE EXTERNAL TABLE sequenzy.email_events_raw
WITH PARTITION COLUMNS (date DATE)
OPTIONS (
  format = 'NEWLINE_DELIMITED_JSON',
  compression = 'GZIP',
  uris = ['gs://acme-exports/sequenzy/email_events/*'],
  hive_partition_uri_prefix = 'gs://acme-exports/sequenzy/email_events'
);

SELECT event_type, COUNT(DISTINCT id)
FROM sequenzy.email_events_raw
WHERE date >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
GROUP BY event_type;

CREATE TABLE email_events_staging (
  id VARCHAR(128), event_type VARCHAR(32), occurred_at TIMESTAMPTZ,
  subscriber_id VARCHAR(128), email VARCHAR(255), campaign_id VARCHAR(128),
  clicked_url VARCHAR(2048)
);

COPY email_events_staging
FROM 's3://acme-exports/sequenzy/email_events/date=2026-09-30/'
IAM_ROLE 'arn:aws:iam::123456789012:role/redshift-s3-read'
FORMAT AS JSON 'auto ignorecase'
GZIP TIMEFORMAT 'auto';

SELECT event_type, COUNT(DISTINCT id)
FROM read_json_auto('s3://acme-exports/sequenzy/email_events/*/*.jsonl.gz',
                    hive_partitioning = true)
GROUP BY event_type;

​

Manage exports

• Pause and resume. Paused exports keep their position and continue where they stopped. Pausing or deleting an export stops a run in progress before its next file.
• Change datasets. Datasets you add start from the time you add them.
• Move or rotate keys. Changing the bucket, prefix or credentials writes a new test file first. Exports continue from their position in the new location, and a subscriber snapshot in progress starts over there. An export already running stops before its next file and continues with the new settings.
• Export now. Runs immediately instead of waiting for the schedule.
• History. Each run from the last 14 days shows rows, files, size and any error.
• Delete. Stops the export. Files already written stay in your bucket.