AdminTrace Activity Logger is a WordPress activity log for sites that need a clear audit trail. It records who changed the site, what changed, and when, in short sentences instead of raw database dumps. Activate it and recording starts at once. There is no paid upgrade.
If you find an issue, or want another feature, please
open a support ticket.
Features
- Activity journal with search, filters, timeline and table views
- Logs content, media, comments, users, plugins, themes, menus, widgets, and WordPress settings
- WooCommerce order, stock, coupon, refund, and product changes when WooCommerce is active
- Login, logout, and failed-login tracking with source (admin form, REST API, XML-RPC, WP-CLI, or other)
- Failed logins grouped into one journal card with a count
- Optional IP lockout after repeated wrong passwords or unknown usernames
- Optional Google reCAPTCHA v3 on login, lost-password, and registration forms
- Dedicated Login security screen with failed-login chart, lockdown list, and unblock
- Optional outgoing email log with preview and resend (separate table, off by default)
- File and database change scan for plugins, themes, drop-ins, and key root files
- Daily or weekly email digest, failed-login alerts, and critical-event emails
- CSV and JSON export of the current journal filters
- Dashboard widget, admin bar list, and post editor history panel
- REST API, WP-CLI, and
srah_log() for other plugins
- Retention controls, masked network addresses by default, and per-site journals on Multisite
- Free: every feature is included without a license
Security and user activity
- Logins, logouts, and failed logins. A failed login says whether the password was wrong or the username does not exist, and whether it came from the admin login page, REST API, XML-RPC, WP-CLI, or another login form. Repeated failed logins collapse into one journal card with a count (like Simple History occasions). After 100 consecutive failures, further attempts are suppressed until other activity is logged.
- Optional Google reCAPTCHA v3 on the WordPress login, lost-password, and registration forms. Add your site and secret keys in Settings, choose a minimum score, and turn it on. There is no checkbox: v3 scores the request in the background. Attempts blocked by reCAPTCHA are written to the journal (for example, a bot login blocked for a username). XML-RPC, REST, and application passwords are not challenged. Failed-login alert emails mention when reCAPTCHA is still off, so you can enable it.
- Second-factor sign-in when the Two Factor plugin accepts a code, including the method name. Rejected second-factor checks are recorded without the code.
- Password resets, role changes, deleted accounts, and application passwords. The secret itself is never stored. Ending the other login sessions for an account is recorded.
- On a multisite network: sites created, deleted, or archived, and users added to or removed from a site.
- Denied admin screens, Site Health changes, and plugin or theme file edits after WordPress has written the file.
- Network addresses are masked by default. The plugin does not look up a city, a host, or a map.
Content, media, and comments
- Posts, pages, custom post types, and site-editor templates. An edit stores the field names and a short added-and-removed preview, not the full post.
- Media uploads, deletions, and image edits such as crop, rotate, flip, and scale. Enable Media Replace file replacements are recorded when that plugin is active. File contents are not stored.
- Categories, tags, comments, and the collaboration notes introduced in WordPress 6.9.
- Navigation menus, including the titles that were added or removed, and sidebar widgets.
Plugins, themes, WordPress, and settings
- Plugin install, update, activation, deactivation, deletion, and automatic-update toggles, with the plugin name and version.
- Theme install, update, switch, deletion, and automatic-update toggles.
- WordPress core updates, language packs, automatic updates, and a notice when the number of available updates changes.
- A curated set of settings, including the site title, permalinks, the homepage, comment rules, and the privacy policy page. Options that look like passwords or API keys are skipped.
- Yoast SEO and Rank Math on-page title, description, and social fields. Other private fields stay out.
WooCommerce activity log
When WooCommerce is active, the same journal records order status, coupon codes used on an order, refunds, stock, product price and SKU changes, and store settings such as currency. Customer email addresses are not stored.
WordPress email log
Outgoing mail is optional and stays off until an administrator turns it on. When the email log is on, messages sent by WordPress, WooCommerce, and other plugins through
wp_mail are saved on their own Email log screen, in a separate table from the activity journal.
Each saved email keeps the recipient, subject, time, and result (sent, failed, or not confirmed), along with the headers, attachment file names, and the message. Search by recipient or subject, and filter by result. Open a subject to preview the message in a popup. Rich email shows the rendered message, and HTML shows the source. The same preview can resend that message to the same recipient. File attachments are not sent again. Message bodies stay out of the activity journal. The log is off by default because a saved message can include a password-reset link. Saved emails follow the same retention period as the journal.
Other plugins
These events are recorded when the other plugin is active and fires its public hook:
- Jetpack module activation and deactivation
- User Switching
- Advanced Custom Fields field groups
- Duplicate Post clones
- Beaver Builder layout saves
- Redirection saves and deletions
Where to read the audit log
- The activity journal, with search plus filters for category, severity, source, account, and date
- Timeline and table views
- A Dashboard widget and an admin-bar list
- On WordPress 6.9 and newer, the journal screens can be opened from the WordPress command palette, because core lists every admin menu page there. The plugin does not add commands of its own.
- A panel on the post editing screen for that post’s history
- A plain-text daily or weekly email digest, and an email when failed logins cross a threshold
- A private RSS feed that stays off until an administrator enables it
- CSV and JSON export of the current filters, up to 5,000 rows
- REST API and WP-CLI, including a way for other plugins to add events with
srah_log()
- Separate screens for event ID switches and the file and database scan
Files and database
A scan can record files that were added, changed, or deleted. It covers PHP, JavaScript, CSS, and HTML files in plugins, themes, and must-use plugins, PHP drop-ins in wp-content, and wp-config.php, .htaccess, and .user.ini in the site root. Each plugin or theme is limited to 6,000 files and the whole scan to 20,000. Uploads are left out unless you turn them on under Files and database. Then PHP, JSON, XML, text, SVG, and HTML files in uploads are included. JavaScript, CSS, images, and archives in uploads are not scanned.
The scan runs when an administrator opens wp-admin (at most once a minute, and every time on the AdminTrace screens), after a plugin or theme is installed, activated, deleted, or switched, once a day from WP-Cron, and when you click Scan now. It can also record when a database table with this site’s prefix is created or dropped. The first scan only saves a baseline. File contents and SQL are not stored. WordPress core folders are not hashed.
How long it is kept
Events are kept for 90 days by default. Choose any period from 0 days, which keeps rows until you delete them, through 10 years. Administrators can tick events in the journal (timeline or table) and delete them after a confirmation, delete one event through the REST API, or clear the journal for the current site from Settings. Deleting a combined card removes every repeat it stands for.
Editors and shop managers can be allowed to see content activity. They do not see security events or network addresses. Shop managers can also see WooCommerce events.
Multisite keeps a separate journal on each site.
Privacy
The journal stays on this site. Profile photos load from Gravatar for events tied to a user account; initials are drawn on the site when there is no account. Each event stores the acting user’s role and the time to the millisecond. It does not set a tracking cookie or call an analytics service. The email digest and the HTTPS webhook stay off until an administrator turns them on. Two emails are on by default and go to the site administration address, or to the alert address you set: one when failed logins cross the threshold (this can be turned off), and one for each critical event. Google reCAPTCHA v3 stays off until you add keys and enable it; then the login forms load Google’s script and the server verifies tokens with Google. Suggested wording is added under Settings → Privacy, and the personal-data exporter and eraser include rows tied to that account.
What this activity log does not do
- It does not hide itself from the Plugins screen.
- It does not scan core files against WordPress.org checksums.
- It does not forward events to syslog, Datadog, or Splunk. One HTTPS webhook is available.
- It does not record the body of outgoing HTTP requests. Outgoing email is stored in a separate table only after an administrator turns the email log on.
- It does not keep a separate log of WP Crontrol cron events.