Skip to main content

How to Manually Translate your Site

Written by Benjamin Dell

Use Content Translations to change standard wording for your event. For example, you can call speakers "Presenters" or categories "Tracks" to match the terms your audience uses.


​

Change a phrase

  1. Sign in as an event organiser and open your event dashboard.

  2. Go to Event Settings > General > Content Translations.

  3. Use Search translations, or open Filter records, to find the phrase you want to change.

  4. Enter your wording in the Translation field and select Save beside that phrase. Repeat for other phrases.


​

Content Translations with Export and Import controls, editable Translation fields and per-row Save buttons


​

Saved custom wording is highlighted in green. Review your public event site after saving to check the wording in context.


​

Export wording to a spreadsheet

  1. Open Event Settings > General > Content Translations in the source event.

  2. Clear the search and category filter if you want all phrases. Export uses the current search and filters.

  3. Choose Export, leave Download Now selected, then choose Export in the confirmation. HeySummit emails you a link to the CSV when it is ready.

  4. Open the CSV in a spreadsheet. Keep Translation key unchanged. Use Default wording for reference and enter your wording in Translation.

  5. Keep placeholders such as {} and any merge fields exactly as they appear in the default wording. Save the file as CSV.


​

The Translation column contains event-wide custom wording already saved in the source event. Blank cells do not automatically contain the default wording or language translation, so fill in the phrases you want to import.


​

Import wording into an event

  1. Open Content Translations in the destination event and choose Import.

  2. Leave Replace existing custom wording? off to preserve wording already saved in this event. Turn it on only when you want the non-blank translations in your file to replace existing custom wording.

  3. Select your CSV file and choose Next.

  4. Map Translation key and Translation to their matching CSV columns. The exported Default wording column is for reference and does not need to be mapped.

  5. Review the linked columns, then choose Import to submit the request.


​

Importing translations with Replace existing custom wording switched off and its keep-existing help text


​

Check the result

Imports run in the background. HeySummit emails you when processing finishes, with a link to the import summary. Review any row errors, then check the public event site to see the wording in context.

  • Unknown or unavailable translation key: use keys from a current Content Translations export or the importer's CSV template. Do not rename them.

  • Keep the placeholders from the default wording unchanged: restore the placeholders or merge fields in the affected phrase, then retry the corrected rows.

  • A phrase did not change: check whether its Translation cell was blank or the destination already had custom wording while replacement was off. Skipped rows can be reported as successful.


​

What the import changes

  • Only event-wide system wording is updated. Page-specific wording overrides stay unchanged.

  • Blank translations are skipped, even when replacement is on. They do not erase existing wording.

  • The import does not change the event's language or translate page copy, talk titles, descriptions or speaker biographies.

  • Event-wide legal wording is not included in this import.


​

Choose the event language

To choose the default interface language, go to Event Settings > General > Date, Time & Language, choose Language and select Save. Event-specific wording overrides apply to the event's base language. Attendees who choose another language see the standard interface wording for that language.


​

Translate your own content separately

These settings change standard interface text. They do not automatically translate organiser-written page copy, talk titles, descriptions or speaker biographies. For an overview of the language settings, see Translate your event site.

Did this answer your question?