Known analytics issues
Written by Lois Mortimer
Updated at March 26th, 2025
Table of Contents
This document provides an overview of the known issues affecting analytics tracking across our iOS, Android and Web platforms. Our team is actively working to resolve these issues to ensure that all features are tracking as expected.
Cross-platform issues
| Event / feature | Issue description | Versions affected | Status |
|---|---|---|---|
| BoltVideo* | Currently in-content YouTube videos (those on article pages) are not tracking any analytics events | Under investigation | Fix in progress |
| SearchAttempt | SearchAttempt event fires on every user keystroke resulting in a significant increase in the volume of SearchAttempt events. | Search version 2.3 | Fixed in Search version 2.3.14 |
| BoltSave / BoltUnsave | Sending two events every time a user interacts with the save icon from the timeline | Timeline versions < 5.3 | Fixed in Timeline version 5.3. Fix in progress for save icons in kebab menus |
Bolt Android
| Event / feature | Issue description | Versions affected | Status |
|---|---|---|---|
| BoltNotificationOpen |
The event captures a fraction of true notification opens as it only fires when the app is in the foreground.
To glean true numbers, use the notification provider or |
Under investigation | Fixed in 4.3 |
Bolt iOS
| Event / feature | Issue description | Versions affected | Status |
|---|---|---|---|
| Screen View | Two screen view events fire for each page in an edition (only impacts editions with double page spreads). | 4.1.0 - 4.1.12 | Fixed in 4.1.13 |
| Screen View | Screen interruptions (e.g. Apple's App Tracking Transparency, phone calls, a Google interstitial ad) resulted in duplicate screen views. | Fixed in 4.3 | |
| Screen View | In some cases, the start screen sends two screen views after a fresh restart (e.g. after the app is force killed). | Fixed in 4.3 |
Bolt Web
| Event / feature | Issue description | Versions affected | Status |
|---|---|---|---|
| Page views | Article page views track multiple times when one article is visited, caused by the “page changes based on browser history events” setting in the GA console. | Since GA4 | Fixed in Bolt Web 5.20.0 |
| All events | Only page views sent when interacting with Bolt Web. | 5.17.7 | Fixed in Bolt 5.20.0 |
| Page views |
Multiple page view events recorded per user action caused by automatic page view tracking in GA4 and Mixpanel
Manual page view tracking behaviour moving forward:
|
All versions | Fixed in Web 6.2.12 |
Third party providers
| Event / feature | Issue description | Status |
|---|---|---|
| GA4 engagement_time | Cannot be sent with manually tracked screen_view event on iOS (see Firebase post). Sends with separate user_engagement event. | Pending Firebase fix |
| GA4 engagement_time | Elevated engagement duration on Android. See Firebase issue for more detail. Firebase made improvements in May 2024 however engagement duration on Android may remain inflated. | Pending Firebase fix |