Overview

The Pulse Status section in the Netcore Unbxd Console lets you monitor the health of your Pulse analytics for a site. It shows how many events Pulse captures, how those events move through the shopper journey, how well they are attributed to a source, and where tracking errors occur.

Pulse Status is built for the period when a site is moving from the legacy analytics integration (V1) to the new Pulse integration (V2). It places both versions side by side over the same date range, so you can confirm that V2 is tracking correctly before V1 is retired.

ℹ️

Pulse Status vs. Analytics Health

The same data is presented in two ways depending on what is running for your site:

• Pulse Status shows both V1 and V2 together, so you can compare the two integrations during migration.
• Analytics Health shows only V1 or only V2, depending on the Pulse toggle for the site. Use this view once a single version is active.

The panels, controls, and columns described in this guide apply to both. The only difference is whether one version or two are displayed.

Key Capabilities

• Track total event volume and the breakdown by event type (Click, Cart, Order) for each version.
• Validate the conversion funnel from Hits to Click to Cart to Order, and see how V2 compares to V1 at each stage.
• Check attribution coverage across sources (Search, Browse, Experience) and confirm that unattributed events are decreasing.
• Surface tracking errors by type and by day, so issues can be debugged before they affect AI personalisation.

• Navigate to Pulse Status

1. Log in to the Netcore Unbxd Console.
2. Go to Manage for the site you want to check.
3. Select the Pulse Status tab. It sits alongside Site Details, Feed Settings, Site Settings, and Algorithms.

Page Controls

The following controls are available at the top of the page and apply to whichever view is open.

Graph View

Graph View gives a visual comparison of event trends across V1 and V2. It is organised into four panels.

Event Volume & Breakdown

This panel shows total event tracking with a detailed breakdown by event type, comparing V1 and V2 along with daily trends.

At the top, four summary cards show the totals for the selected date range. Each card displays the V1 value, the V2 value, and the percentage change from V1 to V2.

Below the cards, a daily chart plots event volume for each day in the range. The stacked bars show how each day's events are distributed across event types, and the trend lines show the overall daily movement for V1 and V2.

💡

A steadily rising or stable V2 line, tracking close to V1, is a good sign that V2 is capturing events as expected.

Conversion Funnel Analysis

This panel maps the shopper journey from Hits → Click → Cart → Order and shows the drop-off between stages, with V1 (Legacy) on the left and V2 (New) on the right.

• The stage values are the event counts at each funnel step for that version.
• The percentage between two stages is the change from one stage to the next. A positive value means the funnel narrowed as expected. A negative value means the next stage recorded more events than the stage before it.
• The green badge in the centre shows the improvement in V2 over V1 for that stage, with the absolute difference below it.
• Use the All Sessions dropdown to change the session scope used for the funnel.

⚠️

A later stage can show a higher count than the stage before it (a negative drop-off). This usually means some events contain errors or duplicates. Cross-check the Error Tracking & Analysis panel before drawing conclusions from the funnel.

Attribution Performance

This panel shows how events are attributed to a source (Search, Browse, Experience) and highlights the reduction in unattributed events from V1 to V2.

• Two donut charts break down the event total for V1 and V2 by source, including the share of unattributed events.
• Attribution Change shows the percentage improvement in attribution coverage. A lower unattributed share is better.
• Attributed Events shows how many more events were successfully attributed in the selected range.
• The daily chart below the donuts shows the attributed-versus-unattributed split for each day.

💡

A falling unattributed share in V2 means more events are being tied to a real source, which improves the quality of AI personalization.

Error Tracking & Analysis

This panel shows the distribution of tracking errors by type, with daily trends, comparing error rates and counts between V1 and V2.

Two summary figures report V1 Total Errors and V2 Total Errors, each with the error count and the error rate (errors as a percentage of total events). The daily chart breaks errors down by type for each day and version.

The error types tracked are described below.

To investigate further, select Go to Table View. The table breaks the same errors down by date, version, and event type so you can isolate where they originate.

Table View

Table View monitors event trends across versions for your site as a day-by-day numeric breakdown. Each date has two rows, one for V2 and one for V1, so the two versions can be compared directly. Use the Filter control next to the date range to narrow the results.

The table begins with three columns that identify each row, followed by one column group for each event category.

Event Category Groups

Each event category is shown as a group of columns. Within a group, the source columns report how many events were attributed to each source, Total Events is the group total, and Total Errors (shown in red) is the number of events in that group that contained an error.

ℹ️

Unattributed counts events that could not be tied to a source. Total Errors values are highlighted in red so problem areas stand out as you scan the table.

👍

Best Practices

• Check Pulse Status soon after enabling V2 and again before retiring V1, to confirm V2 is capturing events at the volumes you expect.
• Compare the V1 and V2 trend lines in Event Volume & Breakdown for the same date range. Large unexplained gaps are worth investigating.
• Watch the unattributed share in Attribution Performance. It should trend down in V2.
• Treat negative drop-offs in the funnel as a signal to review Error Tracking & Analysis for duplicates.
• When an error type spikes, switch to Table View, filter to that version and date, and identify the event category driving it.