Data sharing - TicketMaster
Zaklina Udovicic avatar
Written by Zaklina Udovicic
Updated over a week ago

Sometimes, you partner with another event organizer or venue, and one of you ends up with all the data. Data sharing allows both of you to access and participate in the customer and order data.

In this article, we will refer to these terms:

The receiver: the organizer that wants to receive data into their MarketHype.

The sharer: the organizer that is going to share the data.

For TicketMaster, the data is received via the integration, and both the receiver and the sharer must have a TicketMaster account. An agreement also needs to be fulfilled between both parties.

Step 1: The receivers part


The organization that will receive the shared data needs to contact TicketMaster support to inform them about the data sharing and ask them to set up a data-sharing agreement between the two organizations.

Once this is settled, the receiver will get access to their API credentials and share them with us at MarketHype so we can enable the integration.

Step 2: The sharers' part


When the receiver has a TicketMaster account, the sharer can start to share events in TicketMaster with the receiver.

This is done in TicketMaster Microflex. The sharer enters the specific event(s) and adds the receiver's customer number (in TicketMaster) in the field "Report access".

The smoothest way is if the sharer gives access at the same time as they add a new event in TicketMaster Microflex. That way, when ticket sales start, all sales automatically get shared with the receiver.

Step 3: The receivers part in MarketHype


The integration automatically picks up upcoming events and all new ongoing sales. However, in order to receive all historical events and historical ticket sales for upcoming events, the receiver needs to contact our success team (success@markethype.io) to ensure that all historical data is imported into their MarketHype.

This needs to be done for all historical events you get access to and every time you get access to an event that already has had ongoing sales before the report access was given.

Did this answer your question?