Notification campaigns and inbox
Create targeted storefront messages with clear audience, timing and publication rules.
On this page
Choose the right message workflow
| Workflow | Use it for |
|---|---|
| Audience campaign | A scheduled message or a message triggered by a supported customer journey event. |
| Storefront inbox | Published announcements and recipient-visible messages, with read/unread state. |
| Legacy journey templates | Personalized generated records that require their own review and inbox publication. |
| Transactional email | Account and order emails, managed separately in Email templates. |
Create and activate a campaign
- Open Marketing → Notifications and start an audience campaign.
- Message: write the plain-text message and choose a supported internal action when needed.
- Audience & journey: choose everyone, guests or signed-in customers; select the supported event and any segment, product, condition or location restrictions.
- Timing & frequency: set the start, expiry, event delay, cooldown and delivery limit.
- Save the draft, then review the complete audience and message before activation.
- Check publication history and the eligible recipient's storefront inbox.
Understand who can receive a message
- Audience restrictions intersect: matching a segment alone does not bypass location, timing or condition rules.
- Customer segments and customer/order conditions require the signed-in customer audience.
- Guest store visits are scoped to the browser; guest history is not merged into a customer account on sign-in.
- Missing facts do not satisfy a targeting condition.
- Journey campaigns evaluate events after publication starts and within their lookback; activation does not replay older activity.
Investigate a missing notification
Opening the inbox does not mark every message read. Read/unread controls and mark-all manage receipt state separately. Withdraw a publication when its message should no longer be available.
- Confirm that the campaign is activated and within its start and expiry window.
- Check the recipient identity, segment membership, event and selected delivery area.
- Check event delay, cooldown, purchase suppression and delivery limits.
- Ask the recipient to open the store inbox; some activity is discovered on the next inbox visit or poll.
- Review publication state and worker health with the platform team if eligibility is correct.
Assign editing and publication access
Authors need notification read and write access. Activation requires publication permission. Signed-in customer campaigns also require customer and order read permissions. Published targeting and content cannot be silently edited.
