s. Parent Task
- Mentioned In
- T174947: Implement banners according to design
T175914: deliver test report from real wiki
- Mentioned Here
- T174948: Deploy 'hack' patch & logging for tracking user registrations and guided tour
T175914: deliver test report from real wiki
T174952: Preparation for daily reports
T175911: Testing: Tracking
Dummy banners are set up:
(we're talking about your dummy Banner D), and the clicks "ACCOUNT ANLEGEN" in the image at the bottom of the page, he or she will be redirected to:
which does not contain any campaign url parameter.
Q: How will we track how many users came to the registration page from this landing page?
EDIT. The same seems to hold for all other banners, indeed. Probably I can track the referral page for every page view of the Registration page, I guess?
- I can see the test banner clicks in the referer field of the wmf.webrequest table on the landing pages;
- I can also track the hits to the registration page from the respetive landing pages and/or the banner that point directly to it.
@kai.nissen Thanks a lot!
None of the following banners:
- - https://de.wikipedia.org/?banner=WMDE_editor_campaign_fall17_a
- - https://de.wikipedia.org/?banner=WMDE_editor_campaign_fall17_b
- - https://de.wikipedia.org/?banner=WMDE_editor_campaign_fall17_c
- - https://de.wikipedia.org/?banner=WMDE_editor_campaign_fall17_d
- - https://de.wikipedia.org/?banner=WMDE_editor_campaign_fall17_e
Can be found from the wmf.webrequest table for September 20, 21, and 22, from the following (essential only) HiveQL query parameters:
SELECT uri_query FROM webrequest WHERE uri_host = 'de.wikipedia.org' AND uri_path = '/beacon/impression'
On the other hand, many other WMDE banners can be found there (for example, campaign=wlm+2017-de-anon, campaign=C17_WMDE_Test07), and that's the method we have used during the Summer Banner Campaign to collect banner impressions.
Thanks Groan for the hint.
We can, of course, create test banners that will not be part of an active campaign, but can be forced to display by using the banner parameter. Calling banners with that parameters will not trigger an impression count, though.
Does that mean, that there will be no record in webrequest-table and thus no page-views tracked?
That impressions are not trackable was clear before starting this testing, though. If the pageviews are not trackable with the webrequest-table we can still track the banner clicks (@GoranSMilovanovic: please confirm) and thus the page views.
@Stefan_Schneider_WMDE No worries about the banner clicks and landing page/registration page views; I've already tracked the test data and I'm working on the report right now. Ok, so no banner impressions in the test report.
Q: Did you engage in any user registration, guided tour or editing from these pages during the test? Thank you.
Some people of our team clicked on every banner and I created some test accounts that you should be able to track. Unfortunately there was no Guided Tour shown after the registration.
@Addshore: Am I right, that the hack should start the guided tour after the registration? Is there something not working properly? I just tried again and the guided tour does not show up.
Could you please check whether you are tracking the referer for the Registration Page (Spezial:Benutzerkonto_anlegen) when the source is /wiki/Wikipedia:Wikimedia_Deutschland/Mach_mit?
I can't see any cases where users starts from /wiki/Wikipedia:Wikimedia_Deutschland/Mach_mit and lands on Spezial:Benutzerkonto_anlegen - could it be because the the user needs to click on an image on /wiki/Wikipedia:Wikimedia_Deutschland/Mach_mit in order to get there? Thanks.
"Some people of our team clicked on every banner and I created some test accounts that you should be able to track. Unfortunately there was no Guided Tour shown after the registration."
There are no event_campaign field values remotely similar to our campaign tags in the log.ServerSideAccountCreation_5487345 table. Please check whether the campaign user registrations are tracked properly.
Please let's avoid digging this out from server logs like we did last time. Also, please check whether Guided Tour tracking is enabled for this campaign.
Does the fix, that was deployed today, only correct the guided-tour-issue or also that the campaign tags are not recorded in the log.ServerSideAccountCreation_5487345 table. I got, that last time it worked like that. Could you have a look on it, please?
If all the bugs are fixed I would test it again and make sure everything works properly.
So I can confirm the code seems to be working.
Here are the server logs for the test I just carried out:
2017-09-25 15:46:47 [Wckk5wpAIDUAACychPkAAAAG] mw1183 dewiki 1.30.0-wmf.19 WMDE INFO: wmde_abc2017_bt2 - 1 - Banner click by anon user without cookie 2017-09-25 15:46:50 [Wckk6gpAEKoAAHE41goAAAAT] mw1215 dewiki 1.30.0-wmf.19 WMDE INFO: wmde_abc2017_bt2 - 2 - Inject campaign value on CreateAccount 2017-09-25 15:47:33 [WcklFQpAMFAAAIpZqdQAAABA] mw1245 dewiki 1.30.0-wmf.19 WMDE INFO: wmde_abc2017_bt2 - 3.e - User older than the campaign.
The last log line right now is generated by https://github.com/wikimedia/mediawiki-extensions-WikimediaEvents/blob/59d2eea7aa13a05a7de1fb16599ef310e4cd5b15/WikimediaEventsHooks.php#L762
The start time is set @ https://github.com/wikimedia/mediawiki-extensions-WikimediaEvents/blob/59d2eea7aa13a05a7de1fb16599ef310e4cd5b15/WikimediaEventsHooks.php#L697
Which is set to 20171004000000 (as I understand it this is essentially the start of the campaign)
No users will be shown guided tours until after that timestamp, but the guided tours will be shown then :)
Here's what I've found in log.ServerSideAccountCreation_5487345 last night (sometime between 00:30 and 1:40 CEST):
- wmde_abc2017_bt1 (2 registrations)
- wmde_abc2017_bt2 (1 registration)
Thanks for testing. That should be the data I created. It would have been more, but Wikipedia denied to create more accounts from my IP.
Ok, Great - then it's working now. Can't wait to see your updated report.
Now I get, why it wasn't working these days. We planned to test the guided tour beforehand. Is there a particular reason to start the guided tour only from the beginning of our campaign and not for testing issues right now? Then we could be sure that the tracking is working.
So firstly the reason the 'hack' broke for the tracking this time was due to changes that I made to make it easier to reuse for each campaign. The code that triggers the guided tour has not changed.
For the next campaign I may be able to simply make the campaign options configurable and avoid re deploying this hack each time, and just leave it in place and turn it on and off with different options.
The reason for the date limit is otherwise the following can happen (which happened in the first campaign)
- User registered since 2015 is logged out but views and clicks on a banner adding the session cookie to their browser.
- User logs in and views a mainspace page, as they have started the banner process and now have an account they would be shown the guided tour.
It might be possible to think of another way around this issue, perhaps by using multiple different cookies to identify each step / make sure a user lands on the registration page, or maybe even the successful registration page before having the chance of being shown the guided tour.
I'm not sure if it is worth working on this though as at one of the last meetings I understand we were thinking about stopping the guided tour all together?
It's no problem that it initially didn't work - that's why we are doing the test. So now it's cured :)
About the guided tour. Yeah, I remember this problem and totally get the date now. For now we will not change the user journey or any campaign tags, as it is too close to the start of the campaign. We will work on other ways of getting started in the wikipedia but if we reuse the guided tour again we will revisit that problem.