Block for Strava vs MH User Activity Monitor

Block for Strava lets you share your Strava activities, routes, and segments on your WordPress site. Paste a link from Strava and the official Strava embed appears in your post — interactive map, elevation profile, stats, and all. There’s nothing to set up. No accounts to connect, no keys to copy, no extra software. If you can paste a link, you can use this plugin. What you can do: Paste a Strava link and turn it into a rich, interactive embed Embed any public activity, route, or segment — and your own private activities too (see the FAQ) Customize how routes look: map style, terrain, units, full-width display, dirt-surface highlighting, and an elevation toggle See exactly what your readers will see, right in the editor as you make changes Already typed a Strava link inside a paragraph? Click the paragraph and use the block toolbar’s “Transform to” menu to swap it for a Strava block A note about private activities: If your Strava activity is set to “Followers” or “Only You”, open it on Strava, click Share → Embed, and copy the embed code Strava gives you. Paste that on its own line in your post and the block takes care of the rest. Trademark Notice: Strava is a trademark of Strava Inc. This plugin is not affiliated with or endorsed by Strava Inc. External services This plugin uses Strava’s public embed feature to display your content. When someone views a page with a Strava block, their browser loads the embed directly from https://strava-embeds.com/. As part of that, Strava may receive normal request information from the visitor — such as their IP address, browser type, your site’s domain (not the full page URL), and the ID of the activity, route, or segment being shown. For private activities, the embed code you paste from Strava includes a share code. That share code is what tells Strava it’s allowed to display the activity, and it’s sent to Strava every time the embed loads. For Strava short links (the kind that start with https://strava.app.link/), your site asks Strava what the full link is and remembers the answer for up to a day, so the same link doesn’t trigger a fresh lookup on every visit. After that the check happens again. These checks only go to strava.app.link or strava.com. External service: Strava public embeds (strava-embeds.com, strava.app.link, strava.com), operated by Strava, Inc. This plugin is independently developed and is not affiliated with or endorsed by Strava Inc. Terms of Service: Strava Terms of Service Privacy Policy: Strava Privacy Policy Development The plugin’s source code is maintained on GitHub: Block for Strava on GitHub. The version downloaded from WordPress.org is ready to use as-is. If you’d like to build the plugin from source, clone the repository and run: npm ci npm run build

MH User Activity Monitor shows in real time which users, visitors, WooCommerce customers and bots are currently active on your WordPress website. The plugin helps administrators identify unusual activity, cart sessions, bot traffic and suspicious requests more quickly, with privacy options such as IP anonymization, data-saving mode and automatic cleanup. Live monitoring for WordPress websites MH User Activity Monitor displays active sessions directly in the WordPress admin area. Administrators can see which visitors are currently online, whether logged-in users are active, which page types are being viewed and when the last activity occurred. The overview uses dashboard cards, filters, sorting and live refresh. This makes it easier to distinguish normal visitor activity from unusual access patterns. Administrators can also export the currently filtered session overview as a CSV file for short-term support or security review workflows. Keep an eye on WooCommerce carts When WooCommerce is active, the plugin can display active cart sessions. Depending on the selected setting, it stores and displays only the item count, item count and cart total, or detailed product information. This can help shop owners see whether customers currently have products in their cart, whether carts are abandoned or whether unusual sessions appear in the checkout area. Detect bots and suspicious requests The plugin detects known bots, crawlers, SEO tools, AI crawlers, social media preview bots and suspicious request patterns. Examples include requests to login areas, XML-RPC, .env files, .git directories or other typical scanner targets. The bot and risk indicators are not a firewall and do not replace a dedicated security plugin. They help make suspicious technical traffic more visible and easier to classify. Privacy-friendly settings Because the plugin processes technical visitor data, it includes several privacy options. New installations use anonymized IP addresses by default. Additional privacy modes such as None, Standard, Data-saving and Strict are available. Stored URLs and referrers are saved without query parameters so sensitive values such as tokens, email addresses, search terms or tracking parameters are not stored unnecessarily. User-agent, URL and referrer values are also length-limited to reduce the amount of stored data. Additional options include automatic cleanup via WordPress-Cron, ignored IP rules, CIDR support, WooCommerce cart modes and the ability to disable the frontend ping completely. Who is this plugin for? The plugin is suitable for operators of WordPress websites, WooCommerce shops, membership areas, booking sites and editorial websites who want a short-term view of what is happening on their website right now. Typical use cases include: Shop owners want to monitor active carts and checkout sessions. Administrators want to identify unusual bot traffic or scanners more quickly. Website operators want to see which pages are currently being visited. Support teams want to understand short-term technical visitor activity. Operators of smaller websites want a simple live overview without external tracking services. The plugin is intended for short-term technical monitoring. Site operators should check which data they really need, how long it is stored and whether information must be added to their privacy policy. Stability note This version is marked as the current stable build. Translations, help texts, screenshots, version metadata and basic PHP/ZIP checks were reviewed again before release. Requirements WordPress 6.2 or newer. PHP 7.4 or newer. Tested up to WordPress 7.0. WooCommerce is optional and only required for cart monitoring.