The eventScribe connection sends attendee purchases from a Rhythm event to your Cadmium eventScribe conference, including the access level for each registration package.
Prerequisites
- An eventScribe API key from Cadmium for your conference event.
- The event and its registration packages already set up in Events.
- Access to System & Security in the Console. This connection does not require a separate permission.
Connect eventScribe
- Go to System & Security › Integrations, then choose the Cadmium EventScribe card.
- Enter an account name and the eventScribe API key Cadmium gave you.
- For
Event Name:, choose the conference event whose registrations you want to send. After you choose an event, its registration packages load below. - Select the purchase types you want to send: sessions, functions, add-ons, courses.
- For each registration package listed, choose the eventScribe access level it should receive:
basic,standard, orpremium. - When you are ready for the connection to run, turn on
Enable Connection:. - Choose
Save Changes.
Result
Rhythm saves the connection and is ready to send the selected purchases for the packages you mapped.
You Need an Access Level for Every Package
Every registration package under the chosen event needs an access level before you can save the connection. If the event does not have registration packages yet, add them in Events first.
Choosing a Different Event Clears Your Choices
When you change Event Name: on a saved connection, Rhythm clears the test registration and every access-level mapping you selected. Map access levels again for the new event's packages.
Settings
| Setting | Options | Default | Effect |
|---|---|---|---|
| Account name | Text, required | Empty | Names the connection |
| eventScribe API key | Text, required | Empty | Uses the key Cadmium issued for your event |
Event Name: | One event, required | None chosen | Sets which event's registrations are sent; changing it clears the access-level map and the test registration |
| Send sessions / functions / add-ons / courses to eventScribe? | Four checkboxes | All unticked | Selects which purchase types are sent |
| Access level per registration package | basic, standard, or premium, one per package, all required | None chosen | Gives everyone who bought that package the selected eventScribe access level |
Enable Connection: | On or off | Off | Controls whether the connection is active |
| Test registration | One registration from the chosen event, optional | None | Sends only that registrant while selected |
Test Before You Go Live
Choose a test registration before you send everyone. While a test registration is selected, Rhythm sends only that registrant's purchase and ignores every other registration. Use this to confirm the access-level mapping in eventScribe before you clear the test registration and start sending everyone again.
A success response from eventScribe, even one that echoes the values you sent, does not prove that eventScribe applied the record as expected. If a value such as the access level still looks wrong in eventScribe after Rhythm's outbound data has been confirmed correct, check with Cadmium instead of sending the same record again.
What Rhythm Sends to eventScribe
Rhythm sends each attendee's account details with a few key identifiers.
| Field | Maps to | Uniqueness |
|---|---|---|
| AccountAssociationID | The registrant's Rhythm contact | Unique per contact |
| AccountRegID | The event registration | Unique per registration |
| AccountKey | The event's numeric login number | Not unique; shared across the event's registrants |
Rhythm may send a registrant's purchase to eventScribe more than once with the same identifiers, such as after a profile change or session update. Sending the same registration again with unchanged values has not been observed to create a duplicate account in eventScribe.
Session identifiers are also included in what Rhythm sends. They appear in the AccountUnlockCodesPDF, AccountUnlockCodesAudio, and Favorites fields of the outbound record. Each session ID matches the number at the end of that session's URL in eventScribe, which helps you confirm which sessions were sent for a specific registrant.
Sessions you manually add to a registration after it was first sent are included in what Rhythm sends to eventScribe. Adding those sessions from the console does not resend the registration on its own; open the affected Event Registration and save it to push the updated session list.
Tip
For a purchased session to show as a favorite, or blue check, in eventScribe, the Education Harvester Presentation ID for that session in eventScribe must match the Rhythm session ID exactly. Session syncing also depends on Rhythm's session IDs matching the IDs eventScribe expects. If one session is missing after an otherwise successful sync, the cause is often one mismatched ID rather than a problem with the connection.
If someone's sessions, functions, or add-ons came from a group registration instead of an individual purchase, they may not be stored on that person's Event Registration the same way individual selections are. When a registration record does not list any sessions of its own, eventScribe sync falls back to the sessions tied to that person for the event before sending the payload. Group and later-modified registrations are still expected to sync, though this fallback behavior has not been fully validated in every case.
Cancellations and Access After a Purchase Changes
Rhythm sends a cancellation to eventScribe only for a purchase tied to a standard event registration process. A purchase made as a product or store transaction, including one made through a universal shopping cart, is not tied to that process, so canceling it may not send a cancellation to eventScribe. The same applies when someone buys a product related to a course instead of an actual course registration. Without the registration process the eventScribe setup above depends on, Rhythm may have nothing to send when that purchase is canceled.
If you are checking whether a cancellation removed someone's access, keep history and active access separate. A canceled registration can still appear in your registration history regardless of what was purchased, so history alone does not confirm that eventScribe removed the person's current access. Verify access in eventScribe itself, and contact Cadmium support if it still shows access that should have been removed.
A successful sync to eventScribe is not the same as a successful login there. Rhythm can send a registrant's account details successfully, and the registrant can still be unable to log in. If that happens, investigate the login failure with Cadmium instead of assuming it is a Rhythm sync problem.
Dependencies and Precedence
When you change Event Name:, Rhythm rebuilds the access-level map from scratch using the newly chosen event's registration packages. You cannot carry a mapping from one event to another. The four purchase-type checkboxes apply to the whole connection, not to individual registration packages.
An eventScribe connection syncs one event at a time with one integration key. Rhythm does not support syncing two events, such as the live and virtual parts of a hybrid event, through the same key at the same time. You cannot turn on simultaneous multi-event sync yourself. If you need it, raise it with your Customer Success Manager as a feature request, and plan for manual handling or a delay in the meantime.
Change Impact and How to Revert
After you save an eventScribe connection, you cannot remove it from the Console. To stop it from running, turn off Enable Connection: instead. To change any setting, including the API key or event, open the eventScribe screen again and save your changes. The new values replace the previous ones.
Permissions
Anyone who can sign in to the Console and open System & Security can view and change this connection, including its API key. There is no separate permission for the eventScribe connection.
Validation and Errors
The account name, API key, and event are required. Every registration package under the chosen event must also have an access level before Save Changes completes the save. Registration identifiers that eventScribe receives are limited to 50 characters. Cadmium may reject or mishandle a registration whose outbound registration ID is longer, so keep that in mind if you rename events or packages with long names.
If you are not sure whether a specific registrant reached eventScribe, ask Support to check the integration log for that registration's outbound request and the response eventScribe returned, including account data on a successful send.
| What you see | Cause | Fix |
|---|---|---|
| An attendee has no eventScribe account and can't log in | The registration was never sent, often because it was created before the connection was set up correctly | Confirm the connection settings, then open and save the Event Registration record to send it. Resaving a registration was observed to send it right away instead of waiting for the connection's own schedule |
| An attendee's eventScribe access level doesn't match the mapping you configured | The sync ran before a later change to the registration | Open and save the Event Registration record again to refresh the access level |
| After a substitution, both the original and the substitute registrant still show in eventScribe | Substituting a registration does not automatically update what eventScribe already received | Resave the affected registrations, or resync the event, so only the substitute remains |
| A resend to eventScribe times out | The resend was not filtered to the intended event or meeting, so the payload included far more registrations than needed | Filter the resend to the intended event before sending it again |
| Many registrants for one event need to be resent after a fix | Resaving every record individually is slow | Perform a full resync for that event instead |