Skip to content

Separate event time from publication time

Build an event interpretation from what a source says happened, rather than assuming a post’s publication date is the date of the reported event.

Guides

When did the reported event happen relative to the post?

A video published in November may describe a camping stove failure from the previous summer. Placing that failure on a November incident timeline would confuse reporting with occurrence. For retrospective research, preserve the time a source became public separately from the time it says an event happened, including uncertainty in both fields.

Example research prompt
Build separate event and publication timelines for supplied camping stove accounts. Preserve relative date wording and leave event timing unknown where publication alone is insufficient.
01 / Guides

Extract distinct time claims

Record publication date, explicitly stated event date and the date the material was reviewed as separate fields. Include relative phrases such as last weekend verbatim beside any interpretation. Exclude publication dates from the event-date field unless the source clearly establishes that the described event occurred on that same date.

02 / Guides

Interpret relative wording carefully

Resolve a phrase such as yesterday only when the publication timestamp and relevant time basis are sufficiently clear. Keep an interval or unknown value when they are not. Do not invent day-level precision from a seasonal reference, nor assume the reviewer’s local time zone matches the source’s intended calendar date.

03 / Guides

Check the analytical consequence

Build one view ordered by publication and another ordered by known event timing. Ask whether the apparent cluster of failures changes. A difference can reveal reporting delay, but cannot explain why people posted late. Keep events with unknown timing out of precise incident comparisons while retaining them in the broader evidence inventory.

04 / Guides

Deliver a two-clock timeline

Present events and publications with explicit labels and uncertainty ranges where needed. Explain which conclusions concern public attention and which concern reported occurrences. If event dates are largely missing, limit the result to publication patterns rather than presenting a detailed incident trend assembled from timestamps that measure a different process.

Keep the boundaries clear.

  • Publication timing can measure attention without measuring incident timing.
  • Platform context does not guarantee historical access or complete coverage.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage