diff --git a/config/vufind/config.ini b/config/vufind/config.ini
index b670cc084e2156ec9e637ab73d98edab39f50e3f..9c0febe09ebd27acb61d887a2b9a3495c1156173 100644
--- a/config/vufind/config.ini
+++ b/config/vufind/config.ini
@@ -1761,7 +1761,7 @@ treeSearchLimit = 100
 ;sender_name       = "VuFind Feedback"
 
 ; Note: for additional details about stats (including additional notes on Google
-; Analytics and Piwik), look at the wiki page:
+; Analytics and Matomo/Piwik), look at the wiki page:
 ;     https://vufind.org/wiki/configuration:usage_stats
 
 ; Uncomment this section and provide your API key to enable Google Analytics. Be
@@ -1772,18 +1772,20 @@ treeSearchLimit = 100
 ;apiKey = "mykey"
 ;universal = false
 
-; Uncomment this section and provide your Piwik server address and site id to
-; enable Piwik analytics. Note: VuFind's Piwik integration uses several custom
-; variables; to take advantage of them, you must reconfigure Piwik by switching
+; The Piwik product has been renamed to Matomo, but for backward compatibility,
+; the terminology has not yet been changed in VuFind. Uncomment this section and
+; provide your Matomo or Piwik server address and site id to enable Matomo/Piwik
+; analytics. Note: VuFind's Matomo/Piwik integration uses several custom variables;
+; to take advantage of them, you must reconfigure Matomo/Piwik by switching
 ; to its root directory and running this command to raise a default limit:
 ; ./console customvariables:set-max-custom-variables 10
 [Piwik]
 ;url = "http://server.address/piwik/"
 ;site_id = 1
 ; Uncomment the following setting to track additional information about searches
-; and displayed records with Piwik's custom variables
+; and displayed records with Matomo/Piwik's custom variables
 ;custom_variables = true
-; By default, Piwik searches are tracked using the format "Backend|Search Terms."
+; By default, searches are tracked using the format "Backend|Search Terms."
 ; If you need to differentiate searches coming from multiple VuFind instances using
 ; a shared site_id, you can set the searchPrefix to add an additional prefix to
 ; the string, for example "SiteA|Backend|Search Terms." Most users will want to