Data Dictionary / Translations

The data dictionary was implemented to give everyone the ability to register through Blackthorn Events! Currently, we have enabled many languages and will be adding more soon.


Permission Sets and Licensing for Data Dictionary

To use the Data Dictionary feature, you must have a Blackthorn Payments license, as well as access to the following fields:

  • Create/Read/Update - Data Dictionary Group
  • Create/Read/Update - Data Dictionary Entry

Data Dictionary Demonstration

By default, whichever language your browser is using, Blackthorn Events will automatically use. For example, if your browser location is set to Australia, the event will switch to English (Australia) instead of English (United States).


Data Dictionary Update

The Data Dictionary feature will work with the new Checkout process, allowing other languages to be used as they are in the rest of the Events app.

This is enabled by default, and you can change languages from the language selector in the top right corner of the event page:

  • Note: When iframing the events page, the language selector will be disabled, as Blackthorn Events will rely on the host page to determine the language to display.

Override Labels

If for some reason there is a label or button that is not translating correctly (we are using Google Translate, so it's not always correct) or you just want to override a value with your own label, you can manually define the correct label for your event.


Data Dictionary Group Visibility

To show the Data Dictionary Group field on the event settings, navigate to the Event Settings object, and add the Data Dictionary Group field on your page layout.

Please follow the instructions below:

  1. Create a Dictionary Group related to an Event Setting record

Alternatively, you can create a Dictionary Group on an Event Group record. This will add the Dictionary Group to all events within the Event Group. The Data Dictionary Group on the Event Setting record will take priority over the Data Dictionary Group on the Event Group.

  1. From the Dictionary Group add a new Data Dictionary Entry
  1. Select what language/locale you'd like to change; for this example we will select English.


Language Support

In the Language / Locale picklist, we do not support all languages available to pick from at this time. At the bottom of this page, you will find a list of all languages that we do support.

  1. Now, we're prompted with a "Key" and "Value," this is where it gets fun!
  • First, click on this Google Document - this will give you all the information of what the translations are.

  • Second, If you are looking for a specific key you want to override, click on the Event Page URL, and swap the language in the domain with "debug" to see all the keys on a specific Event. This will show you a debug version of the event, with each field identified. Essentially swap '' with ''. See images below.

  • Here are some of the most frequently used Data Dictionary entrees and their keys:
    Add Attendee - ACT_ADD_ATTENDEE
    Done button - ACT_DONE
    Free - LBL_FREE
    Registration button - ACT_REGISTER
    You are registered! - MSG_REGISTRATION_CONFIRMED

  • Since English is our primary language we selected, we will use that for our source translation. After that, we can select any word or phrase to replace an action with. For this example, we will use the "Complete" field.



In the Key definition, use capital letters.

  • Now that we've selected that, we should now see this as the expected result:

However, if we were to change "Complete" in the Value field to "Test"... this would be the result...

Removing the Paid/Free Verbiage


Please Note: This currently only applies to the Event Group URL

There is currently two ways to remove the "Free" and "$XX.XX" pricing.

  1. Reach out to Blackthorn Support to disable this throughout the entire org

  2. If you would like to only remove the "Free" verbiage from the event registration, you can do so by setting the Value field to a: Space bar entry

Going back to this Google Document, we can find the key we're looking for. In this case, let's remove the "Free" from the Subtotal column. The key we will be using is LBL_SUBTOTAL. Next, for the Value field, simply click the space bar to enter in an empty value.

And voila! Now, we can see that the text has been removed from the page.

With the Data Dictionary, it is completely up to you on what you'd like each field to represent in your checkout process.

Using Merge Fields with Data Dictionary

While we do not support merge fields in data dictionary out of the box, we do have ICU formatted messages that by default gives you the ability to insert dynamic text within the message. Syntax is {variable}.

Click here for more information on Salesforce Supported ICU Formats.

Use Cases

  • Use Case 1: When overriding the AttendeeLink Personal Welcome Message (Key = MSG_ATTLINK_PERSONAL) include {name} in the Value field which will dynamically pull in the Attendee's first Name.
    • Ex: Welcome {name}. Thank you for your interest in the upcoming event.
  • Use Case 2: When overriding the 'Starting from price' on the Event page (Key = LBL_STARTING_FROM_PRICE), include {price} in the Value field which will dynamically pull in price.
    • Ex: Price starts at {price}!
  • Use Case 3: When overriding the 'Registration Canceled' message on the AttendeeLink (Key = MSG_REGISTRATION_CANCELED), include {name} and {date} in the Value field which will dynamically pull in Event Name and Date.
    • Ex: Your registration to {name} on {date} is canceled.


On Event Settings, we have a couple fields to control language translations.

  1. Language Selector: This will allow/disallow the attendee's ability to change the event to a different language. The language selector will not be available when using the Preview button on an event record.
  1. Source Language: This is used to define what language the events are created in. This helps Google Translate convert text into other languages. If the event itself is created in English (description, event name, etc.), then Source Language should be English.

  2. Target Language: This field is currently not being used.

When an attendee loads an event page, the default language they see will be based on their IP. Their IP will determine what country they are in, and will display the assosciated language.

  1. If there is a language code defined in the URL (Ex:, where es is the language code), it will display the event in Spanish.
  2. if there is no language code in the URL (, detect the user's IP and redirect to a URL with the detected language code.

Supported Languages

We currently support 31 languages and are actively adding more. The below list is all languages that we properly support. If a language is chosen that we do not currently support, the event will default to English.

  1. English
  2. Arabic
  3. Danish
  4. German
  5. Spanish
  6. Finnish
  7. French
  8. Haitian
  9. Creole
  10. Hindi
  11. Hmong
  12. Indonesian
  13. Italian
  14. Japanese
  15. Korean
  16. Dutch
  17. Norwegian
  18. Polish
  19. Portuguese
  20. Romanian
  21. Russian
  22. Somali
  23. Swedish
  24. Thai
  25. Vietnamese
  26. Chinese (Simplified)
  27. Chinese (Traditional)
  28. Czech
  29. Hungarian
  30. Dutch
  31. Turkish

Did this page help you?