Overview
Two different things reach an attendee through AttendeeLink after they interact with an Event, and they are configured separately.
- A Post-Registration Form is shown immediately after checkout, before the event happens. Use it to collect anything you did not ask for during registration: dietary needs, session preferences, travel details.
- A Post-Event Survey is shown after the event has finished. Use it to collect feedback.
Until the September 2026 release the two shared a single title. They are now separate.
Titles
Each surface has its own title, and each can be reworded and translated independently through the Data Dictionary.
| Surface | Data Dictionary key | Shipped default |
|---|---|---|
| Post-Registration Form | MSG_POST_REG_FORM_TITLE |
"Please take a few moments to complete this form." |
| Post-Event Survey | MSG_SURVEY_TITLE |
"Thank you for attending this event. Please take a few moments to answer our survey." |
Before the September 2026 release, MSG_SURVEY_TITLE drove both surfaces. That meant the survey wording, which thanks the attendee for attending, appeared on forms shown before the event had happened.
Both keys ship translated in all 37 supported languages, so no action is needed if you rely on Blackthorn's translations.
If you had overridden or translated MSG_SURVEY_TITLE yourself, that wording stays on your Post-Event Surveys and is unaffected. It no longer applies to Post-Registration Forms, which now show the shipped default instead. To restore your wording on forms, add a Data Dictionary entry for MSG_POST_REG_FORM_TITLE.
To find out whether this applies to you, any result means you have an override that stopped applying to forms:
SELECT Id, bt_stripe__Data_Dictionary_Group__c, bt_stripe__Locale__c
FROM bt_stripe__Data_Dictionary_Entry__c
WHERE bt_stripe__Data_Dictionary_Values__c LIKE '%MSG_SURVEY_TITLE%'
For how to create Data Dictionary Groups and Entries, see Data Dictionary.
When a Post-Event Survey closes
There is a field on the Event record, Post Event Survey Expiration (Days), intended to close a survey a set number of days after the event ends.
While an Event is published, its Post-Event Survey stays open indefinitely and the expiration value is ignored. An attendee can still open and submit the survey however long ago the event ended.
This is deliberate and temporary. An earlier release enforced the cutoff on published events, which closed surveys for organizers who needed them open for longer, so the behavior was reverted. A supported way to configure the cutoff is being built; until then there is no per-org way to turn the old automatic close back on.
The expiration value does apply once an Event is no longer published:
- Field has a value. The survey stays reachable until the event end date plus that number of days, then stops accepting responses.
- Field is empty. The survey stops being reachable as soon as the event is unpublished. Attendees opening the link see a page saying the event is not available.
Closing a survey today
Because the expiration field does nothing on a published event, the only way to close a survey is to take the event offline, or to remove the survey from the event.
Taking an Event offline also takes down its public event page and its ticket and check-in links. It is not a clean switch for the survey alone. If the event is still selling tickets or running check-in, remove the survey from the event instead.
A note on the field name
The field is stored as conference360__Post_Event_Survey_Expiration_Date__c, but it holds a number of days, not a date. A value of 14 means fourteen days after the event ends, not the 14th of a month.
What to expect after the September 2026 release
- Post-Registration Forms show the new shipped title unless you add an entry for
MSG_POST_REG_FORM_TITLE. - Post-Event Surveys are unchanged, including any wording you had customized.
- Survey expiration behavior is unchanged from 20 August 2026, when the revert shipped as an off-cycle fix. Nothing changes on the September release date.