Ticketure Integration

This article gives an overview of the TixTrack Ticketure integration for Alpine.

Overview

Your Alpine database can be configured to automatically integrate with your Ticketure GA/Time-Based Ticketing account, syncing over ticket admissions, donations, and membership payments in real-time. Never miss a beat again and see comprehensive data in one place, your Alpine database, without worrying about manually needing to do exports and imports.

What we push to Ticketure

Since the goal of this integration is to pull information from Ticketure, your Humanitru Alpine database will not push any information into your Ticketure account—it will only pull information. This is to prevent data overrides—if you update a Members information in Ticketure (name, address, etc.), you will need to manually update the corresponding Constituent in Alpine as well. Likewise, if you update a Constituent in Alpine, that information will not automatically update in Ticketure.

What we pull from Ticketure

Alpine will automatically pull all Tickets from Ticketure via web hooks. Every Ticketure Ticket can encompass several different Alpine Actions: one Ticket may involve a Ticket to an Event, as well as an additional Donation, and a Membership Purchase. This means that each Ticketure Ticket will correspond to several Alpine Actions, grouped by the following criteria: 

Event Name

Events are considered tickets in Ticketure and will be imported into Alpine as "Event RSVP" Actions.

Ticketure Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Transaction Amount	Amount
Ticketure Cart ID	Notes
Quantity	Summed into Ticket Quantity field
Event Name	Campaign

Example Action:

 

Donation Add-On

Donation add-ons are considered tickets in Ticketure and will be imported into Alpine as "Donation" Actions.

Ticketure Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Transaction Amount	Amount
Ticketure Cart ID	Notes
Donation Type	Campaign

Example Action:

 

Membership Payment

Memberships are considered tickets in Ticketure and will be imported into Alpine as "Membership Payment" Actions.

Ticketure Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Ticketure Cart ID	Notes
Membership Length	Membership Length
Transaction Amount	Amount
Membership Type	Campaign
Ticketure Membership Code	Notes
Admit Name(s)	Notes

Example Action:

 

Ticket Redemptions

When a ticket has been scanned, which is referred to in Ticketure as a Ticket Redemption, will be imported into Alpine as "Check In" Actions.

Ticketure Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Ticketure Cart ID	Notes
Event Start Time	Notes
Event Name	Campaign

Example Action:

 

Constituent Profile

All Alpine Actions will be associated with one Constituent, that is matched / de-duplicated by the email address given in the transaction from Ticketure. This means that any Transactions without an email address will be skipped, and not synced into Alpine.

Ticketure Transaction Field	Humanitru Alpine Constituent Field
Email	Email
Contact First Name + Contact Last Name	Name
Contact First Name	Email Salutation
Phone Number	Phone
Address1 + Address2 + City + State + Zip Code	Combined into the Address field

 

Membership Record Reconciliation

Key membership information such as Membership Number and Membership Expiration Date managed in Ticketure will also be reconciled within Alpine in real-time. Memberships within Ticketure will be reconciled with their corresponding Alpine Actions of type "Membership Payment", with the most current Membership Expiration Date from Ticketure updating the Membership Length attribute of the corresponding Alpine Action.

Furthermore, any Ticketure Card Holders associated with that Ticketure Membership, with valid email addresses, will be reconciled with any matching Alpine Constituents via email address, and will have the Alpine Membership Payment action “linked” or “soft-credited” to their profile. 

Sync Details

Timing: Real-time

This integration syncs data from Ticketure into Alpine in real-time.

Constituent Matching: Email only

When looking up a pre-existing constituent to match within Humanitru Alpine, the “Email” field will be prioritized, then any Custom Fields of type “Email” to return the first matching constituent. If no match is found, then a new Constituent will be created.

Action Matching: Yes

Transactions from Ticketure are de-duplicated by the Ticketure Cart ID if they already exist within Humanitru Alpine; however, once created/initially synced into Alpine, any further updates will not be propagated into Alpine from Ticketure. This means that if changes are made to Ticketure Tickets after they are created, they will need to be manually updated within Alpine.