|
Matthew Farrand
|
August 2, 2014 at 9:05 pm
I’m running WordPress 3.9.1 and EE 4.2.0.reg. An example of my reg form can be seen here: http://www.maryvillevineyard.com/events/next-step-dinner-2/
Since upgrading to EE4, my analytics show more than 50% of registrations for free events are abandoned when users see “Attendee information submitted successfully.” I’ve substantiated this w/ user feedback – we’ve had lots of conversations w/ people who thought they were registered, but it “somehow didn’t work.”
I saw this previous post: https://eventespresso.com/topic/ee4-how-to-completely-suppress-proceed-to-payment-for-a-free-event/
The “solution” that closed that topic will not work for me, since we have both free and paid events.
It is simply not acceptable to require registrants to complete a “payment options” step for a free event. I understand there’s probably 2,001 reasons why it was developed this way, but it’s just not good UX. We need a real solution that fixes this in the core.
Until then, is there a bandaid I can use to help reduce abandon registrations?
Thanks for all you guys do!
|
|
Matthew Farrand
|
August 2, 2014 at 9:07 pm
To clarify, the long-term solution I’m interested in would completely eliminate all user clicks for “payment options” when the ticket is FREE.
|
|
Dean
|
August 4, 2014 at 5:52 am
Hi Matthew,
Thanks for the feedback, it is really helpful to get real life UX cases like this.
This is something that has come up before and we have an outstanding ticket to look into a way to resolve it, most likely by changing the wording for free events.
Right now there is no band aid fix for it, though you could rename the Proceed to Payment Options button to something more generic like Finalize the registration.
https://eventespresso.com/wiki/customize-checkout-registration-button-text/
|
|
Josh
|
February 3, 2015 at 3:18 pm
Hi Matthew,
A little update on this: Event Espresso 4.6’s registration removes the payment step if the selected tickets are free. Here’s a screenshot that shows how it looks like now along with the new reCAPTCHA:
|
