# Marketing Automation Journey

This path is for teams that want to track customer behavior, build segments, trigger workflows, and send marketing email with Bento.

---

## Goal {{ id: 'goal' }}

By the end, Bento receives useful product signals and can use those signals to trigger workflows, build audiences, and measure engagement.

---

## Recommended Path {{ id: 'recommended-path' }}

1. Read [Core Concepts: Events](/docs/concepts/events), [People](/docs/concepts/people), [Tags](/docs/concepts/tags), and [Fields](/docs/concepts/fields).
2. Pick an [SDK](/docs/sdks) or use [Events API](/docs/events_api).
3. Track a small set of high-value events.
4. Import existing contacts with [Subscribers API](/docs/subscribers) or [Import Contacts](/docs/migrations/import).
5. Build your first [Workflow](/docs/concepts/workflows).
6. Send only to engaged, consented contacts while reputation warms up.


> ⚠️ **Warning**
> Do not track every possible event. Start with events that will trigger an automation, build a segment, or answer a specific reporting question.


---

## First Events {{ id: 'first-events' }}

Good first events:

- `$signed_up`
- `$created_account`
- `$subscribe`
- `$purchase`
- `trial_started`
- `checkout_completed`
- `subscription_cancelled`

Use `fields` for flat profile updates and `details` for nested event metadata.

---

## Launch Checklist {{ id: 'launch-checklist' }}

- Events are named consistently.
- Test users appear in the activity timeline.
- Existing contacts are clean and consent-aware.
- Workflows use clear entry and exit criteria.
- First broadcasts target engaged users.
- Deliverability setup is complete.

## Related docs

- [Events API](/docs/events_api)
- [Subscribers API](/docs/subscribers)
- [Workflows](/docs/concepts/workflows)
- [Deliverability](/docs/deliverability)