Default Language Field
Sets the account's interface language. Offered in visitor mappings and in the owner-account part of exhibitor mappings.
The value lands on the account's Default Language field, stored as a two-letter ISO 639-1 language code (e.g. en, de, fr).
Behaviour
The field resolves the incoming source value using the strategy configured by the Language Matching option. Three strategies are available:
-
Direct code — takes the source value as a two-letter ISO 639-1 code, no table involved
-
By country ISO — maps a country ISO code to that country's primary language, using the fixed table below
-
By Aventri code — translates Aventri-specific language identifiers, using the fixed table below
If the resolved language code is not enabled on your ExpoPlatform environment (the set of available languages is configured per environment), or if the source value can't be resolved at all, the system default (English) is used — no error, no skip.
Options
|
Option |
What it does |
Default |
|---|---|---|
|
Language Matching |
The resolution strategy: Direct code, By country ISO, or By Aventri code. |
Direct code |
When synced visitors end up with English unexpectedly
Two things to check:
-
The source value appears in the relevant table below
-
The target language is enabled for your environment
If either isn't true, the fallback to English kicks in silently.
Fixed lookup tables
Only the combinations listed here can be mapped. Any source value not listed resolves to nothing and the system default is used.
By country ISO
|
Source country code |
Resolved language |
|---|---|
|
DE, AT, CH |
German (de) |
|
FR |
French (fr) |
|
IT |
Italian (it) |
|
ES |
Spanish (es) |
|
PT, BR |
Portuguese (pt) |
|
NL, BE |
Dutch (nl) |
|
RU |
Russian (ru) |
|
CN, TW, HK |
Chinese (zh) |
|
JP |
Japanese (ja) |
|
KR |
Korean (ko) |
|
SA, AE, EG |
Arabic (ar) |
|
TR |
Turkish (tr) |
|
PL |
Polish (pl) |
|
CZ |
Czech (cs) |
|
GB, US, AU, CA, IE, NZ, SG, IN, ZA |
English (en) |
By Aventri code
|
Aventri code |
Resolved language |
|---|---|
|
eng |
English (en) |
|
ara |
Arabic (ar) |
|
bah |
Malay (ms) |
|
cat |
Catalan (ca) |
|
chs, cht |
Chinese (zh) |
|
cze |
Czech (cs) |
|
dan |
Danish (da) |
|
dut |
Dutch (nl) |
|
fin |
Finnish (fi) |
|
fre, fca |
French (fr) |
|
ger |
German (de) |
|
gre |
Greek (el) |
|
heb |
Hebrew (he) |
|
hun |
Hungarian (hu) |
|
ita |
Italian (it) |
|
jap |
Japanese (ja) |
|
kor |
Korean (ko) |
|
nor |
Norwegian (no) |
|
pol |
Polish (pl) |
|
por |
Portuguese (pt) |
|
rom |
Romanian (ro) |
|
rus |
Russian (ru) |
|
slo |
Slovak (sk) |
|
spa |
Spanish (es) |
|
swe |
Swedish (sv) |
|
tha |
Thai (th) |
|
tur |
Turkish (tr) |
|
ukr |
Ukrainian (uk) |
|
vnm |
Vietnamese (vi) |
Which strategy for which integration
The By Aventri code strategy exists specifically for Aventri feeds, which deliver their own language identifiers. Other integrations typically use Direct code (when the source carries ISO 639-1 codes) or By country ISO (when the source carries country codes instead).