1. Overview

• Definition: Maps each Source Column (data from your business’s database) to a Destination Column (an entity field in Mobio) — the 3rd step in the sync setup process.
• Purpose: Ensures incoming data lands in the correct CDP field so that it can be stored and analyzed accurately.

2. Prerequisites

• Related article: Configure Trusted Sources & Overwrite Rules.
• Permissions: Your Mobio account must have the INTEGRATION RBAC permission. See the RBAC permissions guide.
• Your source table/view must have a clearly defined data structure.

3. Steps to Set Up Mapping and Handle Formatting

Mapping ties directly into Mobio’s data transformation rules. Here’s what to know about formatting before mapping:

3.1. Format Error Handling Rules

• Identifier fields (required): If the source data has the wrong format for a core identifier field (e.g., a phone number containing letters), Mobio fails the entire record — none of that row’s data gets recorded in Mobio.
• Non-identifier fields (optional): Mobio still accepts the record and processes the valid attributes; it only skips the value with the format error.
• You can check which fields were updated and which weren’t by monitoring the log in the sync report.

3.2. Data Type Matching Rules

• String: String data from a source column can only map successfully to a destination field of type String or Array (String). String can’t map to an Integer field.
• Number to Date/Datetime: Mobio automatically converts based on a millisecond timestamp format.
  • If the destination is Date: only the Day/Month/Year is recorded; the Hour/Minute/Second defaults to 00:00:00.
  • If the destination is Datetime: the full Day/Month/Year + Hour/Minute is recorded.
• Time zone: Mobio records Datetime fields from every data source in UTC. The field is then displayed in the GMT zone that matches whatever time zone the user or admin has configured in Mobio.

4. Advanced Mapping

4. Advanced Mapping Steps

Configure mapping

On the Mapping screen, you’ll see two columns: Source (left) – CDP Base Services (right).

• Select the mapping entity: You can map multiple entities within a source (e.g., row 1 maps to Profile-Dynamic Event, row 2 maps to Profile).
• Auto-Mapping: Saves you time — when a Source Column’s key matches a Destination Column’s key, Mobio maps them automatically. Mobio can also remove Vietnamese accents and/or replace spaces with underscores to find a match (e.g.,fullname/full_name → Full Name).

(Optional) Configure Data Transformation

For each mapped row, you can define rules to convert the source data before it is recorded into Mobio. This step is optional, but critical when your source data’s format or values differ from Mobio’s standards.

See Configure Data Transformation for details.

Handle complex nested JSON arrays.

• Source data can include an Array of nested objects — for example, a customer with multiple addresses (home address, billing address, and so on), each holding its own city, district, and ward. Mobio displays these nested keys using dot notation (e.g., address.city, address.ward).
• You can only set the Overwrite/Add-new rule on the top-level parent column — every nested field under it automatically follows that same rule.

Use a Constant Value

Instead of selecting an existing source column, Mobio lets you manually enter a fixed value and map it to a destination field.

Example use case: Type “Branch A” as a Constant Value and map it directly to the behavior tag field. This tag is then automatically added to every Profile recorded from this Connector — extremely useful for segment filtering later.

• If a Connector has Trusted Source turned on, you must map at least 1 Verified field.

5. Frequently Asked Questions (FAQ)

• Q: Can I map one Source Column to multiple Destination Columns?
  • A: Yes. A source column can map to multiple fields in Mobio if their data types match.

6. Next Steps

Configure Data Transformation