# Reward Confirmation Page: https://alidemirbas.com.tr/en/lab/journeys/reward-confirmation Reward earned โ†’ in-app confirmation โ†’ wait โ†’ redeem or remind ## Purpose Confirm the earned reward immediately, then send one reminder only if its redemption code remains unused. Goal: Delivery & Confirmation ยท Category: Loyalty & Relationship ## Steps - **Trigger**: User earns a reward - **Action**: In-app: Show the earned reward + redemption code - **Wait**: Wait 3 days - **Decision**: Was the reward code used? - Yes: Reward used - No: Push: Use your reward before it expires - **Action**: Push: Use your reward before it expires - **Exit**: Reward used - **Exit**: Reminder sent; journey ends ## Guardrails - Do not send the reminder after redemption. - Do not invent a different value, expiry or benefit. ## Core rule Reward communication should reflect the reward and redemption terms that were actually recorded. ## When to set it up Earned rewards whose redemption codes sit unused, and members asking support where their code is or why it reads as invalid, are the signal to build this flow. The reward record and its code must be created at a known moment, the code's use must be an event you can match to that record, and the real value, expiry and benefit must sit on that record, with in-app message and push channels live. If the code fails to apply at checkout or the reward is not visible in the app, fix the product first; a confirmation and a reminder will not fix a broken code. ## How to set it up - **Trigger and entry**: The journey opens the moment a user earns a concrete reward and its record and redemption code exist. Everyone sees the in-app confirmation; at entry, split rewards at random so that the control group does not get this flow's reminder push. - **Who must not enter**: Rewards whose record or code does not yet exist stay out. Each instance follows one reward and its code: the same reward is not reannounced as newly earned each session, and a tier change is not a reward; it belongs to Loyalty Tier Change. - **Timing and channels**: In-app, the reward and its code are shown at the moment of earning; 3 days later the code is checked and, if unused and the reward still valid, one push says to use it before it expires. Value, expiry and benefit in both messages come from the reward record; nothing absent from it is written. - **Exit and handoff**: If the code has been used by the day 3 check, the journey ends there and no reminder is sent. If not, the push goes and the journey closes as reminder sent; there is no further touch and no handoff to another journey. - **Frequency and consent**: Two touches at most per reward: one in-app confirmation and at most one push. The push goes only to users with push permission; the in-app message appears when the user opens the app. This flow outranks Unused Loyalty Reward and never carries that flow's message on the same membership. ## How to measure success **Incremental code redemption rate vs control**: What the push adds is how many more codes the reminded group redeems than the control group that only saw the in-app confirmation; seeing the confirmation or opening the push is not a redemption. Every reward assigned at entry to either group is the denominator; the numerator is those whose code is redeemed, matched to that reward record, within the same follow-up window from assignment, and the gap between the groups is the reminder's effect. Push delivery or opens do not change the denominator. Also track: - **Redemption by the day 3 check**: Codes redeemed on the in-app confirmation alone, before any reminder, as a share of assigned rewards; it shows how much the confirmation and redemption instructions do by themselves. - **Redemption after the reminder**: Of the rewards still unused on day 3, the share redeemed after the push, compared with the control group's share over the same period; the single push's real contribution shows here. - **Reminders sent on expired rewards**: Pushes sent for a reward whose validity had ended; the count should be zero, and if it is not, fix the expiry check. - **Push opt-outs and support contacts**: Push opt-outs and support contacts about the reward's value, date or code belong together here; if contacts rise, the message may be saying something the record does not. ## What to watch when reading the result - A redemption gap near zero means users were redeeming on the confirmation alone, and push opens do not change that call. The reminder's only contribution is how many of the codes still unused on day 3 it brings back. - This reading covers one in-app confirmation, a 3 day wait and one push. Because Unused Loyalty Reward is suppressed on the same membership, a redemption in this period is credited to this journey only; never count it in both. Read the effect of a tier change happening at the same time in Loyalty Tier Change. - One push will move redemption only a little, so you need many rewards. Work out the rewards needed per arm with the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator), starting from the control group's redemption rate and the smallest gap worth detecting, and do not decide before you reach that count. - Should support contacts climb, compare the confirmation and push templates with the reward record first; where a different value, date or benefit was written, the template is talking, not the redemption data. ## Frequently Asked Questions ### When should an earned reward be confirmed? Show it once the reward and any redemption code genuinely exist. This example confirms it in-app first. Keep conditions and redemption instructions clear, and do not announce an unearned reward as ready. ### Is a reminder needed after reward confirmation? This example checks code use after three days. It exits if redeemed, otherwise sends one push and ends. Skip the reminder if validity has already ended. Do not reannounce the same reward as newly earned each session.