> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # New Customers (30d), Microsoft Dynamics 365 > New Customers (30d): customer master records created in the last 30 days vs prior. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > How many new customer records landed in your ledger this month versus last, a growth signal that also flags duplicate creation from ecom sync. ## At a glance > The count of customer master records created in the last 30 days, compared with the prior 30 days. It is a clean acquisition signal on the finance side, distinct from marketing's lead or signup counts, because it counts customers that reached the ERP customer master. The caveat: where commerce orders flow into Dynamics via dual-write or an integration, a burst of "new" customers can be duplicate records created by the sync rather than genuinely new buyers. | | | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | Customer master records whose creation date falls inside the last 30 days. In F\&O this is `CustTable` records by created date; in Business Central it is Customer records by created date. The card compares this window against the prior 30 days for direction. | | **What it is not** | Not new orders, not new revenue, and not marketing signups. A customer record can be created without an order, and an order can land against an existing customer. This counts records, not transactions. | | **Currency** | Count metric, currency-independent. | | **Multi-Company** | Aggregated across the selected legal entities. The same buyer set up in two entities counts as two new records unless de-duplicated by a shared identifier. | | **Time window** | `30D vsP` (last 30 days vs the prior 30 days) | | **Alert trigger** | n/a | | **Roles** | owner, finance, marketing | ## Calculation Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A DTC supplements brand on F\&O with a Shopify front end flowing customers in via dual-write through Dataverse. Snapshot 14 Apr 26, covering the last 30 days against the prior 30. | Source of new customer record | Last 30 days | Prior 30 days | | -------------------------------- | ------------ | ------------- | | Genuine new buyers (first order) | 410 | 380 | | B2B accounts opened by sales | 18 | 15 | | Duplicates created by ecom sync | 64 | 12 | | **New Customers (this card)** | **492** | **407** | Four things to notice: 1. **492 vs 407 looks like 21% growth.** On the surface a strong month. But the headline hides a data-quality problem underneath. 2. **Duplicate creation jumped from 12 to 64.** A dual-write matching rule changed, so the integration started creating fresh customer records instead of matching to existing ones. Most of the apparent growth is noise. 3. **Stripped of duplicates, real new customers were 428 vs 395, about 8% growth.** Still healthy, but a third of the headline lift was spurious. This is exactly the trap this card is built to surface. 4. **No alert on this card.** It is a context metric. The duplicate spike would surface through the dual-write and Dataverse-promotion sibling cards, which is why they are the recommended pairing. ## Sibling cards merchants should reference together New customer creation is a growth signal that needs a data-quality cross-check. Pair it with the customer-master integrity cards. | Card | Why pair | | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | [Active Customers](/nerve-centre/kpi-cards/microsoft-dynamics/msd-active-customers) | The stock to this card's flow. New records only matter if they convert to active, transacting customers. | | [Ecom Customers Absent from D365](/nerve-centre/kpi-cards/microsoft-dynamics/ecom-customers-absent-from-d365) | The other side of sync drift: buyers on the storefront with no ERP record at all. | | [Customers in Dataverse not Promoted to D365](/nerve-centre/kpi-cards/microsoft-dynamics/customers-in-dataverse-not-promoted-to-d365) | The dual-write staging gap that explains a stalled or spiking new-customer count. | | [Customer Churn Signals](/nerve-centre/kpi-cards/microsoft-dynamics/customer-churn-signals) | Net growth only makes sense alongside loss. Read acquisition and churn together. | | [Top Customers by Revenue](/nerve-centre/kpi-cards/microsoft-dynamics/msd-top-customers-revenue) | Tells you whether new customers are landing at the top end or only adding long-tail records. | ## Reconciling against Microsoft Dynamics 365 **Where to look in Business Central / Finance & Operations:** > **BC: Sales > Customers** (filter or sort by created date for the last 30 days) > **BC: Customer List > Statistics** (recent activity context per customer) > **F\&O: Accounts receivable > Customers > All customers** (filter `CustTable` by created date range) > **F\&O: System administration > Inquiries > Database log** (creation audit trail, if database logging is enabled) To match this card, filter the customer master to records created in the trailing 30 days and count them. The card does exactly this and then sets it next to the prior 30-day count for the trend. **Why our number may legitimately differ:** | Reason | Direction | Why | | -------------------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Created date vs first-order date** | Either | The card counts by record-created date. A native report that counts by first invoice or first order date will diverge for records created ahead of, or after, their first transaction. | | **Dual-write duplicates** | Card higher | Integration-created duplicate records inflate the count. A native dedup view that merges them reads lower. | | **Dataverse staging not yet promoted** | Card lower | Customers sitting in Dataverse that have not been promoted into the D365 customer master are not counted until promotion. | | **Multi-company replication** | Card higher | The same buyer created in several legal entities counts per entity unless de-duplicated. | | **OData / Dataverse sync lag** | Card up to 15 min behind | A record created in D365 appears on the card within the cache window. | **Cross-connector note:** This card counts the ERP-side customer master, which is related to but not identical to commerce-platform customer counts. Shopify, BigCommerce, and Adobe Commerce each track their own customer records, and not every storefront customer becomes a D365 customer (guest checkouts, unsynced buyers). A clean reconciliation against the commerce side belongs on the absent-from-D365 and Dataverse-promotion sibling cards, which exist specifically to quantify that gap. ## Known limitations / merchant FAQs **Does this count new orders or new customers?** New customer records, not orders. A record can be created without an order, and a repeat order against an existing customer does not count here. For order and revenue growth, use the revenue and sales-order cards. **Why might the count be inflated?** Most commonly duplicate creation from ecom sync. When a dual-write or integration matching rule misfires, the same buyer is written as a fresh record instead of matched to the existing one. A sudden spike with no marketing campaign behind it is the classic tell. **How do I tell genuine growth from duplicates?** Cross-check against the Dataverse-promotion and ecom-absence sibling cards, and look for clustered creation timestamps or near-identical names and emails. Ask Viq can surface likely duplicate clusters in plain English. **Why is there no alert on this card?** It is a growth-context metric, not a threshold pulse. The data-quality problems it can hint at are alerted on the dedicated sync-integrity cards instead. **Created date or first-transaction date?** Record-created date. This is deliberate: it measures master-data growth, which can run ahead of or behind the first actual transaction. **Does multi-company double-count?** It can. The same buyer set up across legal entities counts per entity unless your field map de-duplicates on a shared customer identifier. **Can a customer be created in D365 with no storefront record?** Yes. B2B accounts opened directly by a sales team, wholesale customers, and manually keyed records all create D365 customers with no commerce-platform origin. That is normal and expected, not drift. *** ### Tracked live in Vortex IQ Nerve Centre *New Customers (30d)* is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.