# 5. Campaign Analytics

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 5. Campaign Analytics

### 5.1 Track Redemptions per Code
**What it does:** Tracks the redemptions per code: the redemptions of the discount codes (the number of redemptions, the period, the code) are tracked, so the code usage is visible (the redemptions are recorded). The Super Administrator views the redemptions per code (the code, the redemptions, the period) so the tracking is structured and the redemptions are explicit.

**Sub-features:**
- Redemption tracking: the tracking (the code, the redemptions, the period)
- Redemption scope: the scope (the code, the redemptions)
- Redemption count: the count (the number of redemptions per code)
- Redemption period: the period (the period of the redemptions)
- Redemption view: the view (the redemptions per code, per period)
- Redemption record: the redemptions recorded (the code, the redemptions, the period)
- Audit logging of the redemption tracking

**Super Administrator User Journey:**
1. Super Admin views the redemptions per code: the codes (the discount codes), the redemptions (the number of redemptions per code), and the period (the period of the redemptions); the redemptions are explicit.
2. Sets the redemption scope: the scope (the code, the redemptions); the scope is the tracking.
3. Views the redemption count: the count (the number of redemptions per code); the count is the metric.
4. Views the redemption period: the period (the period of the redemptions); the period is the timing.
5. The redemptions are visible: the redemptions per code, per period, so the tracking is complete.
6. For a code (a specific discount code), Super Admin views the code's redemptions (the count, the period, the trend); the redemptions are the detail.
7. Exports the redemptions (the redemption report, the period); the export is the record.
8. The redemption tracking is audit-logged with the code, the redemptions, and the timestamp.

**Rules & Edge Cases:**
- The redemption tracking is explicit (the code, the redemptions, the period); the tracking is the visibility.
- The redemption scope is the code and the redemptions; the scope is the control.
- The redemption count is the metric (the number of redemptions per code); the count is the measure.
- The redemption period is the timing (the period of the redemptions); the period is the context.
- The redemptions are visible (the redemptions per code, per period); the tracking is managed.
- Redemption tracking is audit-logged with the code, redemptions, and timestamp.

### 5.2 Measure Campaign Performance
**What it does:** Measures the campaign performance: the performance of the campaigns (the reach, the engagement, the conversion, the revenue) is measured, so the campaigns are evaluated (the performance is recorded). The Super Administrator views the campaign performance (the campaign, the reach, the engagement, the conversion, the revenue) so the measurement is structured and the performance is explicit.

**Sub-features:**
- Performance measurement: the measurement (the campaign, the reach, the engagement, the conversion, the revenue)
- Performance scope: the scope (the campaign, the performance)
- Reach metric: the reach (the number of users reached)
- Engagement metric: the engagement (the clicks, the opens)
- Conversion metric: the conversion (the enrollments, the redemptions)
- Revenue metric: the revenue (the revenue per campaign)
- Audit logging of the performance measurement

**Super Administrator User Journey:**
1. Super Admin views the campaign performance: the campaigns (the promotional campaigns), the reach (the number of users reached), the engagement (the clicks, the opens), the conversion (the enrollments, the redemptions), and the revenue (the revenue per campaign); the performance is explicit.
2. Sets the performance scope: the scope (the campaign, the performance); the scope is the measurement.
3. Views the reach metric: the reach (the number of users reached); the reach is the audience.
4. Views the engagement metric: the engagement (the clicks, the opens); the engagement is the interaction.
5. Views the conversion metric: the conversion (the enrollments, the redemptions); the conversion is the outcome.
6. Views the revenue metric: the revenue (the revenue per campaign); the revenue is the value.
7. Exports the performance (the performance report, the period); the export is the record.
8. The performance measurement is audit-logged with the campaign, the metrics, and the timestamp.

**Rules & Edge Cases:**
- The performance measurement is explicit (the campaign, the reach, the engagement, the conversion, the revenue); the measurement is the visibility.
- The performance scope is the campaign and the performance; the scope is the control.
- The reach metric is the audience (the number of users reached); the reach is the measure.
- The engagement metric is the interaction (the clicks, the opens); the engagement is the measure.
- The conversion metric is the outcome (the enrollments, the redemptions); the conversion is the measure.
- Performance measurement is audit-logged with the campaign, metrics, and timestamp.

### 5.3 Revenue Attribution to Promotions
**What it does:** Attributes the revenue to the promotions: the revenue is attributed to the promotions (the revenue per promotion, the promotion's contribution), so the promotions are evaluated (the revenue is recorded per promotion). The Super Administrator views the revenue attribution (the promotion, the revenue, the contribution) so the attribution is structured and the revenue is explicit.

**Sub-features:**
- Revenue attribution: the attribution (the promotion, the revenue, the contribution)
- Attribution scope: the scope (the promotion, the revenue)
- Revenue per promotion: the revenue (the revenue per promotion)
- Contribution metric: the contribution (the promotion's contribution to the revenue)
- Attribution view: the view (the revenue per promotion, per period)
- Attribution record: the attribution recorded (the promotion, the revenue, the contribution)
- Audit logging of the revenue attribution

**Super Administrator User Journey:**
1. Super Admin views the revenue attribution: the promotions (the promotional campaigns, the discount codes), the revenue (the revenue per promotion), and the contribution (the promotion's contribution to the revenue); the attribution is explicit.
2. Sets the attribution scope: the scope (the promotion, the revenue); the scope is the attribution.
3. Views the revenue per promotion: the revenue (the revenue per promotion); the revenue is the value.
4. Views the contribution metric: the contribution (the promotion's contribution to the revenue); the contribution is the share.
5. The attribution is visible: the revenue per promotion, per period, so the attribution is complete.
6. For a promotion (a specific campaign, a specific code), Super Admin views the promotion's revenue (the revenue, the contribution, the period); the revenue is the detail.
7. Exports the attribution (the attribution report, the period); the export is the record.
8. The revenue attribution is audit-logged with the promotion, the revenue, and the timestamp.

**Rules & Edge Cases:**
- The revenue attribution is explicit (the promotion, the revenue, the contribution); the attribution is the visibility.
- The attribution scope is the promotion and the revenue; the scope is the control.
- The revenue per promotion is the value (the revenue per promotion); the revenue is the measure.
- The contribution metric is the share (the promotion's contribution to the revenue); the contribution is the measure.
- The attribution is visible (the revenue per promotion, per period); the attribution is managed.
- Revenue attribution is audit-logged with the promotion, revenue, and timestamp.
