Eventscribe Registration to Elevate: Course Enrollments

Overview

Purchases in Eventscribe (Es) Registration create enrollments in Elevate, and cancellations trigger unenrollments—reducing manual work and providing a seamless learner experience.

During setup, you will work with Cadmium to map Es Registration fee items to the appropriate Elevate products. 

How It Works

Es Registration serves as the system of record for the products configured for this integration.

• When a learner purchases a product-related item in Es Registration, they are enrolled in the corresponding Elevate product.
• If the registrant does not already exist in Elevate, an account is created. 
• If the item is canceled, they are unenrolled from the corresponding Elevate product.

Timing & Processing

• Enrollments: Processed immediately after purchase (typically within 1 minute)
• Cancellations: Processed immediately after cancellation (typically within 1 minute)

Important Considerations

Before enabling this integration, please review the following to ensure a smooth and successful sync experience: 

• If you also sell other products through Elevate’s own cart, set Remote Registration URL on the products that should go through Es Registration instead:

  • In the Admin Control Panel, open the corresponding Elevate product’s edit page, go to the Basic tab, then the Integration sub-tab, and set the Remote Registration URL field to the Es Registration URL. This makes the Register button redirect learners to Es Registration for that product instead of Elevate’s built-in cart.
  • If the product has a free variant that shouldn’t be sent to Es Registration, check Remote URL Usage: Only Use Remote Registration URL If Product Is NOT Free To The User. This lets free registrants complete registration directly in Elevate, while registrants who owe payment are redirected to Es Registration.
• Remote User ID is required for identity matching:
  • This integration is intended to be used in combination with Es Registration Member Lookup and Elevate Single Sign-on integrations.
  • The identity provider and Remote User ID (typically Member ID) must be the same for both integrations. 
  • All registrants must go through the member lookup flow, meaning non-members must also exist in the identity provider's membership database. 
  • A Remote User ID must be present on a registrant's record at the time of purchase; registrants without a Remote User ID on file will not be enrolled in the corresponding Elevate product.
• Remote User ID consistency is required to ensure accurate matching: 
  • Remote User ID serves as the unique identifier used to match records between Es Registration and Elevate, and must remain the same in both systems. 
  • If a Remote User ID needs to be updated, it must be updated in both systems to maintain proper record matching. 
• Registration transfers must be handled by canceling & purchasing:
  • If a registration needs to be transferred to another individual, the item(s) must be canceled/refunded for the original registrant and purchased for the new registrant.
• Enrollments only apply after integration launch: 
  • The sync applies to purchases and cancellations made after it is enabled. 
  • If the Es Registration form launches before the sync is enabled, an initial import must be completed in Elevate using the standard import process to ensure all existing registrants are properly enrolled.

Field Mapping

*Fields marked with an asterisk are sent with every registration and used to look up the matching Elevate user. They are only written to Elevate when a new user record is created. If the user already exists in Elevate, these fields are not updated on subsequent registrations. In Es Registration, self-service editing of these fields should be read-only for registrants. If an administrator edits any of these fields in Es Registration, the corresponding updates must also be made directly in Elevate.