You can now use the codes your participants enter or receive during a Qualifio campaign as criteria in your Loyalty earning rules — for example, to award more points for a premium product than an entry-level one, based on the code a consumer typed in.
This article explains what's new, how the two supported code types differ, and how to set up a rule.
What's new?
Two new criteria are available under Earning rules → Trigger, when Source = Qualifio campaigns and Action = Campaign participation:
- Unique code — the code a participant enters on the campaign welcome screen to unlock participation (proof of purchase).
- Burned code — a reward or coupon code redeemed by the participant during the campaign (for example, on the exit screen).
Both criteria support the "Start with" operator, so you can match on a prefix rather than an exact code. This is what makes per-product rules possible: if your codes are generated with a product prefix (e.g. PROD1-X7K2M9, DOG-A1B2C3), you can write a rule such as:
When a member participates in campaign X and the code they entered starts with
PROD1-, award 10 points.
Unique code vs. Burned code vs. Access code — what's the difference?
These three concepts are easy to mix up, so here's a quick comparison:
| Concept | What it is | Where it's entered | Used in earning rules? |
|---|---|---|---|
| Unique code | A per-participant code, one per person, used once — typically proof of purchase | Campaign welcome screen, before participation | ✅ Yes — new criterion |
| Burned code | A reward/coupon code drawn from a list and marked "used" the moment it's handed out | Given to the participant on the exit screen (or similar) | ✅ Yes — new criterion |
| Access code | A single generic code shared by all participants, used to unlock the campaign itself | Campaign welcome screen | ❌ Not covered by this feature |
Access code is a different, already-existing concept — it is not affected by this update and is not exposed as an earning-rule criterion.
How do I set up a rule based on a code?
- Go to your earning rule, and in the Trigger section set:
- Source:
Qualifio campaigns - Action:
Campaign participation
- Source:
- Select your campaign using the existing campaign search field, just as you do today.
- Add a criterion and choose either:
- Unique code, if you want to match the code entered at the welcome screen, or
- Burned code, if you want to match a redeemed reward/coupon code.
- Set the operator to "Start with" and enter the prefix you want to match (e.g.
PROD1-). - Combine it with the existing Campaign criterion, and add as many code-based rules as you need — one per product prefix, for example.
- Save the rule.
You can of course still use other operators (equals, contains, etc.) on these fields if you don't need prefix matching.
Do I need to configure anything on my campaign for this to work?
Yes — the criterion can only match data that your campaign actually produces:
- For Unique code, your campaign needs a welcome screen with unique code entry configured, and codes must have been uploaded (typically via CSV) for participants to enter.
- For Burned code, your campaign needs to be configured to hand out reward/coupon codes (for example, a code-list-backed prize or an exit-screen coupon).
If a participation doesn't include the relevant code, the rule simply won't match for that participation — it won't error or award points incorrectly.
Why is my rule not matching any participations?
A few things to check:
- The code is genuinely present on the participation. Confirm the welcome screen (for unique codes) or the reward mechanism (for burned codes) is correctly configured on the campaign.
- The prefix is correct, including case. Codes are recommended in uppercase; matching is based on the exact characters you enter in the rule.
- You're using the right criterion. Double-check you picked "Unique code" and not "Burned code" (or vice versa) — they come from different steps of the participation.
- The campaign selected in the Trigger matches. The code criteria only apply to participations on the campaign(s) you've selected.
Does matching a code prefix prove the code is genuine or unused?
No — the "Start with" match is a string comparison on the code itself. It confirms the pattern of the code entered, not that the code is authentic or hasn't already been used elsewhere. If code authenticity or single-use enforcement matters for your use case, this should be handled upstream (for example, at the point the code list is generated and validated), separately from the earning rule.
Is this compatible with my existing earning rules?
Yes. This update only adds two new criteria and narrows the "Start with" operator's availability to these two fields specifically — it does not change the behavior of your existing earning rules or criteria. Rules you've already saved will continue to load and evaluate exactly as before.