Overview

FanThreeSixty offers clients the opportunity to integrate data from any ticketing vendor into the Fan Data Platform using a variety of data integration pipelines, as outlined below.

FlexPath Ticketing

Data Availability

To utilize the vendor-agnostic ticketing integration pipeline, clients are responsible for ensuring data is made available to FanThreesixty via secure means.

Options include:

• Automated file drops to Amazon Simple Storage Service (S3)

• Secure File Transfer Protocol (SFTP)^§

• REST API^§

• Webhook^§

S3 file drops are the fastest and lowest-cost option if your organization can support this capability. FanThreeSixty will provide credentials and an S3 file repository link to access an S3 location specific to your organization and file type (e.g. ticketing). You may publish files to this repository via automated service (manual file drops are not supported).

If SFTP is selected, FanThreeSixty will provide you with connection details, including url, port, and home directory information as well as a username and password. You may publish files to this repository.

If data files are not available via either S3 file drop or SFTP transfer, but an API or webhook is available, speak with your Client Success representative to discuss pricing and strategy for this approach.

If none of these are a capability of your ticketing provider, the FlexPath integration may not be an option for your implementation. Speak with your Client Success representative to discuss a strategy.

Historical Data Load

Clients may provide up to three years of activity data and all active customers. Using the file format defined below, these files may be batched in monthly or yearly files.

Incremental Data Load

Clients may provide ongoing, incremental data files that represent activity (e.g. all purchases and returns in the 24 hours). Incremental data files will be processed up to once daily into the Fan Data Platform.

File Requirements

Data must be provided in a character-delimited flat file (e.g. file type of .CSV) that meets the file specification outlined here. The following fields are supported in the file structure. Required fields are marked with an asterisk (*). Additional, unusable columns should be minimized to optimize file processing. Each field is single-valued. If multiple values are required, multiple rows should be sent.

Ticketing Sample File

sample-lightweight-ticke…

Download file here

• CUSTOMER DETAILS

  • First Name *

  • Last Name *

  • Email *

  • Phone Number

  • Ticketing Account ID

  • Address Components:
    Note: only US & Canadian addresses are supported

    • City

    • State Abbreviation

    • Postal Code (3-5 characters)

• TRANSACTION DETAILS

  • Transaction DateTime * (UTC or Timezone Offset)

  • Action Type *

  • Order Number *

  • Area

  • Section

  • Row

  • Seat

  • Seat Unique ID *

    • NOTE: If not available, a unique ID can be generated as long as the following values are present:

    • Area *

    • Section *

    • Row *

    • Seat *

  • Price *

  • Ticket Scan Indicator

  • Scan DateTime

• EVENT DETAILS

  • Venue Name

  • Event Name *

  • Event DateTime * (UTC or Timezone Offset)

Scans Sample File

Scans-Sample-File.csv

• tkt_account_id

• given_name

• surname

• street_address

• city

• state

• postal_code

• email

• ticket_id

• seat

• row

• section

• area

• scan_datetime

• event_id

• event_short_name

• event_full_name

• event_start_datetime

• venue_name

Standard Partner Integrations

Ticketmaster, SeatGeek, Paciolan, Tickets.com

If your organization utilizes any of these ticketing providers, we have a custom data integration pipeline built to support them. Each vendor provides a custom route for FanThreeSixty to retrieve data and process into your org’s Fan Data Platform. Speak with your Client Success representative to initiate this process.

File frequencies:

Ticketmaster, SeatGeek: Every 3 hours via API

Tickets.com: Every 3 hours via Flat files

Paciolan: Once daily via Flat Files

Full Custom Integration

If your organization uses a ticketing provider other than Ticketmaster, SeatGeek, Paciolan, or Tickets.com, and is not a candidate for the FlexPath Integration pipeline, a custom route may be needed. This approach is the most time- and resource- intensive approach, therefore it is imperative that you discuss cost and timeline with your Client Success representative before pursuing this approach.