Do subscriber event sequences improve 30-, 60- and 90-day churn forecasts compared with a single account snapshot?

Do subscriber event sequences improve 30-, 60- and 90-day churn forecasts compared with a single account snapshot?

The study calls for Dated subscription events, usage and plan histories, confirmed termination dates and observation end dates and matched cohorts.. The measure to examine is to confirm: an observable measure for this question.

This custom study is prepared to order. Choose the city, date range, population and required records; the accepted order defines the final study scope.

Onboarded city options

Nairobi (Kenya)

Custom city requests

African Major Cities · Additional cities require availability, scope and quote confirmation.

Data type

Synthetic

Priced domains

Telecommunications, Demographics

Catalogue structure

Question-specific research data

Key features

Record concepts for your order-specific extract.

Who it is for

• ML engineers
• data scientists
• research teams
• analysts

Proposed study unit

Study unit to define

Planned records and relationships for this study.

Record concepts for your extract

• Dated subscription events
• usage and plan histories
• confirmed termination dates
• observation end dates and matched cohorts.

The agreed specification defines the final columns, keys, relationships and observation period for your order.

Agree a comparable cohort, baseline or held-out scoring protocol.

Proposed questions for your custom order

1. Do subscriber event sequences improve 30-, 60- and 90-day churn forecasts compared with a single account snapshot?

Proposed research and analytical applications

• Prediction prototyping
• feature exploration
• temporal validation

Study and modeling guidance

Information available at prediction or evaluation time

Use evidence valid and available at the agreed as-of date; later information cannot be a past-time feature.

Comparison and evaluation

Agree a comparable cohort, baseline or held-out scoring protocol.

Incomplete observation

Retain unknown outcomes, incomplete observation and censoring.

Data generation

FCTE synthetic city engine

Data classification

Synthetic

FCTE generation methods and published city/domain checks provide source context. The order defines the final extract and the release-specific checks, documentation and limitations supplied with it.

Known limitations

• Define confirmed termination separately from inactivity or suspension, and use only events recorded before the prediction date.
• No verified paid-release schema or benchmark artifacts are established by catalogue association.
• Synthetic records describe generated scenarios; they do not establish observed population prevalence or real-world causal effects.

Catalogue base price

$599 USD

Price basis

Base price per selected city

Availability

Prepared after order

The displayed catalogue amount is a base price per selected city. Your requested dates, population, fields, formats and usage rights determine the agreed scope and final quote. Applicable published discounts and taxes are confirmed with that quote.

Your prepared package

Your order confirms the data files, documentation, evidence, examples and release controls included in the prepared package.

• Agreed data extract
• Schema and field documentation
• Release-specific evidence and limitations
• Agreed loading or analysis examples
• Licence, manifest, checksums and delivery note

SD_RESEARCH_DATASET/
├── data/
│   ├── telecommunications_records.parquet
│   └── citizens.parquet
├── tasks/
│   ├── task_definition.yaml
│   ├── train.parquet
│   ├── validation.parquet
│   └── test.parquet
├── evaluation/
│   ├── baseline_model.py
│   ├── metrics.json
│   └── example_notebook.ipynb
├── documentation/
│   ├── README.md
│   ├── DATA_DICTIONARY.csv
│   ├── SCHEMA.md
│   └── METHODOLOGY.md
├── evidence/
│   ├── CERTIFICATION.json
│   ├── VALIDATION_REPORT.pdf
│   └── KNOWN_LIMITATIONS.md
├── MANIFEST.json
├── CHECKSUMS.sha256
└── LICENSE.pdf

Delivery process

Confirm the cities, date range, records, formats, rights and price in writing. The order-specific extract is then prepared and supplied under the agreed payment and delivery conditions.

One secure download package for the agreed release and licensed entity.

Delivery timing, access expiry, formats and prerequisites are confirmed in the accepted order.

Support, refreshes, future releases, hosting and APIs are included only when expressly ordered.

Data Licensing Agreement · 2026-10

A non-exclusive, non-transferable licence for the named customer within the accepted scope and duration.

Permitted use

Internal research, development, testing and analytics within the accepted order.

Model training

Model training, external applications, commercial distribution and access by other legal entities must be expressly addressed in the order.

Redistribution

Raw or substantially reconstructable data cannot be resold, published or redistributed without separate written authorization.

Attribution

Preserve release provenance and applicable third-party notices. Published outputs must identify the data as synthetic.