Early accessBy invitation, and the SDKs aren't published yet.Ask for an invitation
Skip to Content
Docs

Countries

Lyrelog works out the country from the address a batch came from, at ingest, and never stores the address.

When a batch arrives at https://ingest.lyrelog.com, the server looks up the sender's IP address in a local copy of DB-IP's free country database and stores only the ISO country code on each event of the batch (country). The address itself is never kept, and no third-party service is called.

A client can't set country: sending it is rejected as an unknown field.

Events your backend sends (Node, Python, Go) carry the country of your server, not of the person. The same goes for events relayed through a proxy of your own: only Lyrelog's own front server is trusted for X-Forwarded-For. Send events from the device when the country matters.

Where a person is

The dashboard places a person by the country of their events, and falls back to the region of their device's locale (es_ES is Spain) for events without one. The map on the explorer, the people list, the sessions list and the Country filter and breakdown all use that rule.

The map credits "IP geolocation by DB-IP" (CC BY 4.0).

On this page