You created link categories under Management > Link Categories. Where can you utilize them? Note:
There are 2 correct answers to this question.
AB
Explanation:
In SAP Emarsys, link categories are utilized to segment recipients based on their interactions with
specific types of links. After creating link categories under Management > Link Categories, you can
assign them to links within your email content. This categorization allows for more targeted analysis
and segmentation.
Utilization in Contacts > Segments: Within the Contacts > Segments section, you can filter contacts
based on their engagement with links from specific categories. This enables the creation of segments
that reflect user behavior related to particular link types, enhancing targeted marketing efforts.
Utilization in Analytics > Trends: In the Analytics > Trends area, link categories help analyze trends in
user interactions with different link types over time. This analysis provides insights into the
effectiveness of various link categories, informing future content strategies.
While the Main Dashboard's Email Results widget provides an overview of email performance, it
doesn't specifically utilize link categories. Similarly, the VCE Email Editor's Predict Mail Category
widget focuses on predictive content recommendations and isn't directly related to link categories.
You want to collect data from contacts using forms. Which forms does SAP Emarsys Customer
Engagement offer? Note: There are 3 correct answers to this question.
A, B, C
Explanation:
SAP Emarsys provides several form types to collect contact data:
Option A (General Registration): Correct. This form is used for new contact sign-ups, collecting basic
information like email or name.
Option B (Newsletter Registration): Correct. Specifically designed for subscribing contacts to
newsletters, often with opt-in options.
Option C (Change Profile): Correct. Allows contacts to update their existing profile data (e.g.,
preferences, contact details).
Option D: Incorrect. "Background Registration" is not a recognized form type in Emarsys
documentation.
Option E: Incorrect. While consent management is a feature, it’s not a distinct form type; it’s
integrated into other forms like Newsletter Registration.
The SAP Emarsys Help Portal under "Forms" lists General Registration, Newsletter Registration, and
Change Profile as standard options.
Reference: SAP Emarsys Help Portal - "Forms" (https://help.emarsys.com/).
Which of the following describe Automation programs? Note: There are 2 correct answers to this
question.
A, C
Explanation:
Automation programs in SAP Emarsys are managed via the Automation Center and Interactions:
Option A: Correct. Interactions are designed for real-time, event-driven programs reacting to
customer actions (e.g., abandoned cart), distinct from scheduled Automation Center programs.
Option C: Correct. The Automation Center is ideal for recurring lifecycle campaigns (e.g., welcome
series, re-engagement), offering scheduled and structured workflows.
Option B: Incorrect. Automation Center and Interactions have different entry points; Automation
Center uses segments or events, while Interactions rely on real-time triggers.
Option D: Incorrect. Automation Center respects opt-in status unless explicitly overridden, ensuring
compliance with marketing preferences.
The SAP Emarsys Help Portal under "Automation Center" and "Interactions" clarifies these
distinctions.
Reference: SAP Emarsys Help Portal - "Automation Center" and "Interactions"
(https://help.emarsys.com/).
SAP Emarsys has four types of block lists. Under which list do notorious complainers fall?
D
Explanation:
SAP Emarsys maintains four block list types to manage contact exclusions:
Option D (Complaints): Correct. Notorious complainers—contacts who frequently mark emails as
spam or complain—are added to the Complaints block list to prevent further sends and protect
sender reputation.
Option A (Internal): Incorrect. Internal block lists are for manual exclusions (e.g., employees), not
complainers.
Option B (Robinson): Incorrect. The Robinson list is for contacts who have opted out via a third-party
list, not specifically complainers.
Option C (Global Suppression): Incorrect. Global Suppression is a broader list for legal or compliance-
based exclusions, not complaint-specific.
The SAP Emarsys Help Portal under "Block Lists" identifies the Complaints list for this purpose.
Reference: SAP Emarsys Help Portal - "Block Lists" (https://help.emarsys.com/).
Why is "daily" the recommended frequency for importing sales data into Smart Insight?
B
Explanation:
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.
Reference: SAP Emarsys Help Portal - "Smart Insight" (https://help.emarsys.com/).
You are creating personalization tokens that you can reuse across different channel campaigns.
Which of the following token types are available? Note: There are 2 correct answers to this question.
A, C
Explanation:
Personalization tokens in SAP Emarsys allow reusable data insertion across channels:
Option A (Contact Data): Correct. Tokens can pull from contact fields (e.g., first name, email), a core
personalization type.
Option C (External Data): Correct. Tokens can use data from external sources (e.g., Relational Data or
API feeds) for dynamic content.
Option B: Incorrect. "Email Address" is a specific field within Contact Data, not a distinct token type.
Option D: Incorrect. "Custom Data" is not a defined token type; custom fields fall under Contact Data
or External Data.
The SAP Emarsys Help Portal under "Personalization Tokens" lists Contact Data and External Data as
key types.
Reference: SAP Emarsys Help Portal - "Personalization Tokens" (https://help.emarsys.com/).
How are list-unsubscribes generated?
B
Explanation:
List-unsubscribes in SAP Emarsys refer to a standardized unsubscribe mechanism:
Option B: Correct. List-unsubscribes are generated when a recipient clicks the unsubscribe link in the
email header, typically inserted via the List-Unsubscribe header (RFC 2369), which Emarsys supports
for compliance.
Option A: Incorrect. Changing profile info may update preferences but doesn’t trigger a list-
unsubscribe.
Option C: Incorrect. Footer unsubscribe links typically lead to a preference center, not a list-
unsubscribe.
Option D: Incorrect. Email client links (e.g., "Report Spam") are not managed by Emarsys as list-
unsubscribes.
The SAP Emarsys Help Portal under "Email Compliance" details the header-based list-unsubscribe
process.
Reference: SAP Emarsys Help Portal - "Email Compliance" (https://help.emarsys.com/).
What can you do with Open Data for SAP Emarsys? Note: There are 3 correct answers to this
question.
A, C, E
Explanation:
Open Data in SAP Emarsys allows integration of external data:
Option A: Correct. An Open Data project can be connected to multiple Emarsys tenants for
centralized data use.
Option C: Correct. Data can be automatically exported for use in third-party BI tools via APIs or
scheduled exports.
Option E: Correct. Users can upload additional data (e.g., custom datasets) into Open Data for
enrichment.
Option B: Incorrect. There’s no strict 10 MB export limit; limits depend on configuration, not a fixed
size.
Option D: Incorrect. Open Data requires specific setup, not just any business email account.
The SAP Emarsys Help Portal under "Open Data" confirms these capabilities.
Reference: SAP Emarsys Help Portal - "Open Data" (https://help.emarsys.com/).
Which of the following applies when using Send Time Optimization (STO)?
C
Explanation:
Send Time Optimization (STO) in SAP Emarsys optimizes email send times based on contact behavior:
Option C: Correct. STO can be activated on either the default or advanced scheduling page when
setting up an email campaign, allowing flexibility in configuration.
Option A: Incorrect. STO uses historical behavior; new contacts without data default to a standard
time, not a configurable one.
Option B: Incorrect. Duplicate exclusion is a separate feature, not tied to STO.
Option D: Incorrect. STO doesn’t allow hour exclusions; it optimizes based on past engagement
patterns.
The SAP Emarsys Help Portal under "Send Time Optimization" verifies STO’s activation options.
Reference: SAP Emarsys Help Portal - "Send Time Optimization" (https://help.emarsys.com/).
Which of the following statements describes how the Email Campaign Update functionality works?
Note: There are 3 correct answers to this question.
BCE
Explanation:
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.