Hey @Cstone, thanks for working on this; we are definitely observing a year over year drop in impression counts in our Brazil campaign. I don't *think* that has much to do directly with this status code issue, it'd just be great to rule out that this status code issue is inadvertently blocking valid banners.

Thanks very much for this investigation, @Urbanecm_WMF, and for the detailed instructions! I've tested the production desktop link (https://en.wikipedia.org/wiki/Special:CreateAccount?campaign=typage-6C-en-2023) and can confirm that I got the 'donor-branded' account creation page, as expected; and was able to create an account without any disruptions.

Hi @MatthewVernon, this is approved from my side, thanks much!

Hi @KStoller-WMF, thanks much for your help! I'll be project managing these last pieces but shoutout to @HNordeenWMF for her guidance :)

Hi @Melos, thanks for reporting this. I work on the Foundation's online fundraising team.

Thank you so much @AnnWF + @AKanji-WMF and all for the work! This is great.

Hi @JTannerWMF and teammates, I just updated the task description with finalized dates, copy and donate URL. Thank you for making this happen, very neat to be trying our first iOS app fundraising experiment in India.

Hi @JTannerWMF and colleagues, we've updated the task description with confirmed dates later this month, as well as finalized copy and updated donate URLs.

Yes, thank you!

Hi, could I (username spatton) please get access to the sql_lab role, too? Thanks!

+1, thank you @Pcoombe for holding down the banner fort as only you can.

Thanks @EMartin, the pre-test for this has been scheduled in asana, running @ 25% traffic from 10 UTC on June 13 - 10 UTC on June 14.

Hi @AKanji-WMF! (rerouting this to Anil to triage)

@AKanji-WMF, @Ejegg : yes, I would still like to test V2; is it fully functional? My last understanding was that it would take extra technical work to complete, but maybe I missed that it's already done.

+1, as a CentralNotice admin this makes sense and would be a useful administrative interface element. When creating a new campaign, important features like impression limiting (which significantly impacts user experience for people served banners) are by default hidden inside a toggle box in the Extra campaign features section; it is reasonable to assume some CentralNotice admins might miss the option or fail to configure it appropriately.

@SNowick_WMF, thank you so much. This is great and useful, I have one more related request and then this can be resolved > I really appreciate your time and support on this.

Thanks @Seddon, @JTannerWMF and @SNowick_WMF > some life events happened and this fell down my priorities. Picking it back up!

+1, I do very rarely look at archived campaigns but I'd be a big fan of this change for the improved interface responsiveness, and even responsiveness of the archive when we want to access it.

+1, the level of trust is there and I've never used this feature / heard of it being used.

My javascript isn't great so someone else should review this but in case it's helpful: I saw this task, investigated a little and can replicate click issues for this banner in any browser I try (chrome, firefox, safari). I think it's due to the onclick event that hides the banner happening on the cbnnr-close-icon element, rather than its container; you can't actually click the blue circular padding on the close icon, so you have to be right on top of the X for the click to register.

Noting that I've updated my original task with new markup for shorter messages in each country.

Noting that I've updated my original task with new markup for shorter messages in each country.

Hi @Jdlrobson I'll try to look into this but want to quickly state that this isn't a fundraising banner; I think someone is reusing some of our banner code, where the frb naming convention shows up.

Declined bc this pertained to a single banner variant, not control.

Declined as an edge case.

Resolving this and moving to our Asana dev board.

Thanks for that info @EMartin!

I know @EMartin, @TSkaff, @greg, @jgleeson and others are looking at this super actively; I am triaging it as Unbreak Now because it is significantly impacting our ability to send our emails and convert donors over in Online Fundraising.

I think this is a great call, @EMartin; several of us on the front-end testing side feel that our conversion rate from banners (e.g. donations on payments wiki over visits to payments wiki) is lower than we'd expect. The PAN field is an obvious source of friction. TY for making this request!

Hi, following up with my public key as requested:

Hi @Sharvaniharan! TY so much for your work on this. I just realized that there's a typo (I think) in the screenshot proof you posted above: there should be a non-breaking space in between the rupee symbol (₹) and the numeric amount (75).

Hi @Sharvaniharan, thanks for your response! You caused me to realize that I left a little stray text in my original task description when I updated it; sorry about that. The copy in the description is final and ready to use.

Hi @JTannerWMF and @MattCleinman, I've updated the task description to include links + copy, and moved most of my original message into a background section. I'll check in w/ y'all next week. Thanks and really looking forward to this!

Hey @DStrine, the prototype's footer has been updated to match the TY page and remove the broken search bar that had appeared below it.

@scervantes is working on it and we'll come back here with questions or concepts.