Both skin preference and global preference reflect the status as of the data collection date, which is April 15, 2024.

@JAllemandou @BTullis, Thank you very much for detailed explanation! I will move from hive to presto and spark. I am going to mark this ticket as resolved.

@ovasileva, here are the analysis result. The answer to the third questions is a very rough estimate. Let me know if you disagree with any of the assumptions.

What is the default font value on vector-2022 ? Regular

Here is the font size stats on desktop web by skin version. A few questions based on the data

1. What is the default font value on vector-2022 ?
2. What do the values 0, 1, 2 , and disabled stand for on vector-2022?
3. What is the default font value on vector ?

As a followup, I have documented sample rate at data hub.

As a followup, the sample rate is document at datahub

As a followup, I have documented the current sample rate at https://datahub.wikimedia.org/dataset/urn:li:dataset:(urn:li:dataPlatform:hive,event.mobilewebuiactionstracking,PROD)/Documentation?is_lineage_mode=false

• Following the inclusion of client hints in the analysis, there was an average increase of 2 in the maximum number of unique user agents on a daily basis.
  • Throughout January 2024, the daily maximum rose from 6 to 8 unique user agents per IP on English Wikipedia.
  • For some days, the increase in maximum after including client info could be as large as 5.

Based on the number of events captured in the old and new schema, we believe the new schema is configured with the same sample rate as the old schema, as mentioned in T353029#9621127. However, it is recorded as 100% for all wikis in the new schema.

@KSarabia-WMF , thanks for the info.

@KSarabia-WMF, thanks for checking. Can you also clarify what's the sample rate for logged-in users?

Hi, @KSarabia-WMF , Can you confirm if below sample rate captured in the new schema is correct?

@kostajh, please see the findings below.

Methodology

We reviewed the distribution of the number of distinct user agents that appear for a given IP address per day on each pilot wiki candidate and the largest wiki enwiki.
We also reviewed the worst-case scenario: the maximum number of the distinct user agents that appear for a given IP address per day across all wikis.
The analysis is limited to anonymous edits committed between 2024-01-01 and 2024-01-31.

@KSarabia-WMF, can you also provide the sample rate of the old schema DesktopWebUIActionsTracking? Thanks.

@KSarabia-WMF, can you also provide the sample rate of the old schema MobileWebUIActionsTracking? Thanks.

HI @ovasileva, please see my investigation summary below.

Thanks for checking on it. Regarding 0.2% discrepancy, it can be marked as PASS given 1) it's within variance range , 2.5% variance for daily events across all wikis, that we defined in Metrics Platform Instrument Migration Data QA Process Description ; 2) the new instrumentation is capturing more unique sessions than old instrumentation.

I'll defer to Jennifer about 2 vs auto. I think it's better to do 2 personally in case these definitions ever change in future this will be more resilient to change.

Migration of desktopwebuiactionstracking schema is ready for QA.
The mobilewebuiactionstracking schema is pending for migration.

Hi, thank you for bringing up and clarifying that.

@phuedx, Here are some findings from my investigation.

Here are the baselines for devices with a viewport larger than 1200px. @ovasileva , let me know if you have any questions.

Preview disable rate (viewport > 1200px)

Metric: Number of unique sessions with preview off (non-default)/ total number of unique initialized sessions (viewport > 1200px).
The following statistics are based on the data collected between Dec. 21, 2023 and Dec. 31, 2023

@phuedx, Thanks for resolving all the questions. I will further investigate the remaining question of why the numbers of events, sessions and pages are slightly higher in the new schema. Will bring it up to you when I have more data.

Questions to confirm with engineers

1. The number of events, sessions and pages are slightly higher in the new schema. Is it expected?
2. Which field is to capture Spider user agent?
3. Is access_method captured in agent.client_platform_family in the new schema?
4. Please review the field mapping table below and confirm whether all entries are as expected.

Perhaps the best thing to do here would be to only consider devices with > 1200px for the desktop milestone. What do you think?

I have further investigated the preview disable rate in 1000px-1199px viewport bucket, analyzing it by device families and wikis.
In summary, the high preview disable rate in the 1000px-1199px bucket is influenced primarily by devices in the Mac family, specifically those running Mac OS X with the version details: os_major 10 and os_minor 15.

By device family

@ovasileva, @Jdlrobson, I have reran the analysis using the recent data as we discussed.

Dashboard has been published at https://superset.wikimedia.org/superset/dashboard/p/xgaOAD5rz2A/

Hello @Sj, we only collect data on the viewport size buckets, and these are segmented into six groups. Unfortunately, 1400px is not the threshold to divide groups. I hope the data below still provides insights into how full-width preference varies in each group.

Hi @ovasileva , when I analyzed the data based on the viewport size buckets, I noticed that the preview disable rate in the 1000px-1199px group was significantly higher than in the adjacent bucket groups for both anonymous users and logged-in users. Is there any specific reason for this?

Hi @Sj, we have discussed your questions within the team. The request requires recording the reader's user_id along with the timestamps of their visits and clicks. We don't track such detailed info for readers. The session based stats are the closest approximation we have for readers.

@Sj, please see the broken down of preview, width and media viewer at T346979#9285473.

Summary of data QA for the data collected on Dec 14, 2023

All to-dos are done.

@ovasileva ,please see the analysis of pin rate and overall non-default rate below.

Methodology

@ovasileva , here is the baseline collection for font size on mobile web. Let me know if you have any questions.

Summary

% of pageview sessions which have set a non-default font size in the Minerva skin (On mobile web)

Metric: Number of unique sessions with regular font size disabled (non-default) / total number of unique initialized sessions
The following statistics are based on the data collected between Nov.4, 2023 and Nov.8 , 2023 (incomplete date) ,

Summary of data QA for the data collected on Nov 8, 2023

Minerva (Mobile)

Schema: event.MobileWebUIActionsTracking
Instrumentation purpose: collect baseline for % of pageviews which have set a non-default font size in the Minerva skin (On mobile web)

What has been checked	Field name	Status	Note	Snapshot of the result
Font size	event.font	✅ PASS	The expected values are: small, regular, large, xlarge. The numbers of '0' and ‘NULL’ are tapering off, but will take more days.