This project is not covered by Drupal’s security advisory policy.
ViewMend is a website quality platform for understanding, monitoring, and improving websites. This official integration connects Drupal to ViewMend Site Tracker for durable Drupal website change monitoring, explicit deployment monitoring, and privacy-bounded public content lifecycle tracking.
Drupal stores each event locally before delivery and sends it asynchronously. ViewMend uses accepted events as Timeline markers and can queue the Site Tracker checks associated with a connection.
Use the integration to connect Drupal publishing and deployment events with the website content, metadata, indexability, performance, script, and page-weight checks that follow in Site Tracker.
Features
- Records confirmed publish, update, unpublish, and deletion events for allow-listed public content types.
- Records successful configuration imports, extension install or uninstall operations, optional full cache flushes, and explicit deployment markers.
- Persists events before delivery with stable event IDs, bounded retries, retention, and duplicate-safe delivery.
- Provides administrator activity with queued, in progress, accepted, duplicate, retry scheduled, permanently failed, and cancelled states.
- Supports explicit retry, run-now, cancel, and delivered-history cleanup operations.
- Does not send content bodies, titles, account information, request data, arbitrary configuration, or customer data.
Post-Installation
Open Configuration → Web services → ViewMend Site Tracker. Configure the integration UUID, public site origin, environment, and token source, then choose the content types and confirmed Drupal lifecycle events to report. Drupal cron schedules due deliveries, recovers interrupted work, and applies retention.
Additional Requirements
External delivery requires a ViewMend account, a Site Tracker integration UUID, and a bearer token. The module sends deliberately configured operational event metadata to https://viewmend.com/api/v1. Review ViewMend, Site Tracker, and the applicable ViewMend terms and privacy information before enabling delivery.
The runtime module uses Drupal core HTTP, Queue, Lock, and Database APIs. It does not require Drush, Key module, the ViewMend PHP SDK, or a third-party HTTP package.
Recommended modules/libraries
The Key module can optionally provide the bearer token, and Drush 12 or later adds deployment, queue, status, and retry commands. Neither is required for normal runtime operation.
Similar projects
This module is specifically designed to connect confirmed Drupal lifecycle events to the hosted ViewMend Site Tracker. It complements rather than replaces Drupal logging, uptime monitoring, content moderation, or crawler-based website audits.
Community Documentation
The project supports Drupal 10.6, Drupal 11.3, and Drupal 11.4 on compatible PHP releases. It is licensed under GPL-2.0-or-later.
Project information
- Project categories: Administration tools, Automation, Integrations
- Created by phpner on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
Releases
Initial stable release with durable queued delivery, Drupal lifecycle event rules, redacted activity, deployment markers, retries, and Drupal 10.6/11.x support.
