Please let me know the deploy date as early as possible as I need to reserve a slot in the deployment calendar, which may get filled.

Interface pages:

"Reader-demographics-1-description" : "", //leaving blank, because it was blank for a previous survey: https://en.wikipedia.org/wiki/MediaWiki:Reader-segmentation-1-description
"Reader-demographics-1-link" : "https://docs.google.com/forms/d/e/1FAIpQLSdEkmzsJphxoAJohZWoll80AT4Q-ExJvia_-lT9bKOL-uofOw/viewform?hl=en"
"Reader-demographics-1-message" : "Take a short survey and help us improve Wikipedia."
"Reader-demographics-1-privacy" : "Survey data handled by a third party. https://foundation.wikimedia.org/wiki/Survey_Privacy_Statement_for_Schema_Revision_15266417 "

Pages created:

https://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Reader-demographics-1-message
https://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Reader-demographics-1-privacy
https://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Reader-demographics-1-description
https://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Reader-demographics-1-link

Please let me know the deploy date as early as possible as I need to reserve a slot in the deployment calendar, which may get filled.

Thanks for reminder re: deployment -- still waiting on privacy statement but as soon as that is finalized and uploaded to foundation, I'll message you.

Also: interface pages now created on beta enwiki as detailed above so I think we're ready to test at least. Is there anything else that I can provide to help launch it on beta or specific things I should be checking for once it's launched?

Yes, let's add the configuration for the survey to the description of this task and the parent task (one for production — I imagine they'll be the same, they will be good documentation for the future).

Oh I see the parent task already has it: T217080.

Yeah, the parent-child relationships in phab are somewhat of a mess as I figure these things out but i linked this to T217080 so that it would be clearer

Change 493103 had a related patch set uploaded (by Bmansurov; owner: Bmansurov):
[operations/mediawiki-config@master] Labs: Enable reader demographics survey

https://gerrit.wikimedia.org/r/493103

I'll enable the survey in the beta cluster in about 4 hours from now.

enabling this evening is great and thanks for updating the testing details. i'll try to do the testing then and also will add those details to the documentation

Change 493103 merged by jenkins-bot:
[operations/mediawiki-config@master] Labs: Enable reader demographics survey

https://gerrit.wikimedia.org/r/493103

The change's been deployed. It should be live in about 15-30 mins.

Scratch that, the config was not complete. I missed the 'enabled' => true, part. I'll redeploy tomorrow.

Not seeing the survey at https://en.wikipedia.beta.wmflabs.org/wiki/Book

Just the reader trust survey appears despite refreshes / dismissing it. On inspection, the only potential issue I can see is that it appears that the config is missing 'enabled' => true

Change 493221 had a related patch set uploaded (by Bmansurov; owner: Bmansurov):
[operations/mediawiki-config@master] Labs: actually enable the demographics survey

https://gerrit.wikimedia.org/r/493221

Change 493221 merged by jenkins-bot:
[operations/mediawiki-config@master] Labs: actually enable the demographics survey

https://gerrit.wikimedia.org/r/493221

@Isaac the survey should be live in about 15-30 mins.

Ignoring the issues with caching and the links (T217282), the pageviewToken is correctly being loaded into the Google Forms survey and matches the token being recorded in the QuickSurveyInitiation and QuickSurveysResponses schemas.

Interestingly, opening the survey in a new tab did not trigger the QuickSurveysResponses schema as far as I could tell from the client side (by watching the network tab in the web console), which is odd though not a blocker (the QuickSurveyInitiation schema gives not all but enough information in most cases)

Also, not sure if this is expected behavior or not, but I only see the survey on mobile when looking at Spain, but not Book:

See: https://en.m.wikipedia.beta.wmflabs.org/wiki/Spain
Don't see: https://en.m.wikipedia.beta.wmflabs.org/wiki/Book

That's true even when I append ?quicksurvey=external-survey-reader-demographics-en-pilot to the end of the URL

Interestingly, opening the survey in a new tab did not trigger the QuickSurveysResponses schema as far as I could tell from the client side (by watching the network tab in the web console), which is odd though not a blocker (the QuickSurveyInitiation schema gives not all but enough information in most cases)

It maybe worth creating a separate task for this.

The Book issue is known: T210646: Quick surveys do not show up on pages without infoboxes that have table of contents (The task you linked in the description).

Thanks for linking to that Book issue. After reading through, it looks like while it still is an issue on Beta, it's not supposed to affect production any more. I'll see what I can do to verify this when the pilot runs.

And I'll dig into the Responses EL issue to see the extent of it.

@bmansurov after doing a bit more digging, I think what is going on with the right-click + "open in new tab" is very similar to what was reported here re: hovercards: T147846

Not clear if this is just beta or production too. I see the behavior on Chrome and Firefox. Notably:

• right-click + "open in new tab" = no events triggered (survey link remains instead of switching to "thank you" and no QuickSurveysResponses EL)
• cmd+click (which also opens the survey in a new tab) = events triggered (survey box changes to "than you" and QuickSurveysResponses EL triggers)

@Isaac OK, thanks for looking into this. I think it's worth keeping in mind when doing analysis. If we want an event triggered on right-click + "open in new tab", then we should create a task for it.

Yeah, if I recall there weren't too many instances in the previous reader motivation survey where there was a completed survey but not a corresponding EL data point. I'll check this with the pilot and then see whether this seems to be an issue worth addressing (and quite possibly it doesn't even happen on production).