Collection, attribution and coverage

Collection controls determine the supported categories recorded on your site. Activity filters select from already-retained records. A preset or exclusion is a collection choice; changing a filter does not change future capture.

Supported collectors cover WordPress account, content, settings and component activity, with WooCommerce-specific activity. General WordPress hooks are not dedicated coverage for every SEO, forms, membership or custom-field plugin.

Check acting user, affected object, execution channel and observed outcome separately. A background action or unknown actor should not be reassigned to whichever administrator is currently looking at the screen.

A deleted user can leave a retained identifier without a current profile. Before/after values can be minimized or unavailable. The absence of a field or record is not proof that no operation occurred.

Overview cards and the activity map summarize a retained sample. They are not a complete traffic count or network-topology map. Request minute groups count admitted observations, not unique attackers.

Activity cannot reconstruct unsupported direct database edits or events missed before activation, during a gap or after retention removed them. Local storage also does not make the evidence independently immutable.