Description
Divide their exact integer difference using floor semantics, returning numeric window index and a nonnegative offset below windowLength.
Advertising records distinguish billable exposure, disclosure support, cyclic reporting windows, layout insets and supplied tax bases. A code-point budget or visibility-duration share does not establish readable or legally sufficient disclosure. Nominal geometry and costs require the intended platform and reporting conventions.
Divide their exact integer difference using floor semantics, returning numeric window index and a nonnegative offset below windowLength.
When to use this tool
Use Frequency Cap Window Offset when checking the stated advertising layout, exposure, boundary or cost convention.
How to use the tool and how it works
- Enter eventTime, windowOrigin, windowLength. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read windowIndex, offset. Use the output convention below.
Require whole event/origin coordinates and positive whole window length. Divide their exact integer difference using floor semantics, returning numeric window index and a nonnegative offset below windowLength.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| eventTime | Event Time | Required. Safe integer. |
| windowOrigin | Window Origin | Required. Safe integer. |
| windowLength | Window Length | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| windowIndex | Floor quotient of exact relative integer time; negative windows are allowed and output remains numeric. | Required. Safe integer. |
| offset | Nonnegative within-window remainder strictly below windowLength. | Required. Safe integer. |
{
"input": {
"eventTime": 125,
"windowOrigin": 100,
"windowLength": 10
},
"output": {
"windowIndex": 2,
"offset": 5
}
}Limitations and assumptions
- Negative relative times belong to negative windows; outputs are numbers rather than arbitrary-precision text and no ad-delivery policy is selected.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Inspect actual rendered creatives and verified delivery/billing records, and consult applicable platform, advertising and tax requirements for real decisions.
References
Similar or alternative tools
- Ad Frequency Reset Boundary Token
Return eventTime>=resetTime when equalityInNewPeriod=true; otherwise require strict eventTime>resetTime for newPeriod.
- Coupon Attribution Last Day Flag
Compare conversion<=expiry or conversion<expiry according to inclusive, and preserve the source label.