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.

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).

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

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
  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.
  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 would like to know which "Key" fields are which, you can click on this event and will see a debug version of the event, with each field identified.

  • 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.

Also supports merge fields. Syntax is {variable}. Definitions of available fields coming soon.

Capital letters and merge field example (bottom right)

  • 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 Free Verbiage

If you would like to remove "Free" from the event registration, you can do so by setting the Value field to: 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.


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

  1. Source Language - this controls what language the event is created with.
  2. Target Language - as of Events 2.73, this field is no longer used. This will be removed in a future package.

The rules to decide the final language shows to the user:

  1. If there is a language code in the URL (**/es/**281eJYf, where es is the language code), show the events with the language code
  2. if there is no language code in the URL (, detect the user's browser language and redirect to a URL with the detected language code.

If Source Language is the same as the language code in the URL, then the events are not translated. If they are different, events will be translated from Source Language to the language code in the URL.

Updated 15 days ago

Data Dictionary / Translations

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.