ViewMend Site Tracker

ViewMend Site Tracker connects confirmed WordPress changes to the ViewMend website change monitoring workflow. It records events locally and delivers compact metadata through a durable background queue, so normal WordPress requests do not wait for the external service.

ViewMend handles the resource-intensive work on its own infrastructure: running audits, capturing screenshots, comparing pages, and storing monitoring reports and evidence. The WordPress plugin sends compact change events and brings site health, performance statistics, and findings into your admin dashboard. This keeps heavy audit processing and report storage off your WordPress hosting.

Use this WordPress connector to add publication, plugin, theme, WordPress core, and WP Rocket cache context to tracked website changes. When WordPress can identify the affected public page, the event includes its exact URL. ViewMend may match already tracked pages and queue a check when auto-check, page scope, credits, and queue state allow.

Timeline events and completed ViewMend checks help administrators investigate what happened around a release or content update. This plugin is an event connector, not a standalone crawler, rank tracker, backup tool, or replacement for ViewMend’s page comparison and website change monitoring service.

Supported WordPress changes

• Public posts, pages, and products when they are published, meaningfully updated, or permanently deleted.
• Plugin installation, activation, deactivation, update, and deletion.
• Theme installation, activation, update, and deletion.
• Completed WordPress core updates.
• Confirmed full-domain and exact-URL WP Rocket cache purges.
• An explicit administrator connection test.

Autosaves, revisions, drafts, trash moves, comments, users, orders, customer records, media churn, and arbitrary option changes do not create events.

How WordPress website change monitoring works

1. WordPress confirms an enabled content, plugin, theme, core, or supported cache action.
2. The plugin creates one stable event ID and stores the compact event in its local queue.
3. A background worker delivers the event to ViewMend without delaying the originating WordPress request.
4. ViewMend records the Timeline context and returns delivery, matched-page, and queue status.
5. When the ViewMend integration permits it, selected tracked pages can be checked and the completed evidence reviewed in ViewMend.

For the wider release-verification workflow, see post-deployment website monitoring.

Native WordPress controls and durable delivery

The settings area separates Overview, Connection, Event rules, and Activity. Overview reads project health, findings, significant content changes, resource impact, and selected-page performance from ViewMend. It does not invent sample values when no completed check is available. Selecting a resource type loads the exact stored request URLs for that check without exposing the API token to browser JavaScript.

Each event category explains what is reported, what is excluded, what happens when it is disabled, and which exact actions can be selected. For example, plugin events can be limited to completed updates only.

ViewMend owns server-side event deduplication, tracked-page selection, queue ordering, credit checks, Tracker checks, Timeline markers, and before/after comparisons. This plugin does not reproduce those services inside WordPress.

The API token is stored separately with autoload disabled and is never displayed after saving. The plugin does not send post bodies, customer/order data, usernames, emails, cookies, IP addresses, or arbitrary settings.

ViewMend Site Tracker is a service connector. A ViewMend account and an existing Site Tracker integration are required before events can be delivered. See the External service section for exactly when the plugin contacts ViewMend and which data is sent.

External service

This plugin connects to ViewMend Site Tracker to deliver site-change events to the integration selected by the administrator and to read Tracker results for the administrator-only Overview. It does not contact ViewMend until an administrator explicitly configures an Integration ID and API token. After configuration, a request is made when the administrator opens or refreshes Overview, selects a stored resource type, queues a connection test, or when an enabled, supported WordPress action creates an event and the background queue processes it.

Requests contain a stable event ID, event type and time, a short change title and description, the configured public site URL and environment, exact affected public page URLs when WordPress can determine them, and minimal operational metadata such as WordPress/plugin/theme versions, public content type and numeric object ID, or the confirmed operation name. A WordPress administrative edit URL can be included as a reference for a public content event. The API token is sent only in the Authorization header. The plugin does not send post bodies, excerpts, usernames, email addresses, customer or order data, cookies, IP addresses, or arbitrary settings.

ViewMend receives and processes this information to record the event, match already tracked pages, conditionally queue Tracker checks, and return delivery and queue status. For Overview, ViewMend returns project health counts, findings, significant content changes, selected-page performance, resource URLs, MIME types, response status, transferred bytes, and request duration already collected by ViewMend checks. It does not return request or response headers, cookies, authorization values, or remote IP addresses to the plugin. Successful dashboard responses are cached in WordPress for up to five minutes. An accepted event does not guarantee that a check starts or completes. Use of the service is subject to the ViewMend Terms of Service and ViewMend Privacy Policy.

Privacy

The plugin sends public site and affected-page URLs, event timestamps/types/titles, field categories, and minimal WordPress/plugin/theme version or object identifiers. It excludes post bodies, excerpts, protected content, user/customer/order records, emails, cookies, IP addresses, and arbitrary option values.

The local queue stores the event payload, delivery state, attempts, selected redacted errors, HTTP status, and ViewMend response identifiers/state. Completed and failed history is bounded. A successful administrator dashboard response is stored as a WordPress transient for up to five minutes. The API token is stored in a separate non-autoloaded option and never stored in queue rows or sent to browser JavaScript.