Hey FR-Tech! First, a definition: "Monthly Convert logic" is the term we use for the array of additional, Monthly Convert recurring amounts we suggest to one-time donors. E.g., if one-time gift is less than or equal to X, suggest Y as the Monthly Convert recurring amount.
Looks like its technical name is DonationInterfaceMonthlyConvertAmounts in your code, based off T324863 filed by Peter in December.
We want to start testing alternate logic to see if we can increase our average recurring gift. In the past, y'all have created some Monthly Convert variants for us (e.g. T266590), but they only concerned Monthly Convert modal content (buttons, copy, etc.); not the ask logic.
How feasible is it for y'all to provide MC variants that change the logic, but not the modal contents?
We are going to be running in-banner Monthly Convert tests imminently. Our first one is next weekend, July 28. It'd be awesome if we could run a post-payment MC test simultaneously, but it's not urgent if that timeline is too tight for y'all.
So, two questions:
- Generally, can we run post-payment Monthly Convert logic variants, with our current infrastructure?
- How much heads up do y'all need to make those tests happen?
cc @MSuijkerbuijk_WMF and @HNordeenWMF for visibility.