When someone buys an individual ticket for one of your events on ticketmaster.com, they are using Ticketmaster’s Host system. Ticketmaster pushes this Host data into Archtics: if the buyer has an existing Archtics account, the purchase is added to the standard Ticket table. Otherwise, the purchase is added to a RetailNonTicket table. In both cases, KORE Ticketing receives this data from Archtics during an incremental update and makes the Host data available in your CRM.
KORE does not have direct access to Host data—Ticketmaster is responsible for syncing the data into Archtics. If there’s an error during the sync, Ticketmaster retries several times. However, the system will eventually give up if the failures continue. If this happens, the Host data isn’t added to Archtics and KORE has no way to retrieve it.
One common point of failure occurs when Archtics events aren’t mapped to Host events. This creates a validation error. To reduce the risk of losing the Host data, teams should resolve these errors as soon as possible.