3rd Party-to-Elevate Registration Data Sync

Overview

This integration automatically creates registrations (enrollments) in Elevate when a purchase or registration occurs in a connected third-party system, and removes them when items are cancelled. The third-party platform — typically a registration system, event platform, or AMS store — acts as the authoritative source for purchase and cancellation records. Elevate receives that data through the Elevate Registration API and provisions the user and registration automatically.

The integration reduces manual administrative work and keeps registration data consistent across platforms.

Availability is conditional on the third party. We can offer this integration so long as the third party supports one of the two supported trigger options and meets the third-party requirements outlined below. Confirmation by the customer and the third party is a prerequisite to contracting.

How It Works

The third-party system is the source of truth for registrations and cancellations. Data flows in one direction: third party → Elevate.

Trigger Options

1. Webhook subscription (preferred). If the third party can emit an event/webhook when a registration is created or cancelled, Cadmium subscribes to that trigger and processes each event in near real time.
2. Scheduled pull. If the third party does not offer webhooks but exposes an API, Cadmium makes a request on a fixed schedule, detects new and cancelled registrations, and processes them in batches.

In both cases, once a qualifying registration is detected, Cadmium maps the data and sends it to the Elevate Registration API.

Registration Flow

• Create-or-match user. Cadmium sends the user's identifier, name, and email, plus the product identifier and amount paid, to the Elevate Registration API. Elevate looks the user up by remote_user_id:
  • If the user already exists (by remote_user_id), they are simply registered for the indicated product.
  • If the user does not exist, Elevate creates the account first and then registers them.
• Product mapping. Each third-party item is mapped to an Elevate product, identified by either remote_product_id (the product's ID in the AMS/store, configured in Elevate's Remote Product ID field) or Elevate's internal product_id.
• Confirmation. Once the registration succeeds, Elevate confirms it and the user gains access to the mapped product.
• Optional learner email. Elevate can optionally send the buyer a confirmation email with a product-access link. Whether this is enabled is a client decision.

Cancellation Flow

When the third party reports a cancellation, Cadmium cancels the corresponding registration in Elevate using the reference stored at registration time, along with a cancellation reason. The originally registered user can optionally be notified.

Timing & Processing

• Webhook mode: registrations and cancellations process in near real time.
• Scheduled-pull mode: registrations and cancellations process on a scheduled cadence.
• Non-retroactive: the sync applies only to registrations and cancellations that occur after activation of the integration. Pre-activation registrations require a manual import.

Field Mapping

Cadmium maps third-party registration fields to the Elevate Registration API:

Identity & User Matching

Elevate's Registration API matches on remote_user_id, the same identifier used by the SSO integration. The Registration API was built to complement SSO, where the AMS acts as the identity provider and also pushes registrations into Elevate. The value placed in remote_user_id depends on the client's identity configuration.

Important Considerations

• Product mapping is per-item. Each syncing third-party item must be mapped to an Elevate product during implementation.
• Financials. If Elevate is not the system of record for payments, the amount paid is sent as 0.
• One-directional sync. Changes made directly in Elevate are not pushed back to the third party. Email/profile updates should be made in the source system.
• Non-retroactive. Only post-activation activity syncs; historical data requires manual import.

Third-Party Requirements

1. Third-party trigger support: the third party offers a webhook or API.
2. Required data available from the third party: a unique user identifier, first name, last name, email, and a product identifier mappable to an Elevate product.
3. Product mapping defined: each third-party item mapped to an Elevate product.