Adobe Analytics vs Matomo

Often yes, in part: if your pages load Adobe's tag layer and Analytics collection through it, switching the destination is a tag change, but every data element, rule and extension built on that layer must be rebuilt or retired. To test this, list every tag container on your sites, every data element that writes to props, eVars and events, and the teams who edit rules. Then ask whether a self-hosted Matomo tag (set through a standard tag manager) can carry the same events. Matomo covers page and event tracking, goals and custom dimensions, but you should confirm that each Adobe-specific rule maps to something Matomo can express. Replacing the layer means re-testing each tag on staging, and that work recurs whenever a page template changes.

They can, and this is one of the less visible lock-in points. Audiences built in Adobe Audience Manager or Target often use Analytics segments as their source, so the same definitions drive personalization and reporting. To test it, export a list of active Target activities and Audience Manager traits, then check which ones reference Analytics segments or report suites. If an audience feeds an ad platform or a personalization engine through Adobe, you need a replacement for the activation step, not just the measurement step. Matomo can segment visitors and exports data through its APIs, but it does not replace an audience activation service, so confirm with your marketing technology owner whether another tool will take over that job before you retire the Adobe audiences.

If your Adobe Experience Platform pipeline sends web events to Customer Journey Analytics, the dependency sits in the data model, not only in the dashboards. To check it, identify which datasets and connections feed Experience Platform, which downstream consumers read them, and whether any of them expect Analytics report suites or the Analytics schema. Adobe's guidance cited in our research, summarized on the Adobe Analytics to Customer Journey Analytics page, is that implementers should avoid locking into the Adobe Analytics schema, which suggests the event model is the thing to decouple. A self-hosted option means re-implementing the event collection once and writing a separate export into your warehouse, which is an engineering project with its own testing and ownership.

Executive dashboards are usually the hardest dependency to move, because the people who read them rarely use the tool directly. Start by listing every Analysis Workspace project that is shared, scheduled as a report, or linked from a board pack or internal portal, along with its owner and refresh schedule. Then compare each metric and breakdown against what Matomo's reports and custom reports produce. Matomo covers common web metrics well, but advanced Workspace features such as flexible attribution and multi-dimensional fallout views may not have a direct equivalent, so mark each as a gap to confirm. Expect to rebuild the most important dashboards in the new tool and to agree on definitions with finance and marketing before the old figures are retired.

Frequently, yes. Analytics may be sold alongside Target, Audience Manager, Experience Platform or a wider Experience Cloud agreement, so cancelling Analytics alone may not reduce the bill. To test this, read the order form and the renewal schedule with procurement, and ask Adobe in writing what each product line costs and what the termination and data retention terms are. Note the retention deadline that applies to your historical data, because it sets your timeline. Once bundled products are separated, you can compare the remaining Adobe cost against the self-hosted costs, which include servers, storage, upgrades, support and internal analyst time. Ask for the terms in writing rather than assuming a saving.

If analysts or finance pull Analytics data from Adobe-hosted data feeds or Data Warehouse exports into a warehouse, that pipeline is a dependency even if nobody opens Workspace. To find it, ask the data team which jobs load Analytics files, where they land, which tables and dashboards read them, and who receives the alerts when they fail. Replacing the feed means choosing where the event history will live, whether in a self-hosted warehouse or the Matomo database, and then rewriting each downstream job. Matomo exposes data through its reporting APIs and can be connected to a warehouse, but the transformation work is yours, so confirm the exact export shape with your data engineers before planning the cutover.

The Matomo software itself carries no license fee, so the cost is the infrastructure, the implementation work, the premium plugins you choose to buy, and the internal time your team spends. Infrastructure is one recurring cost, and it scales with traffic: Matomo's requirements FAQ sizes a single server with at least 4 CPUs, 8 GB of RAM and 250 GB of SSD for up to 1 million pageviews a month, and recommends separate app and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million. Implementation, tag switching and history replay are largely one-time. Your current Adobe contract and any retention extension are the figures to set against these, so ask Adobe for the exact terms in writing. For a line-by-line breakdown, see the cost comparison page under this hub.

The timeline is set mainly by two dates: the retention deadline in your Adobe contract, which controls how long you can still export raw data, and the scope of the historical export you decide to keep. Confirm the retention end date with Adobe first, because it fixes the window for pulling raw data feeds and any Data Warehouse exports. After that, the work depends on how many props, eVars and events you map to Matomo custom dimensions and goals, how many sites and tag containers you run, and how much history you replay. No duration is set here; ask for a schedule built from your own inventory of implementation variables and sites.

Plan for three roles that the work cannot do without. An analyst owns the reporting requirements, decides which Adobe reports and segments must be rebuilt, and signs off on the mapping of props, eVars and events to Matomo dimensions and goals. A server owner runs the application and database hosts, handles network access, backups and patching, and is the person who approves the sizing. A tag owner controls the tag manager containers and the site code, and switches the tracking calls over without breaking pages. In smaller organizations one person may hold two roles, but each role still needs time from someone accountable for it. Ask any implementation partner to name who fills each role in the written scope.

A small team can do it alone if it has someone comfortable with a PHP and MySQL or MariaDB stack, someone who can change the tag manager and site code, and an analyst who can rebuild the reports that matter. The harder parts are sizing and running the servers, replaying history through the bulk Tracking API, and keeping the consent setup correct for your markets. Matomo's requirements also depend on the version: Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer. Teams that lack one of these skills often bring in outside help for those specific tasks only, and that help should be scoped in writing.

No ready-made importer for Adobe Analytics data is supplied for this comparison, so you should confirm the path with Matomo and your implementation partner before you plan around it. The approach described for this migration is to export raw history through Adobe's data feeds, replay it into Matomo with the bulk Tracking API, and map the old variables to Matomo custom dimensions and goals. Matomo's Google Analytics Importer shows the limits of a different route: it brings over aggregated reports only, so the Visitor Log and segmentation do not work on imported data. Ask whether replayed raw hits will support the segments and logs you need, and what fidelity you lose.

Matomo can fit within the consent exemption that France's CNIL describes for audience measurement, but only if your configuration meets the conditions, and the exemption is not automatic. The CNIL conditions include limiting purposes to audience measurement and A/B testing, a single publisher scope, no cross-checking with other processing, truncating the last byte of the IP address and a tracker lifetime of at most 13 months. Adding User ID, heatmaps or session recordings removes the exemption, according to Matomo's own ePrivacy FAQ. The CNIL also states that most large audience measurement offerings fall outside the exemption regardless of configuration. Have counsel confirm your setup in each market, including Italy, the Netherlands and Spain.

Analysis Workspace features such as its drag-and-drop freeform tables, cross-report calculations and certain attribution models do not have one-to-one equivalents in Matomo, and some depend on Adobe's stitching across Experience Cloud products. Matomo offers its own reports, segmentation and custom reports, and paid plugins such as Heatmap and Session Recording, which is sold under a separate commercial license and removes the consent exemption when used. Make a feature inventory before you commit: list each dashboard, calculated metric and Experience Cloud integration you depend on, then mark each one as rebuilt, replaced, accepted as lost or kept on Adobe. Ask the implementation partner to deliver that inventory as part of the written scope.

DeployOpen works on fixed scope agreed in writing before any work starts. The written scope should name the sites and tag containers, the variables to map, the historical data to replay, the servers to build, the consent configuration, the test and cutover steps, and the training and handover. The quote follows from that scope, and DeployOpen does not publish a price list. Ask for a fixed price tied to each deliverable, a list of what is excluded, and the responsibilities of your analyst, server owner and tag owner. Ongoing upgrades, backups and support can be covered by a retainer, which you should price separately. DeployOpen prepares systems and evidence for compliance assessments but does not issue audit reports or certifications.