Posted: August 23, 2015 at 6:50 am
|
Hello, esteemed EE team! I’m developing a new site for use with EE4. The site is currently on EE3 in Bluehost with a horrendous theme, and so the WP Engine on EE4 will be a welcome respite for us all. Once I get my repo set up, I’ll look into how to get EE4 in staging as EE3 runs in production. I’m just confirming that the somewhat arduous purchase process can be pretty much solved by: https://eventespresso.com/wiki/ee4-single-page-checkout-page-actions-filters/, https://eventespresso.com/features/intelligent-single-page-checkout/. I poked through support docs and QUs. If there are any “will only work if you are selling 1 ticket” restrictions/caveats that might not be immediately obvious, could you let me know or point me to those support tickets? Here is why I ask. I’m creating ecommerce funnel steps in GA so we can have historical pre/post launch data, and the purchase path was rather tedious. Each step isn’t on a different URL, but each step does represent a submit button click, and it sure feels like it from a user standpoint. Step 1: View class In EE3 I’m not seeing a way to simplify matters. I’m sure this is somehow due to how it was set up by “us” – does that sound accurate? Even with user I-D-I-O-T error, with so many steps as a default I am puzzling that a single plugin will be able to streamline all of that. Many of the options in support that have solved a few of these challenges for other users I believe/suspect are only available for EE4. Am I right here? Or am I missing something? Basically, wondering how simple I’m going to be able to make it. Would love our purchase funnel to go like this: Step 1: View event description and fill out all info, click to pay This next would be fine if above kills load times: Step 1: View event description and fill out all registrant/ticket number info Am I on the right track? Any additional links I’ve not seen? Thank you again! |
Hi Eleanor, EE4 works differently from EE3, the 5 steps you have listed above appear to be from EE3. Have you tested registrations with EE4? Its not as streamlined as you listed, but fits better than EE3. There are 2 ways to select tickets. Otherwise the user views event details and select tickets from that page. Inputs registration details. Selects payment details and inputs details (payment details for one of your payment methods can set to open by default so no need to click and select that payment method for it to show the input fields) *Directed to the thank you page.
Without knowing how your intending to setup the pricing structure for the event its hard to say, ‘Required tickets’ maybe but it depends on you want registration to work in terms of tickets. If you can provide more details on how you will be setting up the pricing structure for the event we can provide more details. *Note for offsite payment gateways such as PayPal Standard the user is directed to PayPal than back to your site. |
|
|
Hi, Tony. Thank you for the thorough response. We do not actually sell events for the most part….we sell classes (though that is basically semantics). Most classes are one-time, however, some people will purchase a class that is actually a series of classes over 8 weeks, or perhaps a week long camp. I’m still convinced EE has better features than any of the bulky class registration managers out there. The only thing EE does not handle is any sort of “package” deal, but that just isn’t important to the model right now. Here are the class types: Each class has a unique price that is set at the time of creation, though many items, such as day camps, are set at recurring for an entire yer in advance. Users typically only buy one class (or course) at a time, though they may buy multiple seats to a single class – such as signing up both of your kids at once. Users may also opt to purchase multiple classes. I’m not sure how to allow users to easily buy multiple day camps at a time, but that’s a different hurdle. So, based on that, what are your thoughts, or do you need more information? I’m looking to reduce the number of clicks to as few as possible and make this very easy, as bounce rates will continue to be high otherwise, and people will not be inspired to use the website. That’s all! Looking forward to implementing EE4. |
Hi Eleanor, Event Espresso 4 has a few tools that I can recommend you check out for handling the registration of one class, or many classes. The first one is with how you can set up tickets for accessing more than one datetime. I’ll step back and clarify these two terms. A datetime would be one time the class meets, and a ticket is like an access pass to gain entry to the classroom when it meets. So you can set up several datetimes, then you can set up a ticket that grants access to a datetime, and you can set up a ticket that grants access to many datetimes. Another option is use the Multi Event Registration add-on. This could be useful for folks that want to register for one week skill class for one child, and another class for another child. |
|
|
Sounds good, Josh. I am aware of the add ons, but this is a solid rundown that applies directly to our business, so thank you. We aren’t yet at the point where we are verifying purchase on premises or scanning tickets, however, for the online payment option this could really help. I know ultimately we’ll want to go to a scanning system, and at that time would want “packages” where a number of classes could be purchased in advanced, and each class does have a first-come-first-serve limit, while the actual date of the class doesn’t have to be secured in advance. However, we’ll cross that bridge when we come to it. Thanks for the answer! |
You’re welcome. |
|
The support post ‘Simplifying the Purchase Path’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.