Exports and BigQuery

Exports give you your app data as a file. Destinations send the same data to another tool on a schedule.

Status: on by default for file exports. Destinations need setup with your own account keys.

Datasets#

You can export these datasets:

• events: what shoppers did in the app.
• devices: installed phones and their settings.
• campaigns: campaign records.
• sends: messages sent by campaigns and automations.
• order attributions: which orders came from the app.

The push token of a phone is never exported.

File exports#

1. Open Exports and press New export.
2. Pick a dataset and a date range.
3. Pick CSV or NDJSON.
4. Choose how personal data is handled. The default is to leave it out. You can hash a column so it still matches across datasets, or keep it.
5. Review and run.

When the file is ready, use the download link. Links expire after 24 hours. A single file can hold up to 200,000 rows. For more, use a destination.

Destinations#

Open Exports, then Destinations. There are three kinds:

• BigQuery: you create the tables first. The app does not create them. The destinations page lists the column names and types.
• S3-compatible storage: files are sent to your bucket.
• Webhook: each batch is sent to your web address. Requests are signed with a secret you set.

Secrets are write-only. The app never shows them again. To edit connection settings, enter the secret again.

Schedules and failures#

• A destination can run every few minutes up to once a week.
• Each run only sends new data since the last successful run.
• If a destination fails 10 runs in a row, the app turns it off. Fix the problem and turn it on again.
• A "test connection" check tells you if a table or key is missing.

Note on updates#

Some datasets (devices, campaigns and sends) send a new row each time a record changes. Remove duplicates by the ID column in your own tool.

Permissions#

Exports need the analytics export permission. Destinations need the integration manage permission. See Team and roles.