Name: Exploring the Implementation Steps in SAP Emarsys Customer Engagement
Uploaded: 2024-5-3
Duration: 351 s
Description: This video provides an overview of the SAP Emarsys Customer Engagement implementation key steps and topics you have to consider before the implementation starts.

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>This video provides an overview of the SAP Emarsys Customer Engagement implementation key steps and topics you have to consider before the implementation starts.</div></div>

Exploring the Implementation Steps in SAP Emarsys Customer Engagement

Welcome! In this video we will provide an overview of the SAP Emarsys Customer Engagement implementation steps.  We’ll cover the topics you have to consider before the implementation starts and the steps of the actual  implementation as well. So, what do you need to consider  before you start the implementation? Identify the use cases! Do you need a multi-language  or multi-currency setup? Are you considering a single  or a multi-account system?  How many brands do you plan to serve? What channels are you going  to implement now and in the future? User identification is of key importance. Are the contacts consistently  identified across channels? Ideally you have already mapped out all data sources, data warehouses and architecture including CRM systems, plugins and connectors that have  a connection to your Emarsys account.  For real-time user journeys  you will need APIs to be set.  Have you thought over all the events that will trigger user messages and journeys, in Emarsys or externally? Think about the deliverability requirements, such as email sending compliance and the DNS settings. IP warm up and timelines and key elements like domains  and dedicated reply management should also be considered. What content types will be used? Think of templates, HTML, images, fonts, and more. Also, consider the data export from Emarsys.  Will the data be fed into  a third-party BI tool? Once you have a plan for all the above,  your scoping is done and the  Implementation process can start. Before we go into the details, please note that there are a few things  only Emarsys can manage  - we mark those visually in this video. Let’s discover the milestones  of the implementation process! Configure Create Account Owner Activate Channels  Integrate Data Activate Email Sending Migrate Campaigns The first step is provisioning. To configure an Emarsys account, also called tenant, Emarsys needs some information: Tenant name: to reflect the name  of the business or company  Email configuration details:  like sender and link tracking domains Account time zone and currency User identification method  - email, customer ID, or custom field  Details for channel and advanced capabilities: for example group admin for Open Data; Loyalty related information Once the account is set up, it is time for the Account Owner creation.  Account Owners are the users  who can create and maintain  all the user profiles and permissions, as well as manage the security settings  in the account. The next step is  email channel activation: To prepare the account for email sending, Emarsys needs to know  the expected email volume, and some technical, legal and information security  contact information as well.  We are now moving to one of  the most important topics: data! Let’s start with Contact Data as it is essential for  segmentation and personalization.  Before importing or collecting contact data, the fields and unique identification  methods should be clarified. Product Data is needed to power  product-based journeys in campaigns,  such as back-in-stock scenarios.  So, you need to load product data  and a unique product identifier. Next, we have the Web Extend  data collection scripts.  These need to be deployed on the website  to track and collect web behavior data,  for example which contact  is viewing which products, which can later be used  for product recommendations. Lastly, Sales Data. This powers Smart Insight to help clients  automate the lifecycle of their marketing journeys.  Regarding data alignment, use email addresses or customer IDs  to link sales records to Emarsys contacts.  The product information must  be reconciled with sales data. How to integrate data with channels? Within Emarsys, there's a vast  technical integration ecosystem, including CSV,  API,  Web Extend, mobile SDKs,  data from SMS operators, Digital Ads, and so on. All this is documented on our Help Portal. Of course, we also offer various  options to manage data export.  The next step is enabling  account email sending. This includes deliverability and  domain related tasks and DNS warmup. The domain and DNS settings  can be done and validated in the platform  with a couple of clicks. Emarsys support will  assign the IP groups. To ensure the best deliverability results  and the right inbox placement, the planning and execution  of a proper IP ramp up is key.  Then send your first test messages. So, as soon as the account has been created, and the data is prepared, you can upload your brand’s creatives and set up the messages  in all the desired channels.  The final step is evaluating  the sending volume to provide the easiest path  to starting the email campaigns.  This might require a dedicated IP or a longer, more controlled  domain warmup process. We hope this overview helps you better understand the SAP Emarsys implementation process. Thanks for watching our introduction  to the SAP Emarsys implementation.