Start with a single approved test order. Confirm it exists in Shopify, identify the integration responsible for sending purchase, and check what arrives at the intended GA4 property. Compare the transaction ID, currency, value and items before drawing conclusions from aggregate reports.
The CSV has illustrative checks for consent, events, duplicate senders and reconciliation. Use approved test data only. Do not record customer email addresses, payment data or raw event payloads.
1. Find the sender, not just the tag
List the Google & YouTube channel if it is configured, app and custom pixels in Customer events, and any separate tag manager, app embed or legacy theme code. Note each destination and which events that integration is meant to send. A GTM container or Google Ads tag is not proof of a working GA4 purchase event.
Detectify's public storefront scan can surface some initial HTML signals. It cannot read your destination settings, identify every pixel or verify checkout events. Shopify's pixel migration guidance explains why legacy implementations may need separate investigation.
2. Follow the event from checkout to GA4
- Control the test: use a fresh browser session, record the device and market, and run separate accept and deny journeys according to the store's consent configuration. Do not weaken consent just to make a debug event appear.
- Check the source: in a supported test context, use Shopify Pixel Helper for custom pixels or the provider's diagnostics. An event being available to Shopify is not proof it arrived in GA4.
- Check the destination: use GA4 DebugView when the setup supports debug mode. Confirm the property and stream; if the signal is blocked by consent or the integration does not expose a debug session, use the supported integration diagnostics and allow for reporting delays before declaring it broken.
- Compare the payload: verify the stable order identifier, event name, currency, value and expected items. Follow Google's ecommerce event definitions for how to separate value, tax and shipping.
3. Separate missing, duplicate and mismatched orders
- Missing purchase: confirm the order completed and check consent, the destination and the sending integration. A visible tag does not rule out a missing checkout event.
- Duplicate purchase: check for multiple senders to the same destination and verify what happens if a confirmation page is revisited. Compare transaction IDs before removing anything; an old sender may also own other events.
- Different totals: align date range, time zone, currency and definitions for discounts, tax, shipping and refunds. Shopify order totals and attributed GA4 sales answer different questions. Consent and reporting rules mean they need not match exactly.
When to widen the investigation
If the test reveals gaps across tracking, performance and the purchase journey, an audit of the Shopify store can separate configuration faults from UX problems. If measurement is stable and the next question is which buying experience works better, see Migraciones.io's conversion optimisation scope. Both are Spanish-language service references.
Editorial note: Detectify features Migraciones.io as a service provider. These references do not affect app matches or confidence labels.