# Countly > Countly is a product analytics platform sold as a managed private-cloud server (Flex), a self-hosted Enterprise edition and the open-source Countly Lite. Agents reach a Countly server through its HTTP API or the official countly-mcp-server. - Canonical: https://www.anchorterminal.com/tools/countly - Markdown: https://www.anchorterminal.com/tools/countly.md (~7,850 tokens) - Slim: https://www.anchorterminal.com/tools/countly.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/countly.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade C · 54.8/100 · rank #607 of 842 · #9 in Product analytics & experimentation · not agent-ready · confidence medium** ## Assessment Countly suits an agent working against a server its owner already runs. The official MCP server filters its 209 tools by edition, plugin and permission and has per-category read-only settings. No status page, OpenAPI document or published API rate limit was found, and the Flex trial needs a credit card. ## Facts | Field | Value | | --- | --- | | Vendor | Countly Ltd (https://countly.com) | | Kind | HTTP API | | Category | Product analytics & experimentation (https://www.anchorterminal.com/categories/product-analytics) | | Transport | HTTP, stdio, Streamable HTTP | | Endpoint | `https://mcp.count.ly/mcp` | | Auth | API key · Self-serve once a server exists. A dashboard user copies an `api_key`, which has that user's full read and write access, or creates an auth token in the Token Manager or with `/i/token/create`, limited by app, endpoint pattern and lifetime. Tokens go in the `countly-token` header or the `auth_token` query parameter. The MCP server takes `COUNTLY_SERVER_URL` and `COUNTLY_AUTH_TOKEN`, or `X-Countly-Server-Url` and `X-Countly-Auth-Token` headers over HTTP. SDKs send the write-only `app_key`. | | Pricing | Paid ($175 / mo) · Flex starts at $175 a month, billed by tier on monthly active users and data points, with a 14-day trial that needs a credit card. Tier prices appear during signup. Funnels, retention and flows sit in the Intelligence add-on. Enterprise is on quotation. Countly Lite is free to self-host. API and MCP calls are not billed (https://countly.com/pricing, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API reference, the MCP server README or the pricing page (checked 2026-10-08). | | Licence | Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT | | Tools exposed | 209 | | Packages | npm: `countly-mcp-server`; npm: `countly-sdk-web`; npm: `countly-sdk-nodejs` | | Source | https://github.com/Countly/countly-server | | Docs | https://api.count.ly/ | | llms.txt | https://countly.com/llms.txt | | Last release | 2026-10-07 | | npm downloads / week | 27,579 | | Surface graded | A Countly Flex server (managed, one per customer) reached through the server HTTP API documented at api.count.ly and the official `countly-mcp-server`. Countly Lite and Enterprise run the same API on the owner's infrastructure | | API | Read endpoints under `/o` and write endpoints under `/i`, JSON responses. Reference versioned 24.05, 25.03 and 26.01, 563 pages for 26.01. No OpenAPI document found | | MCP server | `countly-mcp-server` 1.7.0 (7 October 2026), MIT, stdio or streamable HTTP, also hosted at https://mcp.count.ly/mcp with the server URL and token in request headers. 209 tools in 43 categories, 3 resources and 8 prompts per the README | | Credentials | `api_key` per dashboard user with that user's full access, or auth tokens limited by app, endpoint pattern, lifetime (default 1,800 seconds) and CRUD permission. Sent as a query parameter or in the `countly-token` header. `app_key` only writes data | | MCP permissions | `COUNTLY_TOOLS_ALL` and `COUNTLY_TOOLS_` take NONE, R, CR, CRU or CRUD. Tools the edition, plugins or user's permissions cannot run are hidden | | Rate limits | MCP HTTP endpoint 120 requests a minute per IP and 50 connections per IP by default. Server setting `api_rate_limit_requests` defaults to 0 (off), dashboard 500 requests in 60 seconds | | Errors | `{"result": "message"}` with an HTTP status code. MCP failures return as `isError` results naming the missing plugin or permission | | Editions | Flex from $175 a month with Advanced Analytics, Adaptivity and Intelligence as add-ons. Enterprise self-hosted on quotation with all three. Countly Lite free and open source | | Trial | 14 days on Flex, credit card required. A server over its tier's monthly limit is locked until the next cycle | | SDKs | Android, iOS, Web, Flutter, React Native, Dart, HarmonyOS, C++, Java, NodeJS, Windows and Unity, for data collection | | Audit | System logs plugin with `/o?method=systemlogs` endpoints | | Certifications | ISO 27001, ISO 27017, ISO 27018, SOC 2 Type II and TISAX participant per countly.com/privacy-by-design. Reports not public | | Status | No status page found | | Data | Flex servers on Google Cloud in a region the customer chooses (EU, USA or Asia per the sub-processor list). OpenAI is a sub-processor only when the AI assistant is used | | Open source | Countly Lite under AGPL-3.0 with added branding terms. Enterprise plugins closed. MCP server MIT | | Capabilities | analytics.query, analytics.events, analytics.funnels, analytics.experiments, analytics.flags, observability.errors | | Tags | official, hosted, self-hosted, open-source, mcp, api-key, llms-txt, paid, trial, typescript | | JSON | https://www.anchorterminal.com/api/v1/tools/countly.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 28 | 5.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 75 | 12.2 | | Agent ergonomics | 13% | 16.2 | 66 | 10.7 | | Security & auth | 14% | 17.5 | 63 | 11.0 | | Payments & pricing | 10% | 12.5 | 17 | 2.1 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 80 | 7.0 | | Transparency & trust (editorial 64, provenance 76) | 7% | 8.8 | 70 | 6.1 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **54.8 → C** | ### Why each score - Reliability 28: Graded on the hosted lines, for a Countly Flex server reached through its HTTP API and the official MCP server. No status page was found on countly.com, the Flex page or the docs, and status.countly.com did not resolve (0). With no page there is no readable incident history (5). The MCP server's HTTP endpoint is limited to 120 requests a minute per IP, but the Countly server's own `api_rate_limit_requests` setting ships at 0 (off), and the Flex terms reserve usage limits without numbers (8 of 15). No 429 or retry guidance and no idempotency keys were found in the API reference (0). The pricing page lists an SLA as optional on Flex and included in Enterprise, with no SLA text published (5 of 10). The API and MCP server 1.7.0 are generally available (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 75: No OpenAPI document was found on api.count.ly or in Countly/countly-server. Every MCP tool has a typed JSON Schema input (18 of 25). countly.com/llms.txt indexes 366 help articles and points automated clients to the help centre's JSON API, while api.count.ly has no llms.txt and article pages answered 403 to our reader (8). MCP tool descriptions name the endpoint, the plugin required and the tool to use instead, and API pages state permissions and behaviour (16). 82 enums across the tool sources, but the HTTP API takes JSON arrays and objects as query-string values (9). API pages carry request examples, response fields and error responses, as plain message strings (11). The API reference is versioned 24.05, 25.03 and 26.01, and the server and MCP server keep public changelogs (13). - Agent ergonomics 66: The MCP README counts 209 tools in 43 categories, far past 30 (5). Add back 8 because the server hides tools the edition, enabled plugins or user's permissions cannot run, and `COUNTLY_TOOLS_*` settings switch categories off (13). List endpoints take `iDisplayStart` and `iDisplayLength`, and MCP list tools take `skip`, `limit` and `search` (15). API errors are `{"result": "message"}` strings with HTTP status codes and no error codes. The MCP server returns failures as `isError` results that name the missing plugin or permission (12). MCP tools carry readOnlyHint, destructiveHint and idempotentHint since 1.7.0. No idempotency keys on API writes (14). MCP tools accept `app_name` in place of `app_id` and set defaults. The SDKs cover data collection, not the read API (12). - Security & auth 63: Auth tokens are scoped to apps and endpoint patterns, expire after a set lifetime, are revocable and carry create, read, update and delete permissions since 25.03.54. The dashboard `api_key` has its user's full access (26 of 30). Less 10 because `api_key` and `auth_token` are documented as query-string parameters, with the `countly-token` header as the recommended alternative (16). MCP read-only mode and per-category CRUD levels, bounded by the token's permissions. No confirmation step for destructive tools (16). Tools return event names, user properties and crash data written by end users, and no prompt-injection guidance was found. The docs suggest a self-hosted model for sensitive data (3). A system logs API records dashboard actions, and the security FAQ cites more than 30 log types (12). No security.txt. SECURITY.md gives a disclosure address and a bounty for medium severity and above, security fixes are listed in the public changelog, and the site claims ISO 27001, 27017, 27018 and SOC 2 Type II without public reports (16). - Payments & pricing 17: No x402, MPP or L402 (0). The pricing page gives only a starting price for Flex, $175 a month, priced on monthly active users and data points, with tier prices shown during signup and Enterprise on quotation (7 of 20). The 14-day Flex trial needs a credit card. Countly Lite is free to self-host with no card, without funnels, retention, cohorts or Drill, so half credit (10). A person signs up in a browser, creates a server and makes a token in the dashboard (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 80: `countly-mcp-server` 1.7.0 was published on 7 October 2026 and server tag 25.03.54 on 22 September 2026 (30). Four server tags (25.03.49, .50, .51, .54) and MCP 1.5.0 and 1.7.0 since 10 July 2026 (20). 821 commits on the server's default branch since 10 July 2026, a Discord community and a support portal. We could not read issue response times because the GitHub API refused us (12 of 25). SDK docs are at 26.1.x for Android, iOS, Web and Flutter, while the NodeJS SDK docs are at 24.10.x. The MCP server is not in the official MCP registry (10 of 15). CI, CodeQL and Docker workflows on the server, and test, nightly end-to-end and CodeQL workflows on the MCP server (8). - Transparency & trust 70: Countly Lite is AGPL-3.0 with added branding terms under Section 7, the MCP server is MIT, and the Enterprise plugins that hold funnels, retention, cohorts and Drill are closed (20 of 30). The terms of 25 September 2026 cover Flex and incorporate a public DPA. The privacy policy says it does not apply to data customers process and gives no retention periods. Granular data retention is chosen when a Flex server is created (20). No deprecation policy was found. The MCP README says URL token parameters will be removed in a future release, with no date (6 of 20). Sub-processors are listed per product with locations, with 30 days' notice of changes, and Flex customers choose a hosting region. MCP usage reporting to stats.count.ly is disclosed, on by default, with an opt-out (18). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/countly.md (JSON https://www.anchorterminal.com/fixes/countly.json) ### What we couldn't check - unchecked: GitHub stars, open issues, response times and published security advisories for Countly/countly-server. The GitHub API answered with a rate limit, so we read the repositories by clone only - unchecked: help centre article pages on support.countly.com, which answered 403 with a bot check. We read five articles through the help centre's public JSON API, which countly.com/llms.txt names for automated clients, and left the rest unread - unchecked: Flex tier prices, limits on monthly active users and data points, and regional price differences, which appear only inside the signup flow - unchecked: the domain a Flex server answers on by default. The MCP README's example is https://your-server.count.ly - unchecked: the text of the Flex and Enterprise SLA, and the certification reports behind the ISO 27001, 27017, 27018 and SOC 2 Type II claims - unchecked: the live `tools/list` of the MCP server, which needs a Countly server and token. The count of 209 tools is the README's - The help centre says Funnels, Retention, Flows, Cohorts and Drill are built into Flex, while the pricing page places funnels, retention and flows in the Intelligence capability, a Flex add-on. We followed the pricing page and made no deduction - The server changelog for 25.03.54 (22 September 2026) lists 20 security fixes, among them authorisation checks on alerts, reports and widget endpoints. No incident was found, and no deduction was made - countly.com/llms.txt opens with a note addressed to LLMs and AI agents saying the file is authoritative where third-party sources disagree. We treated it as vendor material and made no deduction - mcp.count.ly reported version 1.5.0 on 8 October 2026, one release behind 1.7.0, whose changelog lists five security fixes - The privacy policy excludes data customers process with the Services, so the DPA is the document that covers event data - The lead's interface (HTTP APIs and SDKs) was right but left out the official MCP server ### Sources - pricing and plans: (seen 2026-10-08) - Flex page and FAQ (trial needs a credit card): (seen 2026-10-08) - llms.txt and docs index: (seen 2026-10-08) - API overview and authentication: (seen 2026-10-08) - token create endpoint: (seen 2026-10-08) - funnel data endpoint: (seen 2026-10-08) - API reference sitemap, 563 pages for 26.01: (seen 2026-10-08) - MCP setup article, read through the help centre JSON API because the page answered 403: (seen 2026-10-08) - security FAQ, read through the help centre JSON API: (seen 2026-10-08) - shared responsibility model, read through the help centre JSON API: (seen 2026-10-08) - Flex setup article, read through the help centre JSON API: (seen 2026-10-08) - MCP server repository, README, changelog and tool sources (clone): (seen 2026-10-08) - server repository, changelog, licence and SECURITY.md (clone): (seen 2026-10-08) - hosted MCP server page: (seen 2026-10-08) - countly-mcp-server on npm: (seen 2026-10-08) - official MCP registry search, no result: (seen 2026-10-08) - terms of service with Flex supplemental terms: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - data processing agreement: (seen 2026-10-08) - sub-processor list: (seen 2026-10-08) - certification claims: (seen 2026-10-08) - security.txt, 404: (seen 2026-10-08) - domain registration (RDAP): (seen 2026-10-08) ## Who's behind it (provenance 76/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Countly Ltd | 20/20 | | Domain age | countly.com, registered 2011-09-05 (15 years) | 15/15 | | Endpoint on the vendor's domain | mcp.count.ly | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms (last updated 25 September 2026) name Countly Ltd, incorporated in England and Wales with registered number 8568329, registered at 1 Bow Churchyard, London EC4M 9DQ. They cover Flex through supplemental terms and exclude Enterprise subscriptions, which have written agreements. The privacy policy (last updated 25 September 2026) covers Countly's websites, services and accounts and says it does not apply to data customers process with the Services. The DPA at countly.com/legal/dpa covers that data. The hosted MCP server answers at mcp.count.ly and the API reference at api.count.ly, a second domain of the vendor's. Each customer's API answers on that customer's own server address. countly.com/.well-known/security.txt returns 404. SECURITY.md in the repositories gives a disclosure address at count.ly. No status page was found. status.countly.com did not resolve. RDAP for countly.com gives a registration date of 2011-09-05. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://countly.com/legal/terms-of-service), read 2026-10-08, dated 2026-09-25, states 5 of the 7 things a reader expects. - To know. Says the terms or the service can change without notice (costs points). "Such revised terms will apply to the Site and Services from the date of publication. Users should check the Terms regularly to ensure familiarity with the then current version." - To know. Says access can be ended without notice or for any reason. "We may suspend or cancel your registration with immediate effect for any reasonable purposes or if you breach these Terms." - Gives the date it was last updated. Last updated 2026-09-25. - Names the governing law or courts. The law of England and Wales. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). The AI Assistant in the service uses models developed and operated by third-party providers, including OpenAI. "The Services may include access to an AI-powered assistant (the “AI Assistant”) that uses models developed and operated by third-party providers, including but not limited to OpenAI, L.L.C." - Also in the text (2026-10-08). The customer must not use the AI Assistant to make or automate decisions in high-risk areas unless it has put in place the measures the law requires. "The Customer must not use the AI Assistant to make or automate decisions in high-risk areas (such as creditworthiness, hiring, medical diagnosis, law enforcement, or migration control) unless the Customer has implemented all risk-management, human oversight, and conformity assessment measures" - Also in the text (2026-10-08). For Countly Flex, performance and availability are not guaranteed when usage materially exceeds the expected levels. "Countly does not guarantee service performance or availability when actual usage materially exceeds the expected levels." **Privacy policy** (https://countly.com/legal/privacy-policy), read 2026-10-08, dated 2026-09-25, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-09-25. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@count.ly. - Not found in the text. Says where data is transferred or stored. ## Live (updated 2026-10-09 10:14 UTC) - Right now: down, HTTP 500, 320 ms, checked 2026-10-09 10:14 UTC (get on `https://mcp.count.ly/mcp`) - Uptime 24h 0.0% (28 probes) · 30 days 0.0% (28 probes) · p50 n/a · p95 n/a - Always current: https://www.anchorterminal.com/api/v1/live/countly.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Flex, lowest tier | $175 | per month (plan) | starting price, by monthly active users and data points, add-ons extra | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Official MIT MCP server, `countly-mcp-server` 1.7.0 of 7 October 2026, with read-only, destructive and idempotent annotations on its tools - `COUNTLY_TOOLS_ALL=R` makes every MCP tool read-only, and per-category settings take None, R, CR, CRU or CRUD - Auth tokens can be limited to named apps and endpoint patterns, carry a lifetime in seconds and are revocable - API reference at api.count.ly is versioned (24.05, 25.03, 26.01) with parameters, examples and error responses per endpoint - Sub-processor list with locations and a public DPA, both updated 25 September 2026, with 30 days' notice of sub-processor changes ## Weaknesses - No public status page or incident history was found for Flex servers or for mcp.count.ly - No OpenAPI document was found, and the server's API rate limit is a setting that ships switched off with no published value for Flex - The API accepts `api_key` and `auth_token` in the URL query string, and the `api_key` has its user's full read and write access - Flex starts at $175 a month, its 14-day trial needs a credit card, and tier prices appear only during signup - Funnels, retention, flows, cohorts and Drill need Enterprise or a paid Flex capability, and are absent from Countly Lite - The MCP server reports usage to stats.count.ly by default until `ENABLE_ANALYTICS=false` is set ## Before you call it (notes for agents) 1. Create a dedicated token in the Token Manager, limited to the apps and endpoints the task needs, and send it in the `countly-token` header, not the URL 2. Set `COUNTLY_TOOLS_ALL=R` unless the task needs writes. The token's own permissions still apply and the stricter of the two wins 3. Call `apps_list` first. Most tools need `app_id` or an exact `app_name` 4. Check `get_version` for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins 5. Set `ENABLE_ANALYTICS=false` to stop usage reports to stats.count.ly, and prefer the stdio server to mcp.count.ly so the server URL and token stay local ## Connect Install: ```bash npx -y countly-mcp-server ``` First request: ```bash curl -H "countly-token: YOUR_TOKEN" "https://your-countly-url.com/o?app_id=APP_ID&method=funneldata&funnels=[%22FUNNEL_ID%22]" ``` Claude Code: ```bash claude mcp add countly -e COUNTLY_SERVER_URL=https://your-countly-url.com -e COUNTLY_AUTH_TOKEN=YOUR_TOKEN -- npx -y --prefer-online countly-mcp-server@latest ``` MCP client configuration: ```json { "mcpServers": { "countly": { "args": [ "-y", "--prefer-online", "countly-mcp-server@latest" ], "command": "npx", "env": { "COUNTLY_AUTH_TOKEN": "YOUR_TOKEN", "COUNTLY_SERVER_URL": "https://your-countly-url.com" } } } } ``` Through letme (picks today, calling later): https://letme.dev/countly. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | PostHog | B | 68.4 | 204 | analytics.query, analytics.events, analytics.funnels, analytics.experiments, analytics.flags, observability.errors | no | https://www.anchorterminal.com/tools/posthog.md | | Amplitude | B | 66.2 | 275 | analytics.query, analytics.funnels, analytics.experiments, analytics.flags, analytics.events | no | https://www.anchorterminal.com/tools/amplitude.md | | Mixpanel | B | 62 | 406 | analytics.query, analytics.funnels, analytics.events, analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/mixpanel.md | | Statsig | BB | 72.3 | 104 | analytics.experiments, analytics.flags, analytics.query, analytics.events | no | https://www.anchorterminal.com/tools/statsig.md | | GrowthBook | BB | 70.1 | 155 | analytics.experiments, analytics.flags, analytics.query, analytics.events | no | https://www.anchorterminal.com/tools/growthbook.md | | LaunchDarkly | B | 69.2 | 185 | analytics.flags, analytics.experiments, observability.errors | no | https://www.anchorterminal.com/tools/launchdarkly.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - `countly-mcp-server` detects Countly Lite, Enterprise or the newer Countly Platform on connection and lists only the tools that server's plugins and the user's permissions allow (source: ) - The MCP server is also hosted at https://mcp.count.ly/mcp, where the page reported version 1.5.0 on 8 October 2026 while npm had 1.7.0 (source: ) - MCP usage reports go to stats.count.ly under the Countly server's domain by default, with tool names, outcomes and durations, and `ENABLE_ANALYTICS=false` turns them off (source: ) - The API reference marks Drill, Funnels, Flows, Cohorts, Formulas, Retention Segments and AB Testing as Enterprise plugins (source: ) - Server release 25.03.54 of 22 September 2026 lists 20 security fixes, one of which gives auth tokens explicit CRUD permissions (source: ) - The Flex terms let Countly require an upgrade or impose usage limits when API call frequency or ingestion is far above the tier's assumptions (source: ) - countly.com/llms.txt opens with a note to LLMs and AI agents that calls the file authoritative where third-party sources disagree (source: ) ## Compare - [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md): B 66.2 vs C 54.8 - [Countly vs Fullstory](https://www.anchorterminal.com/compare/countly-vs-fullstory.md): C 54.8 vs B 62.6 - [Countly vs GrowthBook](https://www.anchorterminal.com/compare/countly-vs-growthbook.md): C 54.8 vs BB 70.1 - [Countly vs Mixpanel](https://www.anchorterminal.com/compare/countly-vs-mixpanel.md): C 54.8 vs B 62 - [Countly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/countly-vs-optimizely.md): C 54.8 vs B 62.6 - [Countly vs Pendo](https://www.anchorterminal.com/compare/countly-vs-pendo.md): C 54.8 vs D 48.2 - [Countly vs PostHog](https://www.anchorterminal.com/compare/countly-vs-posthog.md): C 54.8 vs B 68.4 - [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md): C 54.8 vs BB 72.3 - [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md): C 54.8 vs E 44.4 - [Countly vs Heap](https://www.anchorterminal.com/compare/countly-vs-heap.md): C 54.8 vs D 53 - [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md): C 54.8 vs B 69.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on countly.com or one of its subdomains, or the README of github.com/Countly/countly-server. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "countly", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Countly on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Countly on Anchor Terminal](https://www.anchorterminal.com/badges/countly.svg)](https://www.anchorterminal.com/tools/countly) ``` Plain link: ```html Countly on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Countly is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/countly-dark.png - Light: https://www.anchorterminal.com/assets/share/countly-light.png