# Upgrade Completion Reminder Page: https://alidemirbas.com.tr/en/lab/journeys/upgrade-blocker-prompt Upgrade started → missing step → email → push → complete or exit ## Purpose Bring a user back to an upgrade they started but did not finish, pointing them directly to the missing step. Goal: Readiness & Revalidation · Category: Activation & Usage ## Steps - **Trigger**: Upgrade started but not completed - **Action**: Identify the incomplete step - **Action**: Email: Show the remaining step to complete the upgrade - **Wait**: Wait 2–3 days - **Decision**: Upgrade completed? - Yes: Upgrade completed - No: Push: Complete your upgrade - **Action**: Push: Complete your upgrade - **Wait**: Wait 1–2 days - **Decision**: Upgrade completed? - Yes: Upgrade completed - No: Journey ends - **Exit**: Upgrade completed - **Exit**: Journey ends ## Guardrails - Stop once the upgrade completes. - Do not keep reminding after the upgrade is no longer valid. ## Core rule A completion reminder should name the one thing still blocking the upgrade. ## When to set it up Your upgrade funnel is the signal here: upgrades that start at plan selection, payment or confirmation and are still unfinished days later. Track upgrade started and upgrade completed on the same account, and make sure the incomplete step can be identified, before launch. A link must lead straight to that step, the upgrade's validity and price conditions must be readable, and you need an email address and push permission. If upgrades stall because payment errors or the confirmation step breaks, fix that step first; a reminder that sends people back to a broken step only makes them repeat the work. ## How to set it up - **Trigger and entry**: A plan upgrade that starts but does not complete enters, and the first job is to identify the incomplete step: payment, selection or confirmation. Each upgrade attempt is its own scope; randomize eligible attempts at entry so that a control group receives no reminders. - **Who must not enter**: Users whose upgrade has completed do not enter, and one attempt never carries two flows. No reminder goes to a user whose upgrade is no longer valid, whose price terms have changed or whose attempt was cancelled; check validity at entry and before every send. - **Timing and channels**: First an email that shows the missing step and links straight to it; 2 to 3 days later the upgrade is checked. If still unfinished, a 'complete your upgrade' push goes out and a final check follows 1 to 2 days later. Send people to the remaining step, never to a generic pricing page. - **Exit and handoff**: Completion of the upgrade stops the journey at once, and a queued push is cancelled. If the final check still finds it unfinished, the journey ends; there is no handoff, both exits are terminal, and the same attempt does not re-enter. - **Frequency and consent**: No more than two reminders per attempt: one email and one push. Each channel needs its own consent, permission for push and a subscription for email; these two touches and their waits are an example plan, not a requirement for every product. ## How to measure success **Incremental upgrade completion vs control**: Only attempts that end with the new plan or capacity actually applied count, measured as how many more of them the reminded group produces than the control group; a click or a payment start does not count by itself. Among all eligible upgrade attempts taken in at entry, journey group and control group, the share where the new plan or capacity is successfully applied within the same follow-up window; what separates the two groups is the journey's effect. Neither delivery nor clicks change the denominator, and failed or cancelled attempts stay in it. Also track: - **Payment start rate**: Of all assigned attempts, the share that start the payment step after the link; the intermediate step before completion, not an outcome. - **Email vs push contribution**: Split completions by the touch that preceded them, email or push; if the push adds nothing, try dropping the second touch. - **Failed and cancelled attempts**: Keep the share of attempts ending in a payment error or a cancellation visible; if it is high, the problem is in the upgrade step, not in the reminders. - **Opt-outs and unsubscribes**: Watch push opt-outs and email unsubscribes; if they rise, review the wording and timing of the two touches. ## What to watch when reading the result - If the journey group's completion rate does not clear the control group's, the reminders only pulled forward users who would have finished anyway; extra clicks or payment starts do not change that picture. Judge the journey on the difference in upgrades actually applied. - This result belongs to these two touches, the 2 to 3 and 1 to 2 day waits and a link that lands on the missing step. Do not credit this flow with a completion that comes after the journey ended or after the upgrade stopped being valid, nor with an upgrade made through another offer. - The [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test) takes each group's attempts and completions and tells you whether the difference is significant; do not call a small gap a win before running it, and if it is not significant, extend the follow-up window beyond the final 1 to 2 day wait and let more attempts accumulate. ## Frequently Asked Questions ### Where should an unfinished upgrade reminder lead? Link directly to the missing payment, selection or confirmation step. Returning to a generic pricing page can make users repeat work. Verify that the upgrade and its price conditions are still valid when the link opens. ### How many upgrade reminders should be sent? This example checks completion 2–3 days after an explanatory email. If unfinished, it sends one push and checks again after 1–2 days. Stop after completion. These timings are an example rather than a requirement for every product. ### How should upgrade completion be measured? Use eligible upgrade attempts entering the journey as the denominator and count those with the new plan or capacity successfully applied as completed. Track clicks and payment starts separately. Keep failed and cancelled attempts visible.