Connect Salesforce data to Cordial to trigger personalized email, SMS, and mobile app messages from real-time customer and product updates, so campaigns react to behavior faster.
• Salesforce objects and fields (for example, Lead, Contact, Account, and custom objects) are mapped to Cordial profiles, including identifiers, segmentation attributes, and consent-related fields.
• Change-driven syncs transfer created and updated records from Salesforce to Cordial as deltas, with timestamp-based filtering to avoid full re-exports.
• Behavioral and commerce events (such as signup, preference changes, and key lifecycle milestones) are routed to Cordial as event payloads used for trigger-based orchestration.
• Email, phone, and device identifiers are normalized and de-duplicated during ingestion so Cordial can resolve identities across email, SMS, and mobile app messaging.
• Cordial-generated engagement signals (for example, message sent, delivered, opened, clicked, unsubscribe, and bounce) are written back to Salesforce as activities or custom records when required.
• Sync jobs log run status, record counts, and failed payloads, and retries handle transient API errors with idempotent upserts to prevent duplicates.
.png)
We map Salesforce fields to Cordial profiles and keep them updated via API or scheduled sync so personalization tokens, segments, and send rules stay accurate.
Yes – we pass key events like sign-ups, purchases, browsing, or support actions into Cordial to launch journeys, branching logic, and message timing automatically.
Common write-backs include subscription status, SMS consent, campaign engagement, and last message timestamps, so Sales and Support see the latest customer context.
Yes – we structure data, IDs, and preference centers to support multiple locales, brands, and permission rules without mixing audiences or breaking compliance.
We enforce one consent source, sync updates both ways, and log changes so Cordial sends only to customers with valid permissions.






