Confirmed users
534
edits
Firefox/Stub Attribution: Difference between revisions
Jump to navigation
Jump to search
Add init projects
(→Communications: update) |
(Add init projects) |
||
| Line 22: | Line 22: | ||
= Projects = | = Projects = | ||
== | == Construct and transmit attribution code on mozilla.org == | ||
= | [https://bugzilla.mozilla.org/show_bug.cgi?id=1259612 Bug 1259612] [tracking] Construct and transmit attribution code on mozilla.org | ||
== | When users visit the Mozilla download page, the website will construct an attribution code. | ||
* DRAFT algorithm: https://docs.google.com/document/d/1DzIg19kAdtYEzS_waQNCQBfi8CSGj4cl9N8T24WSiyc/edit#heading=h.883gjcln63zt | |||
* Example attribution code hashes from real mozilla.org download: https://docs.google.com/spreadsheets/d/1U-0JHpc3INJnBwTFkdrPqpk7yqvpEn16DJtp6d6TRiY/edit#gid=1351498707 | |||
* No tracking codes will be used if the user has DNT set. | |||
* A single, encrypted, code. | |||
* Owner: mozilla.org website team | |||
== | This code will be passed to bouncer via a URL param. For example: | ||
* https://download.mozilla.org/?product=firefox-45.0-SSL&os=win&lang=en-US&stub_attcode=utm_getfirefox | |||
* In the future other stub_ codes may be present, to signal things other than attribution: for example users who opted into telemetry or already saw the “know your rights” privacy notice | |||
* Owner: mozilla.org website team | |||
== Pass stub_attcode to the stub installer == | |||
[<span style="color:red;">blocked</span>] 25-Mar: Lots of questions on how to do this. Working on it. | |||
(Current plan, pending discussions) | |||
* The stub installer will be constructed with a special section that can be modified without invalidating the signing | |||
** For more details about the options, see https://docs.google.com/a/mozilla.com/document/d/1iMkD-tqjHq59ZffFXGRp4aw8wHDENauQ9oaifiRNtNo/edit?usp=sharing | |||
* Bouncer will point to a modified version of the normal stub installer: the stub_attcode and other stub_* attributes will be passed through as bytes in the stub installer binary. | |||
** pending questions on if this is possible. | |||
* The stub installer self-extractor will pass this info (when present) to the stub installer. | |||
** Owner: install/update team | |||
* The stub_attcode will be sent with the stub installer success ping. | |||
** Owner: install/update team | |||
* The stub_attcode will be saved to disk with the install. | |||
** This is how it gets passed to Firefox for use with Telemetry. | |||
** Owner: install/update team | |||
== We will include the stub_attcode value in the unified telemetry activation ping == | |||
[https://bugzilla.mozilla.org/show_bug.cgi?id=1120370 Bug 1120370] Implement a Telemetry activation ping | |||
* ... (and potentially ongoing UT main pings) | |||
* First time you run Firefox on a new profile. This is a new bug. | |||
* Questions | |||
** Do we need to send the code with main pings for a specified time period? If so, we’ll need a bug | |||
** If the attribution code is only sent on the activation ping, do we use profileID to correlate a profile with a specific cohort? | |||
* Owner: bsmedberg or install/update team | |||
== Construct a funnel dashboard that for each code lets us monitor the funnel in close-to-realtime == | |||
[https://bugzilla.mozilla.org/show_bug.cgi?id=1259614 Bug 1259614] [tracking] Construct a funnel dashboard for Stub Attribution that allows us to inspect the funnel in close to realtime | |||
Metrics | |||
* campaign clicks (logs/GA) | |||
* Download clicks (bouncer logs) | |||
* Install success (stub install ping) | |||
* Firstrun (UT activation ping) | |||
* Ongoing churn and engagement (UT main pings) | |||
Owner: Heather team, with kparlante responsible for pings coming through system. | |||
= Team = | = Team = | ||