A WordPress team can know how many Contact Form 7 submissions were recorded and still have unanswered questions. Which campaign brought the visitor? Where did people abandon a long form? Did the inquiry reach a person who could respond? These questions require different data, so choosing an analytics tool starts with the decision you need to make.
CF7 Analytics, Google Analytics 4, Matomo, Plausible and Fathom can contribute to form measurement from different directions. This comparison separates local submission reporting, site-wide event measurement and deeper form analysis. It is based on current product documentation and the inspected free CF7 Analytics tracker, not a five-tool performance benchmark.
CF7 Analytics is our product. We include it where local Contact Form 7 reporting is the relevant task and explain where another measurement layer is more suitable.
What are you trying to measure?
A submission report counts a defined form outcome. A web analytics report adds the surrounding website journey. A form-analysis system may examine interactions within the form itself. A CRM connects the inquiry to follow-up and qualification. These layers can work together, but none should be treated as proof that every stage of the customer journey succeeded.
Write one acceptance question before comparing dashboards. For example: “Can our account manager compare recorded submissions by form each month?” is narrower than “Can marketing compare completion by acquisition source?” Another question, “Which field makes a long application difficult?”, requires evidence that a simple count cannot provide.
The quick difference
| Tool | Best fit | Main strength | Main consideration |
|---|---|---|---|
| CF7 Analytics | Reporting inside WordPress | Focused Contact Form 7 submission statistics | Submission counts are not delivered mail or a visitor funnel |
| Google Analytics 4 | Form events within broader website measurement | Event-based measurement beyond one plugin | Automatic form events need validation against the intended outcome |
| Matomo | Teams investigating form behavior | Dedicated Form Analytics capability | Confirm the deployment, entitlement and tracking setup |
| Plausible | Website goals with a compact reporting workflow | Custom events and goal configuration | Event definitions and counting still need ownership |
| Fathom | Clearly named website conversion events | Direct event tracking | The chosen conversion formula changes the interpretation |
CF7 Analytics
CF7 Analytics is the focused option when the team wants Contact Form 7 reporting within WordPress. The free WordPress.org plugin is listed as Svetlik Analytics for Contact Form 7. It provides submission trends and statistics, while the Pro product page describes additional form insights, visual charts and CSV export.
Its scope is the important tradeoff. In free version 1.0.3, the inspected server-side tracker records mail_sent and mail_failed outcomes after validation. It does not turn the count into proof of inbox delivery. Do not assume that the reporting layer also supplies form-start counts, a visitor denominator, a complete attribution journey or a lead database.
Best fit: a freelancer or agency that wants a straightforward form-activity report in the site’s administration area. Main consideration: use another suitable data source when the question goes beyond recorded submissions. Start with our measurement guide before labeling a chart “conversions.”
Google Analytics 4
Google Analytics 4 is relevant when form measurement belongs inside a broader website reporting program. Google’s enhanced-measurement documentation defines form_start and form_submit events and associated form parameters. Those automatic events are useful starting points, but their documented definitions should not be silently replaced with “qualified lead” or “email delivered.”
For a Contact Form 7 implementation, evaluate what actually happens during valid input, invalid input and a mail failure. A custom event tied to the relevant CF7 outcome may be appropriate when you need a more specific signal. Keep form identifiers separate from names, email addresses and message text; Google prohibits collecting personally identifiable information in this measurement.
Best fit: teams already using a wider Google Analytics measurement plan. Main consideration: someone must own event naming, duplicate prevention and validation. An event being visible in a dashboard proves it was recorded under that setup, not that the business received a useful inquiry.
Matomo
Matomo’s dedicated Form Analytics offering is the candidate to investigate when you need evidence about the form itself. Its product documentation describes form discovery and reporting, and explicitly says the feature does not store what users type into form fields. This positions it differently from a submission-count plugin or an operational message archive.
Evaluate the actual forms you intend to analyze, including conditional fields, multiple steps and dynamically displayed content. Ask which interactions are captured in the proposed setup and how the resulting report distinguishes a form being seen, used and completed. A feature list cannot establish compatibility with every custom WordPress configuration.
Best fit: teams with a concrete form-behavior investigation and capacity to maintain the measurement. Main consideration: check the Form Analytics entitlement and deployment requirements separately from the core analytics installation. Do not assume every Matomo package includes the same form-analysis capability.
Plausible
Plausible provides custom events and configured goals, with WordPress integration documented separately. A named custom event must have a matching goal configuration to appear as a conversion in the relevant dashboard. Its documentation also describes automatic form tracking and properties for more specific event reporting.
For a small team, the practical appeal is a short list of clearly defined outcomes. A quote form and a newsletter signup can have distinct event names, with the reporting plan explaining when each occurs. Avoid counting the same interaction through both an automatic mechanism and an extra custom listener unless your design deliberately separates them.
Best fit: teams looking for a compact website-goal workflow around their forms. Main consideration: verify how the selected WordPress integration interprets Contact Form 7 responses. Plausible documents that custom events contribute to billable monthly pageviews, so estimate event volume as well as page traffic when reviewing the plan.
Fathom
Fathom exposes named events through fathom.trackEvent(). Its form documentation shows generic submission-event examples, and its current event overview explains how the conversion formula can use pageviews or site visitors as the denominator. That denominator choice changes the meaning of a reported rate.
When adapting generic form instructions to Contact Form 7, define whether you want an attempted submission or a specific completed outcome. A native submit listener is not automatically the same as CF7’s successful-mail event. Name the event after the action you have actually instrumented and test it before using the rate in a client report.
Best fit: a team that wants a small number of explicit website conversion events. Main consideration: record the formula and event implementation together. Comparing a visitor-based rate in one product with a pageview-based rate in another can create an apparent disagreement that is only a definition mismatch.
How to choose without collecting five conflicting totals
Choose the question first. Use a local report for recorded form activity, a site-wide analytics setup for the surrounding website context, and a dedicated behavioral capability when you need evidence inside a form. Buying a broader tool before identifying the question usually creates more configuration work than useful information.
Specify the outcome and denominator. Write down whether you count attempts, validated submissions, mail-sending success or qualified inquiries. Then define whether a rate uses attempts, visits, sessions or unique people. Keep these definitions visible in the reporting document so future administrators do not accidentally change the meaning.
Compare a controlled sample. In staging, use a successful submission, an invalid field, a repeat submission and any safely simulated failure relevant to the implementation. Trace the expected event in each measurement system. Never force totals to match by removing inconvenient records without understanding why they differ.
Include maintenance in the cost. Count plugin or service fees, the required product edition, event volume, implementation effort and recurring review time. A dashboard that takes little time to open can still require significant work to keep its event definitions correct after form or theme changes.
Choose the layer your team will use
Start with CF7 Analytics for local submission reporting, Google Analytics 4 for a broader event-measurement program, Matomo when investigating dedicated form analytics, Plausible for configured website goals, or Fathom for explicit named events. These are fit-based starting points, not an overall ranking. Add a second layer only when it answers a question the first one cannot.
If the actual problem is assigning and following up inquiries, move beyond dashboards to an operational workflow such as Notion or Airtable. A well-defined handoff often matters more than another conversion chart.