Page MenuHomePhabricator

create test banners (dummy)
Closed, ResolvedPublic3 Estimated Story Points

Description

As we will use only 2 different banners, please create 2 dummy-banners with the tracking information shared in T191497.

Acceptance Criteria:

  • The banners contain a link to the landing page.
  • The links pass the campaign tag to the landing page using the parameter campaign.
  • The page names of the banners match the campaign tags.
  • The campaign tag (and banner page name) of the first banner is defined as WMDE_2018_sprbt1.
  • The campaign tag (and banner page name) of the second banner is defined as WMDE_2018_sprbt2.

Event Timeline

kai.nissen set the point value for this task to 3.

@kai.nissen Thank You for the setup!

@GoranSMilovanovic I've clicked the links today on Fr. 20. April between 15:30 and 15:40. I also clicked on the Banner with the landingpage and created a test account (Testttttt123) with the campaign tag campaign=WMDE_2018_sprbt1. Could you please check, if the test created the data we will need for our campaign?

@Stefan_Schneider_WMDE @kai.nissen

A. Pageviews (== Banner Clicks)

The following HiveQL query was run on 24. April 2018. approx. 00:50 CET:

USE wmf;
  SELECT uri_path, uri_query, referer FROM webrequest
  WHERE
    uri_host = 'de.wikipedia.org'
    AND uri_path = '/wiki/Wikipedia:Wikimedia_Deutschland/LerneWikipedia'
    AND year  = 2018
    AND month = 4
    AND day = 20
    AND ((uri_query LIKE '%WMDE_2018_sprbt1%') OR (uri_query LIKE '%WMDE_2018_sprbt2%'));

resulting in:

uri_path        uri_query       referer
/wiki/Wikipedia:Wikimedia_Deutschland/LerneWikipedia    ?campaign=WMDE_2018_sprbt1      https://de.wikipedia.org/?banner=WMDE_2018_sprbt1
/wiki/Wikipedia:Wikimedia_Deutschland/LerneWikipedia    ?campaign=WMDE_2018_sprbt1      https://de.wikipedia.org/?banner=WMDE_2018_sprbt1
/wiki/Wikipedia:Wikimedia_Deutschland/LerneWikipedia    ?campaign=WMDE_2018_sprbt2      https://de.wikipedia.org/?banner=WMDE_2018_sprbt2

In conclusion, the clicks on dummy banners have produced the respective pageviews. All fine. However, your user registration procedure does not seem to work (see section B).

B. User Registration

The currently valid log.ServerSideAccountCreation schema to track user registrations is 17719237.
We can check that by querying:

SELECT MIN(timestamp), MAX(timestamp) FROM log.ServerSideAccountCreation_17719237;

which results in:

+----------------+----------------+
| min(timestamp) | max(timestamp) |
+----------------+----------------+
| 20180208223038 | 20180423231840 |
+----------------+----------------+

The following SQL query, run on 24. April 2018, approximately at 01:25 CET:

SELECT event_campaign, count(*) FROM log.ServerSideAccountCreation_17719237 WHERE timestamp >= 20180420000000 GROUP BY event_campaign;

has produced the following:

+---------------------------+----------+
| event_campaign            | count(*) |
+---------------------------+----------+
|                           |    28417 |
| ACP1                      |        1 |
| ACP2                      |        6 |
| anoneditwarning           |     2106 |
| anonwelcometemplate       |        3 |
| loginCTA                  |    12740 |
| mobile_watchPageActionCta |      669 |
| semiprotectednotice       |        4 |
+---------------------------+----------+

In conclusion, no users with event_campaign tag of WMDE_2018_sprbt1 or WMDE_2018_sprbt2 where registered on or following 20. April 2018, as suggested by @Stefan_Schneider_WMDE T191506#4145875

@GoranSMilovanovic: Thx for checking the tracking. I've just created two different accounts from both campaign tags. Could you please recheck the data and maybe ask Adam for help here? I think he always had a fast solution on those topics.

I've created the following accounts (between 11:00 and 11:10):
Tesssstt from the WMDE_2018_sprbt1-Tag
Teeeesst from the WMDE_2018_sprbt2-Tag

@Tobi_WMDE_SW @Addshore Hi guys, do you know if we need the hack for the tracking of new registrations? That would explain, why there is no registration data in the tables.

@Tobi_WMDE_SW @Addshore Hi guys, do you know if we need the hack for the tracking of new registrations? That would explain, why there is no registration data in the tables.

This depends if users are being directed straight to the registration page using a campaign param in the URL or via another landing page.

@Addshore: The user journey is as follows: banner --> landingpage --> registration --> back zu landingpage --> training modules --> first edit

@Stefan_Schneider_WMDE Nothing yet, from:

SELECT event_campaign, count(*) FROM log.ServerSideAccountCreation_17719237 WHERE timestamp >= 20180420000000 GROUP BY event_campaign;

we get to

+---------------------------+----------+
| event_campaign            | count(*) |
+---------------------------+----------+
|                           |    31954 |
| ACP1                      |        1 |
| ACP2                      |        8 |
| anoneditwarning           |     2379 |
| anonwelcometemplate       |        3 |
| FundEdit_SE18             |        6 |
| FundEdit_SE18-NM          |        2 |
| loginCTA                  |    14177 |
| mobile_watchPageActionCta |      740 |
| semiprotectednotice       |        6 |
+---------------------------+----------+

Pls check your user registration tracking settings.

@Addshore: The user journey is as follows: banner --> landingpage --> registration --> back zu landingpage --> training modules --> first edit

@Stefan_Schneider_WMDE That would mean we need the code (aka hack) in place. Please coordinate with @Addshore. I suggest deploying it right away as soon as @Addshore has time for it.

@GoranSMilovanovic

After Adam deployed the hack I now did another test registration:

Teeestttt = WMDE_2018_sprbt1
Tessttte = WMDE_2018_sprbt2

This was between 11:45 and 12:00 on 03. May 2018. Could you please check if it worked this time?

@Stefan_Schneider_WMDE User registration tracking is now in place. The following query

SELECT event_campaign, count(*) FROM log.ServerSideAccountCreation_17719237 WHERE timestamp >= 20180503000000 GROUP BY event_campaign;

results in:

+---------------------------+----------+
| event_campaign            | count(*) |
+---------------------------+----------+
|                           |     9464 |
| ACP1                      |        1 |
| ACP2                      |        5 |
| anoneditwarning           |      744 |
| loginCTA                  |     4107 |
| mobile_watchPageActionCta |      195 |
| semiprotectednotice       |        1 |
| uploadCampaign:wle-br     |        3 |
| WMDE_2018_sprbt1          |        1 |
| WMDE_2018_sprbt2          |        1 |
+---------------------------+----------+

This open task is associated to a project for Spring 2018 (a year ago). Any updates? Is this task still valid? Should it be associated to a project that's not in the past?