Skip to content
DocsSearch the docsEnglishBack to siteOpen console

Demographics report

Which country and city your visitors come from, on what device and which internet operator, from inside which app — and which value group your customers fall into. The menu calls it Demographics, the address bar says `/geo` — same page either way.

Where the screen is#

In the console's left menu, under the Reports group, choose Demographics. The route is /geo — if a colleague sends you a link to /geo, this is the page it opens.

The page heading is Demographics overview and it holds these blocks:

Block What it shows
Overview three headline tiles: Users, Sessions, Views
Users by country a world map, shaded by user count
Users by device a share bar of device category (desktop, mobile, tablet), with each category's share and user count beneath
Countries a table of country, users, sessions — with a Download CSV link
Cities a table of city, country, users
Internet operator & network each user's operator with network type, sessions, conversions, revenue and share
In-app browsers Instagram, Telegram, Bale and others: users, sessions and conversion rate
Customer value groups (RFM) five cards: New, Repeat, Loyal, At risk, Lapsed
Demographics: visitor country, city and device.
Demographics: visitor country, city and device.

The device card on this page reads exactly the same data as the Tech report; Demographics carries it alongside location so that answering "how many Iranian mobile users" does not need two screens.

Where country and city come from#

Nothing is asked of the browser and no location permission is requested. The collector looks the request's IP address up against a location database that lives on the collector itself and takes four things from it: country, region, city, and an approximate coordinate — the city centroid, or the country centroid when the city is unknown.

The full IP is not kept on the event

Only the /24 block of the address is retained — the first three octets and a zero. The IP itself is never written to the event table. That sets the ceiling on this report's precision: city level, not visitor level.

Three consequences worth knowing before you act on the numbers:

  • VPNs and proxies hide the real country. Those visits go into the Location hidden (VPN/proxy) row instead of the server's country; see below.
  • Mobile-carrier IPs often have no city. Carriers rotate large blocks between cities, so the share of "no city" is structurally higher on mobile traffic.
  • With no location database installed on the collector, this page stays empty. Country and city are never filled and the map renders blank — which is not the same as having had no traffic.

Country and city names are localised for display: countries through the browser's standard region list, cities through a curated table covering Iranian cities and the world's major ones, falling back to the English name for anything outside it. The stored value is identical either way.

Internet operator & network#

Internet operator & network shows which operator your users came through and on what kind of connection. Iranian operators carry the names people know — MCI, Irancell, Rightel, TCI, Shatel, ParsOnline, Asiatech and so on (written in Persian in the Persian console); everyone else shows their network's registered name.

Column Meaning
Operator the operator, with a network-type badge (Mobile internet, Home broadband, Business network, VPN, Proxy, Data center / hosting)
Users and Sessions as everywhere else
Conversions and Revenue conversions and revenue from that operator's users; revenue in the website's currency
Share that operator's share of all users

Above the table a share bar splits users by network type: how many came on mobile internet, how many on home broadband, how many behind a VPN or proxy. It comes from the network lookup made on every visit, so it is filled for past ranges too — nothing to install or switch on.

Location hidden (VPN/proxy)#

A visitor behind a VPN, proxy, Tor or a data center presents the server's country, not their own. AdPix does not count those visits as Germany or the Netherlands: the Countries and Cities tables give them a separate row, Location hidden (VPN/proxy), and the map leaves them out. A note under the Countries title says what share of users is hidden.

For an Iranian audience this is not a small number

The hidden share on Iranian traffic is usually high. To see where those users really are, look at Internet operator & network: an Iranian operator that is not behind a VPN reports the right country.

In-app browsers#

When someone taps a link to your website inside Instagram, Telegram, Bale, Eitaa, Rubika, WhatsApp and similar apps, the page opens inside that app. The In-app browsers table shows how many Users and Sessions each app brought and their Conversion rate — which social network actually sends buyers. Above the table is the share of users who opened the website in a regular browser.

  • An app the tracker can't name, but that opened the page in a WebView, is listed as Other apps (WebView).
  • Telegram on iOS opens pages in a Safari view and can't be told apart from Safari; those users are not in this table.
This section collects from the update onwards

The app is detected from the full user-agent string, which was never stored before. Data starts on the day the updated tracking code is live on your website, and the section says Collecting since that date. Until then it shows "No data yet"; earlier visits never appear here.

Customer value groups (RFM)#

Customer value groups (RFM) places every customer — anyone with at least one purchase event — in one of five groups by order count and how recently they last bought:

Group Definition (default values)
New one order, in the last 60 days
Repeat two or more orders but fewer than 3, the last one in the last 60 days
Loyal 3 or more orders, the last one in the last 60 days
At risk last order 60 to 180 days ago
Lapsed last order more than 180 days ago

Each card shows the group's customers, its share of all customers, Revenue and Avg order, with the group's actual thresholds written underneath. A customer is one resolved person — if you send their email or phone with identify, purchases from several devices count as one customer. The groups are built from recorded purchases, so past ranges are filled too.

If purchases were recorded in more than one currency, amounts are never added across currencies and a note above the cards says which currency the amounts show — the same rule as the E-commerce report.

What the three headline numbers count#

The tiles use the same definitions as the rest of the reports:

Tile Definition
Users distinct visitor identifiers seen in the selected range
Sessions distinct sessions; events that carry no session are not counted
Views page_view events only — not every event that fired on the page
A user here means a browser, not a person

Demographics and Tech count users by each browser's anonymous identifier, not by the unified identity AdPix builds from email and phone. Someone who visits on a phone in the morning and a laptop at night is two users on this screen. For the unified figure, use the reports built on identified users; the stitching logic is in How AdPix identifies visitors.

Second point: server-side events carry no session, and their country is only populated when your server-to-server call passes the visitor's IP in context. Your server's own IP is not a substitute for the visitor's.

What never reaches this screen#

Three filters apply before data reaches the report, all of them deliberate:

  • Test traffic never appears in reports.
  • Internal IP blocks listed in Admin → Website details → Traffic filtering → Excluded CIDRs are dropped at collection time. If your office range is listed there, it is counted in no country at all.
  • A browser holding the exclusion cookie — the one you set for yourself so the team's own visits stay out.

The Countries table returns at most 250 rows and the Cities table at most 200, both ordered by user count. Rows with no country are dropped from the first, rows with no city from the second.

Comparing with a previous period#

Turn Compare on in the date-range picker and each of the three headline tiles gains a percentage change underneath: green with ▲ for growth, red with ▼ for a fall, measured against the same three numbers over the second window.

Comparison lands on the headline tiles only. The map, the device card and both tables always reflect the primary range. To see how countries shifted between two periods, pull each range separately and put the two CSVs side by side. The four comparison modes are covered in Date ranges and comparison.

CSV export#

The Download CSV link under the Countries table produces a file with three columns — country, users, sessions — up to 5,000 rows. The range and website selected on screen are applied to the file as well.

Two differences from what you see:

  • Cities are not in the file. Location export is country level only.
  • The country arrives as its two-letter ISO code (IR, DE), not as the localised name shown on screen.
Read the file by column name, not column position

Column order in this export is not guaranteed and may differ between two downloads. If you feed the file to a script or a dashboard, resolve columns from the header row. And if the range holds no rows at all, the file comes back completely empty — not even a header row.

If the page is locked#

Demographics is included in both plans by default, but a platform administrator can remove any feature from a plan. If you get the premium-feature message instead of the report, check the website picker at the top of the page first — you may be looking at a different website. The full explanation is in A feature is greyed out.

Frequently asked questions#

Why does the menu say Demographics when the URL is `/geo`?

They are the same page — only the menu name and the route differ. The route is /geo, the page heading is Demographics overview, and the console's own search finds it under geo, country, city and demographic alike.

Where does the country come from, and is the full IP stored?

From the visitor's IP address, looked up against a location database that sits on the collector itself. The full IP is never written to the event table — only country, region, city and an approximate city-centre coordinate, plus the /24 block of that IP.

Why don't the country rows add up to the headline number?

Two reasons. Rows with no country are dropped from the table, and the table is capped at the 250 busiest countries. And one visitor can legitimately appear from two countries within the range — travel, a VPN, a mobile network — counting in both rows but only once in the total.

Why is the city empty when the country is not?

The location database almost always resolves a country but frequently cannot resolve a city, especially on mobile-carrier and corporate IP ranges. Events with no city are excluded from the Cities table, but they are still present in the Countries table and in the headline numbers.

Why do some of my users have "Location hidden"?

They were behind a VPN, proxy, Tor or a data center, so their IP shows the server's country, not theirs. AdPix puts those visits in a separate row instead of the server's country, so Germany and the Netherlands don't look bigger in your report than they are.

Why is the in-app browsers table empty for past months?

The detection reads the full user-agent string, which was not stored before this release. Data starts on the day the updated tracking code went live on the website, and that date is shown above the table.

Build with the APIUnderstand where revenue comes from.
Was this page helpful?