Sur d’autres sites (8343)

• 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 !

• Evolution #3928 : les emails sont publics dans le privé

  1er juillet 2019, par b b

  Pour moi et dans le cadre de spip.net, oui.

  Maintenant, le plan est simple, il faut modifier tous les squelettes de prive/objets/liste ainsi que prive/contenu/auteur.html pour conditionner l’affichage de la colonne email dans les lites, et la ligne email dans la fiche auteur en fonction de la valeur d’une constante dont il faut définir le nom. Ensuite, si la majorité pense que cela doit-être appliqué par défaut, il suffit d’inverser le teste et zou :)

• Exceeded GA’s 10M hits data limit, now what ?

  21 juin 2019, par Joselyn Khor
  Exceeded GA’s 10M hits data limit, now what ? Matomo has the answers

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month as outlined in our Terms of Service. If you continue to exceed the limit, we will stop processing new data on XXX 21, 2019. Learn more about possible solutions.”

  Yikes. Alarm bells were ringing when a Google Analytics free user came to us faced with this notice. Let’s call him ‘Mark’. Mark had reached the limits on the data he could collect through Google Analytics and was shocked by the limited options available to fix the problem, without blowing the budget. The thoughts racing through his head were :

  • “What happens to all my data ?”
  • “What if Google starts charging USD150K now ?”

  Then he came across Matomo and decided to get in touch with our support team …

  “Can you fix this issue ?” he asked us.

  “Absolutely !” we said.

  We’ll get back to helping Mark in a minute. For now let’s go over why this was such a dilemma for him.

  In order to resolve this data limits issue, one of the solutions was for him to upgrade to Google Analytics 360, which meant shelling out USD150,000 per year for their 1 billion hits per month option. Going from free to USD150,000 was too much of a stretch for a growing company.

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month …”, what did this message mean ?

  With the free version, Mark could collect up to 10 million “hits” per month, per account. Going over meant Google Analytics could stop collecting any more data for free as outlined in their Terms.

  Google Analytics’ Terms of Service (2018, sec. 2) states, “Subject to Section 15, the Service is provided without charge to You for up to 10 million Hits per month per account.”[1]

  In general, what’s a "hit" ?

  Data being sent to Google Analytics. It can be a transaction, event, social interaction or pageview - these all produce what Google calls a “hit”.

  

  And their Analytics Help Data Limits (n.d.) support page makes clear that : “If a property sends more hits per month to Analytics than allowed by the Analytics Terms of Service, there is no assurance that the excess hits will be processed. If the property’s hit volume exceeds this limit, a warning may be displayed in the user interface and you may be prevented from accessing reports.”[2]

  

  Possible solutions

  So the possible solutions given by Google Analytics’ Data Limits support page were (also shown in image below) :

  • To pay USD150K to upgrade to Google Analytics 360
  • To send fewer hits by setting up sampling
  • Or choose the slightly less relevant option to upgrade mobile app tracking to Google Analytics for Firebase.

  Without the means to pay, the free version was fast becoming inaccessible for Mark as he was facing a future where he risked no longer having access to up-to-date data used in his business’ reporting.

  Mark was facing a problem that potentially didn’t have a cost-effective solution.

  

  So what can you really do about it ?

  This is where we can help provide some assistance. If you’re reading this article, we’ll assume you can relate to Mark and share with you the advice on options we gave him.

  Options :

  One option posed by Google is for you to send fewer hits by auditing your data collection processes

  If you really don’t have the budget, you’ll need to reassess your data collection priorities and go over your strategies to see what is necessary to track, and what isn’t.

  • Make sure you know what you’re tracking and why. Look at what websites are being tracked by Google and into what properties.
  • Go through what data you’re tracking and decide what is or isn’t of value.
  • Set up data sampling, this however, will lead to inaccurate data.

  From here you can start to course correct. If you’ve found data you’re not using for analysis, get rid of these events/pageviews in your Google Analytics.

  But the limitations here are that eventually, you’re going to run out of irrelevant metrics and everything you’re tracking will be essential. So you’ll hit another brick wall and return to the same situation.

  Option 2 – Ignore and continue using the free version of Google Analytics

  With this option, you’ll have to bear the business risks involved by basing decisions off of analytics reports that may or may not be updated. In this case, you may still get contacted about exceeding the limits. As the free service is provided for only up to 10 million hits, once you’ve gone over them, you’re violating what’s stipulated in the Terms of Service. 

  There’s also the warning that “… you may be prevented from accessing reports” (Data limits, n.d.). So while we may not know for certain what Google Analytics will do, in this case it may be better to be safe rather than sorry by acting quickly to resolve it. 

  Option 3 –The Matomo solution. Upgrade to a web analytics platform that can handle your demanding data requirements

  Save money while continuing to gain valuable insights by moving over to Matomo Analytics (recommended)

  This is where you can save up to USD130,000 a year. As well as that, the transition from Google Analytics to the Matomo Cloud is a seamless experience as setup and maintenance is taken care of by our experts.

  For example, you can get up to 15M pageviews for USD1,612.50/month (or USD19,350/year) on the Essentials plan.

  Or even 25M pageviews for USD2400/month (or USD24000/year) on the Business plan – which offers additional web analytics and conversion optimization resources.

  Matomo Cloud is a great option if you’re looking for a secure, cost-effective and powerful analytics solution. You also get what Google Analytics could never offer you : full control and ownership of your own data and privacy. 

  No need to worry about losing your Google Analytics data because …

  Now you can import your historic Google Analytics data directly into your Matomo with the Google Analytics Importer tool. Simply follow the step-by-step guide to get started for free.

  Along with savings you can get :

  • A solution for the data limits issue forever. You choose the right plan to suit your data needs and adapt as you continue growing
  • 100% accurate data (no data sampling)
  • 100% data ownership of all your information without signing away your data to a third party
  • Powerful web analytics and conversion optimization features
  • Matomo Tag Manager
  • Easy setup
  • Support from Matomo’s specialists

  Learn more about Matomo Cloud pricing.

  

  Or go for Matomo On-Premise

  If you have the in-house infrastructure to support self-hosting Matomo on your own servers then there’s also the option of Matomo On-Premise. Here you’ll get full security knowing the data is on your own servers. 

  Setup will also require technical knowledge. There will also be costs associated with acquiring your own servers, and keeping up with regular maintenance and updates. With On-Premise you get maximum flexibility, with no data limits whatsoever. But if you’re coming over from Google Analytics and don’t have the infrastructure and team to host On-Premise, the Matomo Cloud could be right for you.

  Learn more about Matomo On-Premise.

  Where do you go from here ?

  Getting 10 millions hits per month is no small feat, it’s actually pretty fantastic. But if it means having to shell out USD150,000 just to be able to continue with Google Analytics, we feel your problem could be fixed with Matomo Cloud. You could then put the rest of the money you save to better use.

  If you choose Matomo, you now have the option to : 

  • Raise your data limits for a fraction of Google Analytics 360’s price
  • Get a comprehensive range of analytics features for the most impactful insights to ensure your website continues excelling
  • Get data that’s not sampled – meaning 100% accuracy in your reports
  • Migrate your data easily with the help of Matomo’s support team

  We’ll have you covered. 

  By sharing with you the options and advice we gave to Mark, we hope you’ll be able to find a solution that makes your life easier and solves the issue of data restrictions forever.

  The team at Matomo is here to help you every step of the way to ensure a stress-free transition from Google Analytics if that is what works best for you.

  For next steps, why not check out our pricing page to see what could suit your needs !

  References :

  [1] Terms of Service. (2018, July 24). In Google Analytics Terms of Service. Retrieved June 12, 2019, from https://www.google.com/analytics/terms/us.html

  [2] Data limits. (n.d.). In Analytics Help Data limits. Retrieved June 12, 2019, from https://support.google.com/analytics/answer/1070983?hl=en