Research:Timestamp position modification/Clicktracking

Event naming scheme

The general template for events logged in the timestamp position modification experiment is the following:

'ext.lastModified@' + version + '-' + key

where version is the version number as set in the configuration file and key is the event name, based on the following scheme:

[bucket id]-[event type]

Identifiers

Bucket IDs

ctr1

User in the control group (experiment #1)

tpm1

User in the experimental condition (experiment #1)

Full list of events

Unless otherwise specified all events are tracked at 100%.

ctr1-impression (1%)
tpm1-impression (1%)

ctr1-history_tab_link-click
tpm1-history_tab_link-click

tpm1-timestamp_link-click

ctr1-edit_tab_link-click
ctr1-section_edit_link-click

tpm1-edit_tab_link-click
tpm1-section_edit_link-click

ctr1-edit_tab_link-edit_attempt
ctr1-section_edit_link-edit_attempt
ctr1-edit_tab_link-edit_success
ctr1-section_edit_link-edit_success

tpm1-edit_tab_link-edit_attempt
tpm1-section_edit_link-edit_attempt
tpm1-edit_tab_link-edit_success
tpm1-section_edit_link-edit_success

Notes

• (semi)protected articles will not be editable by non-autoconfirmed users and should therefore be excluded in the log.
• rev_id's for *-edit_success events will be those of the successfully created revision.

Log format

Clicktracking data is stored using the following, tab-separated format:

enwiki ext.lastChange@0-tpm1-impression 20120113013257 1 w4dtyfWSw714KsgmMAAkdC7isy8CmHvP9 0 0 0 0 0 Pokémon|274278

Log format specification

1. project name (e.g. enwiki or ptwikisource)
2. event name (as documented above)
3. timestamp (in YYYYMMDDhhmmss format)
4. user category: 1 for logged in users, NULL for anons
5. user token: an anonymous token replacing user names or IP addresses
6. namespace: (e.g. 0 for the main namespace)
7. lifetime edit count (0)
8. 6-month edit count (0)
9. 3-month edit count (0)
10. last month edit count (0)
11. additional data (page_title, rev_id)