Skip to content

Join date-only records without inventing exact event times

Preserve calendar-date precision when evidence lacks an offset-bearing timestamp.

Guides

Join date-only records without inventing exact event times — what should the operator record?

Some returned evidence carries a day but no exact publication instant. Converting that day to midnight can make an interval join look precise while introducing an assumption. Treat date-only records as calendar observations and explain when they cannot support an instant-level match to another operational table.

Practical operations check
Preserve calendar-date precision when evidence lacks an offset-bearing timestamp.
Separate instant, local-datetime, calendar-date and missing values in a precision column before attempting any temporal transformation. A calendar-date value should stay recognizable as a date rather than being rendered with an invented time and offset that downstream users may interpret as observed.
Include join_precision and unresolved_reason, preserving actual returned dates without implying that every event within those dates was inspected. If later authorized evidence provides a precise timestamp, append a new observation and update the derived join revision rather than retroactively pretending the original date was exact.
01 / Guides

Classify time precision

Separate instant, local-datetime, calendar-date and missing values in a precision column before attempting any temporal transformation. A calendar-date value should stay recognizable as a date rather than being rendered with an invented time and offset that downstream users may interpret as observed.

02 / Guides

Choose a compatible window

Use a declared calendar and timezone context for date-level comparisons; if that context is unknown, leave cross-zone alignment unresolved. For cross-zone daily summaries, require an explicit agreed calendar context; a date attached to a public page may not identify the publisher's exact event-day convention.

03 / Guides

Test narrow-window behavior

Verify that a date-only fixture does not automatically qualify for a one-hour window merely because a parser assigned midnight. An unresolved narrow-window result should remain present in an exception view instead of being silently excluded as though its event definitely occurred outside the interval.

04 / Guides

Review coarse matches

Label date-level joins as coarse and keep them separate from exact-instant matches so downstream operators can apply an appropriate gate. A date match may be adequate for a daily operational inventory but insufficient for ordering events; keep the intended task attached to that approval.

05 / Guides

Deliver precision-aware output

Include join_precision and unresolved_reason, preserving actual returned dates without implying that every event within those dates was inspected. If later authorized evidence provides a precise timestamp, append a new observation and update the derived join revision rather than retroactively pretending the original date was exact.

Keep the boundaries clear.

  • Preserve calendar-date precision when evidence lacks an offset-bearing timestamp.
  • Operational record: Classify time precision. Context badges do not certify access.

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-15. 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