Overview
BigQuery is a fully managed, serverless data warehouse available on the Google Cloud Platform (GCP). It allows you to perform complex analytics on terabytes of data in real time without managing infrastructure.How Does MoEngage Work with BigQuery?
The MoEngage and BigQuery integration directly transfers user and event data to Google BigQuery for advanced analytics.Integration
To create a BigQuery connection, refer to Google BigQuery.Export Events from MoEngage to BigQuery
Step 1: Ensure Your User’s Assigned Role Has Required Permissions
To successfully set up and execute a BigQuery export, your service account or user must have the following permissions based on the action being performed:- To Create a Connection: To establish a new BigQuery connection within the MoEngage App Marketplace, the user must have the BigQuery Data Viewer and BigQuery Job User roles. This allows MoEngage to validate the project and dataset details. For more information, refer here.
- To Perform Exports: To execute the actual data transfer, your service account must be assigned the BigQuery Data Editor role. This grants MoEngage the necessary permissions to read and write data to your specific BigQuery tables.
Step 2: Add a New BigQuery Export in the MoEngage App Marketplace
- For a full list of events and attributes, refer to the Data Exports Glossary.
- The
event_timeof exported events is always in UTC. - MoEngage does not currently support exporting historical data.
- On the left navigation menu in the MoEngage UI, click App marketplace.
- On the App Marketplace page, search for BigQuery.

- Click the Google BigQuery tile.
- On the Google BigQuery page, go to the Integrate tab and click +Add Export.
- Enter the following details:
- Click Save export.
Export Process and Frequency
After you save the export, MoEngage creates a destination table in your dataset. New event data is then appended to this same table at hourly intervals: Initial action: MoEngage creates the table when the first export is triggered. Recurring action: MoEngage adds (appends) data to the same table every hour.Sample Table Structure
If you do not specify a table name in the export configuration, MoEngage creates a single table in your dataset using the following format:moe_events_<table_creation_timestamp>
Export Failure Policy
MoEngage pauses an export that keeps failing. While it is paused, MoEngage collects the events the export would have delivered, and you replay them after you fix the problem.When MoEngage Pauses an Export
Exports to BigQuery run hourly. MoEngage will retry an export multiple times before marking it as failed. The export will be paused after 3 consecutive scheduled export failures. When MoEngage pauses an export, it alerts you and shows the export as Paused on the App Marketplace.What Happens While an Export Is Paused

Resume an Export
Find the Failure Reason
On the App Marketplace, click the Integrate tab, and then hover over the Paused label on the export. MoEngage names the reason for the failure, such as a missing write permission on the destination table, and tells you how to fix it.
Enable the Export
Fix the cause at your end, and then turn on Export status for the export. Do this as soon as you can, because the 7-day window keeps moving while the export stays paused. When you enable the export, MoEngage stops collecting and sets aside what it has: the last 7 days of paused data, or all of it if the pause was shorter. This is the data you can replay. It stays fixed from then on, and does not reduce further even if you wait to replay it.Replay Paused Data
Request a Replay
MoEngage saves the data it collected while the export was paused. An export with data waiting shows a Replay available label on the Integrate tab. To replay, perform the following steps:- Hover over the Replay available label, or open the kebab menu on the export.
-
Click Replay paused data.

-
In the Replay paused data dialog box, click Confirm.

Replay Results
When the replay finishes, MoEngage emails the user who requested it with one of the following results:Avoid Duplicate Data
Every replay sends the whole collection again, because MoEngage does not deduplicate. If you replay more than once, deduplicate at your end on theevent_uuid field, which is unique for each event. For the fields in the export, refer to the Data Export Glossary.
Export Paused Alerts
MoEngage alerts you when it pauses an export, so you can fix the issue and replay the data collected while the export was paused. MoEngage subscribes workspace admins to the Data Exports system alert by default, and adds the user who creates or updates an export. To subscribe or unsubscribe anyone else, go to the Alert Management page. Subscribing or unsubscribing changes notifications only for that person, and does not affect anyone else’s subscription.Frequently Asked Questions
What does the Replay available label mean?
What does the Replay available label mean?
My export was paused for three weeks. Why can I replay only part of it?
My export was paused for three weeks. Why can I replay only part of it?
Why did my replay come back as Partially Successful?
Why did my replay come back as Partially Successful?
Can I run two replays at the same time?
Can I run two replays at the same time?
I replayed twice and I see duplicate rows. Why?
I replayed twice and I see duplicate rows. Why?
event_uuid field, which is unique for each event.How soon will I start getting the data?
How soon will I start getting the data?
Can I export additional events at a later time?
Can I export additional events at a later time?
Can I export historical data using Automated Data Exports?
Can I export historical data using Automated Data Exports?
Is there any pricing involved for Automated Data Exports?
Is there any pricing involved for Automated Data Exports?
Does Data Exports guarantee the latest user attributes?
Does Data Exports guarantee the latest user attributes?
