Recherche avancée

Sur d’autres sites (12211)

• 12 ways Matomo Analytics helps you to protect your visitor’s privacy

  5 mai 2020, par InnoCraft — Analytics Tips, Privacy, Security

  This post was originally published on January 11, 2017, and updated on May, 2020.

  At Matomo we think privacy matters. From the beginning, Matomo has had a strong focus on privacy and ensuring the privacy of your visitors and analytics data. 

  Here are some ways how you can ensure your users and visitors privacy by using Matomo (Piwik).

  1. Owning the data gives you power to protect user privacy

  Whether you host Matomo on-premises yourself, or whether you use Matomo’s cloud, YOU keep control of your data and nobody else. By knowing exactly where your data is stored and having full control over what happens to it, you have the power to protect your user’s privacy. No-one else can claim ownership. 

  2. GDPR compliance

  GDPR is one of the most important privacy laws to have come out in the last few years. As such, Matomo takes GDPR compliance very seriously. There’s even a 12-step checklist for you to follow to ensure your Matomo is GDPR compliant. Not only that Matomo is HIPAA, CCPA, LGPD, and PECR compliant.

  3. Data anonymization

  For better privacy by default, Matomo implements a range of data anonymization techniques. One of the main techniques is not recording the full IP address of your visitors. Some countries even require you to anonymize additional info considered Personally Identifiable Information (PII).

  To change the IP anonymization settings go to “Administration > Privacy”. 

  

  4. Configuring Matomo to not process personal data or personally identifiable information (PII)

  To further protect the privacy of your visitors, you can learn how to not process any personal information or PII. 

  5. Deleting old visitor logs

  The is important because visitor logs contain information all the collected raw data about every visitor and every action. You can configure Matomo to automatically delete logs from the database. When you delete old logs, only the real time and visitor log reports will no longer work for this old time period, all other aggregated reports will still work.

  For privacy reasons, we highly recommend that you keep the detailed Matomo logs for only 3 to 6 months and delete older log data. This has one other nice side effect : it will free significant database space, which will, in turn, slightly increase performance !

  

  6. Supporting the Do Not Track preference

  Do Not Track enables users to opt out of any tracking by websites they do not visit, including analytics services, advertising networks, and social platforms. By default, Matomo respects users preference and will not track visitors which have specified “I do not want to be tracked” in their web browsers. Get more information about DoNotTrack.

  To make sure Do Not Track is respected, go to “Administration => Privacy”.

  7. Including an Opt-Out Feature on your website or app

  By embedding the Opt-Out feature in your website, you give your visitors the possibility to opt-out of the tracking. When you go to “Administration > Privacy”, you will be able to copy and paste an HTML Iframe code to embed the opt-out feature for example into your privacy policy page or in your ‘Legal’ page. Your users can then click on a link to opt-out.

  On the Matomo Marketplace there are also some plugins available to customize the Opt-Out experience. For example AjaxOptOut and CustomOptOut.

  

  8. Disabling Live features

  The Real-Time, Visitor Log and Visitor Profile features give you insights into the tracked raw data by showing you details about every visitor and every action they performed. To protect the privacy of your visitors you may decide to prevent access to such features by disabling the “Live” plugin in “Administration => Plugins”. This way only aggregated reports will be shown in your Matomo.

  9. Disabling fingerprinting across websites

  By default, when one of your visitors visits several of your websites, Matomo will create a fingerprint for this user that will be different across the websites to increase the visitors’ privacy. You can make sure that this feature is disabled by going to “Administration => Config file” and verifying that the value of “enable_fingerprinting_across_websites” is set to zero.

  10. Disabling tracking cookies

  Matomo uses first-party cookies to store some information about visitors between visits. In some countries, the legislation requires websites to provide a way for users to opt-out of all tracking, in particular tracking cookies. You can disable cookies by adding one line in the Matomo Javascript code.

  11. Creating the tool of your dreams by developing your own plugins and getting access to the API

  Matomo is an open platform that lets you extend and customise the tracking ; reporting ; and user interface to your needs and to protect your visitors’ privacy the way you want or need it. Learn more in the Matomo Developer Zone. You may also have a look at our Matomo Marketplace where you can find several free and premium features to extend your Matomo.

  12. Transparency

  By default, all information and all collected data in your Matomo server are protected and nobody can access it. However, Matomo allows you to optionally make your collected data public and you can export any Matomo report including the whole dashboard to embed it into your website. This way you can show your users exactly which information you track. When you decide to make reports public, we do our best to protect privacy and automatically hide any Personally Identifiable Information such as the Visitor Profile and we make sure to not show any Visitor IP address and the Visitor ID.

  Bonus tip – A privacy policy template for you

  When you use Matomo to track your visitors, we recommend you update your Privacy Policy to explain how Matomo is used and what data it gathers. Here’s a Privacy Policy template for you to copy on your site.

  Continuous privacy improvements

  We are always interested in improving the privacy. If you miss any feature or have an idea on how to improve the privacy, please let us know.

  More information about all the Matomo features

  If you want to learn more about all the features in Matomo, have a look at our User Guides and FAQ entries.

• Unlocking the power of web analytics dashboards

  22 juillet, par Joe — Analytics Tips, App Analytics

  In the web analytics world, we have no shortage of data — clicks, views, scrolls, bounce rates — yet still struggle to extract valuable, actionable insights. There are facts and figures about any action anybody takes (or doesn’t take) when they visit your website, place an order or abandon their shopping cart. But all that data is often without context.

  That’s where dashboards come in : More than visual summaries, the right dashboards give context, reduce noise, and help us focus on what matters most — whether it’s boosting conversions, optimising campaigns, or monitoring data quality and compliance efforts.

  In this article, we’ll focus on :

  • The importance of data quality in web analytics dashboards
  • Different types of dashboards to use depending on your goals 
  • How to work with built-in dashboards in Matomo
  • How to customise them for your organisation’s needs

  Whether you’re building your first dashboard or refining a mature analytics strategy, this guide will help you get more out of your data.

  What is a web analytics dashboard ?

  A web analytics dashboard is an interactive interface that displays key website metrics and data visualisations in an easy-to-grasp format. It presents key data clearly and highlights potential problems, helping users quickly spot trends, patterns, and areas for improvement.

  Dashboards present data in charts, graphs and tables that are easier to understand and act upon. Users can usually drill down on individual elements for more detail, import other relevant data or adjust the time scale to get daily, weekly, monthly or seasonal views.

  Types of web analytics dashboards

  Web analytics dashboards may vary in the type of information they present and the website KPIs (key performance indicators) they track. However, sometimes the information can be the same or similar, but the context is what changes.

  Overview dashboard

  This offers a comprehensive overview of key metrics and KPIs. For example, it might show :

  • Traffic metrics, such as the total number of sessions, visits to the website, distinct users, total pages viewed and/or the average number of pages viewed per visit.
  • Engagement metrics, like average session duration, the bounce rate and/ or the exit rate by specific pages.
  • Audience metrics, including new vs. returning visitors, or visitor demographics such as age, gender or location. It might also show details of the specific device types used to access the website : desktop, mobile, or tablet.

  An overview dashboard might also include snapshots of some of the examples below.

  Acquisition dashboard

  This reveals how users arrive at a website. Although an overview dashboard can provide a snapshot of these metrics, a focused acquisition dashboard can break down website traffic even further. 

  They can reveal the percentages of traffic coming from organic search engines, social platforms, or users typing the URL directly. They can also show referrals from other websites and visitors clicking through from paid advertising sources. 

  An acquisition dashboard can also help measure campaign performance and reveal which marketing efforts are working and where to focus efforts for better results.

  Behavioural dashboard

  This dashboard shows how users interact with a website, including which pages get the most traffic and how long visitors stay before they leave. It also reveals which pages get the least traffic, highlighting where SEO optimisation or greater use of internal links may be needed.

  Behavioural dashboards can show a range of metrics, such as user engagement, navigation, page flow analysis, scroll depth, click patterns, form completion rates, event tracking, etc. 

  This behavioural data lets companies identify engaging vs. underperforming content, fix usability issues and optimise pages for better conversions. It may even show the data in heat maps, click maps or user path diagrams.

  Goals and ecommerce dashboard

  Dashboards of this type are mostly used by e-commerce websites. They’re useful because they track things like sales goal completions and revenue targets, as well as conversions, revenue, and user actions that deliver business results. 

  

  The typical metrics seen here are :

  • Goal tracking (aka conversions) in terms of completed user actions (form submissions, sign-ups, downloads, etc.) will provide funnel analysis and conversion rates. It’ll also give details about which traffic sources offer the most conversions.
  • Revenue tracking is provided via a combination of metrics. These include sales and revenue figures, average order value, top-selling items, revenue per product, and refund rates. It can also reveal how promotions, discounts and coupons affect total sales.
  • Shopping behaviour analysis tracks how users move from browsing to cart abandonment or purchase.

  These metrics help marketing teams measure campaign ROI. They also help identify high-value products and audiences and provide pointers for website refinement. For example, checkout flow optimisation might reduce abandonment.

  Technical performance dashboard

  This monitors a website’s technical health and performance metrics. It focuses on how a website’s infrastructure and backend health affect user experiences. It’ll track a lot of things, including :

  • Page load time
  • Server response time
  • DNS lookup time
  • Error rates
  • Mobile optimisation scores
  • Browser usage
  • Operating system distribution
  • Network performance
  • API response times
  • Core web vitals
  • Mobile usability issues

  This information helps organisations quickly fix issues that hurt SEO and conversions. It also helps to reduce errors that frustrate users, like checkout failures. Critically, it also helps to improve reliability and avoid downtime that can cost revenue.

  Geographic dashboard

  When an organisation wants to analyse user behaviour based on geographic location, this is the one to use. It reveals where website visitors are physically located and how their location influences their behaviour. Here’s what it tracks :

  • City, country/region 
  • Granular hotspots
  • Language preferences
  • Conversion rates by location
  • Bounce rates/engagement by location
  • Device type : Mobile vs. tablet vs desktop
  • Campaign performance by location
  • Paid ads effectiveness by location
  • Social media referrals by location
  • Load times by location

  Geographic dashboards allow companies to target marketing efforts at high-value regions. They also inform content localisation in terms of language, currency, or offers. And they help identify and address regional issues such as speed, payment methods, or cultural relevance.

  Custom segments dashboard

  This kind of dashboard allows specific subsets of an audience to be analysed based on specific criteria. For example, these subsets might include :

  • VIP customers
  • Mobile users
  • New vs. returning visitors
  • Logged-in users
  • Campaign responders
  • Product category enthusiasts. 

  What this dashboard reveals depends very much on what questions the user is trying to answer. It can provide actionable insight into why specific subsets of visitors or customers drop off at certain points. It allows specific metrics (bounce rate, conversions, etc.) to be compared across segments. 

  It can also track the performance of marketing campaigns across different audience segments, allowing marketing efforts to be tailored to serve high-potential segments. Its custom reports can also assist in problem-solving and testing hypotheses.

  

  Content performance dashboard

  This is useful for understanding how a website’s content engages users and drives business goals. Here’s what it tracks and why it matters :

  • Top-performing content
    • Most viewed pages
    • Highest time-on-page content
    • Most shared/linked content
  • Engagement metrics
    • Scroll depth (how far users read)
    • Video plays/podcast listens
    • PDF/downloads of gated content
  • Which content pieces lead to
    • Newsletter sign-ups
    • Demo requests
    • Product purchases
  • SEO health
    • Organic traffic per page
    • Keyword rankings for specific content
    • Pages with high exit rates
  • Content journey analysis
    • Entry pages that start user sessions
    • Common click paths through a site
    • Pages that often appear before conversions

  All this data helps improve website effectiveness. It lets organisations double down on what works, identify and replicate top-performing content and fix underperforming content. It can also identify content gaps, author performance and seasonal trends. The data then informs content strategy and optimisation efforts.

  The importance of data quality

  The fundamental reason we look at data is to make decisions that are informed by facts. So, it stands to reason that the quality of the underlying data is critical because it governs the quality of the information in the dashboard.

  And the data source for web analytics dashboards is often Google Analytics 4 (GA4), since it’s free and frequently installed by default on new websites. But this can be a problem because the free version of Google Analytics is limited and resorts to data sampling beyond a certain point. Let’s dig into that.

  Google Analytics 4 (GA4)

  It’s the default option for most organisations because it’s free, but GA4 has notable limitations that affect data accuracy and functionality. The big one is data sampling, which kicks in for large datasets (500,000+ events). This can skew reporting because the analysis is of subsets rather than complete data. 

  In addition, user privacy tools like ad blockers, tracking opt-outs, and disabled JavaScript can cause underreporting by 10-30%. GA4 also restricts data retention to 2-14 months and offers limited filtering and reduced control over data collection thresholds. Cross-domain tracking requires manual setup and lacks seamless integration. 

  One solution is to upgrade to Google Analytics 360 GA360, but it’s expensive. Pricing starts at $12,500/month (annual contract) plus $150,000 minimum yearly spend. The costs also scale with data volume, typically requiring $150,000−500,000 annually.

  

  Matomo’s built-in dashboards

  Matomo is a better solution for organisations needing unsampled data, longer data retention, and advanced attribution. It also provides functionality for enterprises to export their data and import it into Google BigQuery if that’s what they already use for analysis.

  Matomo Analytics takes a different approach to data quality. By focusing on privacy and data ownership, we ensure that businesses have full control over all of their data. Matomo also includes a range of built-in dashboards designed to meet the needs of different users. 

  The default options provide a starting point for tracking key metrics and gaining insight into their performance. They’re accessible by simply navigating to the reports section and selecting the relevant dashboard. These dashboards draw on raw data to provide more detailed and accurate analysis than is possible with GA4. And at a fraction of the price of GA360. 

  You can get Matomo completely free of charge as a self-hosted solution or via Matomo Cloud for a mere $29/month — vs. GA360’s $150k+/year. It also has other benefits :

  • 100% data ownership and no data sampling
  • Privacy compliance by design :
    • GDPR/CCPA-ready
    • No ad-blocker distortion
    • Cookieless tracking options
  • No data limits or retention caps
  • Advanced features without restriction :
    • Cross-domain tracking
    • Custom dimensions/metrics
    • Heatmaps/session recordings

  Customisation options

  Although Matomo’s default dashboards are powerful, the real value lies in the customisation options. These extensive and easy-to-use options empower users to tailor custom dashboards to their precise needs.

  Unlike GA4’s rigid layouts, Matomo offers drag-and-drop widgets to create, rearrange or resize reports effortlessly. You can :

  • Add 50+ pre-built widgets (e.g., traffic trends, conversion funnels, goal tracking) or create custom SQL/PHP widgets for unique metrics.
  • Segment data dynamically with filters (by country, device, campaign) and compare date ranges side-by-side.
  • Create white-label dashboards for client reporting, with custom logos, colours and CSS overrides.
  • Schedule automated PDF/email reports with personalised insights.
  • Build role-based dashboards (e.g., marketing vs. executive views) and restrict access to sensitive data.

  For developers, Matomo’s open API enables deep integrations (CRM, ERP, etc.) and custom visualisations via JavaScript. Self-hosted users can even modify the core user interface.

  Matomo : A fully adaptable analytics hub

  Web analytics dashboards can be powerful tools for visualising data, generating actionable insights and making better business decisions. But that’s only true as long as the underlying data is unrestricted and the analytics platform delivers high-quality data for analysis. 

  Matomo’s commitment to data quality and privacy sets it apart as a reliable source of accurate data to inform accurate and detailed insights. And the range of reporting options will meet just about any business need, often without any customisation.

  To see Matomo in action, watch this two-minute video. Then, when you’re ready to build your own, download Matomo On-Premise for free or start your 21-day free trial of Matomo Cloud — no credit card required.

• How to add new pages and menu items to Piwik – Introducing the Piwik Platform

  11 septembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a widget). This time you’ll learn how to extend Piwik by adding new pages and menu items. For this tutorial you will need to have basic knowledge of PHP and optionally of Twig which is the template engine we use.

  What can be displayed in a page ?

  To make it short : You can display any corporate related content, key metrics, news, help pages, custom reports, contact details, information about your server, forms to manage any data and anything else.

  Getting started

  In this series of posts, we assume that you have already set up your development environment. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik.

  To summarize the things you have to do to get setup :

  • Install Piwik (for instance via git).
  • Activate the developer mode : ./console development:enable --full.
  • Generate a plugin : ./console generate:plugin --name="MyControllerPlugin". There should now be a folder plugins/MyControllerPlugin.
  • And activate the created plugin under Settings => Plugins.

  Let’s start creating a page

  We start by using the Piwik Console to create a new page :

  ./console generate:controller

  The command will ask you to enter the name of the plugin the controller should belong to. I will simply use the above chosen plugin name “MyControllerPlugin”. There should now be two files plugins/MyControllerPlugin/Controller.php and plugins/MyControllerPlugin/templates/index.twig which both already contain an example to get you started easily :

  Controller.php

  class Controller extends \Piwik\Plugin\Controller
  {
      public function index()
      {
          return $this->renderTemplate('index', array(
               'answerToLife' => 42
          ));
      }
  }
  Télécharger

  and templates/index.twig

  {% extends 'dashboard.twig' %}
   
  {% block content %}
      <strong>Hello world!</strong>
      <br/>
   
      The answer to life is {{ answerToLife }}
  {% endblock %}
  Télécharger

  Note : If you are generating the Controller before Piwik 2.7.0 the example will look slightly different.

  The controller action index assigns the view variable answerToLife to the view and renders the Twig template templates/index.twig. Any variable assigned this way can then be used in the view using for example {{ answerToLife }}.

  Using a Twig template to generate the content of your page is actually optional : instead feel free to generate any content as desired and return a string in your controller action.

  As the above template index.twig is extending the dashboard template the Logo as well as the top menu will automatically appear on top of your content which is defined within the block content.

  

  How to display the page within the admin

  If you would like to add the admin menu on the left you have to modify the following parts :

  • Extend \Piwik\Plugin\ControllerAdmin instead of \Piwik\Plugin\Controller in the file Controller.php. In a future version of Piwik this step will be no longer neccessary, see #6151
  • Extend the template admin.twig instead of dashboard.twig
  • Define a headline using an H2-element

  {% extends 'admin.twig' %}
   
  {% block content %}
      <h2>Hello world!</h2>
      <br/>
   
      The answer to life is {{ answerToLife }}
  {% endblock %}
  Télécharger

  Note : Often one needs to add a page to the admin to make a plugin configurable. We have a unified solution for this using the Settings API.

  

  How to display a blank page

  If you would like to generate a blank page that shows only your content the template should contain only your markup as follows :

  <strong>Hello world!</strong>
  <br/>
   
  The answer to life is {{ answerToLife }}
  Télécharger

  Predefined variables, UI components, security and accessing query parameters

  In this blog post we only cover the basics to get you started. We highly recommend to read the MVC guide on our developer pages which covers some of those advanced topics. For instance you might be wondering how to securely access $_GET or $_POST parameters, you might want to restrict the content of your page depending on a user role, and much more.

  If you would like to know how to make use of JavaScript, CSS and Less have a look at our Working with Piwik’s UI guide.

  Note : How to include existing UI components such as a site selector or a date selector will be covered in a future blog post. Also, there are default variables assigned to the view depending on the context. A list of those variables that may or may not be defined is unfortunately not available yet but we will catch up on this.

  Let’s add a menu item to make the page accessible

  So far you have created a page but you can still not access it. Therefore we need to add a menu item to one of the Piwik menus. We start by using the Piwik Console to create a menu template :

  ./console generate:menu

  The command will ask you to enter the name of the plugin the menu should belong to. I will use again the above chosen plugin name “MyControllerPlugin”. There should now be a file plugins/MyControllerPlugin/Menu.php which contains an example to get you started easily :

  Menu.php

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          // reuse an existing category. 
          $menu->addManageItem('My User Item', $this->urlForAction('showList'));
   
          // or create a custom category
          $menu->addItem('My Custom Category', 'My User Item', $this->urlForDefaultAction());
      }
  }
  Télécharger

  This is only a part of the generated template since all the examples of the different menus are similar. You can add items to four menus :

  • configureReportingMenu To add a new item to the reporting menu which includes all the reports like “Actions” and “Visitors”.
  • configureAdminMenu To add a new item to the admin menu which includes items like “User settings” and “Websites”.
  • configureTopMenu To add a new item to the top menu which includes items like “All Websites” and “Logout”.
  • configureUserMenu To add a new item to the user menu which is accessible when clicking on the username on the top right.

  In this blog post we will add a new item to the user menu and to do so we adjust the generated template like this :

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          $menu->addManageItem('My User Item', $this->urlForAction($method = 'index'), $orderId = 30);
      }
  }
  Télécharger

  That’s it. This will add a menu item named “My User Item” to the “Manage” section of the user menu. When a user chooses the menu item, the “index” method of your controller will be executed and your previously created page will be first rendered and then displayed. Optionally, you can define an order to influence the position of the menu item within the manage section. Following this example you can add an item to any menu for any action. I think you get the point !

  

  Note : In Piwik 2.6.0 and before the above example would look like this :

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          $menu->addManageItem('My User Item', array($module = 'MyControllerPlugin', $action = 'index'), $orderId = 30);
      }
  }
  Télécharger

  How to test a page

  After you have created your page you are surely wondering how to test it. A controller should be usually very simple as it is only the connector between model and view. Therefore, we do usually not create unit or integration test for controllers and for the view less than ever. Instead we would create a UI test that takes a screenshot of your page and compares it with an expected screenshot. Luckily, there is already a section UI tests in our Automated tests guide.

  Publishing your Plugin on the Marketplace

  In case you want to share your page with other Piwik users you can do this by pushing your plugin to a public GitHub repository and creating a tag. Easy as that. Read more about how to distribute a plugin.

  Advanced features

  Isn’t it easy to create a page ? We never even created a file ! Of course, based on our API design principle “The complexity of our API should never exceed the complexity of your use case.” you can accomplish more if you want : You can make use of Vanilla JavaScript, jQuery, AngularJS, Less and CSS, you can reuse UI components, you can access query parameters and much more.

  Would you like to know more about this ? Go to our MVC (Model-View-Controller) and Working with Piwik’s UI guides in the Piwik Developer Zone.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.