Connect Salesforce with Friendbuy to run referral and loyalty programs that track advocate and friend journeys, automate rewards and promo codes, and tighten attribution and fraud controls.
• Customer profiles are mapped between Salesforce objects and Friendbuy customer records using stable identifiers (email and, where available, Salesforce Contact/Account IDs).
• Order and transaction events are sent from Salesforce-connected commerce data sources to Friendbuy to power referral attribution, reward eligibility checks, and conversion reporting.
• Advocate and referred-friend relationships are recorded in Friendbuy and related back to Salesforce via referral identifiers, allowing campaign-level attribution to be tied to CRM entities.
• Promo codes and reward states (issued, pending, approved, canceled) are synced as statused records, with ownership defined per field to prevent overwrites.
• Referral widgets and share links generate click and signup events that are captured in Friendbuy and reconciled with downstream purchases through event IDs and timestamps.
• Fraud controls apply rules on event ingestion (duplicate identities, self-referrals, velocity signals), with flagged events stored for audit and downstream handling.
• Sync jobs support incremental updates by sending deltas for changed customers and orders, and failed payloads are logged with retry and error detail for traceability.
.png)
We map Salesforce accounts, contacts, and orders to Friendbuy advocate and friend identities, then sync reward status back for end-to-end visibility. This keeps referral outcomes tied to the right customer record.
Typically orders, order items, customer identifiers, coupon usage, and channel metadata used for attribution and eligibility rules. We align fields so Friendbuy can approve rewards based on real purchase events.
Yes, we can write promo codes, reward states, and key referral events back to standard objects or custom fields. That makes it easier for Sales, Support, and Marketing to see what happened without logging into Friendbuy.
We pass the identifiers Friendbuy uses for fraud controls and enforce deduplication rules in the sync layer. This reduces double-counting when customers place multiple orders or use multiple emails.
Yes, we can segment sync logic by business unit, currency, locale, and program rules. It supports separate referral widgets, reward catalogs, and reporting per market.






