All Collections
Adding data and integrations
Integrating data: complex systems
Source system data requirements
Source system data requirements

What data from a typical source system looks like coming into Dexibit

Justin Kearney avatar
Written by Justin Kearney
Updated over a week ago

Data is different from each source system and each vendor. Depending on how data is stored and accessed, this may be:

  • Item level data (preferred)
    For example, a shirt sold in a store (as part of an order with other products) or a fast pass ticket for a child (as part of an order with other tickets)

  • Order level data
    For example, a transaction in a store (which consists of a shirt, a hat and a postcard) or a transaction of a ticketing system (which consists of an adult ticket and a child ticket, each with a fast pass)

  • Aggregate data
    For example, the store made 100 transactions totalling $1,000.00 for the day.

Dexibit prefers to receive data as granular as possible, as this level of data becomes more insightful. If item level data is provided, Dexibit will also summarize the data to provide order level metrics (such as party size). If item or order level data is provided, Dexibit will also aggregate the data to provide additional metrics (such as an attrition rate).

Different systems collect different data. Dexibit prefers to receive all data fields/columns. As well as the data available from a source system, Dexibit can also create novel derived, compound or enriched data.

Example data: ticketing system

Tickets have a lifecycle represented in the ticket data by a series of date/time stamps. Depending on how data is stored, accessed and reconciled by the source system, this data will be shared in different ways with Dexibit:

  1. Booked/Sold, when the ticket was purchased or reserved

  2. Scheduled/Session, when the ticket was issued for

  3. Redemmed/Scanned, when the ticket was used onsite (sometimes, a ticket might have multiple redemptions if it is used multiple times during the visit or across multiple visits)

Personally identifiable data such as the customer's name and contact details should be redacted from the data before it is sent to Dexibit.

Depending on the source system, data relating to the ticket could include items such as:

  • Location ID (venue)

  • Ticket ID

  • Order ID

  • Member ID

  • Seat number

  • Zipcode (location data might also include city, state, country, FIPS)

  • Ticket product

  • Ticket type

  • Ticket category

  • Quantity

  • Unit price ($)

  • Total item price, net ($)

  • Discount amount ($)

  • Discount code

  • Tax ($)

  • Total item price, gross ($)

  • Sales channel

  • Sales person

  • Source

  • Campaign code

  • Payment method

  • Entry gate

  • Voucher amount ($)

  • Voucher ID

  • Refund?

  • Refund amount ($)

  • Refund reason

  • Accessibility requirement

  • Note

Depending on the source system, data relating to the ticket allocation could include:

  • Date/time of the ticket session

  • Ticket product, type or channel

  • Ticket allocation volume (how many tickets can be sold at capacity)

  • Ticket release volume (how many tickets from the capacity have been made available to the public)

  • Date/time of release (when the tickets were released to the public)

  • Name of release (for example, 'Visa exclusive presale')

Did this answer your question?