Browse the knowledge centreKnowledge centreMake sense of your workspace.The complete manual 17 chapters · print or save
REFERENCEFree & Pro3 min read

Collection, attribution and coverage

Understand what Logged.ai records, what the fields mean, and how to read missing or incomplete evidence.

For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.

On this page
IN YOUR WORDPRESS WORKSPACE

Logged.ai → Settings → Collection controls; Activity → Events

Quick answer

Use a record to explain an observed operation. A missing record, a request finding or a summary count cannot prove everything that happened on the site.

01Actor

Who performed the action?

02Subject

What did it affect?

03Outcome

What was observed?

01

Collection and filters do different jobs

#
Choose the control that matches your intention
I want to…UseEffect
Find an existing changeActivity filtersSelects from records already retained. It does not change future capture.
Change supported optional collectionSettings → Collection controlsChanges future content/commerce collection. Essential identity, configuration and privacy collection remain enabled.
Keep evidence for a different periodSettings → Privacy and retentionChanges when older evidence becomes eligible for cleanup; shorter retention needs separate confirmation.
See more detail on the screenDisplay detailChanges presentation only.

Collectors cover supported WordPress accounts, content, settings and components, plus supported WooCommerce activity. Generic WordPress hooks do not provide dedicated coverage for every SEO, form, membership or custom-field plugin.

A preset can change both optional categories and administrative-event retention. Review its proposal before applying it; a troubleshooting preset is not a read-only filter.

02

Read actor, subject and outcome separately

#
How to interpret a record
TermMeaningKeep in mind
ActorThe account or execution context that performed the observed operation.Background or unknown context must not be reassigned to the administrator reading the screen.
Subject / affected objectThe account, post, setting or other object affected.The affected person can be different from the actor.
OutcomeThe result observed by that collector.An attempt, failure and successful change are different results.
Captured field differencesThe supported before/after detail retained for that event.Sensitive values can be minimized or unavailable; not every field has a full value history.
Example: Alex changes Maya’s role

Alex is the actor; Maya is the affected account. Check the observed result and role difference before concluding that the requested change succeeded. Current profile labels are not a historical profile snapshot.

A deleted user can leave an identifier without a current profile. Keep that uncertainty in your notes and handover.

Current navigation context and recorded evidence

Content titles and native editor links are looked up using your current access to help navigation. They are separate from the event’s stored and exported evidence. A revision link refers to the exact retained accessible revision, not a reconstructed copy. Compact price, stock and order differences use the recorded values only; missing or redacted values remain explicit. Item-history and Pro evidence links show retained records in the correct site, not a promise that every past action was collected.

Minimized fields and local integrity

Slug, date, comment and pingback change markers preserve the fact of a supported change without retaining those raw values. Current navigation labels stay separate from the stored record. Report/export consistency checks can detect damaged or mismatched records; they are not signatures against an equally privileged operator who can alter coordinated database values.

03

Know what the evidence cannot answer

#
  • Overview cards and the activity map summarize retained samples. They are not a complete traffic count or a map of your network.
  • Request minute groups count admitted observations, not unique attackers. A finding describes a pattern; it does not prove intent or successful exploitation.
  • Traffic handled by a cache, CDN or server before WordPress may be invisible to the WordPress observer.
  • Events before activation, unsupported direct database edits, collection gaps and evidence already removed by retention cannot be reconstructed from this log.
  • Local storage is not independent, tamper-proof evidence storage.
If something is missing

Check the site, filters, collection choices and retention first. Then use the troubleshooting reference to inspect collection health and request-source coverage.

Why one failed sign-in can leave no Activity row

Failed sign-ins are grouped: ten observed failures in the same fixed five-minute interval create a burst entry. Fewer failures have no individual Activity entries. Intervals restart every five minutes, so attempts on different sides of a boundary count separately. Supported WordPress failures against an existing account can also create a separate account-targeted burst. This identifies the account targeted, not the person attempting to sign in; passwords and attempted login text are not retained.

Requests contains matching findings, not a complete sign-in or traffic log. An upstream block or unsupported authentication integration may never reach the supported WordPress hooks. If an expected burst is missing, inspect System status and collection coverage.

ABOUT THIS REFERENCE

This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.

A question we haven’t answered?

Get help with your next step.

Contact support