Data CloudIntermediatecrm-connectorsyncincremental
Map Salesforce CRM Connector incremental sync behavior
Real World Scenario
CRM updates are delayed 6 hours in unified profiles causing agents to see stale case counts.
Expected Answer
• Understand connector sync frequency and object inclusion scope
• Prioritize high-change objects for more frequent sync
• Use Data Actions for operational real-time needs vs batch connector
• Monitor sync job failures in setup audit logs
• Document lag SLAs per object for consumers
• Fallback messaging in UX when data may be stale
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Understand connector sync frequency and object inclusion scope Also consider: Prioritize high-change objects for more frequent sync In practice: Use Data Actions for operational real-time needs vs batch connector Balance speed of delivery with maintainability.
Architect Perspective
CRM Connector is batch-oriented—do not assume CRM-real-time for activation-critical attributes.