Connect Magento 2 with Iterable to sync customers, catalog, and events in near real time, trigger smarter email and SMS journeys, and measure revenue back to campaigns.
• Customer identity fields (email, customer ID, and phone where available) are mapped from Magento to Iterable user profiles, with deduplication handled by the chosen primary identifier.
• Commerce events such as checkout, purchase, refunds, and cart updates are sent as Iterable events with order, item, value, currency, and timestamp attributes.
• Delta-based sync logic transmits only new or changed customers, subscriptions, and key profile fields to reduce payload size and avoid reprocessing.
• Marketing consent and subscription status are mapped to Iterable lists and channels, with locale-specific preferences passed as profile attributes when present.
• Product and line item data is normalized to a consistent schema so Iterable can use category, SKU, price, and quantity in templates and event filters.
• Retries, error handling, and response logging capture failed calls, API rate-limit responses, and rejected payloads for later replay and auditability.
.avif)
We map Magento entities and events to Iterable data types, then sync via API for near real-time updates. The setup covers profiles, catalog fields, and behavioral events used for triggers.
Typical events include product views, add to cart, checkout started, purchase, refund, and subscription or consent changes. We tailor the event schema to your journeys and reporting needs.
Yes, we can pass store view, locale, currency, and region-specific consent flags into Iterable. This keeps segmentation and suppression logic consistent across markets.
We implement update and reversal logic for order edits, cancellations, and returns, so Iterable reflects the latest state. This helps avoid sending the wrong post-purchase messaging.
Yes, we send order and event identifiers that let Iterable tie message engagement to conversion outcomes. If needed, we validate the tracking end to end in GA4, too.