Page MenuHomePhabricator

Japan Form Variations for Testing for Q3
Closed, ResolvedPublic4 Estimated Story Points

Description

Hi all,

Camille gathered all input about the Japan form improvements from various sources (Seilo, Yukari & ichi, and the firm David hired) and organized it so the Online team could prioritize what to test. We have her to thank for this!

The team would like to create 2 Japan payments wiki variants so we can test the performance. Here is a visual accompaniment to this task, in case it's easier to see it this way.

On the Japanese/Japan payments wiki:

VERSION 1A

#1 Donation amount:

Change
金額を選ぶ
to
寄付する金額

#2 Billing information:
Change
請求情報
to
お支払情報

#3 In the empty name fields, please add (in a greyed-out style) the following (these are the equivalent of "John Doe" in Japanese):
鈴木 (last name) 太郎 (first name)

#4 Expiration date field.

Change
MM/YY
to
月月 / 年年

VERSION 2

Repeat #1, #2, #4.

ALSO:

Under the existing name fields, add another set of text input fields:
フリガナ

セイメイ

If this is possible, we'd want to update the existing name fields too:
Change
姓(苗字)
to
氏名

And add to the text input fields (in a greyed-out style) :
姓 (surname) 名 (name)

Version 2 is visualized here.

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Dwisehaupt set the point value for this task to 4.Nov 14 2022, 9:28 PM

So for version 2, the supplemental inputs are the 'Furigana' / phonetic first and last names? And I guess you would want some new fields in CiviCRM to store those?

This visualization might spell it out more easily.

As for whether we need that supplemental information stored in Civi, I'm going to ping @krobinson, @CDenes_WMF perhaps with Seilo's input? I can't find Seilo's Phab name to ping him too! :) Would we ever need the Furigana information of our Japan donors?

Hi @TSkaff somehow I'm only seeing Variation 1 at that link. It sounds like version / variation 2 is adding another set of inputs?

Under the existing name fields, add another set of text input fields:
フリガナ

セイメイ

Wouldn't it be a waste of donors' time to collect extra fields and not store them in Civi?

Sorry, now GDocs is loading all the slides for me, as well as the note under version 2 with the rationale for the extra fields even if they aren't saved to Civi:

Requesting to provide the reading (furigana) dictates that the customers must provide their names in kanji style (hiragana and katakana do not need reading help as there is just one way to pronouce them).

So we add the extra fields specifically to prompt the donors to use Kanji in the existing fields (which is what we actually want to collect).

Thanks Elliott! Yes the slides are much easier to digest IMO :) (wikilove to Thea for creating them).
We could either *not* store the Furigana at all; or Seilo suggested we could save it in Civi's "Nickname" field:

"we could keep them under "Nickname" in Civi, if possible This is where I have been keeping donors names when they reach us in JPN at first and later in ENG for an example."

@Ejegg Hi Elliott, just checking in: Do these variants seem reasonable to test in Q3? Any blockers you spot, or do we need to simplify anything?

We also respect that English banners go up tomorrow & all eyes will be on that. :)

Hi @TSkaff, most of that sounds reasonable. The expiration date fields are not under our direct control (they are controlled by an Adyen script and are technically teeny little iframes hosted on Adyen's site, to maintain our PCI compliance) so switching them to be dropdowns may not be possible. I think we can tell the Adyen script to use custom text for their labels instead of MM/YY though.

Hi @Ejegg just a heads up that Thea, Evelyn, and I chatted and we made a couple edits to the proposed variants, which are 2. You can find them in the Slides

My follow up question is if we will be able to run these two variants against some sort of control in order to determine lift?

Hi @Ejegg just a friendly bump on my last message. Please let me know.

I also wanted to share that the banner pretest could be scheduled around mid-Feburary. Could you please confirm that the payment forms would be ready to go around then? Thank you!

Hi @CDenes_WMF sorry I didn't see the question before. Yes, for the parts of the form that we control (i.e. not the input type of the expiration date) we would implement the changes using our 'variant' logic, which can render the form differently based on the 'variant' url parameter. That will let us show different forms to different donors during a single test.

XenoRyet moved this task from Later to Current Sprint on the Fundraising-Backlog board.
XenoRyet subscribed.

Change 879658 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] WIP first variant for Japan tests

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

Hi @TSkaff I am starting to implement these now. I've got a working version of variant 1A, with one catch: The expiration date placeholder is outside of the control of our usual variant mechanism because it's a special field in a tiny iframe hosted by Adyen.

I CAN update the Japanese expiration date placeholder across the board to "月月/年年" but it would take some acrobatics to use that only in a variant.

Would it be acceptable to change that universally and make the other form changes subject to the variant code?

Change 879665 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] WIP update Japanese Adyen expiration date placeholder

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

@EMartin @CDenes_WMF @krobinson Per Elliott's comments above--is this ok with you that we update:

MM/YY to 月月/年年

everywhere & we keep an eye on it? Seems hard to separate out for test. I'd cc Seilo but why can't I find him in Phab :)

Change 879689 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] Japan form variant #2

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

Dang! I really wanted to see how that would affect performance. I suspect it's one of the biggest variables (since currently the placeholder is in English). But if that's easier, then I'm fine with it

@CDenes_WMF @Ejegg From talking with Seilo, he advises that the local format is month/Year for credit cards online. I think this format should be ok and I will definitely be watching it.

Dang! I really wanted to see how that would affect performance. I suspect it's one of the biggest variables (since currently the placeholder is in English). But if that's easier, then I'm fine with it

I came up with something that might work to make that switch part of the variants. I'll try it out and see if it works.

Change 879665 abandoned by Ejegg:

[mediawiki/extensions/DonationInterface@master] WIP update Japanese Adyen expiration date placeholder

Reason:

squashed into JA variant 01A

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

Change 882694 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] WIP try loading adyen variants with mw.loader.using

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

Change 879658 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] First variant for Japan tests

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

Change 879689 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Japan form variant #2

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

From the commit message on the patch for the 2nd variant:

TODO: actually submit and pass through the _phonetic versions of

the first and last name fields.

Just a quick thought: is there any danger that donors would fill out only the phonetic versions and not the standard fields? in that case @Ejegg, if we don't do that follow-up, would we risk not getting any name information for the donow?

@AndyRussG the existing name fields are still required, so donors shouldn't be able to submit the form without filling them in.

Change 882694 abandoned by Ejegg:

[mediawiki/extensions/DonationInterface@master] WIP try loading adyen variants with mw.loader.using

Reason:

going with the copypasted RL module config

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

OK @TSkaff, these are deployed. Note that the phonetic fields are currently just cosmetic - that is, they don't get saved to anywhere in Civi.

Link for variant 1: https://payments.wikimedia.org/index.php?title=Special:AdyenCheckoutGateway&appeal=JimmyQuote&payment_method=cc&recurring=0&language=ja&uselang=ja&country=JP&currency=JPY&amount=150&variant=ja_01A&utm_source=internal_test
Link for variant 2: https://payments.wikimedia.org/index.php?title=Special:AdyenCheckoutGateway&appeal=JimmyQuote&payment_method=cc&recurring=0&language=ja&uselang=ja&country=JP&currency=JPY&amount=150&variant=ja_02&utm_source=internal_test

Remember that variant is a 'sticky' parameter, so if you load a form with no variant parameter it will remember the last variant you used. To go back to the normal form you can clear you cookies for payments.wikimedia.org or change the URL to an invalid variant code like jp_xx

Wo-hoo thank you @Ejegg!!

I'll pass these off to the Online team for QA & review to ensure no other edits are needed.

Hi again @Ejegg, I think I misunderstood--so we can't run real donations through these yet?
Or can we, but I'm getting an error message when I try (and I tried incognito too). I get one of those: "Error reference: 157742741.1" or "An error occurred while processing your request."

Nevermind, I got it. I added a real banner for the utm_source @Ejegg

Pulling back into 'Doing' because it sounds like people really do want to get the fields from variant 2 into CiviCRM.

Change 883673 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] Send phonetic name fields through on queue messages

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

Thank you @Ejegg ! Exciting stuff. Yukari, Seilo, and Ichi all reviewed. Just one edit they requested: changing the text in the donate button from "寄付" to "この内容で寄付する".

Hi @CDenes_WMF so that donate button text change is universal across all JA forms, or just for these two Adyen variants?

Change 885044 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Add new fields for phonetic first/last names

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

@Ejegg let's keep for just these variants, so we can measure any change in KPI

Change 885044 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add new fields for phonetic first/last names

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

Change 883673 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Send phonetic name fields through on queue messages

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

Change 885462 had a related patch set uploaded (by Amire80; author: Amire80):

[mediawiki/extensions/DonationInterface@master] Fix comma to full stop in a message

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

Change 885462 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Fix comma to full stop in a message

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

Change 885918 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] Japan variants also change donate text

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

Change 885918 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Japan variants also change donate text

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

Change 886208 had a related patch set uploaded (by AndyRussG; author: AndyRussG):

[wikimedia/fundraising/crm@master] Consume phonetic names for Japan variant

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

@Ejegg To clarify something that came up today in office hours:

Is the proposed donate button text change (from "寄付" to "この内容で寄付する") possible in just the variants or would it need to be visible in the control too? cc @HNordeenWMF

Sure, I think we were only leaving this open in case people wanted us to finish the V2 work - importing the phonetic names into Civi. If they still care about that we can open a new ticket.