Test your tracking without placing real orders

Placing test orders pollutes your data and still misses server-side events. How to verify browser and server tracking on a WordPress site, layer by layer.

Last updated ·

The problem

The naive way to verify ecommerce tracking is to buy something from your own store. It works once, badly: the test order lands in your revenue data, the refund follows it, payment fees stick, and you still have not tested the paths that matter most, like what fires for a visitor who declines consent, or whether your server-side events reach the container.

Testing tracking is a layered problem, because tracking is layered: events are born in the browser’s data layer, travel through your GTM container, and, on a server-side setup, also arrive at your sGTM container without a browser involved. Each layer needs its own check.

Layer 1: the browser data layer

GTM’s Preview mode (Tag Assistant) is the baseline and it is free: connect your site, click through it, and watch events, triggers and tags fire. Use it to confirm an event exists and its tags fire at the right moment.

Preview mode’s limitation is context: it runs in its own connected session, and walking a full flow while cross-referencing every push gets slow.

GTM Kit Premium adds an Event Inspector: a live overlay on your actual site listing every data layer push as it happens, with the full payload, persisted across page navigation for the session. You browse your store normally, on the pages your customers see, and watch view_item, add_to_cart and begin_checkout appear with their exact parameters. It loads only for site administrators (or when WP_DEBUG is on), so normal visitors never see it or load its script.

Layer 2: the server side

Server-side events are the hard case. A purchase webhook fires from your server to your sGTM container; there is no browser to open Preview in, and GA4’s DebugView does not reliably list purely server-originated events. Verify them in the sGTM container’s own Preview panel and in GA4 Realtime instead.

Getting a test event into that Preview panel normally requires a real order. GTM Kit Premium removes that requirement with Send test webhook to sGTM Preview (Setup → Environment): send a server-side event to your container with the Preview token attached, so it shows up in the Preview/Debug panel on demand. Pick the event type, send a synthetic sample or replay a real past order, and read the container’s response inline. An optional, self-expiring developer toggle can also surface live orders in Preview while you debug; it disarms itself when the token expires, so it cannot be left on by accident.

A practical checklist

  1. GTM Preview: core events fire once, at the right moment, with the parameters you expect.
  2. Event Inspector (Premium): walk the full purchase path on the real site and read every push in place.
  3. sGTM Preview test send (Premium): confirm webhook events reach the server container and your server tags accept them, without touching production data.
  4. GA4 Realtime: confirm the events land in the property.
  5. Repeat the browser checks in a private window with consent declined, and confirm what fires matches your consent setup.

Run a Tracking Health Check for an outside-in view of what your site actually sends.

← Previous

Previous article

Next →

Next article