JDGMNT / PURCHASE EVENT AUDIT CARD
Version 1 · 24 October 2026

Use approved test orders and your own authorized systems. Keep unnecessary
customer and payment information out of this record.

01 / EXPECTED EVENT
Store / site and integration:
Event name:
Action that should trigger it:
Action that should not trigger it:
Expected value, currency, and value definition:
Time zone:
Consent and data-sharing settings to verify:
Owner:

02 / TRACE ONE TEST ORDER
Non-sensitive test reference:
Store record confirms the order:
Browser event observed, if applicable:
Server event observed, if applicable:
Event name, value, and currency agree with the definition:
Repeated page visits do not create unintended new purchases:
Browser/server deduplication checked against current integration guidance:
Cancellation/refund behavior understood:
Evidence location:

03 / COMPARE REPORTS
Store report definition and period:
Analytics definition and period:
Advertising report definition and attribution window:
Expected reasons for differences:
Unexpected discrepancy:
Responsible system or integration:

04 / REPAIR & RECHECK
Specific change:
Date and version:
Follow-up test:
Remaining limitations:
Who confirms resolution?

Do not force reports with different definitions to match. An event appearing
in an advertising report does not by itself prove that advertising caused it.
This worksheet is not an API specification. Use the current documentation for
your exact platform and integration before changing event implementation.

You may use and adapt this worksheet, including commercially. Attribution to
JDGMNT is appreciated. It is a practical audit aid, not a certification.