Event Feeds

Feeds are a way to automatically pull event content from various sources into Localist for centralized management through standardized feed exports. This virtually eliminates duplicate entry, as any events entered in other systems will appear in Localist with no additional work.

In this article you’ll find:

  • How to Add an Event Feed
  • Important Feed Import Details

How to Add an Event Feed

1. In your admin dashboard, navigate to Events > Feeds

2. Select +Add Feed

3. Description Fields

  • Feed Type:  Your options are CSV/ICS/RSS or Eventbrite
  • Name:  This should be used as a general description for the feed. See “Men’s Ice Hockey” above.
  • Feed URL:  This is where you enter the URL to the iCal or 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.
  • 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 2. Essentially, 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.
  • Don’t Update Filters:  If checked, Content Overrides will only be applied upon the event’s first import. This means that you can apply a general override to the entire feed then apply specific filters on an individual basis without the Content Override replacing the specific filters after the next import.
  • Content 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.
    • Note: If you apply a content override then you cannot apply more of the same filter type on an individual basis after import as they will be removed after the next import.
  • Group:  You can choose to assign a group to the events in the feed.
    • Username / Password
  • Photo:  All events in the feed will be assigned this photo.
    • Photo Fallback for Feeds: 

RELATED ARTICLE:  Photo Fallback Chain

  • Authentication:  If your feed requires an authenticated user to access it, enter the Username and Password in these fields.

Note:  Past events are not imported.

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

Feed Statuses:  After each import, the feed overview page will note the following details:

  • Status (complete, etc.)
  • Date and time of import
  • Number of events imported
  • Number of pending events
  • Number of rejected events

If an event has been rejected, there will be a link to see the exact errors per event.


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 your platform’s existing classification scheme 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.