Description
Validate year/month components, compute (observationYear - cohortYear) × 12 + observationMonth - cohortMonth, and require a nonnegative result.
Marketing records combine campaign dates, labels, attribution terms, and supplied counts. A local arithmetic or formatting result describes the stated record without proving campaign effectiveness or causal impact.
Validate year/month components, compute (observationYear - cohortYear) × 12 + observationMonth - cohortMonth, and require a nonnegative result.
When to use this tool
Use Customer Cohort Age Index when you need one campaign-record calculation or formatter under the stated convention.
How to use the tool and how it works
- Enter cohortYear, cohortMonth, observationYear, observationMonth. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read ageMonths. Use the output convention below.
Validate year/month components, compute (observationYear - cohortYear) × 12 + observationMonth - cohortMonth, and require a nonnegative result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| cohortYear | Cohort Year | Required. Safe integer; minimum 1; maximum 9999. |
| cohortMonth | Cohort Month | Required. Safe integer; minimum 1; maximum 12. |
| observationYear | Observation Year | Required. Safe integer; minimum 1; maximum 9999. |
| observationMonth | Observation Month | Required. Safe integer; minimum 1; maximum 12. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ageMonths | Age Months | Required. Safe integer. |
{
"input": {
"cohortYear": 2025,
"cohortMonth": 11,
"observationYear": 2026,
"observationMonth": 2
},
"output": {
"ageMonths": 3
}
} Limitations and assumptions
- This counts calendar-month labels rather than elapsed days, completed months from a day-of-month, or verified cohort membership.
- 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
Review the complete measurement model, source data, and campaign terms before interpreting a performance result.
References
Similar or alternative tools
- Customer Repeat Purchase Gap
Parse previousDate and repeatDate as real Gregorian dates, require repeat no earlier, and return the day difference.
- Visitor Day Over Night Label
Parse real YYYY-MM-DD arrival and departure dates at UTC midnight, require departure no earlier, and divide their difference by 86400000 for nightCount.