Skip to content
Back to Blog

How Do You Run Confex Registration in More Than One Language?

HB
Henrique B. 15 November 2026 · 7 min read
How Do You Run Confex Registration in More Than One Language?

To run confex registration in more than one language, give each language its own web address and translate the whole chain: the form, the checkout, the payment page, the confirmation email and the PDF ticket. Then store each person's choice so every later email follows it. Write the questions and the terms yourself.

Most multilingual registrations fail in the same place. The landing page is in elegant German, the form is in German, and then the confirmation arrives in English with a ticket that says "Admit One". Bill Murray had a better time in Tokyo. The rest of this piece is about closing that gap for a confex, where delegates, visitors and exhibitors arrive from several countries and each group fills in a different form.

What Has to Be Translated Before Registration Counts as Multilingual?

Seven things, and the form is only one of them. A delegate who picks French should stay in French from the first page to the badge in their hand, so count the links in the chain before you count languages.

  1. The event page, at an address you can put in a French email campaign without asking people to find a flag icon.

  2. The form: question labels, placeholders, every answer option, section headings, and the terms text with its tick box.

  3. What they are buying: price names, perks and add-ons. "Early Bird" is not a French phrase.

  4. Checkout and the payment page, including error messages. A declined card explained in the wrong language is a lost registration.

  5. The confirmation email, subject line included.

  6. The PDF ticket attached to it.

  7. Everything sent later: resends, payment requests, session booking emails.

Items five to seven are where the chain usually snaps, because they are produced after the visitor has left the page. The system has to remember the language, not ask the browser again.

Who Should Write the Translations: You or a Machine?

You, for anything a person agrees to or answers. Platform wording such as "Next", "Required" and "Card declined" can safely come pre-translated, but your questions, your answer options and your terms are yours, and a machine does not know that "stand" means a booth and not a posture.

Vendors split on this. idloom says it translates the text the platform controls (labels, validation messages, consent notices, receipts) in more than 20 languages, and leaves event descriptions and custom email copy to the organiser. Cvent works in a similar way according to the University of Colorado's Cvent guide: default labels and error messages arrive translated, while registration questions and session names are translated by hand. Webex Events goes further and offers machine translation through Google Translate across 35 languages, as a switch the organiser turns on. SpotMe keeps it manual and lets you export the strings to Excel for a translator.

My view: machine translation is fine for a welcome paragraph and risky for a consent question. If a Spanish visitor ticks a box whose wording nobody on your team has read, you have a record of agreement to a sentence you cannot vouch for. Pay a translator for the form and the terms. It is a few hundred words.

How Do Registration Platforms Compare on Languages?

The table below compares what each vendor's own help page or guide says, read on 15 November 2026. Each row rests on the single page linked above or below it, so treat it as a starting point for your own questions, not a verdict.

PlatformLanguages OfferedWho Writes the TranslationWhat Follows the Registrant's LanguagePage Date
idloomMore than 20; more on request through an account managerPlatform text supplied; organiser writes custom contentSite, form, confirmation emails and payment receipts26 May 2026
CventNot stated on the page readDefault labels supplied; organiser translates questions and session namesEvent website through a language selector; emails not covered on the page read22 September 2026
Webex Events35Organiser, or machine translation if switched onRegistration site, PDF tickets, confirmation emails, invoices and receipts30 August 2026
SpotMeNo maximum statedOrganiser, with an Excel export for translatorsRegistration page and forms; emails not covered on the page readNot shown
vFairsNo maximum statedOrganiser, one page per languageRegistration form fields and labels; emails not covered on the page readNot shown
eventcloudFive per event, each at its own web addressOrganiser or their translatorForms, checkout, payment page, attendee emails and PDF ticketsOur own product

The vFairs row comes from its help centre article on multilingual forms. Notice how many cells say "not covered on the page read" under emails. That is the question to put to any vendor in a demo: show me the confirmation a French registrant receives, subject line and attachment included.

Registration, Sorted

A Form for Every Audience. Answers on Every Badge.

Delegates, speakers and exhibitors each get their own registration form, and every answer flows to badges, emails and the Excel export.

See Event Registration

How Does eventcloud Handle a Confex in Several Languages?

An event on eventcloud offers up to five languages in total: its primary language plus four more, each at its own web address. The production languages are UK English, US English, Spanish, German and French. A visitor who picks German books in German from the form to Stripe's payment page, and their confirmation email and attached PDF ticket follow.

Because each ticket group has its own registration form, the translation work follows your audiences. Delegates, visitors and exhibitor staff each answer their own questions, and each form is translated question by question: labels, answer options, section headings and the Terms agreement. Price names, perks, add-ons, the success page and the wording on your ticket design are translated in the same way. Answers are matched by question, so translating or renaming a question never breaks the badge, the ticket, the attendee list or the Excel export that depend on it.

Two settings deserve ten minutes before you open:

  • Confirmation emails have a version per language. A new ticket group's confirmation starts in English, so publish a version for each language you offer before the first French delegate books.

  • Badges print in the event's primary language, or, with a switch, in each attendee's language. Choose on purpose. A badge is read by other people, so a single language across the hall is often the better call even when registration ran in four.

Arabic is coming. Need Arabic, or a language outside those five, for your event? Tell us which one and who it is for.

What Breaks on the Day If You Only Translated the Form?

The desk. Registration languages create onsite questions that no help page mentions, and they are easier to settle in a planning meeting than in a queue.

First, the list. If a dropdown asks for job function in four languages, you want one column in your export, not "Purchasing", "Einkauf", "Achats" and "Compras" as four different answers. Ask how choice answers are stored before you build the form, and prefer dropdowns over free text for anything you will count.

Second, the people. Check-in staff need to greet a delegate whose confirmation was in Spanish. They do not need to be fluent. They need a printed card with five phrases and the confidence to scan a QR code, which is the same in every language.

Third, the exhibitors. A stand team scanning visitors wants company and job title in a form it can read. If your confex registration types split delegates from visitors, make sure the questions that feed the badge are the same questions in every language, in the same order.

A multilingual registration is finished when a stranger can book in their own language on a phone and never once wonder whether they are still on the right website.

How Do You Test It Before You Open?

Book once per language, on a phone, with a real email address. It takes an afternoon and it finds almost everything.

  1. Start from the address you will put in that country's campaign, not from the home page.

  2. Read every question aloud to a native speaker. Dropdown options too.

  3. Trigger an error on purpose: leave a required field empty, type a phone number with letters in it.

  4. Go as far as the payment page and check the language there.

  5. Open the confirmation email. Read the subject line first, then the attachment.

  6. Print the badge that booking produces and look at it from two metres away.

How Many Languages Does Your Event Really Need?

Fewer than the sales team thinks. Look at last year's attendee list by country and translate for any market that sent a meaningful share of your visitors or that you are paying to reach this year. A UK confex with a strong German exhibitor base probably needs English and German. Adding French because the brochure looks more international creates a fourth set of emails to proofread and nobody to read them.

Start with the country question on last year's export. Count the top five countries, pick the languages that cover them, and brief the translator on the form before anything else.

Share This Article Twitter LinkedIn
Registration, Badges, Check-in

Run Your Next Event with No Meter Running.

Unlimited events, registrations and attendees on every plan, with badges, a self-service kiosk, check-in and lead retrieval on every seat.

Get in Touch. Let's Talk Events.