SAP Emarsys Customer Engagement Implementation Consultant flashcards
SAP Emarsys Customer Engagement Implementation Consultant · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Contact database
- The central store of all contact records and their fields in SAP Emarsys; it drives segmentation, personalization, and automation, so its schema must be finalized before import.
- Custom contact field
- A user-defined attribute added to the contact schema with a specific data type; it must exist before importing values and is referenced by segments and personalization tokens.
- Opt-in status
- A per-channel, per-contact consent flag that records whether a contact agreed to receive messages; the send engine enforces it and it must be captured at import.
- Domain authentication
- Configuration of SPF, DKIM, and DMARC records so mailbox providers can verify the sending domain; required before launching email from a new sender domain.
- Tracking domain
- A branded subdomain, configured via CNAME, used for link tracking and image hosting so clicks and opens are attributed to the sender's domain.
- Segment
- A saved set of contact criteria combining profile fields and behavioral filters; it is used to target sends and must be reviewed when the underlying schema changes.
- Automation program
- A node-based workflow with entry criteria, waits, decisions, and actions; it needs explicit re-entry and exit rules to avoid duplicate or runaway sends.
- Re-entry policy
- A setting that controls whether a contact can enter an automation program more than once and under what conditions; it prevents duplicate messaging.
- Seed list
- A set of internal test addresses included in test sends to verify rendering, links, and personalization before a campaign or automation goes live.
- Idempotency key
- A unique identifier sent with an API or feed update so repeated requests do not create duplicate contacts or events during integration syncs.
- Deliverability warm-up
- The gradual increase of sending volume from a new domain or IP so mailbox providers build reputation; it is planned before full-volume launch.
- Personalization token
- A placeholder in message content that is replaced at send time with a contact field value; it depends on the field existing and being populated.
- Behavioral filter
- A segmentation criterion based on contact actions such as opens, clicks, or purchases; it requires event tracking to be configured and flowing.
- External ID
- A unique identifier from an external system stored on the contact record; it links SAP Emarsys contacts to CRM or webshop records during integration.
- Deduplication
- The process of detecting and merging duplicate contact records during import, typically keyed on email address or external ID, to keep the database clean.
- Relational data
- Linked data such as orders or product records associated with a contact; it enables advanced segmentation and personalization beyond flat contact fields.
- Product catalog feed
- A structured feed of product data used for recommendations and dynamic content; it must be synced on a defined schedule and validated for completeness.
- Entry criteria
- The condition that triggers a contact to start an automation program, such as a form submission, field change, or event; it defines who enters the flow.
- Exit condition
- A rule that removes a contact from an automation program, for example after a purchase or opt-out, preventing irrelevant or duplicate messages.
- Wait node
- An automation step that pauses a contact for a set duration or until a condition is met, controlling the timing of subsequent actions in the flow.
- Decision node
- An automation step that branches contacts based on criteria such as engagement or field values, enabling different paths within one program.
- Sending domain
- The domain used in the from address of email messages; it must be verified and authenticated before campaigns can be sent at scale.
- DMARC alignment
- A policy check that the from domain matches the authenticated SPF or DKIM domain; misalignment causes failures and must be resolved during setup.
- REST API integration
- A programmatic connection using HTTP endpoints to sync contacts, events, or orders; it requires authentication, error handling, and defined sync frequency.
- Event tracking
- The capture of contact actions such as opens, clicks, and purchases; it feeds behavioral segments and automation triggers and must be verified at launch.
- Opt-out handling
- The process that records a contact's withdrawal of consent per channel and blocks further sends; it must be tested before go-live to ensure compliance.
- Data import mapping
- The assignment of source file columns to contact fields during import; incorrect mapping causes data loss or type errors and is validated with a test file.
- Field data type
- The format of a contact field such as text, number, or date; it constrains valid values and affects segmentation and personalization behavior.
- Multi-select field
- A contact field that can hold several values at once, useful for interests or categories; segmentation on it uses contains-style matching rather than equality.
- Go-live checklist
- A documented set of pre-launch checks covering authentication, seed testing, automation review, and data feed validation, with a rollback plan for failures.
- Sync frequency
- The interval at which an integration pushes or pulls data between SAP Emarsys and an external system; it determines data freshness for segments and automations.
- Impact assessment
- A review of how a schema or configuration change affects existing segments, personalization tokens, and automations, performed before the change is applied.