Create challenge¶

Create a challenge activity by completing five simple steps in the Creation Wizard.

Activity details¶

Here you configure the general details of the activity - Activity name, Start date, End date, Display priority, Chains or stores, and also Template switcher is present.

You can save a draft activity by just filling in the Activity name and validity dates. The Create button will be enabled and you can save the activity and resume the configuration at a later time.

Activity Name is used to identify and locate activities in the Lobyco Portal. Unique names aren't required, but a naming convention is recommended (e.g., 2024_week_42_43_Buy10Get1milk).

Start date and End date determine the visibility of the Challenge in the App and tracking of progress based on member purchases.

It's good practice to start activities at 00:01 and end at 23:59 to avoid confusion and track in an easier way.
Even though the challenge end date supports past dates, we recommend not creating them with start times in the past.
If the challenge is created inside a campaign, the start date and end date need to be inside the campaign dates. The campaign start date and end date are shown under the dates input fields.

Display priority defines the order of the challenge in the App, compared with other challenges.

Allows values from 1 to 10, where 1 is the highest priority and is shown first. By default it is 5, so all challenges are medium priority and you can always create some higher or lower priority challenges that are shown before or after them.
Challenges with the same priority keep the default sorting order in the App.
Display priority is a required field and applies to both Standard and Tiered challenges.
It can be changed at any time, including on an active challenge, to reorder challenges in the App.

📝 Note: Challenges created before this setting was introduced are treated as priority 5 until they are edited.

Chain IDs or Store IDs¶

Select where the offer is valid, either in chains or stores.
Chains and stores cannot be selected simultaneously. If you choose one or more chains, the store selector will automatically be disabled, and vice versa.
Press the up arrow from the store field to upload a store list. The file needs to be in CSV format, with one store ID per line.
Once one or more stores are selected, press the down arrow to download the list of selected stores in CSV format.

Reward settings¶

In this tab, you can select a reward for completing the challenge — either a Coupon or a Bonus.

Reward Type allows you to select the type of challenge. Challenges with lotteries (2&3) are covered in the specific help center section.

Standard - Users get the reward as soon as they complete the challenge
Global Lottery - Winners are drawn randomly, and rewards are allocated after the activity ends
Local Lottery - Winners are drawn randomly per store, and rewards are allocated after the activity ends

Coupon reward gives users who completed the challenge a coupon, created as an Offer activity of type Challenge (StampCard has been deprecated). The user receives it in the app as a coupon for a free or discounted product, or it could even be a basket discount (e.g., 10% off, $5 off, etc.)

Select the desired Offer reward from the drop-down menu and set the Pick-up End Date.
The Redemption expire date must be the same as or later than the activity’s end date, but no later than the Reward End Date.
Or use the Validity period of redemption to configure for have many days the reward is valid starting from the day it was rewarded to a user.
Redeemable only in the store where the challenge was completed - The coupon reward with the option where they can only be redeemed in the store where the challenge is completed, is consistent across standard, global, and local lotteries, and it applies specifically to the coupon reward type.

Bonus reward can be configured to give to users a bonus (or points) amount added directly to the user’s account as a reward for completing the challenge.

For bonus reward, a sponsor can be selected in order to track the funding in the reporting activities. The values are customizable on demand (e.g., Supplier, Retailer, Store, etc.).

Custom reward is a prize that is delivered outside the app, such as home delivery, pickup points, etc. This should be communicated clearly to users that complete the challenge.

Activity behaviour¶

Here, the main behavior of the activity is set up.

Pre-activated

On: The challenge is automatically activated for the user, allowing progress to be collected without the user having to do any actions in the app.
Off: The user must manually activate the challenge in the app before progress can be collected.

Hide Challenge from App List

Turn this on to keep the challenge hidden from the App list and, where available, home screen while it runs in the background, tracking progress and granting rewards as usual.

It should always be used together with Pre-activated toggled on, so that users can collect progress in the background without any interaction.

Accumulation¶

Based on how the progress is tracked, multiple types are available.

1. One purchase: The user can complete the challenge if one or more conditions are met within a single purchase. This is the only type that currently supports multiple rules, like having a transaction of a minimum $20, and 1 can of Coca Cola to get a reward.

Earn method

Product quantity requires the user to buy a specific number of products to receive the reward. Supports configurable Units of Measurement — see Units of Measurement below.
Purchase amount sets the total purchase value required for the user to complete the challenge and receive the reward.

IDs action

Choose whether to include or exclude certain products/categories in the calculation. You cannot select both options simultaneously.

Product IDs / Category IDs

Configures the items or categories that are included in the offer. Click the pen or plus to edit the list of item IDs, one per line.
You can also upload a CSV file with IDs, one ID per line. The content of the file is just populated in the form and can be later reviewed and edited. The initially uploaded file name is not stored.
We advise that the list of IDs should not exceed 40,000 affiliations and 20 challenges running simultaneously, as going beyond these limits may lead to performance issues.
The IDs can be downloaded for further review.
For Basket Discount, the product and categories are used for exclusion from the offer.

Global Product exclusion If you frequently exclude the same Product/Category IDs from challenge calculations (e.g., alcohol, tobacco), you can upload them once in the Product Exclusion configuration under the Settings page.

After setup, these exclusions are automatically applied to every new Challenge.

📝 Note: If you include a Product/Category ID locally in a specific Challenge, but the same ID is excluded in the global Product Exclusion, the local setting will override the global one. The product will be included in that Challenge.

2. Multiple purchases: The user can complete the challenge gradually by making multiple purchases and accumulating progress over time.

It can have either Product Quantity or Purchase Amount, with the same configurations as detailed for One purchase.

3. Store visits: Sets the required number of store visits with a purchase for the user to complete the challenge and receive the reward.

Any purchase counts as a store visit, with some limitations that can be optionally configured.
Store visits configures the number of visits to complete the challenge, which is a maximum of 9.
Minimum purchase amount is the minimum value of a transaction so that it counts as a store visit.

4. Payment method: The user need to make the purchase using a specific payment method.

Purchases by payment method configures the number of purchases required using on of the allowed payment methods.
Minimum amount per purchase is the minimum value of a single transaction so that it counts as a purchase with a payment method. Can be 0 or empty.
Payment method configures allowed payment methods for a transaction to count towards progress. Supported payment methods are:
- Card
- Cash
- Loyalty app - any payment through the app. It could be card, bonus, etc. but should happen through the member app.
- Other - any other specific payment method or condition that is used for custom logic on request.

Units of Measurement¶

When using the Product count earn method, you can configure the Unit of Measurement (UoM) used to count progress. This allows Challenge rules to be built around weight or volume, not just whole-item counts.

Standard supported UoM types:

Item (default) — counted in whole units (e.g., "buy 5 units of product Y")
Litre — counted in litres (e.g., "buy 40 litres of fuel")
Gram — counted in grams
Kilogram — counted in kilograms (e.g., "buy 2 kg of apples")

You can mix earn methods and units within a single Challenge — for example: "spend 100 kr excluding product X" combined with "buy 9 units of product Y" and "buy 5 kg of product A".

If you need an additional UoM type beyond the standard list, please reach out to your support manager.

⚠️ Important: UoM must match the POS purchase load¶

The Unit of Measurement selected for a given Product ID / Category ID in the Challenge rule must match the unit of measurement sent from the POS for that same product. The system does not perform unit conversion — it treats the POS quantity as already being in the UoM configured on the rule.

Example: A rule says 2 kilograms for productId 1001. The POS purchase load sends productId 1001 with a quantity of 600 grams. The system will read that quantity as 600 kilograms and the Challenge will be incorrectly recognized as completed.

To avoid this, do one of the following: - Configure the POS to pass 0.6 kilograms (so the unit on the rule and the unit in the purchase load match), or - Configure the Challenge rule to use Gram and ensure the POS always sends grams for that product.

Align the unit with your POS integration before configuring rules that use weight or volume.

Delay between purchases¶

Specifies the amount of hours that should pass from the last purchases in order for the next one to be applicable towards progress. This helps prevent the case when Challenge is Auto-renewable or Unlimited and user is able to accomplish challenge multiple times withing the same trasaction if rules are met multiple times.

With the Delay between purchases they would have to wait before the next Challange can be completed. Can be set to empty if not delay.

One-time or renewable¶

One-time: The user can complete the challenge once. After completion, the challenge is no longer available.
Auto-renewable: The user can complete the challenge, and it will become available again. You can specify the number of times the challenge can be renewed.
Unlimited: The user can complete the challenge repeatedly, with no limit on renewals, until the activity's end date.

Discounted items¶

Include Discounted Items - discounted items count at full quantity
[Deprecated] Include Proportional Discounted Items - discounted items count proportionally (e.g. 4 items at 25% off = progress of 3). Only for Product Count.
Exclude Discounted Items - 0nly full-priced items count towards challenge progress

[Deprecated] Product accrual value allows to set a value of the free product that will be divided in reporting to the number of the challenge, where applicable (in case product count earned is selected). This is an optional value that can support reporting but does not impact the mechanics. This value is not displayed on the mobile app.

Progress trackers in App¶

Depending on your accumulation and earn settings, the progress tracker has different styles in the App: no tracker, stamps tracker (up to 9), and progress tracker.

Challenge layout¶

This page lets you configure the look and feel of the challenge card in the App.

Product image¶

Is displayed in the app in the description of the stamp cards, but also in the stamp card details. The product image can be an actual image or an illustration.

Formats: jpeg, jpg, png
Format recommendation: PNG with transparent background for bets visual outcome on darker backgrounds
Max file zie: 2 MB
Image size: square of minimum 300x300 px, transparent or white background
Image edges: 25px on all sides

Background image¶

Is displayed on the app as the background of the challenge card. It’s optional, when not configured the background will be App theme color that you selected during the implementation.

Formats: jpeg, jpg, png
Image size: 686x140px (for better quality, should double to 1372x280px)
Max file size: 2 MB

Challenge progress and reward label¶

You can optionally override the default label text that mentions the progress and reward. E.g., Buy 4, get 1. Maximum of 30 characters.

Challenge completion counter label¶

You can show a counter of how many times the challenge has been completed. Leaving it blank will not show it. It could be used for lottery challenges to hint at the number of tickets in the lotteries.

Maximum of 40 characters. You can use the %counter% placeholder. E.g., Completed times: %counter%

Description texts¶

Card name – shown as the challenge title in the app
Details text – show in the app to describe the general campaign
Terms & conditions text – details the T&C of the campaign (limited stock, special conditions, etc.)

Challenge preview¶

The challenge previews (challenge card and challenge details) are just to help with a general hint on how the images and text will be displayed. The actual App design will differ based on the UI aligned during the implementation phase.

Segmentation¶

Segmentation defines the audience for the specific challenge.

Segmentation is dynamic, like other attributes of the Activity. New/changed segmentation lists can be uploaded during the activity to either expand or narrow the audience.

The segmentation list must be in CSV format with one user ID per line, while the file size cannot exceed 48 MB.

The list can be added via "drag and drop” or via the "select file" link.

Segmentation with Audience Service¶

Some customers have integration with Audience Service that allows the management of Member Segments in one centralized place and reuse throughout the other promotion and communication sections.

This means that when selecting Target only selected segments, there will be the option to select from a predefined list of Segments or create a new one.

Select from list of predefined segments brings up a pop-up where all predefined audiences in the scope of Challenges are listed. Based on the name and description, the needed Audience can be selected as a target for this game.

Multiple audiences can be selected for a challenge, including all the members. Even if a member is present in multiple audiences, the challenge is shown and progressed only once per user.

Create new list brings up a pop-up where a new Audience can be created. Even if a user ID is present multiple times in the file, the duplicates are removed upon uploading the file to the system.

Name – use a representative name.
Destination(s) – select where this list of members will be available for selection. Can be only Challenges or throughout other activities (e.g. Bonus, Feed, Notifications, etc.).
Description – longer text field that allows detailed description.
Upload file - the list of member IDs should be uploaded in a CSV with one member ID per line.

Save as template¶

An activity can be flagged as a template and be used as a starting point later on to create new activities. This is just a flag and does not impact active activities in any way.

The template flag can be toggled on and off at any point, even after the activity has expired.