Real-time and batch integration flows

Learn how the Reltio–Veeva Vault CRM integration supports both real-time and batch data synchronization, and when to use each mode.

Veeva Vault CRM integration supports two distinct synchronization flows: real-time and batch. Each mode uses a different trigger and processing method to keep healthcare professional (HCP), healthcare organization (HCO), location, and relationship data aligned between Reltio and Veeva Vault CRM.

Real-time flows use event-driven triggers to send data as soon as changes occur.
Batch flows process larger volumes of records on a scheduled basis, often for initial loads or periodic updates.

The integration supports bi-directional data flow — from Reltio to Veeva and from Veeva to Reltio — using prebuilt recipes and the Reltio Integration Hub (RIH).

Real-time integration from Reltio to Veeva Vault CRM

Real-time synchronization enables low-latency data exchange from Reltio to Veeva Vault CRM. It uses event-driven triggers to send entity updates — such as HCP changes or affiliation updates — as soon as they occur in the Reltio.

In this mode, the system listens for changes on streaming queues (like AWS SQS or Azure Topic), and the integration recipes process updates in small batches.

Use real-time sync when:

You need immediate propagation of field changes, such as license status or address updates
You want to reflect approved DCRs in both systems with minimal delay
You need up-to-date data in customer-facing applications used by field teams

The following characteristics define how real-time mode operates:

Trigger type: Event-driven

Processing method: micro-batch, depending on configuration

Direction supported: Reltio to Veeva Vault CRM

Near real-time integration from Veeva Vault CRM to Reltio

Near real-time synchronization enables fast data exchange from Veeva Vault CRM to Reltio. It uses Vault Direct Data APIs to detect changes and send updates, such as newly created HCPs, affiliation changes, or profile edits, to Reltio for enrichment or master data alignment. The recipe uses the incremental files provided by the Direct Data APIs. Every 15 minutes, Direct Data API generates an Incremental file which contains the set of data which changed in Vault CRM during this 15-minute interval.

The records available in the incremental files are processed in small batches by recipes in the Reltio Integration Hub (RIH).

Use the near real-time sync when:

You need to reflect Veeva originated changes, such as address or license updates, in Reltio quickly
You want to raise DCRs in Reltio based on edits made in Vault CRM
You require near real time enrichment of HCP or HCO data initiated from Vault CRM workflows

The following characteristics define how real-time mode operates:

Trigger type: Scheduled pull every 15 minutes by default (depending on Vault CRM configuration)

Processing method: Small batch

Direction supported: Veeva Vault CRM to Reltio

Batch integration

Batch synchronization enables scheduled, high-volume data transfers between Reltio and Veeva Vault CRM. It's commonly used for initial loads, large updates, or recurring data refreshes where immediate delivery is not required.

In batch mode, the integration runs on a predefined schedule (such as daily or weekly) and processes data in bulk. This flow supports record grouping by entity type (HCP, HCO, Location) and can handle transformations and mappings during export or import.

Use batch sync when:

You need to load a large number of records, such as onboarding a new country or product line
You want to periodically refresh HCO–HCO hierarchies or affiliations
You're synchronizing reference data or relationship updates on a defined cadence

The following characteristics define how batch mode operates:

Trigger type: Scheduled

Processing method: Bulk (by job or entity type)

Direction supported: Reltio ↔ Veeva Vault CRM

Cloud-based event queue support

If you're using real-time synchronization from Reltio to Veeva Vault CRM, the integration relies on external event delivery through cloud-based messaging services. The table below lists supported queue types by provider and their current production support status.


Cloud Provider	Supported Queue Type
AWS	SQS
Azure	Topic
GCP	Pub/Sub

These queues deliver change events from Reltio to the Integration Hub. The recipes subscribe to those queues and process the messages using configured logic.

For Veeva Vault CRM to Reltio flows, changes are typically detected using Vault CRM extract jobs or APIs triggered in scheduled intervals.

Choosing the right flow

Use the table below to compare when each mode is best suited:


Criteria	Real-time integration (Reltio → Veeva)	Real-time integration (Veeva → Reltio)	Batch integration
Trigger type	Event-driven	Event-driven or scheduled poll	Scheduled
Data volume	Small, continuous updates	Small, continuous updates	Large, periodic updates
Latency requirements	Sub-minute	Sub-minute to minutes	Minutes to hours
Ideal for	Operational sync, field changes	Vault-driven changes to HCP, HCO, affiliations	Initial loads, hierarchy sync
Error recovery	Retry, alert logic	Retry, alert logic	Re-run batch job
Cloud dependencies	Requires queue configuration	Depends on Vault API or event model	Requires file or API export
Direction supported	Reltio → Veeva	Veeva → Reltio	Reltio ↔ Veeva

Unify and manage your data