The Buyer Journey
What a buyer experiences from landing to thank you, and three things to know before designing offers.
The Buyer Journey
The buyer opens the landing page, presses Buy, pays at checkout, then continues from the order page to the next offer. Here are the details, because some parts are deliberately different from what you might expect.
Every offer is paid separately
An accepted offer creates a new order with its own payment; it does not add lines to an order that was already paid. Indonesian payment gateways do not store the buyer's card or account, so a one-click charge is not possible. A buyer who accepts an upsell pays again through VA, QRIS, or bank transfer. Design your offers with that in mind: an offer whose value is obvious is easier to pay for twice.
On the order page, an offer's order is marked as a follow-up of its parent order, so reporting can still chain them together.
The Continue button appears after payment
After paying, the buyer sees the usual order page. Once the payment is confirmed, a Continue button appears leading to the next step. The buyer is deliberately not redirected automatically: they are reading their payment proof, and throwing them onto another page makes them think the transaction failed. A buyer who stops there still has a valid order.
For manual bank transfer, the button appears only after you confirm the payment in the dashboard.
Offer pages open only through the journey
Upsell, downsell, cross-sell, and thank-you pages cannot be opened directly by address. A visitor arriving without a valid journey, for example from a search engine, is redirected to the homepage. A buyer's journey stays valid for 3 days, enough for someone who pays a VA through mobile banking and comes back.
Buyer details are prefilled
At an offer checkout, the buyer's name, email, and phone number are already filled in from their first order. A shipping address is still requested for physical products.
Declines are recorded too
A buyer who presses No is sent down the No branch, and the decline is recorded in the journey. That is what lets reports show accept and decline counts per offer, and lets conditions use "declined offer X".