2014-02-24 18:41 GMT+02:00 Dario Taraborelli :
> Hi Strainu
>
>>> that’s correct: we do have aggregate entry/exit reports based on panel data
>>> from comScore for all Wikimedia properties ,
>>
>> What does that mean, exactly?
>>
>> Strainu
>
> we obtain from comScore on a monthly basis aggregate d
2014-02-23 22:25 GMT+02:00 Dario Taraborelli :
> that’s correct: we do have aggregate entry/exit reports based on panel data
> from comScore for all Wikimedia properties ,
What does that mean, exactly?
Strainu
>
> On Feb 23, 2014, at 11:29 AM, Oliver Keyes wrote:
>
> To my knowledge we don't hav
Magnus – yes: just to be clear, this is not particularly challenging from a
technical standpoint (EventLogging could be used for this purpose) and I also
expect the volume of events to be low compared to page impressions, as clicks
on external links are in general two steps away from a page visi
Hi Strainu
>> that’s correct: we do have aggregate entry/exit reports based on panel data
>> from comScore for all Wikimedia properties ,
>
> What does that mean, exactly?
>
> Strainu
we obtain from comScore on a monthly basis aggregate data on the % of entries
by referrer domain (e.g. YouTube
FWIW, I once had some JavaScript added to the common JS script on Commons,
collecting anonymized clicks to external links on image pages, in an
attempt to give some stats to the GLAM community. That would fire off basic
data like time, page, and target URL to a toolserver logging script. Volume
was
that’s correct: we do have aggregate entry/exit reports based on panel data
from comScore for all Wikimedia properties , but no exit data at the individual
article/link level. Raw request logs do not include this information and for
this data to be captured we would need to add ad-hoc instrument
