METHODOLOGY

What the data can tell you, and what it cannot.

A practical guide to structure, coverage, estimates and responsible use of the D2C Radar database.

How the file is structured

Each row represents a candidate ecommerce business record. The file has 42 named fields spanning store identity, platform, category, geography, estimated commercial signals and detected technologies.

The product count of 268,950 reflects India-coded records in the current source. Field coverage is not uniform, so blank values should be expected in narrower attributes.

Field coverage in the profiled source
Store domain2,69,383 (100%)
Platform2,68,955 (99.8%)
Category2,11,703 (78.6%)
Technology signals2,00,327 (74.4%)
Revenue estimate2,63,443 (97.8%)
Traffic estimate98,850 (36.7%)
State92,454 (34.3%)
City87,389 (32.4%)

Estimated fields

Revenue and traffic values are directional estimates, not audited financial statements or analytics exports. Use them to prioritize research, then verify important claims.

Platform and technology labels

These are source classifications and detections. A label may become outdated as a store changes its stack.

Category and location

Categories, states and cities are available only where the source could classify them. They should not be treated as complete market counts.

Versioning

A purchase provides the database version available at checkout. It is a one-time file purchase, not an automatically updating subscription.

Responsible use

Use the data for legitimate business research, segmentation and relevant outreach. Verify records before acting, respect applicable laws and platform terms, and provide a clear way for recipients to opt out of communications.

Want to inspect the format first? Download the redacted sample.