1. Overview

• Definition: Covers the end-to-end framework for setting up a sync of event data from your source into a Profile, Oppty, or Ticket in Mobio.
• Value: Makes it easy to collect and sync customer behavioral events for analysis and experience personalization.
• Users: Admin, Data Engineer.

2. Prerequisites

• Related article: You need at least one Connector already set up. (See the Create Connector series.)
• Permissions: Your Mobio account must have the INTEGRATION RBAC permission. See the RBAC permissions guide.
• Access Path: Go to Settings → Data Integration → Data Source → select Data Mapping.

3. Step-by-step instructions

This article is a basic 5-step framework. Each step is covered in the linked articles below.

Step 1: Select an Entity

You only complete this step once, when you first set up this sync — none of these settings can be reconfigured after you save the Connector.

Select the entity to sync

• Under Entity, the system displays: “Please select the target entity.”
• Select the entity based on your process’s business need:
  • Profile: Sync behavioral events to individual customers.
  • Oppty: Sync events tied to sales opportunities.
  • Ticket: Sync events tied to support tickets.
• Note: Company doesn’t support Dynamic Event — this option is greyed out in the interface.

Select the Data input type when the entity is Oppty/Ticket

• Add New: Creates a new Oppty/Ticket when syncing data.
• Update: Updates an existing Oppty/Ticket in Mobio.

Declare the source data structure

• Your next step depends on your Connector type:
  • Database Connectors (Oracle, MySQL, PostgreSQL, SQL Server, etc.): Select the table containing the behavioral data you want to sync (Table, View, or Materialized View). You can select only one table/view at a time, and you can’t change it after you save the configuration. Mobio extracts 1,000 sample records for preview.
  • HTTP API Connectors: Declare your source data structure with a JSON Schema, in one of two ways:
    • Paste valid JSON into the JSON Data field.
    • Upload a sample file (up to 1 MB).
• Click Continue when you’re done.

Step 2: Map the data

Mobio displays a side-by-side mapping screen: Source Column on the left, CDP Base Services (destination fields in Mobio) on the right.

For each mapping row, configure:

• Source Column: Select keys from your JSON schema.
• Overwrite rules: See Configure Trusted Sources & Overwrite Rules for details.
• Target Entity: Select which entity to sync this data into (e.g., Dynamic Event, Profiles).
• Destination Field: Select the specific attribute of that entity to map data into (e.g., event timestamp, phone number).

A source field can map to multiple Mobio fields.

Click Add New to add another mapping row. See Configure Data Mapping Rules for details.

Step 3: Set the event sync rules

Event record rules

Mobio applies two fixed rules (no configuration needed):

• Synced Event data is always created new — Mobio can’t update Events that have already been synced.
• Mobio syncs Event data by matching the Event key and all Event fields.

Sync rules

This section controls which Profile records an Event.

Consent information (per Decree 13/2023/ND-CP):

• Set the default Consent value assigned to a new Profile created from this source. Configure 3 types:
  • Tracking Consent: Yes/No (default: Yes)
  • Analytics Consent: Yes/No (default: Yes)
  • Marketing Consent: Yes/No (default: Yes)

Profile sync rules:

• If a Profile already exists and meets the configuration, Mobio records the Event to it. If no matching Profile is found, Mobio creates a new one from the synced data.
• Select the Identification Information used to merge Profiles (e.g., phone number). Click Add Rule if you need more matching conditions.

Step 4: Set the sync schedule

• Set up the mechanism and schedule for Mobio to automatically pull data into the CDP. See Set Up Sync Mechanisms & Schedule for details.
• Click Finish to save your entire sync configuration.

4. Frequently Asked Questions (FAQ)

• Q: Can I change the source configuration (e.g., update the JSON Schema) after saving the process?
  • A: Click Update Schema on the Mapping screen to update the source structure. However, the entity and data input type you selected in Step 1 are locked after saving — to change them, create a new connector.

5. Next Steps

Once your sync process is running, check the Reports area to monitor incoming records: Overview of Data Flow synchronization reports