The Security Settings page in SAP Emarsys is a critical administrative interface accessible only to Account Owners, allowing them to configure security levels for account access and data management. According to the official SAP Emarsys documentation, the correct answers are A (Set up IP access control) and B (Define the permitted email domains). Below is a detailed explanation of each option, validated against Emarsys resources, to clarify why these two are correct and the others are not.

A . Set up IP access control:

Verified Answe r: Correct.

Account Owners can configure IP access control on the Security Settings page to enhance account security. This feature restricts login access to approved IP addresses, requiring two-step authentication for logins from unrecognized IPs. The documentation states, 'Set up IP access control: This is an optional, but highly recommended, security feature that requires two-step authentication for all login attempts from unrecognized IP addresses' (reference: 'Security settings:: Your account Security Settings,' updated November 12, 2024). When enabling this feature, Account Owners can define allowlisted IP addresses or ranges, ensuring that users logging in from these IPs can use only their username and password, while others must complete additional verification. This action is a core capability of the Security Settings page, making option A correct.

B . Define the permitted email domains:

Verified Answe r: Correct.

Another key action available to Account Owners on the Security Settings page is defining permitted email domains. This setting ensures that all users in the account have email addresses from approved domains, as Emarsys only sends invitation emails and security-related communications (e.g., password resets) to these domains. The documentation confirms, 'Define the permitted email domains: All the users in your account must have valid email addresses that belong to a domain listed here' (reference: 'Security settings:: Your account Security Settings,' updated November 12, 2024). At least one domain must be specified (e.g., the Account Owner's domain), and multiple domains can be added as needed. This is a fundamental security configuration task exclusive to the Security Settings page, validating option B.

C . Create external events:

Verified Answe r: Incorrect.

Creating external events is not an action performed on the Security Settings page. External events in SAP Emarsys are used to trigger automated actions (e.g., emails or program entries) based on data imports or API calls, and their setup occurs in the Automation Center or via API configurations, not under Security Settings. The documentation specifies that external events are managed through 'Automation > External Events' or API integration settings (reference: 'External Events Setup,' updated October 2024), and the Security Settings page focuses solely on access and data management controls (e.g., IP restrictions, email domains, API credentials). Thus, this action is outside the scope of the Security Settings page, making option C incorrect.

D . Deactivate users:

Verified Answe r: Incorrect.

Deactivating users is an administrative task performed on the User Management page, not the Security Settings page. Account Owners can deactivate user profiles to prevent login access (e.g., if credentials are compromised) by navigating to Management > User Management > Users, selecting a user, and using the deactivate option. The documentation states, 'As Account Owner, you can also edit user profiles on the User Management page, as well as deactivate and reactivate them' (reference: 'Creating and managing users,' updated June 10, 2024). While security-related, this action is distinct from the configurations available on the Security Settings page, which focuses on account-wide settings rather than individual user management, disqualifying option D.

Additional Context: The Security Settings page also allows other actions, such as creating API credentials and WebDAV users, or setting up Keyring for SFTP imports (reference: 'Security settings:: Your account Security Settings,' updated November 12, 2024). However, the question limits the correct answers to two, and options A and B are explicitly highlighted as primary tasks in the documentation. Options C and D, while relevant to broader account administration, do not align with the specific functionalities of the Security Settings page.

Conclusion: The actions an Account Owner can perform on the Security Settings page include setting up IP access control (A) and defining the permitted email domains (B), as these are core security configurations explicitly supported by this interface in SAP Emarsys.

If new contacts don't appear in the Database Growth widget:

Option A: Correct. The widget updates periodically (often daily), so a delay of up to 24 hours is possible.

Option D: Correct. If the opt-in field isn't TRUE, contacts may not count as 'available' for marketing.

Option B: Incorrect. Upload volume doesn't inherently block updates.

Option C: Incorrect. The widget includes manual uploads, not just auto-imports.

The SAP Emarsys Help Portal under 'Database Growth' explains update timing and opt-in impact.

A -1 audience size in Digital Ads indicates:

Option D: Correct. The audience is still being processed by Facebook, searching for matching profiles, and the size isn't finalized yet.

Option A: Incorrect. Insufficient contacts would show a low number, not -1.

Option B: Incorrect. Multiple identifiers don't inherently prevent size reporting.

Option C: Incorrect. A failed transfer would show an error, not -1.

The SAP Emarsys Help Portal under 'Digital Ads' explains -1 as a processing state.

Deleting a contact in SAP Emarsys:

Option A: Correct. Purchase data in Smart Insight is removed as it's tied to the contact.

Option B: Correct. The contact is removed from all contact lists in Emarsys.

Option C: Correct. Rewards data in the Loyalty module is deleted with the contact.

Option D: Incorrect. Deletion in SAP CDP depends on integration settings and isn't immediate.

Option E: Incorrect. Past campaign data remains for reporting; only future sends are affected.

The SAP Emarsys Help Portal under 'Contact Management' details deletion effects.

For omnichannel personalization extending from Web Channel:

Option B (Mobile Engage): Correct. Mobile Engage requires an external ID to link mobile app users to webshop contacts for consistent personalization.

Option A: Incorrect. Digital Ads uses segments, not external IDs directly.

Option C: Incorrect. SMS uses phone numbers, not external IDs.

Option D: Incorrect. Web Channel itself uses external IDs but isn't an extension target here.

The SAP Emarsys Help Portal under 'Mobile Engage' specifies external ID for contact matching.

To extend your webshop personalization experience to another channel and provide an omnichannel experience to your customers, it's essential to understand how Emarsys identifies contacts across different channels. Emarsys offers two primary methods for explicit contact identification:

Email Address: This method uses the visitor's email address for identification.help.emarsys.com+1help.emarsys.com+1

External ID: This method utilizes a unique customer ID or user ID that your website uses to identify registered users.

It's crucial to use the same identification method consistently across all platforms, including your website and mobile applications, to ensure a seamless personalization experience.help.emarsys.com

Channel Analysis:

A . Digital Ads: This channel typically uses cookies and other tracking mechanisms for user identification and does not require an external ID.

B . Mobile Engage: For mobile applications, Emarsys requires the use of an external ID to identify users. This ensures that the personalization experience is consistent across both your website and mobile app. Therefore, to extend your webshop personalization to your mobile app, you should use an external ID as the identifier. help.emarsys.com

C . SMS: This channel primarily uses phone numbers for contact identification and does not require an external ID.

D . Web Channel: For website interactions, Emarsys can use either the email address or an external ID for contact identification.help.emarsys.com

Summary:

To provide an omnichannel experience by extending your webshop personalization to another channel, Mobile Engage requires the use of an external ID for contact identification. This ensures consistent and personalized interactions with your customers across both web and mobile platforms.