Ticketek is an Australia-based ticketing services provider. KORE Ticketing can collect, deduplicate, and process Ticketek data for use in your CRM. Ticketek provides data in realtime via an Amazon Kinesis data stream, which we queue for processing every 15 minutes.
Important: KORE's Ticketing Data Manager (TDM) cannot be used with Ticketek at this time.
To load historical data into KORE Ticketing, we use the Ticketek APIs to download the data. The time this takes will vary depending on how much data exists. Additionally, Ticketek limits how fast we may access the data in order to protect their systems.
Alternatively, you can submit an export of historical data to us. This may be useful if it contains more historical data than what is available via the Ticketek APIs. Contact your KORE Success Manager to discuss this option.
Once loaded, we will begin the deduplication process and incremental updates.
Main article: Incremental updates
Because the Amazon Kinesis stream delivers data in realtime, KORE's incremental update differs slightly from the three-phase update used for other ticketing services. Instead of a Download phase, each update received is stored in a queue until the next Apply phase begins and succeeds. A new Apply phase begins every 15 minutes, unless the previous one is still running.
Main article: Deduplication and the mapping table
Note: Most KORE clients who use Ticketek also use an additional ticketing system such as Archtics. Our MultiDB feature ensures that deduplication is handled correctly in these cases.
Ticketek provides data as either a sales record or an attendance record. Each record contains a user ID for the purchaser or attendee, and we use the mapping table to determine if a contact with this user ID is already in your CRM.
If no existing contact is found, we use our deduplication logic to search for a matching CRM record. If a match is found, we mark this user ID as a secondary ticketing account for that CRM contact and store it in the mapping table. Otherwise, we create a new CRM contact and mark this user ID as the primary ticketing account.
Our deduplication logic works for both people and company names. We also use “fuzzy matching” to help match up information that isn’t written in exactly the same way, such as First St. and 1st Street.
If the ticketing account also has a company name associated with it, we use deduplication logic to check if there’s an existing CRM account or if a new one needs to be created. CRM accounts represent companies and let us display all your contact people at that company together in one place.