Skip to main content
Every Vortex IQ cross-platform card joins data from two or more connectors to compute a value neither tool alone can produce. These are the cards that make the AI OS positioning real, the cards that no single-tool analytics platform can ship because no single-tool sees both sides of the join.

The problem with single-tool analytics

A merchant who runs BigCommerce, Klaviyo, Google Ads, Datadog, and Royal Mail today already has analytics. Each of those platforms ships a dashboard. Each one tells the merchant a true number inside its own boundary. None of them can tell the merchant which Google Ads campaign is currently spending on an out-of-stock BigCommerce SKU, or how many cart-abandons during the last 5xx-incident window cost the brand in lost orders, or how much revenue is at risk right now from an open New Relic incident. Those questions live in the joins between connectors. The joins are where the catalogue’s decision-grade value lives, and the joins are what Vortex IQ ships. A cross-platform card has three properties that a single-tool analytics card cannot reproduce:
  1. Two or more source connectors. The card’s derive_from: clause names the connectors and the join keys. Vortex IQ owns the canonical join (SKU, email_hash, utm_source, order_id) between every pair of connected platforms.
  2. Conditional render. The card’s only_when: clause hides the card if a required sibling is not connected. A Stripe-only merchant does not see the Stripe-to-Shopify decline-versus-funnel card; the moment they connect Shopify, the card appears with no further configuration.
  3. Decision-grade outcome. Each card answers a question the merchant otherwise has to assemble manually from two browser tabs and a spreadsheet. The card carries the alert threshold, the sentiment band, and the recommended action.
Detail on the tier system, including how cross-platform cards rank against Key Metrics and standard cards in the Nerve Centre dashboard and Vortex Mind reports, lives in Key Metrics, cross-platform and standard tiers.

The portfolio today

148 cross-platform kill-shot cards across 41 connectors, indexed below. Each row in each table is a single card. The Joins column names the connectors the card crosses; the Why it’s XC column is the one-line answer to “why does this need two connectors to compute”.

Per-connector index

AbeBooks - 4 XC cards

Adobe Commerce - 5 XC cards

Alibris - 4 XC cards

Amazon - 4 XC cards

Amazon Prime Shipping - 2 XC cards

APC - 1 XC card

BigCommerce - 8 XC cards

Costco SIP - 3 XC cards

Cybersource - 4 XC cards

Datadog - 4 XC cards

DHL InExpress - 1 XC card

Dotdigital - 4 XC cards

DPD - 2 XC cards

DPD Local - 5 XC cards

eBay - 4 XC cards

FedEx - 2 XC cards

Google Analytics 4 - 5 XC cards

Hermes / Evri - 1 XC card

HubSpot - 5 XC cards

Jira - 2 XC cards

Klaviyo - 4 XC cards

Mailchimp - 5 XC cards

Microsoft Dynamics 365 - 5 XC cards

Net Dispatch - 1 XC card

NetSuite - 5 XC cards

New Relic - 4 XC cards

OnBuy - 5 XC cards

Oracle ERP Cloud - 5 XC cards

Parcelforce - 1 XC card

PayPal - 4 XC cards

Royal Mail - 2 XC cards

Sage Intacct - 5 XC cards

SAP S/4HANA - 5 XC cards

ShippyPro - 1 XC card

Shopify - 5 XC cards

Shopline - 5 XC cards

Stripe - 4 XC cards

USPS - 1 XC card

WooCommerce - 5 XC cards

How a new connector inherits the XC pattern

When a new connector reaches Heroes + Manifest + Graph parity, its manifest declares the XC cards it ships. The four card families that every Ad platform and Marketplace connector must include for Phase 3 parity are documented in CONNECTOR_PARITY_PLAN.md under “Feedonomics XC mandate”. Email and CRM, Payment gateways, ERP, Fulfilment, Analytics, and Monitoring connectors each have their own four-card canonical sets, visible per-connector in the tables above. The pattern is deliberately consistent across the catalogue. A merchant moving from Klaviyo to Mailchimp finds the same four cross-platform cards (abandoned-cart recovery, email-share-of-revenue, send-to-purchase lag, post-purchase unsub rate). A merchant moving from Stripe to Adyen finds the same payment XC family (decline-vs-funnel, 3DS-friction-loss, chargeback-forecast, recoverable-revenue). The cross-platform layer is what makes the catalogue feel like a single product rather than 41 isolated dashboards.