The “calendar event” ticketing function in LO does not allow me to prompt attendees to login first with their Luminate credentials. By not having this login feature we feel like we are seeing duplicates in the system. They may use the same email address but then they enter Matthew instead of Matt and before you know it we have 2 records for them in Luminate. Or maybe they used their work email vs their personal email. If we prompted them to login this would alleviate this mess. When I create surveys in Luminate I have this option. We need this also for ticketed/calendar events.
Area of the Product | Content |
Org/Company Name | Roswell Park Alliance Foundation |
Correct Ken. We want people to see the event. But then before you purchase you are asked to sign in with your log in credentials (which then will pull up your Luminate profile). If you do not have a login you continue "as guest" which then creates your Luminate profile. This is available in Luminate surveys and will help create less duplicates in the database. A line such as this "If you have previously registered, please login here to prepopulate your information." THANKS!
Ah, I think I understand now. So the barrier to exploring the event and starting the purchase process are low but right before you purchase it prompts you with log in (or maybe even checkout as guest options that you see on other websites)? It's more the placement of the login request rather then the ability to restrict the event to a select group of people.
That restricts it too much in that it requires a login to even get to the page. I want people to see the event so they can get information on the event before they decide to purchase or register. Then if they do give them the option of signing in with their credentials they don't create a duplicate. Or if they don't have credentials they end up creating a constituent record. Does that make sense?
Hi you should be able to create an event and put it into a security category where only registered users can see. Then there are various ways you can direct them to that event through a login workflow. Support can answer how to questions around this or our Services team can help think through the whole workflow and do the work for you if you'd like some help.
Let me know if I misunderstood and this isn't an option for you.
Thanks,
Ken