talivia_flutter 0.1.0

Flutter app analytics for screen views, events, and user journeys in Talivia.

Talivia for Flutter

Connect Flutter screen views and product events to your Talivia analytics workspace.

talivia_flutter sends app sessions, screen views, custom events, and user identity to Talivia. Talivia helps website and SaaS teams understand visitor journeys and which traffic turns into verified payment revenue. With the same Website ID on web and mobile, you can inspect both sources of activity in one workspace.

[Talivia revenue analytics dashboard showing visitors, traffic sources, and payments]

Explore Talivia | View website analytics | Read the documentation

The SDK supports Flutter apps on iOS and Android. It uses the existing /api/send collector and needs no private API key in the app.

Install

flutter pub add talivia_flutter

What you can measure

• Screen views and app sessions alongside website activity.
• Custom events such as signups, onboarding steps, and feature use.
• Known customers through identify, using the same user ID as your website.

Call screen from your app's navigation flow and track where meaningful actions happen. Talivia links known identities across web and app, while current funnels still count each visitor separately. App-store purchases and campaign attribution need separate trusted integrations.

Track your app

import 'dart:io';
import 'package:shared_preferences/shared_preferences.dart';
import 'package:talivia_flutter/talivia_flutter.dart';

final analytics = Talivia(
  websiteId: 'YOUR_WEBSITE_UUID',
  platform: Platform.isIOS ? 'ios' : 'android',
  preferences: await SharedPreferences.getInstance(),
  hostname: 'example.com',
);
await analytics.screen('Home');
await analytics.track('signup_completed', {'plan': 'pro'});
await analytics.identify('your-stable-user-id');
// On logout: await analytics.reset();

Call screen when your Navigator/Router changes. Use the same Website ID as web. Offline requests are retained only while the app is running, capped at 100; a server-rejected request is dropped. Cross-device funnels are not yet identity-merged. Record trusted purchase amounts from your backend, not from mobile events.