Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
BT Salesforce Release
(Release Date: January 27, 2026)
Bug Fixes
Clone Events: The Donation Payment Gateway (conference360__ Donation_Payment_Gateway__c) field is now available to add to the Event’s "Deep Clone Layout" (conference360__Deep_Clone_Layout) field set. If an Event uses the Donation Payment Gateway field and a user clones the Event, the field will be cloned to the new Event. To add the field, use Event > Field Sets > Deep Clone field set. (Known Issue: 000004974)
Session Attendee: The Session Attendee record’s Name formula field now correctly reflects the updated Attendee name. Previously, the Session Attendee’s Name referenced deprecated fields and was not updated when the Attendee’s name was changed. (Known Issue: 000004974)
Visibility Rules: When creating Visibility Rules, Event Organizers will only see Contacts who meet the eligibility requirements in the Preview Eligible Contacts section. Previously, both eligible Contacts and Contacts with visibility but no eligibility were visible.
Waitlists and Person Accounts: An Event has an Event Item with waitlists enabled and is in an org with Person Accounts. If an Attendee registers for the Event, their Attendee record’s Contact and Account fields will populate as expected. Previously, the Contact and Account fields were overwritten and left blank.
Event Registration Submission (ERS): When an Attendee registers for an Event with valid attendee and payment details, the registration is processed successfully, and an Event Registration Summary (ERS) record is created and linked to the Attendee record. No error messages appear in the logs or on the UI. Previously, the registration appeared to be successful, but the "Attempt to dereference the null object" error message was displayed on the ERS record, and a new Attendee record was not created. (Known Issue: 000005090)
Event Groups: If an Event Organizer creates a new Event in Salesforce and the related Event Settings record has the Disable Auto-Add to Default Event Group field checked, then the Event won’t be added to an Event Group. Previously, the Event was added to the default Event Group. (Known Issue: 000005036)
Webinars: The following updates were made to how links are generated for Webex webinars after a user clicks the Create Webinars for Events button. Previously, clicking the button didn’t trigger the WebinarAuthRefresh batch job to update the refresh token. (Known Issue: 000005053)
When the Event and Session start and end dates are in the past, the Webinar/Meeting URL will not be populated, and Blackthorn logs are not generated.
When the Event and Session start and end dates are in the future, the Webinar/Meeting URL will be populated, and Blackthorn Logs are not created.
Smart Scheduler: Updates were made to the Smart Scheduler component to remind Event Organizers that clicking the Backspace/Delete keys on a template in the Body field will delete the entire template in the Body field. This is because of a Salesforce limitation with the rich text component. The new message also includes a link to edit the Email Template. Previously, when a user clicked into the Body field to make changes to the template and pressed the Backspace or Delete key, they inadvertently deleted the entire template in the Body field. (Known Issue: 000004934)
Attendee Registration Component: If an Event Organizer tries to register an Attendee for an Event from the Attendee Registration Component on the Event record, they will only see Event Items with Type set to “Main event ticket.” Event Items with Type set to “Donation,” “Guest,” and “Other” are not available from the Attendee Registration Component. (Known Issue: 000005082)
Form Elements
Event Organizers can now map a hidden Form Element (Type = “Hidden”) to a number field on the Lead object using the Form Element’s Maps To (Field) field. Previously, the Form Element’s Maps To (Field) dropdown did not include number fields. (Known Issue: 000005132)
Event Organizers can now map answers from Big List Group questions (Form Element with Type = “Big List Group”) to picklist and multi-select fields in the Form Element’s Maps To (Field) field. For example, an Event Organizer can set the Maps To (Object) field to “Attendee” and select any picklist field, such as “Attendee Checkout Type” or “Visibility Control.” Previously, the Maps To (Field) did not show picklist field options. (Known Issue: 000005138)
Enhancements
Discount Codes: Updated discount logic now allows Event Organizers to add a discount or access Code to a Product.
Event Builder: When using the Event Builder to add a Session, the Event Builder will auto-populate the Session’s Start Date, End Date, Start Time, and End Time fields based on the values in the Event’s Event Start Date, Event End Date, Event Start Time, and Event End Time fields.
Express Registration: When using Express Registration, an authenticated user can select “Someone Else” to register a guest, and the newly created Contact record for the guest will be associated with the authenticated user’s Account. This enhancement provides better data organization and Account relationship management for Events with guest registrations.
Email Templates: Event Organizers can now override the following flows and update the Email Template used in the flow to provide greater customization.
Blackthorn | Events ERS Failed (Blackthorn_Events_ERS_Failed)
Blackthorn | Events WebinarService Failed (Blackthorn_Events_WebinarService_Failed)
Send Blackthorn | Event Reminder email (Send_Blackthorn_Event_Reminder_email)
Send Blackthorn | Event confirmation email (Send_Blackthorn_Event_confirmation_email)
Send Blackthorn | Event invite email (Send_Blackthorn_Event_invite_email)
Send Cancelled Registration Email (Send_Cancelled_Registration_Email)
Send the Waitlisted Email (Send_the_Waitlisted_Email)
Send the removed from the Waitlist Email (Send_the_removed_from_the_Waitlist_Email)
Custom Content: When an [embed] tag is used to embed media in a Custom Content record, Salesforce will validate that the embed tag source URL is allowlisted. If the source is not part of the allowlist, the content is not displayed. Example: When an Event Admin embeds an iframe in Custom Content, they will get an error if the [embed] tag includes a non-allowlisted origin.
Send Email Component: The title of the Send Email component on the Event record was updated to “Send Email Immediately.”
Email Configuration Component: Event Organizers can configure a default email address for the Email Configuration component by using the Event Settings Send Email From field. The new field lets Event Admins change the default email address to an org-wide email address, ensuring emails are sent from monitored and authorized addresses. Now, when sending emails, the 'Send Email From' dropdown will default to the email address configured in the Send Email From field. NOTE: Only Org-wide email addresses are accepted. If a NON-org-wide email address is added to this field, the default selection will be the current user.
Object: Event Settings
Field Label: Send Email From
API Name: conference360__Send_Email_From__c
Data Type: Text(80)
Help Text: Email address to use as the sender for emails sent from this event. Only Org-wide email addresses are accepted. If an email address is added to this field and not set up as an Org-wide email address, the default selection will fall back to the current user.
UI Experience: We are continuing to modernize the Events user experience. New installations of Blackthorn Events will no longer include the “Full-Width” and “BYO-CSS” picklist values from the Event UI Experience field. Once the full deprecation of the Full-Width UI is complete, existing Events with the UI Experience field set to “Full-Width” will automatically be changed to the Dynamic UI. Existing customers who upgrade Events will not be impacted by this change.
Seats and Tables
The Table Manager now supports up to 100 Tables with 50 Seats per Table, for a total of 5000 Attendees. To manage large Events with a higher volume of seated Attendees, Event Organizers can use the “Select Tables” feature to show or hide different Tables. NOTE: There must be at least 101 Seats for the Select Tables button to be visible.
Event Organizers will see up to 100 Seats if there are more than 100 Seats across all Tables. Click the Select Tables button to view more Tables.
After clicking Select Tables, Event Organizers can search for Tables by Table Name, click Select All to select all Tables, or select individual Tables.
Additional updates to the Attendee search and display Table functionality include the following.
If a user performs a search and there are more than 100 Attendee records, then they will see a list of 100 Attendees and the following message. “100 records matched your search and are displayed in the results. Please refine your search keywords."
If some Attendees are assigned to Tables, and a user performs a search and views the Unassigned section, they will only see unassigned Attendees.
To help users differentiate between Attendees with the same name, users can hover over an Attendee’s name to see the Attendee’s email.
Event Organizers can use the Filter By picklist to filter results by Attendee Registration Status. "Registered" is selected by default.
Static Translations
Event Organizers can now add Static Translations to Event Groups by using the following four new fields on the Translation object.
Field Label: Event Group
API Name: conference360__Event_Group__c
Data Type: Lookup
Description/Help Text: Select the Event Group to translate. This lookup associates the translation record with a specific Event Group.
Field Label: Events Event Group Alternative Text
API Name: conference360__Events_Event_Group_Alternative_Text__c
Data Type: Text(255)
Description/Help Text: Enter the translated alternative text (alt text) for Event Group images.
Updated Permission Sets
Read/Edit: Blackthorn | Events (Admin) and Blackthorn | Events (Organizer)
Read Only: Blackthorn | Events (Lite User) and Blackthorn | Events (Read Only)
Field Label: Events Event Group Description
API Name: conference360__Events_Event_Group_Description__c
Data Type: Rich Text Area(32768)
Description/Help Text: Enter the translated description for the Event Group.
Updated Permission Sets
Read/Edit: Blackthorn | Events (Admin) and Blackthorn | Events (Organizer)
Read Only: Blackthorn | Events (Lite User) and Blackthorn | Events (Read Only)
Field Label: Events Event Group Name
API Name: conference360__Events_Event_Group_Name__c
Data Type: Text(80)
Description/Help Text: Enter the translated name for the Event Group.
Updated Permission Sets
Read/Edit: Blackthorn | Events (Admin) and Blackthorn | Events (Organizer)
Read Only: Blackthorn | Events (Lite User) and Blackthorn | Events (Read Only)
Event Tracking Improvements (GTM and UTM)
The Event Settings object now includes the GTM Container ID field, enabling Event-level configuration of Google Tag Manager (GTM).
Object: Event Settings
Field Label: GTM Container ID
API Name: conference360__GTM_Container_ID__c
Data Type: Text (Length 30)
Help Text: Your Google Tag Manager container ID (e.g., GTM-ABC1234). Used to load GTM on event pages and embedded registration. Event-level setting overrides org-level GTM.
Description: Stores the Google Tag Manager (GTM) container ID for this event. When populated, this event-level setting overrides the org-level GTM configuration and is used by the Events webapp to load GTM on Event pages and embedded registration.
Updated Permission Sets
Read/Edit
Blackthorn | Events (Admin)
Blackthorn | Events (Organizer)
Read
Blackthorn | Events (Lite User)
Blackthorn | Events (Community/Platform User)
Blackthorn | Events (Read Only)
No Access
Blackthorn | Events (Limited Access)
Blackthorn | Events (Community Guest User)
The value in the Event Settings GTM Container ID (GTM_Container_ID__c) field must meet the following criteria:
The ID starts with “GTM-“
Includes only valid characters (uppercase letters and numbers)
The format matches “GTM-XXXXXXX” (prefix GTM- followed by 6–10 uppercase letters/numbers).
The “Google Tag Manager ID” set at the Event level (Event Settings GTM Container ID) will override the “Google Tag Manager ID” set at the company level (Company Info Google Tag Manager Id).
If the Event Settings GTM Container ID field is blank, the “Google Tag Manager ID” will default to the value in the Company Info Google Tag Manager Id field.
If neither field contains a value, the “Google Tag Manager ID” will be blank.
Webapp Release
(Release Date: January 27, 2026)
Bug Fixes
Add to Wallet: iOS device users can click the Add to Wallet button from their post-registration AttendeeLink and add their Ticket to the Apple Wallet. Previously, users got an error, and the ticket wasn’t added to the Apple Wallet.
Currency: For Events with Currency set to “JPY” (Japanese Yen), registrants will see the correct amount on the Stripe Checkout page if the Payment Method is set to Stripe Checkout. Previously, the amount listed on the Stripe Checkout page was multiplied by 100. (correct: JPY 5,000 vs. incorrect: JPY 500,000) (Known Issue: 000005065)
AttendeeLink: To match the AttendeeLink functionality, Navigator app users will see a Session if the related Event Item has the Hidden field checked. Previously, users could not see the Session. (Known Issue: 00004997)
Waitlisting and Minimum Quantities: Event Items with the Waitlist Enabled field enabled count toward the Event Item’s Minimum Quantity requirement when an Event’s UI Experience = “Dynamic.” If an Event Item’s Minimum Quantity field contains a value other than zero, and the Quantity Available is less than the Minimum Quantity, the Attendee will see two Tickets and one waitlisted Ticket in their cart. If the Quantity Available is greater than the Minimum Quantity, the Attendee will see the Get Tickets button on the Event webpage and can use the “+” and “-“ buttons when selecting Tickets. Previously, on the Event webpage, the “Maximum Items Selected” message was displayed on the Ticket even though the Attendee had not added Tickets to the cart. Additionally, clicking the “+” and “-“ buttons did not change the number of Tickets selected.
UTM Parameter Tracking: If an Event has UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, and utm_content) in the URL, and an Attendee moves through the Event registration process (Event webpage > Cart > Checkout), the UTM parameters will persist through each step. Previously, the UTM parameters were dropped from the URL, resulting in the loss of UTM data, which impacted the accuracy of analytics, marketing attribution, and reporting on ad campaign performance.
Accessibility: When using a screen reader to read a Form question with a date-type format, the screen reader will first announce the question and then read the associated hint. Previously, the screen reader only read the question.
Forms: An Event URL or Form URL will load correctly when the related Event includes an Event Item with a Form, and the Form URL contains an invalid or expired encrypted value. Previously, when an Attendee tried to load the Event URL or Form URL, they received a 2004 or 2006 error message if the Form included nested questions without a parent question, and the Form URL contained an invalid or expired encrypted value. (Known Issue: 000005103)
Stripe Checkout: If an Attendee abandons their cart by clicking the back arrow at the final checkout step and the Event is embedded in an Experience Cloud and configured to use Stripe Checkout, the Attendee will be redirected back to the Event webpage. Previously, they received an error and were not redirected to the Event webpage.
Sessions: An Event offers Sessions, and Attendees have registered for those Sessions. If the Event’s Hide Register Button is set to “Yes,” registered Attendees can open their AttendeeLink and view their registered Sessions and register for available Sessions. Previously, all Session information disappeared from the AttendeeLink once the Event’s Hide Register Button was set to “Yes.” (Known Issue: 000005148)
Enhancements
Static Translations: Event Organizers can add static translations to the following Event Group fields:
Events Event Group Alternative Text (conference360__Events_Event_Group_Alternative_Text__c)
Events Event Group Description (conference360__Events_Event_Group_Description__c)
Events Event Group Name (conference360__Events_Event_Group_Name__c)
Waitlisting and Attendee Groups: If an Attendee, who is part of an Attendee Group, registers for a waitlisted Ticket, the Primary Email field on their Attendee record will be populated with the Attendee Group’s main Contact’s email address. Previously, the Primary Email field was left blank.
Forms for Sessions: The Forms for Sessions feature now works for Events with UI Experience set to “Tabbed.” For information about how the feature works, click here.
Post-Event Questions: If an Event includes a Form in the Post Event Questions field and the Event is past the Event End Date, then the post-Event survey will remain accessible for the number of days listed in the new Post Event Survey Expiration Date (conference360__Post_Event_Survey_Expiration_Date__c) field. The Post Event Survey Expiration Date field only works when the Event's Event End Date field is populated.
Sessions
When a Session’s Location field contains information and an Event has UI Experience set to "Dynamic," the information will be displayed on the Event overview page, Session selection page, and on the AttendeeLink’s “My Agenda” tab and Session Registration tab.
Registrants will see the Session search bar on the Session Selection screen when there are 10 or more Sessions to choose from, making it easier for registrants to find a Session. Previously, the search bar appeared when there were 20 or more Sessions.
To help Attendees see as many Sessions as possible on the Session Registration page without having to scroll as much, each Session is now collapsed when the page loads. Clicking Show Details expands the Session’s details, while clicking Hide Details collapses the section. This feature applies to Dynamic and Tabbed UIs.
The header for the Session includes the Display Name, (Session Name if the Display Name field is blank), Image URL, Start Date, Start Time, End Date, and End Time.
The following information is visible after an Attendee clicks Show Details.
Description
Location
Speakers
Event Tracking Improvements (GTM and UTM)
The Universal Event Tracking via GTM now includes an Attendee’s purchase summary details, providing Event Organizers with better visibility into revenue tracking.
Waitlist-Only Event Items
Attendees who register for an Event with only waitlisted items in their cart will be tracked, allowing Event Organizers to capture the following information: the currency, quantity of waitlisted Event Items, and a list of the waitlisted Event Items.
Waitlist + Regular Event Items
Attendees who register for an Event with a combination of available and waitlisted items in their cart will be tracked, allowing Event Organizers to capture the following information:
Event Items: the currency, quantity, amount, total (amount * quantity), and a list of the Event Items
Waitlisted Event Items: the currency, quantity of waitlisted items, and a list of the waitlisted Event Items
Regular Event Items
Attendees who register for an Event with only available Event Items in their cart will be tracked, allowing Event Organizers to capture the following information: the currency, quantity, amount, total (amount * quantity), and a list of the Event Items.
Multiple Waitlisted Event Items
Attendees who register for an Event with different waitlisted Event Items in their cart will be tracked, allowing Event Organizers to capture the following information. Each unique waitlisted Event Item will include: the currency and quantity of that Event Item, and a list of those waitlisted items.
For example, if the Event includes four Event Items and each one is waitlisted, then there will be four sets of information, each containing the currency and quantity of that Event Item, as well as a list of those waitlisted items.
UTM parameters (e.g., utm_source, utm_medium, utm_campaign, utm_term, utm_content) will remain consistent each time a user moves between URLs, in an iframe, or reloads a webpage.
To help Google Analytics capture and report on metrics for visits to an Event Group webpage, the following information will be gathered when a user visits an Event Group URL.
Event Group Name
Timestamp or the date/time the visit occurred
UTM parameters are available for all Events opened from an Event Group, regardless of whether the Event is embedded in an iframe.
When a user goes to an Event webpage from an Event Group, the Event Group Name and Event Name will be saved in a custom GTM event.
Field/Layout Updates
New
Object: Event Settings
Field Label: Send Email From
API Name: conference360__Send_Email_From__c
Data Type: Text(80)
Help Text: Email address to use as the sender for emails sent from this event. Only Org-wide email addresses are accepted. If an email address is added to this field and not set up as an Org-wide email address, the default selection will fall back to the current user.
Field Label: GTM Container ID
API Name: conference360__GTM_Container_ID__c
Data Type: Text (Length 30)
Help Text: Your Google Tag Manager container ID (e.g., GTM-ABC1234). Used to load GTM on event pages and embedded registration. Event-level setting overrides org-level GTM.
Description: Stores the Google Tag Manager (GTM) container ID for this event. When populated, this event-level setting overrides the org-level GTM configuration and is used by the Events webapp to load GTM on Event pages and embedded registration.
Object: Translation
Field Label: Event Group
API Name: conference360__Event_Group__c
Data Type: Lookup
Description/Help Text: Select the Event Group to translate. This lookup associates the translation record with a specific Event Group.
Field Label: Events Event Group Alternative Text
API Name: conference360__Events_Event_Group_Alternative_Text__c
Data Type: Text(255)
Description/Help Text: Enter the translated alternative text (alt text) for Event Group images.
Field Label: Events Event Group Description
API Name: conference360__Events_Event_Group_Description__c
Data Type: Rich Text Area(32768)
Description/Help Text: Enter the translated description for the Event Group.
Field Label: Events Event Group Name
API Name: conference360__Events_Event_Group_Name__c
Data Type: Text(80)
Description/Help Text: Enter the translated name for the Event Group.
Upgrade Instructions
Go to the Blackthorn Candy Shop to upgrade Events to the newest version.
Blackthorn has adopted Salesforce’s managed package installer to simplify the installation process. The installer will confirm that the correct Base Package and Payments versions are installed before upgrading Events.
For step-by-step instructions, click here.
Important Definitions
Breaking Change
A breaking change is a significant change that requires a package upgrade to see the update.
Off-Cycle or Hotfix Release
A hotfix is a release that corrects a problem that impacted extensive functionality.
BT Salesforce Release
The following applies to a Salesforce release.
Salesforce fixes REQUIRE a package upgrade to see and utilize the fixes/enhancements.
Only users with a System Administrator profile or the ModifyAllData system permission can install packages.
Webapp Release
The following applies to a Webapp Release (previously referred to as a platform release).
Webapp fixes/changes usually do not require updates to the Salesforce package.
These updates automatically apply to all customers; you cannot opt-out.
If you have any questions or need help with testing, please contact Blackthorn Support.