Attendee Overview
  • 01 Feb 2024
  • 4 Minutes to read
  • Dark

Attendee Overview

  • Dark

Article Summary

Attendance Type Field

A new field called Attendance Type has been added to help track whether an Attendee is attending virtually or in person. The picklist field can be set manually, via custom automation, or by using Forms with Attendee mapping.

NOTE: When upgrading your Events package, the new field will need to be added manually to the Attendee page layout.

The Attendee object is used to capture all the details of the person attending the Event.

The following fields and Related List are now on the out-of-the-box Attendee object page layout.

  • AttendeeLink Section

    • Post Event Questions URL

  • Attendee Info Section

    • Not Paid

    • Donated

    • Visibility Control

  • Others Section

    • Purchased Products

  • Form Submission Answer Related List

Attendees can be related to Contacts in Salesforce. When a Contact is selected while creating an Attendee the details are auto-populated.

Registration Status

Block Registrations with the Same Email 

An Attendee registering for an Event for a second time using the same email address as before can now be blocked. The Attendee will see a registration error if One Unique Attendee Email Per Event is marked “True” on the Event Settings record related to the Event.

Select one of the following values in the Registration Status field.

  • Registration Status = "Lead"
    Manually select this status to set the Attendee as a Lead.

  • Registration Status = "To Invite"
    The status is automatically selected when a Campaign Member is added as an Attendee. The status can also be manually selected when creating Attendees.

  • Registration Status = "Invited"
    If the status is selected and the packaged Workflow Rule "Send Blackthorn | Event invite email" is active, the email invitation will be sent to the Attendee.

  • Registration Status ="Pending"
    Select this status when the Attendee is approved in a waitlist and is awaiting registration.

  • Registration Status ="Registered"
    Select this status when the Attendee is registered for the Event and has completed the payment (if the Event was paid). If the Workflow Rule "Send Blackthorn | Event confirmation email" is "Active", the confirmation email will be sent.

  • Registration Status = "Waitlisted - Pending" (usually set automatically)
    Updating the status to "Waitlisted - Pending" adds the Attendee to the waitlist. See our Waitlist Management documentation for more info.

  • Registration Status = "Waitlisted - Rejected"
    Manually selecting this field indicates that the Attendees were rejected from the waitlist. For example, after an Event is complete and the Attendee is still marked as "Waitlisted - Pending".

  • Registration Status = "Declined"
    This field is automatically set if an Attendee is invited and clicks "No" on their AttendeeLink.

  • Registration Status = "Canceled"
    This field automatically updates to this status when an Event is canceled.

  • Registration Status = "Awaiting Approval"
    This field is manually set to mark Attendees as awaiting approval for the Event.

  • Registration Status = "Rejected"
    Use this field is manually set Attendees as rejected for the Event.

Registration Language Field

Event Admins can identify the language an Attendee used to register for an Event by using the Registration Language field on the Attendee object. The Registration Language field pulls the value from the language of Translation (Source Language) used during registration.

Attendance Status

The Attendance Status field shows the attendance status of an Attendee at an Event. The following values have related actions: 

  • Attendance Status = "Pending"
    This value can be set manually or through a custom process flow.

  • Attendance Status = "Attended"
    When the Attendee is checked in via the mobile app, their status will automatically update to "Attended".

  • Attendance Status = "No-Show"
    This status is for registered Attendees who don't show up. After the Event is complete, their status be updated automatically to "No-Show".

Automatically Set the Attendance Status to No Show

The Event Settings’ Auto-update Attendance to No Show field must be set to "Yes" for the batch job to update the Attendance Status to “No Show”. (You will need to add this field on the page layout). To learn more about the batch job, click here.

Attendance Status

Custom Attendance Status Picklist Value

If you have your own custom picklist value for the Attendance Status field on Attendee, it will get updated to "No Show" after the end date/time has passed.

Primary Email

The main Contact's Email from the Event registration.

The primary email has been added to all email workflows, so the main Contact will receive the invite, confirmation, and reminders of all Attendees they registered.

Example Use Case: executive assistants who register for employees and need to be included in all email communications.

Primary Email 1

Primary Email 2

Registration Date/Time

When an Attendee's Registration Status is updated to "Registered", the Registration Date/Time value is set.

registration date time

Attendee Origin

Use the Source field on the Attendee object to track the origin of an Attendee’s data. The field will be automatically populated with the appropriate value based on how the Attendee was created. The values include “Web App”, “Salesforce UI”, “Bulk Import”, “Attendee Registration Component”, “Campaign Sync”, and “Check-In App”.

  • Field Label: Source

  • API Name: conference360__Source__c

  • Data Type: Picklist

  • Description: Tracks the originating source of an Attendee

Deprecated Fields on the Attendee Object

Below is a list of deprecated fields located on the Attendee object. Please use the fields in the Replacement Field column.

Field Label

API Name

Replacement Field

First Name(Deprecated)



Last Name(Deprecated)










Q: How do I transfer an Attendee from one Event to another Event?
A: Transferring an Attendee from one Event to another Event is not recommended. We recommend creating a new Attendee for the second Event due to potential issues with the related Invoices, Invoice Line records, and the AttendeeLink.