​

Overview

​

Types of Imports

1. Registered Users: These are users who are already registered on MoEngage.
2. Anonymous Users: These are users who are not yet registered on MoEngage.
3. Events (Standard and User Defined): MoEngage can import standard events like Campaign Interaction Events as well as your own user-defined events.

​

Preparing the Data

​

Importing Datetype attributes

​

Required Access Permissions

-- Grant SELECT permission on all tables in the schema
GRANT SELECT ON SCHEMA `catalog\_name`.`schema\_name` TO `[email protected]`;
-- Grant USE SCHEMA permission to access the schema
GRANT USE SCHEMA ON SCHEMA `catalog\_name`.`schema\_name` TO `[email protected]`;
-- Grant USE CATALOG permission (recommended for complete access)
GRANT USE CATALOG ON CATALOG `catalog\_name` TO `[email protected]`;

1. “ - The name of the warehouse you want MoEngage to use while executing queries.
2. “ - The name of the database you want to import data from.
3. “ - Give a strong password to the newly created database user.

​

Set Up Imports from Snowflake

1. 1. On the sidebar menu in MoEngage, hover over the Data menu item PROTECTED_4 . The Data menu appears.
   2. Click Data imports.
      PROTECTED_5
2. On the Data imports page, click + Import and select Users or Events to create a new import.
3. Click Snowflake to create a new import for either Users (Registered/Anonymous can be picked in the next step) or Events.

​

Step 1: Select Your Snowflake Connection and Table Source

​

Import Name

​

Step 2: Map Your Columns to MoEngage Attributes

1. Column name - This is the column name to be mapped. Below the column name, we also show a sample value (picked from the first row of the fetched table in the previous step) for your reference.
2. Map attribute - Here you need to pick which MoEngage attribute you want to map the table column to. You can also choose to create a new attribute. Some attributes support ingestion from multiple data types, so you need to pick the data type of the column as well. For the “DateTime” columns, you also need to pick the PROTECTED_32.
3. More actions - You can optionally choose to skip the column. The skipped column will not be imported.

Event Imports

Mapping	Description
User ID	This column will be used to match the users in MoEngage to your events.
Event time	You need to map the column that contains the timestamp (date + time) of when the event occurred. You need to ensure that this timestamp (date + time) is in UTC Timezone. The column type for this should be TIMESTAMP\_NTZ. The “Event Time” of the imported event will be converted to the timezone chosen in your MoEngage Dashboard settings: For the full list of supported datetime formats, refer to this section.

Once a mandatory mapping is marked, it will reflect against the column name in the mapping table and you will no longer be able to mark the column as skippable.Just like new events, you can also create a new attribute from the dropdown by clicking on ”+ Create attribute”:Give your attribute a name and select its Data type. You can edit this as well as existing attributes from the Data Management page. Do note that any new attributes you create now will only be available in your app after the first successful import.

​

Manifest Files

Optionally, you can choose to auto-map these columns by uploading a manifest file.To upload a manifest file, click the “Upload mapping file” option on the top-right of the mapping table:

Upload your manifest file and click Done. Your mappings will be auto-configured accordingly. Any columns with non-MoEngage attributes will be left blank and can either manually map the column or create a new attribute for it. Make sure your manifest file follows the expected conventions as mentioned.Any additional columns that are present in your Manifest File but not there in your table will be ignored. Also, if the mapping for an existing table column is not present in the manifest file, MoEngage will keep the mapping blank for you to manually configure it.Do note that if a column in the manifest file is mapped to a non-existent MoEngage Attribute, then the mapping will be blank and you will need to first manually create a new attribute from the UI and then map it.

​

Support for Object Data Type

Support for Object Data Type needs to be enabled for your account.

The Object data type is supported in Snowflake as well.

​

Store Compatible JSON Data in Snowflake

To store valid JSON inside Snowflake, you must change the data type of the column to VARIANT type. For more information, refer here. The JSON stored inside Snowflake should be a valid JSON; otherwise, the values will not be written as JSON. Here is an example JSON column:JavaScript

{ "Designation": "SSE", "Palace": "Banglore", "age": 30, "name": "Shasha" }

​

Import JSON Data via Snowflake

Existing attributes in MoEngage that have been marked as an Object type and are available to map to columns in Snowflake:You can always create new Object attributes from the mapping step as well, as shown below:

MoEngage does not support mapping with nested attributes. Only top-level attributes are available to map.

​

Save as a Segment

If you’re importing users, you can also add them to a custom segment inside MoEngage. Each time the sync is run, the imported users will continue to be added to this custom segment. We will not delete any users from this segment. You can then send targeted campaigns to this segment. To save your imported users in a custom segment, enable the “Save as a custom segment” option:Give your Segment a name and select the Identifier column in your table.

​

Import Behaviour

In the case of User Imports, you can also choose to update existing users only. This is helpful when you want to bulk update users’ attributes in MoEngage without creating any new users. To enable this, check the “Update existing users only” option under Import Behaviour:

​

Sending Import Notifications

You can, optionally, choose to get notified about your imports’ statuses via email. Select up to 10 emails to send the status emails to. You will receive an email about the following events:

1. An import was created
2. An import was successful
3. An import failed

When you are satisfied with all mappings, click Next. If there are any errors, correct them to move forward.

​

Step 3: Select the Import Frequency

1. One-Time imports: You can either choose to run the import as soon as possible or at a later date and time (scheduled). All existing rows that match the import criteria will be imported.
2. Periodic: You can choose to run your imports every few minutes, hourly, daily, weekly, or monthly, or with intervals and advanced configurations.

​

Duplicate Imports

1. Import Type - Users / Events
2. Import Sub-Type - Event Name / Registered / Anonymous / All users - If the event name is the same, or there already exists a registered/anonymous/all users import with the same Snowflake connection
3. Snowflake connection
4. Import schema & table

​

Frequently Asked Questions