Skip to content

Handle repeated and missing clock times in evidence joins

Resolve daylight-saving ambiguity before matching local-time records across tables.

Guides

Handle repeated and missing clock times in evidence joins — what should the operator record?

A local clock time can occur twice during a seasonal clock change or fail to occur during another transition. Joining by displayed hour alone can misplace evidence. Keep the region and offset where available, and decline precise joins when the returned fields do not identify an unambiguous instant.

Practical operations check
Resolve daylight-saving ambiguity before matching local-time records across tables.
Preserve any returned offset and explicit zone name separately; a city label or language alone must not determine a timezone. A region identifier and an offset answer different questions: preserve both where returned, and do not derive either from an account's apparent audience or language.
State which records could be aligned to instants and which remain local-time-only, without claiming unavailable precision or complete hourly coverage. Use local-time-only as a precision state rather than a failed-source label; the evidence can still be useful for a coarser approved task without supporting the precise join.
01 / Guides

Identify region information

Preserve any returned offset and explicit zone name separately; a city label or language alone must not determine a timezone. A region identifier and an offset answer different questions: preserve both where returned, and do not derive either from an account's apparent audience or language.

02 / Guides

Declare ambiguity handling

Require an offset or documented disambiguation for repeated local times, and flag nonexistent times instead of shifting them automatically. If the source gives an ambiguous repeated local hour without offset, the correct output may remain unresolved even when the surrounding records suggest a likely ordering.

03 / Guides

Build transition fixtures

Use clearly labeled test rows for two different offsets sharing one local clock time, checking that the comparison keys remain distinct. Two fixture values with the same displayed 01:30 but different explicit offsets should produce different instants, proving that the join does not collapse them by display text.

04 / Guides

Audit affected joins

Inspect all ambiguous-time exceptions and ensure the transformation did not silently borrow the host computer's timezone or normalize invalid times permissively. Check any spreadsheet import that converts timestamps before the transformation receives them, because ambiguity can already be lost by the time the join script starts.

05 / Guides

Publish the limitation

State which records could be aligned to instants and which remain local-time-only, without claiming unavailable precision or complete hourly coverage. Use local-time-only as a precision state rather than a failed-source label; the evidence can still be useful for a coarser approved task without supporting the precise join.

Keep the boundaries clear.

  • Resolve daylight-saving ambiguity before matching local-time records across tables.
  • Operational record: Identify region information. 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