In which cases can you use personalization rules in an email campaign? Note: There are 2 correct answers to this question.
Answer : C, D
In SAP Emarsys, personalization rules allow marketers to dynamically insert content into email campaigns based on contact data, such as names, preferences, or other stored attributes. These rules are applied using the Emarsys personalization engine and are supported in specific types of email campaigns. According to the official SAP Emarsys documentation, personalization rules can be utilized in batch emails and recurring emails, making options C and D the correct answers. Let's explore each option in detail to clarify why only these two are valid.
A . In a triggered email: Triggered emails in SAP Emarsys are automated emails sent in response to specific contact actions (e.g., cart abandonment, form submission) and are typically managed through the Automation Center or predefined programs. While triggered emails can include personalization (e.g., using contact fields like first name), they do not support the full application of personalization rules as defined in the Emarsys Email Editor. Personalization rules, which involve conditional logic and dynamic content blocks (e.g., 'if field X = Y, show content Z'), are designed for manual campaign setup rather than the automated, event-driven nature of triggered emails. The documentation states that personalization in triggered emails is limited to basic field insertion rather than complex rule-based logic (reference: 'Automation Center: Triggered Emails,' updated October 2024). Thus, this option is incorrect for personalization rules specifically.
B . In an on-event email: On-event emails are a subset of triggered emails tied to specific events (e.g., a purchase or subscription) and are similarly managed through automation workflows. Like triggered emails, they support basic personalization (e.g., inserting a contact's name or order details) but do not allow the application of advanced personalization rules with conditional logic. The Emarsys Help documentation clarifies that on-event emails rely on predefined templates and event data, not the flexible rule-building interface available in the Email Editor for manual campaigns (reference: 'Event-Triggered Campaigns,' updated September 2024). Therefore, this option is also incorrect for personalization rules.
C . In a batch email: Batch emails are one-time, manually scheduled email campaigns sent to a segment of contacts (e.g., a newsletter or promotional blast). These emails fully support personalization rules within the SAP Emarsys Email Editor. Marketers can create rules using the drag-and-drop interface to define conditions (e.g., 'if gender = female, show women's products') and insert dynamic content accordingly. The documentation explicitly states, 'Personalization rules can be added to batch emails to tailor content based on contact data' (reference: 'Email Campaigns: Personalization Rules,' updated November 2024). This makes batch emails a correct case for using personalization rules, validating option C.
D . In a recurring email: Recurring emails are scheduled to send repeatedly at set intervals (e.g., a weekly digest) to a defined segment. Like batch emails, they are created and edited in the Email Editor, where personalization rules can be applied to customize content for each send based on contact attributes. The Emarsys documentation confirms that 'recurring campaigns support the same personalization features as batch emails, including rules for dynamic content' (reference: 'Recurring Campaigns: Setup and Personalization,' updated October 2024). This compatibility with personalization rules makes option D correct.
To summarize, personalization rules---distinct from basic field personalization---are a feature of the Email Editor used in manually configured campaigns like batch and recurring emails. Triggered and on-event emails, while capable of personalization, rely on automation workflows and event data rather than the rule-based logic applied in the Email Editor. The two correct cases, as verified by Emarsys resources, are batch emails (C) and recurring emails (D).
You want to build a comma-separated values (CSV) file and import it into SAP Emarsys. Which of the following rules apply? Note: There are 2 correct answers to this question.
Answer : B, D
When preparing a comma-separated values (CSV) file for import into SAP Emarsys, it's essential to adhere to specific formatting guidelines to ensure data integrity and successful import processes.
B . Always use a period as the decimal separator.
For numerical data, especially floating-point numbers, SAP Emarsys mandates the use of a period (.) as the decimal separator, regardless of regional or locale-specific conventions that might use a comma (,). This standardization ensures consistent data interpretation across different systems and regions.
D . Imported files must have a newline control character in the first 265 KB.
To prevent the accidental upload of binary files and to ensure proper file processing, SAP Emarsys requires that imported CSV files contain a newline control character within the first 265 kilobytes (KB) of the file. This requirement helps the system recognize and validate the file format before processing the entire content. help.emarsys.com
Incorrect Options:
A . UTF-8 4 byte characters are allowed.
This statement is incorrect. SAP Emarsys supports UTF-8 encoding for CSV files; however, it does not allow UTF-8 4-byte characters, such as emojis. Including such characters can prevent the successful import of files. help.emarsys.com+5help.emarsys.com+5help.emarsys.com+5
C . Values are not case sensitive.
This statement is also incorrect. In SAP Emarsys, values within CSV files are case sensitive. For example, the email addresses 'example@address.com' and 'EXample@address.com' would be treated as distinct entries. help.emarsys.com
Adhering to these guidelines is crucial for the accurate and efficient import of data into SAP Emarsys, ensuring that your marketing campaigns and data analyses are based on reliable information.
You have just added a new product line to your online store and you want to target your existing VIP clients with a one-off omnichannel Automation Center program. Which entry node do you use?
Answer : A
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.
In which of the following scenarios can an Automation program be tested?
Answer : C
Testing Automation programs in SAP Emarsys:
Option C (When a program is In Design): Correct. Programs can be tested during the design phase before activation, using test contacts to simulate the flow.
Option A: Incorrect. Freezing locks the program, preventing testing.
Option B: Incorrect. Testing isn't available 'at any time'; it's restricted to design mode.
Option D: Incorrect. Pausing an active program allows edits but not full testing.
The SAP Emarsys Help Portal under 'Automation Center' specifies testing in design mode.
Which tools can you use to show different content to female and male contacts in a single email campaign? Note: There are 3 correct answers to this question.
Answer : B, D, E
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.
You are tasked with setting up a new product feed for SAP Emarsys. What rules should you follow to ensure the product feed is accepted in Predict Data Sources? Note: There are 2 correct answers to this question.
Answer : A, C
For a product feed in Predict Data Sources:
Option A: Correct. Empty fields should be left blank (not null or placeholder) to avoid processing errors.
Option C: Correct. The first row must contain field names (e.g., item_id, title) for proper mapping.
Option B: Incorrect. UTF-8 is the recommended encoding, not ASCII, to support international characters.
Option D: Incorrect. Commas are the default separator for CSV feeds; pipes are not standard unless specified.
The SAP Emarsys Help Portal under 'Predict Data Sources' outlines these rules.
SAP Emarsys has four types of block lists. Under which list do notorious complainers fall?
Answer : D
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.