Configuration
AI 1-to-1 Delivery configuration defines the plan setup, the Coupons Bank, the objective inputs, and the validation rules required before Loyal Guru can generate campaigns.
Use Cases
| Use Case |
|---|
| -> Validate whether a Coupons Bank can be used for AI campaign generation. |
| -> Restrict an AI Plan to a pre-approved Audience. |
| -> Configure up-selling and cross-selling inputs before generation. |
How It Works
- The operator configures the plan-level fields.
- The Coupons Bank is loaded and validated.
- Valid coupons are grouped by product/category affectation.
- Objective-specific inputs tell the models which periods and Customer pools to use.
- Generation is blocked until required fields and coupon validation pass.
Configuration
| Area | Current capability |
|---|---|
| Plan description | Name, availability dates, printing range, non-printable coupons, and optional ROI calculation schedule |
| Business goals | Up-selling and Cross-selling are active. Churn and Increasing Frequency are visible as future goals but disabled in the current flow |
| Coupons Bank | Select discount/coupon IDs manually or import them from a CSV whose first column contains IDs |
| Budget / contribution | Budget used to size the audience and distribute coupon assignments when budget-based allocation is enabled |
| Restricted Audience | Optionally limit the whole AI Plan to one existing Audience |
| Up-selling period | Date range used by the PBS model to identify existing category buyers and split them by purchase behavior |
| Cross-selling periods | Recency windows used to target Customers who have not bought a category recently: 1, 3, 6, or 12 months, or never purchased |
| Cross-selling filters | Optional flags for Customers who bought in the last 12 months and active Customers |
| Advanced configuration | Plan-level overrides for up-selling percentile splits and cross-selling Customer selection threshold |
Coupons Bank
The Coupons Bank is the set of coupons or discounts the AI can distribute. Operators can paste IDs manually or import a CSV. The importer reads discount IDs from the first column and caps the import size to keep validation and generation manageable.
Before generation, the bank is normalized by product/category affectation. Coupons with compatible affectation are grouped together so the platform can create campaign actions per category or product group. Coupons that do not provide usable product/category scope are ignored or blocked during validation, depending on the issue.
Validation
The Coupons Bank must be validated before the plan can generate campaigns. Validation checks whether the selected IDs can be used for AI distribution.
| Validation outcome | What it means |
|---|---|
| No valid coupons | Blocking issue. The plan cannot be built if no selected IDs map to valid coupons |
| No product/category affectation | Blocking issue. The plan needs coupons tied to product category or product affectation |
| Cart-level affectation | Warning. Coupons with full-cart affectation are ignored for AI campaign generation |
| More than 5 coupons in one category group | Warning. Only up to 5 coupons are used for up-selling segments in that category |
| Duplicate discount and minimum purchase condition | Warning. When several coupons have the same discount and minimum condition, the backend keeps one and ignores the rest |
In the Owner App, validation results are shown in a modal with the coupon and the warning or ignored reason. Save and continue remains disabled until validation passes for the current form state.
Current Scope
This page documents the current AI 1-to-1 Delivery implementation and the Phase 0 Coupons Bank scope.
| Area | Current status |
|---|---|
| AI Plan creation/editing | Implemented |
| Coupons Bank import and validation | Implemented |
| Automatic campaign generation | Implemented through asynchronous generation after Save and continue |
| Plan-level Campaigns and Forecast tabs | Implemented |
| Campaign-level Audience and Forecast detail screens | Present in the app, but still evolving; use the plan-level Campaigns and Forecast tabs as the main operator reference |
| Budget-based audience sizing | Documented as the allocation model for Coupons Bank. UI/activation details may depend on rollout configuration |
| ROI tab | Planned/evolving for AI Plan detail; use the KPI definitions in Forecast and ROI to interpret actuals when available |
| Analysis / pre-post comparison tab | Planned for a later phase; route is not active in the current AI Plan detail |
| Automatic budget enforcement after launch | Future phase; budget allocation forecasts expected spend, but live enforcement and later automatic budget control remain separate rollout scope |
| Additional recipes | Future phases may include churn, frequency, automatic coupon creation, coupon scoring, and microsegmentation |