Summary / Rationale
When we build special APKs to be distributed to our preload partners, we give the APK a special "channel" fingerprint that gets sent via the User-Agent when the app is running. Unfortunately, if the preloaded app happens to get updated via the Play Store before the user runs it for the first time, the channel identifier gets erased. We need to make sure that the channel identifier gets preserved, so that we can measure more reliably our reach via preloads.
Goal Visibility
Reading internal goal
Success Metrics
To be able to consistently track the specific preload vendor from which eventlogging data originates, and be more compliant with the current options available for Wikipedia Zero banners.
External Dependencies
Unknowns
It's not clear what type of solution would best solve this issue. We may need to experiment with more than one.
Product Plan
Prototyping
See dependent tasks.
MVP
See mockups in dependent tasks.
Metrics Implementation
We are already instrumenting saved pages, so we will be able to measure the impact of this feature on the usage of saved pages.
Timeline Estimate
- Delivery Estimate