Hey @apaskulin and @KBach. Thank you so much for your help getting the announcement banner up! I noticed that the “Sign up to participate” button isn't working on production (the behavior was fine when we tested the patch locally!). The browser console indicates that we need to set the 'allow-popups' permission for the element:

In T432285#12125949, @apaskulin wrote:

Would you be willing to open a patch for this? That would be the fastest path forward. In the meantime, I'll think about some copy suggestions.

In T432285#12125892, @apaskulin wrote:

Thanks for opening this! What is your target date for having this live?

Hey @Pginer-WMF and @RHo. Sorry if this should be an AC instead, but I was wondering if you could please bring to Wikimania some flyers to recruit technical volunteers for future research projects 🙏🏻 I'm attaching a PDF version of the flier (4/page). Here's a link to the Figma file in case it's useful. Thank you so much!

This task should have been closed together with its corresponding hypothesis (WE5.2.1b). Apologies for the extremely late update.

This task should have been closed together with its corresponding hypothesis (WE5.2.1b). Apologies for the extremely late update.

This task should have been closed together with its corresponding hypothesis (WE5.2.1b). Apologies for the extremely late update.

Status update: A Traffic referral section with recommendations for external reusers to improve accuracy of web traffic provenance was included in the Technical Implementation page of the public Wikimedia Attribution Framework site. The Participation CTA implementation recommendations were adjusted too for consistency with the latest recommendations (link meta tag removal v. app-level header specification). Review comments and amendments are welcome.

Status update: A User-Agent policy and rate limits section was included in the Technical Implementation page of the public Wikimedia Attribution Framework site. Review comments and amendments are welcome.

Status update: A first draft of the attribution recommendations for Media and publications (with assets and a link to the configurator design in Figma) is now ready for review.

Status update: The Attribution framework site was added to Wikimedia's Matomo instance. Analytics data is starting to flow in and is reflected in the dedicated dashboard. We also set up an event to track interactions with the "Configure" button in the various scenario configurators. We're testing the setup right now to confirm its accuracy and proper operation.

Update: A draft of this section was added to our internal document. Tech review pending before publishing.

Status update: We validated, with help from the Data platform team, that the Attribution Framework site can be added to Wikimedia's Matomo instance. All stake holders should have access to the instance with their LDAP accounts (see Data Platform/Systems/Matomo > Access). We're waiting to receive the JS tracking code that we'll need to add to our project to enable tha analytics data flow.

In T425576#11922017, @pmiazga wrote:

@Sarai-WMF @HCoplin-WMF I added also wprov param info to schema documentation:

Does this meet your expectations regarding

We transparently communicate the presence of these parameters to users of the Attribution API

@Pginer-WMF @RHo. I moved this task to the In progress column because the Games and rich media experiences configurator needs a few fixes. Specifically, we need to:

• The contents of section "Retrieving attribution metadata through Wikimedia APIs" in the "Technical implementation" page are almost ready
• The new page and its draft contents were committed to a new branch in the Wikimedia-Attribution GitLab repo
• What's missing: The "Signal support overview" section on this page revealed missing data source entries for the Enterprise, Action and MediaWiki REST APIs in some signal pages. We're working on documenting the missing information to ensure consistency across the site.
• Regarding the "Traffic referral" section: This is WIP and under review by engineers/data scientists
• Recent feedback made us realize that we might need to include a section with information about Wikimedia's User Agent policy and Rate limits to make these visible and accessible for reusers.

In T425576#11899168, @HCoplin-WMF wrote:

Notes from estimation:

• We can use linker tool/library to append the right values to the title link
• Values are assumed to be directly concatenated to the hardcoded CTAs
• Add a test that confirms presence of wprov

In T425576#11898628, @pmiazga wrote:

After a deeper thought, I don't think we need different wprov values for each link -> as the we will know which link was clicked by the link ( URL ) itself. Therefore we may be totally good with just two af[s|c]w1 which would be translated to

afsw1 -> Attribution Framework, Source, Web, ver 1
afcw1 -> Attribution Framewor, Calls to Action, Web, ver 1

Thanks @pmiazga. @RHo and I agree to follow the predetermined format more closely. Following your lead, this would leave us with:

Status update:

Hey @HCoplin-WMF and @RHo! I decided to document this recommendation to improve the discoverability of the Wikimedia Attribution Framework and the Attribution API by potentially exposing them to AI agents when they access wiki pages. This idea came out of an exchange with @SGautam_WMF. I'm unsure of its technical feasibility, and whether the idea fits our product vision. Your thoughts and feedback would be very much appreciated. Thank you!

Hey @Khantstop! We'd really appreciate your help crafting this recommendation, which we're hoping to include as a best implementation practice for Participation CTAs in the Attribution Framework. Please find an initial draft of the guidance in this task's description. It's also included in our internal draft document to facilitate feedback sharing. Please don't hesitate to add your suggestions/comments directly there. Thank you!