Contact Form 7 analytics should help you answer a practical question: are the right people reaching your team, and where does the process stop working? A rising submission total can be encouraging, but it does not tell you whether a message reached the inbox, whether the inquiry was relevant, or whether the person became a customer.
Start with a small measurement plan. Define what you count, identify the form and date range, and connect the report to an action someone can take. This guide explains how to build that plan around Contact Form 7 and the CF7 Analytics plugin without confusing form activity with business results.
Define a submission before building a report
A form interaction can mean several things: someone viewed the page, started typing, attempted to submit, passed validation, or reached a successful mail response. These are separate events. They should not share an ambiguous label such as “leads” unless your team has deliberately defined that label.
The installed free Svetlik Analytics for Contact Form 7 version 1.0.3 counts submissions with either mail_sent or mail_failed status. Its tracker is designed to be independent of whether mail sending succeeds. Invalid and spam responses are excluded by that status check. This means its submission total is not a delivered-email total. We verified this behavior in that version’s tracker code; check your installed version when investigating differences.
Contact Form 7 also exposes browser events for different outcomes. Its wpcf7mailsent event is a successful mail-sending signal, while wpcf7submit covers the completed submission process more broadly. These events operate during AJAX submission. Neither a button click nor a browser event proves a recipient actually received an email in their inbox. See the official event definitions before configuring external tracking.
Choose a small set of useful metrics
| Metric | Question it answers | What else you need |
|---|---|---|
| Recorded submissions | How much activity reached this form’s tracked outcome? | A documented event definition and form ID |
| Mail failures | Where did the mail-sending stage fail? | A separate outcome signal or appropriate mail log |
| Completion rate | What share of measured attempts or visitors completed? | A compatible denominator and deduplication rule |
| Qualified inquiries | How many submissions were useful to the business? | Human review or a defined CRM qualification stage |
| Follow-up time | How long did people wait for a response? | Submission and first-response timestamps |
You do not need all five on day one. A freelancer might start with weekly submissions by form and a simple review of useful inquiries. An agency may need a separate operational report for every client. A sales team may care most about the delay between form completion and the first meaningful reply.
Set up the WordPress reporting baseline
- Confirm Contact Form 7 is active and identify the form you want to measure. Give similar forms descriptive names, such as “Service quote” and “General contact.”
- Install and activate Svetlik Analytics for Contact Form 7, the free plugin associated with this site. Its documented administration location is Contact → Analytics.
- Record the activation date and installed version. Do not assume activity from before tracking began will appear retroactively.
- Choose a reporting period and timezone. Compare full weeks or equal date ranges, and record the number of active days if tracking started partway through a period.
- Check the result with clearly labeled test data in a staging environment. Keep tests out of business reporting, and do not send test mail to real prospects.
The free plugin provides submission trends and statistics. The Pro product page describes additional form insights, visual reporting and CSV export. Match the edition to the reporting task; installing an analytics plugin does not automatically create a CRM, an email-delivery audit or a visitor-level funnel.
Calculate rates using compatible numbers
Suppose, in an illustrative week, a form had 40 recorded submissions and the relevant page had 1,000 measured visits. Dividing 40 by 1,000 gives 4%. That is a submission-to-visit ratio under those definitions. It is not automatically the percentage of unique people who completed the form: one person could visit twice or submit more than once.
For a visitor-based completion rate, count unique eligible visitors and unique visitors who reached the chosen outcome, using compatible identity rules and the same reporting window. For an attempt-based rate, use attempts as the denominator. If you only collect submissions, publish a submission count; do not manufacture the missing denominator.
A form shown on several pages needs another decision. You can report its combined activity, or break it out by page when your data supports that distinction. Avoid comparing a combined submission count against traffic for only one page. Document whether internal visits, tests and repeat submissions are included.
Read changes in context
Imagine submissions rise from 12 to 18 after a form redesign. That is six more submissions, but it could reflect a busier week, a new campaign or a different audience. Check the traffic and inquiry quality before attributing the entire change to the design. With small totals, one or two submissions can produce dramatic percentages.
Keep a short change log: date, affected form, what changed, why it changed, and when you will review it. Make one focused improvement where practical. For example, clarify a confusing field label, explain the expected response time or remove a question your team does not use. Review enough subsequent activity to judge the result responsibly.
Connect the report to the lead workflow
Analytics is most useful when somebody owns the next action. If the report shows activity but the team cannot find the inquiries, inspect mail handling and storage. Contact Form 7 does not itself retain submitted messages; its author recommends Flamingo for message storage. An analytics count is not a substitute for that record.
For a shared operations queue, see our guides to Contact Form 7 and Notion and Contact Form 7 and Airtable. Keep individual contact details in the operational system that needs them, while using aggregate metrics for the routine performance report.
End each review with a concrete decision: investigate a failed handoff, improve a form, adjust traffic targeting or leave a working setup stable. If you need campaign attribution or a deeper funnel, our analytics tools comparison explains which additional measurement layer to consider.