Cuseum Integration

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

Humanitru connects the Cuseum integration on your behalf, so contact your Customer Success Manager when you're ready to get started. Before the integration is connected, make sure you have the following in place:

API credentials from Cuseum. Cuseum creates a dedicated API user for your account and shares the details through a one-time access link. (See Setup below.)
A membership tier Category in Alpine. Create a Category whose Campaigns represent your membership tiers (for example, a "Membership Tiers" Category with "Gold," "Silver," and "Bronze" Campaigns). Campaign names must exactly match your membership levels in Cuseum. If they don't match, the sync will create new memberships in Cuseum.
Custom fields for member numbers and barcodes. You'll need a custom field for member numbers, and you can optionally add one for barcodes (for example, "[Cuseum] Member Number" and "[Cuseum] Barcode"). If you already store these values in existing custom fields, you can use those instead.
Member numbers, set up with your Customer Success Manager. Every member who should sync needs a member number before the first sync. Because these numbers become the IDs on your members' digital cards, work with your Customer Success Manager or implementation team to set them up rather than creating them on your own.
- New to Alpine? Your implementation team will help you decide how member numbers should be assigned and get them into Alpine before the integration is turned on.
- Migrating from another system (such as Raiser's Edge)? If you want to keep your existing member numbers, let your implementation team know. They'll bring those numbers into Alpine so your members keep the same numbers on their digital cards.

NOTE: If you sell memberships through Pinecone, your membership Category is created automatically with your first membership purchase and is named "Membership Actions" by default. A Campaign for each membership level is created the first time that level is purchased.

Setup

Request API credentials from Cuseum. Cuseum's technical or support team will create a dedicated API user for your account and send the email, password, client ID, client secret, and museum ID through a one-time access link.
Share the credentials with your Customer Success Manager. Humanitru will connect your Cuseum account on your behalf.
In Alpine, go to Settings > Integrations and open the Cuseum integration. Choose:
- The Category that contains your membership tier Campaigns
- Member Number Field: the custom field that holds your member numbers
- (Optional) Barcode Field: the custom field that holds your barcodes
Before the first sync, make sure every active member has a member number in the field you chose.
- New to Alpine? Enter or import member numbers before the integration is turned on. Your Customer Success Manager can help with a bulk import.
- Migrating from another system (such as Raiser's Edge)? Let your implementation team know, and they can copy your existing member IDs into Alpine before the first sync.

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	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.