A festival near the border, a parade with German visitors, a conference with international speakers, a village fair with Polish seasonal workers: the moment even one visitor doesn't speak Dutch, a single-language ticket page starts to hurt. As of today MijnEvent solves that for you. You tick which languages your visitors speak; the rest happens by itself.
You can choose from eleven languages: Dutch, Flemish, English, German, French, Spanish, Italian, Polish, Ukrainian, Simplified Chinese and Frisian.
One setting, the whole sales side follows
In Settings → Languages for your visitors you tick the languages you offer and pick your primary one. That's it. Every language you enable is complete from the very first second: ticket pages, checkout, module storefronts, system e-mails, validation and error messages — every platform text is already there. "Automatically available" really means automatic: there is no translation backlog waiting for you.
The entire setup: tick languages, pick a primary one, save.
If you offer just one language — like most organisers — nothing changes at all. No switcher, no English sneaking in: your page stays exactly as it was.
Visitors don't have to configure anything
A German-speaking visitor opening your event page simply gets it in German — MijnEvent looks at the browser language, limited of course to the languages you offer. Switching is always possible via the language switcher at the top of the page. That choice is remembered for a year, and for logged-in visitors the preference even travels along to their next device.
The same event page as a non-Dutch visitor sees it — including dates and price formatting in that language. Switching is done with the flags at the top right.
It goes beyond the words alone: dates ("Samstag, 14. November") and amounts ("75,00 €") follow the chosen language too. And because the switcher only appears when there is genuinely something to choose, the page stays calm for everyone who is offered a single language.
FAQs: translate with one click
Your own content is yours to write, but not yours to translate: event descriptions, ticket types, menus, courses and your own e-mail texts are carried along automatically into every language you switch on. Every item has a Translations button where you can refine a sentence yourself — and what you enter there wins for good. Frequently asked questions work the same way: in Dashboard → FAQ you'll find a tab per language, and every question that doesn't yet exist in all your languages gets a translate button. One click and both the question and the answer are translated automatically. The translation gets its own "AI-translated" badge and stays fully editable; a variant you polished by hand is never silently overwritten.
Language tabs above the list; the globe button translates a question into the languages that are still missing.
On your public pages, visitors then automatically see the questions in their own language, with a graceful fallback to your primary language while a translation doesn't exist yet.
Who is this for?
Anyone with visitors crossing a border: festivals and parades near the border, events in tourist regions, sports events with international participants, conferences. German and French for the border region and tourists, Polish and Ukrainian for the large groups of migrant workers, Spanish for international visitors — and Frisian, because a Frisian organiser should simply be able to address their visitors in Frisian.
One thing we say plainly: the translations are machine-made. 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 if anything differs.
Automatically translating event descriptions and ticket type names is the obvious next step — we're working on it. Until then: everything that comes from the platform is already multilingual, and everything that comes from you stays yours.
Enable your first extra language under Settings → Languages for your visitors — and if anything looks off, we'd love to hear it.
