XOM does not currently ship a map surface. No mapping library is bundled with the application and there is no map view in the product. What does exist is a set of location-aware fields and two registered but inactive mapping extension slots. This page describes that state accurately so it is not mistaken for a shipped feature.
01Where location data already appears
Three parts of the platform are location-aware today, none of them cartographic.
User demographics. The user document carries a country field, captured at registration alongside date of birth and gender. It exists to support audience analysis and ad reporting.
Ad targeting. Every ad creative carries a targeting block with a geographies list. The value is expressed as region strings — global, or a set such as US, EU, UK — and the feed's advertisement component filters candidate creatives against the viewer's profile before selecting one. This is list matching against named regions, not coordinate or radius targeting.
Post analytics. The per-post analytics view includes an audience-by-country breakdown in its demographics tab, rendered as a distribution rather than plotted on a map.
02The registered mapping extensions
XOM's Media Console bridge maintains a catalog of controllers and third-party extension slots. Two entries in that catalog are mapping-related:
- Google Mapping API, described as integrating Google Maps and location services for geolocation and navigation features. Status:
offline. - Baidu Geolocation Mapping, described as providing geolocation and mapping services from Baidu's geographic data. Status:
offline.
The catalog is a registry of integration points with a status flag per entry. An offline status means the slot is declared and not connected — the majority of entries in the catalog carry that status. Registering an extension does not provision credentials, add a dependency, or make an API call.
03What would be required to ship this
Adding a map surface to XOM is a provider decision before it is an engineering one. The application is a static export that talks to Firebase directly from the browser, so a mapping SDK would run client-side with a publishable key, and any per-request cost would be incurred on page load rather than metered server-side. Beyond the provider choice and its licensing terms, enabling geolocation would raise consent and disclosure questions that the current country-level capture does not: browser geolocation is a permission prompt and a materially different privacy posture from a self-declared country on a profile.
Until those decisions are made, the accurate description of XOM's mapping capability is that the integration points are reserved and the capability is not implemented.