How MetricPoints works

Know first. Know why. Keep the client’s trust.

A client site can look fine while leads disappear, checkout stalls, or visitors hit broken pages. MetricPoints watches from the outside first, adds deeper evidence when you connect a site, and turns confirmed problems into clear incidents your team can act on before the client has to explain the problem to you.

Put your sites under watch Explore the two levels ↓

One site. Several sources. One response.

01 / External

Watch the public site without installing anything.

02 / Connected

Add WordPress application evidence or browser beacon reporting.

Then / Act

Review the incident, route the alert, and show the proof.

Two levels of coverage

Start outside. Go deeper where it matters.

Every client site can begin with external monitoring. Connected sources add evidence that outside checks cannot see. WordPress and non-WordPress sites both belong in the same agency portfolio.

External monitoring

Get useful coverage today, with no code on the site.

MetricPoints checks the public website and its supporting infrastructure: availability, important pages, TLS, domains, DNS, redirects, security headers, indexability, public assets, visual changes, and configured forms or journeys.

Public behavior: detect problems a visitor could meet even when the homepage still responds.
Business paths: configure checks for forms, lead delivery, search, booking, or other important journeys.
No WordPress dependency: use it on WordPress, custom sites, and other platforms.

Connected evidence

See beyond what an outside check can prove.

Choose the source that fits the site. The WordPress plugin adds application-side evidence. The lightweight browser beacon adds real visitor and browser evidence, including on non-WordPress sites. They can work together on a WordPress site.

WordPress plugin: WooCommerce health, form and mail signals, cron, updates, user changes, cache issues, and approved cache clears or other bounded actions.
Browser beacon: JavaScript errors, failed requests, performance, and session context from visitors’ browsers.
Same incident view: related observations can support one explanation instead of creating separate piles of alerts.

A second set of eyes

More than one monitoring vantage point.

MetricPoints has a primary monitoring system in Virginia and a separate New York runner on another provider. For eligible checks, the second location can help verify a suspicious failure and reveal when a problem is regional rather than global.

Coverage depends on the check and the site’s monitoring configuration; every check is not run from both locations.

Primary system

Virginia

Scheduled checks and the agency’s main monitoring view.

Independent provider

New York

A remote vantage point for configured checks and failure verification.

From signal to response

An alert your team can actually use.

MetricPoints turns checks and connected evidence into current site health, incidents, history, and client-ready proof. A brief recovered blip stays in history; it does not become a permanent crisis.

Notice

External checks, remote results, the beacon, and the WordPress plugin contribute observations with their sources and times.

Understand

Related signals can be grouped into one incident with business impact, likely context, and technical evidence underneath.

Respond

Route confirmed incidents and recoveries to the right people by email, webhook or Slack, and SMS where configured; keep a record of what happened.

Choose who handles the response

Run it with your team, or let MSWD handle the watch and investigation.

Use MetricPoints directly to triage your client portfolio. If your agency wants a technical partner behind the scenes, Main Street Web Developer offers managed monitoring, alert review, business-hours investigation, and a scoped path to fixing what breaks. After-hours response and repair work depend on your agreement.