Privacy and Exclusion settings in network mode are managed per blog but should be managed in one place

Nobody has claimed this yet.

That's because when Matomo is running in WP Multisite network mode, then most settings are managed in one place. But all settings that are stored in Matomo itself need to be managed per blog as we have a separate install for each blog. It's explained here: https://matomo.org/faq/wordpress/does-it-support-wp-multisite/

I figured out a way to sync the exclusion settings across blogs but it would only work for blogs that exist at the time. It wouldn't sync it for newly added blogs. We'd basically need to validate the entered data somehow, then also store the configured data in WP-Options or so, and sync these settings when we sync each blog/site.

For privacy settings, as well as any other admin setting in Matomo this becomes even more tricky and might not be feasible easily. We'd basically need to listen to several API methods and sync these calls across sites and also across blogs that are added in the future.

Another workaround be of course using one Matomo install for all blogs. This has several problems though eg in regards to not being able to access the uploads/cache dir etc. meaning we won't be always able to find config files, JS tracker files etc.

The best workaround is currently using [Matomo On-Premise](https://matomo.org/docs/installation/) or [Matomo Cloud](https://matomo.org/hosting/) in combination with the [WP-Matomo plugin](https://wordpress.org/plugins/wp-piwik/).

The issue names no files, tests, or code entry points; start by reviewing the linked WP Multisite explanation and the plugin's current per-blog settings behavior. Define how privacy and exclusion settings should sync for existing and newly added blogs, then establish a feasible completion criterion before implementation.

Written by the indexing model from the issue text.