Compare
| Campaign | Journey | |
|---|---|---|
| Shape | Single send or schedule | Multi-step flow per person |
| Trigger | Date or API | Event, audience qualification, read audience or business event |
| Best for | Broadcasts and announcements | Onboarding, abandonment, lifecycle |
Journey types
- Unitary event journeys (real-time)
- Audience qualification journeys
- Read-audience (batch) journeys
- Business event journeys
- API-triggered campaigns
Using attributes in content and conditions
Any attribute — consent, preferences, loyalty, custom fields — can drive audience logic, journey conditions and personalisation, provided the field and its dataset are enabled for Profile. AJO data sources and configurations make external or profile data available to journeys; AEP source connections are how data is ingested into the platform.
Frequently asked questions
Can a journey send a broadcast?
A read-audience journey can, but if there is no per-person logic a campaign is simpler.
Why is my attribute missing in personalisation?
Check that the field is in a profile-enabled schema and dataset.
Last updated: