New Customers (30d), NetSuite

New Customers (30d) for NetSuite. Tracked in the Vortex IQ Nerve Centre, how to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Customer Master

New Customers (30d) as reported by the NetSuite integration.

At a glance

New Customers (30d) is a customer master metric tracked from NetSuite data. It surfaces operational signal so you can spot regressions, opportunities, and structural patterns. Cross-reference the sibling cards below for the full diagnostic picture.

What it counts	New Customers (30d) as reported by the NetSuite integration.
Sample type	Backend API data from NetSuite, refreshed on the standard data refresh.
Why it matters	The metric appears in the Customer Master category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities.
Reading the value	Compare the current period to the prior period to read direction. Cross-reference siblings to triangulate cause.
Format	number
Time window	30D vsP
Alert trigger	-
Sentiment key	-
Roles	owner, finance, marketing

Calculation

Calculated automatically from your NetSuite data on the standard refresh. See the At a glance summary for what it tracks and the worked example below for a typical reading.

Worked example

A representative reading of New Customers (30d) for a typical NetSuite account. The card reports the current value alongside a comparison against the previous period, direction matters. When it moves outside the expected range, cross-reference the siblings below to find the cause; use Vortex Mind to trace upstream causes and Ask Viq for natural-language exploration.

Sibling cards merchants should reference together

Card	Why merchants reach for it
ns_customer_master_drift	Customer Master sibling: Ecom Customers Absent from NetSuite.
ns_customers_missing_subsidiary	Customer Master sibling: OneWorld Customers Missing Subsidiary.

Reconciling against the vendor’s own dashboard

Where to look in NetSuite’s own dashboard: find this metric (or its components) under the relevant report/section. Confirm the period boundaries and any filters match the Vortex IQ profile to reconcile cleanly. The Vortex IQ value may legitimately differ due to period definition, time zone, sampling, or how the vendor buckets the underlying records.