Check website events

Inspect outgoing events detected by the browser and compare them with events received in CJM.

The Events tab helps you understand whether an action generates an outgoing request from the website. You can use it without signing in, but the website needs the Pixel installed and the action configured.

Run a test

Open the published website with the extension installed and reload the page.
Open the extension panel. For a clear test, use one website tab and avoid other pages generating CJM events.
Make a choice in the cookie banner connected to CJM. Accept statistics to test an ordinary page view.
Perform the action outside selection mode, such as the click configured as richiesta_demo_click.
Open Events and use Filter by name or trigger… to find it. Newest events appear first.
Open the event card to check its name, trigger, time, and available data.
In the dashboard, open Setup → Pixels → Pixel → Installation & test → Live verification. Leave the list open, repeat the website action, and check that the event arrives there too.

The dashboard list receives events from the whole project. If there are several Pixels, use a recognizable test name and follow the Pixel verification guide.

Understand what you see

Indicator	What it confirms
Green dot at the top or Pixel CJM rilevato banner	The extension recognized the Pixel's presence or an outgoing request. This alone does not prove the server accepted the data.
Event in Events	An outgoing request attempt was detected on the page. The extension does not check the server response.
Receiving events on the Pixel card in Change context	This is the state read from CJM for the selected Pixel, alongside First event and Last event. It does not confirm each row in the local list.
Event in Live verification	CJM received an event visible in the project's list. This does not prove forwarding to Meta or Google.

Details can include the page title, visitor or session identifiers, and action-specific data. Fields depend on the event and consent. Show raw JSON opens the complete detected structure, useful when your website developer needs to investigate a technical problem.

Local list limitations

The extension observes recognized ordinary Pixel requests, including ecommerce events sent through that channel. Contact submissions through trackLead, errors, aggregate site quality measurements, and anonymous counts use different channels and do not appear in this list. Absence here does not rule out receipt in CJM.
Events with the same name and trigger within about two seconds can be collapsed in the display, even if they come from different actions. Leave more than two seconds between identical tests.
The icon's number is a local count, not total conversions. Do not use the list as an archive: reopening retrieves at most 100 recent events per tab, and a new page load resets the collection kept for that tab.
A panel left open can retain earlier rows or receive events from other tabs: the Pixel selection does not filter this stream. After changing pages, close and reopen the panel on the tab you want to test.
Requests inside iframe content are not observed by this version of the extension.

Use the Catalog

Open Catalog and expand a group or Triggers to read descriptions. The seen label compares the entry's name with those in the local event list.

The catalog is a reference: a listed entry does not mean that event is enabled on your website. An event with your own name can appear in Events without a matching catalog entry.

If you cannot find the event

Check that you are on the correct website and the Pixel is published.
Reload the website after installing or updating the extension and after changing events.
Check that the rule is saved and the cookie banner passes the visitor's choice.
Finish element selection before repeating the action.
Reopen the panel and remove any search filters.
Check the dashboard. If the event appears only in the extension, ask your website developer to check the outgoing request and server response.