Releases: telegram-mini-apps-dev/analytics
Releases Β· telegram-mini-apps-dev/analytics
1.4.4 (September 16, 2025)
[1.4.4] - 2025-09-16
Critical fix
- Web View observer: Properly reassign WebView receiveEvent method
1.4.3 (June 26, 2025) (deprecated)
[1.4.3] - 2025-06-26
Fixed
- Analytics controller: set up threshold default value on initialization
Issue: #42
1.4.2 (June 4, 2025) (deprecated)
[1.4.2] - 2025-06-04
Fixed
- Web App observer: Delete $ from start of slug
1.4.1 (May 23, 2025) (deprecated)
[1.4.1] - 2025-05-23
Fixed
- Invoice Observers:
- WebApp Observer: Checking that the openInvoice method is not undefined.
- WebView Observer: The event tracking method has been rewritten to support all platforms.
Added
- Invoice Observers:
- WebView Observer: purchase-cancelled event implementation.
- Generally:
- Network controller: Event upload compression.
1.4.0 (April 15, 2025) (deprecated)
[1.4.0] - 2025-04-15
Added
- Invoice Observers:
- WebApp Observer: Tracks the
purchase-initevent triggered by theopenInvoicemethod of the Telegram Mini Apps SDK. - WebView Observer: Tracks
purchase-successandpurchase-failedevents via theinvoice_closedevent in WebView from Telegram Mini Apps SDK.
- WebApp Observer: Tracks the
1.3.16 (April 15, 2025)
[1.3.16] - 2025-04-15
Added
-
Session-based event thresholding:
Introduced support for throttling specific events based on session limits. The SDK now queries a new endpoint,/events/threshold, with a 2-second timeout to fetch event thresholds dynamically.
If the endpoint fails or times out, default thresholds are used.Default behavior:
- For the
app-hideevent, the SDK will allow sending it up to 3 times per session.
This helps reduce noisy or redundant analytics and gives more control over high-frequency events.
- For the