Compare CSV and JSON without conflating their representations — what should the operator record?
CSV flattens values into cells, while JSON may preserve nested structures and explicit nulls. A raw text comparison will overstate differences and miss semantic mistakes. Define a shared projection from authorized records, then reconcile that projection rather than claiming the two files should look identical in every detail.
Check semantic parity across two export formats while preserving type and null distinctions.
Select fields both outputs actually carry, such as context-qualified identifier, original link and publication timestamp, excluding format-specific envelope metadata. A shared projection might omit nested comments while preserving source_key and link; describe that omission before calling the comparison a parity check of those fields.
State which fields reconciled and which could not be compared; never describe omitted nested evidence as proven equivalent just because identifiers match. A useful outcome is identifiers-and-links reconciled, nested fields untested, rather than a blanket all-data-equivalent statement that exceeds the actual projection checked.Choose the shared projection
Select fields both outputs actually carry, such as context-qualified identifier, original link and publication timestamp, excluding format-specific envelope metadata. A shared projection might omit nested comments while preserving source_key and link; describe that omission before calling the comparison a parity check of those fields.
Describe flattening rules
Write how arrays, nulls and nested objects are represented in the CSV; if undocumented, flag ambiguity instead of inventing an equivalence. An array serialized into one CSV cell is not equivalent to an array expanded into several rows; choose one explicit comparison grain for the check.
Normalize only for comparison
Create a typed comparison view that preserves raw values and records every conversion, especially string identifiers that resemble numbers. Keep the original column strings when testing conversions, especially timestamps and large numeric-looking identifiers that a spreadsheet may alter before comparison begins.
Inspect semantic mismatches
Separate genuine membership differences from quoting or column-order changes, checking a representative conflicting row against the original receipt. When one file is a later export, differing visibility states may explain membership changes; parity requires compatible authorized scope and observation context, not just matching filenames.
Deliver a parity statement
State which fields reconciled and which could not be compared; never describe omitted nested evidence as proven equivalent just because identifiers match. A useful outcome is identifiers-and-links reconciled, nested fields untested, rather than a blanket all-data-equivalent statement that exceeds the actual projection checked.
Keep the boundaries clear.
- Check semantic parity across two export formats while preserving type and null distinctions.
- Operational record: Choose the shared projection. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.