Folder monitoring follows an already detected copy over time. In LDM, the observation window starts from that copy's first receipt or detection, rather than treating the whole run's start time as the age of every message. Later checks can show that copy's observed folder history. They do not resend the message, test an edited template, or establish the delivery of a future campaign.
Identify the copy and its starting point
Record the recipient, matching identifier, first-detection timestamp, and first observed folder. Different destinations can receive their copies at different times. A late-arriving copy should not be described as having completed the same observation duration as an earlier copy merely because both belong to one run.
Keep sending time separate from first detection. The gap can include queueing, transport, or observation scheduling. It is not automatically a measured receiving-provider delay. If the report provides several timestamps, name them precisely in an export or review. A single unlabelled time makes a timeline difficult to interpret.
Read changes as observations at checkpoints
Suppose an educational timeline shows Inbox at one check and Spam at a later check. That supports a change in observed folder between those checkpoints for the matching copy. Unless a more precise event is available, it does not establish the exact instant of movement or the receiver's private reason for the change.
Confirm that the observer is still following the same copy. Duplicate sends, threading, or replacement messages can otherwise confuse a comparison. Save the message identifier and relevant recipient token. If a mailbox becomes unavailable during the window, preserve the gap; do not assume the previous folder continued unchanged throughout an unobserved interval.
Separate monitoring from a new experiment
Editing your template or changing DNS does not retroactively create a new copy inside an old mailbox. The older message can continue to supply evidence about its own history, but it does not evaluate the newly configured route. Send a fresh controlled test when the question concerns changed content, authentication, tracking, or infrastructure.
Likewise, an old copy remaining in Inbox does not certify a resumed campaign. Sending volume, audience composition, and receiving context can change. Folder history is one diagnostic view within a broader operational review. It cannot establish subscriber engagement, consent, or future delivery simply by remaining green for a day.
Compare timelines fairly
Compare copies at similar elapsed times from their own first detection. Note any observation gaps and differences in the provider set. A run observed for several hours and another observed only immediately after receipt have unequal evidence. Do not select the most favourable point from each and call the difference a controlled improvement.
For a useful incident record, include first detection, each available folder observation, unavailable intervals, and any new sends or manual actions. Keep the original observations when later data changes the summary. If a copy is no longer found, distinguish that later search result from a confirmed move to a particular folder. Missing at a checkpoint is not a substitute for observing its destination.
Frequently asked questions
Does monitoring send the email again every time?
No. It observes the same matching copy. A new send is a separate action and should have its own recorded identity and conditions.
Does the window start when I create the test?
For copy-level monitoring, use the copy's first receipt or detection. Run creation and individual message arrival are different events.
Can monitoring explain who moved the message?
The folder history alone normally cannot establish whether filtering, a user action, or another rule caused the change. Preserve the observation and investigate additional evidence before assigning a cause.
Sources and scope
Source check: November 5, 2026. Source checking is separate from publication. Observations apply to the tested copies and conditions.