New account setup – Emarsys

Welcome to SAP Emarsys.

In order to configure your Emarsys tenant, we will need some key details of your desired configuration.

The following forms will help you provide us all the information we need.

Please provide the forms to your Implementation Consultant (if you have one) or open a request on the SAP for Me customer portal to send the forms to Emarsys.

Step 1: Tenant Configuration

Download and fill out the form below to begin the Email Channel activation process.
Tenant Configuration (Click to save locally.)

Please review the relevant terms and definitions:

Core/Core sandbox

Field Name	Information	Related documentation
Account Information
Emarsys Tenant name*	The name of the Emarsys Tenant
Emarsys Email Configuration
Sender domain(s) - Required	Marketing sender domain(s): At least one domain is required to be set up and configured to be used to send your marketing emails from. To ensure maximum deliverability results and reputation, we highly recommend creating a new subdomain that will explicitly be used to send emails from SAP Emarsys. For example: your website domain: www.mybrand.com your subdomain as sender domain: reply.mybrand.com The sender domain needs to be configured with certain SAP Emarsys settings. These settings include SPF, DKIM, DMARC, MX. Check the related documentation for the specific settings you need to add.	SAP Emarsys DNS settings
Sender domain(s) - Recommended	Transactional sender domain(s): Optionally, you will need to set up and configure at least one subdomain to be used to send your transactional emails from. To ensure maximum deliverability results and reputation, we highly recommend creating a new subdomain that will explicitly be used to send emails from SAP Emarsys. For example: your website domain: www.mybrand.com your subdomain as sender domain: notifications.mybrand.com The sender domain needs to be configured with certain SAP Emarsys settings. These settings include SPF, DKIM, DMARC, MX. Check the related documentation for the specific settings you need to add.	Do not use noreply@ Split marketing and transactional streams
Sender domain(s) - Recommended	Google Postmaster: Set up Google Postmaster Tools for your email sending domain(s). Google does not send back information about spam complainers to any sender, which is why Google Postmaster Tools is the only place where you can see your spam complaint rate with Gmail addresses. You can find steps on how to set it up here: Set up Postmaster Tools - Google Workspace Admin Help In Step 3: Give others access to your Postmaster Tools dashboards (Optional) you can add gdeliv@emarsys.com mailbox, so that Emarsys Deliverability team would have access to this data for your sending domain. You can remove this access at any point. In addition to spam complaint rate, Google shares other metrics that only they see. This includes email delivery error rate, domain reputation, IP reputation, authentication and such. You can find more details on the data available on the Google Postmaster Tools dashboards here: Postmaster Tools dashboards - Google Workspace Admin Help
Link domain(s)	At least one link domain is required to be setup and configured. All the tracked links in your emails will be routed via this domain. The link domain needs to be configured with a CNAME record: linkdomain-mybrand-com.emarsys.net Example: your website domain: www.mybrand.com your subdomain as link domain: link.mybrand.com CNAME record: link-mybrand-com.emarsys.net	SAP Emarsys DNS settings
Mail server for replies	MX – Mail Exchange Server - that will handle how replies to marketing/transactional emails are managed. If you want to use the Emarsys reply management (replies to emails are stored in Emarsys), use the following record: mx.eemms.net If you want to use your own reply management (replies will be sent directly to your mailboxes/mail servers), use your own mail-server record. Provide your choice and the mail server record here. If you configured your domain to use Emarsys reply management, enter`mx.eemms.net`.
Mailbox for transactional mails	To send transactional emails with Emarsys, we will need a dedicated mailbox (the part before the @ of your domain, e.g. [name]@subdomain.customer.com] for the provided sender domain. Example: sender domain: reply.mybrand.com mailbox: service@reply.mybrand.com
Additional Email Channel Configuration
Additional accountwide link tracking parameters (e.g. Google Analytics)	Emarsys provides an option to attach link-tracking parameters to all your links for all campaigns. These parameters will help to you feed external tracking tools, for example, Google Analytics. For tracking parameters that apply to every single link in every single campaign, Emarsys can configure the backend accordingly. You can provide static values as well as the following placeholders: $cname$ - campaign name $ascii_cname$ - campaign name (ASCII) $cdate$ - campaign date $cyear$ - campaign year $cmonth$ - campaign month $cday$ - campaign day $chour$ - campaign hour $clinkcat$ - link category $clinkname$ - link name $clinktitle$ - link title $pers_N$ - user’s element N (N = Emarsys Field ID) $campaign_category$ - campaign category Example: utm_medium=emailutm_campaign=$cname$_$cyear$-$cmonth$-$cday$utm_content=$clinktitle$	Link tracking for external analytics These parameters can be edited at anytime via a request on the SAP for Me customer portal.
List-Unsubscribe URL	If unsubscriptions are managed outside of Emarsys, a custom List-Unsubscribe URL is required. The list unsubscription process is part of the email header that is sent with every email. Using that customers can unsubscribe from your email without opening them. If you collect the unsubscriptions in any of your systems first before these are synchronized to Emarsys, you will need to take care of list unsubscriptions, too. A URL of your webservice that processes these unsubscriptions is required. It must contain a parameter to identify the users, and additionally, it could contain parameters that identify the campaign the unsubscription was done in. Example URL: https://www.customer.com/newsletter-unsubscribe/webservice/?contact=[field-name]&cid=$cid$&llid=$llid$ Contact=[field-name] – this is a placeholder and needs to be replaced by the corresponding identifier that you are using. cid=$cid$ - Emarsys can pull the campaign ID automatically llid=$llid$ - Emarsys can pull the launch list ID automatically In order to report these unsubscriptions back into Emarsys, 2 API calls are required: Update Contact Unsubscribe contact from campaign (to report an unsubscription back to Emarsys’ campaign reporting)
Web Extend
User identification method*	Select how you will identify users for our Web Extend tracking script on the website. You can choose between email address and any other custom information, e.g. customer ID. If email is used, Emarsys will not send PII to its servers, but the email address is hashed prior to being sent to the servers. If email is used, Web Extend requires the ‘setEmail’-command to identify users. If you intent to use any other identification information (custom field), the following criteria must be met: A custom field must already be there (e.g. customerID, CRM_ID, contact_key, …) This contact data information must be present for all users If a cutom field (not email) is used, Emarsys requires the `setCustomerId` command to identify users. You must not mix both methods (setEmail, setCustomerId) within one integration. Even though switching the method is technically possible, we do not recommend it as your collected data will be lost.	Web Extend User identification: https://help.emarsys.com/hc/en-us/articles/360005884453-identifying-users-with-web-extend setEmail API command setCustomerId API command Create custom fields: https://help.emarsys.com/hc/en-us/articles/115004634689-End-user-guides-Creating-custom-fields
Custom Field for User Identification*	Custom Field that will be used as contact identifier. The field needs to be created prior to this configuration. Only provide the field name if Customer Field has been chosen as user identification method above
Email Channel Options

Advanced capabilities

Field Name	Information	Related documentation
Open Data
Group Admin	Please provide the email address of the group administrator/the manager that will act as the owner of the Google project. Make sure to use an email address associated with a Google account.	https://help.emarsys.com/hc/en-us/articles/360000176214-End-user-guides-Open-Data-End-user-guide

Industry Accelerator - Loyalty

Field name	Information
Customer Identification	What key do you use to identify customers? You can select between email (clear text) or any custom field from the SAP Emarsys platform that holds the corresponding customer identifier.
Customer field for user identification	Custom Field that will be used as contact identifier. The field needs to created prior to this configuration. Only provide the field name if "Customer Field" has been chosen as User identification method
Wallet design specifics Fill out the below part if you intend to use the SAP Emarsys Loyalty wallet.
Wallet color	#Hexcode of primary wallet color
Wallet style	Choose between solid color or gradient:
Wallet secondary color	If you have selected the gradient color, select your secondary color from the same family
CTA desktop position	Decide on the Wallet’s position for desktop devices
CTA mobile position	Decide on the Wallet’s position for desktop devices
CTA text	Decide on the text for new customers to join the Loyalty program
Wallet logo	Provide an Image file, if you want to use your own symbol for the Loyalty wallet. SVG format. Please attach to the SAP for Me case

Once you've filled out the form, contact your Implementation Consultant (if you have one) or open an Incident from the SAP for Me customer portal to get your account configured. Please make sure to set the component to CEC-EMA.

As a first step, the EMARSYS TENANT CONFIGURATION from the Core section is required, so please ensure that this information is sent to Emarsys as soon as possible.

If you haven’t decided on the specifications for the additional channels or add-ons, you’re free to raise subsequent tickets from the SAP for Me customer portal at any time.

Step 2: Email Channel activation

In order to activate the email channel, we need some more information from you. Please follow the steps below.

Download and fill out the form below to configure further details of your services.
Email Channel Activation (Click to save locally.)

Please review the relevant terms and definitions here:

Email Channel activation

Field Name	Information	Related documentation
EMAIL ACCOUNT CREATION
Emarsys Tenant name	The name of the Emarsys Tenant
Account Type	Choose one of the following: Small volume – for senders that usually do not send more than 1 million emails per day. High volume – for senders that often send more than 1 million emails per day.
Region	Select the region from which you are sending your emails (main region). Select one of the following: AMER EMEA APAC
ACCOUNT INFORMATION AND CONTACT LIST
Client technical contact	Provide the name and the email address of your main contact responsible for technical questions related to the Email Channel.
Client legal contact	Provide the name and the email address of your main contact responsible for legal questions around email marketing.
Client InfoSec/abuse contact	Provide the name and the email address of your main contact responsible for information security and email abuse.

Once you've filled out the form, contact your Implementation Consultant (if you have one) or open an Incident from the SAP for Me customer portal to get your account configured. Please make sure to set the component to CEC-EMA.

Important: Please take into consideration that it is your responsibility to ensure that your company is compliant with regards to data and marketing. We recommend that you go through our compliance recommendations: Email compliance self-assessment.

Attachments:

SAP_EMARSYS_TENANT_CONFIGURATION.docx

SAP_EMARSYS_EMAIL_CHANNEL_ENABLE.docx

Optional Step: Multiple accounts: Asset generation

You can generate assets in freshly created accounts by transferring Automation programs and sub-assets and custom fields from a fully set up and configured account.

This functionality can be particularly useful if you intend to utilize the same marketing use cases or assets across multiple business units and prefer not to recreate them from scratch. To initiate this process, follow the instructions described on Bulk distribution of Automation programs and Distributing custom fields pages.