Eventbrite

Localist is able to connect with Eventbrite to automatically import event data from your organization’s Eventbrite account.Localist’s communication with Eventbrite is only Eventbrite -> Localist.

In this article you’ll find:

  • Eventbrite Import Data
  • How to Import an Eventbrite Feed
  • Ticket & Attendee Consolidation
  • Important Feed Import Details

Eventbrite Import Data

  1. Name
  2. Description
  3. Start Date
  4. Start Time
  5. End Time
  6. Location
  7. Address
  8. City, State & Zip
  9. Ticket URL
  10. Cost

**If a Localist field is not listed, it is because a matching field is not provided by the Eventbrite API.

Eventbrite Events with Multiple Instances

The Eventbrite ID is the number at the end of the Eventbrite listing’s URL. For an Eventbrite event with multiple instances, Eventbrite gives each instance a unique ID, so Localist imports each one a unique event. You can display Eventbrite RSVPs on Localist by including this ID in the Event Form, allowing or a more accurate attendance projection.

​Eventbrite Event

  • Instance #1 on ​Jan 1 @ 11 AM instance with unique Eventbrite ID = unique event in Localist
  • Instance #2 on Jan 2 @ 10 AM instance with unique Eventbrite ID = unique event in Localist

If you edit the time of an Eventbrite instance then that will not change the ID, so Localist will update the time as expected.

However, if you were to remove instance #1 then re-add an instance for the same date with a different time then it will change the ID and Localist will create a unique event instead of updating the already existing event in Localist.


How to Import an Eventbrite Feed

1. Navigate via Events > Feeds

2. Select +Add Feed

3. Select Eventbrite in the Feed Type drop down (this option was not displayed before this feature was configured on your platform)

4. Once you have selected Eventbrite, you will see a Connect to Eventbrite button appear. Select this button.

5. On this page, select Allow. After selecting you will be taken back to the feed’s edit page.

6. Save Changes – if this is not selected after allowing access then the feed will not import.Description Fields

  • Name: This should be used as a general description for the feed.
  • Feed URL: This is where you enter the URL to the RSS feed.
  • Skip Pending: By default,  all  events in the feed will be automatically posted. Uncheck this option to send  all  events to the pending queue for additional approval.
  • Taxonomy Overrides: These drop downs will match your platform’s filters. Selecting from the drop downs will apply the filter to  every  event in the feed.
  • ShowAdvanced Options
    • Username / Password
    • Match Instances: If selected, event  instances  that have been added to Localist, but are no longer present in the feed, will be removed. Here’s a breakdown:
      • If checked: Event A on Oct 1 is imported —> Upon next import Event A is now listed for Oct 2 and Oct 1 is no longer present in the feed —> The live event in Localist is updated from Oct 1 to Oct 2.
      • If  not  checked: Event A on Oct 1 is imported —> Upon next import Event A is now listed for Oct 2 and Oct 1 is no longer present in the feed —> The live event in Localist is updated to now have two instances – both Oct 1 and Oct 2Essentially, this functionality is only applied to  instances  of events that are still in the feed. If an entire event is remove from the feed then Localist will not make any updates or deletions and the event will stay in the last-imported state unless manually modified.

Note:Upon saving, the feed will initially import once. After the initial import, the feed will import once a day and overnight. Changes will not be reflected in Localist until the nightly import.


Ticketing & Attendee Consolidation

Ticket price will sync, but if there are multiple levels available Localist will display a range. For example:

  • Free, $15 and $25 will display Free-$25
  • $15, $25 and $35 will display $15-$35

Eventbrite ID: This is the number at the end of the Eventbrite listing’sURL. Adding this number will connect the Localist listing to the Eventbrite listing so that the RSVP number that is displayed on the Localist details page is as accurate as possible. You should still enter a ticket URL. Note:

  • The event’s attendee list must be configured for public visibility.
  • Localist displays information from Eventbrite so if a user has restricted their attendance information on the Eventbrite side, it won’t propagate over to Localist. If it’s not disabled, we will. There’s no way for the user to separately set the attendance visibility on Localist unless they’re also a Localist user.
  • Localist syncs Eventbrite attendees once a day.

IMPORTANT FEED IMPORT DETAILS

Feed Data Takes Precedent

1. Data imported by a feed into Localist will always take precedent over data that has been added or updated in the Localist event. Only the following 3 details can be locked and cut off from further updating:

  • Name
  • Description
  • Event Place

2. All other details that are brought in via a feed must be changed at the feed source. If it is changed in any way in Localist then the changes will only stick until the next feed import, at which time it will revert back to the data in the feed.

  • Exception: If a piece of data is not provided by the feed then any changes or additions in Localist will stick even after the next import. For example, if the feed only provides name/date/time/description/place then anything else, such as a tag or custom field, will remain as updated in Localist.

3. If fields in a feed match fields in Localist then the data must match exactly to what is saved in Localist. It is not possible to assign aliases or alternative spellings. For example, place names must match the place landing pages and filters must match the taxonomy on your platform in order to connect properly.

Deleting a Feed Event

1. Deleted in Localist: If an event has been imported to the calendar then deleted, it will reappear if it is sent back over through the feed. Since feed data takes precedent, if the event is present in the feed then it will be re-added to Localist.

  • Exception: If an event is rejected from the pending queue then it will not re-appear. If the event is deleted while still in the pending queue then it will be re-imported into the queue.

2. Deleted at the feed source: If an event is removed from the feed source, the event in Localist will not be removed. This is because it is impossible for Localist to determine wether the event has been deleted/cancelled or if the event is just not present in the feed. In this case you will need to delete the instance in the feed and in Localist.