Zap won't pull optional questions from Eventbrite?

Hey there, @7theNeven!

I wanted to pop back in and mention I can see you were able to open a ticket with my teammates in support, which is amazing. They did have a clarifying question that was sent on the 15th:

...could you let me know which fields seem to be missing in the Zap? If you could share screenshots of examples of this, that would be helpful as well!

We’d recommend continuing to troubleshoot with my friends in support but please keep us in the loop with any solutions ya’ll are able to find! 🙂

Hi @7theNeven, 

We experienced this issue fairly recently, as well. Not sure when the change occurred but we no longer capture the optional questions from the trigger, only the required ones. 

If I understand your solution correctly, in the event setup on the Order Form options, to have optional and required questions answered at the same time, we must set “Collect information from” to “Buyer only”, not “Each attendee”?

Thanks for your help!

This is actually bigger problem than what’s being reported here, and the context needs clarification. Edit: I solved it by the end.

Eventbrite shows required questions in order to complete registration on both desktop and mobile browsers, then it shows not required questions after registration, which means a huge drop-off in response rate.

Eventbrite actually does show all questions in advance of registration when transacting via their mobile app, but that’s a minority of users.

The problem we’re seeing, since our most important question is not required (it's not applicable to too many of our attendees so it can’t be required, or, if we make it required, too many responses will be garbage), is that we are only getting custom question data sent to Zaps for only about 10% of the responses.

I do not know if that’s because the only ones we’re seeing are purchased via mobile app or if it’s just intermittently working, but I’d bet it’s the former.

We do have our events set to collect custom questions from Each Attendee. I’ll try changing it but I doubt that’s the issue here, since most our ticket sales are single tickets and that would already be only the buyer entering data.

I know there’s data we’re missing from analyzing event reports and seeing all the custom question responses not collected by Zaps.

More than “collect from buyer vs each attendee setting” being the culprit, it makes more sense that the data is sending after the initial registration, so the custom question data doesn’t have a chance to be captured when the trigger activates. Even asking the Zap to delay 5 minutes doesn’t help because once the trigger data goes, it doesn’t revisit it - that attendee is no longer classified as “new” when the optional custom question data arrives.

So - and I’m solving my own problem here by writing this all out, lol - the solution is simply to make the custom questions required when you want their data in Zaps.

I could just make the first of the multi-selects in my question be a “nothing now” option for everyone to which this isn’t applicable. It will cause a drop in responses from those who just want to check it to move on vs read the choices but hey, better than me wrestling with data reports and manual importing, and the trade-off of having it appear up front vs optional after registration is probably better in the end anyway.

Thanks for coming to my TED Talk! 🤣

Hi @ken.a

May have missed a response to this issue, is there a fix planned from Zapier to correctly transfer non-required questions from Eventbrite to other apps? We are using ON24 and this is a challenge for us as half of our Eventbrite questions are not required.

Thanks for your assistance.

Hey @luckylou, 

A sort-of-but-not-great workaround for capturing the optional questions we came up with was a second zap that triggers when a registrant is checked in at our event. If they answered the optionals after registration, their answers are still stored on their profile so we were able to grab the data then. 

Again, this is less than ideal as it requires 2 interactions, making sure to check them in at the event(we use the EB app on tablets/phones), and maintaining 2 zaps just to capture what was already given. This of course doesn’t work if they don’t show up or someone neglects to check them in.

@ken.a says a fix might be coming(thanks!) but until then this is what we’ve got. Hope that helps a little.

@ken.a Is there any update on when this might be available? This seems to be a very important missing feature. Without this, the integration is sort of pointless as I will have to manually go in and update values.