FAQs on Reltio–Veeva Vault CRM integration

Find answers to common questions about the Reltio–Veeva Vault CRM integration.

Integration Behavior

Does the integration support bi-directional data sync?: Yes. Data can flow from Reltio to Veeva Vault CRM and vice versa using prebuilt recipes.
Can we use both real-time and batch sync?: Yes. You can choose based on data volume and latency needs. See Real-time and batch integration flows.
What happens when records are merged in Reltio?: The integration uses the _crosswalkTree API to determine winner/loser logic and update or remove the corresponding Vault CRM records.
Does Reltio automatically reflect deletes from Veeva Vault CRM?: Yes. Based on your configuration, deletes in Vault can either remove crosswalks or set a delete date in Reltio.

Do we need a queue to use the integration?: Only if you plan to use real-time sync. For batch mode, queues are not required. Supported queue types include AWS SQS, Azure Topic, and GCP Pub/Sub.
Is the Vault CRM connector customizable?: No. The connector is managed by Reltio and versioned for compatibility. You can customize the recipes but not the connector itself.
How do we test the integration before production?: You can import the recipes into a sandbox RIH project, connect to non-production tenants, and run controlled test jobs. See Deploy and configure the Veeva Vault CRM integration recipes.

What data domains are supported?: The integration supports HCP, HCO, location, relationships, identifiers, and reference data. See Use cases and supported data domains.
Does the integration support DCRs?: Yes. You can configure the recipes to raise data change requests in Reltio when records are updated in Vault CRM.
Can we sync relationships like HCP–HCO affiliations?: Yes. The integration includes mapping support for HCP–HCO and HCO–HCO relationships.
Can we use this integration with legacy Veeva CRM (Salesforce-based)?: No. This integration is built specifically for Veeva Vault CRM. Customers migrating from Salesforce-based Veeva CRM will need to reconfigure their flows and mappings.