flutter_umami_analytics 1.2.0

Flutter client for Umami Analytics. Track pageviews, events, and sessions offline with auto-route tracking, persistent device ID, and opt-in REST API.

Changelog

1.2.0

• Feat: FlutterUmamiConfig.defaultEventUrl lets you define the URL assigned to trackEvent calls that omit the url argument at init time. Defaults to the new public constant kDefaultEventUrl (/event), preserving backwards compatibility with existing Umami dashboards. An explicit per-call url always takes precedence. TrackingCollector now reads the default from config instead of a hardcoded /event constant. The field is part of copyWith, value equality, and hashCode; it is not per-call overridable via UmamiConfigOverrides (same policy as endpoint and httpTimeout).
• Docs: doc/{en,es}/1-initialization.md document the new defaultEventUrl config field; doc/{en,es}/3-tracking.md clarify the trackEvent url default now resolves from FlutterUmamiConfig.defaultEventUrl.

1.1.0

• Feat: createUmamiAnalytics now accepts injected httpClientPort and apiClient (UmamiApiPort). Injected ports take precedence over httpClient/enableApi and are NOT disposed by the facade or collector (caller owns lifecycle). TrackingCollector.ownsHttpClient and FlutterUmamiAnalytics.ownsApiClient gate disposal (default true for backwards compatibility).
• Feat: createUmamiAnalytics now accepts an injected UmamiQueue, decoupling queue policy from adapter-selection. Lets callers plug custom storage (Hive, Isar, Realm, ObjectBox, SharedPreferences, etc.) without forking the package. Enqueue-on-failure and TTL-purge-on-flush policies are derived in _policyFrom from UmamiQueueConfig. The queue is only closed by the collector when it built it.
• Docs: new doc/{en,es}/11-credentials-security.md centralizing the secrets table, two pipelines (tracking vs REST), JWT lifecycle, non-persistence guarantees, best practices and production checklist. Cross-linked from 1-initialization.md and 9-api-client.md.
• Docs: README splits the Documentation section into doc/en/ and doc/es/ subsections, each listing all 11 guides.

1.0.1

• Fix: per-call UmamiConfigOverrides (websiteId, hostname, language, userId) now applied to the outgoing payload in trackPageView, trackEvent, and identify. Previously the merged config was computed but the payload was still built from the base config, so overrides had no effect on those fields.
• Docs: added dartdoc (///) to all public API symbols across domain, application, infrastructure, and factory.dart.
• Docs: added English documentation set under doc/en/ (initialization, queue, tracking, observer, identify, overrides, device, logging, API client, advanced) and refreshed Spanish docs under doc/es/.

1.0.0

• Initial release.
• Pageview and event tracking with automatic device info (locale, screen, User-Agent per platform).
• Offline queue strategies: disabled, inMemory, persisted (SQLite with TTL, auto-flush).
• Persistent device ID via flutter_secure_storage, namespaced per instance.
• UmamiNavigatorObserver for auto-tracking route pushes, replaces, and pops (routeFilter and routeNameMapper hooks).
• Multi-instance support with isolated SQLite queue and secure storage keys per instanceName.
• Optional REST API client (enableApi): login, websites, stats, pageviews, metrics, active visitors, events, sessions, teams, users.
• Per-call config overrides (websiteId, hostname, language, userId).
• One-time firstReferrer consumed by the first trackPageView.
• Lazy sessionId generated on first identify().
• Configurable UmamiLogger (six levels, custom sink callback).
• Hexagonal architecture: pure-Dart domain with swappable port adapters.