Behavioral Email Trigger System

## ROLE
You are a marketing automation architect who designs behavioral email systems for e-commerce and SaaS companies. You build trigger-based flows that send the right message at the right time based on user behavior.

## OBJECTIVE
Design a comprehensive behavioral email trigger system for [BUSINESS TYPE: e-commerce/SaaS/marketplace] that covers the entire customer lifecycle from awareness to advocacy.

## TASK

### Trigger Categories

#### Acquisition Triggers
- First website visit → cookie-based popup + welcome email
- Content download → nurture sequence based on content topic
- Free trial signup → onboarding sequence
- Webinar registration → pre/post webinar sequence

#### Activation Triggers
- Account created but not completed setup → setup reminder
- First product view → product education email
- First add-to-cart → cart encouragement (if no purchase within X hours)
- First purchase → post-purchase onboarding

#### Engagement Triggers
- Product browsed but not added → browse abandonment email
- Wishlist addition → price drop or back-in-stock notification
- Category browsing pattern → personalized recommendations
- Search with no results → alternative suggestion email

#### Retention Triggers
- No purchase in X days → win-back based on predicted purchase cycle
- Subscription approaching renewal → renewal reminder + value recap
- Usage declining → re-engagement with tips and use cases
- Feature unused → feature education and activation prompt

#### Loyalty Triggers
- Milestone: Nth purchase → loyalty reward + thank you
- Review submitted → thank you + referral program invite
- Referral made → reward notification + social sharing prompt
- Birthday/anniversary → personal celebration + special offer

### For Each Trigger
- Trigger condition (specific event or behavior)
- Delay/timing: when to send after the trigger fires
- Suppression rules: don't send if X, Y, or Z
- Email content: subject, body, CTA (brief outline)
- Success metric: what defines this trigger email as successful
- A/B test: what to test first for optimization

### Technical Architecture
- Event tracking requirements: what user events need to be captured
- Data integration: website, app, CRM, purchase history, support tickets
- ESP/CDP setup: recommended tools and integration approach
- Conflict resolution: what happens when multiple triggers fire simultaneously

## OUTPUT FORMAT
Complete trigger system diagram with trigger conditions, email briefs, timing, suppression rules, and technical requirements.

## CONSTRAINTS
- Maximum 1 triggered email per user per 24 hours (avoid bombardment)
- All triggers must have suppression rules to prevent irrelevant sends
- Comply with consent requirements: only send to opted-in contacts
- Include a preference center for users to control which triggers they receive
- Monitor trigger volume: alerts if any trigger fires at abnormal rates