StackedCompletion Conditions
Defining how users complete offers and earn rewards
What are Completion Conditions?
Completion conditions define what actions a user must take to complete an offer and claim rewards. While surfacing conditions determine WHO sees an offer, completion conditions determine HOW they finish it.
Multiple conditions can be combined - all must be met for the offer to become claimable.
Available Conditions
Completion conditions define specific actions users must take to claim rewards:
Buy Item
Users must purchase a specific item.
| Parameter | Description |
|---|---|
| Item ID | The specific item to purchase |
| Item Name | Display name for the item |
| Amount (optional) | Number of items required (default: 1) |
Spend Currency
Users must spend a certain amount of any currency.
| Parameter | Description |
|---|---|
| Currency ID | The currency type (e.g., gold, gems) |
| Currency Name | Display name for the currency |
| Amount | Total amount to spend |
Deposit Currency
Users must add currency to their account (typically via purchase).
| Parameter | Description |
|---|---|
| Currency ID | The currency type to deposit |
| Currency Name | Display name for the currency |
| Amount | Total amount to deposit |
Login
Users must log in (simple boolean check).
| Parameter | Description |
|---|---|
| Login | Must log in (true/false) |
Shared Conditions
These conditions work for both surfacing and completion:
| Condition | Description |
|---|---|
| Login Streak | Consecutive login days required |
| Levels | Reach a specific level or skill |
| Currencies | Have certain currency balance or spend/deposit amounts |
| Achievements | Complete an achievement |
| Quests | Finish a quest |
| Memberships | Obtain a membership |
| Staked Tokens | Stake cryptocurrency tokens |
| Trust Score | Reach reputation threshold |
| Days in Game | Minimum days the user has logged in |
See Surfacing Conditions for parameter details.
Note
Tags and Dynamic Fields are only available for surfacing conditions, not completion conditions.
How Conditions Combine
Multiple completion conditions use AND logic - all must be met for the offer to become claimable.
Example: An offer requiring "Buy 3 health potions" + "Reach level 10" + "Login 3 days straight" needs all three actions completed.
How Progress Works
Stacked automatically tracks progress in real-time:
- Offer Surfaces → User meets surfacing conditions
- Tracking Begins → Stacked monitors relevant actions
- Progress Updates → Each action updates completion trackers
- Threshold Met → Offer becomes "claimable"
- User Claims → Rewards distributed
Tip
Show progress clearly with visual indicators. Users complete offers more often when they can see how close they are to the goal.
Examples
Here are practical examples of combining completion conditions:
Starter Bundle Quest
New player engagement
- Buy Item: "health_potion", Amount = 3
- Spend Currency: "gold", Amount = 100
- Login Streak: 2 days
New players must buy health potions, spend gold, and log in twice to complete.
Level Up Challenge
Progression milestone
- Level (player_level): Min = 10
- Achievement ("tutorial_complete"): Min Count = 1
- Login: true
Users must reach level 10, complete tutorial achievement, and log in to claim.
First Purchase Bonus
Monetization conversion
- Deposit Currency: "gems", Amount = 100
- Min Days in Game: 3
Users who've been playing for 3+ days and deposit 100 gems get bonus rewards.
Daily Spending Goal
Economy circulation
- Spend Currency: "gold", Amount = 500
- Login Streak: 1
Daily challenge requiring 500 gold spent and logging in.
Best Practices
- Match effort to reward - Higher requirements need better rewards
- Show progress clearly - Visual indicators improve completion rates
- Test with real users - Monitor completion rates and adjust
- Allow reasonable time - Consider user schedules and play patterns