Parse.ly
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Automattic Inc. · www.parse.ly
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.
Parse.ly at a glance
- Vendor
- Automattic Inc.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Outside the EU by default source, captured 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Parse.ly 2/5, the mean of 6 judges. Parse.ly, a content analytics service from WPVIP Inc., parent Automattic, scores as a strong traffic reporter held back by US processing and consent-based tracking. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Parse.ly, a content analytics service from WPVIP Inc., parent Automattic, scores as a strong traffic reporter held back by US processing and consent-based tracking. It is strongest at traffic reporting and data ownership: five of six judges give traffic reporting the maximum 6 for a real-time dashboard covering referrers, campaigns, Google Search Console, channels and segments with scheduled emailed reports, and data ownership clusters at 6 to 7 on a Data Pipeline that sends raw, event-level data to the customer's warehouse and a documented reporting API. Sovereignty clusters at 2 to 3: visitor data is processed, archived and stored long-term in US data centres in Virginia and Oregon, with backups in Virginia and Ohio on AWS, under New York governing law. The judges genuinely split on privacy: five judges score consent and privacy at 4 while the Data Protection Officer scores 0 on every criterion, calling it a consent product with a 13-month visitor cookie. Conversions cluster at 4 to 6 and are a paid add-on in bundles of 20 labels; no price figures appear on the captured pages.
Speaks for it
- Real-time traffic reporting covering referrers, campaigns, Google Search Console, channels, segments and pages, with scheduled reports delivered by email.
- A Data Pipeline that sends raw, event-level data from websites and apps to the customer's own data warehouse and BI tools.
- A documented reporting API with key-and-secret authentication, pagination and error handling, plus exact-count raw export through support.
- A WordPress plugin that injects metadata from a Site ID alone, alongside an open-source Google Tag Manager template for web and AMP containers with a sandbox dashboard.
- IP address tracking can be disabled per site or per visitor with the address hashed before storage, and Global Privacy Control is respected.
Held against it
- The documented mode is consent-based: a first-party cookie uniquely identifies a browser for 13 months, and visitors who reject cookies are still counted under a single pseudonymous OPTOUT identifier.
- Visitor data is processed, archived and stored long-term in US data centres in Virginia and Oregon, with backups in Virginia and Ohio on AWS, and we found no public information on EU hosting, a published data processing agreement, or a subprocessor list beyond AWS.
- We found no public information on funnels with drop-off per step, order- or product-level revenue tracking, or sending conversions back to ad platforms.
- We found no public information on a self-hosted edition, an import of historical data from another tool, or data return and deletion when a contract ends.
- Site IDs are provisioned by support ticket only after purchase, and the single-page-application tracker requires activation by support.
Best for
- You publish content on WordPress and need real-time reporting on referrers, campaigns and Google Search Console for editorial decisions.
- You want raw, event-level data flowing into your own warehouse or BI tools through a documented API.
- You measure content outcomes such as newsletter signups and outbound link clicks and are comfortable running the tracker behind a consent banner.
- You deploy analytics through Google Tag Manager and value an open-source tag template with a sandbox dashboard for testing.
Avoid if
- You need consent-free or cookieless measurement — the vendor itself recommends loading the tracker only after consent has been obtained.
- Your compliance regime requires the visitor-data chain to remain in the EU — data is processed and stored long-term in US data centres in Virginia and Oregon under New York governing law.
- You run an online shop and need order-, product- or revenue-level reporting — the documented conversion labels cover content actions, and we found no public information on revenue reconciliation or checkout funnels.
- You must budget an annual cost before talking to sales — the captured pages state no prices, and Site provisioning begins with a support ticket after purchase.
The scores
| Criterion | Panel median |
|---|---|
| Traffic, sources & campaign reports | 3 of 5 |
| Goals, events, funnels & e-commerce | 2.5 of 5 |
| Consent-free operation & data minimisation | 2 of 5 |
| Data access, export & self-hosting | 3 of 5 |
| Installation, integrations & performance | 2.5 of 5 |
| European sovereignty | 1.5 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
The sources menu covers referrers, campaigns, Google Search Console data, channels and segments beside pages, there is a real-time view, and scheduled reports are delivered by email — that covers most of my weekly routine. What I did not find is any public information on date comparisons, custom dashboards, roll-up reporting across several shops, or a statement on sampling. 1 4 6 7
The Data Protection Officer
The dashboard documentation covers a sources menu with referrers, campaigns, channels and segments and Google Search Console data beside the traffic, a real-time view, email and scheduled reports, saved favourites, and dashboard pages filterable by conversions; device analytics and approximate geographic segmentation are documented from the collected fields. We found no public information on date comparisons, custom dashboard builders, roll-up reporting across sites or annotations. That is more than a standard dashboard, but short of a configurable, organisation-wide reporting layer. 1 6 7 8 10 13
The Agency Developer
The dashboard gives me real-time data with referrers, campaigns, Google Search Console shown beside the traffic, channels and segments, and a reports suite with scheduled email delivery — solid content reporting for my WordPress clients. I found no public information on date comparisons, dashboards shared with a client login, multi-site roll-up reporting, or sampling guarantees; the documentation even states the API accepts a 1-2% error rate in the name of speed while the dashboard aims for exact counts. 1 4 6 7 13
The Growth Analyst
The sources menu covers referrers, campaigns, Google Search Console, channels and segments, and pages, with everything in real time, plus a reports tab with scheduled email delivery and a favorites menu for saved views, and conversions can filter and sort lists across the dashboard. We found no public information on date comparisons, filters across every report, or dashboards shared with clients and colleagues, so I could not confirm the stakeholder-reporting basics I rely on. 1 4 6 7 8
The Public-Sector Site Owner
The dashboard's sources menu covers referrers, campaigns, Google Search Console, channels and segments, and pages, alongside a real-time dashboard and scheduled reports that can be emailed to colleagues. We found no public information on country, device or browser breakdowns, date comparisons, or roll-up reporting across several sites, which a district running many departmental sites would need. 1 6 7
The Skeptic
The dashboard documents a real-time view with referrers, campaigns, pages, and Google Search Console data shown beside the traffic, plus segments and channels in the sources menu and scheduled, emailed reports. We found no public information on date comparison, custom dashboard builders, dashboards shared with clients, or whether reports are sampled, which keeps this a solid standard suite rather than an organisation-wide reporting layer. 1 6 7
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
Conversions are labelled goals with types such as Purchase, Newsletter Signup and Link Click, broken down by pages, sections and referrers with linear attribution, configured via Google Tag Manager or JavaScript. As a shop operator I miss everything revenue-side: no order, product or revenue tracking reconciled with my Shopware backend, no checkout funnel with drop-off per step, and no documented path to send conversions back to Google Ads or Meta. 8 9
The Data Protection Officer
Content Conversions are documented in depth: typed labels for purchase, subscription, lead capture, newsletter signup and outbound link click, with conversion count, converting visitors and rate metrics, drill-down by pages, authors, sections and referrers, URL restrictions, and linear attribution; file downloads are trackable through dynamic tracking. We found no public information on funnels with drop-off per step, revenue or product-level e-commerce, or conversions passed back to ad platforms. 8 9 14
The Agency Developer
Conversion labels cover lead capture, link clicks, newsletter signups, purchases and subscriptions, with conversion count and rate per 100 or 1,000 page views, drill-down by pages, authors, sections and referrers, plus goals and an attribution discussion including linear attribution. File downloads and dynamically loaded content are trackable, but I found no public information on funnels with drop-off per step, product-level e-commerce for a shop, or conversions sent back to Google Ads or Meta — and conversions are a separately purchased module sold in bundles of 20 labels. 8 9 14
The Growth Analyst
Conversion labels cover lead capture, link clicks including outbound sites and file downloads, newsletter signups, one-time purchases and recurring subscriptions, with conversion count, converting visitors, rate per 100 page views, drilldown by pages, authors, sections and referrers, goals, and attribution models including linear attribution — sold in bundles of twenty labels as a paid add-on. We found no public information on funnels with drop-off per step, revenue per order reconciled with a shop system, cohorts and retention beyond new-versus-returning visitors, or conversions sent back to ad platforms, which is exactly the funnel-and-revenue layer my signup tracking depends on. 8 9 10 14
The Public-Sector Site Owner
Content Conversions are documented with labels for lead capture, link clicks that cover outbound links and file downloads, newsletter signups, purchases and subscriptions, per-label counts and conversion rates, a drilldown by pages, authors, sections and referrers, and references to attribution models including linear attribution. We found no public information on funnels with drop-off per step or on revenue reporting, so the form-abandonment analysis my office needs is not covered by what we read. 8 9
The Skeptic
Content Conversions are documented with goals and conversion types covering form fills, link clicks, newsletter signups, purchases and subscriptions, a drilldown by pages, authors, sections and referrers, and a linear attribution model; file downloads are handled through dynamic tracking. We found no public information on funnels with drop-off, cart- and checkout-level e-commerce, cohorts or conversion send-back to ad platforms — and conversions themselves are an add-on sold in bundles of twenty labels at additional cost through the Relationship Manager. 8 9 14
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
There are real minimisation switches — IP tracking can be disabled with the address hashed before storage, only first-party cookies are set, and an opt-out plus the GPC signal are respected — and the privacy documentation is thorough. But there is no consent-free counting mode: the vendor itself recommends loading the tracker only after consent, visitors who refuse cookies collapse into a single OPTOUT visitor, Do Not Track goes unanswered, and customer data is aggregated for the vendor's own web-wide attention studies. 3 10 11
The Data Protection Officer
The privacy documentation is candid: the fields collected by default are listed — IP address, user agent and a first-party visitor identifier — the visitor cookie runs 13 months, and IP tracking can be disabled per site or visitor, after which the address is hashed before storage. But this is a consent product: the vendor states the most privacy-conscious implementation is to load the tracker only after consent, page views still fire for cookie-rejecting visitors and all of them are counted as one visitor, the policy states do-not-track signals are not responded to, and customer data is aggregated and anonymised for the vendor's own web-wide attention studies. We found no public information on the vendor's reading of §25 TDDDG, a consent exemption, or retention settings for the analytics data. 3 4 10 11
The Agency Developer
The vendor's own documentation says the most privacy-conscious implementation is to load the tracker only after consent has been obtained, and the default collection includes the IP address plus a first-party visitor cookie that uniquely identifies a browser for 13 months; visitors who reject cookies still fire a page view under an OPTOUT id. There are real settings — IP collection can be disabled per site or per visitor with hashing before storage, GPC is respected — but I found no cookieless mode, no position against §25 TDDDG or the CNIL exemption, and customer data is aggregated for the vendor's own web-wide attention studies. 3 10 11
The Growth Analyst
Visitors are identified by a first-party UUID cookie with a 13-month lifetime (or LocalStorage), the vendor itself recommends loading the tracker only after consent has been obtained, visitors who reject cookies are still counted under a shared OPTOUT identifier, and aggregated, anonymized customer data is used for web-wide attention studies; on the minimisation side, IP tracking can be disabled per site or per visitor with the address hashed before storage, Global Privacy Control is respected while Do Not Track signals are not. We found no public information on a cookieless or consent-free counting mode or any position stated against §25 TDDDG or the CNIL exemption, so for my Munich setup this would run behind a consent banner. 3 4 10 11
The Public-Sector Site Owner
The privacy controls are documented in detail — IP address tracking can be disabled per site or per visitor with the address hashed before storage, Global Privacy Control signals are respected and an opt-out link exists — but visitors are counted through a first-party cookie that uniquely identifies a browser for 13 months, the vendor recommends loading the tracker only after consent has been obtained, and customer data is aggregated and anonymised for the vendor's own web-wide attention studies. A consent-first tracker with a 13-month identifier is exactly what our council's no-banner rule rules out. 3 10 11
The Skeptic
By default a first-party visitor cookie uniquely identifies a browser for thirteen months and the vendor itself recommends loading the tracker only after consent has been obtained — the documented mode is consent-based, and a pageview still fires on opt-out, with all opting-out visitors grouped under a single pseudonymous identifier. Real controls exist (disabling IP collection, which then hashes the address before storage; first-party cookies only; a LocalStorage alternative; respect for GPC), but we found no public information on a cookieless or consent-free counting mode, the privacy policy states Do Not Track signals are not responded to, and customer data is aggregated and anonymised for the vendor's own web-wide attention studies. 3 10 11
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
A documented API plus a Data Pipeline that sends raw event-level data to a data warehouse and BI tools is the direction I need to reconcile figures with my shop backend. But raw exports are routed through Parse.ly Support, the API accepts a 1-2% error rate where the dashboard aims for exact counts, and I found no public information on a self-hosted edition, stated raw-data retention, or an import of my Google Analytics history. 1 4 13
The Data Protection Officer
There is a documented reporting API with authentication and pagination, and a Data Pipeline that sends raw event-level data to the customer's data warehouse and BI tools, with raw export options for exact counts described through support; the dashboard's export subsystem is stated to aim for the most exact counts possible while the API accepts a small typical error rate. We found no public information on a self-hosted edition, a stated retention period for raw data, importing historical data from Google Analytics, or the return and deletion of data on termination. 1 4 13
The Agency Developer
There is a fully documented reporting API with key-and-secret authentication, and a Data Pipeline that sends raw, event-level data to a data warehouse or BI tool — exactly what I want before I ever move a client off the tool; a raw export of exact counts also exists, though it runs through support. I found no public information on a self-hosted edition, an import of Google Analytics history, or what happens to the data when a contract ends. 1 4 12 13
The Growth Analyst
The Data Pipeline module sends raw, real-time, event-level data from our website and apps to our data warehouse and BI tools, and a fully documented API with key-and-secret authentication, JSON envelopes and pagination serves posts and metadata with metrics, with raw export for exact counts reachable through support. The API accepts a typical error rate of one to two percent versus the dashboard's most-exact counts, and we found no public information on a self-hosted edition, warehouse targets named by product, historical import from Google Analytics, or data return and deletion on termination. 1 4 5 13
The Public-Sector Site Owner
A Data Pipeline module is documented that sends raw event-level data from websites and apps to the customer's own data warehouse or BI tools, the reporting API is documented with authentication, pagination and error handling, and exact-count raw data export is available through support. We found no public information on a self-hosted edition, CSV export of every report, retention periods for raw data, or what happens to the data when a contract ends. 1 4 13
The Skeptic
A Data Pipeline sends raw, event-level data to the customer's own data warehouse, the reporting API is documented down to authentication, pagination and error handling, and exact-count raw exports exist — though only by reaching out to support. We found no public information on a self-hosted or on-premise edition, an import of historical data from another tool, or terms for returning or deleting data on termination, and the API itself accepts a typical 1-2% error rate in the name of performance while the dashboard aims for exact counts. 1 4 13
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
Installation is a JavaScript tracker or a WordPress plugin that injects metadata automatically, with an open-source Google Tag Manager template covering conversions, dynamic tracking and AMP, a sandbox dashboard and a specialised single-page-app tracker. For my shop nothing is documented: I found no plugin or guide for Shopware or any other shop system, the script size is not stated, SPA tracking requires support activation, and Site IDs are provisioned via support ticket after purchase. 11 14 15
The Data Protection Officer
Installation is documented for a paste-in snippet placed in the body, a WordPress plugin that injects metadata given only a Site ID, a specialised tracker for single-page applications, and an open-source Google Tag Manager template for web and AMP containers with a sandbox dashboard for testing; named integrations include Gatsby, RebelMouse, Sitecore, Substack, News Break and Tealium. We found no public information on the script's size, team roles and permissions, single sign-on, mobile SDKs or a public status page. 14 15
The Agency Developer
For WordPress this is the best-documented install path I have seen on this panel: a plugin that installs the tracker and automatically injects metadata needing only a Site ID, an open-source Google Tag Manager template with a sandbox dashboard, a single-page-app tracker (activated via support), and dynamic tracking for infinite scroll, carousels and file downloads. I found no public information on the script's size, TYPO3 or Shopify set-ups, first-party proxying against ad blockers, team or client roles, or a public status page. 11 14 15
The Growth Analyst
The tracker is a line of JavaScript placed in the body, with a WordPress plugin that injects metadata from just a Site ID, a specialised tracker for single-page applications activated through support, dynamic tracking for infinite scroll, carousels and file downloads, and an unusually deep, open-source Google Tag Manager template covering web and AMP containers with a testing sandbox; partner integrations include Gatsby, Sitecore, Substack and Tealium. We found no public information on the script's size, team roles and permissions, single sign-on, SDKs for tracking our own mobile app, or a public status page. 3 14 15
The Public-Sector Site Owner
Installation paths are documented: a JavaScript tracker placed at the end of the body, a WordPress plugin that injects metadata from a single Site ID, a specialised single-page-application tracker activated through support, a sandbox dashboard for pre-production traffic, and an open-source Google Tag Manager template for web and AMP containers with conversion and dynamic-tracking tags. We found no public information on the tracker's file size, mobile SDKs, team roles and permissions, or single sign-on. 14 15
The Skeptic
Installation is documented around a JavaScript snippet, a WordPress plugin that injects metadata from just the Site ID, a single-page-application tracker requiring activation by support, and an open-source Google Tag Manager template with AMP, conversion and dynamic-tracking tags, alongside named partners such as Tealium, Sitecore and Substack. We found no public information on script size or measured performance impact, mobile SDKs, server-side collection, team roles, single sign-on or a public status page, and Site IDs are provisioned by support ticket only after purchase. 14 15
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
The contracting entity is WPVIP Inc. under parent Automattic with New York governing law, and every visit is immediately processed and archived long-term in United States data centers in Virginia and Oregon, with backups in Virginia and Ohio on AWS; transfers rest on the EU-US Data Privacy Framework and standard contractual clauses. No EU hosting option, self-hosted edition or full subprocessor list is published — for my German and Austrian shops the whole chain runs through the US. 2 3 10
The Data Protection Officer
The contracting entity is WPVIP Inc. under New York law with Automattic as parent, and visitor data is processed and stored long-term in United States data centres in Virginia and Oregon, with backups in Virginia and Ohio on AWS, whose infrastructure carries the ISO 27001 scope; transfers rest on consent, standard contractual clauses and the EU-US Data Privacy Framework certification held by Automattic Inc. We found no public information on EU hosting, an EU contracting entity, a subprocessor list with locations, or a published data processing agreement, so the entire visitor-data chain sits in the United States. 2 3 4 10 11
The Agency Developer
The contracting entity is WPVIP Inc. under New York law with Automattic as parent, and every page view is processed, archived and backed up in US data centers in Virginia and Oregon (backups in Virginia and Ohio) on AWS, with transfers covered by consent or standard contractual clauses and the EU-U.S. Data Privacy Framework. I found no public information on EU hosting, a subprocessor list, a data processing agreement, or a self-hosted edition — a hard stop for my German public-sector clients. 2 3 4 10
The Growth Analyst
The contracting entity is WPVIP Inc. under New York law with Automattic as parent, and visitor data is immediately processed, archived and stored long-term in US data centers in Virginia and Oregon with backups in Virginia and Ohio on AWS, with EEA transfers covered by the EU-US Data Privacy Framework or standard contractual clauses and SOC 2 and ISO 27001 certifications stated. We found no public information on EU hosting, a subprocessor list beyond AWS, or a published data processing agreement, so the entire chain would sit outside the EU for us. 2 3 4 10 11
The Public-Sector Site Owner
Every captured page points the visitor-data chain to the United States: events are processed and stored long-term in data centers in Virginia and Oregon on Amazon Web Services, backups sit in Virginia and Ohio, and the contracting entity is WPVIP Inc. under site terms governed by New York law, with separate product terms for the analytics service and transfers relying on consent or standard contractual clauses. We found no public information on EU hosting, a subprocessor list, a data processing agreement or a self-hosted edition, so nothing in this chain can run on our municipal data centre in Germany. 2 3 4 10
The Skeptic
Every visitor record is processed, archived and stored long-term in US data centres in Virginia and Oregon, with backups in Virginia and Ohio on AWS, under contracting entity WPVIP Inc., New York governing law and parent Automattic — a US chain end to end, with the only stated safeguards for Europe being consent or standard contractual clauses plus the parent's Data Privacy Framework certification. We found no public information on EU hosting options, a data processing agreement, or the remaining subprocessors such as the provider behind the global CDN. 2 3 10
Pricing transparency
not rated — the vendor publishes no price
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 captured pages show no prices at all — the homepage links a pricing page without figures, Content Conversions are available at an additional cost by contacting the Relationship Manager and are sold in bundles of 20 labels, and additional SLAs and Site provisioning run through support. I cannot compute an annual cost from anything published, and no free tier or starting price appears on the captured pages. 1 8 9 14
The Data Protection Officer
We found no public prices: the homepage links to a pricing page without stating figures, Content Conversions are available at an additional cost through the Relationship Manager, additional service level agreements are offered, and Site IDs are provisioned by support ticket following purchase; the only pricing detail we found is that conversions are typically sold in bundles of 20 labels. A buyer cannot compute an annual cost from the captured pages. 1 4 8 9 14
The Agency Developer
The captured pages show a pricing link in the navigation but not a single figure: Content Conversions are "available at an additional cost" with "Contact your Relationship Manager for more information on pricing and functionality", sold in bundles of 20 labels, and Site IDs are provisioned by support ticket after purchase. I cannot compute an annual cost for a client site from public information, so I have no way to tell a client what happens to the bill when one of their posts goes viral. 1 8 9 14
The Growth Analyst
We found no price figures on the captured pages — a pricing page is linked in the navigation but the homepage states none — while Content Conversions are available at an additional cost with the instruction to contact your Relationship Manager for pricing, labels are sold in bundles of twenty, additional service level agreements are offered, and Site IDs are provisioned via support ticket only after purchase. Nothing here lets me compute an annual cost for a given traffic level; it reads as a fully sales-led motion. 1 4 8 9 14
The Public-Sector Site Owner
We found no price figures on any page we read: a pricing link appears in the navigation without numbers, Content Conversions are "available at an additional cost" with pricing only from the Relationship Manager, conversions are sold in bundles of 20 labels with no price attached, and additional service level agreements are offered without prices. A procurement office could not compute an annual cost from this material. 1 4 8 9
The Skeptic
The captured pages state no prices: the homepage links a pricing page without figures, Content Conversions are "available at an additional cost" from the Relationship Manager in bundles of twenty labels, and additional SLAs are offered. We found no public information on tiers, traffic-based scaling, included sites or users, or a free tier — a buyer cannot compute an annual cost from anything we captured. 1 8 9
European sovereignty — proven facts
1 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
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location | Outside the EU | 0/4 pts | 10 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Parse.ly
Is Parse.ly European?
Not determined: the vendor’s pages as captured do not say where Parse.ly is based.
Where does Parse.ly store data?
Parse.ly stores customer data outside the EU by default, per the vendor’s page captured 17 Nov 2026.
Does Parse.ly have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Parse.ly?
As of 11 Nov 2026, the panel rates Matomo (4/5), etracker Analytics (4/5) and Piwik PRO Analytics Suite (3.5/5) highest among the other 21 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 etracker Analytics (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Parse.ly alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- 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.
- 12 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
- 8 integrations 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
- 4 legal 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 pricing 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
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.parse.ly Checked 17 Nov 2026 Details →
- 2 Terms of service — found from the homepage www.parse.ly Checked 17 Nov 2026 Details →
- 3 Privacy policy — found from the homepage www.parse.ly Checked 17 Nov 2026 Details →
- 4 Security / trust page — found from the homepage www.parse.ly Checked 17 Nov 2026 Details →
- 5 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
- 6 Traffic, sources & campaign reports — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 7 Traffic, sources & campaign reports — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 8 Goals, events, funnels & e-commerce — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 9 Goals, events, funnels & e-commerce — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 10 Consent-free operation & data minimisation — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 11 Consent-free operation & data minimisation — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 12 Data access, export & self-hosting — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 13 Data access, export & self-hosting — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 14 Installation, integrations & performance — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →
- 15 Installation, integrations & performance — found from sitemap docs.parse.ly Checked 17 Nov 2026 Details →