EMARSYS INTEGRATION
We connect online stores to Emarsys so contacts, orders, product catalogues and web behaviour feed the personalisation, automation and predictive features the platform is built for. We plan the data that should move, build the connection on the platform the store already runs on and keep it running once it is live.
In brief
Emote Digital is a digital agency in Hawthorn, Melbourne, founded in 2001. We connect eCommerce stores to Emarsys, the SAP owned customer engagement platform used by larger retailers, so contacts, sales data, product catalogues, web behaviour and consent reach the platform in the shape its automation and personalisation expect. Connections are built on the platform the store already runs on, through the Emarsys APIs, Web Extend and scheduled data feeds.
The integration
Emarsys suits established retailers with the volume and the ambition for predictive segments, personalised recommendations and automation across email, SMS, push and web.
Contacts and their fields, sales items for every order line, the product catalogue with categories and availability, web behaviour through Web Extend, consent and preferences, and campaign responses back to the store where they are useful. Each record has an agreed owner.
Smart Insight, predictive segments and recommendations only work when sales data, product data and contacts arrive in the agreed format, on schedule, with matching identifiers. The integration is built and checked around those contracts.
The connection is built on the platform the store already runs on, using the Emarsys connector where one fits the platform and custom feeds and API integrations where the catalogue, pricing or customer model needs more.
What we do
A connected set of decisions, shaped around the data contracts the platform depends on.
Map the contact, sales, product and behaviour data that should reach Emarsys, and agree who owns each record and each identifier.
Send contacts, fields and consent for each channel, with unsubscribes flowing back to the store.
Build and schedule the sales items and product catalogue feeds Smart Insight and recommendations rely on.
Implement Web Extend and the events the automation programs trigger on, with the right identifiers.
Validate feeds, place real orders and trigger real events end to end and check Emarsys, the store and the analytics agree before launch.
Watch feed runs, API failures and data quality, and keep the connection working through theme, app and platform updates.
Buyer context
A Emarsys integration has to suit the people, systems and operating conditions around it.
Emarsys programmes depend heavily on data quality, identifiers and feed schedules, and the available connectors vary by platform. We help determine where a connector is enough and where custom feeds and events earn their place.
The value of an Emarsys integration is not in sending every field. We define the data contracts the segments, recommendations and programs depend on, honour them cleanly and on schedule, and leave the store to sell and Emarsys to engage.
Takeover and improvement
We can assess the current connector or feeds, data quality and identifiers, consent handling, why segments or recommendations look wrong and whether Web Extend sends what the programs need. We can help identify what is working, what is missing and which changes deserve priority.
Talk to us
Thirty minutes on the data, the programs and what it would take to connect or fix the integration.
Approach
Formal Discovery may be appropriate for several storefronts or markets, loyalty in scope, complex catalogues or a connection that also involves an ERP or CRM.
Establish which Emarsys features the business runs or wants, how contacts, orders and the catalogue work in the store, how consent is collected and which other systems hold the same customers. Any existing connector or feeds are reviewed first.
Define the contact fields, sales item and product feed formats, identifiers, consent handling, web events and schedules each feature needs, and the checks that will prove the data is right. Connector or custom build is agreed first.
Design the sign up, preference and checkout experience around the Emarsys data, and the recommendation and personalisation placements on the store so the platform has somewhere to act.
Configure the connector or build the feeds, API integrations and Web Extend events, including scheduling, validation, queuing and retries. Formats and rules are documented so the connection remains easy to support.
Validate feeds against the Emarsys specifications, place real orders, browse real products and test consent changes end to end before the programs go live on real traffic.
Monitor feed runs, failures and data quality after launch and keep the connection working through theme, app and platform updates. Improvements follow what the programme reporting shows over time.
Questions
Contacts and fields, consent per channel, sales items for every order line, the product catalogue, web behaviour through Web Extend and custom events for automation programs. Which move is agreed in scoping.
Almost always a data issue: a feed that failed or ran late, identifiers that do not match between contacts and sales, or catalogue fields that are missing. We trace the feature back to its data and fix the source.
Consent is captured per channel with a clear statement, recorded with its source and timestamp and passed to Emarsys, and unsubscribes flow back to the store, in line with Australian spam rules.
We are platform agnostic. The connection is built on whatever the store already runs on, using a connector where it fits and building custom feeds, API integrations and Web Extend events where it does not.
Yes. Web recommendation placements can be added to product, category, cart and account pages, driven by the catalogue and behaviour data the integration provides.
Yes. We review the connector, feeds, identifiers and events, fix what is failing or mismatched and rebuild the parts that cannot meet the way the business sells.
Start a conversation
Connecting a new store, fixing feeds that keep failing or adding Emarsys to a store that already runs the business?
Book a meetingProud partners
