[Spike 2 hours] Create document enumerating possibilities for search referrer metric
Closed, ResolvedPublic1 Story Points

Description

To achieve T115652: Dashboard: Create performance indicator on referrer traffic and our third Q2 goal, let's create a short document enumerating some possibilities for the metric and run it past @Wwes, @Tfinc, et. al.

I've set this as a two hour spike to keep the feedback loop short, because it's an initial stab at the metric and further iteration will be required.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 19 2015, 4:14 PM
Deskana changed the title from "[Spike 2 hours] Create document enumerating possibilities for " to "[Spike 2 hours] Create document enumerating possibilities for search referrer metric".Oct 19 2015, 4:16 PM
Deskana set Security to None.
Deskana assigned this task to Ironholds.

Moving to in progress and assigning, per IRC discussion with @Ironholds.

Ironholds edited a custom field.Oct 19 2015, 5:34 PM

Very simple and quick writeup at https://www.mediawiki.org/wiki/Wikimedia_Discovery/External_search_metrics

Put simply, my recommendation is we start with referer counts. If we want to do something more complex than that, we can use the referer counts to inform what that 'something more complex' should be, and how we would handle implementing it incrementally to be as beneficial to our customers as possible, as early on as possible. I will reiterate that that second part is still going to need resourcing, however!

+1 to the recommendation. Start simple.

Deskana closed this task as "Resolved".Oct 23 2015, 7:46 PM

We're proceeding with a first iteration based on the above document. That worked is being tracked in T115652: Dashboard: Create performance indicator on referrer traffic. As the intention of this task was to document our first iteration, this task is resolved.