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.

IMPORTANT NOTE

If combining SSO and Registration Validation across two different vendors, a shared unique identifier is required for matching. Either the registration record must include the MemberID from the SSO identity provider, or the AMS must include the RegistrationID from the registration system.

IMPORTANT NOTE

If combining SSO with Eventscribe Registration, every registration record must include the MemberID from the SSO identity provider for matching. This is typically accomplished through a Registration Member Lookup integration.

Description

During login, the Website, Mobile App, or Survey Magnet calls the third-party registration provider's API to retrieve the user’s registration data.

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)

NOTE

Survey Magnet can only accommodate one unlock code per presentation evaluation, so if you have a complex registration structure, we will have to discuss the requirements to ensure we can accommodate your needs.

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 email address and 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.

NOTE

Note, the Mobile App does not force users to log out. Once authenticated, users generally remain logged in unless they manually log out or delete the app.

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 account associated with their registration record. If the issue persists, submit a ticket to integrationservices@gocadmium.com including:

  • Email address
  • RegistrationID
  • Error message encountered

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article