Skip to main content
Best answer

Eventbrite update issues: New second registration page with custom (required) questions not getting Zapped

  • 17 January 2024
  • 3 replies
  • 353 views

(I know this question has been written before- but none of the previous solutions are working)

Ever since Eventbrite updated their platform and changed their registration page to “increase ticket sales”, custom questions at registration (in my case Title and Company) are now being asked on a secondary check out page. 

The custom questions are not being pushed through my Zap. 

  • The questions are all required
  • Ticket checkout is set to “Buyer only”

When building the zap and testing it in the build mode, it works fine. But once published and running on its own, it will only push through the zap the initial “standard” eventbrite questions on registration page 1 (Name and email). 

I have attempted to push the Zap into both Salesforce and Airtable and both have the same issue. 

According to Eventbrite there is no way to change this or revert back to the old check out page. :(    I don’t like this for all kinds of reasons- primarily being that my Zap no longer works! 

Has any discovered a workaround? Any idea if this will be fixed? My entire paid plan is to support this Zap and really need to get this resolved. Thank you for any and all help! 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

SamB
Rank
Userlevel 7
Badge +11

Hi @BVM, sorry to hear of the troubles here! 

I did some digging and found that you’re not the only one who’s been affected by this. We’ve got an existing bug report open for this issue so I’ve gone ahead and added you to it. I can’t give any sort of ETA on when you can expect this to be fixed by. But adding you will help to increase it’s priority and allow us to notify you by email the moment it’s sorted.

In the meantime, do you get email notifications from Eventbrite when someone registers?

If yes, and assuming those emails contain all the necessary registrant details, then as a workaround perhaps you could trigger a Zap from those emails instead. For the trigger you’d need to use an email parsing app like Zapier’s Email Parser. If you’ve not worked with it before I’d recommend checking out out Trigger Zaps from new parsed emails guide for details on how to set it up.

Hope that helps. Do let us know whether you’re able to give that workaround a try and get it working - happy to help if you run into any issues on that! 🙂

S

Are there any updates? Please add me to the issue tracker for this.

SamB
Rank
Userlevel 7
Badge +11

Hi @samm 👋

Ah, it looks like we had two duplicate bug reports open for this issue. The bug report relating to this thread has been closed and both you and @BVM have been added to the remaining bug report. That bug report is related to another Community thread:


There’s a few different workarounds that have been shared there which I’ll surface here in case it’s useful:

  1. 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.
  2. 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).
  3. 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.

 

We can’t give any sort of timeline on when it will be resolved but you’ll both be notified by email as soon as it is.

As we’ve already got one topic relating to the bug report I’m going to close this one out. For anyone that comes across this post and wants to be added to the bug report please reach out on the main topic here and we’ll take care of it! 🙂

Terms & Conditions