Managing your event across ticketing platforms

The Platform Integrations tab: see where your event is connected (Eventbrite, Fienta, Universe, WordPress), update, sync, unlink, or publish it to another platform.

Check the live listing Create and update work for Eventbrite, Fienta, Universe and WordPress. After you push, open the listing on that platform and confirm the date, description and tickets before you promote the show.

A Gigspot event can be connected to the same event on other ticketing platforms. The Platform Integrations tab on the event's Manage page shows every connection and lets you keep them up to date.

The connections view

Your event sits in the middle, and every platform it is connected to is drawn as a line out to that platform's listing. Each connection shows:

  • the platform's name and icon;
  • a status label (see below);
  • the ticket price or price range, where we know it;
  • a link to open the live listing on that platform.
Origin The connection marked ★ Origin is where the event originally came into Gigspot (for example, the Eventbrite event you imported).

Before you start

  1. Connect an account Add and enable a platform integration in User Settings. See connecting your platforms.
  2. Open the event Go to the event's Manage page (you must be able to edit the event) and open the Platform Integrations tab.

What you can do with a connection

  • Update → — push your latest Gigspot changes (title, description, dates, image and other supported fields) to that platform's listing. A connection that has not been created on the platform yet offers Export → instead.
  • ← Sync — refresh the connection's listing details (price and the other fields stored on the link) from the platform. Gigspot asks Refresh listing details from …? before it runs. Sync does not rewrite the Gigspot event's title, description or dates. Edit those here, or re-import, for a full refresh.
  • View on … — opens the live listing in a new tab.
  • Unlink — removes the connection in Gigspot only. The event on the external platform is left as it is. You can connect again later.
  • Edit — opens the link editor. Only the lead producer team can change Destination URL, Sells tickets, or the Ticket price, Tax and Fees. Leave an amount blank to keep the platform's value. Total appears when ticket, tax and fees are all known.

Connecting to another platform

Use + Add platform and Export to … to create a listing on a platform you have connected but not linked yet. Add the account in User Settings first and it will appear as an option.

Connection statuses

  • Imported — the event came from this platform.
  • Exported — you published this event to the platform from Gigspot.
  • Imported & exported — both of the above.
  • Linked — connected, without that import or export mark.

Multiple accounts on one platform

If you have more than one account connected for the same platform, Gigspot asks which one to use before it publishes or syncs. After you choose, the action runs against that account only.

Supported platforms

  • Eventbrite — create and update events, including the full event description.
  • Fienta — create and update events.
  • Universe — create and update listings (description, venue, dates, and a General Admission ticket). A start time, venue address and map coordinates are required. Cover images are not uploaded.
  • WordPress (The Events Calendar) — create and update events on a connected site.

Known limitations

  • ← Sync refreshes the link, not the event. It updates the stored listing details. It does not pull title, description and dates back onto the Gigspot event.
  • Not every field maps. Lineup, performer spots and internal Gigspot settings may not transfer either way.
  • Check the live listing. After you push changes, open the listing on the platform and confirm dates, description and ticket settings.
Import is still the preferred way in If the event already exists on Eventbrite, Fienta or Universe, importing it remains the most reliable way to get a complete copy into Gigspot. Use + Add platform when you built the event here first.