Website form reporting and submission analytics for agencies

Tuesday 3pm. The email that every agency dreads.

Your biggest client’s VP of Sales writes: “We haven’t gotten a lead from the website in 4 days. Is something wrong?”

You check the site. It loads fine. 200 OK. The contact form page renders perfectly. You fill out the form yourself — it says “Thank you for your submission.”

But no email arrives. No CRM entry is created. No Slack notification fires. The form has been silently failing since Friday’s plugin update — displaying a success message to visitors while failing to deliver the actual submission.

Four days. Maybe 20-30 lost leads. The client is furious. Your developer finds the root cause in 15 minutes: a Contact Form 7 compatibility issue introduced by a plugin update on Friday at 4:12pm. The fix takes 5 minutes. But the damage — lost leads, lost trust, a retainer that’s suddenly under review — took four days to accumulate because nobody was watching the forms.

This scenario isn’t hypothetical. It’s the number one operational failure I’ve seen across 20 years of agency work, and it’s the primary reason I built Burrow.

Two problems, one channel

Form reporting for agencies has two sides — and most tools address neither of them.

Problem 1: Silent failures. Forms break without triggering uptime alerts. The page loads, the form renders, the “Thank you” message displays — but submissions never arrive. Nobody knows until the client notices missing leads.

Problem 2: No insight into what people submit. Every form plugin tells you how many people submitted. None of them tell you what they asked for — across all your client sites, in one view.

Burrow’s Forms channel solves both. Silent failure detection catches broken forms the same day. Subfield reporting shows you what’s inside each submission.

Subfield reporting: the feature no other tool has

A contact form isn’t just a lead counter. It carries operational data in its fields — Subject dropdowns, service-type selectors, budget ranges, “How did you hear about us?” fields. That data tells you what visitors are asking for, which services are in demand, and how the client should allocate resources.

Example: The law firm contact form. A personal injury law firm has a “Case Type” dropdown on their contact form — “Auto Accident,” “Slip & Fall,” “Medical Malpractice,” “Workers’ Comp,” “Other.” Their Gravity Forms entries page shows 89 submissions this month. Useful number. Useless insight.

Burrow’s subfield breakdown shows:

• Auto Accident — 38 submissions (43%)
• Workers’ Comp — 24 submissions (27%)
• Slip & Fall — 14 submissions (16%)
• Medical Malpractice — 8 submissions (9%)
• Other — 5 submissions (6%)

Now the client’s intake team knows where to staff. The managing partner sees workers’ comp inquiries trending up 40% from last quarter. The marketing director shifts ad spend toward the categories driving volume. One form field, properly reported, changes three business decisions.

Example: The home services quote form. A roofing company’s form has a “Service Needed” field — “New Roof,” “Repair,” “Inspection,” “Gutter Work.” Monthly reporting shows 68% of requests are repairs, not new installations. The owner adjusts crew scheduling, updates pricing for repair work, and creates a dedicated repair landing page that converts better because it speaks directly to the majority use case.

Example: The SaaS demo request. A software company’s demo form includes a “Company Size” dropdown. Subfield reporting reveals 41% of demo requests come from companies with 200+ employees — the enterprise segment they thought was a small slice of pipeline. Sales leadership reassigns an AE to enterprise accounts. The VP of Marketing launches an enterprise-specific campaign.

What fields work with subfield reporting?

Any structured form field with discrete, selectable values:

• Dropdowns — Subject categories, case types, service types, department routing, location selectors
• Radio buttons — Budget ranges, timeline preferences, company size, yes/no qualifiers
• Checkboxes — Service interests, feature needs, multi-select preferences
• Hidden fields — UTM source, landing page URL, referral tracking codes

The Burrow WordPress plugin captures subfield values automatically from Gravity Forms, Fluent Forms, Ninja Forms, and Contact Form 7. You configure which fields to include per form — keeping operational metadata while excluding PII per your client agreements.

Why uptime monitoring doesn’t catch broken forms

Oh Dear, UptimeRobot, Pingdom, ManageWP’s uptime add-on — they all do the same thing: ping the URL and check if it returns HTTP 200. If the page loads, the site is “up.”

But “the site is up” and “the site is working” are different statements. A site can be up while:

• The form handler throws a PHP fatal error but the template catches it and shows a “thank you” message anyway
• The SMTP server is blacklisted and no emails are being delivered
• A Zapier webhook URL expired and form-to-CRM integration silently stopped
• A DNS change broke the form’s submission endpoint but not the page itself
• A plugin update conflicted with the form plugin and submissions are lost on the backend

None of these trigger an uptime alert. The page loads. The HTTP response is 200. The monitoring dashboard shows green. And leads are disappearing.

What Burrow does differently

Burrow doesn’t ping the page. It captures form.submitted events from inside the form plugin — Gravity Forms, Fluent Forms, Ninja Forms, CF7, WooCommerce checkout. When a user successfully submits a form and the plugin processes it, Burrow sees the event with its subfield data. When the form plugin stops emitting events, Burrow sees the absence.

The difference is between monitoring the front door (uptime: is the page reachable?) and monitoring the cash register (form health: are submissions actually completing — and what are people asking for?).

Before Burrow

Friday 4:12pm — Plugin update happens. Form handler breaks. ManageWP says “all green” because the site loads fine.

Saturday through Monday — Visitors fill out the form, see “Thank you,” and leave. No leads arrive. Nobody knows.

Tuesday 3pm — Client emails. Four days of lost leads.

After Burrow

Friday 4:12pm — Plugin update event appears in the client’s Burrow timeline. Form.submitted event volume drops to zero at 4:13pm. Scout flags the anomaly within the hour.

Friday 5:30pm — Developer sees the alert, identifies the CF7 conflict, and deploys a fix. Total lead loss: approximately 2 hours’ worth, not 4 days’.

Monday morning — Client call goes normally. The monthly digest shows: “Form issue detected Friday 4:12pm, resolved Friday 5:30pm. 187 form submissions for the month — 58 sales inquiries, 87 general, 29 support, 13 partnership. Uptime 99.97%.” The retainer is safe.

Every agency tool ignores this problem

AgencyAnalytics reports traffic. ManageWP reports plugin health. MainWP reports update status. WP Umbrella reports backups and uptime. None of them monitor whether form submissions are actually completing — and none of them report on what visitors are selecting in form fields.

It’s arguably the highest-ROI operational signal an agency can track — because forms are how clients turn website traffic into revenue. A contact form that works is worth more than a perfect Lighthouse score, a current plugin inventory, and a 99.99% uptime report combined. And a contact form with subfield reporting turns a lead counter into a business intelligence tool.

Burrow makes form health and form analytics a first-class operational signal. Not a footnote. Not a “future roadmap item.”

WordPress integration (form plugin details) | Forms channel | Oh Dear integration (uptime context) | Site monitoring | Client portals | Compare with ManageWP