Connect Magento (Adobe Commerce) with Friendbuy to run referral and loyalty-driven marketing with advocate and friend flows, promo codes, rewards attribution, widgets, and fraud controls.
• Friendbuy referral widgets and tracking scripts are served on Magento storefront pages, and session identifiers are persisted to associate an advocate click with a referred friend visit and checkout.
• Magento customer identifiers and email are mapped to Friendbuy profiles to support advocate and friend linking across logged-in and guest checkouts, with deduplication rules applied where available.
• Order events (placed, paid, shipped, canceled, refunded) are sent from Magento to Friendbuy via API or webhooks, and event timestamps and currency values are normalized for attribution.
• Friendbuy promo codes and campaign identifiers are captured from Magento carts and orders, then stored alongside order IDs to validate incentive eligibility and prevent double rewards.
• Reward approvals are gated by configurable validation logic (return window, partial refunds, order status), and reversals are posted back to Friendbuy when downstream status changes occur.
• Referral and reward actions are logged with request/response payloads, retry logic handles transient failures, and idempotency keys prevent duplicate event processing.
.avif)
We map customer identity, order IDs, statuses, and discount usage so Friendbuy can approve, reverse, or delay rewards based on real Magento events.
Typical triggers include order placed, invoice paid, shipment, refund, and cancellation, with rules set to match your reward approval window and return policy.
Yes, we align Friendbuy promo codes and widget placement with Magento store views, currencies, and locales, so each market can run its own referral logic.
We use Friendbuy fraud controls and add Magento-side checks such as customer matching, order validation gates, and reward holds until eligibility conditions are met.
Track referral source, advocate and friend IDs, code usage, reward cost, and post-purchase events, then tie them to revenue for clean attribution.