Skip to content

Main content

Active User Period Boundary Pair Tool

Calculate active user period boundary pair from explicit caller-supplied inputs.

Loading tool…

Description

Check an active-user event against a supplied interval.

Business timing and cohort summaries depend on event origins, bucket boundaries and the treatment of incomplete records. A time difference or bucket label is a supplied record convention rather than proof of customer behavior, completed service or future retention.

Check an active-user event against a supplied interval.

When to use this tool

Use Active User Period Boundary Pair when checking the stated business timing or cohort convention.

How to use the tool and how it works

  1. Enter eventTime, start, end, includeEnd. 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 included, offset. Inspect included before interpreting the associated values.

Check an active-user event against a supplied interval. Require end >= start; included is start-inclusive and end-inclusive only when includeEnd, offset = eventTime-start.1

Input fieldMeaning and unitsAccepted input
eventTimeEvent TimeRequired. Finite number.
startStartRequired. Finite number.
endEndRequired. Finite number.
includeEndInclude EndRequired. Boolean.
Output fieldInterpretationReturned shape
includedIncludedRequired. Boolean.
offsetOffsetRequired. Finite number.
json
{
  "input": {
    "eventTime": 20,
    "start": 10,
    "end": 20,
    "includeEnd": false
  },
  "output": {
    "included": false,
    "offset": 10
  }
}

Limitations and assumptions

  • No actual event, time-zone/calendar rule or deduplicated user-activity definition is validated.
  • 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

Use complete event records and a defined cohort/period policy; evaluate commercial performance and uncertainty with appropriate complete analyses.

References

  1. Calculation and input contract: business-analytics/active-user-period-boundary-pair — tool.io

Similar or alternative tools