Eventscribe Website/Mobile App/Survey Magnet Registration Validation

Overview

The Eventscribe Website, Mobile App, and Survey Magnet Registration Validation integration determines user permissions to log in to the site and/or access to specific content based on registration data provided by a third-party system.

This integration can be combined with Single Sign-On (SSO) or implemented with a standalone registration provider. It allows Cadmium to retrieve registration details—such as registration type and purchased items—to control user access within the platform.

For detailed configuration instructions, including examples and required templates, please refer to the supplemental Registration & Access Grid Instructions article.

Description

Registration data can be delivered to Cadmium in two ways: Cadmium can call the third-party registration provider's API at login, or the registration provider can push new registrations or updates to Cadmium via webhook.

Registration Validation can control site and content access using the following:

• Site Access (based on registration status)
• Access Levels (based on registration type)
• Unlock Codes (based on purchased items)
• Registration Items (used primarily for Survey Magnet task filtering)

Registrant User Experience with SSO

This option is available when integrating with an identity provider (e.g. AMS, CRM) that you are also using for registration. 

1. The user navigates to the Website, Mobile App, or Survey Magnet login page.
2. The user clicks Login.
3. The user is redirected to the IdP login page.
4. The user enters their login credentials.
5. The IdP validates the credentials and sends an authentication token to Cadmium.
6. Cadmium uses the MemberID or RegistrationID to make additional API requests to pull registration data. 

If authentication is successful and the user has a registration status that allows them site access:

• The user is redirected to the application landing page.
• If this is the user’s first login, a user account is created and profile fields are mapped.
• If the user has logged in previously, their profile fields are updated as applicable.

If authentication is unsuccessful or the user does not have a registration status that allows them site access:

• A no access error message is displayed.

Registrant User Experience without SSO 

This option is available when integrating directly with a registration company. 

1. The user navigates to the Website, Mobile App, or Survey Magnet login page.
2. The user clicks Login.
3. The user is enters their email address and RegistrationID.
4. Cadmium uses the unique RegistrationID to make API requests to the third-party to pull registration data. 

If the user is found and has a registration status that allows them site access:

• The user is redirected to the application landing page.
• If this is the user’s first login, a user account is created and profile fields are mapped.
• If the user has logged in previously, their profile fields are updated as applicable.

If the user is not found or does not have a registration status that allows them site access:

• A no access error message is displayed.

Registrant User Experience with Webhook 

This option is available when a registration company is configured to send webhook notifications to Cadmium upon registration events. 

1. The registrant purchases, updates, or cancels their registration in the third-party registration system.
2. The registration system sends a webhook notification to Cadmium containing the registrant's data.
3. Cadmium uses the data contained in the webhook notification to create or update the user's account and applies the appropriate access level and unlock codes. 
4. The user navigates to the Website, Mobile App, or Survey Magnet login page.
5. The user clicks Login.
6. The user enters their email address and RegistrationID.

If the user is found and has a registration status that allows them site access:

• The user is redirected to the application landing page.

If the user is not found or does not have a registration status that allows them site access:

• A no access error message is displayed.

Supported Fields

The following fields are available to be populated. Specific configurations will be based on the data available from the customer's membership system and the customer's event-specific needs.

• RegistrantID (required)
• Registration Status
• Registration Type
• Purchased Items
• Member ID (required if combining with SSO)
• Salutation
• First Name (required)
• Middle Name
• Last Name (required)
• Suffix
• Credentials
• Company
• Title
• Email (required)
• Phone Number
• Address 1
• Address 2
• City
• State
• Zip
• Country

Troubleshooting

First, confirm the user is logging in with the correct account:

• If SSO, this is their IdP account associated with their Cadmium user account. 
• If Registration Validation only, this is the registration record associated with their Cadmium account. 

If the issue persists, submit a ticket to integrationservices@gocadmium.com including:

• Email address
• RegistrationID
• Error message encountered
• If SSO, also include:
  • Password if possible (so we can try to recreate) 
  • Member ID

For security purposes, request that the user temporarily reset their password so they do not need to share their actual password.