Subscriber Sunset
Measure subscriber access sunset timing against a supplied allowance.
Description
A subscriber sunset interval counts whole UTC days between cancellation and the end of access.
A subscriber sunset interval counts whole UTC days between cancellation and the end of access. The caller supplies the maximum allowed continuation interval.1
Measure subscriber access sunset timing against a supplied allowance.
When to use Subscriber Sunset
Use this tool to measure subscriber access sunset timing against a supplied allowance.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Subscriber Sunset and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter cancellationDate, accessEndDate, allowedSunsetDays using the field table and calculation rules, then run the tool.
- Read sunsetDays, daysBeyondAllowance, withinAllowance. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| cancellationDate | Subscription cancellation date | string | Required |
| accessEndDate | Access end date | string | Required |
| allowedSunsetDays | Allowed sunset duration (days) | integer; minimum: 0 | Required |
Enter YYYY-MM-DD strings and a nonnegative integer maximum. Parse UTC midnight, reject invalid parse results and reversed chronology, then return days, excess and inclusive within-limit flag.
days=floor((accessEnd−cancellation)/86,400,000); excess=max(0,days−maximum) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| sunsetDays | Access sunset duration (days) | integer; minimum: 0 |
| daysBeyondAllowance | Days beyond allowance (days) | integer; minimum: 0 |
| withinAllowance | Within supplied allowance | boolean |
{
"input": {
"cancellationDate": "2025-01-01",
"accessEndDate": "2025-01-31",
"allowedSunsetDays": 30
},
"output": {
"sunsetDays": 30,
"daysBeyondAllowance": 0,
"withinAllowance": true
}
} Limitations and assumptions
Native date parsing can normalize some out-of-range calendar dates. No engagement is detected and no subscription is ended.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Live-Blog Staleness: Measure live-blog update age against a supplied staleness threshold. For a complementary task, use Open-Rate Inflation: Adjust reported email opens for estimated machine-generated opens.
References
-
Subscriber Sunset — tool.io
Similar or alternative tools
- Live-Blog Staleness
Measure live-blog update age against a supplied staleness threshold.
- Open-Rate Inflation
Adjust reported email opens for estimated machine-generated opens.