> WE 2.1.1 for FY25-26: If we invite native speakers of small wikis through a CentralNotice banner on a high-traffic Wikipedia in their region to contribute to SuggestedEdits and other Growth features, we can assess whether this approach attracts new native speakers and if they use these editing tools to improve vital content.
From @srishakatux
* the experiment will target both logged-in and logged-out users.
* CN banner will lead them to the Newcomer homepage.
* If they are not logged in, they'll be directed to the login page.
* If they have an account and are logged in, they'll land directly on the Newcomer homepage.
* If they don't have an account they will redirected to create an account
//and then ... other steps will continue //
At this stage we need to track who created the account using the banners, for later measurements and to follow-up if needed.
One of the ways this tracking can be done is to set
* `campaign` field in [[ https://gitlab.wikimedia.org/repos/data-engineering/schemas-event-secondary/-/blob/master/jsonschema/analytics/legacy/serversideaccountcreation/1.3.0.yaml#L46 | serversideaccountcreation ]] stream
* stream: `/analytics/legacy/serversideaccountcreation/1.3.0`
* It can be simple: `fy25-we211-banner` or something similar.
The data can then be queried from `event.serversideaccountcreation` or `event_sanitized.serversideaccountcreation`
A possible open engineering question is how we set this on CentralNotice side or during redirection (not sure what is the best way for implementation).
----
Previous examples of similar work by other teams:
* {T321370}
* {T387286}
* [[ https://wikimedia.slack.com/archives/CLKDS4MG9/p1744120297954659 | Slack conversation that might be helpful ]]