How do I fix a blank screen after connecting to Eventbrite?
We know how frustrating it is when you click "Connect to Eventbrite," approve the connection, and end up staring at a blank screen. This happens when something goes wrong during the handoff between Eventbrite and Salesforce. There are a few common causes, and we'll walk through each one below.
The Solution
1. Your Eventbrite account doesn't have an organization
This is the most common cause. If your Eventbrite account was only ever used to register for events as an attendee, it won't have an organization attached to it. Our integration needs at least one Eventbrite organization to complete the connection.
To check, log in to Eventbrite and visit your Organizations page. If nothing is listed, you'll need to create an organization by setting up at least one event (even a draft event will do). Once an organization exists, return to Salesforce and try the connection again.
2. Browser cache or cookies are interfering
Sometimes cached sessions from a previous Eventbrite or Salesforce login can interfere with the OAuth redirect.
To fix this, open an incognito or private browser window, log in to your Salesforce org, log in to Eventbrite in a separate tab if needed, navigate to the Eventbrite Settings tab in Salesforce, and click "Connect to Eventbrite" to complete the authentication. Using incognito mode gives you a clean session without any cached data getting in the way.
3. You're not using your custom My Domain URL
Make sure you're accessing Salesforce through your organization's custom My Domain URL, not the standard login.salesforce.com. The OAuth redirect needs a custom Salesforce domain to work properly. You can find your My Domain in Setup by searching for "My Domain."
4. Single Sign-On (SSO) conflicts
If you logged into Eventbrite using Apple SSO or another single sign-on provider, try creating a standard Eventbrite account with a regular email and password instead. Some SSO setups can cause redirect issues during the authentication process.
5. Test in a sandbox
If none of the above resolves the issue, try connecting in a Salesforce sandbox to determine whether the problem is specific to your production org.
