wakeAnalytics for Swift apps that starts with what you want to know.
Design first, then collect
Most analytics tools have you track events first and work out the questions later. By then, the answer usually isn't in the data. In Wake you pick a moment that matters, write down what you want to know about it, and design the event to answer that.
Your coding agent adds the tracking
Studio generates a Swift file from your design, and a prompt that has your coding agent put the calls in the right places. When the design changes, regenerate and hand the agent the prompt again.
One event carries the whole moment
Instead of logging paywall_shown, paywall_closed and purchase and building a funnel, you design one Purchase event. It records where the paywall was opened from, how many times the user had seen it, and how long they looked at it. In observability these are called wide events: one detailed record instead of a trail of clicks.
Views keep the filters you use
Every event opens on its own overview, with every property charted. Filter by country, device, app version or any property, and every chart narrows at once. Save it as a view, and your team sees it too.
And the basics
Active and new users
Daily active users, and new users counted from each first launch.
Sessions
How long sessions last and how many each user has.
Countries, devices and languages
Where your users are, what they use, and the language they read in.
App and OS versions
How fast a release is picked up, and who is stuck on an old build.
Purchases
Pass the StoreKit product and transaction. Storefront price, intro offers and duplicate protection come with it.
Screen time since
Time spent in the app since any moment you mark, like the paywall opening. No timers in your code.
Any period
Step back to earlier periods to compare before and after a release.
Test data kept apart
Events from debug and TestFlight builds stay out of your numbers until you ask for them.
Privacy
No device identifiers, no IP-based location. The SDK ships with a privacy manifest.