Building a kids app with minimal data: lessons from Sago Mini
Kids apps must delight a child who uses the product and reassure a parent who pays for it, while operating under stricter privacy limits than most consumer apps. Brennan Clark, Director of Product at Sago Mini, discusses how his team makes product and growth decisions when the usual data signals are unavailable.
Why kids apps are different
Sago Mini had passed 100 million downloads at the time of the conversation, yet scale did not remove the core difficulty: kids apps have distinctive challenges, and scarce data is one of them. The company, based in Canada, had also expanded beyond apps into a physical subscription offer and an Apple TV+ show, Sago Mini Friends. Clark links that expansion to shared values around high-quality, safe content for children.
A practical checklist for dual-audience design
Use this checklist to test whether a kids product is ready for both audiences:
- Child test: Has the experience been watched in weekly play testing with kids, not only reviewed by adults?
- Parent test: Can a parent understand what the child is doing and why it is worthwhile?
- Privacy test: Does the design work without relying on identifiers the team cannot use?
- Early-value test: Is the value clear within the first 48 hours, when most purchases occur?
- Trust test: Does the content and safety positioning feel consistent enough for a platform partnership?
Design for the child, inform the parent
The team runs weekly play testing with children, but that alone does not solve the parent problem. Sago Mini therefore created an app for parents, letting them see how their kids engage with the apps. This turns the payer into an informed participant instead of a bystander, and it creates product feedback that does not depend on tracking the child.
Privacy-first measurement
Privacy and data rules are especially demanding in this category. Sago Mini could not use IDFA or ATT and was losing its Google Ad ID, so it had to work creatively with partners to avoid crossing boundaries while still delivering good experiences. That constraint also affected measurement: AppsFlyer had to build a custom SDK for Sago Mini. The lesson is to plan measurement around permitted signals from the start, rather than retrofitting standard attribution.
The first 48 hours matter most
Clark notes that roughly 80% of purchases in the kids industry happen in the first two days. That narrow window means onboarding, paywall timing and parent communication should be treated as first-48-hours decisions. Sago Mini operated three subscription apps for preschoolers, with Apple driving 80% of revenue, which further underscores the importance of platform fit and early trust.
Bottom line
When data is minimal, effective decisions come from combining direct observation, parent visibility, privacy-respecting partners and a clear early-value proposition. The Sago Mini example shows that limited data does not have to mean limited learning, provided the team builds alternative feedback loops deliberately.
Frequently asked questions
Why is data especially limited for kids apps?
Kids apps face tighter privacy and data limits, so teams cannot rely on the identifiers and tracking signals common elsewhere. That means decisions must lean more on direct observation, such as weekly play testing with children, and on parent-facing insight, rather than on large-scale behavioural data.
How can parents be brought into the product loop?
Sago Mini added a separate app for parents so they could see how their children were engaging with the apps. That gives the paying adult visibility and gives the product team a second, legitimate lens on use.
How quickly do kids-app purchases tend to happen?
In the example discussed, about 80% of purchases happened in the first two days, or first 48 hours. The practical implication is to front-load clarity, trust and value for both child and parent, rather than expecting a long conversion window.
What if standard attribution tools do not fit?
Standard measurement tools may not fit privacy constraints. In this case, AppsFlyer built a custom SDK for Sago Mini, showing that measurement may need a bespoke, privacy-respecting approach instead of off-the-shelf tracking.