Skip to main content

Why use shopper missions?

Shopper missions turn several customer actions into one visible challenge. Instead of asking customers to notice separate campaigns, you package those actions into a short-term goal with a clear reward at the end.

Business outcomes

Shopper missions are useful when you want to turn several smaller customer actions into one clearer commercial proposition. Instead of relying on customers to discover separate campaigns on their own, you give them a time-boxed challenge with visible progress and one reward at the end. That can increase repeat visits, support profile completion or product discovery goals, and make a group of related campaigns feel like one coordinated experience rather than a scattered set of incentives.

When this solution works best

This solution works best when you already know which customer behaviours matter most and those behaviours can be combined into a sequence that feels achievable. Weekly, weekend, and seasonal challenges are strong fits because the mission window is easy to understand and the customer can quickly judge whether the reward is worth the effort. It is also a strong fit when you use Spaaza Embed Elements or apps and want customers to see the wallet and the related task campaigns in one place.

Tradeoffs and risks

The tradeoff is that missions need more coordination than a single campaign. The wallet, its threshold rule, the audience settings, and every contributing campaign all need to line up properly. If the reward is too weak, customers may see the mission as unnecessary effort. If the task list is too long or the copy is not clear, the mission can feel slow or confusing. The presentation layer matters as well: even a well-configured mission can underperform if the page placement, imagery, or explanatory copy does not make the value obvious.

Design choices to make up front

The most important design decision is choosing one commercial objective and building the mission around it. A mission should feel coherent to the customer, so the tasks should support the same outcome rather than mixing unrelated asks. The number of campaigns should normally match the wallet threshold, the audience logic should be applied consistently across the wallet and each task campaign, and the mission length should match the effort required. It is also worth planning the customer-facing presentation at the same time as the campaign setup, especially if the mission will be shown in Embed Elements or apps.

Why this mechanic tends to work

Missions tend to work because they make progress legible. Customers can see how many steps are complete, how many remain, and what they will receive when they finish. That visible progress helps the reward feel closer and gives the activity a stronger narrative than a set of disconnected campaigns. In practice, this mechanic is strongest when the mission feels achievable inside the stated time window and when each task is easy to understand.