Your workflow ran. Did the right values arrive?
A green run and a matching receipt cannot tell you if a phone field was mapped from the wrong column. Compare source and destination CSV snapshots by an explicit key, spot suspicious value differences, and record exactly what still requires human review.
Use the fictional example first. Only use properly authorized, pseudonymous snapshots without customer names, contact details or credentials. The page performs no server upload, but browser extensions can still access form content. A value difference is not proof of which system is wrong; matching values do not establish a correct business outcome.
Compare two snapshots, not two guesses
Source and destination may have different column names. Put an explicit correlation key in each, then map one to eight field pairs. All calculations and file reads stay in this browser. Use no real identifying contact data in examples.
Example header: event_id,phone,segment
UTF-8, maximum 100 KB, 500 rows. Never uploaded.
Example header: event_id,phone,segment
A row is an observation, not verified final CRM state.
Must exist in the source snapshot.
Key matching and export-window alignment remain your responsibility.
Format: source_field,destination_field (no heading, maximum eight pairs). For example: phone,phone
Try the fictional case. Results are never a customer sign-off.
What this block can contribute
The result uses moruneva.field-mapping-evidence.v1 and can be consumed by other Moruneva tools or authorized local software. It reports row counts, missing-key groups, ambiguous duplicate keys and unequal or missing values per numbered field pair. It intentionally excludes raw IDs, field names and values from the exported report.
Neither this block nor the Acceptance vs Observation Workbench can read Shopify, n8n, a CRM or a client's consent status. Use the Outcome Reconciler to inspect event/receipt existence, and this checker only for supplied value comparisons. They are complementary, not independent proof of final outcomes.
A native alternative may be better
For a single one-off comparison, a spreadsheet or a source/destination validation inside n8n may be quicker. n8n's execution history and Shopify's delivery troubleshooting remain important authoritative starting points. This page is for comparing two already authorized exports, not replacing access-controlled logs or changing customer records.
Worked guide: a green run with wrong CRM fields → · Privacy and limits → · Share voluntary feedback →