Verify events and installation
Check a visit, a custom event, and consent scenarios.
Check the published website before using its data to assess campaigns or conversions.
Check a visit
- Open Setup → Pixels → Pixel → Events and make sure
page_viewis configured. - Open Installation & test → Live verification and keep the dashboard open.
- Open the published website in another tab.
- Make a choice in the banner connected to CJM. Accept statistics for this test.
- Check the event and timestamp in the dashboard. New Pixels start with
page_view; re-enabling the toggle can name it Page Load.
The real-time list shows up to 25 new events for the test session. With multiple Pixels, use a recognizable test name and check its trigger: name and timestamp alone do not conclusively identify the Pixel being tested.
Check a manual call
After the Pixel loads, your developer can run this in the browser console:
window.CJMPixel.track('cjm_installation_test', { test: true });Look for cjm_installation_test. This is a real event; use a test project when available. For ecommerce and leads, also verify data against the corresponding guide. Seeing an event name does not validate amounts or contacts.
Repeat these scenarios
| Test | Expected result |
|---|---|
| Visit with statistics consent | Event sent to CJM; session available, persistent visitor identity only with advertising storage consent. |
| All signals denied | Anonymous counts replace ordinary events; no browser forwarding to Meta/GTM. |
| No banner answer | After about three seconds, or on leaving, queued events become anonymous counts. |
| Explicit form submission | trackLead can send the contact even with cookies refused. |
| New path or query without a reload | New page lifecycle for configured events. |
| Same path and query, or hash-only change | No new virtual page. |
Troubleshooting
| Problem | Check |
|---|---|
CJMPixel undefined | Check publishing, script download, and call order. |
| No events | Check the full key, active event, connected banner, and correct website. |
| Connection unavailable | Restore the dashboard's real-time connection and repeat the test. This alone does not prove a Pixel issue. |
| Configuration does not load | Inspect /config/…, its response, and network blocking in developer tools. |
| Request rejected | Check the key, authorized domain/origin, and data shape. Do not substitute localhost for an authorized website without suitable test configuration. |
| Click event missing | Check the selector and whether the element exists when tracking is configured. |
| Changes not visible | Save in the dashboard and reload the website. An open page does not continuously refresh configuration. |
| Duplicate events | Check for double installation, overlapping DOM rules, HTML attributes plus DOM rules, or repeated manual calls. |
| Lead without answers | Check form_responses: [] does not create an answers record. |
Web Vitals, errors, and anonymous counts use different channels. Do not expect all of them in this list. See Additional signals.