All Collections
Technical Troubleshooting
Trouble with the registration link
Trouble with the registration link

You may experience a registration loop if your magic link is bringing you to the event page and prompting you to register again.

Updated over a week ago

In this article:

Registration Looping

Most users will join the event through their registration confirmation without any issues. In rare cases, however, a user may be prompted to register again. This leads them being told they have already registered, and to enter the event through the link in their confirmation emails β€” a registration loop.

When a user selects their unique link in their confirmation email, Sequel adds a special code at the end of the URL. It can look like this:

.../office-hours/office-hours-customer-spotlight-with-steve-hayton-from-morrow?joinCode=DRnpv3xSa8t0

The issue arises when a website builder is stripping the user token from the link once the registrant selects it, forcing them into a registration loop.

If a user is in a registration loop the easiest solution is to have them enter using their unique Join Code, their special key to enter the event.

Finding the Join Code in the Admin Dashboard

Sequel.io's Manage Participant feature allows an Admin or Member to find the Join Code for a user using these steps:

  1. Select the event in your Admin Dashboard

  2. Choose the Participants tab

  3. Find the participant

  4. Click the dots in the far right column for that participant

  5. Select Copy Join Code

Finding the Join Code in the Registration Email

Attendees can also find the Join Code on their own within their registration confirmation email.

Screenshot 2023-03-14 at 12.14.05 PM

Using the Join Code

Once the user has their join code they can enter the event by clicking the message "Already have a Join Code? Click Here". They simply past the Join Code, select Join session, and they will enter the event.

Untitled design (3)-1

Note: users should NOT share their unique registration link or registration code with others. This will cause users to get kicked out of the event and/or multiple of the same user in the event. This will also impact post-event analytics.


​

Did this answer your question?