With the data aggregated across many users, we can now calculate how many total times a given Tile has been seen and visited. When our server receives a list of seen Tiles from an IP address, we record that the specific individual Tiles were seen and not the whole list. We also break up the data into smaller pieces that cannot be reconstructed to the original data. Our implementation of Tiles uses the minimal actionable dataset, and we protect that data with with multiple layers of security. History Tiles do not have an id, so we can only know that the user saw a history screenshot but not what page - except for early release channel Telemetry related experiments, we do not currently send URL information for Tiles, although of course we are able to infer it for the Directory and Enhanced Tiles that we have sent to Firefox. Unless a user has opted out by switching to Classic or Blank, Firefox currently sends a list of the Tiles on a user’s new tab page to Mozilla’s servers, along with data about the user’s interaction with the Tiles, e.g., view, click, or pin.ĭirectory and Enhanced Tiles are identified by a Tile id, (e.g., “Firefox for Android” Tile has an id of 499 for American English-speaking users while “Firefox pour Android” has an id of 510 for French-speaking users). to report to our commercial partners on volumes of interactions by Firefox usersĪnd we do these things in accordance with our data principles both to set the standards we would like the industry to follow and, crucially, to maintain the trust of our users.to determine if the experience is a good one.We need to be able to report data on user’s interactions with Tiles for two main reasons: Enhanced and Directory Tiles may both be sponsored, involving a commercial relationship, or they may be Mozilla projects or causes, such as our Webmaker initiative. In this post, I will describe how we report on users’ interactions with Tiles.Īs a reminder, we have three kinds of Tiles: the History Tiles, which were implemented in Firefox in 2012, Enhanced Tiles, where we have a custom creative design for a Tile for a site that a user has an existing relationship with, and Directory Tiles, where we place a Tile in a new tab page for users with no browsing history in their profile. Last week, I described how we get Tiles data into Firefox differently from the usual cookie-identified requests. ![]() ![]() Following the launch of Tiles in November, I wanted to provide more information on how data is transmitted into and from Firefox.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |