ACME Ticketing Integration

This article gives an overview of the ACME Ticketing integration for Alpine.

Overview

Your Alpine database can be configured to automatically integrate with your ACME Ticketing account, syncing over ticket admissions, donations, and membership payments on a regular basis. 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 ACME Ticketing

Since the goal of this integration is to pull information from ACME Ticketing, your Humanitru Alpine database will not push any information into your ACME Ticketing account—it will only pull information. This is to prevent data overrides—if you update a Member information in ACME (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 ACME Ticketing.

What we pull from ACME Ticketing

On a nightly basis, Alpine will pull all Transactions from ACME Ticketing from the last time it synced—meaning that Alpine will be at most only 24 hours behind the latest data within ACME Ticketing.

Every ACME Transaction can encompass several different Alpine Actions: one ACME Transaction may involve a Ticket to an Event, as well as an additional Donation, and a Membership Purchase. This means that each ACME Transaction will correspond to several Alpine Actions, grouped by the following criteria:

Event Name

For each line item in the Transaction that shares the same Event Name, they will be grouped together as one Alpine Action of Type RSVP. This includes any Add Ons as well.

ACME Ticketing Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Transaction ID	Notes
Transaction Notes	Notes
Order ID	Notes
Discounted Amount	Summed into the Amount field
Quantity	Summed into the Ticket Quantity field, excluding Add On Quantities
Ticket Type	Combined in the Notes field
Add On	Combined in the Notes field
Event	Campaign

 

Event Check-Ins

For each RSVP Action, if there is a corresponding Check-In with an Email and Event ID present, they will be synced as Alpine Action of Type Check-In.

ACME Ticketing Transaction Field	Humanitru Alpine Action Field
Check-In Date	Date (Happened At / Action Date)
Order ID	Notes
Event Fields	Notes
Event Start Time	Notes
Ticket Type	Notes
Event	Campaign

For each line item in the Transaction of AddOnType of “fixedDonation” that shares the same Add On name, they will be grouped together as one Alpine Action of Type Donation.

ACME Ticketing Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Transaction ID	Notes
Transaction Notes	Notes
Order ID	Notes
Discounted Amount	Summed into the Amount field
Add On	Campaign

Membership Purchase

For each line item in the Transaction of OrderItemType of “MembershipPurchase” that shares the same Membership Level and Membership Offering Name, they will be grouped together as one Alpine Action of Type Membership Payment.

ACME Ticketing Transaction Field	Humanitru Alpine Action Field
Transaction Date	Date (Happened At / Action Date)
Transaction ID	Notes
Transaction Notes	Notes
Order ID	Notes
Discounted Amount	Summed into the Amount field
Membership Number	Notes field (see below, also synced into the Constituent profile as a Custom Field)
Membership Level + Membership Offering Name	Campaign, with Membership Level and Membership Offering Name combined with a colon and space in between
Membership Duration / Length	See below (automatically synced every night)

Constituent Profile

All Alpine Actions will be associated with one Constituent, that is matched / de-duplicated by the email address + name given in the ACME Ticketing Transaction.

ACME Ticketing 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 + ZipCode	Combined into the Address field

Nightly Membership Record Reconciliation

Key membership information such as Membership Number and Membership Expiration Date managed in ACME Ticketing will also be reconciled within Alpine on a regular basis. Every night, all Memberships within ACME Ticketing will be reconciled with their corresponding Alpine Actions of type Membership Payment, with the most current Membership Expiration Date from ACME Ticketing updating the Membership Length attribute of the corresponding Alpine Action. Furthermore, any ACME Ticketing Card Holders associated with that ACME Ticketing Membership, with valid email addresses within ACME Ticketing, 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, as well as having the Custom Field of “[ACME] Membership Number” updated as well. 

If the Membership Payment includes a secondary cardholder who is not already present in the Alpine database, a new Constituent record will be generated for that individual, and they will be linked with the respective membership purchase.

Any Memberships within ACME Ticketing will be appropriately reflected not only to the primary Constituent associated with the Alpine Membership Payment Action but also any additional cardholders listed within ACME Ticketing and will also be reflected on additional Constituent profiles within Alpine. Finally, any changes to Membership Expiration Dates within ACME Ticketing will also be reflected within Humanitru Alpine within twenty-four hours.

 

Sync Details

Timing: Nightly

This integration syncs on a nightly basis every 24 hours.

Constituent Matching: Email + Name

When looking up a pre-existing Constituent to match within Humanitru Alpine, the “Email” field will be prioritized, followed by any Custom Fields of type “Email” to return the first matching Constituent. If multiple Constituents share the same email address, Humanitru will then prioritize matching the Constituent using [Base] Field: Name.

If no match is found, then a new Constituent will be created.

Action Matching: Yes

Transactions from ACME Ticketing are de-duplicated by Transaction 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 ACME. This means that if changes are made to ACME Orders after they are created, they must be manually updated within Alpine.

• ACME Transactions with an Email but no Name - ACME transactions containing an Email but no Name will be tagged with "[System] Needs Review: Missing Name from ACME".
• ACME Transactions with a Name but no Email  - ACME transactions synced containing a Name but no Email will be imported in Alpine as a new Constituent record. These Constituents will be tagged as "[System] Needs Review: Missing Email from ACME".
• ACME Transactions with No Email and No Name - When neither a Name nor an Email is provided with an ACME transaction, the transaction will be imported into Humanitru.These transactions will be mapped to an "Anonymous" Constituent record.

Technical Caveats

• Item Purchases that are not associated with fixedDonations or an Event will not be synced.
• Membership Status filters and reporting within Alpine are based on the primary Constituent (hard-credited), and will not accurately reflect the Membership Status of additional cardholders that are “soft-credited” or linked.
• Within Alpine, Memberships are considered started from the moment of purchase, meaning that if within ACME Ticketing a Membership Level is configured such that purchasing a Membership somehow results in the Membership not activating until a certain in the future, Membership reporting within Alpine may not be accurate.
• Due to timezone issues, calculated Membership expirations within Alpine may be up to a day off in rare cases where the time zone of the ACME Ticketing platform does not match the time zone of the configured Humanitru Alpine deployment.