Controls for Contact Form 7 (Redirects, Analytics & Tracking) vs Profound Agent Analytics

NEW: Subscribe to the 🚀 PRO version for advanced analytics and tracking features, and professional support by the plugin author. This is an addon for the Contact Form 7 plugin with the following features: Track form submissions, errors and completions with Google Analytics (GA4), Google Tag (gtag.js), Google Tag Manager (GTM), Matomo (formerly Piwik) and Facebook Pixel. Redirect to URL on form submission. Enable native WordPress shortcodes in form content. Disable AJAX form submissions. Disable default form CSS. Disable automatic paragraph formatting. Disable HTML5 input field types or enable the HTML5 input type fallback. Specify the Google reCAPTCHA language. Store form submissions in Storage for Contact Form 7 or TablePress. Please note that some settings work on the per-page level and will apply to all forms on the same page. For example, disabling AJAX form submissions for one form will disable AJAX submissions on all forms on the same page. Requirements Contact Form 7 version 4.3 or later for features related to submission tracking and redirects. Usage The plugin adds a new “Controls” tab for each Contact Form 7 form in the WordPress administration area. Form Submission Storage Setup the official companion plugin Storage for Contact Form 7 plugin for capturing the form submissions safely in the WordPres database. Alternatively, there is also a basic integration with the TablePress plugin. Select the TablePress table where to store the form submissions. The plugin will add any missing columns for each form field, and append the form entries as rows to the table. Additionally, fields cf7_time (submission time as ISO 8601) and cf7_url (URL where the form was submitted) are stored along with the form data. Analytics Tracking The plugin automatically triggers analytics events for the following services: Google Analytics (GA4) using Google Tag Manager and Global Tag (gtag.js) with ga(), _gaq.push() and dataLayer.push() implementations, Matomo (formerly Piwik), Facebook Pixel Conversion Tracking. It passes the following data with the event: “Contact Form” as the event category, “Submit”, “Sent”, “Error” or “Spam” as the event action, and the form title as the event title. Facebook Pixel The standard Contact event is used for Facebook Pixel with content_category property set to the event type (Submit, Sent, Error, Spam) and content_name set to the form title. Contribute Report issues and suggest improvements on GitHub. Add a translation to your language.

Profound Agent Analytics is a powerful WordPress plugin that integrates with Profound’s edge log analysis service to identify, classify, and provide reporting on bot and human traffic to your website. The plugin works by efficiently collecting and sending request data from public pages to Profound’s analytics platform. Read more here Key Features Non-blocking Performance: Uses an asynchronous queue system to ensure zero impact on page load times Privacy-Focused: Query parameter redaction to protect sensitive data Smart Batching: Efficiently sends logs in batches to minimize network overhead Circuit Breaker: Automatic protection against API failures to prevent cascading issues Flexible Configuration: Extensive settings for customizing what data is collected and sent Enterprise Ready: Supports environment variables and constants for API key configuration How It Works The plugin captures essential HTTP request metadata (method, path, status, timing) Data is immediately queued in a local database table with minimal overhead A background process sends batched logs to Profound’s API endpoint Failures are automatically retried with exponential backoff Your Profound dashboard provides real-time insights into your traffic Privacy & Security Profound Agent Analytics is designed with privacy and security at its core: Complete IP Tracking: Captures full IP addresses for accurate traffic analysis and reverse DNS lookups (required for bot detection) Sensitive Data Protection: Automatically redacts passwords, tokens, and credit card information from query parameters Public Traffic Only: Excludes all WordPress admin, REST API, and system paths – only tracks public visitor traffic Encrypted Storage: API keys are encrypted using WordPress salts when Sodium extension is available No Cookie Tracking: Server-side only – does not use cookies or client-side tracking Performance Optimized Adds less than 1ms to request processing time Efficient database operations with proper indexing Automatic cleanup of old log entries Memory-aware batching to prevent large payloads Configurable queue size limits Privacy Policy This plugin sends data to Profound’s analytics service (https://artemis.api.tryprofound.com). The data sent includes: – Full IP addresses (required for bot detection and traffic analysis) – Request URLs from public pages only (admin and system paths are excluded) – HTTP headers (user agent, referer) – Response metadata (status code, size, duration) – Query parameters (with sensitive values redacted) The plugin only tracks public visitor traffic. WordPress admin activity, user actions, and system operations are not collected. All data is processed in accordance with Profound’s privacy policy available at https://tryprofound.com/privacy-policy System Requirements WordPress 6.0 or higher PHP 7.4 or higher MySQL 5.7+ or MariaDB 10.2+ Ability to make outbound HTTPS requests WP-Cron enabled (or real cron configured) Sodium PHP extension (recommended for encryption) Development & Testing This plugin includes a .wp-env.json configuration for local testing using wp-env. This requires Docker (or OrbStack) and Node.js. Running Compatibility Tests Start the environment: npx @wordpress/env start Verify the plugin activates without errors: npx @wordpress/env run cli wp plugin deactivate agent-analytics-wp-plugin npx @wordpress/env run cli wp plugin activate agent-analytics-wp-plugin Verify all classes instantiate and core functionality works: npx @wordpress/env run cli wp eval ‘new AgentAnalytics\Settings(); new AgentAnalytics\Queue(); echo “OK”;’ Check for PHP errors, warnings, or deprecation notices (WP_DEBUG is enabled): npx @wordpress/env run cli cat /var/www/html/wp-content/debug.log If the file does not exist, there are no errors. Stop the environment: npx @wordpress/env stop To test against a different WordPress version, edit the core value in .wp-env.json (e.g. "WordPress/WordPress#7.0") and restart. Deploying to WordPress.org See DEPLOY.md for instructions on publishing releases and updating the “Tested up to” value via SVN. Support For support, please contact [email protected]