# Browse Abandonment Page: https://alidemirbas.com.tr/en/lab/journeys/unresolved-interest-recovery Product interest detected → wait → check behaviour → remind or exit ## Purpose Send one relevant reminder when a user repeatedly views the same product but does not add it to cart or buy it. Goal: Recovery & Retry · Category: Acquisition & Intent ## Steps - **Trigger**: Same product viewed at least twice; no add-to-cart or purchase - **Wait**: Wait 6–24 hours - **Decision**: Was it added to cart or purchased? - Yes: Purchased or added to cart - No: Push: Revisit the product you viewed - **Action**: Push: Revisit the product you viewed - **Wait**: Wait for a response within the response window - The response window is set per business; the journey moves on as soon as the user acts. - **Decision**: What happened after the push? - Purchased: Purchased or added to cart - Added to cart: Move to Cart Reminder - No action: No second reminder - **Handoff**: Move to Cart Reminder - **Exit**: Purchased or added to cart - **Exit**: No second reminder ## Guardrails - End the journey on add-to-cart or purchase. - Do not create urgency without real stock, price or promotion data. ## Core rule Repeated views signal interest, not commitment. The message should not overstate what the user intended. ## When to set it up Look at this journey when product analytics show many users opening the same product several times and leaving without adding it to the cart. You need product views counted per user and product, add-to-cart and purchase tracked on the same identity, push permission recorded, and a response window set to fit your business. If the repeated views come from a product page problem such as missing size details, an unclear shipping cost or images that fail to load, fix the page first; a push only sends the user back to the same uncertainty. ## How to set it up - **Trigger and entry**: Entry requires the same product viewed at least twice with no add-to-cart or purchase. Split the users who meet that condition at random: the journey group gets the reminder, the control group sees no push for this product. - **Who must not enter**: Anyone who already added the product to the cart or bought it stays out. A user who saved the product belongs to Saved Product Reminder, one who asked for a stock alert to Back-in-Stock Alert, which suppresses this flow for the people it holds. Scope is one viewed product, with no second flow for it. - **Timing and channels**: After a wait of 6 to 24 hours, add-to-cart and purchase are checked again; if neither happened, a single push goes out. The push recalls only the viewed product and creates no urgency without real stock, price or promotion data. The journey then waits through the response window you set for your business. - **Exit and handoff**: An add-to-cart or purchase at the first check, or a purchase after the push, ends the journey. If the user adds the product to the cart after the push, the user moves to Cart Reminder and this sequence closes; when the response window passes with no action, the journey ends without a second reminder. - **Frequency and consent**: Only one push per viewed product, sent only to users with notification permission. Since push is the only channel, a user without it never enters; keep browse and cart messages for the same product from stacking up. ## How to measure success **Incremental viewed-product purchase rate vs control**: The single push is worth keeping only if the reminded group buys the product it viewed more often than the control group; a tapped push or a reopened product page is not the outcome. Take all users who met the trigger condition and were assigned to either group, and count the share who buy the viewed product within the same follow-up window from assignment; the gap between the groups is the journey's effect. Whether the push arrived or was tapped does not change the denominator. Also track: - **Add-to-cart rate**: Assigned users who add the product to the cart after the push, as a share of everyone assigned; the intermediate step on the way to purchase, and where the handoff to Cart Reminder takes place. Measure it in the control group as well. - **Converted before the push**: Those who add to cart or buy during the 6 to 24 hour wait and leave without a message; they convert on their own, and a push would have been noise for them. - **Push opt-outs**: Users who turn off notifications after the push; interest inferred from views is a weaker signal than a saved item, so tolerance for the message may be lower. - **No-action exits**: Entries whose response window closes with no action; in this flow a no-action ending is the common outcome and is not a failure by itself. ## What to watch when reading the result - A push that leaves the journey group's purchase rate level with the control group's only reached users who were going to convert anyway; tap counts or returns to the product page do not offset that. Base the decision on how much the two purchase rates differ, not on views. - What you measured belongs to this single push, the 6 to 24 hour wait and the response window you chose. In journey reports, a purchase by a user who added to cart after the push and moved to Cart Reminder is credited to that journey; in the control comparison, count purchases for both groups by one and the same rule. - Do not expect a large gap from one push; seeing a small gap with confidence takes many entries. Enter your current purchase rate and the smallest uplift you want to detect into the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) to get the users needed per group, then divide by your daily eligible entries to see how many days the test must run. - If the push used urgency wording such as limited stock or a time-limited discount without data behind it, do not count the resulting sales as the journey's gain; tie the copy to real stock, price or promotion data first. ## Frequently Asked Questions ### How does browse abandonment differ from cart abandonment? Browse abandonment covers product interest without an addition to cart or purchase. This example requires at least two views of the same product. Either event before the push ends the reminder. An addition to cart after the push explicitly hands over to Cart Reminder. ### Should a push be sent immediately after a product view? This example waits 6–24 hours, then checks for an addition to cart or purchase. If neither has occurred, it sends one push to an eligible user. Repeated views are an interest signal, not a definite buying decision. ### Should the browse reminder be repeated without a response? This flow ends without a second reminder. Track clicks, additions to cart and purchases separately. Stop the browse sequence when handing someone to the cart journey so the two do not overlap.