ViewMend Site Tracker connects WordPress to ViewMend website change monitoring. It records content updates, plugin and theme changes, core updates, and supported cache purges, then sends them to ViewMend in the background.

ViewMend runs website checks, captures screenshots, compares pages, and stores reports on its own servers. The plugin displays those findings and performance results in WordPress administration.

Events include the affected public page URL when WordPress can identify it. ViewMend can match that URL to a tracked page and queue a check, depending on your integration settings, credits, and existing queued checks.

Use Timeline events alongside completed checks to investigate changes after a release or content update. A ViewMend account and Site Tracker integration are required.

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

WordPress confirms an enabled content, plugin, theme, core, or supported cache action.
The plugin creates one stable event ID and stores the compact event in its local queue.
A background worker delivers the event to ViewMend without delaying the originating WordPress request.
ViewMend records the Timeline context and returns delivery, matched-page, and queue status.
If automatic checks are enabled and the page is eligible, ViewMend queues a check. Results appear in ViewMend and the WordPress Overview.

Native WordPress controls and durable delivery

The plugin has four sections: Overview, Connection, Event rules, and Activity. Overview displays findings, content changes, resources, and selected-page performance from completed ViewMend checks. Resource details include the stored request URLs for the selected check.

Event rules let you choose which actions to report. For example, you can report plugin updates while leaving activation and deactivation events off.

Activity shows delivery status, retries, and the response received from ViewMend. Website checks and page comparisons run in ViewMend.

External service

The plugin connects to ViewMend Site Tracker after an administrator saves an Integration ID and API token. It sends queued events for enabled WordPress actions and connection tests. It reads dashboard results when an administrator opens or refreshes Overview, and resource details when a resource type is selected.

Event requests contain an event ID, type, time, change title and description, public site URL, environment, affected public page URLs, changed-field categories, and WordPress/plugin/theme versions or public object IDs. Public-content events may include an administrative edit URL. The API token is sent in the Authorization header.

ViewMend uses this data to record events, match tracked pages and, when eligible, queue website checks. It returns delivery status and counts of matched pages and queued checks. Dashboard responses contain health counts, findings, content changes, page performance, and resource URLs, MIME types, status codes, sizes and durations from completed checks. They exclude request/response headers, cookies, authorization values and remote IP addresses. Dashboard responses are cached for up to five minutes. An accepted event does not guarantee a completed check.

The plugin does not send post bodies, excerpts, protected content, usernames, email addresses, customer or order data, cookies, IP addresses or arbitrary settings. Use of the service is subject to the ViewMend Terms of Service and Privacy Policy.

Privacy

Only public change metadata is sent; the full field list and exclusions are in External service.

The local queue stores event payloads, delivery state, attempts, redacted errors, HTTP status and ViewMend response details. Completed and failed history is limited to 250 entries. The token is stored separately with autoload disabled and is never displayed, written to queue rows or sent to browser JavaScript. Dashboard results expire from the cache after five minutes.