Interpreting traffic from Myanmar
Myanmar (MM) uses Burmese (my-MM) in its own script, and is notable for a long-running encoding split between the non-standard Zawgyi font and proper Unicode, which can corrupt text rendering. This page explains how to read an 'MM' country signal, why the Zawgyi/Unicode issue and mobile-first access matter, and how to separate machine traffic from human Myanmar visitors.
Burmese (my-MM) and the Zawgyi versus Unicode split
Myanmar's official language is Burmese, written in the Burmese script (locale my-MM). For years many devices used Zawgyi, a non-standard font encoding that maps Burmese code points differently from Unicode. Content authored in one and viewed in the other renders as garbled text.
The country has been migrating to Unicode, but legacy devices persist. Author content in Unicode and be aware that some MM visitors may still hit rendering issues; check Accept-Language for the my tag.
Mobile-first access and machine traffic
Myanmar's internet adoption came largely through inexpensive smartphones, so the MM human segment is strongly mobile-first and tied to mobile carriers. Coarse region detail is approximate.
Separate machine traffic before reading MM as audience, since cloud hosting and VPN exits can resolve to Myanmar and shift the apparent country.
- Locale is my-MM in the Burmese script
- Zawgyi versus Unicode encoding can corrupt Burmese rendering
- Mobile-first access; coarse region detail is approximate
How it appears in analytics and logs
An 'MM' country value means the connecting network resolved to Myanmar at the edge. Burmese (my-MM) is dominant, but legacy devices may use the non-standard Zawgyi encoding instead of Unicode, so Burmese text can render incorrectly even when the language is right.
Diagnostic use case
Read a Myanmar country segment for coarse trends while accounting for my-MM Burmese, the Zawgyi-versus-Unicode encoding problem that affects rendering, and predominantly mobile access.
What WebmasterID can help detect
WebmasterID classifies bot versus human server-side, so an MM segment can be read with crawlers separated, and locale signals can be checked against a Burmese-script audience.
Common mistakes
- Authoring Burmese in Zawgyi rather than Unicode, breaking rendering for many readers.
- Assuming Burmese text always renders correctly regardless of device encoding.
- Counting cloud-hosted or VPN-exit requests as Myanmar human visitors.
Privacy and accuracy notes
WebmasterID treats a Myanmar country signal as a coarse, privacy-safe edge estimate — never an exact location and never derived from raw client IPs stored in your analytics.
Related pages
- Interpreting traffic from Thailand
Thailand has a highly mobile- and social-first internet culture with heavy in-app browsing, so a 'TH' country value sits behind layers of mobile and app routing. This page explains how to read the Thai country signal as a coarse edge estimate rather than a precise location.
- Mobile carrier geo skew
Mobile carriers route traffic through gateways and carrier-grade NAT that may register IP addresses in a different region than the subscriber. This page explains why mobile traffic skews the apparent country and how to read mobile-heavy geo data honestly.
- Language vs country targeting
Language and country are distinct signals: Accept-Language reflects a browser's language preference, while edge country reflects the connecting network's location. This page explains why conflating them produces poor targeting and where hreflang belongs.
- Privacy-first analytics
Coarse, privacy-safe geo without raw IPs or fingerprinting.
Sources and verification notes
- Unicode — Myanmar script encodingStandard Unicode Myanmar block; Zawgyi is a non-standard alternative.
- W3C — language tags (BCP 47 / my-MM)
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.