Lifecycle decision glossary
These eight definitions describe the components of the EngageMKTG decision layer. Each term links to its operating flow, limitations and application examples. The definitions here match the opening paragraph on the component page so readers can quote and compare the same meaning in either place.
Updated
Use the definitions in context
The platform hub shows how the components work together. Start with the List Revival playbook for a measured workflow, or the sender requirements tracker for provider obligations. List Revival is the recommended entry application when a permissioned dormant audience is the problem to address.
Pristine spam trap
An address created for the purpose, never used by a person, never published.
Read the defining articleRecycled spam trap
A once-valid address that went dormant.
Read the defining articleTypo spam trap
Addresses on domains a few characters away from popular ones (Spamhaus's examples: yaaho.com, homail.com).
Read the defining articleAgentic marketing
Agentic marketing is the use of software agents that take marketing actions on their own within explicit boundaries.
Read the defining articleNext best action
Next best action is a real-time decisioning approach that uses customer data, business rules and prediction to choose the most valuable action for each individual at a given moment, where the set of possible actions includes sending nothing.
Read the defining articleMarketing (HIPAA)
a communication about a product or service that encourages recipients of the communication to purchase or use the product or service
Read the defining articleAI Content & Acquisition
AI Content & Acquisition (a reviewed content and acquisition workflow) connects audience intent, content variants and channel experiments to customer context. It uses AI for repeatable drafting, clustering and analysis while people own value propositions, brand voice, permission and the decisions to publish or expand a test.
Data Intelligence Framework
Data Intelligence Framework (a customer-data preparation and decision model) connects identity, consent, operational status and timestamped events into usable lifecycle context. It defines how source data becomes a reviewed decision input, so planners and channel integrations can work from consistent meanings instead of disconnected exports.
Decision API
Decision API (an interface for profile-level marketing decisions) passes reviewed eligibility, timing and next-action results into an existing channel stack. It separates decision logic from message execution so email, SMS, push and advertising integrations can use consistent customer context without requiring a full migration.
Event-Centric Timeline
Event-Centric Timeline (a timestamped customer activity history) preserves what happened, when it happened and the status context around each action. It gives lifecycle rules and AI models an ordered record to interpret rather than reducing the relationship to a static field or a single engagement score.
Intelligent Planners
Intelligent Planners (reviewed marketing decision algorithms) evaluate behavior, timing, segments and current eligibility to choose a next action. Each planner handles a defined operational workflow while people retain strategy, goals, brand judgment and the authority to review its rules and results.
Live Marketing Status
Live Marketing Status (a per-profile eligibility state) keeps consent, suppression, bounce state, interest and frequency context available before a marketing action. It turns a profile from a static audience row into a current operational record that planners can consult when deciding whether to send, wait or suppress.
Marketing Backend-as-a-Service
Marketing Backend-as-a-Service, or MBaaS (managed lifecycle decision infrastructure), supplies profile, event, status and planner foundations without requiring a team to build a separate marketing backend. It connects those reusable capabilities to existing data sources and channel tools so an application can share current customer context.
Unified Profile Graph
Unified Profile Graph (identity resolution with subscription and permission context) connects records belonging to one person across brands, domains and channels. It gives lifecycle decisions one profile to reference while retaining the source, scope and history of each subscription rather than treating a shared email address as universal permission.