This page is also available in English (Englisch)

Problembehebung

  1. Piwik doesn't track any visits and pages, and shows "There is no data for this report" in all reports.
  2. Visits from search engines or campaigns are not recorded, Piwik shows "There is no data for this report" for all Referrers reports.
  3. Piwik doesn't track Downloads and Outlinks on my website.
  4. Piwik erkennt das Land oder den Kontinent meiner Besucher nicht genau.
  5. Piwik is slow! It takes a long time to load reports and pages.
  6. Statistics from Piwik and my other web analytics tool (log analyzer, webalizer or javascript based) are different, why?
  7. Die Graphen (Kreisdiagramm, Säulendiagramm, Liniendiagramm) werden in meinem Piwik nicht angezeigt.
  8. The sparklines (small graphs like ) are not showing in my Piwik.
  9. Piwik reporting UI doesn't have any css style or, the menu text appears on a white background. How to fix this display problem?
  10. The World map is not showing in my Piwik.
  11. Piwik zeigt anstatt des transparenten 1*1 Tracking-Pixels ein rotes Kreuz an (im IE) oder ein Icon für ein nicht gefundenes Bild, wo liegt das Problem?
  12. How do I configure Piwik when mod_security is enabled?
  13. Only one or a small number of days/months/date ranges are showing 0 zero visits, but other periods are working as expected.
  14. How do I delete historical Piwik data? (purge old logs)
  15. 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?
  16. Piwik doesn't show me when new updates are available, and the SEO plugin doesn't work.
  17. "Segmentation fault Error". Piwik reporting or via cron crashes with Segmentation Fault error. What to do?
  18. Ich bekomme die Fehlermeldung: "Fatal error: require_once() [function.require]: Failed opening required XYZ in /path/piwik/XYZ.php on line X". Wie kann ich Piwik zum Laufen bringen?
  19. What should I do when I get the error message: SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11)
  20. Ich bekomme den Fehler "Warning: gzuncompress() [function.gzuncompress]: data error" wenn ich meine Piwik-Berichte aufrufe.
  21. Emails sent from Piwik use the email address @defaultHostnameIfEmpty.example.org, how do I specify my domain name instead?
  22. Piwik reports this error and fails: "Fatal error: Allowed memory size of X bytes exhausted (tried to allocate X bytes)". What should I do?
  23. Piwik reports this error and doesn't continue: "Fatal error: Maximum execution time of 30 seconds exceeded in ..."
  24. Graphs in PDF/HTML reports and/or Piwik Mobile do not display characters correctly in my language (display squares instead).
  25. When I use http with force_ssl_login=1, I get "Too many redirects". When I use https, CSV/PDF reports and graphs don't work.
  26. I'm a developer, how do I enable logging (and / or SQL profiling) in Piwik?

Antworten

  1. 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.
    • 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.

  2. 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.

  3. 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.

  4. Piwik erkennt das Land oder den Kontinent meiner Besucher nicht genau.

    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.

  5. Piwik is slow! It takes a long time to load reports and pages.

    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.

  6. Statistics from Piwik and my other web analytics tool (log analyzer, webalizer or javascript based) are different, why?

    There could be a various number of reasons why Piwik numbers are different from your other web analytics solution.

    • Tracking Method: Piwik is using a javascript based tracker, and keeps count of unique visitors with a tracking cookie. Logs analyzers softwares (AWStats, Webalizer, Analog, etc.) or custom server-side script would record all traffic including bots and generally rely on the IP address and user agent to determine unique visitors, which is less accurate.
    • Hits vs Visits: Log analyzers softwares will typically report "hits". Hits generally count all http requests to your websites: pages, images, css, javascript files, etc. Piwik reports page views, unique visitors, visits, etc. which are expected to be much less than the number of hits.
    • Record loaded page: when the Piwik javascript code is located at the end of the page, Piwik will only record page views for page that are finished loading. Log Analyzers would also record page requests that have been "cancelled", eg. when the user hits the Back button before the page is displayed.
    • Visitors Browser: Piwik will count visitors with Javascript and Images enabled. Other softwares may record visits from visitors with Javascript disabled, which would include non human activity like search engine bots.
    • Position and presence of Javascript tag: when comparing Javascript-based statistics (eg. number of unique visitors), you have to make sure that both javascript tags are present on all pages you want to track. Also, it is better to put all tracking codes at the end of your pages, just before the </body> tag.

    Concerning Google Analytics, several users compared Piwik and Google Analytics numbers, and found very similar statistics: on significant traffic, differences were always less than 5 percent.

    Conservative counting is definitely best - it makes your statistics more realistic on what you are trying to measure. Most analytics packages are used to measure relative upswings, we recommend using the same tool for all measurements and relative comparisons.

  7. Die Graphen (Kreisdiagramm, Säulendiagramm, Liniendiagramm) werden in meinem Piwik nicht angezeigt.

    If you are not seeing Graphs in Piwik, the most likely reason is that you are using Piwik < 1.5 which are using Flash graphs, and you do not have Flash enabled in your browser.

    As of Piwik 1.5, graphs in Piwik are drawn using open source technologies supported in all modern browsers: see Canvas and Jquery graphs blog post.

  8. The sparklines (small graphs like ) are not showing in my Piwik.

    The GD library is not installed on your server. This library is required to produce the sparklines. Please ask your system administrator or your web host to install php-gd for you.

    On linux, you can install php-gd by executing "apt-get install php-gd" on debian type systems, then restart your webserver.

  9. Piwik reporting UI doesn't have any css style or, the menu text appears on a white background. How to fix this display problem?

    To improve performance, Piwik tries to automatically combine all CSS stylesheets and Javascript files into two large files, instead of having to download 20 individual files. However, on some webhosts, PHP scripts have a max execution time and if the server is overloaded, the script that merges all files together can take more than the time limit.

    There are 2 solutions

    • Ask your webhost to increase the max_execution_time in your php.ini file, for example to 30 seconds.
    • If you can't change this setting, you can alternatively disable the feature to combine together CSS and JS files. To disable this feature, edit your config/config.ini.php and add the following:
      [Debug]
      disable_merged_assets = 1

    Then, delete your browser cache and refresh Piwik: after a few seconds, it should display correctly again!

  10. The World map is not showing in my Piwik.

    The Piwik World Map requires the plugin Flash to be displayed. Please check that you have installed Flash in your browser. Click here to install the flash plugin.
    If you have installed the Flash plugin, and the world map is still not showing, maybe you are using a browser extension that blocks the flash content? For example, if you're using the AdBlock extension, there's a notable bug where it blocks Flash content in <object> tags even if the page is whitelisted. Please consider using AdBlock Plus as a replacement.

  11. Piwik zeigt anstatt des transparenten 1*1 Tracking-Pixels ein rotes Kreuz an (im IE) oder ein Icon für ein nicht gefundenes Bild, wo liegt das Problem?

    Wenn Piwik ein Bild mit einem roten Kreuz bzw. ein ungültigen Bild-Link anzeigt bedeutet dies, dass das Tracking auf Ihrer Seite nicht funktioniert. Dies ist nicht beabsichtigt und es sollte schnellstmöglich nach der Ursache des Problems gesucht werden (in der Zwischenzeit werden die Besucher wahrscheinlich nicht aufgezeichnet).

    Um herauszufinden woher der Fehler kommt, öffnen Sie Ihre Webseite mit Firefox, klicken Sie mit der rechten Maustaste auf den fehlerhaften Bild-Link und klicken Sie dann auf "Bild anzeigen". Dies sollte Sie zu der folgenden URL "ihrewebseite.com/piwik/piwik.php?..." weiterleiten und die Fehlermeldung sollte nun angezeigt werden.

    Wenn die Meldung die MySQL-Datenbank benennt, könnte der Fehler von einer defekten Tabelle oder MySQL-Instanz herrühren. Versuchen Sie die Tabelle zu "reparieren" (mit Hilfe von phpMyAdmin z.B.).
    Wenn die Meldung "failed to open stream: No such file or directory" lautet könnten Dateien fehlen, die Piwik zur Ausführung benötigt. Stellen Sie sicher, dass alle Piwik-Dateien korrekt hochgeladen wurden.
    Für andere Fehlermeldungen, nutzen Sie bitte die Suchfunktion auf Piwik.org.
    Sie können auch versuchen Ihre Antwort im Piwik Supportforum zu finden.

  12. How do I configure Piwik when mod_security is enabled?

    If your host uses mod_security to block requests containing URLs (eg. hosts like HostGator, The Planet), you should contact your provider to whitelist your domain (or URL) and disable mod_security for your website.

    Alternately, if your Piwik is hosted on the same domain as your website being tracked, you can edit your Piwik Javascript Tracking code to force data to be sent in POST, to avoid the mod_security check. Before the line piwikTracker.trackPageView(); you can add the following line piwikTracker.setRequestMethod('POST');

  13. Only one or a small number of days/months/date ranges are showing 0 zero visits, but other periods are working as expected.

    In rare cases, Piwik will show "no data" only for one day or one month, while other periods work fine and report visits as expected.
    If you are not yet using at least Piwik 1.6, please update now (we fixed issues related to this problem in 1.6 and latest).

    It is possible to re-process the specific days or months that are showing zero visit, check out this faq: Re-process reports.

  14. How do I delete historical Piwik data? (purge old logs)

    You can configure Piwik to automatically delete your older logs from the database. Deleting old logs has many advantages: 1) it will free significant database space, 2) which will slightly increase performance, 3) for Privacy reasons, it is sometimes recommended to keep detailed logs only for 6 months or so, and remove older data.

    To configure Log delete in Piwik, login as the Super User, click on Settings > Privacy > Delete old visitor logs from database. You can then configure to Delete logs older than N days, and execute the log purging every day, every week or every month.

    Important: When you enable automatic log deletion, you must ensure that all previous daily reports have been processed, so that no data is lost. See this FAQ for more information.

    Deleted data: When 'Delete old logs' is enabled, only the raw logs of activity will be deleted from the database. Specifically, only the Mysql tables starting with piwik_log_* are affected. All deleted data is lost forever.

    If you have properly setup the auto archiving script (see important note), you will still access all historical reports (even when logs are deleted).

  15. 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?

    When you automatically import your existing userbase in Piwik using the UsersManager API, you might want to disable the check of minimum length and valid characters for the User's login and password.
    In particular, Piwik requires a password at least 6 characters long, and a login string that must contain only valid characters (ie. letters, @, etc.).
    You can disable these checks by adding in the file config/config.ini.php the following: [General]
    disable_checks_usernames_attributes = 1

  16. Piwik doesn't show me when new updates are available, and the SEO plugin doesn't work.

    Your firewall may be blocking outbound HTTP requests. If you have a HTTP proxy (e.g., squid), you can configure the forward proxy as follows.
    Edit your config/config.ini.php and add the following:
    [proxy]
    host = ; Proxy host: the host name of your proxy server (mandatory)
    port = ; Proxy port: the port that the proxy server listens to. There is no standard default, but 80, 1080, 3128, and 8080 are popular
    username = ; Proxy username: optional; if specified, password is mandatory
    password = ; Proxy password: optional; if specified, username is mandatory

    Once configured, Piwik will contact external hostnames using this proxy server.

  17. "Segmentation fault Error". Piwik reporting or via cron crashes with Segmentation Fault error. What to do?

    Unfortunately, Segmentation fault Piwik errors mean that the lower level software has crashed in some unexpected fashion. In this case, most likely PHP or some of its specific modules (PDO, mysqli, etc.). It is possible to overcome this issue by updating these softwares.
    If you get the Segmentation fault error, the solution is to:

    • Upgrade Piwik and make sure to use the latest version
    • upgrade PHP to the latest version
    • upgrade PDO (and/or mysqli) to the latest version
    • You can also try to switch from PDO_MYSQL to MYSQLI in the config/config.ini.php ; edit the line "adapter = [...]"
    • if you still get the error, try disabling extensions such as eAccelerator, APC, xcache and/or Suhosin.
    • if you still get the segmentation fault error at this point, please try the suggestion in this forum post. If it works for you, please post a reply in the thread

    You should now have a working Piwik instance that does not crash, congratulations.

  18. Ich bekomme die Fehlermeldung: "Fatal error: require_once() [function.require]: Failed opening required XYZ in /path/piwik/XYZ.php on line X". Wie kann ich Piwik zum Laufen bringen?

    Dieser Fehler wird ausgelöst wenn Piwik eine Datei nicht findet, die es zur Ausführung benötigt. Bitte stellen Sie sicher, dass alle Dateien von Piwik korrekt auf den Server übertragen wurden. Sie können die fehlenden Dateien, die in der Fehlermeldung benannt werden, nachträglich hoch laden, oder Sie laden alle Dateien erneut hoch: Das sollte das Problem lösen!

  19. What should I do when I get the error message: SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11)

    This means that Piwik could not connect to your MySQL database. If you are on a dedicated server, you can try to restart the Mysql server by running, for example, /etc/init.d/mysql restart. If you are on a shared web hosting, we recommend contacting your web host and ask them to investigate why it fails to connect to the Mysql server.

  20. Ich bekomme den Fehler "Warning: gzuncompress() [function.gzuncompress]: data error" wenn ich meine Piwik-Berichte aufrufe.

    Dieser Fehler kommt sehr selten vor. Aus unbekanntem Grund wurden Daten nicht korrekt in die Datenbank geschrieben. In Piwik werden alle Berichtsdaten komprimiert (gzip) und dann in den Tabellen piwik_archive_* gespeichert.

    Um diesen Fehler zu beseitigen, sehen Sie sich die Fehlermeldung an und suchen nach "piwik_archive_blob". Wenn der Fehler zum Beispiel folgendermaßen aussieht:

    #0 Piwik_ErrorHandler(2, gzuncompress() [function.gzuncompress]: data error, /path/piwik/core/Archive/Single.php, 250, Array ([name] => Referers_searchEngineByKeyword,[typeValue] => blob,[table] => piwik_archive_blob_2009_05,[...]

    Suchen Sie nach "piwik_archive_blob_2009_05" und löschen Sie diese Tabelle in Ihrer Datenbank. Piwik wird diese Tabelle dann bei der nächsten Ansicht der Berichte erneut verarbeiten. Das wird den Fehler beheben.

  21. Emails sent from Piwik use the email address @defaultHostnameIfEmpty.example.org, how do I specify my domain name instead?

    By default Piwik will try to detect the current Hostname and use it in all emails sent. In some cases, the hostname cannot be detected and Piwik will use "defaultHostnameIfEmpty.example.org". You can specify your domain name to appear in From: email addresses by adding the following lines in your config/config.ini.php file:
    [mail]
    defaultHostnameIfEmpty = mydomain.com

    This will affect all emails sent from Piwik: Password reminder, Email reports. You can also change the default email address "From:" in PDF reports emails.

  22. Piwik reports this error and fails: "Fatal error: Allowed memory size of X bytes exhausted (tried to allocate X bytes)". What should I do?

    You must increase PHP memory limit. See this page for more info.

  23. Piwik reports this error and doesn't continue: "Fatal error: Maximum execution time of 30 seconds exceeded in ..."

    Your PHP is configured to stop running a script after some time, generally 30 seconds. When Piwik is used on a websites with few thousands visits per day, then this limit might not be high enough. To fix this, modify in your php.ini the max_execution_time value to zero (which means no time limit):

    max_execution_time = 0

    This will ensure that Piwik always has enough time to process your analytics reports.

  24. Graphs in PDF/HTML reports and/or Piwik Mobile do not display characters correctly in my language (display squares instead).

    To display unicode characters in the Static image graphs, please see this FAQ.

  25. When I use http with force_ssl_login=1, I get "Too many redirects". When I use https, CSV/PDF reports and graphs don't work.

    If you're not using a reverse proxy, but using https with a web server that doesn't set the HTTPS environment variable, you can either set assume_secure_protocol=1 or reconfigure your web server.
    For example, lighttpd should be configured with setenv.add-environment = ( "HTTPS" => "on" ). Similarly, nginx users should use something like fastcgi_param HTTPS on;.

  26. I'm a developer, how do I enable logging (and / or SQL profiling) in Piwik?

    There are a few possibilities with regards to debug logging in Piwik:

    • Enable logging in the Tracker can be useful to debug Tracking issues or improvements. See the documentation page about enabling Debug logging in the piwik.php tracker
    • Enable logging in the Piwik UI: if you are writing a plugin for example, you would need to output messages on screen (or in a file). To do so, you can edit your config.ini.php and add the following block:
      [log]
      logger_message[] = "screen"
      logger_error[] = "screen"
      logger_exception[] = "screen"

      If you wish to debug a live server in production, you can enable logging so that it only outputs the message if you manually append "&debug" in the URL. Under the section [log] in your config.ini.php you can add the following:
      log_only_when_debug_parameter = 1

      All logging configuration options can be found in config/global.ini.php
    • Enable SQL logging & profiling: to see the list of SQL queries executed by Piwik on any given page or widget, you must first enable logging on screen (see point above). Then, edit your config.ini.php and add the following:[Debug]
      enable_sql_profiler = 1

      • Piwik will then output all SQL queries, group them by unique query, and show the total time spent as well as average time spent on each query.

Entries (RSS)