
Website and app activity in one workspace
Mobile app analytics that fits your product
See the screens people visit and the actions they take in your app, alongside your website activity. Add the Talivia SDK for your framework, then choose the navigation and product events that matter to your team.

Wednesday, September 16th, 2026
Product analytics for mobile apps
Measure the journey you actually build
From onboarding to everyday feature use, send meaningful app activity to the Talivia workspace you already use for your website.
Follow screen journeys
Call screen() when navigation changes to measure which parts of the app people use.
Track meaningful actions
Send named events for signup, onboarding, feature use, and other business milestones.
Recognize signed-in customers
Pass your stable account ID after login to link known identity records across app and web.
How it works
Three calls to understand your app
Use a Website ID from Talivia, initialize your platform SDK, then add explicit calls at your navigation and product milestones.
Read the setup guide- 01
Connect the workspace
Use the same Website ID and hostname as your website for a shared analytics workspace.
- 02
Record screens and events
Call screen() from navigation and track() for the actions you want to analyze.
- 03
Identify after login
Call identify() with your stable user ID when your app knows the customer.
Choose your SDK
Start with the framework you ship
Each SDK sends native app activity to Talivia. Pick your platform for installation details and the exact tracking calls.
What you can learn
One workspace, clear measurement
Web and app activity
Inspect both sources in the same workspace while keeping their tracking paths explicit.
Product signals
Give names to the actions that tell you whether onboarding and features work.
Trusted revenue
Keep payment reporting tied to verified server-side payment data, not an untrusted app event.
Clear measurement boundaries
Know what the SDKs do today
Mobile tracking follows the events your app explicitly sends. Known identities can be linked, while cross-device funnels are still visitor-based.
- Screen changes and business events require explicit calls in your app.
- Offline retry is memory-only and capped at 100 events; app restarts clear the queue.
- Install attribution and verified app purchases require separate trusted integrations.
Questions
Mobile analytics, explained
What you can collect now, and where additional integrations are needed.
Can I track a native app with the website script?
No. The browser script tracks web pages, including Expo Web. Native React Native, Flutter, iOS, and Android apps use their respective SDKs.
Are screens tracked automatically?
No. Call screen() from your navigation callback. Call track() for product events you choose to instrument.
Will web and app activity appear in the same dashboard?
Yes, when you use the same Website ID and hostname. Known account identities can be linked with identify(), but current funnels still group by visitor token rather than merging cross-device journeys.
Does this automatically attribute installs or app-store purchases?
No. Native install attribution and app-store purchases need separate integrations. Send authoritative purchase information from a trusted backend.
Bring your app into focus
See your app and website activity together
Create a workspace, add your SDK, and start with your first screen and product event.
Start tracking for free