# 3. Campaign Targeting

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

---

## 3. Campaign Targeting

### 3.1 Targeted Promotions by User Segment
**What it does:** Sets the targeted promotions by user segment: the promotions are targeted to the user segments (the new users, the returning users, the lapsed users, the high-value users), so the promotions are relevant (the segment gets the offer that fits them). The Super Administrator defines the segment targeting (the segment, the offer, the period) so the targeting is structured and the segments are explicit.

**Sub-features:**
- Segment definition: the segment (the new users, the returning users, the lapsed users, the high-value users)
- Segment scope: the scope (the segment, the promotion)
- Segment offer: the offer (the discount, the freebie)
- Segment period: the period (the start, the end)
- Targeting definition: the targeting defined by the Super Admin (the segment, the offer, the period)
- Targeting application: the targeting applied (the segment gets the offer)
- Audit logging of the targeting definition and the application

**Super Administrator User Journey:**
1. Super Admin defines the segment targeting: the segment (the new users, the returning users, the lapsed users, the high-value users), the offer (the discount, the freebie), and the period (the start, the end); the targeting is explicit.
2. Sets the segment scope: the scope (the segment, the promotion); the scope is the segment.
3. Sets the segment offer: the offer (the discount, the freebie); the offer is the value.
4. Sets the segment period: the period (the start, the end); the period is the timing.
5. Saves; the segment targeting is live, and the segment gets the offer (the targeting is applied).
6. For a targeting change (the segment, the offer, the period updated), Super Admin changes the targeting (the new segment, the new offer, the new period); the change is recorded.
7. Tracks the targeting: the performance (the redemptions, the revenue per segment), so the targeting is visible.
8. The targeting definition and the application are audit-logged with the segment, the offer, and the timestamp.

**Rules & Edge Cases:**
- The segment is explicit (the new users, the returning users, the lapsed users, the high-value users); the segment is the audience.
- The segment scope is the segment and the promotion; the scope is the control.
- The segment offer is the value (the discount, the freebie); the offer is the incentive.
- A targeting change (the segment, the offer, the period updated) is recorded (the new segment, the new offer, the new period); it is auditable.
- The segment targeting is visible (the segments, the offers, the periods, the performance); the targeting is managed.
- Targeting definition and application are audit-logged with the segment, offer, and timestamp.

### 3.2 Personalized Course Recommendations
**What it does:** Sets the personalized course recommendations: the recommendations for the users (the courses that fit the user's profile, the user's history) are set, so the promotions are personalized (the user gets the courses that fit them). The Super Administrator configures the recommendation rules (the profile, the history, the courses) so the personalization is structured and the recommendations are explicit.

**Sub-features:**
- Recommendation rule: the rule (the profile, the history, the courses)
- Recommendation scope: the scope (the user, the recommendations)
- Recommendation profile: the profile (the user's profile, the user's interests)
- Recommendation history: the history (the user's history, the user's courses)
- Recommendation courses: the courses (the courses that fit the user)
- Rule definition: the rules defined by the Super Admin (the profile, the history, the courses)
- Audit logging of the recommendation rules and the applications

**Super Administrator User Journey:**
1. Super Admin configures the recommendation rules: the profile (the user's profile, the user's interests), the history (the user's history, the user's courses), and the courses (the courses that fit the user); the rules are explicit.
2. Sets the recommendation scope: the scope (the user, the recommendations); the scope is the user.
3. Sets the recommendation profile: the profile (the user's profile, the user's interests); the profile is the basis.
4. Sets the recommendation history: the history (the user's history, the user's courses); the history is the context.
5. Saves; the recommendation rules are live, and the recommendations are personalized (the user gets the courses that fit them).
6. For a rule change (the profile, the history, the courses updated), Super Admin changes the rules (the new profile, the new history, the new courses); the change is recorded.
7. Tracks the recommendations: the performance (the clicks, the enrollments per recommendation), so the recommendations are visible.
8. The recommendation rules and the applications are audit-logged with the user, the profile, and the timestamp.

**Rules & Edge Cases:**
- The recommendation rule is explicit (the profile, the history, the courses); the rule is the structure.
- The recommendation scope is the user and the recommendations; the scope is the control.
- The recommendation profile is the basis (the user's profile, the user's interests); the profile is the input.
- A rule change (the profile, the history, the courses updated) is recorded (the new profile, the new history, the new courses); it is auditable.
- The recommendations are visible (the users, the profiles, the histories, the courses, the performance); the personalization is managed.
- Recommendation rules and applications are audit-logged with the user, profile, and timestamp.

### 3.3 A/B Testing for Campaigns
**What it does:** Sets the A/B testing for the campaigns: the A/B tests for the campaigns (the variant A, the variant B, the split, the metric) are set, so the campaigns are tested (the variants are compared). The Super Administrator defines the A/B tests (the variant A, the variant B, the split, the metric) so the testing is structured and the tests are explicit.

**Sub-features:**
- A/B test: the test (the variant A, the variant B, the split, the metric)
- Test scope: the scope (the campaign, the test)
- Variant A: the variant (the variant A, the offer A)
- Variant B: the variant (the variant B, the offer B)
- Test split: the split (the split of the users, e.g., 50/50)
- Test metric: the metric (the metric, e.g., the conversion rate)
- Audit logging of the A/B test definition and the results

**Super Administrator User Journey:**
1. Super Admin defines the A/B test: the variant A (the offer A), the variant B (the offer B), the split (the split of the users, e.g., 50/50), and the metric (the metric, e.g., the conversion rate); the test is explicit.
2. Sets the test scope: the scope (the campaign, the test); the scope is the campaign.
3. Sets the variant A: the variant (the variant A, the offer A); the variant is the control.
4. Sets the variant B: the variant (the variant B, the offer B); the variant is the test.
5. Saves; the A/B test is live, and the test is running (the variants are compared, the metric is tracked).
6. For a test change (the variant A, the variant B, the split, the metric updated), Super Admin changes the test (the new variant A, the new variant B, the new split, the new metric); the change is recorded.
7. Tracks the test: the results (the metric per variant, the winner), so the test is visible.
8. The A/B test definition and the results are audit-logged with the campaign, the variants, and the timestamp.

**Rules & Edge Cases:**
- The A/B test is explicit (the variant A, the variant B, the split, the metric); the test is the structure.
- The test scope is the campaign and the test; the scope is the control.
- The variant A is the control (the offer A); the variant is the baseline.
- A test change (the variant A, the variant B, the split, the metric updated) is recorded (the new variant A, the new variant B, the new split, the new metric); it is auditable.
- The A/B tests are visible (the campaigns, the variants, the splits, the metrics, the results); the testing is managed.
- A/B test definition and results are audit-logged with the campaign, variants, and timestamp.