Description
Partition a supplied unique cohort into retained, reactivated and inactive IDs.
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.
Partition a supplied unique cohort into retained, reactivated and inactive IDs.
When to use this tool
Use Cohort Retention Reactivation Boundary when checking the stated business timing or cohort convention.
How to use the tool and how it works
- Enter cohort, priorActive, currentActive. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read retained, reactivated, inactive. Use the output convention below.
Partition a supplied unique cohort into retained, reactivated and inactive IDs. Retained requires prior and current activity, reactivated requires current but not prior, inactive means absent from current; preserve cohort order.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| cohort | Cohort | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| priorActive | Prior Active | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| currentActive | Current Active | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| retained | Retained | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| reactivated | Reactivated | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| inactive | Inactive | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
{
"input": {
"cohort": [
"A",
"B",
"C"
],
"priorActive": [
"A",
"B"
],
"currentActive": [
"B",
"C"
]
},
"output": {
"retained": [
"B"
],
"reactivated": [
"C"
],
"inactive": [
"A"
]
}
}Limitations and assumptions
- Activity lists are caller assertions; no actual customer identity, commercial churn definition or causal behavior is inferred.
- 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.
Alternative or Complementary methods
Use complete event records and a defined cohort/period policy; evaluate commercial performance and uncertainty with appropriate complete analyses.
References
Similar or alternative tools
- Cohort Retention Denominator Delta
Compare retention rates after a denominator revision.
- Cohort Revival Period Base Flag
Return retention share with an optional revived-customer base.