English (Anglais)Diagnostic des problèmes
- Piwik doesn't track any visits and pages, and shows "There is no data for this report" in all reports.
- Visits from search engines or campaigns are not recorded, Piwik shows "There is no data for this report" for all Referrers reports.
- Piwik doesn't track Downloads and Outlinks on my website.
- Piwik ne détecte pas précisément la pays et/ou le continent des visiteurs.
- Piwik is slow! It takes a long time to load widgets, reports and pages.
- Les statistiques de Piwik et de mes autres outils d'analyse Web (log analyzer, webalizer ou javascript based) sont différents, pourquoi ?
- After I updated Piwik, it stopped working (blank page, widgets not loading, error message, etc.). How can I fix this?
- Les graphiques (camembert, barre, graphique évolution) ne s'affiche pas dans Piwik.
-
The sparklines (small graphs like
) are not showing in my Piwik.
- Piwik reporting UI doesn't have any css style or, the menu text appears on a white background. How to fix this display problem?
- When tracking visits on an intranet website, Piwik assigns all page views to a few visitors who have very high page views count. How to fix it?
- The World map is not showing in my Piwik.
- Le code Javascript Piwik afficher une croix rouge (dans IE) ou une icône d'image cassée à la place du pixel de 1*1 transparent, quel est le problème ?
- How do I configure Piwik when mod_security is enabled?
- Only one or a small number of days/months/date ranges are showing 0 zero visits, but other periods are working as expected.
- How do I delete historical Piwik data? (purge old logs)
- I would like to import an existing Users database (login, password, emails) in Piwik, but the usernames and passwords are more permissive than what Piwik allows. How do I disable the checks on the Logins & Passwords?
- Piwik doesn't show me when new updates are available, and the SEO plugin doesn't work.
- "Segmentation fault Error". Piwik reporting or via cron crashes with Segmentation Fault error. What to do?
- J'ai ce message d'erreur: "Fatal error: require_once() [function.require]: Failed opening required XYZ in /path/piwik/XYZ.php on line X". Comment faire fonctionner Piwik ?
- Que faire quand j'ai un message d'erreur de type : SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11)
- J'obtiens l'erreur "Warning: gzuncompress() [function.gzuncompress]: data error" lorsque je consulte mes rapports piwik.
- Emails sent from Piwik use the email address @defaultHostnameIfEmpty.example.org, how do I specify my domain name instead?
- Piwik reports this error and fails: "Fatal error: Allowed memory size of X bytes exhausted (tried to allocate X bytes)". What should I do?
- Piwik reports this error and doesn't continue: "Fatal error: Maximum execution time of 30 seconds exceeded in ..."
- Graphs in PDF/HTML reports and/or Piwik Mobile do not display characters correctly in my language (display squares instead).
- When I use http with force_ssl_login=1 or force_ssl=1, I get "Too many redirects". Also when I use https, CSV/PDF reports and graphs don't work.
- When included in an IFrame, Piwik reports do not load. How do I allow Piwik reports to load from within an iframe?
- I'm a developer, how do I enable logging (and / or SQL profiling) in Piwik?
- Widgets don't load. I get the error message: "Fatal error: Class '...' not found in ... What's wrong?
Réponses
-
Piwik doesn't track any visits and pages, and shows "There is no data for this report" in all reports.
There are several possible reasons why Piwik is not tracking your visits properly:
-
Incorrect Piwik tracking code
Please check that you can find the Piwik javascript code on your website pages that you wish to track. Sometimes, when you copy paste the javascript code in other softwares, like Word or FrontPage, they may add extra spaces or characters. Make sure the code looks like this example (and that it mentions the right URL of your Piwik installation).
In some cases, when you install Piwik on your local test server, the javascript code might contain "localhost" or "127.0.0.1". When you deploy Piwik in production, you have to edit the Javascript code so that it points to your website URL, eg. "http://example.org/piwik/".
Also, each Piwik tracking code contains the idsite of your website registered in Piwik. If you only registered one website in Piwik, the idsite found in your Javascript code should be "1". -
Make sure you are viewing reports for the correct website and date in Piwik
In Piwik, make sure you selected the right website in the website selector. Also, try to look at reports for "today" by changing the date in the date picker. Please wait at least 10 seconds after generating visits on your website: by default Piwik will only process reports every 10 seconds when "today" is selected. - Archiving triggered from the browser must be enabled, if it is disabled the Cron script must be configured properly
In Settings > General Settings, 'Allow Piwik archiving to trigger when reports are viewed from the browser' must be set to 'Yes'. If it is set to 'No', you must configure the cron script to automatically archive your web analytics reports, or Piwik will show 'No Data'. More information about auto archiving. -
Third party Piwik plugins
It is possible that some Third party Piwik plugins could cause problems when tracking your visitors. Please try to disable all the third party plugins you are using to see if it fixes the issue. -
Browser addons blocking the Piwik Tracking Javascript
If you use browsers addons such as Adblock, Adblock plus, NoScript, Ghostery or others, the Piwik Javascript code is not executed in your browser. Try to use a different browser that does not have these extensions, or disable them and try again. -
Do you have logs registered in your Piwik database?
If your Piwik tracking code is properly installed, Piwik would record visits in your database. To check if you have logs in your database, go to Piwik > Visitors > Visitor log, and select "today" in the calendar. If you see recent visitor information, it means that the visitor tracking is working, but maybe there is a problem with reports archiving.
Note: you can also check if logs are recorded correctly by looking at the table "piwik_log_visit" (using phpMyAdmin for example) and see if there are visits recorded. Alternatively, you can enable the plugin "DBStats", and then go to the "Database usage" tab in your Piwik administration area, and check if the table piwik_log_visit has any rows. -
Testing Piwik with disabled Javascript
By default, Piwik only tracks visitors with javascript enabled. When you are testing that Piwik tracks visits properly make sure you have javascript enabled.
If you need help with javascript tracking check out docs/javascript-tracking.
If you need to use a tracking method which doesn't involve javascript have a look at docs/tracking-api. -
Piwik displays a red cross (on IE) or a broken image icon on your tracked pages, instead of the 1*1 transparent Pixel
Check out this FAQ answer. -
Access to piwik.php fails
If your host uses mod_security to block requests containing URLs (eg. hosts like HostGator, The Planet), check out the Piwik and mod_security FAQ.
If you use HTTP Authentication (Basic or Digest) on your Piwik files, you should exclude piwik.php and piwik.js from this authentication, or visitors on your website would be prompted with the authentication popup. -
Tracking https (SSL) pages
If you install the Piwik Javascript Tracking tag on https:// pages, then the tracking requests will be sent to Piwik via https. This means that the server you installed Piwik on must be able to handle these https requests, or no data will be tracked. See also Piwik and SSL tracking. -
Local copy of piwik.js outdated
Some users make a local copy of piwik.js on a different server than their Piwik installation. This is not officially supported and causes issues when the piwik.js bundled with Piwik is updated and not compatible with the previous version (for example, this is the case in Piwik 0.5.5). Please check that your Piwik JS tracking code is exactly the one given in the Piwik admin screen. - Using Piwik latest version
If you are still seing "No data", please make sure you are using the latest version of Piwik (if not, update now). - Check your webserver error logs
If all else fails, it is possible that there is a server misconfiguration preventing Piwik from tracking your visits or processing reports. Often, there will be an error in the webserver error logs (apache logs, IIS logs, nginx logs, etc.). Please check that your PHP is configured to log errors: (php.ini should contain log_errors = On and error_log = /path/to/log). The messages in the webserver error log will help you find the source of the problem, for example search for the error message on this website.
-
Incorrect Piwik tracking code
-
Visits from search engines or campaigns are not recorded, Piwik shows "There is no data for this report" for all Referrers reports.
There are a few possible explanations:
- Are your pages tagged correctly?
If you click on your website in a search result, and look at your page source, can you see the Piwik tracking code? Make sure the Piwik tracking code is installed on all the pages you want to track, and is not within an iframe. We advise to put the Piwik code just before the </body> tag. - Are you using a redirect on your website landing page?
If you are using a redirect, the visitor browser may lose the referer information. If you are tracking campaigns, and the landing page has a redirect, the URL loaded after the redirection will have lost the URL parameters. Make sure that your visitors arrive directly on the page with the Piwik tracking code installed. - Piwik only records 1 referer by visit, which means that only the first referer used to access the website will be recorded.
If you search for a keyword in a search engine, click on your website in the search engine results, and land on a page with the Piwik tracker, you may expect to see the keyword in your Piwik reports.
However, if you visited your website less than 30 minutes ago, Piwik will recognize you as an known visitor on the website, will record your page view, but will not update your visit referer. Piwik only record the first referer of a visit. When testing Piwik and search engine detection, make sure you make the test more than 30 minutes after your last page view on your website. - Check that the Piwik domain name in your Javascript tracking code is correct (this URL is in the second line of the Piwik tracking code).
There have been cases of missing referrers when the Piwik JS code in the pages points to a URL that returns a 302 response instead of the final destination. It seems that some webserver compromise the tracking request when such redirects occur. Check in particular if the URL (doesn't) contains "www.". Also, if the server does an automatic redirection from http to https which also affects tracking requests to piwik.php, it might create problems such as missing referer data. Make such any http->https redirection excludes piwik.php requests.
- Are your pages tagged correctly?
-
Piwik doesn't track Downloads and Outlinks on my website.
Piwik should automatically track clicks on Download files (with a known extension, eg. jpg, png, exe, zip, etc.) and clicks on Outlinks (links to other websites) using Javascript click handlers. There are a few reasons why this could fail:
- Conflicting Javascript code
In some rare cases, Download and Outlink tracking doesn't work in Piwik is because your page is using another Javascript script or library which sets click handlers as well. If a third-party click handler returns a value, it is causing the browser to cancel other registered click handlers. Instead they should return false. Most scripts and libraries are doing it correctly, but you might have to manually edit your Javascript code to return false in onclick events. - Piwik doesn't respond fast enough and user is redirected to the click target
Piwik click handler works by adding a small delay during which the request is sent to the Piwik server. If somehow the request doesn't reach the server within this delay, the request will be not be tracked and the user will be redirected to the clicked download file or to the external website. You can increase this delay, from the default of 500ms (0.5 second), by adding the following in the Javascript code, after the piwik.getTracker(..) line:piwikTracker.setLinkTrackingTimer( 750 ); // increase to 750 milliseconds - You're using Safari, Chrome, or some other WebKit-based browser.
There is a known WebKit bug (feature?) that interrupts the tracking request. One workaround is to add the target="_blank" attribute to anchor elements.
- Conflicting Javascript code
-
Piwik ne détecte pas précisément la pays et/ou le continent des visiteurs.
Unless you're using the GeoIP plugin, Piwik is guessing your location from the language locale disclosed by the browser, e.g. en-us -> country is set to USA, fr-fr -> country is set to France, etc.
In some cases, Piwik will guess the location when the region is omitted, e.g., fr -> France. This can be disabled from config/global.ini.php (or overridden in your config.ini.php):
[Tracker]
enable_language_to_country_guess = 0
If you want to improve the country detection accuracy in Piwik, please install the GeoIP plugin. -
Piwik is slow! It takes a long time to load widgets, reports and pages.
There are a few possible reasons that Piwik could be slow to load:
- By default, Piwik reports are processed when you request them in the User Interface. Please see How to setup auto archiving of your reports every hour? to automate the generation of Piwik reports.
- If you are using Piwik on a website (or thousands of websites) tracking millions of pages per day, please check out the doc: How Piwik for high traffic websites.
- If your server uses NFS-mounted storage (for example if you are using OVH mutu webhost), widgets might load very slowly even if you are not tracking a lot of data. This is because Piwik by default uses "file based sessions" which are very slow when using NFS storage. The solution is to change a setting to enable Database session storage.
-
Les statistiques de Piwik et de mes autres outils d'analyse Web (log analyzer, webalizer ou javascript based) sont différents, pourquoi ?
Il peut y avoir des raisons différents expliquant pourquoi les chiffres de Piwik sont différents des autres solutions d'analyse Web.
- Méthode de pistage: Piwik utilise un tracker basé sur javascript, et comptabilise les visiteurs uniques avec un cookie de traçage. Les analyseurs de logs (AWStats, Webalizer, Analog, etc.) ou les script personnalisés côté serveur vont enregistrer tous le trafic incluant les bots et utiliserons l'adresse IP et le User Agent pour déterminer un visiteur unique, ce qui est moins précis.
- Hits vs Visites: Les logiciels d'analyse de logs vont rapporter des "hits". Les hits prennent en compte toutes les requêtes HTTP de votre site Web : pages, images, css, fichiers javascript, etc. Piwik rapporte les pages vues, les visiteurs uniques, les visites, etc. ce qui constitue moins que le nombre de hits.
- Enregistrer les pages chargées : lorsque vous placez le code Javascript de Piwik à la fin d'une page, Piwik ne tiendra compte que des pages qui sont complètement chargées. Les analyseurs de logs enregistrent aussi les pages dont le chargement a été annulé, exemple : lorsqu'un utilisateur clic sur le bouton Retour avant que la page ne s'affiche.
- Navigateur du visiteur : Piwik va comptabiliser les visiteurs avec le Javascript et l'affichage des images activés. Les autres logiciels vont enregistrer les visites avec le Javascript désactivé ce qui inclut une activité automatique tel que les bots des moteurs de recherche.
- Position et présence du tag Javascript : lorsque vous comparez des statistiques basées sur Javascript( ex: le nombre de visiteurs unique), vous devez vous assurer que les deux tags Javascript soient présent sur toutes les pages que vous voulez tracer. Il est préférable de mettre les tags Javascript à la fin de votre page juste avant
Français
Deutsch
Ελληνικα
polski
Newsletter