Open Forum

Hi, I am curious if anyone knows the best way to build registration that is essentially two events but one registration site, if attendees want to go to event and the other event they can. For the first event we usually have two admission items/registration rates and if they want to add the second half of the event they would get a discounted rate for the second event.  For the second event we usually have only one admission item/registration rate and if they want to attend the first event they would get a discount to attend the first half.  The registration types/contact types are the same for both events, I just want it to be clear as to what they are choosing and if I should use registration paths/sessions/session groups or if anyone has experience doing something like this?

Hi, I am curious if anyone knows the best way to build registration that is essentially two events but one registration site, if attendees want to go to event and the other event they can. For the first event we usually have two admission items/registration rates and if they want to add the second half of the event they would get a discounted rate for the second event.  For the second event we usually have only one admission item/registration rate and if they want to attend the first event they would get a discount to attend the first half.  The registration types/contact types are the same for both events, I just want it to be clear as to what they are choosing and if I should use registration paths/sessions/session groups or if anyone has experience doing something like this?

Out of curiosity, are the two events close together in timing?  So one event one week and the other event the following week, or something like that?  I have seen the fallout of a single event being created for two different events (the same event, one in person and one virtual) that happened several months apart, and the backend management of the event got very convoluted.  By the time we got to the end of the second event occurrence, we decided it would have been better to keep the events completely separate in order to better control and manage emails, reports, etc.  

I like Lynn's solution of using multiple admission items if your events are going to be back to back.  If the events are going to be completely separate, I wonder if you'd be able to accomplish what you're trying to do with discount codes.  If you register for Event A, at the end of the registration process, you can include a link to register for Event B with a discount code that would give half off the registration fee.  And vice versa, at the end of Event B, link back to Event A with a discount code.

I'd love to hear how you end up executing your event!

Hi, I am curious if anyone knows the best way to build registration that is essentially two events but one registration site, if attendees want to go to event and the other event they can. For the first event we usually have two admission items/registration rates and if they want to add the second half of the event they would get a discounted rate for the second event.  For the second event we usually have only one admission item/registration rate and if they want to attend the first event they would get a discount to attend the first half.  The registration types/contact types are the same for both events, I just want it to be clear as to what they are choosing and if I should use registration paths/sessions/session groups or if anyone has experience doing something like this?