SaaS Product Events (JSON)
Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. JSON twin.
[
{
"event_id": "evt_0001",
"ts": "2026-01-10T09:00:00Z",
"user_id": "usr_001",
"event": "signup",
"plan": "free",
"properties": "{\"source\": \"sample\", \"i\": 0}"
},
{
"event_id": "evt_0002",
"ts": "2026-01-10T09:17:00Z",
"user_id": "usr_002",
"event": "login",
"plan": "pro",
"properties": "{\"source\": \"sample\", \"i\": 1}"
},
{
"event_id": "evt_0003",
"ts": "2026-01-10T09:34:00Z",
"user_id": "usr_003",
"event": "feature_used",
"plan": "team",
"properties": "{\"source\": \"sample\", \"i\": 2}"
},
{
"event_id": "evt_0004",
"ts": "2026-01-10T09:51:00Z",
"user_id": "usr_004",
"event": "upgrade",
"plan": "free",
"properties": "{\"source\": \"sample\", \"i\": 3}"
},
{
"event_id": "evt_0005",
"ts": "2026-01-10T10:08:00Z",
"user_id": "usr_005",
"event": "cancel",
"plan": "pro",
"properties": "{\"source\": \"sample\", \"i\": 4}"
},
{
"event_id": "evt_0006",
"ts": "2026-01-10T10:25:00Z",
"user_id": "usr_006",
"event": "invite_sent",
"plan": "team",
"properties": "{\"source\": \"sample\", \"i\": 5}"
},
{Specifications
- Records
- 24
- Schema
- event_id, ts, user_id, event, plan, properties
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“SaaS Product Events (JSON)” is a deterministic Novus Examples fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: 24 records · schema: event_id, ts, user_id, event, plan, properties. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks — delimiters, encodings, null handling, schema, and row counts — in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import json
with open("product-events.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonColumnar Nulls Schema (JSON)JSON description of nullable columns in the null-heavy columnar fixtures.

- jsonFINANCE — Ledger Lines (JSON)JSON twin of the finance/ledger-lines mini-dataset.

- jsonFintech Double-entry Ledger (JSON)Balanced double-entry ledger SAMPLE for accounting engine validation tests.

- jsonFlat JSON ArrayA flat JSON array of ten simple objects — the baseline case for JSON parsing and mapping.

- jsonHealthcare Claim (FHIR SAMPLE JSON)Synthetic FHIR Claim resource for healthcare billing parser tests — not a real patient.

- jsonHealthcare Procedure Codes (JSON)SAMPLE procedure code list with fees for medical billing calculator tests.

Generated by generation/data_domains_wave_c.py. Free for any use, no attribution required — license.