Skip to main content

​
Introduction

MoEngage Event Exports let you forward the events MoEngage receives or generates, such as user actions and campaign interaction events, to a destination outside MoEngage. This page helps you choose the right destination for your use case. Once you pick one, its dedicated help doc walks you through the setup.
Event exports are part of the Streams add-on. Contact your MoEngage customer success manager (CSM) to enable them for your account.

​
Choose Your Export Destination

MoEngage supports three categories of export destinations: Select the destination that matches your setup:

Streams

Forward events to your own API endpoint in near real-time by using a Bulk API call.

Snowflake

Export events directly to Snowflake tables.

Databricks

Export events to Databricks through a direct export or OpenSharing (zero-copy sharing).

Google BigQuery

Export events directly to BigQuery, without an intermediate Google Cloud Storage hop.

Amazon Redshift

Export events directly to your Amazon Redshift cluster.

Amazon S3

Export events as JSON files to an S3 bucket, on a schedule you choose.

SFTP

Export events as JSON files to your own SFTP server, on a schedule you choose.

Google Cloud Storage

Export events as JSON files to a GCS bucket, on a schedule you choose.

​
How Exports Work

The following mechanics are common across data warehouse and cloud storage destinations. Streams, being a direct API call rather than a scheduled export, does not follow this flow. You set up and manage every export from the App Marketplace: search for the destination, open its tile, and go to the Integrate tab to add or manage an export.

​
Export Failure, Pause, and Replay

MoEngage will retry an export multiple times before marking it as failed. The export will be paused if multiple scheduled exports fail. While it is paused, MoEngage saves the events the export would have delivered. After you fix the problem and re-enable the export, you can replay the collected data:
  • MoEngage keeps up to 7 days of collected data while an export is paused, dropping the oldest days if the pause runs longer.
  • You can replay collected data up to 30 days from the date the oldest paused data was collected. The 7-day retention can cut this window short, so not all 30 days are always replayable. For a worked example, refer to the failure policy section on each destination’s page.
  • A replay resends the entire collection, so deduplicate on the event_uuid field at your end if you replay more than once.
The exact number of scheduled exports that need to fail before MoEngage pauses an export depends on its frequency (for example, hourly data warehouse exports pause after 3 consecutive scheduled exports fail, while daily or weekly cloud storage exports pause after 1). For the specific thresholds and replay steps, refer to the failure policy section on each destination’s page. MoEngage notifies you when it pauses an export through the Data Exports system alert, so you can fix the issue and replay the data. MoEngage subscribes workspace admins by default, along with the user who creates or updates the export. To manage who else receives this alert, refer to Alert Management.

​
Further Reading

For the full event and attribute schema exported to each destination, refer to the Data Export Glossary. To track how much data you are exporting against your monthly usage, refer to Analyze the Volume of Data Exports.