Title: ViewMend Site Tracker Author: Oleksandr Published: Атырдьах ыйа 21, 2026 Last modified: Атырдьах ыйа 21, 2026 --- Search plugins ![](https://ps.w.org/viewmend-site-tracker/assets/banner-772x250.png?rev=3658534) ![](https://ps.w.org/viewmend-site-tracker/assets/icon-256x256.png?rev=3658534) # ViewMend Site Tracker By [Oleksandr](https://profiles.wordpress.org/phpner/) [Download](https://downloads.wordpress.org/plugin/viewmend-site-tracker.1.0.0.zip) * [Details](https://sah.wordpress.org/plugins/viewmend-site-tracker/#description) * [Reviews](https://sah.wordpress.org/plugins/viewmend-site-tracker/#reviews) * [Installation](https://sah.wordpress.org/plugins/viewmend-site-tracker/#installation) * [Development](https://sah.wordpress.org/plugins/viewmend-site-tracker/#developers) [Support](https://wordpress.org/support/plugin/viewmend-site-tracker/) ## Description ViewMend Site Tracker for WordPress connects confirmed CMS changes to [ViewMend Site Tracker](https://viewmend.com/site-tracker). It records events locally and delivers compact metadata through a durable background queue, so normal WordPress requests do not wait for the external service. Use the connector to add publication, plugin, theme, WordPress core, and WP Rocket cache context to a website change tracking workflow. 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 website change tracking 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](https://viewmend.com/articles/post-deployment-website-monitoring). #### Native WordPress controls and durable delivery The settings area separates Overview, Connection, Event rules, and Activity. 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](https://viewmend.com/site-tracker) to deliver site-change events to the integration selected by the administrator. It does not contact ViewMend until an administrator explicitly configures a ViewMend endpoint, integration ID, and API token. After configuration, a request is made when the administrator 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. An accepted event does not guarantee that a check starts or completes. Use of the service is subject to the [ViewMend Terms of Service](https://viewmend.com/terms-of-service) and [ViewMend Privacy Policy](https://viewmend.com/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. The API token is stored in a separate non-autoloaded option and never stored in queue rows. ## Screenshots [⌊The Overview shows active event reporting, durable local queue health, and the latest delivery accepted by ViewMend.⌉⌊The Overview shows active event reporting, durable local queue health, and the latest delivery accepted by ViewMend.⌉[ The Overview shows active event reporting, durable local queue health, and the latest delivery accepted by ViewMend. [⌊Connection settings keep the saved API token hidden while showing the exact delivery endpoint, tracked site, and environment.⌉⌊Connection settings keep the saved API token hidden while showing the exact delivery endpoint, tracked site, and environment .⌉[ Connection settings keep the saved API token hidden while showing the exact delivery endpoint, tracked site, and environment. [⌊Event rules explain every confirmed WordPress action and let administrators choose publication, meaningful update, and permanent deletion events individually.⌉⌊Event rules explain every confirmed WordPress action and let administrators choose publication, meaningful update, and permanent deletion events individually.⌉[ Event rules explain every confirmed WordPress action and let administrators choose publication, meaningful update, and permanent deletion events individually. [⌊Activity separates local delivery status from the queue state and matched-page response returned by ViewMend.⌉⌊Activity separates local delivery status from the queue state and matched-page response returned by ViewMend.⌉[ Activity separates local delivery status from the queue state and matched-page response returned by ViewMend. ## Installation 1. Upload and activate the plugin. 2. Open Settings -> ViewMend Site Tracker. 3. Enter the ViewMend URL, integration ID, API token, tracked site URL, and environment. 4. Save the connection and queue a connection test. The test creates a real ViewMend event. 5. Open Event rules and choose the confirmed WordPress operations that should create events. 6. Open Activity, confirm the local test row reaches Delivered, and inspect the queue state returned by ViewMend. WordPress cron must run for background delivery. The plugin schedules near-term work and a recurring five-minute recovery event. Multisite network activation is not supported. Activate and configure the plugin separately for each required site. ## FAQ ### Is this a standalone website change monitor? No. The plugin is a WordPress event connector for ViewMend Site Tracker. It records when supported WordPress changes happen and sends their context to ViewMend. Website checks, selected-page monitoring, screenshots, reports, and comparisons remain ViewMend services. ### Can it track WordPress page changes? For a public post, page, or product, the plugin sends the exact affected permalink when WordPress can determine it. ViewMend can match that URL to an already tracked page and may queue a check when the integration configuration and account state permit it. Drafts, autosaves, revisions, trash moves, and protected content are excluded. ### Which site changes can it report? The plugin supports public content publication, meaningful updates and permanent deletion; plugin and theme lifecycle operations; completed WordPress core updates; confirmed WP Rocket cache purges; and an administrator connection test. Event rules can enable only the categories and exact operations you need. ### Does the plugin run audits or screenshots? No. It sends change metadata to ViewMend. ViewMend owns Tracker checks, screenshots, audit work, credits, scheduling, and comparisons. ### Does the plugin contact an external service? Yes. The plugin is a connector for ViewMend Site Tracker. It sends queued change metadata only after an administrator configures the ViewMend connection. The External service section lists the circumstances, transmitted fields, service link, terms, and privacy policy. ### Which cache plugins are supported? WP Rocket only. The plugin listens to documented WP Rocket post-purge hooks for full-domain and exact-URL cache clearing. It does not guess when another cache product has finished a purge. ### What happens when ViewMend is unavailable? Network errors, HTTP 429, and server errors use bounded exponential retry. Retry- After is respected up to six hours, and one logical event is attempted no more than six times automatically. Manual retry preserves the original event ID. ### What happens on deactivation or uninstall? Deactivation removes cron schedules and preserves all data. Uninstall also preserves data by default. An explicit setting can opt into removing ViewMend settings, the token, and local delivery history during uninstall. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “ViewMend Site Tracker” is open source software. The following people have contributed to this plugin. Contributors * [ Oleksandr ](https://profiles.wordpress.org/phpner/) [Translate “ViewMend Site Tracker” into your language.](https://translate.wordpress.org/projects/wp-plugins/viewmend-site-tracker) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/viewmend-site-tracker/), check out the [SVN repository](https://plugins.svn.wordpress.org/viewmend-site-tracker/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/viewmend-site-tracker/) by [RSS](https://plugins.trac.wordpress.org/log/viewmend-site-tracker/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * Initial production release with durable delivery, recovery, observability, security controls, lifecycle handling, documented event adapters, external-service disclosure, and WordPress Privacy Policy Guide content. ## Meta * Version **1.0.0** * Last updated **8 чаас ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/viewmend-site-tracker/) * Tags * [change tracking](https://sah.wordpress.org/plugins/tags/change-tracking/)[content updates](https://sah.wordpress.org/plugins/tags/content-updates/) [deployment](https://sah.wordpress.org/plugins/tags/deployment/)[website monitoring](https://sah.wordpress.org/plugins/tags/website-monitoring/) * [Advanced View](https://sah.wordpress.org/plugins/viewmend-site-tracker/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/viewmend-site-tracker/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/viewmend-site-tracker/reviews/) ## Contributors * [ Oleksandr ](https://profiles.wordpress.org/phpner/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/viewmend-site-tracker/)