Abandoned Deposit Push Notification
An abandoned deposit push targets players who opened the payment form but never completed the transfer. This segment converts far better than cold traffic because the user already showed buying intent — the push just needs to remove the last objection. In a PWA funnel, this trigger typically delivers a noticeably higher CTR and deposit rate than a broadcast to the full base.
What counts as an abandoned deposit
The event fires when a user opens the payment form or enters an amount, but no successful-deposit postback arrives within a set window — usually 15 to 30 minutes. This segment should build automatically from S2S postbacks that tag funnel steps, not just the final conversion. Don't confuse it with cold traffic: these users already saw the payment form and methods, which makes them a warm segment.
Setting up the event-based trigger
In APEX's push engine, the segment is built from an S2S postback: 'reached deposit' with no matching 'deposit successful' inside the wait window. The trigger fires automatically once that window closes — no manual work from the buyer. It's easy to split-test on top of this: run two copy variants against the same triggered segment.
What to say in the push copy
A reliable structure: remind the user of the action they started, address one objection (payment safety, instant crediting), then add a soft incentive — a bonus on the next deposit or a faster withdrawal. Don't invent countdowns or bonus amounts that aren't actually on the offer; moderation and user complaints will kill the funnel fast. Personalizing by local currency and minimum deposit usually beats an aggressive tone.
Timing and follow-up frequency
The first push usually goes out 15 to 60 minutes after the abandoned event, the second the next day at the same local time, and a third — if used — three to four days later with a different bonus angle. More than three touches on the same event tends to hurt response and increase opt-outs. Send times should follow the geo's local time, not the server's, or the push lands at 3 a.m.
Common mistakes and how to avoid them
The biggest one: pushing everyone regardless of whether the deposit actually failed — without a solid postback, the segment fills with users who already paid, which annoys players fast. The second: reusing one text across every geo without adjusting currency and language. APEX's team roles (lead, buyer) let you split who configures segments from who writes and tests copy, which cuts down on both mistakes.
FAQ
- How soon should the first push go out after an abandoned deposit?
- Usually 15 to 60 minutes — earlier feels pushy, later the user has cooled off. Split-test the exact interval per offer and geo.
- How do you tell an abandoned deposit from a delayed one?
- By the wait window after the payment-started postback: if no successful-deposit postback arrives within 15 to 30 minutes, the event counts as abandoned. A longer window cuts false positives but delays the reminder.
- Does the push need to promise a bonus?
- Not always — often just reminding the user of the unfinished action and addressing a technical objection is enough. Save the bonus for a second touch, and only offer one that genuinely exists on the offer.
- Can the whole sequence run without manual sending?
- Yes, as long as a 'deposit started, not completed' postback exists — then APEX's segmentation and push delivery run on the trigger automatically, including scheduled follow-ups.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free