Activity Log, Error Log, User Activity Tracking from Logtivity

Logtivity has some support for most WordPress plugins. If the plugin uses post types, we record when most post types are updated, created or deleted. We currently have integrations with Easy Digital Downloads, Memberpress and Download Monitor. These integrations allow you to track things like Memberpress subscription creations, changes, or cancellations and also track when files are downloaded through Download Monitor. We are working on more detailed event monitor support for some key plugins, including eCommerce plugins such as WooCommerce and Easy Digital Downloads. Please contact us for specific details on any plugin that you are using.

Yes, our user activity tracking plugin provides a flexible API to log and store custom events with Logtivity. An example of logging a custom event is below. This example is recording information from Stripe.com for a customer: Logtivity::log() ->setAction('My Custom Action') ->addMeta('Meta Label', $meta) ->addMeta('Another Meta label', $someOtherMeta) ->addUserMeta('Stripe Customer ID', $stripeCustomerId) ->send(); Click here to see more about custom activity logs.

Logtivity records all core WordPress actions. In addition to support for the WordPress core, Logtivity records events for many plugins and themes. Click here to see more about what Logtivity records.

It’s important to have an activity log on your WordPress site. You need user tracking because you need to know many people are visiting, making purchases, and logging in to your site. Yes, you can track visitors with Google Analytics, and you can track purchases with your payment gateway, but it’s harder to track WordPress-specific information such as log ins. Using Logtivity, you can get an overview of who is logging in to your site, and how many people are logging in every day. If Logtivity is active on your site, you can go to the “Logs” screen and search for all the “User Logged in” events. You can use the search boxes to drill down for more specific user tracking information. For example, you can use the “Context” box to search for a particular user role. You can use this to search for all "Administrator" logins or all "Editor" logins. You can also use the search option as a security log and look for nefarious patterns in the audit logs. For example, you can search by IP address to see if one person is using multiple logins. Or you can search by username to see if one account is being shared by different people. Click here to see more about activity logs for user logins.

Yes, Logtivity gives you complete control over the user tracking information recorded in the audit logs. You can choose your GDPR settings. You can decide to only log a profile link, user ID, username, IP address, or nothing at all.

• Inside your WordPress site, go to “Tools” and then “Logtivity”.
• You can uncheck the boxes on this screen to stop Logtivity from recording personal user trackking data.

• Store User ID: If you check this box, when logging an action, we will include the users User ID in the logged action.
• Store Users Profile Link: If you check this box, when logging an action, we will include the users profile link in the logged action.
• Store Users Username: If you check this box, when logging an action, we will include the users username in the logged action.
• Store Users IP Address: If you check this box, when logging an action, we will include the users IP address in the logged action.

Yes! You can easily disable all event monitoring that this plugin provides so that you can only store the user tracking audit logs that matter to you manually. You can also disable built in logs on an individual basis via the filter example below: ` add_action('wp_logtivity_instance', function($Logtivity_Logger) { if (strpos($Logtivity_Logger->action, 'Page was updated') !== false) { $Logtivity_Logger->stop(); } }); ` Click here for more about disabling activity logs.

Yes, it is possible to rename the events that are stored in Logtivity’s audit logs. For example, you can add this code to your site’s functions.php file. This code will result in an event “File Downloaded” being logged as “Resource Downloaded”. add_action('wp_logtivity_instance', function($Logtivity_Logger) { if (strpos($Logtivity_Logger->action, 'File Downloaded') !== false) { $Logtivity_Logger->setAction('Resource Downloaded'); } }); Click here for more about renaming activity logs.

Yes, Logtivity makes it easy to export your user activity data into a CSV file. Follow these steps for your audit log export:

• To get started, visit the “Logs” area inside https://app.logtivity.io.
• You can either search for a specific result, or you can use export all your event monitoring logs.
• When you see the logs you want to export, click “Actions” and then “Export to CSV”.
• Logtivity will show you the following message: “Export scheduled”.
• When the export file is ready, Logtivity will send you an email with a download link to the CSV file.

Yes, You can use Logtivity to send alerts to your Slack account. Follow these steps to connect Logtivity to a channel in your Slack account:

• In the Logtivity app, click on the name of your team.
• Click "Alert Channels".
• Check the "Slack" box.
• Enter the name of your Slack channel.
• Click the "Add Channel" button.
• You will now see a screen where Slack asks you to allow Logtivity access. Click the "Allow" button.
• You will be redirected back to the Logtivity app.
• Any alert for this Logtivity team will now be sent to your Slack account.

There are some hosted solutions such as ManageWP, MainWP, WPMU Dev, Jetpack, WP Umbrella, WP Remote, InfiniteWP, CMS Commander, iControlWP and more. Logtivity is different because it is focused on more advanced tools for agencies. With Logtivity you have very detailed activity logs and incredibly detailed error logs. We're committed to building expert levels tools to help WordPress professionals.

Logtivity is the official brandname. When writing about this activity plugin, please make sure to uppercase the L:

• Logtivity (correct)
• logtivity (incorrect)
• Logtivity.io (incorrect)
• Log tivity, loggtivity, logg tivity (all incorrect)