Page MenuHomePhabricator

Set up event and tool links tracking for the surfacing content gaps experiment
Closed, DeclinedPublic4 Estimated Story Points

Description

Users interact with the banner

Banner created using CN page, append url with wprov banner parameters

Click on CTA to land on the event page: https://te.wikipedia.org/wiki/Event:Vital_Knowledge_Drive_2025

Similar code example https://codesearch.wmcloud.org/search/?q=fy25-we211-banner1&files=&excludeFiles=&repos=

When detect banner parameters, append the wprov to all target links

Register for the event using the default feature of registration for CampaignEvents extension

  • for anon user, need to create an account before registering the event
  • for logged-in user, we have a list of participants on the event page

They create an account https://auth.wikimedia.org/enwiki/wiki/Special:CreateAccount

Use the wprov and campaign=fy25-we215-banner field

Account creation: https://auth.wikimedia.org/tewiki/wiki/Special:CreateAccount
They click article links to edit using Visual Editor: https://xx.wikipedia.org/w/index.php?title=pagetitle&veaction=edit
They click article links that take them to the Section Translation tool.
They click article links that take them to the Content Translation tool.

Append url with the wprov param and campaign=fy25-we215-banner and banner=fy25-we215-banner field if necessary.

User edit or create article through the VE, CX/SX tool

  1. submit a request through phabricator ticket to allow new tag https://en.wikipedia.org/wiki/Special:Tags
  2. use hook onRecentChange_save to add tag when user edit the article through VE
  3. use banner param on the url

Event Timeline

hueitan renamed this task from Technical setup for WE 2.1.5 to Technical setup for WE 2.1.5 Week 1.
hueitan claimed this task.
hueitan moved this task from Backlog to In Progress on the LPL Essential (FY2025-26 Q2) board.
abi_ triaged this task as High priority.Nov 18 2025, 11:19 AM
abi_ set the point value for this task to 2.

Change #1213967 had a related patch set uploaded (by Huei Tan; author: Huei Tan):

[mediawiki/extensions/WikimediaCampaignEvents@master] Setup tracking for CentralNotice banners experiment for WE2.1.5

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

hueitan changed the point value for this task from 2 to 4.Dec 3 2025, 12:29 AM

Change the story points as more details needed than the expectation, some still need clarification, it will launch in the coming January, we are here to prepare in advanced.

Thanks @hueitan for sharing a bit about tracking information via Slack. Continuing the conversation here, I have a few more questions:

  • Based on the parameter you shared, does this mean that the URL will become https://ne.wikipedia.org/w/index.php?title=Event:Name_of_the_event&campaign=fy25-we215-banner
  • Also, what will this URL help us track? Will it help us track which users came through the banner and what edits they made?
  • If you look at the work-in-progress event page here, you will see that there are many links embedded on that page, articles linked directly to Content/Section Translation and the Visual Editor as well. I’m wondering if we should also append the parameter to those links if we want to track clicks on them, the edits made on those pages, and the users who made those edits and whether they were part of the campaign, or if this is something that can be tracked independently.

Yes, adding the parameter to the event ULS helps us to know where they are coming from

  • Will it help us track which users came through the banner and what edits they made?
  • If you look at the work-in-progress event page here, you will see that there are many links embedded on that page, articles linked directly to Content/Section Translation and the Visual Editor as well. I’m wondering if we should also append the parameter to those links if we want to track clicks on them, the edits made on those pages, and the users who made those edits and whether they were part of the campaign, or if this is something that can be tracked independently.
  • whether they were part of the campaign?

It depends on whether you want to know if the user visit the event page because of they click a link from the campaign (eg. email/community homepage/external link);
Q: do you need to track the user source (where they came from)?

srishakatux renamed this task from Technical setup for WE 2.1.5 Week 1 to Set up event and tool links tracking for the surfacing content gaps experiment.Mar 16 2026, 8:49 PM

@hueitan Tracking edits is the priority, and it would also be helpful to capture the source.

Also, about the tool links embedded on the event page, articles linked directly to Content/Section Translation and the Visual Editor as well, do we need tracking for these links as well?

Do you think it’s doable to have these tracking links ready by the end of this week?

it would also be helpful to capture the source.

previously we have the ?banner=X to the event page URL, we will need to find other name for this source
Q for tracking team:if we use only one source name, does the referral is enough for the tracking?

articles linked directly to Content/Section Translation and the Visual Editor as well, do we need tracking for these links as well?

We will have the tag when user edit the page (through CX / VE)

Do you think it’s doable to have these tracking links ready by the end of this week?

I don't think so


Q: how many event page? if it is going to be more, we need to consider make the code available for all the event page and give a parameter to detect whether running the tracking script
Q: do we still have the account creation link in the event page?
Q: to minimize work, do you think having only the edit tag is enough? (this also the question for tracking team)

Q: how many event page? if it is going to be more, we need to consider make the code available for all the event page and give a parameter to detect whether running the tracking script

So far, we only have one event page. There’s a slight possibility that in May another community we have been working with might show interest in the pilot, but for now, it is just one.

Q: do we still have the account creation link in the event page?

No we don't have that.

Q: to minimize work, do you think having only the edit tag is enough? (this also the question for tracking team)

Analytics is no longer involved in the project. I plan to get some guidance for them soon on how to measure data. But yes, I’m all for minimizing work. If the edit tag can help us track edits and it can be done with minimal effort, we can just go with that.

I’m all for minimizing work. If the edit tag can help us track edits and it can be done with minimal effort, we can just go with that.

Let's final the "name of this edit, previously we are using fy25-we215-banner as the edit tag, which doesn't make sense now if this is not stick with the specific hypothesis

Q: how long do you want to run this tag if not within one hypothesis or quarter?
if we don't know yet, better to have the edit tag name that can explain itself.

Let's final the "name of this edit, previously we are using fy25-we215-banner as the edit tag, which doesn't make sense now if this is not stick with the specific hypothesis

Q: how long do you want to run this tag if not within one hypothesis or quarter?
if we don't know yet, better to have the edit tag name that can explain itself.

Let's keep fy26-vkd-campaign where vkd stands for vital knowledge drive. We plan to wrap up up this project before June.

It looks like the community has already started the campaign, great to see things moving forward! In our last communication, we had planned to share tracking URLs first, but given the timeline, it makes sense they kicked things off as the start date approached.

Since the campaign is already underway, the task to set up tracking URLs is no longer needed. We’ll work with the metrics we have available. I’m thinking of mapping registered users with the edits they made to the list of articles included in the onboarding material here.

@hueitan Thanks for your time and input in the discussions around setting up the tracking, apologies that we won’t be able to use it this time.

Change #1213967 abandoned by Huei Tan:

[mediawiki/extensions/WikimediaCampaignEvents@master] DNM: Setup tracking for CentralNotice banners experiment for WE2.1.5

Reason:

https://phabricator.wikimedia.org/T410362#11739915

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

MaryMunyoki lowered the priority of this task from High to Medium.Mar 26 2026, 10:17 PM