How can we help?

Search for answers or browse our knowledge base.

Table of Contents

How to configure the WordPress activity log retention policies

By default the WP Activity Log plugin keeps six (6) months of data in the WordPress activity log (audit trail). Therefore when events are older than six months, they will be deleted from the activity log. You can configure the plugin to keep all data or change the retention period of the WordPress activity log events from the plugin’s settings page, as explained in this post.

For how long should you keep the WordPress activity log?

This really depends on your business and requirements. Refer to managing WordPress activity logs best practices for more detailed information on this subject, so you can make an informed decision.

Configuring the WordPress activity log retention policies

You can configure the retention period of the events in the WordPress activity log by specifying how old the data should be before it is deleted. The WordPress activity log data retention settings are highlighted in the below screenshot.

Activity log retention policy

To configure the activity log retention period:

  1. From WordPress’ main menu, click on WP Activity Log and then click on Settings
  2. Click on the Activity log viewer tab
  3. Select any of the following options:
    1. Keep all data – this means that no retention period will be configured and the activity logs will be kept indefinitely
    2. Delete events older than – use this option to delete events that are older than the configured retention period by selecting the number of months or years from the drop-down menus

Retention settings for archiving the WordPress activity log

When you configure the archiving of the WordPress activity log the retention settings are moved to Archiving settings. The archiving feature is available in the premium edition of the WP Activity Log plugin with which you can also use the Activity Log Database & Integration tools  to save the WordPress activity log in an external database rather than on the WordPress database.