Skip to content

Main content

Ad Frequency Reset Boundary Token Tool

Calculate ad frequency reset boundary token from explicit caller-supplied inputs.

Loading tool…

Description

Return eventTime>=resetTime when equalityInNewPeriod=true; otherwise require strict eventTime>resetTime for newPeriod.

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.

Return eventTime>=resetTime when equalityInNewPeriod=true; otherwise require strict eventTime>resetTime for newPeriod.

When to use this tool

Use Ad Frequency Reset Boundary Token when checking the stated advertising layout, exposure, boundary or cost convention.

How to use the tool and how it works

  1. Enter eventTime, resetTime, equalityInNewPeriod. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read newPeriod. Inspect newPeriod before interpreting the associated values.

Return eventTime>=resetTime when equalityInNewPeriod=true; otherwise require strict eventTime>resetTime for newPeriod.1

Input fieldMeaning and unitsAccepted input
eventTimeEvent TimeRequired. Finite number.
resetTimeReset TimeRequired. Finite number.
equalityInNewPeriodEquality In New PeriodRequired. Boolean.
Output fieldInterpretationReturned shape
newPeriodNew PeriodRequired. Boolean.
json
{
  "input": {
    "eventTime": 100,
    "resetTime": 100,
    "equalityInNewPeriod": true
  },
  "output": {
    "newPeriod": true
  }
}

Limitations and assumptions

  • The reset boundary is supplied; no counter, timezone, recurrence or actual frequency cap is applied.
  • 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

  1. Calculation and input contract: advertising/ad-frequency-reset-boundary-token — tool.io

Similar or alternative tools

  • Frequency Cap Window Offset

    Divide their exact integer difference using floor semantics, returning numeric window index and a nonnegative offset below windowLength.

  • Coupon Attribution Last Day Flag

    Compare conversion<=expiry or conversion<expiry according to inclusive, and preserve the source label.