Testing storefront events

Test events is the check for whoever installs the storefront tracking. A test code isolates your own browsing: everything you do with it is validated and shown live, and never written into your real data. The live feed shows everything Nucleo received in the last 30 minutes.

You find it in Catalog > Shoppers > Test events. Only Owners and Admins can create codes and send test events; Editors can watch the feed.

Create a test code

Steps

In Nucleo, go to Catalog > Shoppers > Test events.
In Test code, click New code. A six-character code appears, with how many minutes it's still valid.
Copy the Storefront URL with the test code, or add ?nucleo_test= followed by the code to any page of your storefront.
Open the URL, accept the cookie banner, and browse: view products, search, add to cart.

The code stays for the whole browser session. Your events appear in the Live feed below within seconds.

Note

There's one code per catalog, valid for one hour. A new code replaces the previous one at once.

Send a test event

To check the pipeline without opening your storefront, click Send a test event. Nucleo sends a sample batch (a page view, a product view, a search and an add to cart) through the pipeline in test mode. Nothing is written; you see it arrive in the feed. If there's no active code, one is created.

Watch the live feed

The Live feed shows the latest events received in the last 30 minutes, newest first: where each came from, what it was, and what happened to it.

Filter by source: All, Browser, Web Pixel, Server or Consent. Each shows its count for the last 30 minutes.
Turn on Only my test code to see only your own browsing. It's available while a code is active.
Click Pause to freeze the feed, and Resume to continue. The badge reads Live, Paused or Stopped.
Click a row to see the data that came with the event.

Each row says what happened to the event: stored, processed, rejected, discarded or failed, often with the reason. Rows with your code read dry-run · not written, and withheld: looked like personal data means the event was kept without its words. Badges such as identified, unmapped or cart refused flag what to look at.

Revoke a test code

In Test code, click Revoke, and then click Revoke to confirm. Batches still carrying the code stay in test mode, so nothing reaches your real data. You can create a new code at any time.

Considerations for test events

Events carrying a test code are never written into your real data, even after the code expires.
If your own browsing doesn't appear, check the installation's Allowed domains and status in Event tracking, and that you granted consent on the storefront.
Once events flow, check the result in Signal.