Someone from Cologne opens your event page and sees German. Not just the buttons and the confirmation e-mail, but also the description you wrote in Dutch. You switch on the languages your visitors speak; the rest follows by itself.
Tick the languages
In Settings → Languages. One tick per language, and your primary language stays the one you write in.
Your texts follow
Event name, description, ticket types and your own e-mail texts move to the other languages automatically.
The visitor picks
They get their browser language by default and can switch with one click on a flag.
You do not have to translate anything or keep anything in sync. You only say which languages your visitors speak.
In Settings → Languages you tick who you want to serve. Everything that comes from the platform itself — buttons, forms, e-mails, error messages, the order confirmation — is already fully available in that language. Nothing is invented on the fly: a language can only be switched on once it is completely translated, and a test enforces that.
Whoever arrives gets their browser language — provided you offer it. Click a flag and that choice wins, and we remember it; when they are logged in, their preference travels to their next device. Offer just one language and nobody sees a language switcher at all.
This is the part most platforms leave to you. Change an event description, a ticket type, a menu or the text of your confirmation e-mail, and a translation pass automatically runs for the languages you offer. Whatever you refine yourself wins for good.
Not a row of flags hiding half-finished translations. Every language below is fully populated before it can be switched on — including the error messages in the middle of checkout.
The dashboard and the admin panel stay Dutch and English. This is about what your visitor sees.
Frisian is the second official language of the Netherlands — not a dialect, but a language with its own law and its own spelling. More than half a million people speak it. For a brass band in Drachten, a village fair in Wommels or a handball match in Franeker, Dutch is not automatically the language of the crowd.
Commercially, Frisian is not a smart choice: it will never bring the visitor numbers to carry a business case. We did it anyway, for the same reason we started in Drenthe — a region deserves to be addressed in its own language, even a small one. The set is as complete as the German one: every visitor text, every e-mail, every error message.
Frisian deliberately follows Dutch date and price formatting, because that is what a Frisian reader expects.
Read the article in FrisianNot every organiser needs this. These do.
Around Enschede, Venlo or Terneuzen a good share of your audience comes from Germany or Belgium. A Dutch-only event page is not a detail then but a reason to drop out — or to e-mail you asking whether that ticket went through.
Your programme is English, your speakers are English, your delegates come from ten countries. Switch on English and German and you do not have to write your programme texts twice.
You advertise abroad on purpose. Every language you switch on gets its own web address with hreflang, so Google treats the German version of your event page as a genuinely German page.
A village festival, a brass band, a local match. Your audience lives around the corner and speaks Frisian — then that is the language you invite them in, not the Dutch of a ticketing platform from the big city.
A village festival near the German border switching on Dutch, German, English and Frisian.
Better clear now than after you have switched.
The platform texts are written by hand; your own texts are done by a translation engine. That is why every non-Dutch page and e-mail carries a short note saying the text was translated automatically and that the Dutch version prevails in case of differences. You can refine any translation yourself; empty a field and the engine picks it up again.
The screen where you build your events and review your orders exists in Dutch and English. The eleven languages are about the side your visitor sees — that is where the difference counts, and it spares you a dashboard that feels half translated.
Rental and membership terms stay in the source language. What a visitor ticks has to be exactly the text recorded as accepted; a translation alongside it would mean they read something other than what ends up in the records. We are not taking that risk.
Do you organise events with MijnEvent? Enter your e-mail address and we'll send a login link for your most recent organisation.
No account yet? Sign up for free
You're viewing the English version. Looking for the Dutch page?
Ga naar Nederlands