Security hardening of admin requests and settings validation. No settings or data change on upgrade; custom header names that are not valid HTTP are reported the next time the page is saved.<\/p>","1.0.1":"
Renames the plugin's stored settings, tables and scheduled events to the First WordPress.org release. Adds privacy-policy text and personal-data export\/erasure for form submissions, and makes the interface translatable. No settings or data change on upgrade.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.2"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The Home screen: what Convermetry is recording on this site, the setup checklist and a status overview.","2":"The Analytics dashboard: overview totals and daily page views, followed by content, engagement, acquisition, device, goal and lead reports.","3":"A submission expanded: lead status and value, form details, channel and campaign attribution, and the visitor's path to the form.","4":"The Forms screen: form engagement and abandonment, detected form plugins and per-form settings.","5":"Webhook endpoints: the message types each one receives, signing secrets and test buttons.","6":"The Activity Log: every delivery attempt with its payload and response, including retries.","7":"Goals with their completions, conversion rates and value.","8":"A funnel showing how many visits reached each step on the way to a quote request.","9":"Tracking and privacy settings: interaction types, logged-in users, Do Not Track \/ Global Privacy Control, IP storage and data retention."}},"plugin_section":[],"plugin_tags":[232,601,5446,24188,34953],"plugin_category":[36,42],"plugin_contributors":[284371],"plugin_business_model":[],"class_list":["post-376626","plugin","type-plugin","status-publish","hentry","plugin_tags-analytics","plugin_tags-forms","plugin_tags-lead-tracking","plugin_tags-utm","plugin_tags-webhooks","plugin_category-analytics","plugin_category-contact-forms","plugin_contributors-cpaschall1981","plugin_committers-cpaschall1981"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/convermetry.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n Convermetry connects the question \"where did this visitor come from?\" to the answer \"which lead did they become?\" \u2014 inside your own WordPress site.<\/p>\n\n It records how visitors use your pages, attributes each visit to a traffic channel and campaign, and captures form submissions after the form plugin has confirmed them on the server<\/strong>. Every lead is linked to the analytics session and campaign that produced it. Leads can then be forwarded to your own systems through webhooks, and you can be emailed when one arrives.<\/p>\n\n Everything is stored in your WordPress database. Convermetry works on its own: it needs no account, no API key and no external service.<\/p>\n\n Convermetry detects these automatically and records a submission when the form plugin's own server-side success hook fires. None of them is required.<\/p>\n\n Submissions made before a form is connected are not recorded and cannot be recovered. Per-form options (exclude a form, set a custom form ID, add per-form webhook headers and query parameters) are on the Forms screen.<\/p>\n\n This section describes what Convermetry does. It is not legal advice, and Convermetry does not by itself make a site compliant with any law. Review your privacy policy and your legal basis for processing.<\/p>\n\n What is collected<\/strong><\/p>\n\n Browser storage \u2014 no cookies.<\/strong> The tracker sets no cookies. It stores a random visit identifier ( Consent.<\/strong> Convermetry has no consent banner of its own and is not integrated with a consent-management plugin. Analytics starts collecting as soon as the plugin is activated. If your site needs consent before analytics runs, have your consent tool block the script handle Where it is stored and for how long.<\/strong> In seven custom tables in your WordPress database. Analytics events, submissions, goal completions, lead history and Activity Log entries are deleted automatically after the retention period (default 90 days, adjustable from 7 to 365). Deleting the plugin from the Plugins screen removes every table, option and scheduled task it created.<\/p>\n\n WordPress privacy tools.<\/strong> Convermetry adds suggested text to Settings \u2192 Privacy \u2192 Policy Guide, generated from your current settings. It also adds an exporter and an eraser to Tools \u2192 Export Personal Data and Tools \u2192 Erase Personal Data. For an email address, they find the form submissions whose submitted values contain that exact address. The eraser deletes those submissions with their lead history and queued deliveries and notifications. It removes the lead from the Activity Log's stored payloads, and removes the visitor's IP address from the analytics of that visit. Analytics recorded during visits in which no form was submitted is not linked to an email address, so it can only age out through the retention period.<\/p>\n\n Convermetry does not<\/strong> contact any server by default, and it never sends data to the plugin's author. All fonts, scripts and styles are bundled with the plugin. Information leaves your site only through features a site administrator configures:<\/p>\n\n Copies that have already been delivered to a webhook endpoint or sent by email are outside Convermetry's control. Deleting a submission, retention and the eraser cannot recall them; they are kept according to the receiving system's own policies.<\/p>\n\n Convermetry has a documented hook API (85 actions and filters), a custom form submission API, a read-only REST endpoint for the delivery log, and versioned webhook payload schemas. The full reference is in the plugin under Convermetry \u2192 About and in the README.md file included with the plugin.<\/p>\n\n\n No. Convermetry stores everything in your WordPress database and works with no account, API key or remote service. Webhooks and email notifications are optional and send data only to destinations you configure.<\/p><\/dd>\ncvmtry<\/code> prefix. Settings and data saved by 1.0.0 are not carried over.<\/p>","1.0.0":"Analytics and attribution<\/h4>\n\n
\n
Leads<\/h4>\n\n
\n
Supported form plugins<\/h4>\n\n
\n
convermetry_form_submission<\/code> action or the convermetry_submit_form()<\/code> function.<\/li>\n<\/ul>\n\nWebhooks and email notifications<\/h4>\n\n
\n
wp_mail()<\/code>. They are off by default.<\/li>\n<\/ul>\n\nPrivacy and data handling<\/h4>\n\n
\n
cvmtry_session<\/code>) and the visit's attribution (cvmtry_campaign<\/code>) in the browser's localStorage, and briefly holds unsent events (cvmtry_pending<\/code>) in sessionStorage. The visit identifier is replaced after 30 minutes of inactivity. In the EU and UK, the rules that govern cookies also apply to this kind of storage.<\/p>\n\ncvmtry-tracker<\/code> until consent is given, or return false<\/code> from the convermetry_should_enqueue_tracker<\/code> filter. Form submissions are still recorded server-side when the tracker does not run.<\/p>\n\nExternal services<\/h4>\n\n
\n
wp_mail()<\/code>, and any SMTP plugin you use) to the recipients you enter. It can include the submitted values, analytics context and, only if you enable it, the visitor journey and IP address.<\/li>\n<\/ul>\n\nFor developers<\/h4>\n\n
\n
convermetry<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Do I need an account or an external service?<\/h3><\/dt>\n