All Collections
Event Management
Talks
Running a single event across multiple languages, or time zones
Running a single event across multiple languages, or time zones
Benjamin Dell avatar
Written by Benjamin Dell
Updated over a week ago

Scenario

Planning an event on HeySummit and know you will have attendees from multiple timezones. You are wondering how to best set up this event.

Quick Start

This situation is much better handled using multiple events (i.e. one for each timezone), rather than within one using categories. With the latter, the event will need to have separate categories to group tickets, and sessions.

To create a separate event for each timezone, you can create one event, clone it, and then set global translations to another language.

Categories

For best email results in an event crossing multiple timezones, we strongly recommend having only the "We’re starting now!" and "You’re in!" email templates active under Events > Emails from your dashboard. The rest of the email templates should be marked inactive.

Next, under Content > Categories you can set up the categories (i.e. regions, languages, and/or topics) which you can later attach to your sessions. You’ll want to create a category for each unique track your users may want to register for. You can attach multiple categories to one session, e.g. language and topic.

This example shows a setup where the event will have Talks in English, and separate versions with the webinar dubbed in Spanish and Russian respectively, but there are a lot of ways you can use Categories to group your sessions.

Categories can help sort and separate:

  • Language-specific session titles and descriptions (i.e. for each instance of each talk)

  • Language-specific video configurations (i.e. for audio translation dub or subtitles to be added to your video within your chosen provider)

  • Language, or region-specific ticket permissions

Ticketing

Each ticket can be set to restrict an attendee to sessions in the desired category. For the above example, each English Ticket you set up would “Restrict access” to the "Event Name (Eng)" Category. Check out our help doc on setting up Ticket Permissions here.

Did this answer your question?