A campaign is one moment. A coupon blast, a spin to win, a single quiz. A challenge is a series of small tasks the user does over a week or a month, with a progress bar and a prize at the end. Challenges bring users back many times. Campaigns bring them back once, if at all.
- A campaign is one moment. A challenge is something the user does over many days. They are different products. Don't measure them the same way.
- Challenges bring people back many times. A campaign brings them back once, if at all.
- The reason challenges work: people don't want to waste effort they've already put in, they want a reason to come back tomorrow, and after a few days the habit starts to feel like part of who they are.
- A good challenge has 3 to 7 small tasks, a visible progress bar, small rewards along the way, a clear end date, and a moment the user can share when they finish.
- Don't force a challenge on a behaviour the user only does once. Fake engagement burns trust faster than no engagement.
What is the difference between a campaign and a challenge?
Most teams use these two words to mean the same thing. That is half the problem. A campaign and a challenge are different products. Different design rules. Different ways to measure success.
If you measure them the same way, the campaign will look like the winner. Campaigns peak hard on day one. But on the right window, the picture flips.
A campaign is one moment in time. The user lands, takes one action, gets one reward, and leaves. A Diwali discount email. A paid Meta ad to a landing page. A one screen spin to win. A flash sale. A giveaway form. All campaigns. When you do them well, they convert hard in a small window. Then it's quiet.
A challenge is a small program. The user signs up, works through a series of tasks, sees their progress every time they return, hits small wins along the way, and earns a big prize at the end. A 7 day fitness sprint. A 30 day spend challenge. A 5 step product discovery arc. An IPL season prediction game. The engagement is not one spike. It is a steady line with bumps.
Why does this matter for your work? Because everything around the surface changes. Campaigns are built for first sale, reach, and creative. Challenges are built for repeat visits, progress, and reward timing. A campaign sent to a challenge audience will feel thin. A challenge launched like a campaign will feel like homework.
Five things that are different. Two very different products.
| What changes | Campaign | Challenge |
|---|---|---|
| How long it runs | Minutes to a few hours | Days to weeks |
| How many times user comes back | 1 | 5 to 15 |
| Will the user return | Usually no. They convert once and leave. | Yes. Each new step is a reason to return. |
| What data you get | One action, one snapshot. | A full picture of behaviour, preferences, and effort. |
| Effect on retention | Lifts one conversion. | Builds a habit and a reason to stay. |
What changes
How long it runs
What changes
How many times user comes back
What changes
Will the user return
What changes
What data you get
What changes
Effect on retention
A campaign is a spike. A challenge is a steady line.
Picture a 14 day window. The campaign hits once and goes quiet. The challenge keeps the user coming back. Each new step is a reason to open the app tomorrow.
Shapes are for illustration. Actual numbers depend on your audience, category, and rewards.
Why do challenges drive more engagement than campaigns?
Three things are doing the work. None of them happen in a one tap campaign. If you remember nothing else from this post, remember these three.
1. People don't want to waste effort they've already put in.
Once a user has done 2 of 7 tasks, they feel like quitting now would throw away the work. Think about your own behaviour. If you've used a fitness app for 6 days, you'll open it on day 7 just to keep the run going. If you haven't started, day 1 feels like work.
A campaign can't create this feeling. There is nothing to be half way through. You either took the action or you didn't. A challenge with 5 tasks where the user has done 2 puts them in a totally different mental space than an empty screen.
2. Every new step is a reason to come back tomorrow.
The mid week WhatsApp ping that says “You are more than half way to your prize, 3 days left” is the most under used message in marketing. A campaign sends one message, gets one click, books one sale. A challenge has 5 to 10 natural moments to message the user. Each one is tied to a real piece of progress they earned. Each one is actually about them, not about your brand.
3. After a few days, this becomes part of who they are.
This one is the deepest. By task 5 of a 7 task challenge, the user starts to see themselves as someone who does this thing. Someone who finishes workouts. Someone who reads daily. Someone who saves consistently. Identity sticks in a way that a one time discount never can. The brand that helps a user become someone owns the next ten years of their behaviour. The brand that gave them 15% off owns one sale.
Put these three together and the math gets ugly for campaign only programs. A campaign gives you one visit and one sale. A challenge gives you 5 to 15 visits, 3 to 5 reward moments, a habit, and a user who walks out the other side feeling different about your brand. The cost of running one good challenge is roughly the cost of running one good campaign. The output is on a different level.
The shape of this line is the whole story.
A campaign shows up once, makes noise, and disappears. A challenge gives the user a reason to come back tomorrow, and the day after that. The orange line is what turns into long term retention.
What does a good challenge look like?
Challenges fail in the same ways every time. Most failures come from missing one of the six parts below. The good news is each one is cheap to add and easy to get right the second time around.
- Tasks. 3 to 7 small actions the user can do. Each one stands on its own. Don't make task 3 depend on task 2. The user should be able to start with whichever one feels easiest.
- Progress bar. A clear bar or map. Shown on the home screen every visit. Not buried in a tab. The bar is the product. If users have to hunt for their own progress, you've lost them.
- Mini rewards. Small wins at around 30%, 60%, and 100%. Three mini rewards is the magic number. Not just one big prize at the end. A challenge with only one final prize behaves like a campaign because users feel no win in the middle.
- An end date. 7 days, 14 days, the month of Diwali. Open ended challenges die because there is no urgency to come back today. The clock is the difference between “I'll do it when I get a chance” and “I have 4 days left.”
- A final prize. The big reward at the end. Bigger than any mini reward. Name it clearly. “A recovery kit” works better than “a special surprise.”
- A share moment. Something the user can post or screenshot when they finish. A badge, a card, a leaderboard rank. People want their friends to see they finished.
One detail worth flagging: the spacing of the three mini rewards. The 30% reward tells the user “this system actually pays out.” The 60% reward locks them in. They are more than half way and the sunk cost of quitting feels real. The final reward is the headline. Get any of these three wrong and the curve dips in a very specific spot.
Six parts. Skip any one and the whole thing falls flat.
The mockup on the left shows where each part lives on a real challenge screen. The notes on the right say what each part is doing.
- Log a cardio session
- Hit 8,000 steps in a day
- Try a new class
- Log a strength workout
- Share a finished session
- Tasks
3 to 7 small tasks. Each one can be done on its own. No task waits for another.
- Progress bar
Always on the home screen. Not hidden in some sub-menu. The bar is the whole product.
- Mini rewards
Small wins at around 30%, 60%, and 100%. Each one is a reason to keep going.
- End date
Pick a clear window. 7 days, 30 days, the month of Diwali. Open ended challenges die quietly.
- Final prize
The big reward at the end. Bigger than any mini reward. This is what people are chasing.
- Share moment
Something to post or screenshot at the end. A badge, a card, a rank. People want their friends to see they finished.
What kinds of challenges actually work?
Three patterns show up again and again in apps and brand programs that hold on to their users. Each one is a tool, not a default. Pick the one that fits the behaviour you want.
Streak challenges. One small action every day. The user shows up because their run is on the line. These work for habits people actually do daily: fitness logging, language learning, daily savings, daily journaling, news.
The most important rule: allow at least one freeze day. One missed day should not kill a 30 day run. The moment a user feels the loss, most of them quit instead of starting over. The Duolingo Streak Freeze is the classic example. The mistake brands make is forcing daily check ins on a behaviour that only matters once a week. The streak becomes fake. The user feels played. You lose them and their trust.
Collection challenges. Try N different things. Try 5 product categories. Watch 7 short videos. Order from 3 different cuisines. These work for product discovery and content libraries. You want the user to see more of your product, not just the corner they already know.
The most important rule: every task should be reachable in 2 taps. Hidden tasks kill the loop. If the user has to ask “how do I even do that one?”, they won't. The mistake brands make is listing 15 tasks because the catalog has 15 things. 5 to 7 is the sweet spot. More feels like a homework assignment.
Leaderboard challenges. Compete against other users. This week's top runners. This month's top savers. The IPL prediction season. These work when your audience actually likes to compete and the board is bracketed, not global.
The most important rule: show 5 people above the user and 5 below. Never the global top 10. A user at rank 4,712 looking at the global top 10 sees an unreachable wall and quits. The same user looking at ranks 4,707 to 4,717 sees two people to catch and two to defend against. Engagement spikes. The mistake brands make is one global board with a weekly reset that becomes the same 5 power users every week. Everyone else churns.
You can layer two patterns once the base one is working. A collection challenge with a streak add on (“try one new category each day”) is a strong second version. A leaderboard on top of a streak (“longest active streak this month”) creates a community moment without grinding new users. Don't try to layer all three at launch. You'll ship a confusing screen that nobody fully understands.
Pick the pattern that fits the behaviour you actually want.
When should you NOT use a challenge?
Challenges are a strong tool. They are not the right tool for every job. Four times when a campaign or something else is the honest answer.
One shot sale moments. Big Billion Day. Diwali flash sales. A 24 hour discount window. The whole point is concentrated urgency. A challenge spreads the sale over days and kills that urgency. Use a campaign for the sale. You can use a challenge to warm the audience up before the sale, but not to deliver the offer itself.
Users who already show up every day. If your power users open the app daily and buy at a high rate, layering a challenge on top can feel like extra work. They were going to do it anyway. Now you're asking them to opt in and be tracked for something they already do. Use challenges for the next layer down. The users you wish would behave like your power users.
Behaviours that should not be daily. A 5 minute mutual fund app probably wants a weekly check in, not a daily one. Forcing daily activity on a quarterly product creates fake usage. The user starts doing things that don't actually help them. The metric goes up briefly, then they leave and don't return. Pick the right cadence first, then design the challenge around it.
Wrong brand tone. Formal B2B, healthcare, regulated finance, professional services. These audiences often read streaks and leaderboards as gimmicky and lose trust. The mechanic still works, but dress it differently. Progress checklists, certification paths, onboarding journeys. Same engine, different wrapper. Don't ship streaks to an audience that came for serious advice.
Be honest. A challenge is the wrong tool in these cases.
Four ways teams break their own challenges.
How to measure a challenge
Most challenge programs die because someone measures them like a campaign. Open rate and click rate are the wrong tools. The numbers below are what tell you if the program is actually working.
Sign up rate. Out of the people who saw it, how many opted in. In app banners do well. A cold email to a stale list will land lower. If sign ups are very low, your offer or your headline is off. If they are strong, ship the next one.
Step by step drop off. Where users quit between tasks. The shape tells you exactly which task is broken. Heavy drop off between task 1 and task 2 means task 2 is too hard or the reward there is too small. Drop off between 4 and 5 means you stretched the final prize too far without a mini reward in between.
Average finish percent. How far the middle user gets. For a 30 day program, try to get most users past task 2 at least. If almost nobody finishes, the program is too long or too hard. If almost everybody finishes, your rewards are too generous and you're leaving margin on the table.
Visits per active user. How many times the user opens the app during the challenge. This is the main number to compare against a normal campaign. A campaign gives you close to one visit per buyer. A working challenge gives you several. If yours is barely above the campaign baseline, you've built a campaign with a progress bar bolted on.
Retention 30 days later. Do finishers stick around, compared to non finishers and to a control group who never saw the challenge. The long term effect lives here. Finishers should retain noticeably better than non finishers. Both should retain better than the control group. If finishers and the control group look the same, you made motion but you didn't change behaviour.
Revenue lift. Money per user from challenge participants vs a holdout group that was never enrolled. Always keep a holdout. Otherwise your finance team won't trust the number and you'll be arguing about attribution at the worst possible moment.
Six numbers to track. Forget the rest.
How Bricqs runs challenges
Bricqs ships challenges as a core building block. Tasks, mini rewards, progress, leaderboards, rewards, and the messages around them are all wired together in one engine. A builder for the marketing team. An API for the product team. Companies plug Bricqs into their app, website, or microsite to run challenges without building the plumbing themselves. Sign ups, rewards inventory, fraud and budget checks, audit log, reports. All of it lives in one place.
Most teams start with one 7 or 14 day challenge on top of a familiar mechanic (a points balance or a streak), then add collection and leaderboard formats once they have the data to know what their audience responds to. The progression and reward parts are covered in the points systems guide and the reward systems guide. If you want to see where challenges sit in a wider retention stack, the solutions overview is the right place to start.
Quick answers to the questions teams ask first.
What is the difference between a campaign and a challenge?
A campaign is one moment. A coupon blast, a spin to win, a quiz the user does once. A challenge is a series of small tasks spread over many days, with a progress bar, mini rewards, and a final prize. Campaigns drive one sale. Challenges drive many visits and build a habit.
Why do challenges keep people coming back?
Three reasons. First, once a user has done 2 of 7 tasks, they don't want to waste the effort. Second, each new task is a reason to open the app tomorrow. Third, after a few days, the user starts to see themselves as someone who does this thing, and that identity sticks.
How long should a challenge run?
Match it to the behaviour. 7 days for a quick sprint or a festival push. 14 to 21 days for building a habit. 30 days for a monthly cycle that lines up with a billing date or a content drop. Avoid open ended challenges. Without an end date, users don't feel any urgency to come back today.
How many tasks should a challenge have?
3 to 7. Three is fine for short sprints. Seven is the limit before users see it as a homework list. New teams often try 12 to 15 tasks on the first try and watch sign ups crash.
Do challenges work for B2B audiences?
Yes, but turn down the game feel. For B2B, call it a progress checklist, a certification path, or an onboarding journey. Same engine, different words. Sales teams, partner programs, and customer success teams have used this format for years.
What is the easiest challenge to launch first?
A 7 day collection challenge with 5 tasks, one mid week reminder, and one reward at the end. It tells you if your audience will come back for mini wins, before you spend more time building a 30 day program with streak protection and leaderboards.
How do challenges fit with my existing tools?
Most teams run challenges through an engagement and retention platform that handles the tasks, progress, rewards, and reporting. Activity flows back into your CRM, email tool, and analytics. The challenge engine is the new piece. The rest of your stack stays the same.
Related reading: the psychology of streaks, designing progression systems, from campaigns to journeys.
