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

To add a new BigQuery export, perform the following steps:

1. On the left navigation menu in the MoEngage UI, click App marketplace.
2. On the App Marketplace page, search for BigQuery.
3. Click the Google BigQuery tile.
4. On the Google BigQuery page, go to the Integrate tab and click +Add Export.
5. Enter the following details:
   

   Field	Required	Description
   Export name	Yes	Type a name for the BigQuery export. Ensure your export name contains at least three characters.
   BigQuery connection	Yes	Select your BigQuery connection.
   Dataset ID	Yes	Select the specific dataset in BigQuery where your data will be exported.
   Table name	Optional	Enter the name for the export table. If left blank, MoEngage creates a name for you with the prefix moe_events. Note: To avoid errors, allow MoEngage to automatically create this table.
   User Properties	Optional	Select the specific user properties you want to include in the export.
   Select events	Yes	Select the events to export to BigQuery. You can choose to export all events, including existing and new events coming into MoEngage, or manually select specific events to export.

   
   
6. Click Save export.

Now, MoEngage populates the newly created table with events every hour.

Export Frequency

MoEngage populates the data hourly.

Sample Table Structure

If you do not specify a table name in the export configuration, MoEngage creates the following table in your dataset:

moe_events_<table_creation_timestamp>: MoEngage populates all your events in this table. All exports set up under a single connection are appended to the same table.

The overall structure of the table will remain the same for all event types. Any new user property or event attribute exported will be included in user_attributes or event_attributes, respectively. All events are populated in a single table containing the necessary information, such as event names and times, for easy analysis.