To display different content based on gender in one email:

Option B (Block Targeting): Correct. Block Targeting in the VCE allows content blocks to be shown to

specific segments (e.g., females vs. males).

Option D (Personalization Rules): Correct. Rules can conditionally display content based on contact

fields like gender.

Option E (Emarsys Scripting Language): Correct. ESL enables advanced logic to customize content

dynamically by gender.

Option A: Incorrect. Predict settings are for AI recommendations, not gender-based content splitting.

Option C: Incorrect. Manage Optional Content is for A/B testing, not segment-specific content.

The SAP Emarsys Help Portal under "VCE" and "Personalization" confirms these tools.

Reference: SAP Emarsys Help Portal - "Visual Content Editor" (https://help.emarsys.com/).

For a one-off omnichannel program targeting VIP clients in the Automation Center:

Option A (Target segment): Correct. A segment of VIP clients (e.g., based on purchase history) is used

as the entry node for a one-time campaign across channels.

Option B: Incorrect. Channel Engagement is not an entry node; it’s a metric or condition, not a

starting point.

Option C: Incorrect. Entry from program is for linking programs, not a one-off entry.

Option D: Incorrect. External event is for real-time triggers (e.g., API calls), not a static segment.

The SAP Emarsys Help Portal under "Automation Center" confirms Target Segment for one-off

campaigns.

Reference: SAP Emarsys Help Portal - "Automation Center" (https://help.emarsys.com/).

The Sales Data API is preferred for Smart Insight:

Option C: Correct. API submissions are processed faster than file uploads, making data available in

the UI (e.g., dashboards) more quickly.

Option A: Incorrect. Column order is predefined in the API schema, not flexible.

Option B: Incorrect. Custom columns are possible but not the primary reason for preference.

Option D: Incorrect. Validation occurs, but "real-time" is not the key benefit over speed of UI

availability.

The SAP Emarsys Help Portal under "Sales Data API" highlights faster UI integration.

Reference: SAP Emarsys Help Portal - "Smart Insight" (https://help.emarsys.com/).

When SAP Emarsys integrates with SAP Customer Data Platform (CDP), specific attributes from email

activities (e.g., opens) are synchronized:

Option A (IP address): Correct. The IP address of the contact opening the email is captured and

synced for tracking and geolocation purposes.

Option C (Attachment size): Correct. If an email includes attachments, their size is tracked and synced

as part of activity data.

Option D (Email subject line): Correct. The subject line of the email is synchronized to identify the

specific campaign or email in CDP.

Option B (City name): Incorrect. While IP address might allow geolocation inference, "City name" is

not a directly synced attribute.

Option E (Time zone): Incorrect. Time zone is not typically synced as a standalone attribute from

email opens.

The SAP Emarsys integration guide for SAP CDP lists IP address, attachment size, and email subject

line among synced attributes.

Reference: SAP Emarsys Help Portal - "Integration with SAP Customer Data Platform"

(https://help.emarsys.com/).

Web Recommender widgets in SAP Emarsys enhance product pages:

Option B (Also-Bought widget): Correct. Shows items frequently purchased together, ideal for cross-

sell on product pages.

Option C (Related widget): Correct. Displays similar or complementary items, supporting up-sell and

cross-sell.

Option A: Incorrect. Personal widgets are broader and not product-page-specific.

Option D: Incorrect. Search widgets are for search result pages, not product pages.

The SAP Emarsys Help Portal under "Web Recommendations" recommends these for product pages.

Reference: SAP Emarsys Help Portal - "Web Recommendations" (https://help.emarsys.com/).