Nerve Centre has 215 connectors across 11 archetypes. Connect a source once and every KPI card for that connector appears in your dashboard automatically.
Use this file to discover all available pages before exploring further.
A connector is a data source integration that feeds cards into your Nerve Centre dashboard. When you connect a source, the Nerve Centre authenticates with the vendor’s API (or ingests data via webhook), builds the card set for that connector, and starts rendering live tiles. You do not configure individual cards — you connect the source and the full card set becomes available immediately, organised into categories that mirror the vendor’s own interface.At the time of writing there are 215 registered connectors across 11 archetypes. Of these, 195 are fully active (cards in production), and 20 are pre-card scaffolds being prepared for their first card wave.
When you connect a source, Vortex IQ authenticates with the vendor’s API or ingests data via webhook, then builds the full card set for that connector. Cards begin rendering in Nerve Centre once the initial data pull completes — you do not need to configure individual cards.Cross-Channel cards require data from two or more connected sources. For example, the Active Ads on Out-of-Stock SKUs card requires both an ad platform and a commerce platform to be connected and synced before it can render.
Navigate to Settings → Connected Sources in the left navigation. You see a list of all connectors you have already connected, plus a search field and archetype filter for the full catalogue.
2
Find the connector
Search by connector name (for example, “Shopify” or “Google Ads”) or browse by archetype. Each connector card shows the archetype, the number of cards it unlocks, and its connection method (OAuth, API key, or webhook).
3
Authenticate
Click Connect. For OAuth connectors (Shopify, Google Ads, Meta Ads, Stripe, etc.) you are redirected to the vendor’s authorisation page. Grant the required permissions and you are returned to Vortex IQ. For API-key connectors, paste your key into the field provided.
4
Wait for the first sync
Most connectors are ready within two to five minutes. Commerce platform connectors (Shopify, BigCommerce, Adobe Commerce) backfill historical data on the first sync, which may take 10 to 30 minutes for large catalogues.
5
Review your new connector tab
Open the Nerve Centre. A new tab appears for the connected source. Hero cards are already rendering. Browse by category or use the Hero only filter to see the key metrics immediately.
Cross-Channel cards require their source connectors to be wired. For example, the Active Ads on Out-of-Stock SKUs card requires both Google Ads and Shopify (or BigCommerce, or Adobe Commerce). If one of the source connectors is not yet connected, the cross-channel card shows a “Connect [connector] to unlock” placeholder on the tab.
Ad-platform connectors carry 65 to 102 cards each, the largest card counts in the catalogue. Every ad-platform connector carries a shared base set of categories: Executive Overview, Campaign Performance, Budget Monitoring, Funnel & Conversion, Keyword Intelligence, Device Performance, Geography Performance, Day & Time Performance, Landing Page Performance, and Alerts & Anomalies. Google Ads additionally carries Cross-Channel cards for revenue-at-risk scenarios.
Google Ads — 75 cards
The largest-depth ad-platform connector. Carries the standard 65-card base set plus 5 real-time alert cards (ROAS Drop Alert gads_alert_roas_drop, CPC Spike Alert gads_alert_cpc_spike, Disapproved-Ad Burst Alert gads_alert_disapproved_burst, Wasted-Spend Burst Alert gads_alert_wasted_spend_burst, Conversion-Tracking-Broken Alert gads_alert_conversion_tracking_broken) and 5 Cross-Channel cards joining Google Ads with Shopify, GA4, and Website Performance.
Amazon Ads — 102 cards
The deepest catalogue in the ad-platform archetype. Carries the 65-card standard base plus 37 Amazon-specific cards covering ACOS, TACOS, Amazon DSP (DSP vs Sponsored Spend Mix, DSP Audience Reach, DSP Creative Fatigue Alert), Dayparting (Bid-Modifier Coverage, ROAS by Hour heatmap, Dayparting Waste), and Search-Term Harvest (Harvest Queue, Harvest Velocity Trend, Branded and Non-Branded Harvest Candidates).
Meta Ads (Facebook) — 65 cards
Full standard base set covering ROAS, CPA, CPC, CTR, conversion funnel, and geographic and device breakdowns. Hero cards include ROAS (gauge), Total Spend (kpi), Total Revenue (kpi), Spend vs Budget (progress), Wasted Spend (kpi), and Zero-Conversion Spend (kpi).
Other ad-platform connectors
AdRoll (65 cards), Criteo (65 cards), LinkedIn Ads (65 cards), MediaMath (65 cards), Microsoft Ads / Bing (65 cards), Outbrain (65 cards), Pinterest Ads (65 cards), Quora Ads (65 cards), Snapchat Ads (65 cards), StackAdapt (65 cards), Taboola (65 cards), The Trade Desk (65 cards), TikTok Ads (65 cards). All carry the same 65-card standard base with identical Hero card sets.
Cards cover Revenue & Growth (Total Revenue, Orders Over Time, Revenue by Channel), Order Patterns (Orders by Hour, Weekend vs Weekday, Orders by Day of Week), Customer Mix (New Customers, Repeat Rate, Customer Countries, Customer Segments), Inventory & Fulfilment (Inventory Alerts, Stock vs Sales, Unfulfilled Orders), Discount & Margin (Discount %, Top Discount Codes, Total Discount), and Refund & Recovery (Refund Rate, Refund Count, Top Refunded Products). Also carries Shopify-specific alert cards (Revenue Drop, Refund Spike, Out-of-Stock Spike, Fulfilment Delay, Negative Review Burst) and five Cross-Channel cards.
BigCommerce — 115 cards
The largest per-connector card count in the catalogue. Carries the Shopify equivalent card set plus BigCommerce-specific B2B analytics, channel-level revenue breakdowns per sales channel, and multi-storefront cards.
Adobe Commerce (Magento) — 59 cards
Carries the standard ecommerce card set plus B2B-specific cards (B2B Accounts Gone Quiet, B2B AOV vs B2C AOV, B2B Revenue Share) and five Cross-Channel cards joining Adobe Commerce with Google Ads, Amazon, and email marketing connectors.
Other ecommerce connectors
WooCommerce, Ecwid, Shopline, Square Online, Salesforce Commerce Cloud, SAP Commerce. Card counts range from 30 to 60 depending on API depth.
Hero cards: Authorisation Rate, Successful Charges, Decline Rate by Reason, Total Volume, Refunds Issued. Covers payment health (authorisation and decline rates by reason code, by card brand, by issuer), dispute and chargeback monitoring, subscription and MRR tracking, payout and settlement tracking, Smart Retry outcomes, and Stripe Radar fraud signals. Also carries Cross-Channel cards joining Stripe with Shopify and GA4 for revenue-at-risk scenarios.
PayPal — 77 cards
Covers payment volume, authorisation rates, T19xx dispute events (chargeback and dispute tracking using PayPal transaction event codes), Seller Protection coverage, refund and reversal tracking, and subscription dunning outcomes.
The second-largest per-connector card count. Covers Traffic Acquisition (sessions by channel, source/medium, referral traffic), Ecommerce Revenue (revenue trend, revenue by channel and category, AOV, purchases trend), Conversion (ecommerce conversion rate, checkout completion rate, cart abandonment rate, funnel drop-off), Customer Behaviour (new vs returning, session duration distribution, engaged sessions), Product Intelligence (product views vs purchases, cart additions, conversion rate by product), Real-Time (active users, real-time revenue, real-time purchases), Data Quality (GA4 Property Health, GTM Tag-Fire Rate, sampling threshold), AI Traffic (AI Traffic Overview, AI vs Search Traffic, AI Conversion Rate), and five alert cards including Traffic Drop Alert and Conversion-Rate Drop Alert (both Hero). Five Cross-Channel cards join GA4 with Google Ads, Klaviyo, and Website Performance.
ShipBob (87 cards — the deepest logistics connector, covering order fulfilment SLA, on-time delivery rate, RTO rate, carrier performance, warehouse inventory, and cost-per-shipment), Royal Mail, DHL (iexpress), FedEx, USPS, Hermes/Evri, Parcelforce, Australia Post, Deutsche Post, Japan Post, Bring, DPD, DPD Local, Interlink Express, Net Dispatch, Sendle, Shippo, EasyPost, Shippy Pro, Ship Theory.
Website Performance (PageSpeed + CrUX) — 79 cards covering Core Web Vitals (LCP, INP, CLS), First Contentful Paint, TTFB, Lighthouse scores (Performance, Accessibility, Best Practices, SEO), and CrUX field data broken down by device, connection type, and landing page. Cross-Channel cards join website performance data with GA4 conversion rates and Google Ads landing-page spend.
PagerDuty, OpsGenie, Statuspage, Uptime Robot, Better Uptime. These connectors route Nerve Centre Critical alerts into your existing incident-management workflow.
Twenty connectors are registered in the catalogue but are in the pre-card phase — the OAuth and data-ingestion layer is built but the card manifests have not yet shipped. These appear in Settings → Connected Sources and can be connected, but the Nerve Centre tab shows a “Cards coming soon” placeholder. The list includes some CRM connectors (Salesforce, HubSpot, Zoho CRM, Pipedrive, Keap, Microsoft Dynamics, Insightly, Nimble, SugarCRM, Freshsales, AgentCRM), customer support connectors (Zendesk, Freshdesk, Gorgias, Intercom, HelpScout, LiveChat, LiveAgent, Tidio, Crisp), and headless CMS connectors (Prismic, Strapi, Sanity).
If a connector’s OAuth token expires or the vendor API returns an authentication error, the Nerve Centre displays a “Connection requires attention” banner on the connector tab, and all cards on that tab show a “stale” badge. To reconnect:
1
Open Connected Sources
Navigate to Settings → Connected Sources.
2
Find the affected connector
Connectors with expired authorisation show a red status badge. Click the connector to open its settings panel.
3
Re-authorise
Click Reconnect (OAuth connectors) or update the API key (key-based connectors). You are redirected through the vendor’s authorisation flow. Once complete, the connector resumes polling and stale badges clear within one refresh cycle.
Data-gap alerts (trigger_reason: data_gap) route to the workspace administrator role rather than the card’s domain owner. If you see these alerts on multiple cards simultaneously across a single connector, re-authorisation is almost always the fix.