Skip to content

Main content

Cohort Revival Period Base Flag Tool

Calculate cohort revival period base flag from explicit caller-supplied inputs.

Loading tool…

Description

Return retention share with an optional revived-customer base.

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.

Return retention share with an optional revived-customer base.

When to use this tool

Use Cohort Revival Period Base Flag when checking the stated business timing or cohort convention.

How to use the tool and how it works

  1. Enter activeBefore, revived, retained, includeRevived. 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 denominator, retainedShare. Use the output convention below.

Return retention share with an optional revived-customer base. Require whole activeBefore >= 1, revived >= 0 and retained in [0,activeBefore]; denominator = activeBefore+(includeRevived ? revived : 0), retainedShare = retained/denominator.1

Input fieldMeaning and unitsAccepted input
activeBeforeActive BeforeRequired. Safe integer; minimum 1.
revivedRevivedRequired. Safe integer; minimum 0.
retainedRetainedRequired. Safe integer; minimum 0.
includeRevivedInclude RevivedRequired. Boolean.
Output fieldInterpretationReturned shape
denominatorDenominatorRequired. Safe integer.
retainedShareRetained Share Unit: 1.Required. Finite number.
json
{
  "input": {
    "activeBefore": 100,
    "revived": 20,
    "retained": 80,
    "includeRevived": false
  },
  "output": {
    "denominator": 100,
    "retainedShare": 0.8
  }
}

Limitations and assumptions

  • Revived records enter only the selected denominator, not the retained numerator; actual cohort membership and reactivation policy are supplied.
  • 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/cohort-revival-period-base-flag — tool.io

Similar or alternative tools