Map the purchase flow
List every system that can emit a purchase event: store apps, theme code, tag manager and server integrations. Record their triggers. A second integration may repeat the same order instead of filling a gap.
Check the identifiers
For paired browser and server events, review the platform-specific deduplication setup and identifiers. Inspect the event name, time, value and currency. Use the platform documentation for the integration being used.
Run a controlled check
Complete a permitted test order and follow it through the store and event tools. Compare the order record with what was received. Keep a clear distinction between test traffic and real performance.
Document the final setup
Record which integrations remain active and who owns them. Keep the event map with the account documentation. Recheck after theme, checkout, app or server changes.