Skip to main content

Challenges

Challenges let customers pursue a measurable goal over time with a clear progress bar. You configure the progress metric, the milestone(s), and the prizes on the challenge itself. Use a single milestone for one finish line and one prize set, or a progressive challenge for the same metric with several escalating thresholds — each unlocking its own prize. That prize can be a discount, points, a reward/gift, or access to another game mechanic. Challenges drive purchase frequency, category engagement, and non-purchase participation with a simple "complete the goal, win the prize" mechanic.

Use Cases​

Use Case
→ Run 100 km in a month and earn 1,000 points, using a calculated attribute fed by a fitness tracker integration.
→ Spend €500 in November and earn 500 bonus points.
→ Progressive monthly spender: spend €50 → +25 points, €120 → +75 points, €200 → €5 coupon — same metric, three rewards.
→ Buy 10 units of a specific product category within 3 months and receive one reward/gift.
→ Visit the store 3 times within 30 days and win 100 points.
→ Progressive visit ladder: 2 visits → +25 points, 4 visits → 5% off next purchase, 7 visits → €10 gift card.
→ Buy from 5 different product categories this quarter and receive one reward from the catalog.
→ Complete 100 minutes of sport activity in a week and win 50 points.
→ Complete 5 app check-ins in a month and receive one reward.
→ Make 3 carts of at least €50 this month and earn a fixed points bonus.
note

Each challenge tracks one customer attribute (the progress metric). Choose Single milestone (one threshold and its prizes) or Progressive (2–5 strictly increasing thresholds on the same metric, each with its own prizes). Prizes are selected on the challenge when you create it. Raffles, multi-action journeys (different actions in one challenge), or unlocking an ongoing benefit are not part of the current Challenges mechanic.

How It Works​

  1. You define a challenge with one customer attribute as the progress metric, a format (single milestone or progressive), one or more thresholds, prizes per level, and a validity window.
  2. Customers participate — either automatically or by opting in (enrollment-required mode).
  3. The platform tracks progress whenever the underlying customer attribute is recalculated.
  4. When a customer's attribute value reaches a threshold, that level is marked as won. On a progressive challenge, crossing several thresholds in one calculation awards every level crossed in that run.
  5. The prizes configured on that level are delivered: discount, points, reward/gift (catalog + targeted — appears in the customer's personalized catalog to redeem; never auto-redeemed), or access to another game mechanic.

Targeted Delivery and Dates​

When a Challenge is delivered through Targeted Delivery, the delivery schedule and the Challenge dates are separate controls:

Date controlWhat it means
Challenge availability datesThe period when the Challenge is active and can be won.
Challenge display datesThe period when the Challenge can appear in the app catalogue.
Expiration policyWhen a won Challenge resets so the Customer can attempt it again.
Targeted Delivery recurrenceWhen the Audience receives or is reminded about the Challenge.

A recurrent Targeted Delivery does not extend the Challenge availability window. If the Challenge should run every week for a month, the Challenge must be active for the full monthly period and its progress/expiration setup must support the weekly cadence. Otherwise, a weekly send can target Customers with a Challenge that is no longer active, visible, or available to win.

Example: 6-month Challenge with monthly Targeted Delivery​

Say you want a Challenge that customers can participate in from January through June, and a Targeted Delivery that assigns or reminds them once a month during those six months.

LayerExample configuration
Challenge availability1 Jan – 30 Jun (the full six months — not only the first send date)
Challenge displaySame window, or slightly earlier if you want the Challenge visible before the first send
Targeted DeliveryMonthly recurrence, six sends (e.g. 1st of each month, Jan–Jun)
Progress (Calculated Attribute)Match how often customers should complete the goal. For a once-per-month goal, use a monthly period (e.g. current_month). For one continuous goal across the six months, use a period that covers the whole window.
Expiration policyFor once-per-month wins: reset at the end of the calculation window (or end of the next window) so customers can win again each month. For a single win in six months: use months/days after winning, or leave the Challenge to end with its availability.

If availability were only January, the February–June sends would still run, but customers could not win the Challenge in those months. The monthly send does not create a new Challenge or extend availability by itself.

Configuration​

Go to Gamified Campaigns → Challenges → New Challenge in the Owner App.

Documentation​

PageTopics
How Challenges WorkTracking, enrollment, expiration, API endpoints, progress bar
Create a ChallengeEnd-to-end setup: Calculated Attribute, format, levels, prizes on the challenge, and test progress
PrizesSelect prizes on the challenge (points, discount, reward/gift, game)
ConfigurationField reference and advanced settings
Edit or Delete a ChallengeEditing rules by challenge state, deactivation vs. deletion