Skip to main content
Talk to an expert
Emarsys logo

Emarsys integration for ecommerce marketing

Market with confidence using real customer data and signals. iWeb connects your commerce platform to Emarsys so that customer events, preferences and consent flow bidirectionally with clear ownership and observability. Your marketing team builds segments on live data; suppression and unsubscribe rules are enforced everywhere. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: marketing connector, CRM plugin, app, customer data integration.

EmarsysiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Emarsys integration gives you.

Marketing campaigns triggered by real data

Campaigns in Emarsys are built on live purchase history, browse behaviour and customer attributes from your ecommerce platform rather than stale exports. Segments are accurate and responsive to customer actions.

Suppression and consent respected everywhere

When a customer unsubscribes or updates their consent preferences in Emarsys, the commerce platform knows not to send further marketing material. The customer experience stays consistent across all channels.

Transactional messaging reliability

Order confirmations, shipping notifications and return authorizations are sent via Emarsys with clear audit trails and fallback behaviour if a channel fails. Customers receive the right message at the right time.

Reduced customer duplicate and identity confusion

Customer records are matched and merged across commerce and Emarsys using a documented identity strategy. One customer sees one consistent contact record and messaging history.

Observability and exception handling

Failed events, stale segments, broken consent flows and missed campaign sends are visible in dashboards and trigger alerts. Marketing and commerce teams can resolve issues before they affect customer experience.

02 · When it's worth it

Where a Emarsys integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Capture purchase and browse events to feed Emarsys segmentation and campaign triggers
Sync customer contact and preference data bi-directionally to keep contact records aligned
Push suppression lists and unsubscribe events from Emarsys back to the commerce platform
Trigger transactional messages (order confirmation, shipping update, abandoned cart) via Emarsys
Build dynamic segments in Emarsys based on real-time ecommerce behaviour and product affinity
Manage customer consent and marketing preferences with enforcement across channels
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Event capture granularity

The by default integration may not capture every custom or behavioural event your ecommerce team needs. You may need to extend event schemas or add real-time tracking beyond standard purchase and cart events.

Transactional message routing

Emarsys does not by default determine whether a transactional email (invoice, shipping notification) should go via email, SMS or push. You need to configure routing rules and test fallback behaviour when a contact has no SMS number.

Consent and GDPR enforcement

Emarsys handles consent storage but does not automatically enforce it across all downstream channels. You must map consent logic to your commerce platform and define who is responsible for GDPR checks at send time.

Segment latency and activation

Segments built in Emarsys may have a delay of minutes to hours before they activate. Real-time personalization on the storefront requires a separate, lower-latency data connection or pre-computed segments.

Multi-brand and multi-locale handling

If you operate multiple brands or regions, Emarsys may require separate workspaces or careful segmentation logic. Consolidating customer data across brands while respecting regional preferences can require custom configuration.

04 · The real work

Many teams discover too late that unsubscribe events from Emarsys do not always flow back fast enough to stop the commerce platform or OMS from sending a duplicate message, creating a customer complaint and compliance risk.

05 · Where it sits

Where this integration sits in your estate.

Emarsys holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

No platform lock-in. We integrate Emarsys with the commerce core you already have, or the one you are moving to.

System of record
Source / owner
Emarsys
Customer experience platform for marketing automation, segmentation and messaging orchestration
  • Marketing consent and preference state
  • Email, SMS and push message send and delivery
  • Campaign and segment definitions for marketing activation
  • Customer profile enrichment for marketing use
  • Unsubscribe and suppression list management
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Customer account identity and core contact record
  • Purchase, browse and product affinity events
  • Transactional message triggers (order, shipment, return)
  • Commerce-side suppression enforcement and GDPR checks
  • Real-time personalization rules on the storefront
Connected neighbours
Integration layer
ERP
Customer account and credit data flows to Emarsys for governance; order data backs Emarsys segmentation
Integration layer
OMS
Transactional event triggers (shipment, return, RMA) flow to Emarsys for messaging; suppression comes back to OMS
Integration layer
Data warehouse
Emarsys can send campaign performance and engagement events to the warehouse for analytics and attribution
Integration layer
Search and merchandising
Emarsys segments can be exported to personalize storefront search results and product recommendations in real time
Integration layer
Payments
Customer payment method and transaction history inform Emarsys risk scoring and retention campaigns
Integration layer
Loyalty or CDP
If you have a separate CDP, Emarsys acts as an execution layer for campaigns and messages triggered by the CDP
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (order and customer account synchronisation)
  • OMS (order fulfillment and transactional messaging triggers)
  • PIM (product data for catalogue and recommendation rules)
  • Search and merchandising (segment-driven personalisation rules)
  • Payment platform (for reconciliation of customer financial data)
  • Data warehouse (for analytics on campaign performance and customer behaviour)
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into EMARSYS & COMMERCE
←From EMARSYS
↔BOTH WAYS
Customer events and profiles: Purchase orders, product views, cart abandonment and customer account changes flow from the commerce platform into Emarsys as events and contact records
Emarsys uses these to fuel segmentation, journey orchestration and campaign personalization.
Consent and preference signals: Customer consent status, marketing preferences and channel subscriptions move from the commerce platform into Emarsys so that messaging rules respect customer choice and regulatory requirements.
Suppression and unsubscribe events: When a customer unsubscribes from Emarsys or is added to a suppression list, that signal flows back to the commerce platform to prevent further marketing material being sent.
Campaign and segment membership: Emarsys segments and campaign membership can be passed back to the commerce platform for use in personalization rules, discount codes or customer experience rules on the storefront.
Contact enrichment and identity resolution: Customer email, phone, account ID and profile attributes sync in both directions so Emarsys and commerce stay aligned on who the customer is and what they prefer.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design the event and customer data architecture

    We map out which events (purchase, cart, browse, returns) flow from your commerce platform into Emarsys, define the payload schema, and set latency and retry expectations. We document who owns the event taxonomy.

  2. 02
    Build the bidirectional sync for contacts and consent

    We set up the two-way flow of customer email, phone, account ID, preferences and consent status between your commerce platform and Emarsys, with clear rules for who wins on conflict and how often sync runs.

  3. 03
    Implement transactional messaging routing

    We configure Emarsys to receive transactional triggers from your commerce or OMS platform, route messages to the right channel (email, SMS, push) based on preference and availability, and provide audit logs for every send.

  4. 04
    Set up suppression and unsubscribe propagation

    We ensure that suppression lists, unsubscribe events and preference changes flow from Emarsys back to your commerce platform in near-real-time so that marketing stops immediately when a customer opts out.

  5. 05
    Deliver monitoring and runbooks

    We install dashboards showing event throughput, contact sync lag, failed sends and segment staleness. We document runbooks for common issues so your team can resolve failures independently.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataCustomer contact record (email, phone, account ID, name)
Source / ownerShared: commerce platform owns customer account; Emarsys owns marketing-specific attributes
Maintained byIntegration sync runs on a cadence; either system can update core fields
NotesIdentity resolution must be documented so conflicts are predictable and bidirectional sync does not loop.
DataCustomer consent and marketing preferences
Source / ownerEmarsys holds the canonical preference state for marketing consent; commerce platform holds consent for account and privacy settings
Maintained byEmarsys owns marketing permission; commerce owns account privacy; sync must respect both
NotesEnforcement happens at send time; who checks consent before every message must be clear.
DataBehavioural events (purchase, browse, cart, return)
Source / ownerCommerce platform is the source of truth; Emarsys is the consumer
Maintained byCommerce platform captures and sends events; Emarsys ingests and expires them after retention window
NotesEvent schemas and retention periods must be owned and documented so that segments are built on clear definitions.
DataSuppression lists and unsubscribe records
Source / ownerEmarsys is the system of record for marketing suppression; commerce platform must enforce it for transactional and promotional sends
Maintained byEmarsys manages list membership; commerce platform checks list before message send
NotesSync latency must be defined so commerce knows how stale the suppression list can be at any given moment.
DataSegments and audience membership
Source / ownerEmarsys owns segments used for campaign activation; commerce owns segments used for storefront personalization
Maintained byEmarsys builds and maintains marketing segments; commerce may build its own lower-latency segments
NotesIf segments are exported from Emarsys back to commerce, staleness and refresh cadence must be defined to avoid false personalization.
DataTransactional message triggers and routing
Source / ownerShared: commerce or OMS owns trigger logic; Emarsys owns delivery and channel routing
Maintained byCommerce sends trigger; Emarsys routes to channel and retries on failure
NotesFallback behaviour when Emarsys is down or a channel is unavailable must be pre-defined so customers are not left without critical messages.
10 · Experienced integrator

Built this before

iWeb has integrated Emarsys into commerce estates alongside OMS, ERP and CDP systems. We understand how to architect event flows, keep customer identity consistent, and ensure that suppression and consent rules are enforced uniformly across marketing and transactional sends.

We design event pipelines so that behavioural data (purchase, browse, cart, return) flows into Emarsys with the latency and fidelity your marketing team needs for accurate segmentation.
We implement bidirectional sync for customer contact records and consent so that unsubscribes, preference changes and GDPR requests propagate cleanly without creating duplicate records or stale suppressions.
We configure transactional message routing so that order confirmations, shipping updates and returns are sent via Emarsys with clear fallback behaviour if a channel fails or the platform is unavailable.
We know how Emarsys fits alongside your OMS and ERP so that transactional triggers are reliable and campaigns respect customer data that lives in other systems.
We build monitoring and runbooks so that your team can see stale segments, failed events, suppression lag and identity conflicts at a glance and resolve them before they affect customer experience.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify that purchase events flow into Emarsys within 5 minutes and that segments built on purchase behaviour match commerce transaction records.
Confirm that when a customer unsubscribes in Emarsys, the commerce platform receives the suppression update and stops sending marketing email within 15 minutes.
Test that transactional triggers (order confirmation, shipping) flow from OMS to Emarsys and are sent via the correct channel based on customer preference.
Validate that customer identity resolution between commerce account ID and Emarsys contact ID is deterministic and has no duplicates or orphans.
Check that Emarsys is down, a fallback message route (or logging for manual send) activates so transactional messages are not silently lost.
Confirm that suppression list and consent flags sync bidirectionally and that no customer sees conflicting messaging across commerce and Emarsys sends.
Verify that segment membership exported from Emarsys to commerce for personalization is fresh enough that storefront experience is not stale or misleading.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Lost or delayed events from commerce

If the event pipeline from commerce to Emarsys breaks or backs up, campaigns may be built on stale customer behaviour and segments become inaccurate. This usually happens when network timeouts or API rate limits are not monitored.

Duplicate or conflicting customer records

If identity resolution between commerce and Emarsys is weak (e.g. matching on email alone when email changes), customers end up with multiple contact records. Suppression lists then only cover one identity and messages keep flowing.

Suppression and consent drift

If unsubscribe events from Emarsys do not sync back to commerce reliably, or if there is a delay, customers who opted out still receive messages from transactional or promotional systems. GDPR breach risk rises quickly.

Transactional message failures go unnoticed

When order confirmations or shipping notifications fail to send via Emarsys, there is no automatic fallback to send them via another channel. Customers never receive critical updates and support teams do not know why.

Segment latency creates personalization blind spots

If segments in Emarsys take 30 minutes to update but your storefront tries to personalise based on real-time segments, the experience is inconsistent or uses stale data. Expectations between marketing and ecommerce teams misalign.

Multi-brand data leakage or consolidation failure

If you run multiple brands but Emarsys workspaces are not carefully isolated, customer data can leak across brands or consolidation logic can incorrectly merge separate customers. This damages both privacy and campaign accuracy.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Emarsys integrations.

How do we capture real-time purchase and browse events into Emarsys without creating latency on the storefront?

Events are typically sent asynchronously via an event queue or middleware so that commerce request processing is not slowed. iWeb ensures the queue has retry logic and monitoring so that no events are lost.

What happens if Emarsys is down when we try to send a transactional message?

You must have a fallback plan pre-defined. This usually means either re-trying the send within a time window, using a secondary email provider, or logging the event for manual review. iWeb sets up that fallback logic and observability.

How do we prevent duplicate customer records between commerce and Emarsys?

A documented identity strategy is essential. Usually commerce account ID is the golden key; email or phone are secondary. iWeb implements matching logic and handles the case where a customer changes email but keeps the same account.

If a customer unsubscribes in Emarsys, how long does it take for the commerce platform to stop sending them marketing email?

Sync latency depends on the integration design. iWeb typically implements a near-real-time flow so that unsubscribe events propagate within minutes, and a periodic full sync as a safety check.

Can we use Emarsys segments to personalize the storefront in real-time?

Not directly, because Emarsys segments have a latency of minutes to hours. You can either export low-latency segments from Emarsys back to commerce, or build your own real-time segments in the commerce platform and sync them to Emarsys for campaign use.

How do we handle consent and GDPR compliance across Emarsys and our commerce platform?

Emarsys stores the consent state, but enforcement happens in your commerce platform and OMS when deciding whether to send a message. iWeb documents who is responsible for checking consent at each stage and ensures audit trails are available.

What if we have multiple brands or regions? Do we need separate Emarsys workspaces?

Usually yes. Separate workspaces make it easier to keep brand and regional data apart and apply brand-specific messaging rules. iWeb can design a single integration that populates multiple Emarsys workspaces from a unified commerce platform, with clear segmentation logic.

How does Emarsys handle customer phone numbers and SMS messaging?

Phone numbers flow from the commerce platform into Emarsys as a contact attribute. Emarsys can then send SMS to customers who have opted in. iWeb ensures that phone number validation, opt-in tracking and SMS consent are synchronized.

What data do we send to Emarsys and what stays in the commerce platform?

Typically you send customer contact, account ID, purchase history, preferences and consents to Emarsys. You keep pricing, inventory, fulfillment and financial data in commerce and ERP. iWeb documents this boundary clearly so there is no confusion.

Can Emarsys send campaign data or segment membership back to the commerce platform for personalization or discount automation?

Yes. Emarsys can export which customers are in a segment, and that data can be used by the commerce platform to show personalized banners, apply discount codes, or adjust product recommendations. iWeb implements this reverse flow and manages the latency.

How do we monitor whether events are flowing correctly into Emarsys?

iWeb sets up dashboards showing event throughput by type, latency, retry failures and stale events. You can see at a glance if purchase events are being captured and if Emarsys is falling behind.

What happens if customer data conflicts between Emarsys and the commerce platform?

iWeb defines conflict resolution rules upfront. Usually the most recent write wins, or the system of record is pre-selected (e.g. commerce owns phone, Emarsys owns marketing preference). Those rules are documented and applied consistently.

Can we use Emarsys to send push notifications to app users?

Yes, if your commerce platform captures app user IDs and passes them to Emarsys as a contact attribute. Emarsys can then send push notifications to devices. iWeb ensures device ID management and opt-out handling is clear.

How often should we do a full resync of customer data between commerce and Emarsys?

iWeb recommends a daily or weekly full sync as a safety check, with incremental syncs running more frequently. The cadence depends on data volatility and tolerance for stale segments.

Next step

Have a Emarsys integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →