Burrow for WordPress agencies

The Burrow WordPress plugin captures form submissions from Gravity Forms, Fluent Forms, Ninja Forms, and Contact Form 7, plus WooCommerce order and checkout events. Unified with GitHub, Stripe, and analytics signals for automated client reporting.

Request early access Read the docs

[ Capabilities ]

Form plugin coverage

The Burrow WordPress plugin captures form.submitted events from Gravity Forms, Fluent Forms, Ninja Forms, Contact Form 7, and WooCommerce checkout flows — so you know when lead flow stops, not just when the site goes down.

WooCommerce order and funnel events

Order placed, item added, checkout started, payment completed — WooCommerce signals flow into the same client timeline as GitHub deploys and Stripe invoices. No CSV exports, no manual assembly.

History backfill on install

When you install the Burrow plugin, it doesn't start from zero. Historical form and commerce events are backfilled so your client timeline shows past activity immediately — not just new events going forward.

Example

TypeScript SDK — stream a WordPress form event

import { Burrow } from "@useburrow/sdk";

const burrow = new Burrow({ apiKey: process.env.BURROW_API_KEY });

await burrow.events.create({
  source: "wordpress",
  type: "form.submitted",
  projectId: "client_acme",
  payload: {
    formPlugin: "gravityforms",
    formId: "contact-main",
    pageUrl: "https://acme.com/contact",
    submittedAt: "2026-04-03T14:22:00Z",
  },
});

WordPress is the biggest piece of most agency portfolios. But it’s rarely the only piece.

If you run a web agency, WordPress probably generates 50-70% of your retainer revenue. You know the drill: update plugins, manage hosting, build pages, troubleshoot forms, monitor uptime. Tools like ManageWP ($1.25-$2.75/site add-ons), MainWP ($149/yr for unlimited sites), and WP Umbrella (EUR 1.99/site) handle the WordPress maintenance layer well.

The problem is everything WordPress maintenance tools can’t see.

Client A has a WordPress blog, a Shopify store, and Stripe handling subscriptions. Client B runs WordPress with WooCommerce, a custom Laravel API, and deploys through GitHub Actions. Client C has WordPress for marketing, Craft CMS for editorial, and an ExpressionEngine site for their membership portal.

ManageWP says “all plugins updated, backups complete, uptime 99.9%.” That’s the WordPress slice. But the Shopify checkout threw errors yesterday. The Stripe renewals failed. The Gravity Forms handler broke after a plugin conflict and zero leads have come through since Friday.

Burrow’s WordPress plugin is the bridge between WordPress-specific maintenance and full-stack operational visibility. It captures the signals WordPress maintenance tools don’t — form submission health, WooCommerce funnel events, content publishing activity — and places them in a timeline alongside GitHub deploys, Stripe billing, analytics, and monitoring from every other tool in the client’s stack.

What the Burrow WordPress plugin actually captures

This isn’t a generic “events flow in.” Here’s what the plugin streams to your Burrow project:

Form submissions from Gravity Forms, Fluent Forms, Ninja Forms, and Contact Form 7 — including form ID, page URL, and submission timestamp. When form volume drops to zero, Burrow can flag the anomaly before your client forwards angry email about missing leads.

WooCommerce events — order placed, item added to cart, checkout started, payment completed, refund processed. Commerce signals sit in the same timeline as engineering deploys and marketing analytics so your monthly review covers revenue impact alongside delivery work.

Plugin and system events — update applied, plugin activated/deactivated, system heartbeats. When a Friday plugin update triggers a form handler failure, Burrow’s timeline shows the correlation: plugin update at 3:47pm, form volume drops to zero at 3:48pm.

History backfill — the plugin doesn’t start from zero. On installation, it scans existing form submissions and WooCommerce orders and populates your Burrow timeline retroactively. You get context immediately instead of waiting weeks for data to accumulate.

The scenario that keeps happening

Tuesday 3pm. Your biggest client’s VP of Sales emails: “We haven’t gotten a lead from the website in 4 days.” You check ManageWP — everything looks green. Plugins updated. Backup ran last night. Site loads fine.

You ask your developer to investigate. They SSH into the server, check the logs, and find a PHP fatal error in the Gravity Forms plugin since a CF7 update on Friday. The form silently fails — the page displays “Thank you” but no email is sent and no CRM entry is created. Four days of lost leads. The client questions the retainer.

With Burrow: the plugin detected form.submitted volume dropped to zero Friday at 4:12pm — 25 minutes after a plugin update event. Scout flagged the anomaly. Your developer got a notification before the weekend. The fix went out Saturday morning. The client never knew anything was wrong.

That’s the difference between “site is up” and “site is working.”

How it fits with WordPress management tools

Burrow is not a replacement for ManageWP, MainWP, or WP Umbrella. Those tools handle WordPress maintenance mechanics — plugin updates, backups, security scanning. Burrow handles the operations layer above:

ManageWP/MainWP/WP Umbrella answers “are the WordPress sites maintained?”
Burrow answers “what happened across this client’s entire stack — including WordPress — this month?”

Run both. Use the maintenance tool for updates and backups. Use Burrow for the unified timeline, form monitoring, cross-stack reporting, and client portals that maintenance tools don’t provide.

Compare Burrow vs ManageWP | Compare Burrow vs MainWP | Compare Burrow vs WP Umbrella

Frequently asked questions

Which WordPress form plugins does Burrow support?

The Burrow WordPress plugin captures form.submitted events from Gravity Forms, Fluent Forms, Ninja Forms, and Contact Form 7. WooCommerce checkout events are also captured. Additional form plugins can be supported through WordPress hooks and the Burrow PHP SDK.

Does Burrow replace ManageWP or MainWP?

No. ManageWP and MainWP handle WordPress maintenance mechanics — plugin updates, backups, security scans. Burrow is an operations layer that captures form submissions, WooCommerce events, and CMS activity, then correlates them with GitHub deploys, Stripe billing, and analytics signals for unified client reporting.

What about WordPress multisite?

The Burrow plugin installs on individual WordPress sites. For multisite networks, install on the sites you want to monitor. Events are scoped to Burrow projects, so you can map network sites to client projects as needed.

Does the plugin slow down the WordPress site?

The Burrow plugin uses a durable outbox pattern — events are queued locally and delivered asynchronously via background processing. No blocking HTTP calls during page loads or form submissions.

Can I capture custom events from WordPress hooks?

Yes. Use the Burrow PHP SDK to emit custom events from any WordPress hook — post_save, user_register, custom plugin actions. The SDK handles authentication, retry logic, and backfill processing.

How does history backfill work?

On installation, the Burrow plugin scans existing form submissions and WooCommerce orders (within configurable time windows) and backfills them into your Burrow timeline. You see context immediately instead of waiting weeks for data to accumulate.

Your agency's work deserves to be seen.

We're onboarding agencies in small cohorts to keep the quality high. Request early access and we'll be in touch.

Request early access Read the docs

Self-funded · Independent · Built for the long term