Change Details

As a data analyst, I want to be able to easily distinguish HoverCards hovers as `preview` classified requests in Hive, so that I can ascertain their impact on user interaction with the site. ##Acceptance criteria [x] API web requests triggered on a hover will include an HTTP header `X-Analytics: preview=1` so that they can be classified in Hive ##Sign off [ ] Standardized reports contain the preview metric in some sensible manner in context with pageviews [ ] Verify in Hive that well formed URLs contain the expected X-Analytics value HoverCards to stable desktop web is tentatively slated for Q4 FY 2015-2016 (April-June, 2016), and this is a hard requirement of that work.

As a data analyst, I want to be able to easily distinguish HoverCards hovers as `preview` classified requests in Hive, so that I can ascertain their impact on user interaction with the site. ##Acceptance criteria [x] API web requests triggered on a hover will include an HTTP header `X-Analytics: preview=1` so that they can be classified in Hive HoverCards to stable desktop web is tentatively slated for Q4 FY 2015-2016 (April-June, 2016), and this is a hard requirement of that work.

As a data analyst, I want to be able to easily distinguish HoverCards hovers as `preview` classified requests in Hive, so that I can ascertain their impact on user interaction with the site. ##Acceptance criteria [x] API web requests triggered on a hover will include an HTTP header `X-Analytics: preview=1` so that they can be classified in Hive ##Sign off [ ] Standardized reports contain the preview metric in some sensible manner in context with pageviews [ ] Verify in Hive that well formed URLs contain the expected X-Analytics value HoverCards to stable desktop web is tentatively slated for Q4 FY 2015-2016 (April-June, 2016), and this is a hard requirement of that work.