Recherche avancée

Sur d’autres sites (3027)

• 5 perfect feature combinations to use with Heatmaps and Session Recordings

  28 janvier 2020, par Jake Thornton — Uncategorized

  Gaining valuable insights by simply creating a heatmap or setting up recordings on your most important web pages is a good start, but using the Heatmaps and Session Recordings features in combination with other Matomo features is where the real magic happens.

  If you’re serious about significantly increasing conversions on your website to impact your bottom line, you need to accurately answer these questions :

  1. Are you analysing the most important pages that influence conversions ?
  2. Are you segmenting heatmaps and recordings towards your most valuable visitors ? 
  3. Are you using these features to create better customer journeys ?
  4. Have you identified current pain points for visitors before setting up heatmaps and recordings ?
  5. Are you learning what content resonates best for your audience ?

  With Matomo Analytics, you have the ability to integrate heatmaps and session recordings with all the features of a powerful web analytics platform, which means you get the complete picture of your visitor’s experience of your website.

  Here are five features that work with Heatmaps and Session Recordings to maximise conversions :

  1. Behaviour feature with Heatmaps

  Before creating heatmaps on pages you think are most important to your website, first check out Behaviour – Pages. Here you get valuable information around unique pageviews, bounce rate, average time on page and exit rates for every page on your website.

  Use this data as your starting point for heatmaps. Here you’ll identify current pain points for your visitors before using heatmaps to analyse their interactions on these pages.

  Here’s how to use the behaviour feature to determine which pages to setup heatmaps on :

  

  • Make sure you know what pages are generating the most unique page views, it could be your blog rather than your homepage
  • Which pages have the highest bounce rates – can you make some quick changes above-the-fold and see if this makes a difference
  • When the average time on page is high, why are visitors so engaged with these pages ? What keeps them reading ? Setup a heatmap to learn more
  • Reduce exit rates by moving them along to other pages on your website
  • Determine some milestones you want to achieve e.g. use heatmaps as your visual guide to improve average time on page, bounce rates and exit rates. A milestone could be that the exit rate for your previous blog was 34%, work towards getting this down to 30%

  Learn more about the Behaviour feature

  2. Ecommerce feature and Custom Segments

  If you run an ecommerce business, you may want to learn only about visitors who are more likely to be your customers. For example, if you find 65% of product sales come from customers based in New York, but visits to your product pages are from every state in the USA, how can you learn more specifically about visitors only from New York ?

  Using Segments to target a particular audience :

  • First, make sure you have created heatmaps and recordings on the popular product pages you want to learn about your visitor’s interactions
  • Note : Make sure the segment you create generates enough pageviews to apply a heatmap for more accurate results. We recommend a minimum of 1,000 page views per sample size.
  • Then create a custom Segment – search Ecommerce and find the Product Name and select the product. Learn how to do this here.

  

  Click on ‘Add a new segment’ or on the ‘edit’ link next to an existing segment name to open the segment editor :

  

  Click on any item on the left to see the list of information you can segment by. In this case search “City”, then select “Is” and in the third column search “New York” (example in the image above) :

  

  You can also use the search box at the bottom to search through the whole list.

  • This will give you insights across the Matomo platform based only on customers who purchased this product
  • Then go to the Ecommerce feature – and find Sales. Here you will learn what your most popular locations are for your product sales.

  

  • Once you know the location you want to segment, go back and update the custom Segment you just created. Click on the edit pencil icon and update it by selecting Add AND condition, and add the sub group you would like to track on the product page. In this example, select City – New York. Click Save & Apply.

  Now you should have successfully created a segment for your popular product page with visitors only from New York.

  Check out the heatmap or recordings you created for this page. You may be very surprised to see how this segment engaged with your website compared to all website visitors.

  Note : If you run a lead generation website you can use the Goals feature instead of Ecommerce to track the success metrics you need.

  Learn more about Segmentation

  3. Visitor Profiles within Session Recordings

  Seeing visitor location, device, OS and browser for your recordings is very valuable, but it’s even more valuable to integrate visitor profiles with session recordings as you get to see everything that visitor has done on your website … ever ! 

  What pages they visited before/after the recording, what actions they took, how long they spent on your website etc. All this is captured in the visitor profile of every individual session recording so you can see where exactly engaged viewers are in their journey with your business, for example :

  • How has this visitor behaved on your website in the past ? 
  • Is this visitor already a customer ? 
  • Is this the visitors first time to your website and
  • What other pages on your website are they interested in seeing in this session ?

  Use the visitor profiles feature within session recordings to understand the users better when watching each session.

  You get the full picture of what role the page you recorded played in the overall experience of your website’s visitor. And more importantly, to see if they took the desired action you wanted them to take.

  

  Learn more about Visitor Profiles

  4. Funnels feature (premium feature)

  The Funnels feature lets you see the customer journey from the first entry page through to the conversion page.

  

  Once you create a funnel, you can see the % of visitors who drop off between pages on their way to converting.

  In our example, you may then see page one to page two has a drop-off rate of 47%. Page two to page three 95% users drop-off rate and page three to page four 97.3% users drop-off rate.

  Why is the drop-off rate so high from page two to page three and why is the drop-off rate so low from page three to page four ?

  So, you may need to simplify things on page one because you may unknowingly be offering your visitor an easy way out of the funnel. Maybe the visitor is stuck reading your content and not understanding the value of your offering.

  Small tip for session recordings …

  With session recordings especially you can see firsthand through live recordings where exactly visitors click away from the page which exits them from your conversion funnel. Take note to see if this is a recurring issue with other visitors, then take action into fixing this hole.

  Whatever the case, work towards reducing drop-off rates through your conversion funnels by discovering where the problems exist, make changes and learn how these changes affect engagement through heatmaps and recordings.

  Learn more about Funnels

  5. A/B Testing feature (premium feature)

  Following on from the example with the Funnels feature, once you identify there is a problem in your conversion funnel, how do you know what is preventing visitors from taking an action that pushes them to the next page in the funnel ? You need to test different variations of content to see what works best for your visitors.

  A/B Testing lets you test a variety of things, including :

  • different headlines 
  • less copy vs more copy 
  • different call-to-actions
  • different colour schemes
  • entirely different page layouts

  

  Once you’ve created two or more variations of specific landing pages in the conversion funnel, see how visitors interacted differently between the variations of landing pages through your heatmaps and recordings.

  

  You may see that your visitors have scrolled further down the page because more content was provided or an important CTA button was clicked more due to a colour change. Whatever the case, using A/B testing with heatmaps and session recordings is an effective combination for increasing user engagement.

  Learn more about A/B Testing

  The conversion rate optimization (CRO) strategy

  CRO is the process of learning what the most valuable content/aspect of your website is and how to best optimize this for your visitors to increase conversion chances. 

  Heatmaps and session recordings play a vital role in this strategy, but it’s how you work these features in tandem with other valuable Matomo features that will give you the most actionable insights you need to grow your business.

  Want to learn how to create an effective CRO strategy ?

  Learn CRO strategies

• How to publish your plugin or theme on the Piwik Marketplace – Introducing the Piwik Platform

  25 septembre 2014, par Thomas Steur — Community, Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform. Over the last weeks we have already introduced you to some of the basics on how to create plugins and themes. This time you’ll learn how to publish a plugin or theme on the Piwik Marketplace to share it with all Piwik users.

  What is the Piwik Marketplace ?

  The Marketplace is a showcase for all plugins and themes that can be used in Piwik. You can browse them either on a standalone website or in Piwik itself by going to Settings => Marketplace. There you can install and update them with just one click. Easy as that ! While some of those plugins are provided by Piwik or Piwik PRO most of them are created and maintained by our community. Everyone is very welcome to distribute plugins or themes on the Marketplace.

  Prerequisites

  To publish your plugin on the Marketplace you simply need to meet these requirements :

  • The plugin name is not already taken by another plugin
  • The code of the plugin is hosted in a public GitHub repository
  • The GitHub service “Piwik plugins” for this repository is enabled (Repository Settings => Webhooks & Services => Add Service)
  • Push permission for this repository
  • The plugin is free (as in not paid)
  • The license must be compatible with the GNU General Public License v3 or any later version

  There is also list of Rules for plugins.

  Best practices

  Before actually distributing your plugin we recommend to follow a couple of best practices to make sure your plugin looks good on the Marketplace and provides useful information for your future users. If you have used the console to generate a plugin the needed files were already created for you.

  Provide a good description

  Make sure there is a file named README.md in the root of your plugin. When preparing your plugin for the Marketplace we will search for four sections in this file : Description, FAQ, Changelog and Support. Each of those is optional but it is good practice to provide at least a section Description and Support by prefixing them with ## . Any content of your readme outside of those sections will not be displayed on the Marketplace.

  # Piwik Plugin Name
  
  
  
  ## Description
  
  
  
  Add your plugin description here.
  
  
  
  ## Support
  
  
  
  Please direct any feedback to hello@piwik.org. 
  
  If you experience any issues feel free to file an issue at https://github.com/piwik/piwik/issues .

  A good example can be seen in the README.md of the CustomAlerts plugin and the related CustomAlerts plugin page.

  Provide screenshots

  This will improve your appearance in the Marketplace a lot and users will be more likely install your plugin. It is as easy as placing “png” or “jpg” files in a folder named screenshots. The filename of each image will be shown in the UI with underscores replaced by a whitespace. This way you can provide a nice description. Have a look at the CustomAlerts plugin to see how it works.

  Provide contact details

  Your contact details are specified in the plugin.json file of your plugin root folder. Providing at least one author and a link to your homepage is required. If you do not have a website you can use a link to your GitHub profile. This helps your users contact you in case they want to thank you for your great work or if they have any problem with it. An example plugin.json looks like this :

  {
  
      "name": "MyPluginName",
  
      "homepage": "http://piwik.org",
  
      "authors": [
  
          {
  
              "name": "Piwik",
  
              "email": "hello@piwik.org",
  
              "homepage": "http://piwik.org"
  
          }
  
      ],
  
      "support": {
  
        "email": "hello@piwik.org",
  
        "issues": "https://github.com/piwik/piwik/issues",
  
        "forum": "http://forum.piwik.org",
  
        "wiki": "https://github.com/piwik/piwik/wiki",
  
        "irc": "#piwik-dev"
  
      } 
  
  }

  Choose a license

  Choosing the right license that works best for you and your users is important. To distribute a plugin via the Piwik Marketplace the license must be compatible with the GNU General Public License v3 or any later version. If you do not specify a license anywhere in your plugin, it is assumed your plugin uses GPLv3 or later. The license must be specified in the plugin.json file using the property license :

  {
  
      "name": "MyPluginName",
  
      "license": "GPL v3+"
  
  }

  Provide donation links

  You can define a donation link or email for PayPal, Flattr and Bitcoin in the plugin.json file. Users that love your work will then be able to donate you money directly from the plugin page.

  {
  
      "name": "MyPluginName"
  
      "donate": {
  
          "paypal": "sponsor@piwik.org",
  
          "flattr": "https://flattr.com/profile/piwik",
  
          "bitcoin": "1234567890"
  
      }
  
  }

  How to publish the first version of your plugin

  We are trying to make it as easy as possible for you to publish your plugin on the Marketplace. That’s why we don’t require any logins or packaging. To publish your plugin you only have to create a new tag of your plugin and within a minute your plugin will be ready to be installed on hundreds of thousands of Piwik installations.

  To tag your plugin you can use one of the following two suggestions :

  Using the command line

  git tag 0.1.0 && git push --tags

  Where “0.1.0” is the name of the tag. While you can use any tag name it is best practice to use the current version number as defined in the plugin.json file.

  Using GitHub UI

  To tag a new version via GitHub click on Releases => Draft a new release.

  

  Now you can enter a tag name (version) and press “Publish release” as shown in this screen. That’s it !

  

  How to provide an update for your plugin

  To provide an update you only have to increase the version number in the file plugin.json and create another tag as explained in the previous section. Your new Plugin update will be visible on the Marketplace within a minute or so. It might take a bit longer until the update appears in Piwik itself as each Piwik server only checks for updates every few hours.

  For a complete list of information go to our Distributing Your Plugin guide in the Piwik Developer Zone.

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

• How to publish your plugin or theme on the Piwik Marketplace – Introducing the Piwik Platform

  25 septembre 2014, par Thomas Steur — Community, Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform. Over the last weeks we have already introduced you to some of the basics on how to create plugins and themes. This time you’ll learn how to publish a plugin or theme on the Piwik Marketplace to share it with all Piwik users.

  What is the Piwik Marketplace ?

  The Marketplace is a showcase for all plugins and themes that can be used in Piwik. You can browse them either on a standalone website or in Piwik itself by going to Settings => Marketplace. There you can install and update them with just one click. Easy as that ! While some of those plugins are provided by Piwik or Piwik PRO most of them are created and maintained by our community. Everyone is very welcome to distribute plugins or themes on the Marketplace.

  Prerequisites

  To publish your plugin on the Marketplace you simply need to meet these requirements :

  • The plugin name is not already taken by another plugin
  • The code of the plugin is hosted in a public GitHub repository
  • The GitHub service “Piwik plugins” for this repository is enabled (Repository Settings => Webhooks & Services => Add Service)
  • Push permission for this repository
  • The plugin is free (as in not paid)
  • The license must be compatible with the GNU General Public License v3 or any later version

  There is also list of Rules for plugins.

  Best practices

  Before actually distributing your plugin we recommend to follow a couple of best practices to make sure your plugin looks good on the Marketplace and provides useful information for your future users. If you have used the console to generate a plugin the needed files were already created for you.

  Provide a good description

  Make sure there is a file named README.md in the root of your plugin. When preparing your plugin for the Marketplace we will search for four sections in this file : Description, FAQ, Changelog and Support. Each of those is optional but it is good practice to provide at least a section Description and Support by prefixing them with ## . Any content of your readme outside of those sections will not be displayed on the Marketplace.

  # Piwik Plugin Name
  
  
  
  ## Description
  
  
  
  Add your plugin description here.
  
  
  
  ## Support
  
  
  
  Please direct any feedback to hello@piwik.org. 
  
  If you experience any issues feel free to file an issue at https://github.com/piwik/piwik/issues .

  A good example can be seen in the README.md of the CustomAlerts plugin and the related CustomAlerts plugin page.

  Provide screenshots

  This will improve your appearance in the Marketplace a lot and users will be more likely install your plugin. It is as easy as placing “png” or “jpg” files in a folder named screenshots. The filename of each image will be shown in the UI with underscores replaced by a whitespace. This way you can provide a nice description. Have a look at the CustomAlerts plugin to see how it works.

  Provide contact details

  Your contact details are specified in the plugin.json file of your plugin root folder. Providing at least one author and a link to your homepage is required. If you do not have a website you can use a link to your GitHub profile. This helps your users contact you in case they want to thank you for your great work or if they have any problem with it. An example plugin.json looks like this :

  {
  
      "name": "MyPluginName",
  
      "homepage": "http://piwik.org",
  
      "authors": [
  
          {
  
              "name": "Piwik",
  
              "email": "hello@piwik.org",
  
              "homepage": "http://piwik.org"
  
          }
  
      ],
  
      "support": {
  
        "email": "hello@piwik.org",
  
        "issues": "https://github.com/piwik/piwik/issues",
  
        "forum": "http://forum.piwik.org",
  
        "wiki": "https://github.com/piwik/piwik/wiki",
  
        "irc": "#piwik-dev"
  
      } 
  
  }

  Choose a license

  Choosing the right license that works best for you and your users is important. To distribute a plugin via the Piwik Marketplace the license must be compatible with the GNU General Public License v3 or any later version. If you do not specify a license anywhere in your plugin, it is assumed your plugin uses GPLv3 or later. The license must be specified in the plugin.json file using the property license :

  {
  
      "name": "MyPluginName",
  
      "license": "GPL v3+"
  
  }

  Provide donation links

  You can define a donation link or email for PayPal, Flattr and Bitcoin in the plugin.json file. Users that love your work will then be able to donate you money directly from the plugin page.

  {
  
      "name": "MyPluginName"
  
      "donate": {
  
          "paypal": "sponsor@piwik.org",
  
          "flattr": "https://flattr.com/profile/piwik",
  
          "bitcoin": "1234567890"
  
      }
  
  }

  How to publish the first version of your plugin

  We are trying to make it as easy as possible for you to publish your plugin on the Marketplace. That’s why we don’t require any logins or packaging. To publish your plugin you only have to create a new tag of your plugin and within a minute your plugin will be ready to be installed on hundreds of thousands of Piwik installations.

  To tag your plugin you can use one of the following two suggestions :

  Using the command line

  git tag 0.1.0 && git push --tags

  Where “0.1.0” is the name of the tag. While you can use any tag name it is best practice to use the current version number as defined in the plugin.json file.

  Using GitHub UI

  To tag a new version via GitHub click on Releases => Draft a new release.

  

  Now you can enter a tag name (version) and press “Publish release” as shown in this screen. That’s it !

  

  How to provide an update for your plugin

  To provide an update you only have to increase the version number in the file plugin.json and create another tag as explained in the previous section. Your new Plugin update will be visible on the Marketplace within a minute or so. It might take a bit longer until the update appears in Piwik itself as each Piwik server only checks for updates every few hours.

  For a complete list of information go to our Distributing Your Plugin guide in the Piwik Developer Zone.

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