global.ini.php
1071 lines
| 1 | ; <?php exit; ?> DO NOT REMOVE THIS LINE |
| 2 | ; If you want to change some of these default values, the best practise is to override |
| 3 | ; them in your configuration file in config/config.ini.php. If you directly edit this file, |
| 4 | ; you will lose your changes when you upgrade Matomo. |
| 5 | ; For example if you want to override action_title_category_delimiter, |
| 6 | ; edit config/config.ini.php and add the following: |
| 7 | ; [General] |
| 8 | ; action_title_category_delimiter = "-" |
| 9 | |
| 10 | ;-------- |
| 11 | ; WARNING - YOU SHOULD NOT EDIT THIS FILE DIRECTLY - Edit config.ini.php instead. |
| 12 | ;-------- |
| 13 | |
| 14 | [database] |
| 15 | host = |
| 16 | username = |
| 17 | password = |
| 18 | dbname = |
| 19 | tables_prefix = |
| 20 | port = 3306 |
| 21 | adapter = PDO\MYSQL |
| 22 | type = InnoDB |
| 23 | schema = Mysql |
| 24 | |
| 25 | ; Database SSL Options START |
| 26 | ; Turn on or off SSL connection to database, possible values for enable_ssl: 1 or 0 |
| 27 | enable_ssl = 0 |
| 28 | ; Direct path to server CA file, CA bundle supported (required for ssl connection) |
| 29 | ssl_ca = |
| 30 | ; Direct path to client cert file (optional) |
| 31 | ssl_cert = |
| 32 | ; Direct path to client key file (optional) |
| 33 | ssl_key = |
| 34 | ; Direct path to CA cert files directory (optional) |
| 35 | ssl_ca_path = |
| 36 | ; List of one or more ciphers for SSL encryption, in OpenSSL format (optional) |
| 37 | ssl_cipher = |
| 38 | ; Whether to skip verification of self signed certificates (optional, only supported |
| 39 | ; w/ specific PHP versions, and is mostly for testing purposes) |
| 40 | ssl_no_verify = |
| 41 | ; Database SSL Options END |
| 42 | |
| 43 | ; if charset is set to utf8, Matomo will ensure that it is storing its data using UTF8 charset. |
| 44 | ; it will add a sql query SET at each page view. |
| 45 | ; Matomo should work correctly without this setting but we recommend to have a charset set. |
| 46 | charset = utf8 |
| 47 | |
| 48 | ; If configured, the following queries will be executed on the reader instead of the writer. |
| 49 | ; * archiving queries that hit a log table |
| 50 | ; * live queries that hit a log table |
| 51 | ; You only want to enable a reader if you can ensure there is minimal replication lag / delay on the reader. |
| 52 | ; Otherwise you might get corrupt data in the reports. |
| 53 | [database_reader] |
| 54 | host = |
| 55 | username = |
| 56 | password = |
| 57 | dbname = |
| 58 | port = 3306 |
| 59 | |
| 60 | [database_tests] |
| 61 | host = localhost |
| 62 | username = "@USERNAME@" |
| 63 | password = |
| 64 | dbname = matomo_tests |
| 65 | tables_prefix = |
| 66 | port = 3306 |
| 67 | adapter = PDO\MYSQL |
| 68 | type = InnoDB |
| 69 | schema = Mysql |
| 70 | charset = utf8mb4 |
| 71 | enable_ssl = 0 |
| 72 | ssl_ca = |
| 73 | ssl_cert = |
| 74 | ssl_key = |
| 75 | ssl_ca_path = |
| 76 | ssl_cipher = |
| 77 | ssl_no_verify = 1 |
| 78 | |
| 79 | [tests] |
| 80 | ; needed in order to run tests. |
| 81 | ; if Matomo is available at http://localhost/dev/matomo/ replace @REQUEST_URI@ with /dev/matomo/ |
| 82 | ; note: the REQUEST_URI should not contain "plugins" or "tests" in the PATH |
| 83 | http_host = localhost |
| 84 | remote_addr = "127.0.0.1" |
| 85 | request_uri = "@REQUEST_URI@" |
| 86 | port = |
| 87 | enable_logging = 0 |
| 88 | |
| 89 | [log] |
| 90 | ; possible values for log: screen, database, file |
| 91 | log_writers[] = screen |
| 92 | |
| 93 | ; log level, everything logged w/ this level or one of greater severity |
| 94 | ; will be logged. everything else will be ignored. possible values are: |
| 95 | ; ERROR, WARN, INFO, DEBUG |
| 96 | ; this setting will apply to every log writer, if there is no specific log level defined for a writer. |
| 97 | log_level = WARN |
| 98 | |
| 99 | ; you can also set specific log levels for different writers, by appending the writer name to log_level_, like so: |
| 100 | ; this allows you to log more information to one backend vs another. |
| 101 | ; log_level_screen = |
| 102 | ; log_level_file = |
| 103 | |
| 104 | ; if configured to log in a file, log entries will be made to this file |
| 105 | logger_file_path = tmp/logs/matomo.log |
| 106 | |
| 107 | [Cache] |
| 108 | ; available backends are 'file', 'array', 'null', 'redis', 'chained' |
| 109 | ; 'array' will cache data only during one request |
| 110 | ; 'null' will not cache anything at all |
| 111 | ; 'file' will cache on the filesystem |
| 112 | ; 'redis' will cache on a Redis server, use this if you are running Matomo with multiple servers. Further configuration in [RedisCache] is needed |
| 113 | ; 'chained' will chain multiple cache backends. Further configuration in [ChainedCache] is needed |
| 114 | backend = chained |
| 115 | |
| 116 | [ChainedCache] |
| 117 | ; The chained cache will always try to read from the fastest backend first (the first listed one) to avoid requesting |
| 118 | ; the same cache entry from the slowest backend multiple times in one request. |
| 119 | backends[] = array |
| 120 | backends[] = file |
| 121 | |
| 122 | [RedisCache] |
| 123 | ; Redis server configuration. |
| 124 | host = "127.0.0.1" |
| 125 | port = 6379 |
| 126 | ; instead of host and port a unix socket path can be configured |
| 127 | unix_socket = "" |
| 128 | timeout = 0.0 |
| 129 | password = "" |
| 130 | database = 14 |
| 131 | ; In case you are using queued tracking: Make sure to configure a different database! Otherwise queued requests might |
| 132 | ; be flushed |
| 133 | |
| 134 | [Debug] |
| 135 | ; if set to 1, the archiving process will always be triggered, even if the archive has already been computed |
| 136 | ; this is useful when making changes to the archiving code so we can force the archiving process |
| 137 | always_archive_data_period = 0; |
| 138 | always_archive_data_day = 0; |
| 139 | ; Force archiving Custom date range (without re-archiving sub-periods used to process this date range) |
| 140 | always_archive_data_range = 0; |
| 141 | |
| 142 | ; if set to 1, all the SQL queries will be recorded by the profiler |
| 143 | ; and a profiling summary will be printed at the end of the request |
| 144 | ; NOTE: you must also set [log] log_writers[] = "screen" to enable the profiler to print on screen |
| 145 | enable_sql_profiler = 0 |
| 146 | |
| 147 | ; If set to 1, all requests to matomo.php will be forced to be 'new visitors' |
| 148 | tracker_always_new_visitor = 0 |
| 149 | |
| 150 | ; if set to 1, all SQL queries will be logged using the DEBUG log level |
| 151 | log_sql_queries = 0 |
| 152 | |
| 153 | ; if set to 1, core:archive profiling information will be recorded in a log file. the log file is determined by the |
| 154 | ; archive_profiling_log option. |
| 155 | archiving_profile = 0 |
| 156 | |
| 157 | ; if set to an absolute path, core:archive profiling information will be logged to specified file |
| 158 | archive_profiling_log = |
| 159 | |
| 160 | [DebugTests] |
| 161 | ; When set to 1, standalone plugins (those with their own git repositories) |
| 162 | ; will be loaded when executing tests. |
| 163 | enable_load_standalone_plugins_during_tests = 0 |
| 164 | |
| 165 | [Development] |
| 166 | ; Enables the development mode where we avoid most caching to make sure code changes will be directly applied as |
| 167 | ; some caches are only invalidated after an update otherwise. When enabled it'll also performs some validation checks. |
| 168 | ; For instance if you register a method in a widget we will verify whether the method actually exists and is public. |
| 169 | ; If not, we will show you a helpful warning to make it easy to find simple typos etc. |
| 170 | enabled = 0 |
| 171 | |
| 172 | ; if set to 1, javascript files will be included individually and neither merged nor minified. |
| 173 | ; this option must be set to 1 when adding, removing or modifying javascript files |
| 174 | ; Note that for quick debugging, instead of using below setting, you can add `&disable_merged_assets=1` to the Matomo URL |
| 175 | disable_merged_assets = 0 |
| 176 | |
| 177 | [General] |
| 178 | ; the following settings control whether Unique Visitors `nb_uniq_visitors` and Unique users `nb_users` will be processed for different period types. |
| 179 | ; year and range periods are disabled by default, to ensure optimal performance for high traffic Matomo instances |
| 180 | ; if you set it to 1 and want the Unique Visitors to be re-processed for reports in the past, drop all matomo_archive_* tables |
| 181 | ; it is recommended to always enable Unique Visitors and Unique Users processing for 'day' periods |
| 182 | enable_processing_unique_visitors_day = 1 |
| 183 | enable_processing_unique_visitors_week = 1 |
| 184 | enable_processing_unique_visitors_month = 1 |
| 185 | enable_processing_unique_visitors_year = 0 |
| 186 | enable_processing_unique_visitors_range = 0 |
| 187 | |
| 188 | ; controls whether Unique Visitors will be processed for groups of websites. these metrics describe the number |
| 189 | ; of unique visitors across the entire set of websites, so if a visitor visited two websites in the group, she |
| 190 | ; would still only be counted as one. only relevant when using plugins that group sites together |
| 191 | enable_processing_unique_visitors_multiple_sites = 0 |
| 192 | |
| 193 | ; The list of periods that are available in the Matomo calendar |
| 194 | ; Example use case: custom date range requests are processed in real time, |
| 195 | ; so they may take a few minutes on very high traffic website: you may remove "range" below to disable this period |
| 196 | enabled_periods_UI = "day,week,month,year,range" |
| 197 | enabled_periods_API = "day,week,month,year,range" |
| 198 | |
| 199 | ; whether to enable segment archiving cache |
| 200 | ; Note: if you use any plugins, this need to be compliant with Matomo and |
| 201 | ; * depending on the segment you create you may need a newer MySQL version (eg 5.7 or newer) |
| 202 | ; * use a reader database for archiving in case you have configured a database reader |
| 203 | enable_segments_cache = 1 |
| 204 | |
| 205 | ; whether to enable subquery cache for Custom Segment archiving queries |
| 206 | enable_segments_subquery_cache = 0 |
| 207 | ; Any segment subquery that matches more than segments_subquery_cache_limit IDs will not be cached, |
| 208 | ; and the original subquery executed instead. |
| 209 | segments_subquery_cache_limit = 100000 |
| 210 | ; TTL: Time to live for cache files, in seconds. Default to 60 minutes |
| 211 | segments_subquery_cache_ttl = 3600 |
| 212 | |
| 213 | ; when set to 1, all requests to Matomo will return a maintenance message without connecting to the DB |
| 214 | ; this is useful when upgrading using the shell command, to prevent other users from accessing the UI while Upgrade is in progress |
| 215 | maintenance_mode = 0 |
| 216 | |
| 217 | ; Defines the release channel that shall be used. Currently available values are: |
| 218 | ; "latest_stable", "latest_beta", "latest_4x_stable", "latest_4x_beta" |
| 219 | release_channel = "latest_stable" |
| 220 | |
| 221 | ; character used to automatically create categories in the Actions > Pages, Outlinks and Downloads reports |
| 222 | ; for example a URL like "example.com/blog/development/first-post" will create |
| 223 | ; the page first-post in the subcategory development which belongs to the blog category |
| 224 | action_url_category_delimiter = / |
| 225 | |
| 226 | ; similar to above, but this delimiter is only used for page titles in the Actions > Page titles report |
| 227 | action_title_category_delimiter = "" |
| 228 | |
| 229 | ; the maximum url category depth to track. if this is set to 2, then a url such as |
| 230 | ; "example.com/blog/development/first-post" would be treated as "example.com/blog/development". |
| 231 | ; this setting is used mainly to limit the amount of data that is stored by Matomo. |
| 232 | action_category_level_limit = 10 |
| 233 | |
| 234 | ; minimum number of websites to run autocompleter |
| 235 | autocomplete_min_sites = 5 |
| 236 | |
| 237 | ; maximum number of websites showed in search results in autocompleter |
| 238 | site_selector_max_sites = 15 |
| 239 | |
| 240 | ; if set to 1, shows sparklines (evolution graph) in 'All Websites' report (MultiSites plugin) |
| 241 | show_multisites_sparklines = 1 |
| 242 | |
| 243 | ; number of websites to display per page in the All Websites dashboard |
| 244 | all_websites_website_per_page = 50 |
| 245 | |
| 246 | ; if set to 0, the anonymous user will not be able to use the 'segments' parameter in the API request |
| 247 | ; this is useful to prevent full DB access to the anonymous user, or to limit performance usage |
| 248 | anonymous_user_enable_use_segments_API = 1 |
| 249 | |
| 250 | ; if browser trigger archiving is disabled, API requests with a &segment= parameter will still trigger archiving. |
| 251 | ; You can force the browser archiving to be disabled in most cases by setting this setting to 1 |
| 252 | ; The only time that the browser will still trigger archiving is when requesting a custom date range that is not pre-processed yet |
| 253 | browser_archiving_disabled_enforce = 0 |
| 254 | |
| 255 | ; Add custom currencies to Sites Manager. |
| 256 | currencies[BTC] = Bitcoin |
| 257 | |
| 258 | ; By default, users can create Segments which are to be processed in Real-time. |
| 259 | ; Setting this to 0 will force all newly created Custom Segments to be "Pre-processed (faster, requires archive.php cron)" |
| 260 | ; This can be useful if you want to prevent users from adding much load on the server. |
| 261 | ; Notes: |
| 262 | ; * any existing Segment set to "processed in Real time", will still be set to Real-time. |
| 263 | ; this will only affect custom segments added or modified after this setting is changed. |
| 264 | ; * users with at least 'view' access will still be able to create pre-processed segments, regardless |
| 265 | ; of what this is set to. |
| 266 | enable_create_realtime_segments = 1 |
| 267 | |
| 268 | ; Whether to enable the "Suggest values for segment" in the Segment Editor panel. |
| 269 | ; Set this to 0 in case your Matomo database is very big, and suggested values may not appear in time |
| 270 | enable_segment_suggested_values = 1 |
| 271 | |
| 272 | ; By default, any user with a "view" access for a website can create segment assigned to this website. |
| 273 | ; Set this to "admin" or "superuser" to require that users should have at least this access to create new segments. |
| 274 | ; Note: anonymous user (even if it has view access) is not allowed to create or edit segment. |
| 275 | ; Possible values are "view", "admin", "superuser" |
| 276 | adding_segment_requires_access = "view" |
| 277 | |
| 278 | ; Whether it is allowed for users to add segments that affect all websites or not. If there are many websites |
| 279 | ; this admin option can be used to prevent users from performing an action that will have a major impact |
| 280 | ; on Matomo performance. |
| 281 | allow_adding_segments_for_all_websites = 1 |
| 282 | |
| 283 | ; When archiving segments for the first time, this determines the oldest date that will be archived. |
| 284 | ; This option can be used to avoid archiving (for instance) the lastN years for every new segment. |
| 285 | ; Valid option values include: "beginning_of_time" (start date of archiving will not be changed) |
| 286 | ; "segment_last_edit_time" (start date of archiving will be the earliest last edit date found, |
| 287 | ; if none is found, the created date is used) |
| 288 | ; "segment_creation_time" (start date of archiving will be the creation date of the segment) |
| 289 | ; lastN where N is an integer (eg "last10" to archive for 10 days before the segment creation date) |
| 290 | process_new_segments_from = "beginning_of_time" |
| 291 | |
| 292 | ; this action name is used when the URL ends with a slash / |
| 293 | ; it is useful to have an actual string to write in the UI |
| 294 | action_default_name = index |
| 295 | |
| 296 | ; default language to use in Matomo |
| 297 | default_language = en |
| 298 | |
| 299 | ; default number of elements in the datatable |
| 300 | datatable_default_limit = 10 |
| 301 | |
| 302 | ; Each datatable report has a Row Limit selector at the bottom right. |
| 303 | ; By default you can select from 5 to 500 rows. You may customise the values below |
| 304 | ; -1 will be displayed as 'all' and it will export all rows (filter_limit=-1) |
| 305 | datatable_row_limits = "5,10,25,50,100,250,500,-1" |
| 306 | |
| 307 | ; default number of rows returned in API responses |
| 308 | ; this value is overwritten by the '# Rows to display' selector. |
| 309 | ; if set to -1, a click on 'Export as' will export all rows independently of the current '# Rows to display'. |
| 310 | API_datatable_default_limit = 100 |
| 311 | |
| 312 | ; When period=range, below the datatables, when user clicks on "export", the data will be aggregate of the range. |
| 313 | ; Here you can specify the comma separated list of formats for which the data will be exported aggregated by day |
| 314 | ; (ie. there will be a new "date" column). For example set to: "rss,tsv,csv" |
| 315 | datatable_export_range_as_day = "rss" |
| 316 | |
| 317 | ; This setting is overridden in the UI, under "User Settings". |
| 318 | ; The date and period loaded by Matomo uses the defaults below. Possible values: yesterday, today. |
| 319 | default_day = yesterday |
| 320 | ; Possible values: day, week, month, year. |
| 321 | default_period = day |
| 322 | |
| 323 | ; Time in seconds after which an archive will be computed again. This setting is used only for today's statistics. |
| 324 | ; This setting is overridden in the UI, under "General Settings". |
| 325 | ; This setting is only used if it hasn't been overridden via the UI yet, or if enable_general_settings_admin=0 |
| 326 | time_before_today_archive_considered_outdated = 900 |
| 327 | |
| 328 | ; Time in seconds after which an archive will be computed again. This setting is used only for week's statistics. |
| 329 | ; If set to "-1" (default), it will fall back to the UI setting under "General settings" unless enable_general_settings_admin=0 |
| 330 | ; is set. In this case it will default to "time_before_today_archive_considered_outdated"; |
| 331 | time_before_week_archive_considered_outdated = -1 |
| 332 | |
| 333 | ; Same as config setting "time_before_week_archive_considered_outdated" but it is only applied to monthly archives |
| 334 | time_before_month_archive_considered_outdated = -1 |
| 335 | |
| 336 | ; Same as config setting "time_before_week_archive_considered_outdated" but it is only applied to yearly archives |
| 337 | time_before_year_archive_considered_outdated = -1 |
| 338 | |
| 339 | ; Same as config setting "time_before_week_archive_considered_outdated" but it is only applied to range archives |
| 340 | time_before_range_archive_considered_outdated = -1 |
| 341 | |
| 342 | ; This setting is overridden in the UI, under "General Settings". |
| 343 | ; The default value is to allow browsers to trigger the Matomo archiving process. |
| 344 | ; This setting is only used if it hasn't been overridden via the UI yet, or if enable_general_settings_admin=0 |
| 345 | enable_browser_archiving_triggering = 1 |
| 346 | |
| 347 | ; By default, Matomo will force archiving of range periods from browser requests, even if enable_browser_archiving_triggering |
| 348 | ; is set to 0. This can sometimes create too much of a demand on system resources. Setting this option to 0 and |
| 349 | ; disabling browser trigger archiving will make sure ranges are not archived on browser request. Since the cron |
| 350 | ; archiver does not archive any custom date ranges, you must either disable range (using enabled_periods_API and enabled_periods_UI) |
| 351 | ; or make sure the date ranges users' want to see will be processed somehow. |
| 352 | archiving_range_force_on_browser_request = 1 |
| 353 | |
| 354 | ; By default Matomo will automatically archive all date ranges any user has chosen in his account settings. |
| 355 | ; This is limited to the available options last7, previous7, last30 and previous30. |
| 356 | ; If you need any other period, or want to ensure one of those is always archived, you can define them here |
| 357 | archiving_custom_ranges[] = |
| 358 | |
| 359 | ; By default Matomo runs OPTIMIZE TABLE SQL queries to free spaces after deleting some data. |
| 360 | ; If your Matomo tracks millions of pages, the OPTIMIZE TABLE queries might run for hours (seen in "SHOW FULL PROCESSLIST \g") |
| 361 | ; so you can disable these special queries here: |
| 362 | enable_sql_optimize_queries = 1 |
| 363 | |
| 364 | ; By default Matomo is purging complete date range archives to free spaces after deleting some data. |
| 365 | ; If you are pre-processing custom ranges using CLI task to make them easily available in UI, |
| 366 | ; you can prevent this action from happening by setting this parameter to value bigger than 1 |
| 367 | purge_date_range_archives_after_X_days = 1 |
| 368 | |
| 369 | ; MySQL minimum required version |
| 370 | ; note: timezone support added in 4.1.3 |
| 371 | minimum_mysql_version = 4.1 |
| 372 | |
| 373 | ; PostgreSQL minimum required version |
| 374 | minimum_pgsql_version = 8.3 |
| 375 | |
| 376 | ; Minimum advised memory limit in Mb in php.ini file (see memory_limit value) |
| 377 | ; Set to "-1" to always use the configured memory_limit value in php.ini file. |
| 378 | minimum_memory_limit = 128 |
| 379 | |
| 380 | ; Minimum memory limit in Mb enforced when archived via ./console core:archive |
| 381 | ; Set to "-1" to always use the configured memory_limit value in php.ini file. |
| 382 | minimum_memory_limit_when_archiving = 768 |
| 383 | |
| 384 | ; Matomo will check that usernames and password have a minimum length, and will check that characters are "allowed" |
| 385 | ; This can be disabled, if for example you wish to import an existing User database in Matomo and your rules are less restrictive |
| 386 | disable_checks_usernames_attributes = 0 |
| 387 | |
| 388 | ; Matomo will use the configured hash algorithm where possible. |
| 389 | ; For legacy data, fallback or non-security scenarios, we use md5. |
| 390 | hash_algorithm = whirlpool |
| 391 | |
| 392 | ; If set to 1, Matomo will automatically redirect all http:// requests to https:// |
| 393 | ; If SSL / https is not correctly configured on the server, this will break Matomo |
| 394 | ; If you set this to 1, and your SSL configuration breaks later on, you can always edit this back to 0 |
| 395 | ; it is recommended for security reasons to always use Matomo over https |
| 396 | force_ssl = 0 |
| 397 | |
| 398 | ; Session garbage collection on (as on some operating systems, i.e. Debian, it may be off by default) |
| 399 | session_gc_probability = 1 |
| 400 | |
| 401 | ; (DEPRECATED) has no effect |
| 402 | login_cookie_name = matomo_auth |
| 403 | |
| 404 | ; By default, the auth cookie is set only for the duration of session. |
| 405 | ; if "Remember me" is checked, the auth cookie will be valid for 14 days by default |
| 406 | login_cookie_expire = 1209600 |
| 407 | |
| 408 | ; Sets the session cookie path |
| 409 | login_cookie_path = |
| 410 | |
| 411 | ; the amount of time before an idle session is considered expired. only affects session that were created without the |
| 412 | ; "remember me" option checked |
| 413 | login_session_not_remembered_idle_timeout = 3600 |
| 414 | |
| 415 | ; email address that appears as a Sender in the password recovery email |
| 416 | ; if specified, {DOMAIN} will be replaced by the current Matomo domain |
| 417 | login_password_recovery_email_address = "password-recovery@{DOMAIN}" |
| 418 | ; name that appears as a Sender in the password recovery email |
| 419 | login_password_recovery_email_name = Matomo |
| 420 | |
| 421 | ; email address that appears as a Reply-to in the password recovery email |
| 422 | ; if specified, {DOMAIN} will be replaced by the current Matomo domain |
| 423 | login_password_recovery_replyto_email_address = "no-reply@{DOMAIN}" |
| 424 | ; name that appears as a Reply-to in the password recovery email |
| 425 | login_password_recovery_replyto_email_name = "No-reply" |
| 426 | |
| 427 | ; When configured, only users from a configured IP can log into your Matomo. You can define one or multiple |
| 428 | ; IPv4, IPv6, and IP ranges. You may also define hostnames. However, resolving hostnames in each request |
| 429 | ; may slightly slow down your Matomo. |
| 430 | ; This allowlist also affects API requests unless you disabled it via the setting |
| 431 | ; "login_allowlist_apply_to_reporting_api_requests" below. Note that neither this setting, nor the |
| 432 | ; "login_allowlist_apply_to_reporting_api_requests" restricts authenticated tracking requests (tracking requests |
| 433 | ; with a "token_auth" URL parameter). |
| 434 | ; |
| 435 | ; Examples: |
| 436 | ; login_allowlist_ip[] = 204.93.240.* |
| 437 | ; login_allowlist_ip[] = 204.93.177.0/24 |
| 438 | ; login_allowlist_ip[] = 199.27.128.0/21 |
| 439 | ; login_allowlist_ip[] = 2001:db8::/48 |
| 440 | ; login_allowlist_ip[] = matomo.org |
| 441 | |
| 442 | ; By default, if an allowlisted IP address is specified via "login_allowlist_ip[]", the reporting user interface as |
| 443 | ; well as HTTP Reporting API requests will only work for these allowlisted IPs. |
| 444 | ; Set this setting to "0" to allow HTTP Reporting API requests from any IP address. |
| 445 | login_allowlist_apply_to_reporting_api_requests = 1 |
| 446 | |
| 447 | ; By default when user logs out they are redirected to Matomo "homepage" usually the Login form. |
| 448 | ; Uncomment the next line to set a URL to redirect the user to after they log out of Matomo. |
| 449 | ; login_logout_url = http://... |
| 450 | |
| 451 | ; Set to 1 to disable the framebuster on standard Non-widgets pages (a click-jacking countermeasure). |
| 452 | ; Default is 0 (i.e., bust frames on all non Widget pages such as Login, API, Widgets, Email reports, etc.). |
| 453 | enable_framed_pages = 0 |
| 454 | |
| 455 | ; Set to 1 to disable the framebuster on Admin pages (a click-jacking countermeasure). |
| 456 | ; Default is 0 (i.e., bust frames on the Settings forms). |
| 457 | enable_framed_settings = 0 |
| 458 | |
| 459 | ; Set to 1 to allow using token_auths with write or admin access in iframes that embed Matomo. |
| 460 | ; Note that the token used will be in the URL in the iframe, and thus will be stored in webserver |
| 461 | ; logs and possibly other places. Using write or admin token_auths can be seen as a security risk, |
| 462 | ; though it can be necessary in some use cases. We do not recommend enabling this setting, for more |
| 463 | ; information view the FAQ: https://matomo.org/faq/troubleshooting/faq_147/ |
| 464 | enable_framed_allow_write_admin_token_auth = 0 |
| 465 | |
| 466 | ; language cookie name for session |
| 467 | language_cookie_name = matomo_lang |
| 468 | |
| 469 | ; standard email address displayed when sending emails |
| 470 | noreply_email_address = "noreply@{DOMAIN}" |
| 471 | |
| 472 | ; standard email name displayed when sending emails. If not set, a default name will be used. |
| 473 | noreply_email_name = "" |
| 474 | |
| 475 | ; set to 0 to disable sending of all emails. useful for testing. |
| 476 | emails_enabled = 1 |
| 477 | |
| 478 | ; set to 0 to disable sending of emails when a password or email is changed |
| 479 | enable_update_users_email = 1 |
| 480 | |
| 481 | ; feedback email address; |
| 482 | ; when testing, use your own email address or "nobody" |
| 483 | feedback_email_address = "feedback@matomo.org" |
| 484 | |
| 485 | ; using to set reply_to in reports e-mail to login of report creator |
| 486 | scheduled_reports_replyto_is_user_email_and_alias = 0 |
| 487 | |
| 488 | ; scheduled reports truncate limit |
| 489 | ; the report will be rendered with the first 23 rows and will aggregate other rows in a summary row |
| 490 | ; 23 rows table fits in one portrait page |
| 491 | scheduled_reports_truncate = 23 |
| 492 | |
| 493 | ; during archiving, Matomo will limit the number of results recorded, for performance reasons |
| 494 | ; maximum number of rows for any of the Referrers tables (keywords, search engines, campaigns, etc.) |
| 495 | datatable_archiving_maximum_rows_referrers = 1000 |
| 496 | ; maximum number of rows for any of the Referrers subtable (search engines by keyword, keyword by campaign, etc.) |
| 497 | datatable_archiving_maximum_rows_subtable_referrers = 50 |
| 498 | |
| 499 | ; maximum number of rows for the Users report |
| 500 | datatable_archiving_maximum_rows_userid_users = 50000 |
| 501 | |
| 502 | ; maximum number of rows for the Custom Dimensions report |
| 503 | datatable_archiving_maximum_rows_custom_dimensions = 1000 |
| 504 | ; maximum number of rows for the Custom Dimensions subtable reports |
| 505 | datatable_archiving_maximum_rows_subtable_custom_dimensions = 1000 |
| 506 | |
| 507 | ; maximum number of rows for any of the Actions tables (pages, downloads, outlinks) |
| 508 | datatable_archiving_maximum_rows_actions = 500 |
| 509 | ; maximum number of rows for pages in categories (sub pages, when clicking on the + for a page category) |
| 510 | ; note: should not exceed the display limit in Piwik\Actions\Controller::ACTIONS_REPORT_ROWS_DISPLAY |
| 511 | ; because each subdirectory doesn't have paging at the bottom, so all data should be displayed if possible. |
| 512 | datatable_archiving_maximum_rows_subtable_actions = 100 |
| 513 | ; maximum number of rows for the Site Search table |
| 514 | datatable_archiving_maximum_rows_site_search = 500 |
| 515 | |
| 516 | ; maximum number of rows for any of the Events tables (Categories, Actions, Names) |
| 517 | datatable_archiving_maximum_rows_events = 500 |
| 518 | ; maximum number of rows for sub-tables of the Events tables (eg. for the subtables Categories>Actions or Categories>Names). |
| 519 | datatable_archiving_maximum_rows_subtable_events = 500 |
| 520 | |
| 521 | ; maximum number of rows for other tables (Providers, User settings configurations) |
| 522 | datatable_archiving_maximum_rows_standard = 500 |
| 523 | |
| 524 | ; maximum number of rows to fetch from the database when archiving. if set to 0, no limit is used. |
| 525 | ; this can be used to speed up the archiving process, but is only useful if you're site has a large |
| 526 | ; amount of actions, referrers or custom variable name/value pairs. |
| 527 | archiving_ranking_query_row_limit = 50000 |
| 528 | |
| 529 | ; maximum number of actions that is shown in the visitor log for each visitor |
| 530 | visitor_log_maximum_actions_per_visit = 500 |
| 531 | |
| 532 | ; by default, the real time Live! widget will update every 5 seconds and refresh with new visits/actions/etc. |
| 533 | ; you can change the timeout so the widget refreshes more often, or not as frequently |
| 534 | live_widget_refresh_after_seconds = 5 |
| 535 | |
| 536 | ; by default, the Live! real time visitor count widget will check to see how many visitors your |
| 537 | ; website received in the last 3 minutes. changing this value will change the number of minutes |
| 538 | ; the widget looks in. |
| 539 | live_widget_visitor_count_last_minutes = 3 |
| 540 | |
| 541 | ; by default visitor profile will show aggregated information for the last up to 100 visits of a visitor |
| 542 | ; this limit can be adjusted by changing this value |
| 543 | live_visitor_profile_max_visits_to_aggregate = 100 |
| 544 | |
| 545 | ; If configured, will abort a MySQL query after the configured amount of seconds and show an error in the UI to for |
| 546 | ; example lower the date range or tweak the segment (if one is applied). Set it to -1 if the query time should not be |
| 547 | ; limited. Note: This feature requires a recent MySQL version (5.7 or newer). Some MySQL forks like MariaDB might not |
| 548 | ; support this feature which uses the MAX_EXECUTION_TIME hint. |
| 549 | live_query_max_execution_time = -1 |
| 550 | |
| 551 | ; In "All Websites" dashboard, when looking at today's reports (or a date range including today), |
| 552 | ; the page will automatically refresh every 5 minutes. Set to 0 to disable automatic refresh |
| 553 | multisites_refresh_after_seconds = 300 |
| 554 | |
| 555 | ; by default, an update notification for a new version of Matomo is shown to every user. Set to 1 if only |
| 556 | ; the superusers should see the notification. |
| 557 | show_update_notification_to_superusers_only = 0 |
| 558 | |
| 559 | ; Set to 1 if you're using https on your Matomo server and Matomo can't detect it, |
| 560 | ; e.g., a reverse proxy using https-to-http, or a web server that doesn't |
| 561 | ; set the HTTPS environment variable. |
| 562 | assume_secure_protocol = 0 |
| 563 | |
| 564 | ; Set to 1 if you're using more than one server for your Matomo installation. For example if you are using Matomo in a |
| 565 | ; load balanced environment, if you have configured failover or if you're just using multiple servers in general. |
| 566 | ; By enabling this flag we will for example not allow the installation of a plugin via the UI as a plugin would be only |
| 567 | ; installed on one server or a config one change would be only made on one server instead of all servers. |
| 568 | multi_server_environment = 0 |
| 569 | |
| 570 | ; List of proxy headers for client IP addresses |
| 571 | ; Matomo will determine the user IP by extracting the first IP address found in this proxy header. |
| 572 | ; |
| 573 | ; CloudFlare (CF-Connecting-IP) |
| 574 | ;proxy_client_headers[] = HTTP_CF_CONNECTING_IP |
| 575 | ; |
| 576 | ; ISP proxy (Client-IP) |
| 577 | ;proxy_client_headers[] = HTTP_CLIENT_IP |
| 578 | ; |
| 579 | ; de facto standard (X-Forwarded-For) |
| 580 | ;proxy_client_headers[] = HTTP_X_FORWARDED_FOR |
| 581 | |
| 582 | ; List of proxy headers for host IP addresses |
| 583 | ; |
| 584 | ; de facto standard (X-Forwarded-Host) |
| 585 | ;proxy_host_headers[] = HTTP_X_FORWARDED_HOST |
| 586 | |
| 587 | ; List of proxy IP addresses (or IP address ranges) to skip (if present in the above headers). |
| 588 | ; Generally, only required if there's more than one proxy between the visitor and the backend web server. |
| 589 | ; |
| 590 | ; Examples: |
| 591 | ;proxy_ips[] = 204.93.240.* |
| 592 | ;proxy_ips[] = 204.93.177.0/24 |
| 593 | ;proxy_ips[] = 199.27.128.0/21 |
| 594 | ;proxy_ips[] = 173.245.48.0/20 |
| 595 | |
| 596 | ; Set to 1 if you're using a proxy which is rewriting the URI. |
| 597 | ; By enabling this flag the header HTTP_X_FORWARDED_URI will be considered for the current script name. |
| 598 | proxy_uri_header = 0 |
| 599 | |
| 600 | ; Whether to enable trusted host checking. This can be disabled if you're running Matomo |
| 601 | ; on several URLs and do not wish to constantly edit the trusted host list. |
| 602 | enable_trusted_host_check = 1 |
| 603 | |
| 604 | ; List of trusted hosts (eg domain or subdomain names) when generating absolute URLs. |
| 605 | ; |
| 606 | ; Examples: |
| 607 | ;trusted_hosts[] = example.com |
| 608 | ;trusted_hosts[] = stats.example.com |
| 609 | |
| 610 | ; List of Cross-origin resource sharing domains (eg domain or subdomain names) when generating absolute URLs. |
| 611 | ; Described here: https://en.wikipedia.org/wiki/Cross-origin_resource_sharing |
| 612 | ; |
| 613 | ; Examples: |
| 614 | ;cors_domains[] = http://example.com |
| 615 | ;cors_domains[] = http://stats.example.com |
| 616 | ; |
| 617 | ; Or you may allow cross domain requests for all domains with: |
| 618 | ;cors_domains[] = * |
| 619 | |
| 620 | ; If you use this Matomo instance over multiple hostnames, Matomo will need to know |
| 621 | ; a unique instance_id for this instance, so that Matomo can serve the right custom logo and tmp/* assets, |
| 622 | ; independently of the hostname Matomo is currently running under. |
| 623 | ; instance_id = stats.example.com |
| 624 | |
| 625 | ; The API server is an essential part of the Matomo infrastructure/ecosystem to |
| 626 | ; provide services to Matomo installations, e.g., getLatestVersion and |
| 627 | ; subscribeNewsletter. |
| 628 | api_service_url = http://api.matomo.org |
| 629 | |
| 630 | ; When the ImageGraph plugin is activated, report metadata have an additional entry : 'imageGraphUrl'. |
| 631 | ; This entry can be used to request a static graph for the requested report. |
| 632 | ; When requesting report metadata with $period=range, Matomo needs to translate it to multiple periods for evolution graphs. |
| 633 | ; eg. $period=range&date=previous10 becomes $period=day&date=previous10. Use this setting to override the $period value. |
| 634 | graphs_default_period_to_plot_when_period_range = day |
| 635 | |
| 636 | ; When the ImageGraph plugin is activated, enabling this option causes the image graphs to show the evolution |
| 637 | ; within the selected period instead of the evolution across the last n periods. |
| 638 | graphs_show_evolution_within_selected_period = 0 |
| 639 | |
| 640 | ; This option controls the default number of days in the past to show in evolution graphs generated by the ImageGraph plugin |
| 641 | graphs_default_evolution_graph_last_days_amount = 30 |
| 642 | |
| 643 | ; The Overlay plugin shows the Top X following pages, Top X downloads and Top X outlinks which followed |
| 644 | ; a view of the current page. The value X can be set here. |
| 645 | overlay_following_pages_limit = 300 |
| 646 | |
| 647 | ; With this option, you can disable the framed mode of the Overlay plugin. Use it if your website contains a framebuster. |
| 648 | overlay_disable_framed_mode = 0 |
| 649 | |
| 650 | ; Controls whether the user is able to upload a custom logo for their Matomo install |
| 651 | enable_custom_logo = 1 |
| 652 | |
| 653 | ; By default we check whether the Custom logo is writable or not, before we display the Custom logo file uploader |
| 654 | enable_custom_logo_check = 1 |
| 655 | |
| 656 | ; If php is running in a chroot environment, when trying to import CSV files with createTableFromCSVFile(), |
| 657 | ; Mysql will try to load the chrooted path (which is incomplete). To prevent an error, here you can specify the |
| 658 | ; absolute path to the chroot environment. eg. '/path/to/matomo/chrooted/' |
| 659 | absolute_chroot_path = |
| 660 | |
| 661 | ; The path (relative to the Matomo directory) in which Matomo temporary files are stored. |
| 662 | ; Defaults to ./tmp (the tmp/ folder inside the Matomo directory) |
| 663 | tmp_path = "/tmp" |
| 664 | |
| 665 | ; The absolute path to a PHP binary file in case Matomo cannot detect your PHP binary. If async CLI archiving cannot be |
| 666 | ; used on your server this may make it work. Ensure the configured PHP binary is of type CLI and not for example cgi or |
| 667 | ; litespeed. To find out the type of interface for a PHP binary execute this command: php -r "echo php_sapi_name();" |
| 668 | php_binary_path = "" |
| 669 | |
| 670 | ; In some rare cases it may be useful to explicitly tell Matomo not to use LOAD DATA INFILE |
| 671 | ; This may for example be useful when doing Mysql AWS replication |
| 672 | enable_load_data_infile = 1 |
| 673 | |
| 674 | ; By setting this option to 0: |
| 675 | ; - links to Enable/Disable/Uninstall plugins will be hidden and disabled |
| 676 | ; - links to Uninstall themes will be disabled (but user can still enable/disable themes) |
| 677 | enable_plugins_admin = 1 |
| 678 | |
| 679 | ; By setting this option to 0 the users management will be disabled |
| 680 | enable_users_admin = 1 |
| 681 | |
| 682 | ; By setting this option to 0 the websites management will be disabled |
| 683 | enable_sites_admin = 1 |
| 684 | |
| 685 | ; By setting this option to 1, it will be possible for Super Users to upload Matomo plugin ZIP archives directly in Matomo Administration. |
| 686 | ; Enabling this opens a remote code execution vulnerability where |
| 687 | ; an attacker who gained Super User access could execute custom PHP code in a Matomo plugin. |
| 688 | enable_plugin_upload = 0 |
| 689 | |
| 690 | ; By setting this option to 0 (e.g. in common.config.ini.php) the installer will be disabled. |
| 691 | enable_installer = 1 |
| 692 | |
| 693 | ; By setting this option to 0, you can prevent Super User from editing the Geolocation settings. |
| 694 | enable_geolocation_admin = 1 |
| 695 | |
| 696 | ; By setting this option to 0, the old raw data and old report data purging features will be hidden from the UI |
| 697 | ; Note: log purging and old data purging still occurs, just the Super User cannot change the settings. |
| 698 | enable_delete_old_data_settings_admin = 1 |
| 699 | |
| 700 | ; By setting this option to 0, the following settings will be hidden and disabled from being set in the UI: |
| 701 | ; - Archiving settings |
| 702 | ; - Update settings |
| 703 | ; - Email server settings |
| 704 | ; - Trusted Matomo Hostname |
| 705 | enable_general_settings_admin = 1 |
| 706 | |
| 707 | ; Disabling this will disable features like automatic updates for Matomo, |
| 708 | ; its plugins and components like the GeoIP database, referrer spam blacklist or search engines and social network definitions |
| 709 | enable_internet_features = 1 |
| 710 | |
| 711 | ; By setting this option to 0, it will disable the "Auto update" feature |
| 712 | enable_auto_update = 1 |
| 713 | |
| 714 | ; By setting this option to 0, no emails will be sent in case of an available core. |
| 715 | ; If set to 0 it also disables the "sent plugin update emails" feature in general and the related setting in the UI. |
| 716 | enable_update_communication = 1 |
| 717 | |
| 718 | ; Comma separated list of plugin names for which console commands should be loaded (applies when Matomo is not installed yet) |
| 719 | always_load_commands_from_plugin= |
| 720 | |
| 721 | ; This controls whether the pivotBy query parameter can be used with any dimension or just subtable |
| 722 | ; dimensions. If set to 1, it will fetch a report with a segment for each row of the table being pivoted. |
| 723 | ; At present, this is very inefficient, so it is disabled by default. |
| 724 | pivot_by_filter_enable_fetch_by_segment = 0 |
| 725 | |
| 726 | ; This controls the default maximum number of columns to display in a pivot table. Since a pivot table displays |
| 727 | ; a table's rows as columns, the number of columns can become very large, which will affect webpage layouts. |
| 728 | ; Set to -1 to specify no limit. Note: The pivotByColumnLimit query parameter can be used to override this default |
| 729 | ; on a per-request basis; |
| 730 | pivot_by_filter_default_column_limit = 10 |
| 731 | |
| 732 | ; If set to 0 it will disable advertisements for providers of Professional Support for Matomo. |
| 733 | piwik_professional_support_ads_enabled = 1 |
| 734 | |
| 735 | ; The number of days to wait before sending the JavaScript tracking code email reminder. |
| 736 | num_days_before_tracking_code_reminder = 5 |
| 737 | |
| 738 | ; The maximum number of segments that can be compared simultaneously. |
| 739 | data_comparison_segment_limit = 5 |
| 740 | |
| 741 | ; The maximum number of periods that can be compared simultaneously. |
| 742 | data_comparison_period_limit = 5 |
| 743 | |
| 744 | ; The path to a custom cacert.pem file Matomo should use. |
| 745 | ; By default Matomo uses a file extracted from the Firefox browser and provided here: https://curl.haxx.se/docs/caextract.html. |
| 746 | ; The file contains root CAs and is used to determine if the chain of a SSL certificate is valid and it is safe to connect. |
| 747 | ; Most users will not have to use a custom file here, but if you run your Matomo instance behind a proxy server/firewall that |
| 748 | ; breaks and reencrypts SSL connections you can set your custom file here. |
| 749 | custom_cacert_pem= |
| 750 | |
| 751 | ; Whether or not to send weekly emails to superusers about tracking failures. |
| 752 | ; Default is 1. |
| 753 | enable_tracking_failures_notification = 1 |
| 754 | |
| 755 | ; Controls how many months in the past reports are re-archived for plugins that support |
| 756 | ; doing this (such as CustomReports). Set to 0 to disable the feature. Default is 6. |
| 757 | rearchive_reports_in_past_last_n_months = last6 |
| 758 | |
| 759 | [Tracker] |
| 760 | |
| 761 | ; When enabled and a userId is set, then the visitorId will be automatically set based on the userId. This allows to |
| 762 | ; identify the same user as the same visitor across devices. |
| 763 | ; Disabling this feature can be useful for example when using the third party cookie, where all Matomo tracked sites |
| 764 | ; use the same "global" visitorId for a device and you want to see when the same user switches between devices. |
| 765 | enable_userid_overwrites_visitorid = 1 |
| 766 | |
| 767 | ; Matomo uses "Privacy by default" model. When one of your users visit multiple of your websites tracked in this Matomo, |
| 768 | ; Matomo will create for this user a fingerprint that will be different across the multiple websites. |
| 769 | ; If you want to track unique users across websites you may set this setting to 1. |
| 770 | ; Note: setting this to 0 increases your users' privacy. |
| 771 | enable_fingerprinting_across_websites = 0 |
| 772 | |
| 773 | ; Matomo uses first party cookies by default. If set to 1, |
| 774 | ; the visit ID cookie will be set on the Matomo server domain as well |
| 775 | ; this is useful when you want to do cross websites analysis |
| 776 | use_third_party_id_cookie = 0 |
| 777 | |
| 778 | ; If tracking does not work for you or you are stuck finding an issue, you might want to enable the tracker debug mode. |
| 779 | ; Once enabled (set to 1) messages will be logged to all loggers defined in "[log] log_writers" config. |
| 780 | debug = 0 |
| 781 | |
| 782 | ; This option is an alternative to the debug option above. When set to 1, you can debug tracker request by adding |
| 783 | ; a debug=1 query parameter in the URL. All other HTTP requests will not have debug enabled. For security reasons this |
| 784 | ; option should be only enabled if really needed and only for a short time frame. Otherwise anyone can set debug=1 and |
| 785 | ; see the log output as well. |
| 786 | debug_on_demand = 0 |
| 787 | |
| 788 | ; This setting is described in this FAQ: https://matomo.org/faq/how-to/faq_175/ |
| 789 | ; Note: generally this should only be set to 1 in an intranet setting, where most users have the same configuration (browsers, OS) |
| 790 | ; and the same IP. If left to 0 in this setting, all visitors will be counted as one single visitor. |
| 791 | trust_visitors_cookies = 0 |
| 792 | |
| 793 | ; name of the cookie used to store the visitor information |
| 794 | ; This is used only if use_third_party_id_cookie = 1 |
| 795 | cookie_name = _pk_uid |
| 796 | |
| 797 | ; by default, the Matomo tracking cookie expires in 13 months (365 + 28 days) |
| 798 | ; This is used only if use_third_party_id_cookie = 1 |
| 799 | cookie_expire = 33955200; |
| 800 | |
| 801 | ; The path on the server in which the cookie will be available on. |
| 802 | ; Defaults to empty. See spec in https://curl.haxx.se/rfc/cookie_spec.html |
| 803 | ; This is used for the Ignore cookie, and the third party cookie if use_third_party_id_cookie = 1 |
| 804 | cookie_path = |
| 805 | |
| 806 | ; The domain on the server in which the cookie will be available on. |
| 807 | ; Defaults to empty. See spec in https://curl.haxx.se/rfc/cookie_spec.html |
| 808 | ; This is used for the third party cookie if use_third_party_id_cookie = 1 |
| 809 | cookie_domain = |
| 810 | |
| 811 | ; set to 0 if you want to stop tracking the visitors. Useful if you need to stop all the connections on the DB. |
| 812 | record_statistics = 1 |
| 813 | |
| 814 | ; length of a visit in seconds. If a visitor comes back on the website visit_standard_length seconds |
| 815 | ; after their last page view, it will be recorded as a new visit. In case you are using the Matomo JavaScript tracker to |
| 816 | ; calculate the visit count correctly, make sure to call the method "setSessionCookieTimeout" eg |
| 817 | ; `_paq.push(['setSessionCookieTimeout', timeoutInSeconds=1800])` |
| 818 | visit_standard_length = 1800 |
| 819 | |
| 820 | ; The amount of time in the past to match the current visitor to a known visitor via fingerprint. Defaults to visit_standard_length. |
| 821 | ; If you are looking for higher accuracy of "returning visitors" metrics, you may set this value to 86400 or more. |
| 822 | ; This is especially useful when you use the Tracking API where tracking Returning Visitors often depends on this setting. |
| 823 | ; The value window_look_back_for_visitor is used only if it is set to greater than visit_standard_length. |
| 824 | ; Note: visitors with visitor IDs will be matched by visitor ID from any point in time, this is only for recognizing visitors |
| 825 | ; by device fingerprint. |
| 826 | window_look_back_for_visitor = 0 |
| 827 | |
| 828 | ; visitors that stay on the website and view only one page will be considered as time on site of 0 second |
| 829 | default_time_one_page_visit = 0 |
| 830 | |
| 831 | ; Comma separated list of URL query string variable names that will be removed from your tracked URLs |
| 832 | ; By default, Matomo will remove the most common parameters which are known to change often (eg. session ID parameters) |
| 833 | url_query_parameter_to_exclude_from_url = "gclid,fbclid,fb_xd_fragment,fb_comment_id,phpsessid,jsessionid,sessionid,aspsessionid,doing_wp_cron,sid,pk_vid" |
| 834 | |
| 835 | ; if set to 1, Matomo attempts a "best guess" at the visitor's country of |
| 836 | ; origin when the preferred language tag omits region information. |
| 837 | ; The mapping is defined in core/DataFiles/LanguageToCountry.php, |
| 838 | enable_language_to_country_guess = 1 |
| 839 | |
| 840 | ; When the `./console core:archive` cron hasn't been setup, we still need to regularly run some maintenance tasks. |
| 841 | ; Visits to the Tracker will try to trigger Scheduled Tasks (eg. scheduled PDF/HTML reports by email). |
| 842 | ; Scheduled tasks will only run if 'Enable Matomo Archiving from Browser' is enabled in the General Settings. |
| 843 | ; Tasks run once every hour maximum, they might not run every hour if traffic is low. |
| 844 | ; Set to 0 to disable Scheduled tasks completely. |
| 845 | scheduled_tasks_min_interval = 3600 |
| 846 | |
| 847 | ; name of the cookie to ignore visits |
| 848 | ignore_visits_cookie_name = matomo_ignore |
| 849 | |
| 850 | ; Comma separated list of variable names that will be read to define a Campaign name, for example CPC campaign |
| 851 | ; Example: If a visitor first visits 'index.php?matomo_campaign=Adwords-CPC' then it will be counted as a campaign referrer named 'Adwords-CPC' |
| 852 | ; Includes by default the GA style campaign parameters |
| 853 | campaign_var_name = "pk_cpn,pk_campaign,piwik_campaign,mtm_campaign,matomo_campaign,utm_campaign,utm_source,utm_medium" |
| 854 | |
| 855 | ; Comma separated list of variable names that will be read to track a Campaign Keyword |
| 856 | ; Example: If a visitor first visits 'index.php?matomo_campaign=Adwords-CPC&matomo_kwd=My killer keyword' ; |
| 857 | ; then it will be counted as a campaign referrer named 'Adwords-CPC' with the keyword 'My killer keyword' |
| 858 | ; Includes by default the GA style campaign keyword parameter utm_term |
| 859 | campaign_keyword_var_name = "pk_kwd,pk_keyword,piwik_kwd,mtm_kwd,mtm_keyword,matomo_kwd,utm_term" |
| 860 | |
| 861 | ; if set to 1, actions that contain different campaign information from the visitor's ongoing visit will |
| 862 | ; be treated as the start of a new visit. This will include situations when campaign information was absent before, |
| 863 | ; but is present now. |
| 864 | create_new_visit_when_campaign_changes = 1 |
| 865 | |
| 866 | ; if set to 1, actions that contain different website referrer information from the visitor's ongoing visit |
| 867 | ; will be treated as the start of a new visit. This will include situations when website referrer information was |
| 868 | ; absent before, but is present now. |
| 869 | create_new_visit_when_website_referrer_changes = 0 |
| 870 | |
| 871 | ; ONLY CHANGE THIS VALUE WHEN YOU DO NOT USE MATOMO ARCHIVING, SINCE THIS COULD CAUSE PARTIALLY MISSING ARCHIVE DATA |
| 872 | ; Whether to force a new visit at midnight for every visitor. Default 1. |
| 873 | create_new_visit_after_midnight = 1 |
| 874 | |
| 875 | ; maximum length of a Page Title or a Page URL recorded in the log_action.name table |
| 876 | page_maximum_length = 1024; |
| 877 | |
| 878 | ; Tracker cache files are the simple caching layer for Tracking. |
| 879 | ; TTL: Time to live for cache files, in seconds. Default to 5 minutes. |
| 880 | tracker_cache_file_ttl = 300 |
| 881 | |
| 882 | ; Whether Bulk tracking requests to the Tracking API requires the token_auth to be set. |
| 883 | bulk_requests_require_authentication = 0 |
| 884 | |
| 885 | ; Whether Bulk tracking requests will be wrapped within a DB Transaction. |
| 886 | ; This greatly increases performance of Log Analytics and in general any Bulk Tracking API requests. |
| 887 | bulk_requests_use_transaction = 1 |
| 888 | |
| 889 | ; DO NOT USE THIS SETTING ON PUBLICLY AVAILABLE MATOMO SERVER |
| 890 | ; !!! Security risk: if set to 0, it would allow anyone to push data to Matomo with custom dates in the past/future and even with fake IPs! |
| 891 | ; When using the Tracking API, to override either the datetime and/or the visitor IP, |
| 892 | ; token_auth with an "admin" access is required. If you set this setting to 0, the token_auth will not be required anymore. |
| 893 | ; DO NOT USE THIS SETTING ON PUBLIC MATOMO SERVERS |
| 894 | tracking_requests_require_authentication = 1 |
| 895 | |
| 896 | ; By default, Matomo accepts only tracking requests for up to 1 day in the past. For tracking requests with a custom date |
| 897 | ; date is older than 1 day, Matomo requires an authenticated tracking requests. By setting this config to another value |
| 898 | ; You can change how far back Matomo will track your requests without authentication. The configured value is in seconds. |
| 899 | tracking_requests_require_authentication_when_custom_timestamp_newer_than = 86400; |
| 900 | |
| 901 | ; if set to 1, all the SQL queries will be recorded by the profiler |
| 902 | ; and a profiling summary will be printed at the end of the request |
| 903 | ; NOTE: you must also set "[Tracker] debug = 1" to enable the profiler. |
| 904 | enable_sql_profiler = 0 |
| 905 | |
| 906 | ; Enables using referrer spam blacklist. |
| 907 | enable_spam_filter = 1 |
| 908 | |
| 909 | ; If a value greater than 0 is configured, Matomo will configure MySQL with the set lock wait timeout in seconds during a |
| 910 | ; tracking request. This can be useful if you have a high concurrency load on your server and want to reduce the time of |
| 911 | ; lock wait times. For example configuring a value of 3-10 seconds may give your Matomo a performance boost if you have |
| 912 | ; many concurrent tracking requests for the same visitor. When enabling this feature, make sure the MySQL |
| 913 | ; variable "innodb_rollback_on_timeout" is turned off. Only configure if really needed. The lower the value the more tracking |
| 914 | ; requests may be discarded due to too low lock wait time. |
| 915 | innodb_lock_wait_timeout = 0 |
| 916 | |
| 917 | ; Allows you to exclude specific requests from being tracked. The definition is similar to segments. |
| 918 | ; The following operands are supported: Equals: `==`, Not equals: `!=`, Contains: `=@`, Not Contains: `!@`, Starts with: `=^`, Ends with: `=$`. |
| 919 | ; The structure is as following: {tracking parameter}{operand}{value to match}. |
| 920 | ; For example "e_c==Media" means that all tracking requests will be excluded where the event category is Media. |
| 921 | ; Multiple exclusions can be configured separated by a comma. The request will be excluded if any expressions matches (not all of them). For example: "e_c==Media,action_name=@privacy". |
| 922 | ; This would also exclude any request from being tracked where the page title contains privacy. |
| 923 | ; All comparisons are performed case insensitve. The value to match on the right side should be URL encoded. |
| 924 | ; For example: "action_name=^foo%2Cbar" would exclude page titles that start with "foo,bar". |
| 925 | ; For a list of tracking parameters you can use on the left side view https://developer.matomo.org/api-reference/tracking-api |
| 926 | exclude_requests = "" |
| 927 | |
| 928 | [Segments] |
| 929 | ; Reports with segmentation in API requests are processed in real time. |
| 930 | ; On high traffic websites it is recommended to pre-process the data |
| 931 | ; so that the analytics reports are always fast to load. |
| 932 | ; You can define below the list of Segments strings |
| 933 | ; for which all reports should be Archived during the cron execution |
| 934 | ; All segment values MUST be URL encoded. |
| 935 | ;Segments[]="visitorType==new" |
| 936 | ;Segments[]="visitorType==returning,visitorType==returningCustomer" |
| 937 | |
| 938 | ; If you define Custom Variables for your visitor, for example set the visit type |
| 939 | ;Segments[]="customVariableName1==VisitType;customVariableValue1==Customer" |
| 940 | |
| 941 | [Deletelogs] |
| 942 | ; delete_logs_enable - enable (1) or disable (0) delete log feature. Make sure that all archives for the given period have been processed (setup a cronjob!), |
| 943 | ; otherwise you may lose tracking data. |
| 944 | ; delete_logs_schedule_lowest_interval - lowest possible interval between two table deletes, for tables named log_* (in days, 1|7|30). Default: 7. |
| 945 | ; delete_logs_older_than - delete data older than XX (days). Default: 180 |
| 946 | ; delete_logs_unused_actions_schedule_lowest_interval - lowest possible interval between two table deletes, for table log_action (in days, 1|7|30). Default: 30. |
| 947 | ; delete_logs_max_rows_per_query and delete_logs_unused_actions_max_rows_per_query can be increased for large sites to speed up delete processes |
| 948 | ; |
| 949 | ; The higher value one assign to *_schedule_lowest_interval, the longer the data pruning/deletion will take. This is caused by the fact there is more data to evaluate and process every month, than every week. |
| 950 | delete_logs_enable = 0 |
| 951 | delete_logs_schedule_lowest_interval = 7 |
| 952 | delete_logs_older_than = 180 |
| 953 | delete_logs_max_rows_per_query = 100000 |
| 954 | delete_logs_unused_actions_max_rows_per_query = 100000 |
| 955 | enable_auto_database_size_estimate = 1 |
| 956 | enable_database_size_estimate = 1 |
| 957 | delete_logs_unused_actions_schedule_lowest_interval = 30 |
| 958 | |
| 959 | [Deletereports] |
| 960 | delete_reports_enable = 0 |
| 961 | delete_reports_older_than = 12 |
| 962 | delete_reports_keep_basic_metrics = 1 |
| 963 | delete_reports_keep_day_reports = 0 |
| 964 | delete_reports_keep_week_reports = 0 |
| 965 | delete_reports_keep_month_reports = 1 |
| 966 | delete_reports_keep_year_reports = 1 |
| 967 | delete_reports_keep_range_reports = 0 |
| 968 | delete_reports_keep_segment_reports = 0 |
| 969 | |
| 970 | [mail] |
| 971 | defaultHostnameIfEmpty = defaultHostnameIfEmpty.example.org ; default Email @hostname, if current host can't be read from system variables |
| 972 | transport = ; smtp (using the configuration below) or empty (using built-in mail() function) |
| 973 | port = ; optional; defaults to 25 when security is none or tls; 465 for ssl |
| 974 | host = ; SMTP server address |
| 975 | type = ; SMTP Auth type. By default: NONE. For example: LOGIN |
| 976 | username = ; SMTP username |
| 977 | password = ; SMTP password |
| 978 | encryption = ; SMTP transport-layer encryption, either 'ssl', 'tls', or empty (i.e., none). |
| 979 | |
| 980 | [proxy] |
| 981 | type = BASIC ; proxy type for outbound/outgoing connections; currently, only BASIC is supported |
| 982 | host = ; Proxy host: the host name of your proxy server (mandatory) |
| 983 | port = ; Proxy port: the port that the proxy server listens to. There is no standard default, but 80, 1080, 3128, and 8080 are popular |
| 984 | username = ; Proxy username: optional; if specified, password is mandatory |
| 985 | password = ; Proxy password: optional; if specified, username is mandatory |
| 986 | |
| 987 | [Plugins] |
| 988 | ; list of plugins (in order they will be loaded) that are activated by default in the Matomo platform |
| 989 | Plugins[] = CorePluginsAdmin |
| 990 | Plugins[] = CoreAdminHome |
| 991 | Plugins[] = CoreHome |
| 992 | Plugins[] = WebsiteMeasurable |
| 993 | Plugins[] = IntranetMeasurable |
| 994 | Plugins[] = Diagnostics |
| 995 | Plugins[] = CoreVisualizations |
| 996 | Plugins[] = Proxy |
| 997 | Plugins[] = API |
| 998 | Plugins[] = Widgetize |
| 999 | Plugins[] = Transitions |
| 1000 | Plugins[] = LanguagesManager |
| 1001 | Plugins[] = Actions |
| 1002 | Plugins[] = Dashboard |
| 1003 | Plugins[] = MultiSites |
| 1004 | Plugins[] = Referrers |
| 1005 | Plugins[] = UserLanguage |
| 1006 | Plugins[] = DevicesDetection |
| 1007 | Plugins[] = Goals |
| 1008 | Plugins[] = Ecommerce |
| 1009 | Plugins[] = SEO |
| 1010 | Plugins[] = Events |
| 1011 | Plugins[] = UserCountry |
| 1012 | Plugins[] = GeoIp2 |
| 1013 | Plugins[] = VisitsSummary |
| 1014 | Plugins[] = VisitFrequency |
| 1015 | Plugins[] = VisitTime |
| 1016 | Plugins[] = VisitorInterest |
| 1017 | Plugins[] = RssWidget |
| 1018 | Plugins[] = Feedback |
| 1019 | Plugins[] = Monolog |
| 1020 | |
| 1021 | Plugins[] = Login |
| 1022 | Plugins[] = TwoFactorAuth |
| 1023 | Plugins[] = UsersManager |
| 1024 | Plugins[] = SitesManager |
| 1025 | Plugins[] = Installation |
| 1026 | Plugins[] = CoreUpdater |
| 1027 | Plugins[] = CoreConsole |
| 1028 | Plugins[] = ScheduledReports |
| 1029 | Plugins[] = UserCountryMap |
| 1030 | Plugins[] = Live |
| 1031 | Plugins[] = PrivacyManager |
| 1032 | Plugins[] = ImageGraph |
| 1033 | Plugins[] = Annotations |
| 1034 | Plugins[] = MobileMessaging |
| 1035 | Plugins[] = Overlay |
| 1036 | Plugins[] = SegmentEditor |
| 1037 | Plugins[] = Insights |
| 1038 | Plugins[] = Morpheus |
| 1039 | Plugins[] = Contents |
| 1040 | Plugins[] = BulkTracking |
| 1041 | Plugins[] = Resolution |
| 1042 | Plugins[] = DevicePlugins |
| 1043 | Plugins[] = Heartbeat |
| 1044 | Plugins[] = Intl |
| 1045 | Plugins[] = Marketplace |
| 1046 | Plugins[] = ProfessionalServices |
| 1047 | Plugins[] = UserId |
| 1048 | Plugins[] = CustomJsTracker |
| 1049 | Plugins[] = Tour |
| 1050 | Plugins[] = PagePerformance |
| 1051 | Plugins[] = CustomDimensions |
| 1052 | |
| 1053 | [PluginsInstalled] |
| 1054 | PluginsInstalled[] = Diagnostics |
| 1055 | PluginsInstalled[] = Login |
| 1056 | PluginsInstalled[] = CoreAdminHome |
| 1057 | PluginsInstalled[] = UsersManager |
| 1058 | PluginsInstalled[] = SitesManager |
| 1059 | PluginsInstalled[] = Installation |
| 1060 | PluginsInstalled[] = Monolog |
| 1061 | PluginsInstalled[] = Intl |
| 1062 | |
| 1063 | [APISettings] |
| 1064 | ; Any key/value pair can be added in this section, they will be available via the REST call |
| 1065 | ; index.php?module=API&method=API.getSettings |
| 1066 | ; This can be used to expose values from Matomo, to control for example a Mobile app tracking |
| 1067 | SDK_batch_size = 10 |
| 1068 | SDK_interval_value = 30 |
| 1069 | |
| 1070 | ; NOTE: do not directly edit this file! See notice at the top |
| 1071 |