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.

Updated

Get Free List Audit

The problem it removes

An audience export may be correct when it is created and wrong when it is used. A customer unsubscribes after selection, an address hard-bounces in an earlier cohort, or another campaign consumes the remaining contact allowance. Reusing yesterday's file can put those people back into today's queue.

The problem is especially visible in dormant-list work: an address that bounced in cohort three must not be re-queued in cohort twenty because a separate system still marks it active. Current status connects those changes to later decisions. It also makes the reason for a suppression inspectable instead of hiding it inside a campaign-specific exclusion spreadsheet.

How it works

  1. Bring permission, bounce, unsubscribe, complaint and contact-pressure signals into the same profile context. Map their source and meaning before relying on a status flag.

  2. Update the operational state as relevant events arrive. Fields such as status.hard_bounce, status.unsubscribed, status.series_interest and status.timezone_validated describe different aspects of the profile; one positive signal does not cancel a suppression.

  3. Have the planner evaluate that state before releasing the next action. Apply consent and suppression checks before interest scoring, timing or content selection.

  4. Return a send, wait or suppress result through the Decision API, and retain the reason for the operating team to review. Subsequent events feed the next decision rather than silently rewriting the earlier result.

Explainable lifecycle decision waterfall A vertical decision pipeline checks profile validity, consent, safety status, contact frequency, campaign fit, time, and channel before sending, delaying, suppressing, or requesting human review. DECISION WATERFALL Every engagement action should be explainable. Is the profile valid?Is consent available?Is current status safe? Is the person over-contacted?Which campaign is most useful?Which time and channel fit best? identitypermissionrisk frequencyrelevancedelivery ✓ SendⅡ Delay× Suppress◇ Human Review safe + usefultry laterprotect profilejudgment needed The result includes the checks, inputs, and reason — not just the answer.

Check the whole path during implementation: create a candidate audience, introduce a newer suppression, then verify the profile is excluded from the proposed action. Repeat the check across the source systems that could otherwise reintroduce the address. A rendered field or imported record is weaker evidence than an observed suppressed action.

Event-Centric Timeline supplies the sequence behind a state change, while Unified Profile Graph connects its identity and subscription context. Define how delayed or conflicting updates are reviewed. A team should be able to identify the authoritative permission source before treating the profile as eligible.

A useful review also checks when the signal was received and which system recorded it. Missing or delayed permission updates need investigation before the audience is treated as ready for another release.

Where it shows up

List Revival uses Manactor, Live Marketing Status and Trigger Processor to review gradual cohort release. Campaign Error Shield uses status and trigger checks before campaign execution. Multi-Brand Profile Unification also uses live status alongside identity and consent context, preserving the relevant brand's permission boundary.

What it is not

Live Marketing Status is not an ESP, an inbox-placement guarantee or a replacement for source permission evidence. A current state can prevent a known ineligible send; it cannot establish that every remaining mailbox wants the message. Data quality, authentication, relevant content and a responsible sending plan still matter. A status field should be interpreted with its source and update history.

FAQ

Does interest override an unsubscribe?

No. Interest and eligibility are separate inputs. A click, score or predicted response must not overrule the consent and suppression checks for the proposed action.

Why is a daily export insufficient?

Eligibility can change after the export. A later bounce, unsubscribe or contact-limit event needs to affect the next decision, including records selected by another workflow.

How does this help a dormant-list pilot?

It connects yesterday's bounce, complaint and engagement signals to today's release decision, helping prevent known ineligible profiles from being queued again in a later cohort.

What should the team inspect?

Inspect the status source, latest relevant events, intended brand and decision reason. Test an actual exclusion path during implementation rather than accepting a field name as proof that the control works.

Read more

Read playbook Step 6: staged release and why emails suddenly go to spam to connect profile state with daily operational review.