Hi everyone,
We have been using eventbrite with zapier since a while and its providing great help to our business. We have been facing an issue recently; it is not happening to any of the particular event but in general zaps are not forwarding the correct data to our app sometime.
The current flow of the use case for our business is when some-one gets a ticket from eventbrite zapier forwards us the details of the individual; we have been receiving these details at an api end-point. The issue in particular is that we some time receive data in text as “info requested” for couple of fields. I am not sure about the root cause of problem as it looks like maybe zapier not able to retrieve eventbrite data correctly or forwards it correctly.
Looking for a quick fix or help on this.
Thanks
Eventbrite data being forwarded as "info requested"
Hi there
Thanks so much for reaching out here. I’m so sorry your users are being affected by this too. I’ve added you to the list of folks that are still being impacted by this issue so we can notify you the minute it’s been sorted.
Since this thread is tracking those affected by these issues with the New Attendee trigger I’d recommend creating a new post in the Community here on the topic of working with the New Order trigger.
Please do follow up in the thread here with any further findings you have regarding the issues with the New Attendee trigger here, we’d love to hear from you!
Hello!
This thread seems old, but just wanted to chime in: we are one org that is affected by this change/experiment/senseless feature update. I am only beginning to troubleshoot this now because our users patiently suffered before we realized that the zaps were failing.
- EB is allowing attendee request form to be skipped, and thus custom fields do not come in as they should.
- EB is sending in Info Requested data in the zaps, and it is not clear if this happens only if the form is skipped or even otherwise.
- Both the issues described above are rampant for “New Attendee” trigger.
In the meantime, if you use “New Order” trigger in Eventbrite, then you get two sets of data:
- User’s Name, Email: This is the profile with which a buyer has logged in
- Attendee Profile Name, Email, Questions, Answers, Number of Attendees etc.: Here, since there may be multiple attendees per order (e.g. Clay Potter (user) registers name1, name2, name3 with potentially 3 custom form fills).
- I am also curious if zap will fire multiple times for a “New Attendee” if one order with 2 or more attendees each comes through, even though the data may not come through (at present)? Or is that functionality broken too?
The issue here is that Questions is an array of strings (since there is ONE set of questions across the board for all attendees), whereas answers is an array of either one or more arrays, depending on the Number of Attendees.
We traditionally had this form parsed using Python - and now it seems like we will have to use the same, since there is NO pill available to map in a clean way. We are working to fix the code and will post additional findings.
In the meantime, I am wondering if an additional question/thread should be open to discuss working with “New Order” trigger (since it’s very different from the New Attendee trigger).
If anyone has experience using New Order trigger with custom form and one form per attendee (not one form per order), then I would appreciate any tips or possible warning for pitfalls.
I’m sorry we missed your replies here
I’ve just checked on the bug report and it found another workaround has been added that you might want to give a try:
Add a Delay For (Delay by Zapier) action after the trigger, set to delay the Zap 3 minutes or more. Then add a Find Attendee by ID (Eventbrite) search action to retrieve the attendee details and if the custom questions and attendee details have been added, they will then be available as line items. To access the
question:answer
as separate fields you’d need to use a Formatter (Line item to Text) action to convert them.
Hope that helps!
Hi,
I wanted to give you an update, though it’s not the best news.
I found a workaround to locate attendee names and emails, which helped me get through the registration process. However, I’m now facing major issues in the reporting phase. Answers for the custom questions are missing—it’s blank!
Our funder requires demographic information via Custom Questions, and its absence from the 61 “info requested” registrants is creating a significant gap in our report, potentially affecting our numbers.
Has anyone been able to locate the answers to the Custom Questions?
Thanks for your help!
~W
In exactly the same position.
It looks like Custom Questions are getting passed through the new Attendee Updated trigger, but all as one object rather than individual fields. i.e. basically useless.
Hi,
I wanted to give you an update, though it’s not the best news.
I found a workaround to locate attendee names and emails, which helped me get through the registration process. However, I’m now facing major issues in the reporting phase. Answers for the custom questions are missing—it’s blank!
Our funder requires demographic information via Custom Questions, and its absence from the 61 “info requested” registrants is creating a significant gap in our report, potentially affecting our numbers.
Has anyone been able to locate the answers to the Custom Questions?
Thanks for your help!
~W
Hello everyone!
For now, our engineers have recommended the following workarounds to capture the missing attendee details from Eventbrite:
Users can work around this issue in two ways:
- Change the configuration of their Event's Order Form to require attendee details, or use the purchaser information as interim placeholder information for the attendees. Eventbrite Support should be able to help with specific guidance on this.
- Set up a second Zap which uses the "Updated Attendee" trigger. This will ensure that they are able to capture Attendee information when it is provided by the customer, as well as capture changes to that information if the customer updates it before the event (this is also a configurable setting in Eventbrite).
Hopefully those workarounds will help to get things up and running for everyone affected in the meantime.
I would like to update and report that despite Eventbrite saying they reverted us back to the previous checkout experience, we are still getting “info requested” on data on some recent events.
We will now be certainly moving away from Eventbrite, we no longer trust or have confidence in the platform.
I appreciate this thread and everyone’s input, thank you to all of you for helping clarify what the situation is and the background. My team has experienced the same issue and we couldn’t understand how a required answer could be by-passed and not answered. I’ve logged a ticket with support as well.
Thanks, Sam, this is really helpful. Having thought I’d figured it out with various Zap flows, I’m still having problems because each time it hits an event that hasn’t had the new system implemented it just screws up the fields again for the next Zap run on the new form type!
Along with a global Eventbrite crash earlier this week when it just lost orders in the Dashboard (but taken the bookers’ money!) I am pretty much done with them.
If anyone has found a new alternative that they would recommend is working well for them (and which would work with lovely Zapier) then I’m all ears!
Sorry to hear they’re not able to opt you out of the new checkout experience
I did some digging on this side and found that a new bug report has been opened for these ongoing issues. So I’ve gone ahead and everyone here that’s running into these issues with the new checkout experience to the bug report. I can’t make any promises as to when it may be resolved by but we’ll definitely notify you all as soon as it is, and we’ll be sure to share any updates in the thread here!
In the meantime, I’d suggest exploring some of the helpful workarounds folks have shared in the thread here. I’ll share some quick links to them here in case it’s helpful:
- Use a Delay and search action to get attendee details
- Switch Eventbrite order form settings to “Ticket Buyer”
- Export Zoom registrants details for virtual events
- Make an API Request to Eventbrite’s API to get the order details
Also, I’d like to say a big thank you to everyone who’s shared their helpful insights suggestions in the thread here - it’s very much appreciated!
Hopefully these issues with the new checkout experience can be resolved soon!
As far I can tell, they did opt us out. I haven’t see any more “Info Requested” registrants come in.
Did you email contactsupport@eventbrite.com? If not, try that out, they seem to know a bit more than the typical support agent. If you did, maybe try a whole new email chain and see if you get someone different.
You can mention that at least 3 people on this forum were opted out and were told that the product team was working on a way to opt out for everyone if they wanted to.
We tried to get opted out, were initially told that it would happen, then got an email saying that they could not would not do it. Subsequent attempts to communicate have been met with firm refusal to care. Their way or the highway seems to be their current stance.
Yes, I can confirm we were also granted being opted out from the new order form behaviour today as well. We too will monitor it, as like @zap500 mentioned, it is hard to test for random order selection behaviour.
The feedback does appear to be being received and thanks to everyone who’s directly contacted them to voice concerns and issues related to this new process, I’m sure the responses being made by Eventbrite are directly because of this.
Ultimately, I think if they deliver a configurable option on the Order Form that’s basically a choice of prioritising speed i.e. get tickets as soon as possible vs data collection, this strikes the balance across event organisers. In my personal opinion the mistake was not providing a way to opt out of this, and Eventbrite not being transparent about this new process. I hope they learn from this, but it’s a certainly thanks to voices of organisers making noise around this to get the resolution we have been after, so thanks to everyone!
This fills me with hope as I’ve still not found a suitable replacement for our business to eventbrite but every day the level of dissatisfaction with the new style grows. We are losing hundreds of leads for our business and hundreds of people booking are not being provided access to the event they’ve ordered.
I’ve asked to be opted out, pray for me folks.
Yes, I can confirm we were also granted being opted out from the new order form behaviour today as well. We too will monitor it, as like @zap500 mentioned, it is hard to test for random order selection behaviour.
The feedback does appear to be being received and thanks to everyone who’s directly contacted them to voice concerns and issues related to this new process, I’m sure the responses being made by Eventbrite are directly because of this.
Ultimately, I think if they deliver a configurable option on the Order Form that’s basically a choice of prioritising speed i.e. get tickets as soon as possible vs data collection, this strikes the balance across event organisers. In my personal opinion the mistake was not providing a way to opt out of this, and Eventbrite not being transparent about this new process. I hope they learn from this, but it’s a certainly thanks to voices of organisers making noise around this to get the resolution we have been after, so thanks to everyone!
Eventbrite has apparently just opted us out of this change! We don’t have commercial support and
From the support agent:
“Yes, our product team is working on a way to opt users out of the new post-checkout experience due to the overwhelming feedback we have been receiving.
As I have already submitted your feedback, they have opted you out of this experience as of today.”
Sounds like everyone’s complaints have been working! If you want to be opted out and haven’t been yet, try following up on your case today. Or send an email to contactsupport@eventbrite.com to ask to be opted out if you haven’t already.
So far, our forms seem like they are switched back, but it’s a little hard to tell since it was random before. I’ll have to keep an eye on it and see if we see any more Info Requested coming in later.
This is brilliant, thank you so much, it worked perfectly. I’ve never delved into the API requests before, but you may have created a monster now I can see myself going down the API rabbit hole to do much more!
Add another Eventbrite step, choose API Request (Beta) as the action.
Refer to the Eventbrite API documentation: https://www.eventbrite.com/platform/api#/reference/order/retrieve-order-by-id
To get the Order information, use the link they show in the documentation and put it in the URL field in Zapier: https://www.eventbriteapi.com/v3/orders/order_id/ (replace order_id with the field from the triggering event with the order Id number). Note that the ending slash is important, you get an error without it.
You shouldn’t need any of the other fields besides URL. Zapier handles the authentication for you since you’ve already connected your Eventbrite account.
Once you test, you should see the order data and you can use it later in the Zap. The field names will start with Response Data (so Response Data First Name, Response Data Last Name, etc).
Just had a ‘fun’ few minutes reading the string of this conversation, as I suddenly noticed this ‘info requested’ field data coming through this morning.
I’ve switched some of my Zaps over to the ‘New Attendee Created’ trigger to try to solve this.
The information that we collect in the additional fields is crucial as it collects the attendee names (which is sometimes different from the Booker) and also dietary requirement and LinkedIn profiles which are key to prep before the event itself.
In relation to how the data is brought through in the ‘New Attended Created’ trigger into Zapier, has anyone found that the buyer data comes through with the attended data as well? I can’t seem to find the field that features the buyer’s details and I need to bring through both buyer and attendee info at the same time.
Any thoughts much appreciated.
The fact that it is only rolled out for orders at random (and not for all yet) indicates to me that they are still testing (regardless of what their article says). I myself have seen both behaviors (required questions before and after payment) on the same event form with the same settings without additional terms questions.
However, that’s great news that you shared from your contact with support that they are working on a way for people to opt in/out of this change. That would be a great improvement and hopefully they fast track it because of the number of complaints. I am a little concerned that they specified “ticket buyers,” since we have required questions we need on individual attendees, but hopefully they are including that and just saying ticket buyers as a shorthand. Thanks for sharing!
A couple things:
People keep calling this an “experiment” as if it’s ongoing. The experiment is already over.
As of November 2023 the decision was made to change to the new, flawed system. The blog post clearly states this, and so does their article.
We recently ran a series of experiments where we moved the order form to after payment. Through this work, we saw conversion rates nearly doubled. As a result, we’re moving all order forms including those with custom questions to after payment, with the exception of additional terms and conditions, which will still appear before payment.
More importantly, I got this response from Eventbrite support yesterday, April 18, which indicates to me that we will indeed have a universal option to switch when the custom questions are asked:
To give you transparency, the Product Improvement team is already working to give organizers an option if they want their order form for their event to be answered first by the ticket buyers before they can secure their tickets.
I’ve made a Zap to manage the data I manually import and parse from Eventbrite every few days so I can get some data in the meantime, because as slow as Eventbrite support runs it should be a few months before we see this requested change in the interface.
Update:
Eventbrite Customer Success believes that we’re being affected by a bug which is randomly taking some of our orders through the new checkout process and therefore not collecting our required fields, despite the fact that our account is marked for commercial and should be exempted.
From the dialogue I have had with Eventbrite support, this may provide some further insight into how this “experiment” is working. This is in reference to your previous post
Hi James,
Creators that have contracts with us haven't yet been included in the post-checkout order form experiment, so I wonder if that's what's going on with your friend. If the creator was included in the beginning, that was likely unintended and the team likely corrected that. For context, creators with contracts have connections to the Commercial Team from when they established their contracts.
I haven't heard of any self-sign on creators being omitted from the experiment, so I'm highly doubtful that the team will consider it, but nonetheless, I have asked the product team if there would be any room for negotiation. I'm awaiting a response from them, so as soon as I hear back, I will be in touch.
Again, I apologize for this situation, and I hope that this appeal to the team will work, but I can't guarantee it.
Thanks for your patience and cooperation.
I am not holding out any hope for having this turned off, but we will be moving away from Eventbrite, that is for certain.
Again, to be clear this experiment appears to be possible to run on any order created through the checkout, regardless of the event it is attached to. Commercial clients aren’t meant to be selected in this as per the above response, but it makes it even worse for organisers, adding further inconsistencies to the checkout experience and data collection.
Update: We are still seeing the info requested issue at random. Eventbrite management has assured us that we would be excluded from this product update and the last 100 or so registrations went smoothly with no integration data issues. However, we had a registration last night where Info Requested came through our Zapier integrations.
This morning Eventbrite Customer Success is on the case and saying they believe this may be a bug happening at random. They confirmed that we’re supposed to be excluded from the “optimized” checkout process.
We feel for all of you guys. Eventbrite is/was a bit clueless about the impact of this change. If you’re experiencing issues please let Eventbrite know. They did mess up, but contacting them helps them understand and makes it more likely that this gets resolved in a good way for everyone.
After using Eventbrite + Zapier for exactly 10 years, we’re now forced to find an alternative supplier. Eventbrite’s decision to change all users over to their “better checkout experience” has been disastrous for us. It’s shameful. If anyone knows a good replacement please do let me know.
Make sure to provide your feedback to contactsupport@eventbrite.com so they know this change is a disaster and needs pausing!
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.