Convermetry

Сүрөттөө

Convermetry connects the question “where did this visitor come from?” to the answer “which lead did they become?” — inside your own WordPress site.

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. 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.

Everything is stored in your WordPress database. Convermetry works on its own: it needs no account, no API key and no external service.

Analytics and attribution

• Page views, clicks, form views, starts, validation errors and submit attempts, confirmed conversions, scroll depth, hover and custom events. Each type can be switched off.
• UTM campaign parameters, ad-click identifiers (only which parameter was present, never its value) and entrance referrers classified into channels such as Paid Search, Organic Social or Email.
• An analytics dashboard with top pages, landing pages, referrers, campaigns, channels, devices, conversions and lead outcomes.
• Goals for actions that are not form submissions (phone and email link clicks, downloads, reaching a page, custom events) and funnels that measure the ordered path to a conversion.
• Form engagement and abandonment reporting that never records what a visitor typed into a form they did not submit.

Leads

• A Submissions screen with each lead’s answers, the page it came from, its campaign attribution and its webhook delivery status.
• Lead status (new, qualified, won, lost…) and value, with history, and lead reports by channel, campaign, landing page and form.
• CSV export, per-submission delete, and a retention window after which data is deleted automatically.

Supported form plugins

Convermetry detects these automatically and records a submission when the form plugin’s own server-side success hook fires. None of them is required.

• Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms and Formidable Forms — captured automatically, with no per-form setup.
• Elementor Pro (classic Form widget) — captured automatically.
• Elementor Pro Atomic forms — opt in per form: in the Elementor editor, add Convermetry under Actions after submit on the form and update the page.
• Bricks Builder (native Form element), Bricks 1.12.2 or newer — opt in per form: in Bricks, tick Convermetry under Actions after successful form submit and save. Older Bricks versions are shown as unavailable.
• Any other form — send it through the documented convermetry_form_submission action or the convermetry_submit_form() function.

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.

Webhooks and email notifications

• Send form submissions (one message per confirmed lead, delivered in the background) and/or scheduled analytics reports (hourly, twice daily, daily or weekly) to any number of HTTPS endpoints you configure.
• Optional HMAC-SHA256 signatures, stable delivery IDs for idempotency, automatic retries and an Activity Log of every attempt with its (redacted) payload and response.
• Optional internal email notifications to addresses you choose, sent through wp_mail(). They are off by default.

Privacy and data handling

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.

What is collected

• For each tracked interaction: the event type, the page address without its query string, page title, clicked element text and link target, referrer (without query string), campaign parameters, a traffic channel, a device type (desktop, tablet or mobile), a random visit identifier and a timestamp.
• IP addresses are stored by default with analytics events and form submissions. You can turn this off under Convermetry → Settings (“Store visitor IP addresses”). User agents are never stored.
• For each confirmed form submission: the values the visitor submitted, the page and its query parameters, and the analytics context of the visit (channel, campaign, landing page, pages viewed). Fields that look like passwords or other credentials are withheld from email notifications and redacted in the Activity Log.
• Logged-in users are excluded from tracking by default.
• Do Not Track / Global Privacy Control are not honored by default. When you enable that setting, visitors who send either signal are not tracked, and no IP address is stored with a form they submit.

Browser storage — no cookies. The tracker sets no cookies. It stores a random visit identifier (cvmtry_session) and the visit’s attribution (cvmtry_campaign) in the browser’s localStorage, and briefly holds unsent events (cvmtry_pending) 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.

Consent. 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 cvmtry-tracker until consent is given, or return false from the convermetry_should_enqueue_tracker filter. Form submissions are still recorded server-side when the tracker does not run.

Where it is stored and for how long. 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.

WordPress privacy tools. Convermetry adds suggested text to Settings → Privacy → Policy Guide, generated from your current settings. It also adds an exporter and an eraser to Tools → Export Personal Data and Tools → 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.

External services

Convermetry does not 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:

• Webhook endpoints. When you add an endpoint under Convermetry → Webhooks, Convermetry sends it HTTPS POST requests to the URL you entered. Form submission messages contain the submitted form values, the submitter’s IP address (when IP storage is on), the page and its query parameters, and the visit’s analytics context. Analytics report messages contain aggregated statistics plus a list of individual conversions, each with its IP address (when stored) and visit identifier. You choose which endpoints receive which message type. The receiving service is chosen by you, so its terms of use and privacy policy are the ones you agreed to with that service.
• Email notifications. When enabled, a notification for each new submission is sent through your site’s own mail system (wp_mail(), 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.

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.

For developers

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 → About and in the README.md file included with the plugin.