Linux 软件免费装
Banner图

Effortless Landing Page Tracking for Matomo

开发者 domclic
更新时间 2025年5月7日 07:21
PHP版本: 7.4 及以上
WordPress版本: 6.8
版权: GPLv2 or later
版权网址: 版权信息

标签

tracking seo analytics multisite matomo

下载

1.3.9

详情介绍:

Effortless Landing Page Tracking for Matomo is a lightweight WordPress plugin that seamlessly integrates Matomo analytics across all pages of your site. Designed for both single-site and multisite WordPress installations, it allows you to configure your Matomo URL, Site ID, and optional event tracking through an intuitive settings page. In multisite environments, settings are managed exclusively via the Network Admin, ensuring centralized control. The plugin inserts the Matomo tracking code in the footer of all pages, enabling comprehensive tracking of page views, link interactions, and SEO-relevant metrics like time on page and custom events (e.g., button clicks). Built with WordPress best practices, it ensures strong performance, security, and compatibility, with full support for localization.

安装:

Upload the effortless-landing-page-tracking-for-matomo folder to the /wp-content/plugins/ directory. Activate the plugin: Single Site: Through the Plugins menu in WordPress. Multisite: Network-activate via Network Admin > Plugins. Configure settings: Single Site: Go to Settings > Matomo Tracking to enter your Matomo URL, Site ID, and optional event tracking settings. Multisite: Go to Network Admin > Matomo Network to set the network-wide Matomo URL, Site ID, and optional event tracking settings. Save your settings. The tracking code will automatically be added to all pages.

升级注意事项:

1.3.9 Removed unnecessary load_plugin_textdomain() call, as WordPress 4.6+ automatically loads translations for WordPress.org plugins. 1.3.8 Update to fix i18n issue with translators comment in event validation and correct main plugin file name. No functional changes; test translations if used. 1.3.7 Update to fix i18n issue with translators comment in event validation. No functional changes; test translations if used. 1.3.6 Update to fix i18n issues with translators comment and text domain. No functional changes; test translations if used. 1.3.5 Update to fix adding two event rows when none exist. Test "Add Another Event" button to ensure single row addition. 1.3.4 Update for instant event removal with a trash icon, replacing checkboxes, with inline JavaScript for a smoother UX. Test event table after upgrading to ensure removals work correctly. 1.3.3 Update for an improved event tracking interface with a clear list table, remove checkboxes, and contextual help tab. Test settings after upgrading to ensure event table visibility. 1.3.2 Update for a simplified event tracking interface using native WordPress metaboxes, with no external CSS or JavaScript. Test settings after upgrading to ensure compatibility. 1.3.1 Revamped event tracking UI with WordPress-style repeater fields and metabox design. Added CSS and animations for a native WordPress look and feel. Improved accessibility with ARIA labels and keyboard navigation. Organized assets in assets/js/ and assets/css/ for better structure. 1.3.0 Added support for multiple event tracking with a dynamic table and "+" button. Replaced single event fields with a JSON-based storage system. Improved event tracking UI with add/remove functionality. 1.2.6 Improved event tracking settings with clearer descriptions and an example for newsletter signups. Added stricter validation for event fields, allowing only alphanumeric characters, spaces, hyphens, and underscores. 1.2.5 Added configurable event tracking and Matomo URL validation. Fixed text domain mismatch by updating plugin slug. Rename plugin folder to effortless-landing-page-tracking-for-matomo for compatibility. Update required for enhanced functionality and error resolution. 1.2.3 Fixed PHPCS errors for heredoc and error_log(). Added donation link to settings UI. Optimized performance and WPCS compliance. Update recommended for standards adherence.

常见问题:

Do I need a Matomo instance to use this plugin?

Yes, you must have access to a self-hosted or cloud-based Matomo instance. You will need your instance URL (e.g., https://matomo.example.com) and the Site ID from your Matomo dashboard. The URL must use HTTPS and include matomo.js.

Where is the tracking code inserted?

The tracking code is added to the footer of all pages via the wp_footer hook, enabling Matomo to track visits, link interactions, and SEO metrics across your site.

Does this plugin support multisite installations?

Yes, the plugin supports WordPress multisite. Settings are configured in Network Admin > Matomo Network, applying the same Matomo URL, Site ID, and event tracking settings to all sites in the network. No settings are available in individual site dashboards.

Can I customize event tracking?

Yes, you can configure a custom event (category, action, name) in the settings page. If left blank, no event tracking is included in the Matomo code.

更新日志:

1.3.9 Removed unnecessary load_plugin_textdomain() call, as WordPress 4.6+ automatically loads translations for WordPress.org plugins. 1.3.8 Fixed i18n issue: added translators comment for placeholder in event validation message in sanitize_events(). Updated main plugin file name to effortless-landing-page-tracking-for-matomo.php. Bumped version to reflect i18n fix. 1.3.7 Fixed i18n issue: added translators comment for placeholder in event validation message in sanitize_events(). Bumped version to reflect i18n fix. 1.3.6 Fixed i18n issues: added translators comment for placeholder in event validation message and corrected text domain typo in network settings page. Bumped version to reflect i18n fixes. 1.3.5 Fixed issue where clicking "Add Another Event" added two rows when no events existed. Updated event count logic to start at 0 when no events are configured, ensuring single row addition. Show "No events configured" message when event count is 0. 1.3.4 Replaced remove checkbox with a trash icon (Dashicons) for event deletion. Added inline JavaScript for instant event row removal on click, with automatic reindexing of form fields. Ensured accessibility with ARIA attributes and keyboard support for trash icon. 1.3.3 Enhanced event tracking with a wp-list-table for clear, tabular display, including column headers and remove checkboxes. Added contextual help tab with Matomo event tracking examples. Persisted event count in options to ensure table visibility. Improved sanitization to warn about incomplete events without discarding them. 1.3.2 Simplified event tracking UI to use native WordPress metaboxes and core styles, removing external CSS and JavaScript. Added "Add Another Event" button to include additional event fields on save. Maintained secure sanitization and multisite support. 1.3.1 Revamped event tracking UI with WordPress-style repeater fields and metabox design. Added CSS and animations for a native WordPress look and feel. Improved accessibility with ARIA labels and keyboard navigation. Organized assets in assets/js/ and assets/css/ for better structure. 1.3.0 Added support for multiple event tracking with a dynamic table and "+" button. Replaced single event fields with a JSON-based storage system. Improved event tracking UI with add/remove functionality. 1.2.6 Improved event tracking settings with clearer descriptions and an example for newsletter signups. Added stricter validation for event fields, allowing only alphanumeric characters, spaces, hyphens, and underscores. 1.2.5 Fixed text domain mismatch by aligning plugin slug with effortless-landing-page-tracking-for-matomo. Added configurable event tracking settings (category, action, name) for custom Matomo events. Added Matomo URL validation to ensure HTTPS and matomo.js availability, with admin notices for invalid URLs. 1.2.4 Updated class and file names for consistency with plugin branding. 1.2.3 Fixed PHPCS errors: Removed heredoc for tracking code, removed error_log() for production readiness. Added donation link to settings pages for single site and multisite. Optimized code: Centralized settings retrieval, defined static allowed tags. Improved WPCS compliance: Consistent naming, Yoda conditions, enhanced PHPDoc, streamlined nonce handling. Removed redundant type checks for better performance. 1.2.2 Fixed output escaping to use wp_kses() with custom allowed tags, restoring Matomo tracking functionality while maintaining WPCS compliance. 1.2.1 Fixed WPCS error by escaping tracking code output with wp_kses_post(). 1.2.0 Added multisite support with settings in Network Admin only. Switched to wp_footer for tracking code insertion on all pages. Added SEO enhancements: Heartbeat timer and event tracking. Improved code quality with PHPStan compliance (CamelCase, type safety). Updated settings logic to support single-site and multisite environments. 1.1.5 Fixed warnings from PHPCS. 1.1.4 Updated the text domain to match the plugin slug. Fixed version number and headers to reflect current version. Improved sanitization and escaping for plugin settings. 1.1.3 Minor documentation updates and version bump for maintenance release. 1.1.2 Fixed text domain mismatch to align with plugin slug. Updated plugin version and documentation. 1.1.1 Fixed NonSingularStringLiteralDomain warnings by using a literal text domain string. Simplified register_setting() sanitization callbacks. Updated version and documentation. 1.1.0 Refactored plugin to use a class-based structure. Added internationalization support. Enhanced security with nonce checks and capability verification. Implemented uninstall hook to clean up options on deletion. Followed PHP and WordPress coding standards. Enhanced plugin header with additional metadata. 1.0.2 Removed visitor statistics graph and Matomo API token configuration. Improved plugin description and updated version. 1.0.1 Added nonce verification to the settings form. Simplified sanitization in register_setting(). Synced stable tag with plugin version. 1.0.0 Added license to plugin header. Implemented robust settings sanitization. Replaced CDN-based Chart.js with a local version. Applied output escaping for better security. 0.1.5 Initial release with Matomo tracking and a basic visitor statistics graph.