At the moment, pageviews that come from the Tabs screen might not be getting recorded/measured as we expect. Let's examine this logic and make sure it works for all pageview sources.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dbrant | T392580 Fix and/or streamline pageview analytics from Tabs screen. | |||
| Resolved | SNowick_WMF | T396260 Data Validation for Pageview/Tabs Fix |
Event Timeline
Comment Actions
@Dbrant could you please summarize the current Tabs pageview behavior to help me understand how Android measures it?
Questions on my mind
- When someone clicks on "Open in a new tab" from long-presses on an article link or from Article preview
- is that counted as a pageview...when they click when they click "open in new tab", or only when they open the article from the Tabs overview
- When someone opens "Apple" article from the Tabs overview, then navigates away, then opens the "Apple" article from the Tabs overview again, is that counted as 2 pageviews, or 1?
Comment Actions
Under the updated logic, a pageview is precisely defined as: any time content is loaded (or reloaded) into the WebView.
Therefore, if you long-press and click "open in new tab", this does not actually cause content to load into the WebView, and will not count as a pageview. If you proceed to open the Tabs screen and select that new tab, causing the content to get loaded, it will count as a pageview.
- When someone opens "Apple" article from the Tabs overview, then navigates away, then opens the "Apple" article from the Tabs overview again, is that counted as 2 pageviews, or 1?
This would be counted as 2 pageviews.
Comment Actions
Verifying we are seeing an increase in avg pageview/unique counts as expected from fix from users who had ''TabActivity'' events in android_breadcrumbs_event (data joined with android_article_link_preview_interaction) to get pageview counts.