I'd be curious to see if "name your price as long as it's not $0" options are any more successful—maybe entering payment details is too annoying for users, so given the $0 option, they'll take the least time consuming path.
Any thoughts on the boundaries of A/B testing pricing? It can be construed as very sketchy if you show one set of visitors a certain price and some other another price point.
But not if your test is a control of the current setup of no anchor point and your test condition to be "support us by donating $x" where x is say $10. This isn't as sketchy because its not an actual price since its not mandatory and is still only a donation. You're not changing the price, you're changing the donation verbiage.
Comments
I'd be curious to see if "name your price as long as it's not $0" options are any more successful—maybe entering payment details is too annoying for users, so given the $0 option, they'll take the least time consuming path.
Any thoughts on the boundaries of A/B testing pricing? It can be construed as very sketchy if you show one set of visitors a certain price and some other another price point.
But not if your test is a control of the current setup of no anchor point and your test condition to be "support us by donating $x" where x is say $10. This isn't as sketchy because its not an actual price since its not mandatory and is still only a donation. You're not changing the price, you're changing the donation verbiage.