- User Since
- Sep 7 2015, 3:24 PM (394 w, 3 d)
- LDAP User
- MediaWiki User
- Verena Lindner (WMDE) [ Global Accounts ]
Jan 6 2022
Dec 6 2021
Nov 1 2021
Oct 31 2021
Oct 27 2021
Quick answer! Oh no, you are right :(
Sep 27 2021
Sep 13 2021
Jun 1 2021
May 3 2021
Thanks for the ping. We have to check if we need the data and get back asap.
Mar 24 2021
Mar 23 2021
No worries. For the landingpage the campaign tag is ?campaign=WMDE_aw21 Any entries in the database related to that tag should be included in the report.
For any campaign-caused registration the edits should be tracked. This includes registrations through the Landingpage.
Feb 1 2021
Sep 8 2020
Sep 3 2020
No, we don't. Thank you for your work. I will close the ticket.
Aug 14 2020
We have 2 more requests:
Jul 23 2020
Jul 15 2020
Ok. Thanks for the update.
Jul 8 2020
Jul 7 2020
Jun 25 2020
May 25 2020
Thank you for the update and a relief that we have access to that information.
May 20 2020
Because the campaign is already active and because cryptic tags in links on Wiki pages are usually considered as bad style we will have to refrain from adding these tags and accept some ambiguity concerning the page views von 2b and 2c.
I could not fully understand the discussion on gerrit, but deploying the patch seems more complicated than expected. The possibility to track registrations would be nice but it is not a must have for this campaign.
May 19 2020
Ok, so where would we need these tags? I assume we have to add them to the links to landing page 2b and 2c which are on the first landing page?
May 18 2020
@GoranSMilovanovic As for the research questions: We will do your best to have the questions ready but the analysis can also be done after your absence.
All users see the same [[ de.wikipedia.org/wiki/Wikipedia:Wikimedia_Deutschland/DeinEngagement | landing page ]] after their banner click. Landing Page 2b and 2c both are links on that page. These links don't contain tags. Would you need that to find the event in the database? Or is it possible to find out if users who clicked on the banners later also viewed one of these 2 pages or both?
@Addshore Could you give us an update if the patch was deployed today?
May 13 2020
Thank you Kai. It seems that the campaign tags have changed. Could you please provide the new campaign tags for all banners?
May 12 2020
Thank you all. @GoranSMilovanovic That means we are set and ready? Or is further testing before the campaign set recommended?
May 6 2020
Update: Deployment of scheme update will be on Monday, 11th May.
Apr 30 2020
@GoranSMilovanovic : We made some progress here. The eventlogging scheme will be updated so that user ids should be available. Testing of that is going to happen next week (probably)
Apr 23 2020
@GoranSMilovanovic Does that help you?
Apr 15 2020
The illustrations have been added. As for the other information I just need the contact of who will implement the banners. He/she will get access to the agency's Zep.lin sharing account.
Apr 14 2020
Ok. Will it have an impact on the estimation?
Great! I just updated the target links. If you can deliver different size versions we would like to track them. Does that have an impact on the estimated time? If yes, please let me know.
Apr 8 2020
@kai.nissen Okay, I will provide the information as soon as possible.
Apr 7 2020
Apr 3 2020
Jan 9 2020
@A00604591 Unfortunately I don't know if that is anyone's job. But a person to contact would be @Jseddon
Jan 7 2020
Dec 9 2019
Oct 29 2019
Yes, I cann access Turnilo and Superset both. Thank you.
Oct 18 2019
@RStallman-legalteam Thank you for reaching out and taking action. I just signed.
Oct 9 2019
Oct 2 2019
Oct 1 2019
I understand. Do these numbers apply to a specific time frame or are these lifetime edit counts?
E.g. in month xx of the year xxxx of all the users who made 1 to 4 edits, 40,788 have registered in 2019 vs.
of all the users who made 1 to 4 edits until now, 40,788 have registered in 2019.
@GoranSMilovanovic Please give me some explanation on the data and your understanding what the numbers mean (Because I don't know it). We might have had a misunderstanding here.
Sep 30 2019
Thank you for solving the problem and delivering today.