Campaigns
Overview
A campaign is the active configuration unit of the reward engine. It defines when a reward is granted, under which conditions, and for what amount. Campaigns are configured in the Otonum Rewards application. No API call is required to manage them.
Campaign Components
Each campaign is tied to one application (POS, e-commerce channel, or mobile app) and is active in a specific time window.
| Component | Description |
|---|---|
| Application | The integration scope where this campaign applies |
| Time Window | Start and end date. The campaign evaluates events only within this window |
| Trigger | Event that starts evaluation (for example purchase) |
| Rules | Conditions evaluated when trigger is received |
| Reward | Points or cashback granted when rules are satisfied |
Evaluation Lifecycle
When a member submits a purchase event, Otonum:
- Identifies all active campaigns for the application and trigger
- Evaluates each eligible campaign rules against transaction data
- Grants rewards for every campaign whose rules match
Processing is asynchronous. The purchase endpoint returns a taskId immediately, and reward calculation continues in the background. See Task Status.
Multi-Campaign Behavior
When multiple active campaigns match the same purchase event (same application, same trigger, active windows), all eligible rewards are granted. The member receives cumulative benefits from each applicable campaign.
Do not assume only one campaign will trigger per purchase. Design the customer experience to handle multiple rewards on the same transaction.
Tier Limits
The number of simultaneously active campaigns is limited by partner subscription tier:
| Capability | Starter | Classic | Plus |
|---|---|---|---|
| Active campaigns at once | 1 | 3 | 10 |
| Transaction history retention | 30 days | 90 days | 365 days |
Key Points
- Campaigns are application-scoped. A purchase submitted through app A does not trigger campaigns configured for app B.
- A campaign with no matching rule grants no reward but does not fail the transaction.
- Expired campaigns are ignored. End dates in the past are not evaluated.