Web Analytics
Countly
UK / wider Europe Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Countly Ltd · countly.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Countly at a glance
- Vendor
- Countly Ltd
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 29 Oct 2026
- Panel verdict
- The AI panel rates Countly 2.5/5, the mean of 6 judges. Countly, web and product analytics from Countly Ltd, scores highest on sovereignty, where five of six judges gave 7 or 8, and on data ownership, clustered at 6 or 7, resting on self-hosting that keeps customer data within the customer's infrastructure with vendor access only if explicitly granted, sampling explicitly ruled out, server-to-server migration, and delete-or-return terms on termination. how scores are made
- As of
- Vendor pages captured 29 Oct 2026 to 1 Nov 2026; evaluated by the panel 30 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Countly, web and product analytics from Countly Ltd, scores highest on sovereignty, where five of six judges gave 7 or 8, and on data ownership, clustered at 6 or 7, resting on self-hosting that keeps customer data within the customer's infrastructure with vendor access only if explicitly granted, sampling explicitly ruled out, server-to-server migration, and delete-or-return terms on termination. It scores lowest on pricing transparency, 3 or 4: Flex is quoted "$ 175 / month Starts at" on usage-based pricing whose unit is not stated, leaving no annual figure computable from public pages, and in consent and privacy, clustered at 4, where the Compliance Hub gates collection to consented data and no public information was found on IP truncation or the vendor's reading of §25 TDDDG. Judges genuinely split on implementation, 4 to 6 — the higher score credits per-edition SLA terms and first-party collection, the lower ones cite no public information on CMS or shop plugins, script size, single sign-on or a status page. Sovereignty split 7 against 8, self-hosted control weighed against the London contracting entity and US subprocessors.
Speaks for it
- Self-hosted deployment keeps customer data within the customer's infrastructure, with vendor access only if explicitly granted
- Sampling is explicitly ruled out for queries across page views, referrers, devices and geographies, with search keywords parsed from referrers
- Funnels with drop-off per step, auto-regenerating cohorts usable as filters, and per-event revenue tracking with segmentation are documented
- A published data processing agreement, a subprocessor list naming each provider's location, and ISO 27001, ISO 27017, ISO 27018, SOC 2 Type II and TISAX participation are stated
- Server-to-server migration moves all application data including configurations, with deletion or retrieval of all copies committed on termination
Held against it
- The usage unit behind Flex's usage-based starting price is not stated, so judges could not compute an annual cost from public pages
- The documented consent model gates collection to consented data, with no public information found on IP truncation, configurable retention or a stated position on §25 TDDDG
- Judges found no public information on raw-event export to a named warehouse or a reporting API, with documented migration running between Countly servers
- Judges found no public information on plugins for named CMS or shop systems, script size, single sign-on or a public status page
- The Countly-hosted chain places GCP hosting across EU, USA and Asia and subprocessors such as OpenAI, Zendesk and Postmark in the USA, under a London contracting entity
Best for
- You must run analytics on infrastructure you control, with vendor access only where you explicitly grant it
- You run a public-facing site and need unsampled traffic reporting with referrers, parsed search keywords and real-time monitoring
- Your team works with funnels, cohorts and per-event revenue across web and mobile apps
- You need published compliance artifacts — a data processing agreement, a subprocessor list with locations, and stated ISO 27001, SOC 2 Type II and TISAX credentials
Avoid if
- You must compute a firm annual cost from published prices before committing
- You need the vendor-hosted edition to run entirely within the EU — the published subprocessor list spans GCP hosting across EU, USA and Asia, with US providers for support, mail and the AI assistant
- You need consent-free, banner-less measurement — the documented Compliance Hub instead gates collection to what users have consented to
The scores
| Criterion | Panel median |
|---|---|
| Traffic, sources & campaign reports | 3 of 5 |
| Goals, events, funnels & e-commerce | 3 of 5 |
| Consent-free operation & data minimisation | 2 of 5 |
| Data access, export & self-hosting | 3.5 of 5 |
| Installation, integrations & performance | 2 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 2 of 5 |
Traffic, sources & campaign reports
panel disagrees
Show reasoningHide reasoning
How this is scored
What the standard reports show: page views, visits and visitors, entry and exit pages, referrers, search engines and social networks as sources, campaigns tagged with UTM parameters, countries, devices and browsers, a real-time view, date comparisons, segments and filters, custom dashboards, scheduled email reports, shared or public dashboards, and whether reports are sampled or complete.
0 — Not a web analytics product; website traffic cannot be measured with it.
3 — Page views and visitors over time with top pages and referrers; campaign parameters, segments and report sharing are basic or not described.
5 — A dashboard with pages, referrers, UTM campaigns, countries and devices, a real-time view, date comparison, filters across all reports, email reports, and dashboards shared with clients or colleagues.
8 — Custom segments and saved views, custom dashboards and report builders, channel grouping that can be configured, Search Console or ad platform data shown beside the traffic, unsampled reports stated, several sites and roll-up reporting in one account, and annotations.
10 — Reporting that a whole organisation runs on: custom dimensions and calculated metrics, anomaly alerts, multi-site and multi-brand roll-ups with roles per site, report accuracy and how visitors are counted explained in a published methodology, and every report reproducible from the raw data.
The E-Commerce Marketing Lead
Sources reporting is documented with referrer URLs, parsed search keywords and store attribution, and I can build segments from click, scroll, UTM and custom event data with sampling explicitly ruled out. Real-time monitoring, custom dashboards with sharing, devices and geographies are all evidenced. I found no public information on date comparisons, scheduled email reports or roll-up reporting across several sites, which caps it for me. 2 9 10 15
The Data Protection Officer
Sessions, page views, bounce rate by source, queryable referrers, devices and geographies with an explicit no-sampling statement, UTM-based segments, real-time and historical views, custom dashboards and calculated metrics via formulas are all documented, and the sources feature collects web referrers and parses search keywords. We found no public information on scheduled email reports, dashboards shared with clients, roll-up reporting across sites, or a published methodology for how visitors are counted. 2 9 10 5 15
The Agency Developer
Real-time dashboards, custom dashboards with flexible widgets, drill-down segmentation and cohorts acting as filters across funnels, retention, flows and user profiles are documented, alongside referrer URLs with parsed search keywords, UTM segmentation, and unsampled queries across page views, referrers, devices and geographies. I found no public information on roll-up reporting across several sites, scheduled email reports, date comparisons or annotations — the missing roll-up is what hurts most for a multi-site agency. 2 9 10 11 15
The Growth Analyst
The captured pages show sessions and monthly active users, page view order and bounce rate by source, referrers with parsed search keywords, installation-source attribution for apps, device and geography breakdowns, UTM-based segments, real-time views and custom dashboards, with sampling explicitly ruled out. We found no public information on date comparisons, scheduled email reports, roll-up reporting across several sites, or ad-platform or Search Console data shown beside the traffic, which keeps it out of the top band. 2 9 10
The Public-Sector Site Owner
The captured pages show page views, referrers with parsed search keywords, devices and geographies queryable with no sampling, real-time monitoring alongside historical analysis, custom dashboards and behavioural segmentation — the searched-terms reporting is exactly what I need for the residents' portal. However, we found no public information on date comparisons, scheduled email reports, entry and exit pages, or roll-up reporting across several sites, which a 400,000-resident operation would expect. 2 9 10
The Skeptic
Referrers with parsed search keywords, UTM-based segments, devices, geographies, real-time monitoring, custom dashboards and cohort filters across reports are documented, with no sampling stated. I found no public information on date comparisons, scheduled email reports, configurable channel grouping, Search Console or ad-platform data beside the traffic, or roll-up reporting across several sites. 2 9 10 11
Goals, events, funnels & e-commerce
panel disagrees
Show reasoningHide reasoning
How this is scored
How the product measures what visitors do: goals for pages and events, custom events with properties, outbound links, downloads, form submissions and scroll depth tracked without code, funnels with drop-off, e-commerce tracking of orders, revenue and products, attribution of conversions to channels and campaigns, cohorts and retention, and conversion data passed back to ad platforms.
0 — Counts page views only; no goals, events or conversions can be defined.
3 — Goals for a page or a custom event; funnels, revenue and attribution are basic or not described.
5 — Goals and custom events with properties, outbound links and file downloads tracked, funnels with drop-off per step, revenue attached to goals or orders, and conversions broken down by source and campaign.
8 — Full e-commerce tracking (products, cart, checkout, orders, revenue) with plugins for named shop systems, several attribution models compared, cohorts and retention, user journeys or paths, forms and scroll depth tracked without code, and conversions sent back to Google Ads, Meta or other ad platforms server to server.
10 — Conversion analysis to the level of a product analytics suite: multi-touch attribution explained, funnels and cohorts on any event or property, revenue reconciled with the shop system, predictive or anomaly metrics with their method stated, and every conversion traceable to the raw event.
The E-Commerce Marketing Lead
This answers my checkout question: funnels with drop-off per step, spotting of high-bounce pages, abandoned forms and checkout leaks, plus event-level revenue tracking with segmentation, revenue per session and LTV, cohorts and user journeys. What I found no public information on is conversions being sent back to Google Ads or Meta server to server, plugins for named shop systems such as Shopware, or attribution models — the exact pieces my campaign reporting lives on. 2 9 11 12
The Data Protection Officer
Custom events with properties, funnels with conversion and drop-off rates, flows, cohorts usable as filters in funnels and retention, revenue attached to events with segmentation and trend monitoring, and click and scroll density out of the box are documented. We found no public information on product, cart or checkout e-commerce tracking, plugins for named shop systems, compared attribution models, or conversions passed back to ad platforms. 2 3 9 11 12
The Agency Developer
Funnels with drop-off per step, retention, cohorts that regenerate automatically, user journeys and flows, and revenue tracked per event and per session with segmentation and trends are all documented. I found no public information on plugins or order, cart and checkout tracking for named shop systems, on compared attribution models, or on sending conversions back to ad platforms. 2 9 11 12 15
The Growth Analyst
Funnels with drop-off, cohorts that regenerate automatically and work as filters across funnels, retention, flows and user profiles, revenue tracked per event in real time with segmentation, and journeys and click and scroll density give me most of what I need to trace a signup from campaign click to paid invoice. We found no public information on plugins for named shop systems, comparable attribution models, or conversions passed back to Google Ads, Meta or other ad platforms. 2 9 11 12
The Public-Sector Site Owner
Funnels with conversion and drop-off rates are documented, and the web analytics copy explicitly names spotting abandoned forms and checkout leaks, which answers my form-abandonment question directly; cohorts, retention, journeys and per-event revenue with segmentation each have their own documented pages. We found no public information on plugins for named shop systems, comparison of attribution models, or conversions sent back to advertising platforms. 2 9 11 12
The Skeptic
Funnels with drop-off, auto-regenerated cohorts usable as filters, retention, journeys and flows, and revenue tracked per event with segmentation and revenue-per-session/LTV are all public. I found no public information on full e-commerce tracking with shop-system plugins, compared attribution models, conversions sent back to ad platforms, or outbound links and downloads tracked without code. 2 3 9 11 12
Consent-free operation & data minimisation
panel disagrees
Show reasoningHide reasoning
How this is scored
What is collected and whether a consent banner is needed: a cookieless mode with how visitors are counted (daily hash, server-side fingerprint, no identifier), IP addresses truncated or not stored, no cross-site or cross-device profile and no use of data for the vendor's own purposes, data retention settings, opt-out and Do Not Track, a consent mode for features that do need consent, the vendor's stated reading of §25 TDDDG, the CNIL consent exemption and the authorities' rulings on Google Analytics, and guidance for the site's privacy policy. Where the data is processed is scored under sovereignty.
0 — Requires consent for every visit and sets tracking cookies with no privacy settings at all, or shares visitor data for advertising by default.
3 — IP anonymisation or a cookie setting exists and the product is described as GDPR-compliant; how visitors are identified, retention and the consent position are basic or not described.
5 — A documented cookieless or consent-free mode that states how visitors are counted, IP addresses truncated before storage, no cross-site tracking, retention configurable, an opt-out, a consent mode for the features that need one, and a data protection page explaining when a banner is required.
8 — The consent position stated against named law (§25 TDDDG, the ePrivacy Directive, the CNIL exemption or a DPA ruling), identifiers rotated or never created and the method published, personal data never stored by default, pseudonymisation and retention settings per data type, a legal opinion or external audit of the consent-free mode cited, and wording for the privacy policy supplied.
10 — Data minimisation that can be verified: the collection script and processing open to inspection, exactly which fields are stored documented, a consent-free mode recognised by a named authority or certified, accuracy with and without consent stated, and every privacy setting the customer controls listed with its effect.
The E-Commerce Marketing Lead
The Compliance Hub is documented as powering the SDKs to collect only data users have consented to, on a device- or user-basis, with first-party collection and no third-party cookies in on-premise or private-cloud setups. That is consent management rather than consent-free measurement: I found no public information on how visitors would be counted without consent, IP truncation, retention settings or a stated reading of German telemedia law, so I cannot tell whether my orders hold up without the banner click. 2 4 13
The Data Protection Officer
This is consent-management-first: the Compliance Hub gates SDK collection to data users consented to on a device- or user-basis, with export and purge request tracking, first-party collection and GDPR framework support described, and no third-party cookies claimed for on-premise deployment. But we found no public information on a consent-free mode with a published visitor-counting method, IP truncation, configurable retention, an opt-out, or the vendor's stated reading of §25 TDDDG, and the data processing agreement's processed categories include an advertising ID and location coordinates. 13 4 2 6 7
The Agency Developer
The Compliance Hub collects consent on device or user basis, restricts SDK collection to consented data, tracks export and purge requests, and a no-third-party-cookies claim is made for on-premise or private cloud. I found no public information on a consent-free mode, how visitors are identified, or IP handling against named German or French law, and the processing agreement lists an advertising ID and location coordinates among collected data. 2 4 6 7 8 13
The Growth Analyst
The Compliance Hub gates SDK collection on user consent at device or user level, tracks data export and purge requests, and the product is positioned first-party with no third-party cookies in on-premise or private cloud deployments; retention is stated only as long as necessary. We found no public information on how visitors are identified or counted in a cookieless mode, IP truncation before storage, or the vendor's reading of §25 TDDDG or the CNIL exemption, so the consent position is asserted rather than argued against named law. 4 13 2 6
The Public-Sector Site Owner
A Compliance Hub is documented that gates SDK collection to what users consented to on a device or user basis, alongside first-party collection and no third-party cookies in on-premise or private cloud deployments. But we found no public information on a cookieless or consent-free mode stating how visitors are counted, on IP truncation, or on the vendor's reading of §25 TDDDG and the German authorities' rulings — without that, I cannot tell the council whether a banner is avoidable. 2 4 6 13
The Skeptic
The documented tooling is a consent gate rather than a consent-free mode: SDKs collect only what users consented to, on device- or user-basis, third-party cookies are not used, and GDPR is described as supported, not guaranteed. The processing agreement lists categories that can be held per end user — name, email, location with coordinates, birth year, gender, an advertising ID — while I found no public information on IP truncation, how web visitors are identified, configurable retention, an opt-out, or a stated position against §25 TDDDG or the CNIL exemption. 2 6 7 13
Data access, export & self-hosting
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether the data stays the customer's and can leave with them: a reporting API and a raw event export, CSV export of every report, a scheduled export or sync to a data warehouse or BI tool (BigQuery, Snowflake, Looker Studio), no data sampling or limits on history, import of historical data from Google Analytics or another tool, open-source code, and a self-hosted or on-premise edition the customer runs on its own servers.
0 — No export of any kind; the data can only be viewed in the vendor's dashboard.
3 — A CSV export of reports; an API, raw data and history limits are basic or not described.
5 — A documented reporting API, CSV export of all reports, the retention period for raw data stated, and an import of historical data from Google Analytics or a stated migration path.
8 — Raw event data exportable or streamed to a named warehouse or BI tool, an API covering both reporting and data collection, no sampling stated, a self-hosted or on-premise edition with its own documentation, and the data returned or deleted on termination under stated terms.
10 — The customer owns the data end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete raw export in an open format that another tool can import, and the deletion of every copy on termination documented.
The E-Commerce Marketing Lead
Self-hosted deployment is documented to keep customer data in the customer's infrastructure with no vendor access unless explicitly granted, data migration moves all application data between servers or via export, and the processing agreement promises deletion or retrieval of all personal data on termination. Sampling is explicitly ruled out and APIs plus a data write API are described. I found no public information on streaming raw events to a named warehouse like BigQuery or on CSV export of every report. 2 4 5 7 14
The Data Protection Officer
Self-hosted and private-cloud editions with stated zero vendor access, a stated no-sampling position, server-to-server migration of all application data including configurations with manual or periodic automatic transfer, APIs including a data write API, and data processing agreement terms to delete or return all personal data with copies on termination are documented. We found no public information on raw export to a named warehouse or BI tool, a reporting API, or importing historical data from Google Analytics. 1 2 5 7 14
The Agency Developer
Self-hosting on the customer's infrastructure with no vendor access unless granted, no sampling, a documented server-to-server data migration with automatic periodic transfer, a data write API, and delete-or-return terms on termination are all published. I found no public information on streaming raw events to a named warehouse, importing history from Google Analytics, or the licence terms of the Lite edition. 1 2 4 5 7 14
The Growth Analyst
Self-hosting is documented seriously: on-premise or private cloud with zero vendor access, no sampling, migration of all application data including configurations between Countly servers, and the data processing agreement promises deletion or retrieval of all copies on termination. For my nightly warehouse sync we found no public information on a raw event export or stream to a named warehouse, a reporting API, or CSV export of reports — the only documented interface is a data write API, so the classic analytics-tool history stays portable only within Countly. 1 2 5 7 14
The Public-Sector Site Owner
Self-hosting is documented in depth: data remains within the customer's infrastructure with vendor access only if explicitly granted, server-to-server migration moves all application data including configurations, and the data processing agreement commits to deleting or returning all copies on termination. Getting data out to other tools is thinner — we found no public information on a reporting API, CSV export of every report, or export to a named data warehouse — though queries are stated to run without sampling. 2 4 5 7 14
The Skeptic
Self-hosted deployment with vendor access only if explicitly granted, no sampling, migration between Countly servers or download export including configurations, and deletion or retrieval of all copies on termination under the data processing agreement are all documented. But the migration path is Countly-to-Countly: I found no public information on raw-event export to a named warehouse or a format another tool imports, CSV export of every report, a stated raw-data retention period, or an import of Google Analytics history. 1 2 4 5 7 14
Installation, integrations & performance
panel disagrees
Show reasoningHide reasoning
How this is scored
What it takes to install and run: the size and loading of the tracking script, plugins and documented set-ups for named CMS and shop systems (WordPress, TYPO3, Shopify, Shopware, WooCommerce), single-page apps and mobile SDKs, a tag manager or Google Tag Manager template, server-side tracking and first-party proxying to avoid ad blockers, team roles and permissions, client and agency accounts, single sign-on, and an uptime or status page.
0 — No documented way to install the product on a website or app.
3 — A tracking snippet to paste into the site; plugins, SDKs, server-side options and roles are basic or not described.
5 — A documented snippet with its size stated, plugins or guides for several named CMS and shop systems, support for single-page apps, team members with roles, and an agency or multi-site account.
8 — A lightweight script or server-side collection documented, a first-party proxy or own tracking domain, SDKs for iOS, Android and named frameworks, a tag manager integration, granular roles per site, single sign-on (SAML), and a public status page with uptime history.
10 — Installation that scales across an organisation: server-side and client-side tracking with an equal feature set, an infrastructure-as-code or API-driven site set-up, white-label for agencies, SLA and support terms published, and the performance impact of the script measured and stated.
The E-Commerce Marketing Lead
Ten-plus SDKs for web, mobile, desktop and connected devices are documented, together with a data write API, granular permissions, role-based access and on-premise or private-cloud deployment. I found no public information on plugins for named shop or CMS systems such as Shopware or WordPress, script size, tag manager integration or a public status page — for my shop that leaves the integration effort genuinely open. 1 2 4 9
The Data Protection Officer
Ten-plus SDKs for mobile, web, desktop and connected devices plus a data write API, first-party collection on the customer's own infrastructure, granular role-based permissions, and published SLA terms per edition are documented. We found no public information on the script's size or measured performance impact, plugins or guides for named CMS and shop systems, tag manager integration, single sign-on, or a public status page with uptime history. 1 2 4 5 9
The Agency Developer
Ten SDKs for mobile, web, desktop and connected devices, a data write API, role-based access with granular permissions and audit logs, and a free trial are documented. I found no public information on plugins or guides for WordPress, TYPO3, Shopify or Shopware, on script size, first-party proxying against ad blockers, single sign-on, agency accounts, or a public status page — which is essentially my whole installation checklist. 1 2 4 9 15
The Growth Analyst
Ten-plus SDKs for mobile, web, desktop and connected devices plus a data write API, granular role-based permissions, and published SLA terms for the Enterprise edition cover the basics we would need across a marketing site, web app and mobile app. We found no public information on tracking script size or loading performance, plugins or guides for named CMS and shop systems, single-page app support, tag manager integration, single sign-on, or a public status page with uptime history. 1 2 4 5 9
The Public-Sector Site Owner
Ten-plus battle-tested SDKs for web, mobile, desktop and connected devices, a data write API, role-based access controls, tailored onboarding and an optional or included SLA are documented. We found no public information on the tracking script's size and loading behaviour, plugins for named CMS systems such as TYPO3 or WordPress, single-page app support, single sign-on or a public status page, so my IT team cannot yet size the rollout. 2 5 9
The Skeptic
Ten-plus SDKs across mobile, web, desktop and connected devices, a data write API, granular permissions and role-based access, and on-premise or private-cloud deployment with per-edition SLA terms are documented. Script size is not stated, and I found no public information on plugins for named CMS or shop systems, single-page app support, tag-manager integration, single sign-on, or a public status page with uptime history. 1 2 4 5 9
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where visitor data is collected, stored and processed, and who the subprocessors are (script CDN, collection endpoint, hosting, email reports, support and payment tools). Independently sourced by the sovereignty pipeline; visitor data is personal data under European rulings, so the whole chain counts, not only the database. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (CDN, collection endpoint, email, support, payment) run through non-EU providers without a stated safeguard, or EU processing relies on a proxy in front of a non-EU service.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every visitor record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The E-Commerce Marketing Lead
A self-hosted deployment is documented to keep customer data in the customer's own infrastructure with no vendor access unless explicitly granted, which makes the visitor-data chain mine on my own German servers, and the subprocessor list names every provider with its location, the processing agreement covering EU GDPR is published, and ISO 27001, 27017, 27018 and SOC 2 Type II are stated. The contracting entity is a London company at a UK address, and the managed chain includes US providers such as OpenAI, to which AI-assistant prompts are shared, so the hosted route is not European end to end. 4 5 6 7 8
The Data Protection Officer
The contracting entity is Countly Ltd at a London address, not an EU entity, and the published subprocessor list places GCP for hosted servers across EU, USA and Asia and OpenAI in the USA receiving prompts and event metadata or aggregated data for the AI assistant, alongside US providers for support, mail and payments. A data processing agreement governed by EU and UK GDPR is published, ISO 27001/27017/27018 and SOC 2 Type II are stated, and a self-hosted edition is documented to keep customer data on the customer's own infrastructure with no default vendor access, which lifts it above a purely hosted non-EU chain. 4 5 6 7 8
The Agency Developer
A self-hosted edition is documented that keeps every visitor record on the customer's own servers with zero vendor access and fully customer-defined data location, and the subprocessor list is published with locations, a data processing agreement exists, and ISO 27001, 27017, 27018, SOC 2 Type II and TISAX are stated. The contracting entity is Countly Ltd in London, and the Countly-hosted chain runs through GCP regions in the EU, USA and Asia with support, email and AI-assistant functions at US providers. 4 5 6 7 8
The Growth Analyst
The subprocessor list is published with locations — GCP for hosted servers across EU, USA and Asia, alongside US providers such as OpenAI, Postmark and Zendesk — and the DPA, ISO 27001/27017/27018, SOC 2 Type II and TISAX participation are documented, while the self-hosted edition keeps every visitor record on our own servers with location fully customer-defined. The contracting entity is Countly Ltd at a London address rather than an EU entity, and we found no public information on the company's ownership. 6 8 4 5 7
The Public-Sector Site Owner
The contracting entity is Countly Ltd of London, but the self-hosted route is documented as keeping customer data within the customer's own infrastructure with no vendor access unless explicitly granted, which would place our residents' records on the municipal data centre's own servers. For the hosted route there is a published data processing agreement naming EU GDPR, Google Cloud hosting with an EU region choice and a fully customer-defined data location for Enterprise, a subprocessor list with each provider's location, and ISO 27001, ISO 27017, ISO 27018 and SOC 2 Type II stated. Ownership is not documented on the captured pages, and several listed subprocessors, including OpenAI for the AI assistant, sit in the USA. 4 5 6 7 8
The Skeptic
Countly Ltd of London is the contracting entity under a published data processing agreement naming EU GDPR, UK GDPR and the Data Protection Act, with a subprocessor list stating purpose and country for each — GCP hosting spanning EU, USA and Asia, OpenAI in the USA for the opt-in AI assistant, Zendesk and Postmark in the USA — and ISO 27001/27017/27018, SOC 2 Type II and TISAX stated. The self-hosted edition keeps customer data on the customer's infrastructure with no vendor access unless granted, though the captured pages do not pin data residency and much of the operational chain sits in the UK and USA rather than the EU. 4 5 6 7 8
Pricing transparency
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly page views or events, what happens when traffic exceeds the tier, the number of sites and users included, which features (e-commerce, funnels, raw export, API, SSO, longer retention) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with traffic, sites or features is unclear.
5 — Tiers are public with their price per traffic band and main inclusions, but at least one commonly needed piece (overage, extra sites, raw export, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (page views, events, sites, users), overage handling stated, add-ons priced, the self-hosted edition's cost or licence stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given traffic volume, site count and feature set, with every add-on, setup, support and overage fee and the cancellation and data-return terms published.
The E-Commerce Marketing Lead
The pricing page shows a Flex private-cloud tier with a starting price of $175 per month on usage-based rather than seat-based pricing, a 14-day free trial, and Enterprise at custom pricing, with a free way to start offered on other pages. I found no public information on how cost scales with traffic volume, what the free option includes, or the price of add-ons and the optional SLA, so I cannot compute my real annual cost. 5 15
The Data Protection Officer
Flex is stated at starts at $ 175 / month with usage-based rather than seat-based pricing, a 14-day free trial and per-tier inclusions listed, Enterprise is custom pricing, and a free way to start exists. We found no public information on the usage scaling rule, overage handling, addon prices, minimum term, VAT treatment, or the self-hosted edition's cost, so an annual cost cannot be computed from public pages alone. 5 2 15
The Agency Developer
The pricing page shows Flex private cloud at "$ 175 / month Starts at" with usage-based rather than seat-based pricing, a 14-day free trial, a free way to get started, and Enterprise self-hosted at "Custom pricing". I found no public information on how usage scales the price, on overage handling, what the free tier includes, or minimum terms, so a real annual cost for a client cannot be computed from the public pages alone. 2 5 15
The Growth Analyst
The pricing page publishes Flex at "$ 175 / month" on a starts-at basis with usage-based rather than seat-based pricing, a 14-day free trial, a free way to get started, and listed inclusions, while Enterprise is custom pricing with its inclusions itemised. We found no public information on what the usage unit actually is, overage handling, or the limits of the free tier, so I cannot compute our annual cost from the captured pages alone. 5 15 2
The Public-Sector Site Owner
Flex is quoted at "$ 175 / month Starts at" with usage-based rather than seat-based pricing, a 14-day free trial and a free tier to get started, while the self-hosted Enterprise edition carries "Custom pricing". How the usage-based cost scales with traffic, what overage or the Adaptivity add-on or the optional SLA cost, and what the free tier's limits are, are not shown — so the procurement office could not compute our annual figure from the public pages alone. 5 15
The Skeptic
Flex is quoted as "starts at" $ 175 / month with usage-based pricing whose usage unit is not stated, a 14-day free trial, Enterprise at "Custom pricing", and a free get-started tier whose limits are not described. How cost scales with traffic or events, overage handling, included sites, VAT treatment and minimum term are all unclear, so the real annual cost is not computable from the public pages. 5 12 15
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Countly
Is Countly European?
Yes, though not from the EU. whats-best.ai classifies Countly as UK / wider Europe.
Where does Countly store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Countly have a free plan?
Yes. Countly has a free plan, per the vendor’s page captured 29 Oct 2026.
What are the best alternatives to Countly?
As of 4 Nov 2026, the panel rates Matomo (4/5), Piwik PRO Analytics Suite (3.5/5) and Pirsch Analytics (3.5/5) highest among the other 17 Web Analytics products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Piwik PRO Analytics Suite (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Countly alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Hosting options, Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting location. The pages offer a choice of regions without naming any default, and Enterprise self-hosted deployments place data entirely on customer infrastructure, so EU storage is an option rather than a given.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 17 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (18)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage countly.com Checked 29 Oct 2026 Details →
- 2 Features page (web analytics) countly.com Checked 29 Oct 2026 Details →
- 3 Features page (funnels) countly.com Checked 29 Oct 2026 Details →
- 4 Features page (privacy by design) countly.com Checked 29 Oct 2026 Details →
- 5 Pricing page countly.com Checked 29 Oct 2026 Details →
- 6 Privacy policy countly.com Checked 29 Oct 2026 Details →
- 7 Data processing agreement (dpa) countly.com Checked 29 Oct 2026 Details →
- 8 Subprocessor list countly.com Checked 29 Oct 2026 Details →
- 9 Traffic, sources & campaign reports — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 10 Traffic, sources & campaign reports — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 11 Goals, events, funnels & e-commerce — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 12 Goals, events, funnels & e-commerce — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 13 Consent-free operation & data minimisation — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 14 Data access, export & self-hosting — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 15 Installation, integrations & performance — found from sitemap countly.com Checked 29 Oct 2026 Details →
- 16 Terms of service — found from the homepage countly.com Checked 1 Nov 2026 Details →
- 17 Self-hosting / on-premises installation docs — found from the homepage countly.com Checked 1 Nov 2026 Details →
- 18 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →