Skip to main content

How do individual attendee codes work?

Use individual access codes to securely identify attendees, personalize their experience, and connect their activity to their attendee record.

Written by Jasmin Murcia

Each invited attendee receives a unique code. When they enter the meeting, MeetingPulse asks them to provide that code before granting access. Their name can then appear with their Q&A submissions and in meeting reports.

You can also upload custom data, add bookable sessions, and even assign different individual weights for their votes. See more about CSV formatting

Enable individual access codes

Before adding attendees:

  1. Open your meeting.

  2. Go to Meeting > Settings > Access and Identity.

  3. Select Access Codes as the meeting’s access mode.

You can then add attendees by uploading a CSV file or entering their email addresses directly.

Upload attendees using a CSV file

Uploading a CSV is recommended when you need to include attendee names, vote weights, or custom data.

  1. Go to Attendees > Add Attendees.

  2. Under Upload a CSV, download the sample file.

3. Add your attendees below the header row.

email,firstName,lastName,voteWeight
[email protected],John,Smith,1

Tip: Include one test attendee with an email address you can access. This allows you to test the invitation and login process before contacting your full attendee list.

4. Save the file as a CSV.

5. Click Select file and upload it.

6. Once you have uploaded your attendees, you will see a notification next to the Upload CSV button showing how many attendees were successfully added.

Open the Attendee List to confirm that each attendee appears with an individual access code.

Add attendees by entering email addresses

You can also type or paste email addresses directly into MeetingPulse.

  • Go to Attendees > Add Attendees.

  • Enter the email addresses, separated by commas or spaces.

  • Click Add emails.

When attendees are added this way, their email address is used as their default identity.

Add custom attendee data

To add custom data:

  • Go to the Attendee List.

  • Click Export in the upper-right corner.

  • Open the downloaded CSV file.

This will give you a CSV with the attendee codes and user IDs.

  • Add one column for each custom data field.

Custom data column names should not contain spaces or slashes. For example, use departmentName instead of Department Name.

Keep the existing attendee codes and user IDs in the file so MeetingPulse can match the updated information to the correct attendee records.

  • Enter the appropriate information for each attendee.

  • Return to the Add attendees section and click Select file to upload the updated document.

After uploading the file, review the Attendee List and confirm that the attendees, access codes, and custom data appear correctly.

Send invitations through MeetingPulse

To send invitations containing each attendee’s individual access information:

  1. Go to Attendees > Email Attendees.

  2. Customize the email subject and message.

  3. Add a payment call-to-action, company address, or calendar invitation if needed.

  4. Send a test email to yourself or another test attendee.

  5. Review the test email and confirm that its links and information are correct.

  6. Under Recipients, choose who should receive the email:

  • All attendees: Sends the email to everyone on the Attendee List.

  • Newly uploaded invitees since the last invitation send: Sends the email only to attendees added since invitations were last sent.

  • Attendees who haven’t joined yet: Sends a reminder to attendees who have not entered the meeting.

  • Attendees who haven’t responded to any polls: Sends the email to attendees who have not submitted any poll responses.

  • Select specific attendees: Allows you to choose individual attendees from the list.

7. Confirm the number of recipients shown on the send button.

8. Click Send emails when you are ready.

You can personalize the message using the following variables:

  • %name% — Full name

  • %firstName% — First name

  • %lastName% — Last name

  • %customFieldName% — The value from a corresponding custom data field

Here’s what the email looks like:

Send invitations through another email tool

You can also distribute attendee access information using your organization’s email or communication platform.

  • Go to the Attendee List.

  • Click Export in the upper-right corner.

  • Open the downloaded CSV file.

  • Use the attendee names, email addresses, and values in the code column to create your messages.

Handle the exported file securely because it contains each attendee’s unique meeting access code.

Help attendees retrieve a lost code

If an invited attendee has lost or cannot find their access code, they can request it on the meeting login page.

  1. The attendee opens the meeting link.

  2. They click Send me my code.

  3. They enter the email address used on the meeting’s attendee list.

  4. MeetingPulse checks whether that email address is associated with an invited attendee.

  5. If the address is found, MeetingPulse sends the attendee’s access code to that email.

Note: The attendee must enter the same email address that appears in the Attendee List. If the email is not recognized, confirm that the attendee was added and that their email address is spelled correctly.

If the message does not arrive, ask the attendee to check their spam or junk folder. You can also confirm their information in the Attendee List and resend their invitation if necessary.

Before your meeting

Test the full attendee experience before distributing invitations:

  • Confirm that Access Codes is selected as the access mode.

  • Add a test attendee using an email address you can access.

  • Send yourself a test invitation.

  • Verify that the access code allows you to enter the meeting.

  • Test the Send me my code option.

  • Review the Attendee List for missing or incorrect email addresses.

Testing these steps in advance helps attendees access the meeting quickly and reduces login questions when the event begins.

Did this answer your question?