> ## 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. # Nimble on Vortex IQ > Monitor Nimble pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. Monitor Nimble pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=nimble) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Find failures, leaks and risks before they cost sales. Improve discovery, conversion, campaigns and repeat purchase. Monitor orders, fulfilment, delivery and settlement. Find storefront, speed, accessibility and journey problems. Identify missing, inconsistent or outdated product data. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 34 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | -------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of two confirmed real Nimble Contact fields: share with a populated fields.email entry and share with a populated fields.phone entry. | | **Email Click Rate** | Alert band 2 / 0.5 | Description pending editorial review; the signal is live. | | **Email Open Rate** | Alert band 20 / 10 | Tracked-send open rate. Pair with click\_to\_open\_rate for a proxy-resistant read. | | **Flow Count Summary** | Merchant rule | Count of Nimble workflows / sequences derived from activity automation. | | **Flow Status Breakdown** | Merchant rule | Flow Status Breakdown. | | **Flow Trigger Types** | Merchant rule | Flow Trigger Types, shown by share. | | **Flows List** | Merchant rule | Flows List. | | **List Count** | Merchant rule | Description pending editorial review; the signal is live. | | **List Health Summary** | Merchant rule | Description pending editorial review; the signal is live. | | **Lists Overview** | Merchant rule | Lists Overview. | | **Placed Orders Total** | Merchant rule | Description pending editorial review; the signal is live. | | **Segments Overview** | Merchant rule | Segments Overview. | | **Top Lists by Name** | Merchant rule | Top Lists by Name. | | **Total Sends** | Merchant rule | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | ------------------------------------ | ------------------- | -------------------------------------------------------------------------------------------------------------- | | **Campaign Status Breakdown** | Merchant rule | Tracked group emails grouped by status (draft / scheduled / sent). | | **Checkout-to-Order Rate** | Merchant rule | Share of email-driven checkouts that became orders. Needs a commerce sibling for the order side. | | **Click-to-Open Rate** | Alert band 10 / 3 | Truer engagement signal than open rate - proxy filtering doesn't pre-click. | | **Conversion Rate** | Alert band 3 / 1 | Description pending editorial review; the signal is live. | | **Email Health KPIs** | Merchant rule | Composite send / deliver / open / click snapshot for tracked group emails. | | **Engagement Funnel** | Merchant rule | Sent → Delivered → Opened → Clicked drop-off on tracked sends. | | **Revenue per Recipient** | Merchant rule | Description pending editorial review; the signal is live. | | **Revenue per Send** | Merchant rule | Description pending editorial review; the signal is live. | | **Stalled Deals (>30d no activity)** | Merchant rule | Open deals going cold. Either re-engage or mark lost - stalled deals rot the forecast. Audit NIM01 fires here. | | **Total Revenue** | Alert band 10 / -10 | Order revenue attributed to Nimble-tracked sends. Needs a commerce sibling for the order side. | | Signal | Alert behaviour | What it tracks | | --------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------- | | **Active Subscribers (Est.)** | Merchant rule | Estimated active (person-type, non-bounced) contacts in the Nimble base. | | **Bounce / Spam Spike on Tracked Send** | Merchant rule | Sudden bounce/spam surge on the shared sending domain - pause sends and clean the list. Audit NIM02 fires. | | **Bounce Rate** | Alert band 2 / 5 | Hard-bounce share on tracked group emails. >5% trips sender-reputation throttling. Gated on message tracking being enabled. | | **Customers With No CRM Contact** | Merchant rule | Paying ecom customers absent from the CRM - relationship coverage gap and lost upsell context. | | **Deal Pipeline vs Repeat Ecom Orders** | Merchant rule | Repeat ecom customers with no Nimble deal = untracked expansion the sales team is missing. | | **Delivery Rate** | Alert band 98 / 95 | Description pending editorial review; the signal is live. | | **Refund Rate** | Merchant rule | Refunded / placed on email-attributed orders. Needs a commerce sibling. | | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam complaints / delivered on tracked sends. Above threshold the shared sending domain degrades for everyone. | | **Unsubscribe Rate** | Alert band 0.5 / 2 | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | --------------------- | --------------- | --------------------------------------------------------- | | **Checkouts Started** | Merchant rule | Description pending editorial review; the signal is live. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** critical · **Outcome** Catalogue quality · **Fix status** Report only Once this credential fails, VortexIQ stops seeing deals, contacts and pipeline activity from this CRM entirely, and every pipeline and data-quality finding here goes stale from that moment, silently, until someone notices the numbers stopped updating. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-AUTH-001` **Severity** high · **Outcome** Grow revenue · **Fix status** Report only Leads answered after 8 hours convert at a fraction of the rate of leads answered in minutes; speed-to-lead is the cheapest conversion lever in the pipeline. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-LEAD-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only More than 1 in 5 records is missing a required field. Incomplete records make segmentation, reporting and any automation keyed off those fields (routing, scoring, follow-up sequences) unreliable, so the gap compounds into every process built on top of this data, not just the records themselves. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-DATA-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **8 read** and **3 write** operations across contacts, deals, accounts, activitys, contactgroups, messages on Nimble. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=nimble) #### Ready to build your first Nimble workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | ------------- | --------------- | ---------------- | | contacts | 1 | 1 | | deals | 1 | 1 | | accounts | 1 | 0 | | activitys | 1 | 0 | | contactgroups | 1 | 0 | | messages | 1 | 0 | | oauthtokens | 0 | 1 | | pipelines | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.