1. Overview

• Definition: Controls how data is received (the mechanism) and when Mobio pulls it into the CDP (the schedule) — the final step in setting up a data source.

2. Prerequisites

• Related article: Configure Data Mapping Rules.
• Permissions: Your Mobio account must have the INTEGRATION RBAC permission. See the RBAC permissions guide.

3. Steps to Set Up the Sync Schedule

Streaming

Under Data sync mechanism, select Streaming. Mobio describes it as: “A streaming data-processing model. Data is processed immediately or within a very short time window.”

There’s no fixed schedule — data flows into the CDP as soon as it occurs at the source.

Configure Sync Limits (technical parameters that control how much data each request handles):

• Bulk API query batch size: Mobio uses this parameter to determine partition size. When the number of records in a request exceeds the limit, the Connector automatically splits it into multiple requests to sync the data. (Default: 200 records/request)
• Payload size: The maximum record size, including headers and the request body. If a request’s payload exceeds the limit, the Connector doesn’t process that record. (Default: 3 MB/request)

Once you’ve configured Sync Limits, skip the Snapshot Mechanism section and go straight to Trace Key and Sync Result Notifications below.

Snapshot

The system automatically saves the raw data and always maintains a copy. This process is repeated each time the data is modified.

Choose 1 of 2 Snapshot Types

• Snapshot Full: Syncs all data from the source table.
• Snapshot Incremental: Continues syncing from the latest recorded checkpoint. The system queries only newly generated records instead of scanning the entire table again.

Configure the Sync Start Point

Set a starting value for Mobio to query data from.

Snapshot Full

• Only default: Sync from the 1st record — Mobio automatically syncs from the 1st record every session. No further configuration needed.

Snapshot Incremental

• Default: Recorded value in the most recent synchronization — The system automatically records the last value from the previous session.
• If you need a one-time manual override (e.g., to re-run from the start, or start from a specific timestamp/ID), turn on the Set a one-time exception for the next session toggle.
  • Sync from the 1st record: Skip the current checkpoint and resync from the beginning
  • Optional value: Select a starting value for the sync session.
• Note: The exception only applies to a single session — Mobio automatically reverts to default afterward.

Note: the exception only applies to a single session — Mobio automatically reverts to default afterward.

• Mobio supports sharing the checkpoint value between Snapshot Full and Incremental modes. When you switch between the two, the checkpoint value is preserved, so the sync process continues smoothly without repeating or skipping records.

Chunk Size

Splits data into smaller chunks so Mobio processes it in batches, avoiding overload. You can configure the size of each chunk — from 1,000 up to 20,000 records (default: 10,000). This also lets Mobio pinpoint exactly which chunk failed to sync, so it can rerun just that chunk — instead of re-running every record of the entire sync session.

Note: chunking isn’t the same as splitting a sync session. For example, a sync session covering 1 million records is still a single sync session, even though Mobio processes it in multiple chunks.

Configure the Sync Schedule

• Manual sync: Data is synchronized when you enable synchronization in the UI or when data is pushed via API/ETL
• Periodic Sync: The system automatically synchronizes data from the source according to a schedule
• Select Sync Schedule and Sync time:

Turn On Auto re-sync if an error occurs (optional)

When turned on, the system will automatically re-sync if the previous synchronization error occurs. This feature only applies to the Snapshot mechanism.

Set Up a Trace Key (optional, but strongly recommended)

The Trace Key helps identify the source record and match the processing results in the tracking log.

• Under Information used as the Trace Key, select data columns from the source table or use default values. If multiple columns are selected, their values will be concatenated using a special character.
• Mobio shows a preview of how the value will display.

Configure Sync Result Notifications (optional)

• Select the Contact Information (Mobio user account) that will receive notifications.
• Select the trigger events to send notifications:
  • Change Connection Status: Notification when the data source connection status changes.
  • Change Sync Session Status: Real-time monitoring of data sync sessions.
  • Sync session with failed records: Early detection of sync issues. Select Notification Conditions:
    • When the synchronization session contains failed records
    • When the percentage of failed records reaches a particular threshold
• Once you’ve finished all configuration, click Save to activate the Connector.

4. Frequently Asked Questions (FAQ)

• Q: If my source database is Oracle, can I choose to run Streaming?
  • A: No. Mobio enables features based on each source database’s protocol. For example, Oracle currently only supports the Snapshot mechanism. HTTP API Connectors only support Streaming.

5. Next Steps

Once your Connector setup is complete, monitor the daily volume of incoming data in the Reports area. Continue to the next section: Monitor Sync Reports & Troubleshoot Issues