Key points:
- Ask to Buy puts a child’s purchase into a pending state until a parent approves, declines, or lets it expire.
- A pending request isn’t a finished purchase, and it isn’t a lost one either. It’s genuinely undecided.
- A funnel that treats the tap on “buy” as the final answer can mistake a pending request for an abandoned purchase.
- The real answer, approved or declined, can land well after the first attempt, sometimes days later.
A purchase that’s neither clearly won nor clearly lost sits in the middle of a lot of funnels with nowhere clean to go.
What actually happens with a held purchase
When a child under a family’s set age tries to buy something, the purchase doesn’t finish right away. It holds, waiting on a parent to approve or decline. The child sees it’s pending. The parent gets a request on their own device. Only once the parent acts, or the request times out, does the purchase actually resolve one way or the other. Up to that point, the first attempt was neither a yes nor a no. It was simply undecided.
| What’s true right at the tap | |
|---|---|
| A finished purchase | Already resolved, yes |
| A clearly abandoned purchase | Already resolved, no |
| An Ask to Buy request | Not resolved yet either way |
Why this can quietly skew your numbers
A simple funnel often treats the tap on “buy” as the moment that decides success or failure. For most purchases, that’s a fair shortcut, since most resolve right away one way or the other. An Ask to Buy request breaks that assumption. It can sit pending for real time, sometimes days, before a parent gets around to deciding. If you check your funnel too early, before that answer comes in, a purchase that will eventually go through can look, for a while, just like one that was dropped.
Real-world scenario: A team noticed a small, steady gap between purchase attempts and finished purchases that didn’t match their usual pattern, and started treating it as a possible bug in their purchase flow. Digging into the specific accounts behind that gap, several turned out to be Ask to Buy requests still waiting on a parent, not broken purchases at all. Checking those same accounts again a few days later, a real share of them had gone through once a parent said yes. The numbers hadn’t been wrong. They’d just been checked before the real answer existed yet.
What this means for reading your own funnel
A purchase tied to a family account deserves a second look before you write it off as a lost sale. Giving pending requests real time to resolve, instead of judging your funnel at the exact moment of the first tap, stops you from mistaking a genuinely undecided purchase for a dropped one. The gap doesn’t need to be a mystery or a bug. It often just needs more time before it closes on its own.
What to actually do about it
- Don’t treat every unresolved purchase as dropped right away. An Ask to Buy request can sit pending for real time before it resolves either way.
- Check funnel gaps again after time has passed, not right away. A purchase that looked lost can still go through once a parent actually answers.
- Keep pending family purchases separate from genuinely dropped ones in your own numbers. They look the same at first glance but mean very different things.
- Don’t chase a funnel gap as a bug before ruling out this normal delay. A real problem and a pending approval can look identical until you check which one it actually is.
AppRankr’s ASO Inspector checks your listing’s real conversion signals, a useful next step once you’ve ruled out a timing issue like this one.