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.

Smart Insight in SAP Emarsys relies on sales data for analytics like Customer Lifecycle:

Option B: Correct. Daily imports are recommended because the Smart Insight dashboard updates daily, ensuring analytics reflect the latest sales data for accurate insights.

Option A: Incorrect. File size limits (e.g., 10 GB) are not the primary reason; Emarsys supports larger files via chunking if needed.

Option C: Incorrect. Product data frequency (often less frequent) is distinct from sales data needs.

Option D: Incorrect. File maintenance policies exist but don't dictate daily imports as a compliance rule.

The SAP Emarsys Help Portal under 'Smart Insight' recommends daily sales data imports for dashboard alignment.

In SAP Emarsys, the Email Campaign Update functionality allows users to apply modifications made to a template across multiple existing email campaigns that were created using that template. This ensures consistency and saves time by eliminating the need to manually update each campaign individually.

B . New elements in a template will be available for use in all campaigns once they have been distributed using campaign update.

When new elements or changes are added to a template, utilizing the Campaign Update feature distributes these modifications to all associated campaigns. This means that any new content blocks, design changes, or structural adjustments made to the template become immediately available in all campaigns linked to that template once the update is executed. help.emarsys.com

C . A network connection during a campaign update can result in a failed save attempt.

The stability of the network connection during the campaign update process is crucial. Interruptions or instability in the network can lead to failed save attempts, causing the update process to fail. In such cases, the email content remains unaffected, but the affected campaigns may not send out emails as intended. Users are advised to retry the update process or manually apply the template changes to the affected campaigns. help.emarsys.com

E . Opening a campaign with a previous template version will prompt to update the campaign.

If a campaign was created using an older version of a template and that template has since been modified, opening the campaign will trigger a prompt notifying the user of the available updates. This allows users to decide whether to apply the latest template changes to the campaign, ensuring that all campaigns can be kept up-to-date with the most recent design and content standards.

Incorrect Options:

A . A modification to the campaign template will update all batch campaigns.

This statement is incorrect because simply modifying a template does not automatically update all batch campaigns. The Campaign Update feature must be explicitly used to apply template changes to existing campaigns. Without initiating this process, the campaigns remain unchanged despite modifications to the template. help.emarsys.com+1help.emarsys.com+1

D . Changes made to a template can be reversed by performing a rollback to the previous version.

This statement is incorrect because once changes are made to a template and distributed using the Campaign Update feature, they cannot be automatically rolled back to a previous version.

Mobile Engage push token issues in SAP Emarsys:

Option B: Correct. An outdated app certificate (e.g., APNs, FCM) can invalidate tokens, preventing delivery.

Option D: Correct. An invalid personalization token in the message can cause delivery failures.

Option E: Correct. An outdated app version may not refresh tokens correctly, leading to errors.

Option A: Incorrect. Campaign criteria affect targeting, not token validity.

Option C: Incorrect. Segment criteria define recipients, not token-related delivery.

The SAP Emarsys Help Portal under 'Mobile Engage' lists these as common issues.

Below is the seventh batch of 10 questions (61-70) related to SAP Emarsys, with answers verified against official SAP Emarsys documentation as of March 07, 2025. Each question follows the requested format, including a comprehensive explanation and references to official SAP sources where applicable.

To view an engagement summary for Mobile Engage Push and SMS channels:

Option B (Campaign Analytics): Correct. Campaign Analytics provides detailed engagement metrics (e.g., sends, opens, clicks) for specific channels like Mobile Engage Push and SMS over a selected time period, such as a month.

Option A: Incorrect. Revenue Analytics focuses on revenue attribution, not channel engagement.

Option C: Incorrect. Value Measurement is for ROI and business value, not detailed engagement summaries.

Option D: Incorrect. Strategic Dashboard offers high-level KPIs, not channel-specific engagement details.

The SAP Emarsys Help Portal under 'Campaign Analytics' confirms this.