Skip to content

Use half-open windows to prevent duplicate boundary rows

Define start-inclusive and end-exclusive intervals for reproducible joins across adjacent reporting windows.

Guides

Use half-open windows to prevent duplicate boundary rows — what should the operator record?

Adjacent windows can both admit a row at midnight if their boundary rules are unspecified. A half-open convention is one useful local solution, provided every table applies it consistently. Record the chosen rule and timezone so a later operator can reproduce the split without relying on spreadsheet display formatting.

Practical operations check
Define start-inclusive and end-exclusive intervals for reproducible joins across adjacent reporting windows.
Represent each window as start_inclusive and end_exclusive instants with an explicit comparison timezone and the original requested scope. Write the normalized start and end values into the manifest so an inclusive-looking human label such as through Sunday cannot obscure the implemented boundary convention.
Tell recipients that window labels describe your transformation contract, not a claim that the underlying source uses the same reporting convention. Include precision limitations for date-only evidence, since an instant-based half-open rule cannot resolve a boundary when the source provides only an unspecified calendar day.
01 / Guides

Write the interval contract

Represent each window as start_inclusive and end_exclusive instants with an explicit comparison timezone and the original requested scope. Write the normalized start and end values into the manifest so an inclusive-looking human label such as through Sunday cannot obscure the implemented boundary convention.

02 / Guides

Map eligibility conditions

Use timestamp >= start and timestamp < end in the local transformation, keeping unknown timestamps unresolved instead of assigning them arbitrarily. If an input already uses a different documented reporting convention, record the conversion rather than renaming its labels and assuming the intervals now align.

03 / Guides

Test shared boundaries

Create fixture rows immediately before, exactly at and immediately after the shared cutoff; each exact instant should belong to at most one adjacent window. For a cutoff at 00:00:00Z, the exact cutoff row belongs only to the later adjacent interval; preserve this expectation in the local fixture output.

04 / Guides

Reconcile partition membership

Compare unioned window keys with the eligible input keys and inspect duplicates or omissions before treating the split as correct. Check distinct qualified keys across partitions, not just summed counts, because a duplicate in one window and an omission in another can cancel numerically.

05 / Guides

Document downstream expectations

Tell recipients that window labels describe your transformation contract, not a claim that the underlying source uses the same reporting convention. Include precision limitations for date-only evidence, since an instant-based half-open rule cannot resolve a boundary when the source provides only an unspecified calendar day.

Keep the boundaries clear.

  • Define start-inclusive and end-exclusive intervals for reproducible joins across adjacent reporting windows.
  • Operational record: Write the interval contract. 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