Skip to content
Novus Examples
json2.3 KB

Marketing Attribution (JSON)

Synthetic multi-touch attribution click rows with UTM fields — for marketing analytics importers. JSON twin.

Preview — first 50 linesjson
[
  {
    "click_id": "clk_0001",
    "ts": "2026-01-10T09:00:00Z",
    "campaign": "spring_sale",
    "channel": "paid_search",
    "utm_source": "google",
    "utm_medium": "cpc",
    "conversions": 0,
    "revenue": 0.0
  },
  {
    "click_id": "clk_0002",
    "ts": "2026-01-10T12:00:00Z",
    "campaign": "spring_sale",
    "channel": "social",
    "utm_source": "meta",
    "utm_medium": "paid",
    "conversions": 1,
    "revenue": 29.5
  },
  {
    "click_id": "clk_0003",
    "ts": "2026-01-10T15:00:00Z",
    "campaign": "brand_always",
    "channel": "organic",
    "utm_source": "bing",
    "utm_medium": "organic",
    "conversions": 2,
    "revenue": 59.0
  },
  {
    "click_id": "clk_0004",
    "ts": "2026-01-10T18:00:00Z",
    "campaign": "newsletter",
    "channel": "email",
    "utm_source": "braze",
    "utm_medium": "email",
    "conversions": 3,
    "revenue": 88.5
  },
  {
    "click_id": "clk_0005",
    "ts": "2026-01-10T21:00:00Z",
    "campaign": "partner",
    "channel": "referral",
    "utm_source": "partner",
    "utm_medium": "affiliate",
    "conversions": 0,
    "revenue": 0.0
103 lines total — download for the full file.

Specifications

Records
10
Schema
click_id, ts, campaign, channel, utm_source, utm_medium, conversions, revenue

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

“Marketing Attribution (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: 10 records · schema: click_id, ts, campaign, channel, utm_source, utm_medium, conversions, revenue. 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("attribution.json") as f:
    data = json.load(f)
print(type(data), len(data))

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