چۈشەندۈرۈش
I needed to have a clean and small plugin that offers data protection options for users running sites in Germany.
Unlike many other Google Analytics plugins it offers to anonymize IPs as it’s neccessary for german users in order to have the GA code respect german data protection rules.
Features:
- Simple and guided setup
- Lightweight and fast
- Anonymize IP (recommended for german users to respect german/european data protection rules according to DSGVO/GDPR)
- Usercentrics support (recommended for german users to respect german/european data protection rules according to DSGVO/GDPR)
Included languages:
- ئىنگلىزچە
- German (de_DE) (Thanks to me ;-))
- Spanish (es_ES) (Spanish translation by Ibidem Group)
Looking for more WordPress plugins? Visit www.schloebe.de/portfolio/
ئېكران كەسمىسى
Admin Options Page
ئورنىتىش
- Download the plugin and unzip it.
- Upload the folder goolytics/ to your /wp-content/plugins/ folder.
- Activate the plugin from your WordPress admin panel.
- Installation finished.
FAQ
None. Yet.
باھالاشلار
تۆھپىكار ۋە ئىجادكار
«Goolytics – Simple Google Analytics» كودى ئوچۇق يۇمشاق دېتال. تۆۋەندىكى كىشىلەر بۇ قىستۇرمىغا تۆھپە قوشقان.
تۆھپىكار
«Goolytics – Simple Google Analytics» 1 تىلغا تەرجىمە قىلىنغان. تەرجىمانلارنىڭ تۆھپىسى ئۈچۈن رەھمەت.
«Goolytics – Simple Google Analytics» نى تىلىڭىزغا تەرجىمە قىلىڭ
ئىجادىيەتكە قىزىقامسىز؟
كودقا كۆز يۈگۈرتۈپ، SVN خەزىنە تەكشۈرۈپ ياكى RSSئارقىلىق ئىجادىيەت خاتىرىسىگە مۇشتەرى بولغىلى بولىدۇ.
ئۆزگىرىش خاتىرىسى
1.1.2
- Fixed Admin+ Stored XSS vulnerability
1.1.1
- Localization preparations for translate.wordpress.org
1.1.0
- Switched from old ga.js-Code to Global Site Tag / Universal Analytics.
- Added Usercentrics support (including e-recht24.de’s Usercentrics consent tool!)
1.0.6
- WordPress 5.3 compatibility
1.0.5
- WordPress 4.8 compatibility
1.0.4
- WordPress 4.7 compatibility
- PHP 7 compatibility
1.0.3
- Settings page visual improvements (Thanks pixelkicks!)
1.0.2
- Settings page visual improvements
1.0.1
- ›Redefining already defined constructor‹ bug that occured on several configurations
- WP 3.8 compatibility
1.0
- Initial release