Issue
Sample issue
- ApprovalApproved
A newsletter issue is not dispatched until an editor approves it.
Pro campaigns, plus assisted publisher setup.
Editors approve an issue, then read opens, clicks, bottom-image loads, poll votes, replies and recorded-activity tiers without treating them as proof of a human reader.
Sample account · Sample data. The film is a demonstration of the product, using sample records.
Issue
A newsletter issue is not dispatched until an editor approves it.
An editor approves the issue before the scheduler can send it.
Pro campaigns, plus assisted publisher setup
Editor approval, then opens, recorded clicks, a bottom image load, a poll vote, a reply, recorded-activity tiers, and later activity after a click. Opens are provider-reported. Later activity is not caused by the send.
1. Trigger
An editor approves the issue. The scheduler sends it only after that approval.
2. Long Drive Leads
Provider open events, link-router clicks, the bottom image request, poll votes and replies are stored as separate signals.
3. Operator sees
The ladder, the recorded-activity tier mix, and later activity in the window after a click.
4. Next action
Decide what to send next. The window does not mean the send caused the later activity.
Profiles and inferred topics, through managed onboarding.
Topic ranking and a saved audience from list fields.
Permission, bad addresses, pause and STOP. Supporting, not the flagship.
Pro campaigns, plus assisted publisher setup.