Tiles/Data Collection: Difference between revisions
(minor cleanups, updates to the release status. added 'moving' to the list of events where information is sent) |
|||
| Line 1: | Line 1: | ||
== Current Status == | == Current Status == | ||
In | In a future Firefox release and current pre-release builds, the following information is sent to Mozilla about [[Tiles|tiles]]: | ||
On viewing the new-tab page, blocking a tile, moving, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent: | |||
=== History tiles === | === History tiles === | ||
* | * Position of the tile (ex: 0-8 for a user with 8 visible tiles ) | ||
* | * Pin status of the tile (ex: pinned = true ) | ||
* | * Tile frecency factor (ex: int(Frecency/1000)) | ||
* No tile ID or URL information is sent for history tiles | * '''No''' tile ID or URL information is sent for history tiles | ||
=== Directory and Enhanced tiles === | === Directory and Enhanced tiles === | ||
The information for History tiles, plus: | |||
* The tile ID (which encodes the tile destination) | * The tile ID (which encodes the tile destination) | ||
* A signal (empty string; no URL) if the tile is enhanced | * A signal (empty string; no URL) if the tile is enhanced | ||
| Line 20: | Line 22: | ||
A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed. | A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed. | ||
The data is sent via a SSL connection | The data is sent via a SSL connection with Key-pinning (as of {{bug|1030135}}) to mozilla cloud services. No extra tracking cookies are set by the server for this ping. | ||
When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers. | When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers. | ||
Revision as of 17:23, 14 October 2014
Current Status
In a future Firefox release and current pre-release builds, the following information is sent to Mozilla about tiles:
On viewing the new-tab page, blocking a tile, moving, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent:
History tiles
- Position of the tile (ex: 0-8 for a user with 8 visible tiles )
- Pin status of the tile (ex: pinned = true )
- Tile frecency factor (ex: int(Frecency/1000))
- No tile ID or URL information is sent for history tiles
Directory and Enhanced tiles
The information for History tiles, plus:
- The tile ID (which encodes the tile destination)
- A signal (empty string; no URL) if the tile is enhanced
Other Details
A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed.
The data is sent via a SSL connection with Key-pinning (as of bug 1030135) to mozilla cloud services. No extra tracking cookies are set by the server for this ping.
When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers.
Descriptions for the payload schemas for the pings can be found here
Prospecting Future Tile Partners
In addition to continuous data collection required for partners, we also want to collect information about current user history tiles, to provide business guidance about which sites are most valuable to our users for picking both Directory and Enhanced Tiles.
Proposal:
- Run a limited-time experiment in the beta channel to collect information about the top history site information.
- Rather than sending any URLs, prepare in advance a potential list of top sites or partners as a whitelist of sites. Only send information about tiles on this whitelist, and only send the TLD+2, not the full URL. This will avoid sending many kinds of personal URLs.
This prospecting experiment is tracked in bug 1062708