Introduction
Databricks is a platform that allows organizations to store, analyze, and process large volumes of structured and semi-structured data in a highly scalable and efficient manner. With its unique architecture, organizations can consolidate their data, perform quick analytics, and gain valuable data-driven insights accessible to all users.
MoEngage <> Databricks
With this integration, you can export data from campaign interaction events to your Databricks tables.
Integration
library_add_check |
Prerequisites
|
If not done already, you need to set up a MoEngage <> Databricks integration for your account. For more information, refer to the Databricks Integration help doc.
Export Events from MoEngage to Databricks
Step 1: Ensure Your User's Assigned Role Has Required Permissions
MoEngage will need WRITE
access to your Databricks database to store data. You have the option to grant these permissions to an existing database user or create a new dedicated database user specifically for MoEngage.
Use the following code to configure write access for data storage in your Databricks database:
GRANT USE CATALOG ON CATALOG `<CATALOG_NAME>` TO `<EMAIL_ID_OF_THE_USER>`;
GRANT USE SCHEMA, CREATE TABLE ON SCHEMA `<CATALOG_NAME>`.`<SCHEMA_NAME>` TO `<EMAIL_ID_OF_THE_USER>`;
Remember to change the following values:
-
<CATALOG_NAME>
- The name of your catalog. -
<SCHEMA_NAME>
- The name of your database or schema. -
<EMAIL_ID_OF_THE_USER>
- The email ID of the user who created the token.
Step 2: Add a New Databricks Export on the MoEngage App Marketplace
info |
Information
|
To add a new Databricks export, perform the following steps:
- On the left navigation menu in the MoEngage dashboard, click App marketplace.
- On the App Marketplace page, search for Databricks.
- Click the Databricks tile.
- On the Databricks page, go to the Integrate tab and click +Add Export.
- Enter the following details:
Field Required Description Export name Yes Type a name for the Databricks export. Databricks connection Yes
Select your Databricks connection.
Export into schema Yes
Select the schema that MoEngage uses to create new tables and export your events into.
User properties Optional
Select the user properties (user properties and device properties) you want to export with your events.
Select events Yes Select the events you want to export to Databricks. You can choose to export all events, including existing and new ones coming into MoEngage, or manually select specific events to export. - Click Save export.
MoEngage starts dumping (appending) events to the newly created table every hour.
Export Frequency
MoEngage will dump the data at hourly intervals.
Sample Table Structure
MoEngage will create the following table in your schema:
moe_events_<table_creation_timestamp>
- MoEngage will dump all your events in this table. All exports set up under a single connection will be appended to the same table.
The overall structure of the table will remain fixed for all types of events. Any new user property or event attribute that is exported will be part of the user_attributes
or event_attributes
column respectively. All the events will be dumped in a single table containing necessary information such as event names, event times for easy analysis.
Field | Type | NULL |
---|---|---|
app_name | VARCHAR | NOT NULL |
event_name | VARCHAR | NOT NULL |
event_code | VARCHAR | NOT NULL |
event_uuid | VARCHAR | NOT NULL |
event_time | TIMESTAMP | NOT NULL |
event_type | VARCHAR | NOT NULL |
event_source | VARCHAR | NOT NULL |
uid | VARCHAR | NULL |
user_attributes_moengage_user_id | VARCHAR | NULL |
device_attributes_moengage_device_id | VARCHAR | NULL |
push_id | VARCHAR | NULL |
email_address | VARCHAR | NULL |
mobile_number | VARCHAR | NULL |
event_attributes_app_version | VARCHAR | NULL |
event_attributes_sdk_version | VARCHAR | NULL |
event_attributes_platform | VARCHAR | NULL |
event_attributes_campaign_id | VARCHAR | NULL |
event_attributes_campaign_name | VARCHAR | NULL |
event_attributes_campaign_type | VARCHAR | NULL |
event_attributes_campaign_channel | VARCHAR | NULL |
event_attributes_readable_campaign_id | VARCHAR | NULL |
event_attributes_parent_campaign_id | VARCHAR | NULL |
event_attributes_parent_flow_id | VARCHAR | NULL |
event_attributes_parent_flow_name | VARCHAR | NULL |
event_attributes_variation_id | VARCHAR | NULL |
event_attributes_locale_id | VARCHAR | NULL |
event_attributes_locale_name | VARCHAR | NULL |
event_attributes_url | VARCHAR | NULL |
event_attributes_timestamp | TIMESTAMP | NULL |
event_attributes_first_session | BOOLEAN | NULL |
event_attributes_logged_in_status | VARCHAR | NULL |
event_attributes | VARIANT | NULL |
user_attributes | VARIANT | NULL |
device_attributes | VARIANT | NULL |
Frequently Asked Questions
It typically takes up to 30 minutes for the automated data exports to be set up for your account and for you to start seeing data there.
Yes, if you need to export new events at a later time, you can always edit your configuration on the App Marketplace and get the new events added to your exports.
As of now, you cannot export historical data using Automated Data Exports. Once configured, you will start seeing data for each event from the time you enabled your exports.
If your billing plan does not cover this already and you need to get this enabled at a later time, you would need to work with your Customer Success Manager to get this included in your billing plan. Based on the amount of data that MoEngage will place in your Data warehouse/Partner/API on a monthly basis, this could lead to additional charges.