SAP Emarsys Customer Engagement Implementation Consultant study materials
SAP Emarsys Customer Engagement Implementation Consultant study resources

SAP Emarsys Customer Engagement Implementation Consultant practice questions

One question at a time. Build your SAP Emarsys Customer Engagement Implementation Consultant understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1SAP Emarsys Customer Engagement Implementation

In SAP Emarsys, which contact field typically serves as the primary identifier for a contact record and is used to match incoming data during an import?

  1. The email address field Correct answer.
  2. The first name field
  3. The language field
  4. The opt-in type field

Explanation

The email address is the default primary key that uniquely identifies a contact and is used to match rows during imports and API calls, so duplicates are resolved by it. Other fields such as first name or language are attributes that can be updated but do not identify the record.

Question 2SAP Emarsys Customer Engagement Implementation

A marketer wants new contacts to be created automatically when they submit a web form. Which Emarsys capability is designed to collect and push form submissions into the contact database?

  1. Web Extend or a form integration feeding the Contacts API Correct answer.
  2. Smart Insights dashboards
  3. The email campaign launch schedule
  4. The Predict revenue forecast report

Explanation

Web Extend and form integrations send submitted data into Emarsys through the Contacts API, creating or updating contact records in real time. Analytics dashboards and campaign schedules consume data but do not ingest new contacts from a form.

Question 3SAP Emarsys Customer Engagement Implementation

Which Emarsys feature evaluates a contact against a set of conditions and, when matched, can automatically add the contact to a segment?

  1. A segment with automation rules Correct answer.
  2. A suppression list
  3. A test list
  4. A seed list

Explanation

Segments define criteria and can be paired with automation so contacts are added or removed as their data changes. Test and seed lists are for campaign QA, and suppression lists exclude recipients.

Question 4SAP Emarsys Customer Engagement Implementation

When configuring an email campaign in Emarsys, what is the purpose of the test list?

  1. To calculate revenue attribution
  2. To permanently store bounced addresses
  3. To send a preview to selected addresses before the main launch Correct answer.
  4. To define the sender domain authentication

Explanation

A test list holds addresses that receive a preview send so the creative and personalization can be verified before launching. It does not affect authentication, attribution, or bounce handling.

Question 5SAP Emarsys Customer Engagement Implementation

Which Emarsys module is used to build multi-step customer journeys that trigger messages based on events such as a purchase or a cart abandonment?

  1. Email Analysis
  2. Automation Center Correct answer.
  3. Contact Import
  4. Revenue Attribution

Explanation

Automation Center lets you define entry points, events, and node logic to orchestrate multi-step journeys. The other modules cover reporting, importing, and analysis rather than journey orchestration.

Question 6SAP Emarsys Customer Engagement Implementation

A customer wants to send personalized product recommendations in an email. Which Emarsys component supplies those recommendations based on browsing and purchase behavior?

  1. The bounce handler
  2. The unsubscribe preference center
  3. The Predict product recommendation engine Correct answer.
  4. The sender policy framework record

Explanation

The Predict recommendation engine uses behavioral and transactional data to generate personalized product blocks. Bounce handling, SPF records, and preference centers do not produce recommendations.

Question 7SAP Emarsys Customer Engagement Implementation

Which protocol or record type is used to authorize Emarsys sending domains and improve deliverability by specifying permitted sending servers?

  1. A CNAME for the tracking domain only
  2. SPF and DKIM records Correct answer.
  3. An MX record for the reply address
  4. A PTR record for the unsubscribe link

Explanation

SPF and DKIM records authorize sending servers and cryptographically sign messages, which receivers use to validate authenticity. MX records route inbound mail, and tracking CNAMEs affect link domains rather than sender authorization.

Question 8SAP Emarsys Customer Engagement Implementation

What does a hard bounce indicate about a recipient address in Emarsys?

  1. The recipient opened the message
  2. The recipient clicked a link
  3. The mailbox was temporarily full
  4. The address is permanently undeliverable Correct answer.

Explanation

A hard bounce signals a permanent delivery failure such as an invalid domain or unknown user, so the address should not be retried. A soft bounce is temporary, and opens or clicks are engagement events.

Question 9SAP Emarsys Customer Engagement Implementation

An implementation consultant needs to update a large set of contact records with new attribute values on a recurring basis. Which approach best fits an automated, repeatable process?

  1. Scheduling a recurring data import using a defined source file Correct answer.
  2. Manually editing each contact in the UI
  3. Creating a new segment for each record
  4. Sending a campaign to the contacts

Explanation

A scheduled import with a stable file format and matching key supports repeatable bulk updates without manual effort. Manual edits do not scale, and campaigns or segments do not modify attribute values.

Question 10SAP Emarsys Customer Engagement Implementation

During an import, a consultant wants existing contacts to be updated while new contacts are created. Which setting should be configured?

  1. Delete and re-create all records
  2. Update only and skip unknown contacts
  3. Reject the file if any row is invalid
  4. Create and update using the email address as the match key Correct answer.

Explanation

Setting the operation to create and update with email as the match key lets the import insert new contacts and modify existing ones in a single pass. Update-only would skip new contacts, and delete-and-recreate risks data loss.

Question 11SAP Emarsys Customer Engagement Implementation

A contact has opted out of a specific email category but remains opted in for other categories. How should the consultant model this in Emarsys?

  1. Delete the contact record
  2. Use separate opt-in fields per category and segment on them Correct answer.
  3. Add the contact to the global suppression list
  4. Change the contact's email address

Explanation

Category-level opt-in fields preserve consent granularity so sends can target only contacts who opted in for that category. Deleting the record or globally suppressing the contact would remove legitimate consent for other categories.

Question 12SAP Emarsys Customer Engagement Implementation

Which condition would correctly exclude contacts who purchased within the last seven days from a re-engagement segment?

  1. First name is not empty
  2. Last purchase date is more than seven days ago or is empty Correct answer.
  3. Email address contains the company domain
  4. Last purchase date equals today

Explanation

Excluding recent buyers means selecting contacts whose last purchase is older than seven days or who have no purchase record. Conditions on name or domain do not reflect recency of purchase.

Question 13SAP Emarsys Customer Engagement Implementation

In Automation Center, a consultant needs a journey that waits two days after signup and then sends a welcome email only if the contact has not yet opened a prior message. Which node arrangement achieves this?

  1. A single send node with no conditions
  2. A segment node with no entry point
  3. A wait node followed by a decision node checking the open event, then a send node Correct answer.
  4. A test list node before the entry point

Explanation

A wait node introduces the delay, and a decision node evaluates the open event so the send node fires only for contacts meeting the condition. A single send node cannot express timing or conditional logic.

Question 14SAP Emarsys Customer Engagement Implementation

A campaign must use a different sender address for a specific business unit. What is the correct implementation step?

  1. Create a new segment for the business unit
  2. Change the contact's language field
  3. Configure a verified sender address and assign it to the campaign Correct answer.
  4. Add the address to the suppression list

Explanation

Sender addresses must be verified for the account and then selected at the campaign level so the correct from-address is used. Segments, suppression lists, and language fields do not control the sender identity.

Question 15SAP Emarsys Customer Engagement Implementation

Which personalization approach correctly inserts a contact's first name into an email with a fallback when the value is missing?

  1. Removing the greeting entirely for all contacts
  2. Hard-coding a single name in the template
  3. Using a personalization placeholder with a default value defined Correct answer.
  4. Sending a generic campaign to the whole database

Explanation

A placeholder with a defined default renders the stored value when present and the fallback when the field is empty, avoiding broken greetings. Hard-coding or removing the greeting loses personalization for everyone.

Question 16SAP Emarsys Customer Engagement Implementation

A consultant is troubleshooting why a contact did not receive an automated email. Which factor is the most likely cause to check first?

  1. The number of images in the template
  2. The contact's opt-in status and segment or entry-point eligibility Correct answer.
  3. The color scheme of the email template
  4. The length of the subject line

Explanation

Automation only sends to contacts who meet the entry criteria and are opted in, so eligibility is the primary check. Template styling, image count, and subject length affect rendering or engagement but not whether the journey admits the contact.

Question 17SAP Emarsys Customer Engagement Implementation

A client reports that opens are being recorded but clicks are not. Which area should the consultant investigate first?

  1. The SPF record for the sending domain
  2. The segment definition logic
  3. The contact import match key
  4. The link tracking configuration and tracking domain setup Correct answer.

Explanation

Clicks depend on links being rewritten to the tracking domain, so a misconfigured tracking domain or disabled link tracking explains missing click data while opens still register. SPF, import keys, and segment logic do not govern click tracking.

Question 18SAP Emarsys Customer Engagement Implementation

Which data source in Emarsys is typically used to attribute revenue to a specific campaign?

  1. The sender verification log
  2. The automation node count
  3. Order data captured through Web Extend or a revenue integration Correct answer.
  4. The contact's opt-in history

Explanation

Revenue attribution links orders recorded through Web Extend or an integration back to the campaign or journey that influenced them. Opt-in history, sender logs, and node counts contain no order value.

Question 19SAP Emarsys Customer Engagement Implementation

A consultant must ensure that a contact who unsubscribes from one campaign is excluded from all future marketing sends. Which configuration achieves this?

  1. Changing the contact's language
  2. Removing the contact from a single segment
  3. A category-specific opt-out only
  4. A global opt-out that suppresses the contact from all marketing sends Correct answer.

Explanation

A global opt-out flags the contact so all marketing sends exclude them, satisfying the request. Category opt-out and segment removal affect only limited sends, and language has no suppression effect.

Question 20SAP Emarsys Customer Engagement Implementation

During a data migration, a consultant finds duplicate contacts sharing the same email address with different attribute values. What is the best practice for resolving them before go-live?

  1. Define a merge rule that consolidates attributes into one record per email Correct answer.
  2. Ignore duplicates and import all rows
  3. Delete all rows with duplicates
  4. Create a new email address for each duplicate

Explanation

A merge rule consolidates duplicate rows into a single contact per email, preserving the most reliable attribute values. Ignoring duplicates creates conflicting records, and deleting or fabricating addresses loses valid data.

Question 21SAP Emarsys Customer Engagement Implementation

A client wants a journey where contacts who abandon a cart receive an email after one hour, a second email after 24 hours only if they still have not purchased, and no further messages after a purchase. Which design correctly implements this?

  1. A single segment emailed weekly
  2. A test list that receives all messages
  3. Three independent campaigns launched manually each day
  4. A journey with a cart-abandon entry, wait nodes, purchase-check decision nodes, and exit on purchase Correct answer.

Explanation

The journey uses an event entry point, timed waits, decision nodes that check for a purchase, and an exit condition that stops messaging once a purchase occurs. Manual campaigns and weekly segments cannot enforce timing or purchase-based exit.

Question 22SAP Emarsys Customer Engagement Implementation

After a domain migration, open rates drop sharply while bounce rates remain stable. Which explanation is most consistent with these symptoms?

  1. The tracking domain or open-tracking pixel is misconfigured after the migration Correct answer.
  2. Contacts are being suppressed by opt-out rules
  3. The import match key was changed
  4. The segment criteria were broadened

Explanation

Stable bounces indicate messages are still delivered, so a drop in opens points to the tracking pixel or tracking domain not resolving after migration. Suppression, import keys, and segment changes would alter audience size rather than open tracking.

Question 23SAP Emarsys Customer Engagement Implementation

A consultant is asked to design a segmentation strategy where contacts move between lifecycle stages automatically as their behavior changes. Which approach is most appropriate?

  1. Suppression lists per lifecycle stage
  2. Behavior-driven segments with automation rules that add and remove contacts as criteria change Correct answer.
  3. A single global segment containing all contacts
  4. Static segments refreshed manually each quarter

Explanation

Behavior-driven segments with automation keep lifecycle membership current by adding or removing contacts whenever criteria change. Static or global segments become stale, and suppression lists exclude rather than classify contacts.

Question 24SAP Emarsys Customer Engagement Implementation

A client wants to test two subject lines on a small portion of the audience and automatically send the better-performing version to the remainder. Which Emarsys capability supports this?

  1. A suppression list
  2. A recurring import
  3. A seed list
  4. A/B testing with an automated winner selection Correct answer.

Explanation

A/B testing splits the audience, measures performance on a sample, and can automatically send the winning variant to the rest. Suppression and seed lists control recipients for QA, and imports load data.

Question 25SAP Emarsys Customer Engagement Implementation

A consultant must ensure that transactional messages such as password resets are not blocked by a contact's marketing opt-out. Which configuration is required?

  1. Remove the contact from all segments
  2. Route transactional sends through a separate transactional message type that ignores marketing opt-out Correct answer.
  3. Add the contact to the global suppression list
  4. Change the contact's email address

Explanation

Transactional messages are sent through a distinct message type that is not governed by marketing consent, so password resets still reach the recipient. Suppression, segment removal, or address changes would block or corrupt delivery.

Question 26SAP Emarsys Customer Engagement Implementation

Which Emarsys capability is the primary system of record for storing contact attributes such as birth date and loyalty tier?

  1. The Automation Center journey canvas
  2. The contact database with its custom and standard fields Correct answer.
  3. The email template editor block library
  4. The deliverability reporting dashboard

Explanation

The contact database holds profile data in standard and custom fields, and those stored values feed segmentation and personalization. Automation Center, templates, and reporting consume contact data but do not serve as the authoritative store.

Question 27SAP Emarsys Customer Engagement Implementation

A consultant needs to add a new field to every contact record to store a numeric loyalty points balance. Which Emarsys object should be created?

  1. A segment with a numeric filter
  2. A voucher pool with numeric codes
  3. A relational table joined on email address
  4. A custom contact field of numeric type Correct answer.

Explanation

Custom contact fields extend the contact schema and support typed values such as numbers, which can then be used in filters and personalization. Segments, relational tables, and voucher pools serve different purposes and do not extend the contact profile itself.

Question 28SAP Emarsys Customer Engagement Implementation

Which Emarsys feature should a consultant configure to trigger a welcome email immediately when a contact registers through a web form?

  1. An Automation Center program with a form registration trigger node Correct answer.
  2. A test list used for subject line previews
  3. A recurring newsletter with a daily send time
  4. A scheduled batch campaign sent to a static segment

Explanation

Automation Center programs start from trigger nodes such as form registration, allowing near real-time message dispatch. Batch campaigns, recurring newsletters, and test lists all depend on scheduled or manual initiation rather than an event.

Question 29SAP Emarsys Customer Engagement Implementation

A consultant is defining a segment of contacts who are opted in to the newsletter and live in Germany. Which combination of filter types achieves this?

  1. A link click condition combined with a domain reputation condition
  2. An opt-in status condition combined with a contact field condition on country Correct answer.
  3. A voucher redemption condition combined with a template condition
  4. A revenue attribution condition combined with a send time condition

Explanation

Segments combine conditions on contact profile fields and subscription status, so opt-in state plus a country field filter is the correct construction. The other pairs reference metrics or configuration objects that are not contact-level eligibility criteria.

Question 30SAP Emarsys Customer Engagement Implementation

Which Emarsys feature allows a consultant to embed a contact's stored loyalty points value into an email at send time?

  1. A personalization placeholder referencing the contact field Correct answer.
  2. A static footer block with fixed text
  3. A preheader set in the campaign settings
  4. A reply-to address configured per campaign

Explanation

Personalization placeholders are resolved per recipient at send time from contact data, so a loyalty points field renders individually. Static blocks, preheaders, and reply-to settings carry fixed or configuration values and do not vary per contact.

Question 31SAP Emarsys Customer Engagement Implementation

A consultant must verify that a new email template renders correctly across major clients before launch. Which Emarsys capability supports this?

  1. The Automation Center node history
  2. The contact import log
  3. The voucher pool allocation report
  4. The inbox preview and rendering test feature Correct answer.

Explanation

Inbox preview rendering checks show how a template displays across common email clients and devices. Import logs, voucher reports, and automation histories track data and journey events rather than visual rendering.

Question 32SAP Emarsys Customer Engagement Implementation

Which metric in Emarsys reporting indicates the share of delivered emails that were opened?

  1. Open rate calculated against delivered messages Correct answer.
  2. Click-through rate calculated against opened messages
  3. Unsubscribe rate calculated against delivered messages
  4. Bounce rate calculated against sent messages

Explanation

Open rate expresses opens as a proportion of delivered messages, which isolates engagement from delivery failures. Bounce rate measures non-delivery, unsubscribe rate measures opt-outs, and click-through rate measures clicks.

Question 33SAP Emarsys Customer Engagement Implementation

A consultant is setting up a new user who should view campaign reports but must not be able to send campaigns. Which Emarsys mechanism enforces this?

  1. A separate business unit created for the user
  2. Role-based access permissions assigned to the user account Correct answer.
  3. An API token scoped to reporting endpoints
  4. A segment restricted to the user's contact list

Explanation

Emarsys controls capabilities through user roles and permissions, so assigning a read-only reporting role prevents sending. Segments, API tokens, and business units address audience, integration, and organizational separation rather than UI send rights.

Question 34SAP Emarsys Customer Engagement Implementation

A consultant must ensure that contacts who register through a form receive a confirmation email and are only added to the newsletter segment after clicking the confirmation link. Which approach implements this?

  1. A batch campaign that re-sends the welcome email weekly until a click occurs
  2. A single opt-in import that sets the newsletter field to true during form submission
  3. A segment filter that includes all form registrants regardless of confirmation
  4. A double opt-in automation that sends a confirmation email and applies the opt-in on link click Correct answer.

Explanation

Double opt-in requires a confirmation action before the subscription is recorded, which is implemented as an automation that sends the confirmation and sets opt-in status on the click event. Setting the field immediately is single opt-in, and repeated sends or unfiltered segments do not gate subscription on confirmation.

Question 35SAP Emarsys Customer Engagement Implementation

A consultant needs to suppress all contacts who received any email in the last 48 hours from a promotional campaign. Which configuration achieves this?

  1. A segment filter on the contact's preferred language
  2. A send-time exclusion rule based on recent message history Correct answer.
  3. A template condition that hides the offer for recent recipients
  4. An automation node that delays the campaign by two days

Explanation

Send-time exclusion rules evaluate recent send history and remove contacts who received messages within the defined window. Language filters, delays, and template conditions do not suppress based on prior send activity.

Question 36SAP Emarsys Customer Engagement Implementation

A consultant is building a replenishment journey where the wait duration differs by product category purchased. Which Automation Center design supports this?

  1. Send all reminders immediately and rely on frequency capping
  2. Add a random split node with equal distribution across categories
  3. Branch on the purchased category and place a different wait node in each path Correct answer.
  4. Use a single wait node and vary the email content by category

Explanation

Conditional branching lets each category follow its own path with an appropriate wait duration before the reminder. A single wait, random split, or immediate send cannot express category-specific timing.

Question 37SAP Emarsys Customer Engagement Implementation

A client wants contacts to exit a nurture journey as soon as they make a purchase. Which Automation Center element should the consultant configure?

  1. An exit criteria rule triggered by a purchase event Correct answer.
  2. A wait node set to the maximum allowed duration
  3. A goal node that only records completion without removal
  4. A filter node that removes contacts at program start

Explanation

Exit criteria evaluate events during the journey and remove contacts who meet the condition, such as a purchase. Wait nodes, start filters, and recording-only goals do not remove contacts mid-journey.

Question 38SAP Emarsys Customer Engagement Implementation

A consultant must send a follow-up email only to contacts who clicked a specific link in the previous campaign. Which data should the follow-up segment be built on?

  1. Contact creation date within the prior campaign window
  2. Delivery status of the prior campaign
  3. Email domain of the recipient address
  4. Link-level click behavior recorded for the prior campaign Correct answer.

Explanation

Link-level click data identifies exactly which recipients interacted with a specific URL, enabling precise follow-up targeting. Creation date, domain, and delivery status describe other attributes and do not indicate link engagement.

Question 39SAP Emarsys Customer Engagement Implementation

A consultant is preparing a contact import where a date of birth column is formatted as DD/MM/YYYY. What should be configured to avoid corrupted date values?

  1. An automatic timezone conversion for all imported rows
  2. The matching date format for that field in the import mapping Correct answer.
  3. A deduplication rule that ignores date columns
  4. A text field type so the raw string is preserved

Explanation

Import mappings must declare the source format so dates are parsed into the stored date type correctly. Timezone conversion, storing as text, or excluding the column does not produce valid date values.

Question 40SAP Emarsys Customer Engagement Implementation

A consultant must ensure that only contacts with a valid email address and confirmed consent are included in a transactional order confirmation flow. Which design choice is correct?

  1. Send the confirmation from the promotional campaign calendar
  2. Trigger the flow from the order event and gate it on the transactional consent status Correct answer.
  3. Trigger the flow from a weekly batch segment of all customers
  4. Rely on the marketing opt-in field as the only eligibility check

Explanation

Transactional messages should be event-driven and gated on the consent type that covers transactional communication, keeping them separate from marketing eligibility. Batch segments, marketing-only consent, and promotional calendars do not satisfy these requirements.

Question 41SAP Emarsys Customer Engagement Implementation

A consultant observes that a segment built on a custom field returns far fewer contacts than expected. Which investigation step is most appropriate first?

  1. Re-render the email template with a new layout
  2. Confirm the field is populated on imported contacts and the filter operator matches the stored values Correct answer.
  3. Increase the send frequency cap for the campaign
  4. Rebuild the segment using a different field name

Explanation

Sparse or mismatched field values are the usual cause of unexpectedly small segments, so verifying population and operator semantics comes first. Renaming fields, changing caps, or editing templates does not address the data condition.

Question 42SAP Emarsys Customer Engagement Implementation

A client wants a single email that shows different hero images to contacts based on their stored preference attribute. Which Emarsys technique should the consultant use?

  1. A static image with a generic message for all recipients
  2. Dynamic content blocks conditioned on the contact attribute Correct answer.
  3. A reply-to variation per preference group
  4. A separate campaign per preference with manual audience selection

Explanation

Dynamic content blocks evaluate contact attributes at send time and render the matching variant within one campaign. Separate campaigns, static images, and reply-to variations do not deliver attribute-driven variation in a single message.

Question 43SAP Emarsys Customer Engagement Implementation

A consultant needs to measure which automated journey produces the most revenue per recipient. Which comparison is most appropriate?

  1. Revenue attributed to each journey divided by the number of recipients contacted Correct answer.
  2. Total opens across all journeys divided by total sends
  3. Average template render time per journey
  4. Number of automation nodes in each journey

Explanation

Revenue per recipient normalizes attributed revenue by audience size, enabling fair comparison across journeys of different scale. Opens, node counts, and render times do not express revenue efficiency.

Question 44SAP Emarsys Customer Engagement Implementation

A consultant is asked to explain why a contact who qualifies for two automations received the same promotional message twice within minutes. Which cause is most likely?

  1. Both programs were triggered by overlapping events without a suppression rule between them Correct answer.
  2. The template contained two personalization placeholders
  3. The campaign used a shared sender address
  4. The contact's email address was stored with mixed capitalization

Explanation

Overlapping triggers in separate programs can cause duplicate sends unless a suppression rule or shared exclusion prevents the second dispatch. Capitalization, placeholders, and sender address affect rendering or deliverability, not duplicate triggering.

Question 45SAP Emarsys Customer Engagement Implementation

A consultant must migrate 500,000 contacts from a legacy platform while preserving opt-in timestamps and source. Which implementation approach best preserves this provenance?

  1. Import all contacts as opted in and rely on unsubscribe links to correct status
  2. Map opt-in date and source to dedicated custom fields and validate with a sample load Correct answer.
  3. Store consent details in the email subject line of a welcome campaign
  4. Load only email addresses and rebuild consent from current campaign engagement

Explanation

Consent provenance requires dedicated fields for date and source plus validation before the full load, so the data remains auditable. Rebuilding consent from engagement, defaulting to opted in, or storing details in subject lines loses or misrepresents the record.

Question 46SAP Emarsys Customer Engagement Implementation

A consultant is designing a preference center where contacts can opt out of individual content categories while staying subscribed to others. Which data model supports this?

  1. A segment rebuilt manually after each unsubscribe request
  2. A single global opt-out flag applied to every message
  3. Separate opt-in fields per category evaluated by segmentation and send exclusion Correct answer.
  4. A free-text feedback field reviewed manually before each send

Explanation

Category-level consent is represented by distinct opt-in fields that segments and send exclusions can evaluate automatically. A single flag, manual review, or manual segment rebuilding cannot enforce granular preferences reliably.

Question 47SAP Emarsys Customer Engagement Implementation

A client reports that automation emails are arriving hours later than expected. Which factor should the consultant examine first?

  1. The wait and delay settings configured on the nodes preceding the send Correct answer.
  2. The size of the contact database in the account
  3. The number of images embedded in the template
  4. The sender reputation of the previous month

Explanation

Automation timing is governed by wait and delay node configuration, so unexpected latency usually traces to those settings. Database size, image count, and historical reputation do not introduce configured delays into a journey.

Question 48SAP Emarsys Customer Engagement Implementation

A consultant must ensure that a contact who reaches a goal in one journey is not entered into a second journey that targets the same outcome. Which design is most robust?

  1. Shorten the wait nodes in the second journey
  2. Use a shared exclusion segment updated by the first journey and referenced at entry of the second Correct answer.
  3. Schedule the second journey at a different hour of the day
  4. Rely on contacts to unsubscribe after completing the first journey

Explanation

A shared exclusion segment maintained by the first journey creates a durable, reusable entry condition for other programs. Relying on contacts, changing send hours, or shortening waits does not prevent re-entry.

Question 49SAP Emarsys Customer Engagement Implementation

A consultant is asked to make a campaign's audience definition reusable across several future campaigns while keeping membership current. Which approach is correct?

  1. Attach the filter to a single template and reuse the template
  2. Save the filter logic as a reusable segment that recalculates dynamically Correct answer.
  3. Copy the contact list into a static segment for each campaign
  4. Export the audience to a spreadsheet and re-import it before each send

Explanation

Reusable dynamic segments keep membership current as contact data changes and can be referenced by multiple campaigns. Exports, static copies, and template-bound filters either freeze membership or fail to apply at the audience level.

Question 50SAP Emarsys Customer Engagement Implementation

A consultant must diagnose why a personalized first-name placeholder renders as raw text in some emails. Which explanation is most consistent?

  1. The contact record lacks a phone number
  2. The placeholder syntax is malformed or the field is empty and no default is defined Correct answer.
  3. The recipient's email client blocks all images
  4. The campaign used a shared IP pool

Explanation

Raw placeholder text appears when the merge syntax is invalid or the referenced field has no value and no fallback is configured. Image blocking, IP pooling, and missing phone data do not cause placeholder syntax to display literally.