Recherche avancée

Sur d’autres sites (4243)

• Piwik 2.10.0 – Release Candidate

  22 décembre 2014, par Piwik Core Team — Community

  We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

  How do I upgrade to the release candidate ?

  You can upgrade to the release candidate in one click, by following instructions in this FAQ.

  Think you’ve found a bug ?

  Please create a bug report in our issue tracker.

  What’s new in Piwik 2.10.0 ?

  Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

  Much improved Log Analytics

  Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

  Better scalability using Redis (advanced users)

  At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

  Better performance

  A few performance challenges have been fixed in this release.

  The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

  For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

  Other changes

  We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

  The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

  If you need professional support or guidance, get in touch with Piwik PRO.

  Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

  Happy Analytics, and we wish you a nice holiday season !

• Piwik 2.10.0 – Release Candidate

  22 décembre 2014, par Piwik Core Team — Community

  We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

  How do I upgrade to the release candidate ?

  You can upgrade to the release candidate in one click, by following instructions in this FAQ.

  Think you’ve found a bug ?

  Please create a bug report in our issue tracker.

  What’s new in Piwik 2.10.0 ?

  Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

  Much improved Log Analytics

  Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

  Better scalability using Redis (advanced users)

  At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

  Better performance

  A few performance challenges have been fixed in this release.

  The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

  For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

  Other changes

  We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

  The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

  If you need professional support or guidance, get in touch with Piwik PRO.

  Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

  Happy Analytics, and we wish you a nice holiday season !

• 5 questions you should ask yourself before defining a custom alert in Matomo

  24 janvier 2018, par InnoCraft

  In Matomo, you can create Custom Alerts to automatically be notified of important changes on your website or app. They are a great way to save time, but they also spam your mailbox quickly. Defining good custom alerts takes therefore time and requires some preparations. Here are recommendations on what you should focus on to only get the right alerts at the right time.

  There are several questions you should ask yourself before you define a custom alert :

  1. Do you really want to be alerted ? If the answer is no, then do not use this feature.
  2. What is the level of this alert ? Not important, interesting, highly critical… if it is not highly critical, do not define an alert for this. Probably the emailing report or custom reports feature will be a better fit.
  3. How would you like to be alerted ? SMS, email, sound, homing pigeon (unfortunately we do not support this feature at that time). If you are looking at your emails once a week, then defining a daily email alert won’t make sense.
  4. How would you like the alert to be named ? Give your alert the most explicit name, that’s the first information you will see when you get alerted.
  5. What will be the next step once the alert is triggered ? If you cannot find any action once the alert is triggered, then probably an alert doesn’t make sense.

  Once those questions are answered, you can start configuring custom alerts. There are many alerts you can define but as just mentioned, which alerts you should create always depends on your goals and what is critical to you, or your business. Let’s look at some custom alerts that we see quite often.

  No visit

  One of the easiest custom alert to define. You probably want to be alerted if your website did not receive any visit. As this alert is highly critical, you will want to receive an e-mail, even an SMS. This alert will trigger only if the number of visits is below 1 on a daily basis :

  

  Here the action we will take is to have a look at the website in order to see if it is still live. If the site still works, we will look at the tracking code in order to see if the website is still correctly tracked or not.

  Convinced of this custom alert ? Let’s look at another example.

  Target achieved

  Let’s say you gave a goal to one of your employee to reach a specific threshold in terms of conversions. You can then define a custom alert in order to inform you when the threshold has been reached.

  You can simply do this with an alert saying “Target achieved by Franck” where number of conversions equals the number of actions you defined with him. It takes you only a minute to define something you would have missed otherwise.

  

  Here the actions we can think of are either to congratulate Franck or to ask him what is going wrong if the target is not achieved.

  Did you know that you can also take advantage of Matomo premium features to define custom alerts ? Let’s see one of them.

  Lost SEO ranking

  If you are using the Search Engine Keyword Performance premium feature, there are really interesting combinations you can use to create custom alerts.
  For example, you can be notified when a specific keyword lost or reached a position :

  

  You will be alerted when your website is losing some positions within the search engine results for specific keywords. Here the action we could take is to investigate why we lost a position on Google for this keyword.

  There are many custom alert combinations waiting for you out there. Why not giving them a try ? If you have any questions, feel free to ask them on the Matomo forums.

  The post 5 questions you should ask yourself before defining a custom alert in Matomo appeared first on Analytics Platform - Matomo.