Customer events
Consent, suppression, and event data
Collect customer signals without confusing observed behavior with permission to send marketing email.
Updated 2026-08-237 min
Events do not grant consent
An identify, signup, purchase, login, or product event is evidence that something happened. It does not by itself create permission to send promotional email.
The strongest blocked state wins
| State | Effect |
|---|---|
| Unsubscribed | Do not send marketing journeys or campaigns |
| Complained | Suppress future sending |
| Bounced | Suppress or hold based on the delivery outcome |
| Pending confirmation | Do not treat as confirmed subscription |
| Subscribed with evidence | Eligible only when all other policy and journey checks pass |
What event producers should send
- ✓Stable customer identifiers
- ✓Only the traits and properties needed for the documented purpose
- ✓Original event time when available
- ✓A durable messageId
- ✓No passwords, tokens, payment card details, or free-form sensitive payloads
What journeys enforce
Journey qualification, goals, and timing are evaluated alongside customer eligibility. A technically matching event never overrides unsubscribe, complaint, bounce, sender readiness, or workspace sending policy.