Connect Salesforce order and customer account data with Yotpo Loyalty to run points, VIP tiers, referral rewards, and redemption rules that update reliably after every purchase.
• Customer records are matched between Salesforce and Yotpo Loyalty using stable identifiers (typically email and an external customer ID), with conflict handling based on a defined system of record.
• Order and line-item data from Salesforce is synchronized to Yotpo to trigger earning rules, tier evaluation, and referral attribution based on purchase events and customer status.
• Refunds, cancellations, and partial returns are propagated as order adjustments so points reversals and tier recalculations can be applied against the original transaction context.
• Loyalty state such as points balance, VIP tier, rewards, and redemption events is written back to Salesforce as mapped objects/fields for visibility in customer accounts and service workflows.
• Coupon or reward identifiers generated in Yotpo are mapped to Salesforce promotion constructs or custom fields so redemptions can be validated and traced to a specific reward.
• Event processing is logged with timestamps and payload references, and failed syncs are retried with idempotent keys to prevent duplicate points or duplicate reward issuance.
.png)
We map Salesforce customer and order events to Yotpo Loyalty so points and tier logic update from purchase, cancellation, and return signals. This reduces mismatched balances and late rewards.
Yes, tier movement can be driven by Salesforce lifecycle events and spend thresholds sent to Yotpo. Rules can also account for refunds so customers do not keep unearned tier status.
Typically we sync customer identifiers, email, marketing consent, and key account fields, plus order totals and currency. That gives Yotpo enough context to validate referrals and apply reward rules.
It can, as long as Salesforce carries the right store, locale, and currency attributes per order and account. We align that data with Yotpo program settings to avoid cross-market point leakage.
We design idempotent event handling, consistent customer keys, and deduplication checks before writing to Yotpo. That way, retries and partial failures do not create extra points.






