Cuseum Integration
Push membership details from Alpine to Cuseum so your members' digital membership cards stay up to date.
Overview
Your Alpine database can be configured to automatically integrate with your Cuseum account, pushing membership details to Cuseum on a nightly basis. Cuseum uses this information to create and update your members' digital membership cards.
Before you start
This integration is for organizations that sell memberships through Pinecone. If you sell memberships somewhere else (like ACME or Ticketure), connect that platform to Cuseum directly.
Humanitru sets up the integration for you. To get started, contact your Customer Success Manager. Before the integration is turned on, you'll need to:
- Get API credentials from Cuseum. Cuseum will send them to you through a one-time access link.
- Pick your fields. Tell your CSM which fields to use for member numbers and barcodes (barcodes are optional).
- Get member numbers into Alpine. Every member needs a member number before the first sync. Your CSM will help with this. See About member numbers below.
Your membership tiers come from Pinecone automatically, so there's nothing to set up. Just make sure your membership level names in Pinecone match the ones in Cuseum exactly.
Setup
- Ask Cuseum for your API credentials.
- Send the credentials to your CSM, along with the fields you picked.
- Humanitru connects your account and selects your membership Category and fields in the integration settings.
About member numbers
A member number is a unique ID for each member, like a library card number. Cuseum uses it to know which card to create or update. If a member doesn't have one, their membership won't sync.
Keeping your old member numbers
If your members already have numbers from another system, you can keep them:
- Migrating now: Make sure your old member IDs are brought into a custom field during your migration. Before the first sync, they'll be copied into your member number field.
- Already migrated, and your old IDs came over: They can be copied into your member number field from wherever they're stored.
- Already migrated, and your old IDs didn't come over: Export your member IDs from your old system so they can be imported into your member number field before the integration is connected.
Using Alpine IDs instead
Want to use Alpine IDs as member numbers? Your CSM can set up an automation that copies them into your member number field.
About member numbers
A member number is a unique ID assigned to each member, like a library card number. Cuseum uses it to tell one member's card apart from another's. In Alpine, member numbers are stored in a custom field, which you choose in the integration settings.
When Alpine sends a membership to Cuseum, it combines the member number with the membership tier to create a unique key. Cuseum uses that key to decide whether to create a new card or update an existing one. Without a member number, Alpine can't tell which card to update, so the membership is skipped rather than risk creating a duplicate or overwriting the wrong card.
If your members already have numbers on their existing cards, storing those numbers in Alpine keeps the same numbers on their digital cards.
What we push into Cuseum
On a nightly basis, Humanitru pushes new and updated membership information to Cuseum so your members' digital membership cards are created or updated.
Constituent Mapping
| Humanitru Alpine Field | Cuseum Field | Required? |
|---|---|---|
| Member number combined with membership tier | External ID (external_id) |
Created automatically |
Email Address (email_address) |
Yes | |
| Name | Name (name) |
Yes |
| Phone | Phone Number (phone_number) |
No |
| Address | Address (address) |
No |
| City | City (city) |
No |
| State | State (state) |
No |
| Zip | Postal Code (postal_code) |
No |
| Campaign name (within your membership tier Category) | Membership Level (membership_level) |
Yes |
| Member number (the custom field you chose) | Member Number (member_number) |
Yes |
| Barcode (the custom field you chose) | Barcode (barcode) |
No |
| Membership expiration date | Expiration (expiration) |
No. Left out for lifetime memberships. |
NOTE: Alpine doesn't match members by name or email. If a member doesn't have a member number when the sync runs, their membership is skipped and tagged with the Campaign "Failed to Sync: Cuseum." Add the member number to the custom field you chose in the integration settings to fix it.
What we pull from Cuseum
This integration only pushes data to Cuseum. It doesn't pull any data from Cuseum into Alpine.
Sync Details
Timing: Nightly
This integration syncs on a nightly basis and does not occur in real time.
Member Matching: Member Number and Membership Tier
Members in Cuseum are matched using their External ID, which combines the member number and membership tier. If a matching member already exists in Cuseum, their card is updated. If not, a new member is created.
Updates
Each sync sends every field in the mapping table above. If a field is blank in Alpine, it will also be cleared in Cuseum.
Failed syncs
Memberships that can't sync are tagged with the Campaign "Failed to Sync: Cuseum," under the "Needs Review" Category. A failed membership doesn't stop the rest of the sync.
Best practices
- If you're migrating from another system, wait until your final data migration is complete before connecting the integration.
- Make sure every Constituent who should sync to Cuseum has an email address and full name. Records without them are skipped.
- Add member numbers before the first sync. Memberships without a member number are skipped and tagged "Failed to Sync: Cuseum."
- To keep a Constituent out of Cuseum (for example, staff or test records), tag them Do Not Sync.
- Don't rename or delete the Campaigns in your membership tier Category. The Campaign name becomes the membership level in Cuseum. If a Campaign is deleted by accident, restore it as soon as possible and contact your Customer Success Manager. The affected memberships need a manual re-sync, since the nightly sync won't fix them on its own.
- For lifetime memberships, leave the membership expiration blank. Cuseum requires lifetime memberships to have no expiration date.
FAQ
What happens if a Constituent doesn't have an email address?
Their membership is skipped and tagged "Failed to Sync: Cuseum." Add an email address to the Constituent record, and the next nightly sync will try again.
What happens if a Constituent doesn't have a full name?
Their membership is skipped and tagged "Failed to Sync: Cuseum." Add the name to the Constituent record, and the next nightly sync will try again.
What happens if a member doesn't have a member number?
Their membership is skipped and tagged "Failed to Sync: Cuseum." Add the member number to the custom field you chose in the integration settings to fix it.
Can I keep certain Constituents from syncing to Cuseum?
Yes. Tag the Constituent Do Not Sync, and they'll be excluded from all Cuseum syncs.
Can I sync to Cuseum in real time?
No. The integration syncs nightly only.
Why isn't a member's card in Cuseum updating?
This can happen when a membership was added directly in Cuseum. Add the membership sale in Alpine so future syncs update that member's card.