# Edit thousands of products at once with AI Rules Profiles
Source: https://docs.vortexiq.ai/actions/bulk-content-edit

Export products to a grid, apply a Rules Profile to AI-edit thousands of rows in one batch, then import and review every change before it touches your store.

Bulk Content Edit is the high-volume content engine inside Vortex Agents. It gives you a three-step workflow - Export to Grid, Generate with AI Request, Import File - that lets you apply consistent, brand-governed AI edits to every product description, collection page, or content block on your store in a single operation, without touching a spreadsheet cell by hand. Every batch is held for your review before it touches the store, applied safely, and reversible with one-click rollback if an edit is not right.

The companion **Rules Library** stores the Rules Profiles that govern how the AI edits. A Rules Profile defines voice, tone, length, schema structure, and forbidden-word constraints so every bulk edit matches your brand standards and respects your legal guardrails.

## The three actions

<CardGroup>
  <Card title="Export to Grid" icon="table">
    Pull products, collections, or content into a spreadsheet-style grid and export as CSV.
  </Card>

  <Card title="Generate with AI Request" icon="sparkles">
    Apply a Rules Profile to thousands of rows in one batch. The AI edits according to your constraints.
  </Card>

  <Card title="Import File" icon="upload">
    Upload the edited CSV and review every change in the grid before deciding what to apply.
  </Card>
</CardGroup>

## The full workflow

<Steps>
  <Step title="Export to Grid">
    Open `/v2/actions` and click **Bulk Content Edit**, then choose **Export to Grid**.

    Select the entity type you want to edit: **Products**, **Collections**, or **Content**. Filter the export by collection, product type, tag, or any other dimension available in your connected storefront connector. The grid loads your selected entities with one row per product (or collection or content block) and one column per editable field - title, description, meta title, meta description, body HTML, and so on.

    When the grid looks right, click **Export CSV** to download the file. This CSV is the input to the next step.
  </Step>

  <Step title="Generate with AI Request">
    Click **Generate with AI Request** and upload your exported CSV, or work directly in the grid.

    Select the **Rules Profile** you want to apply. The Rules Profile defines:

    * **Voice** - the register and personality the AI writes in (e.g. confident, technical, conversational)
    * **Tone** - the emotional texture appropriate for your brand and audience
    * **Length** - minimum and maximum word counts per field
    * **Schema** - which schema.org fields to populate and in what format
    * **Forbidden words** - terms, competitor names, or claims the AI must never use

    Write your AI Request - for example, *Rewrite every product description to lead with the primary benefit, include the key specification in the second sentence, and end with a single call to action. Apply the brand voice from the Rules Profile.* - and click **Generate**.

    The AI processes every row in the CSV according to your request and your Rules Profile constraints. For large catalogues this runs as a background batch; you will see the job in the **Active Work** area at the bottom of the Vortex Agents hub.
  </Step>

  <Step title="Review in the grid">
    When the batch completes, the edited CSV is loaded back into the grid with a diff view showing the original value and the AI-generated replacement side by side for every changed field.

    Review the changes. You can:

    * Accept individual cells
    * Reject individual cells and keep the original
    * Edit a cell inline before accepting
    * Filter to rows with changes only
    * Filter to a specific field (e.g. review all `meta_description` changes before reviewing `body_html` changes)

    Nothing is applied to your store at this stage. The grid is a staging environment.
  </Step>

  <Step title="Import File">
    Click **Import File** (or **Apply changes** if you are working directly in the grid) to push the approved rows back to your storefront via the connected platform connector - Shopify, BigCommerce, or Adobe Commerce.

    Only the rows and fields you approved are written. Rejected cells keep their original values. The import is logged in Vortex Memory with a timestamp, the Rules Profile used, and the count of changes applied, so you have a full audit trail.
  </Step>
</Steps>

## Rules Profiles

A Rules Profile is the AI's brief for a bulk edit. Without one, the AI uses a neutral retail-friendly tone and flags that a brand voice would tighten the output. With one, every row in a thousand-product batch sounds like it came from the same writer who knows your brand.

### What a Rules Profile contains

| Constraint          | What it controls                                                                                       |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| **Voice**           | Register and personality - e.g. expert, friendly, authoritative, direct                                |
| **Tone**            | Emotional texture appropriate to your brand and audience                                               |
| **Length**          | Minimum and maximum word counts per field type                                                         |
| **Schema**          | Which schema.org properties to populate, in what format and order                                      |
| **Forbidden words** | Terms, competitor names, unsubstantiated claims, or regulatory no-go phrases the AI must never produce |

### Creating and managing Rules Profiles

Rules Profiles live in the **Rules Library**, accessible from the top-right of every Vortex Agents screen. Each profile has a name, a description, and the full set of constraints listed above.

<Note>
  Rules Profiles connect directly to the **Brand & AI settings tab** under Platform Settings. Brand voice rules you configure in Brand & AI cascade into every bulk operation that references a Rules Profile, so your guardrails are consistent across Bulk Content Edit, SEO content production, and AI-generated pages.
</Note>

You can create as many Rules Profiles as you need. Common setups:

* One profile per brand (if you manage multiple merchants)
* One profile per content type (product descriptions vs blog posts vs meta descriptions)
* One profile per locale (if voice or tone differs by market)

### Applying a Rules Profile from Ask Viq

You can trigger a bulk edit from the Ask Viq chat:

* *Rewrite all product descriptions in the Accessories collection using the UK Brand Voice profile*
* *Update meta descriptions for products with no meta description, apply Rules Profile: SEO Default*
* *Bulk edit all collection page descriptions to add a structured lead paragraph*

Ask Viq parses the request, confirms the scope and the Rules Profile it will use, and runs the Generate step. The result lands in the grid for review before anything is applied.

## What Bulk Content Edit does not do

Bulk Content Edit operates on **existing entities** - products, collections, and content already in your store. To propose entirely new pages or design changes optimised for sales, use [Generate New Page / Design Change](/actions/store-audit) from the Store Audit module.

## Cross-links

* Brand voice source: [Brand & AI settings](/platform/settings)
* Audit-driven edit triggers: [Store Audit](/actions/store-audit)
* SEO content production: [SEO + GEO Engine](/actions/seo-geo)
* Change history: [Vortex Memory](/vortex-memory)


# The Kanban Board: where findings become done work
Source: https://docs.vortexiq.ai/actions/kanban

The Vortex IQ Kanban Board turns audit findings, Vortex Mind report items, and AI-proposed actions into cards that move through To Do, In Review, Doing, and Done - with automation rules, assignees, and due dates.

The Kanban Board is where Vortex IQ findings become done work. Every audit finding, every Vortex Mind report item, every AI-proposed change, and every customer-journey friction point lands here as a card and moves through the workflow until it is resolved. When a card carries a Vortex Agent fix, it pauses in **In Review** so you approve it before anything ships: the fix then applies staging-first and stays reversible with one-click rollback, so nothing reaches your live store unchecked. The board lives at `app.vortexiq.ai/v2/kanban` and it is the single resolution surface across every other module on the platform.

## Why a Kanban Board inside an AI OS

Most ecommerce teams already use a project tool - Jira, Asana, Linear, Trello, ClickUp, Monday. They are good at tracking work once it is defined. They are not good at *defining the work*: a generic project tool has no idea what is broken, what is underperforming, what is leaking revenue, or what to prioritise. The merchant has to figure that out and enter the work by hand.

The Vortex IQ Kanban Board sits on the other side of that gap. The work is **generated** by the audit and report engines, **prioritised** by the severity model, and **routed** by automation rules. You inherit a board where every card is already a real, ranked, contextualised piece of work with a recommended fix path attached. Your job is to triage, assign, and ship - not to figure out what should be on the board in the first place.

<Info>
  Many teams run both: the Vortex IQ Kanban Board for triage and prioritisation, and Jira (or Asana / Linear) for engineering execution, with bidirectional sync between the two.
</Info>

## What lives on the board

Cards come from five primary sources, plus manual entry:

| Source                                            | Card type        | Routing default                        |
| ------------------------------------------------- | ---------------- | -------------------------------------- |
| [Store Audit](/actions/store-audit) findings      | Audit finding    | To Do                                  |
| Customer Journey Test friction points             | Journey friction | To Do                                  |
| UI/UX Regression Test regressions                 | Regression       | Critical column / Regressions swimlane |
| Generate New Page proposals                       | Proposal         | To Do with *Proposal* label            |
| [Vortex Mind](/vortex-mind/overview) report items | Report action    | To Do with *From Vortex Mind* label    |

Cards can also be created manually for work that did not originate in an automated source.

## The default board

Out of the box, every workspace gets a board with four columns:

| Column        | What it represents                                                                                                         | Auto-transition                                                                                        |
| ------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **To Do**     | Cards not yet started - the intake column for every new finding.                                                           | None (manual move out).                                                                                |
| **In Review** | Cards in the proposal- or fix-review stage: an AI-generated fix awaiting approval, or a draft change awaiting team review. | When an Ask Viq fix is approved, the card auto-moves to Doing.                                         |
| **Doing**     | Cards actively being worked on.                                                                                            | When a fix lands (deploy event, Bulk Content Edit applied, manual close), the card auto-moves to Done. |
| **Done**      | Cards that have been resolved; the finding is marked resolved in Vortex Memory.                                            | None.                                                                                                  |

Each column shows its card count in the header so you can see queue depth at a glance. Columns are customisable for workspaces with more complex workflows, and a workspace can run multiple boards (for example, one each for Marketing, Engineering, and Finance) with their own columns, swimlanes, and rules.

## Card anatomy

Every card carries:

| Element                      | Detail                                                                                                                                           |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Title**                    | The finding name or work-item title.                                                                                                             |
| **Severity badge**           | Critical / High / Medium / Low / Informational, mirrored from the originating finding.                                                           |
| **Source label**             | Which connector or scan surfaced the work.                                                                                                       |
| **Assignee**                 | Who is responsible. Defaults to unassigned; set by rules or manually.                                                                            |
| **Due date**                 | Defaults to severity-driven (Critical +24h, High +7d, Medium +30d, Low +90d).                                                                    |
| **Labels**                   | Source, finding type, journey, regression, proposal, and custom labels.                                                                          |
| **Recommended fix**          | AI-generated guidance on the lowest-friction resolution.                                                                                         |
| **Affected items checklist** | URLs, SKUs, transactions, or customers ticked off as resolved.                                                                                   |
| **Linked context**           | Chips linking to the related [Ask Viq](/ask-viq/overview) conversation, [Vortex Mind](/vortex-mind/overview) report, or mirrored external issue. |

Click any card to expand the full panel with comments, history, attachments, and the complete finding context.

## Filters, search, and swimlanes

A filter rail above the board scopes the view by **source** (Audit, Journey, Regression, Proposal, Vortex Mind, Manual), **severity**, **assignee**, **date range**, and **label**, plus full-text search across titles, descriptions, and comments. Filters stack, the filtered view is shareable via URL, and named filter combinations are saved as quick-access views.

For horizontal grouping, **swimlanes** group cards by source, severity, assignee, team, or storefront - for example one lane per connector, one lane per severity band, or one lane per storefront. Swimlanes can be enabled or disabled per workspace.

## Automation rules

Automation rules drive routing, status transitions, and external integrations. Common rules:

* Route critical findings to **In Review** for engineering review.
* Send SEO findings to the **Marketing** swimlane.
* Send Vortex Mind findings to **Operations**.
* When the linked deploy lands, move the card from **Doing** to **Done**.
* When a card sits in **Done** for 14 days, archive it.

Within a column, cards also carry a finer-grained status (*Awaiting approval*, *Awaiting fix*, *Pending data refresh*, *Blocked*) that is independent of column position.

## Exports and integrations

The board exports to **CSV** (every card with full metadata) and **PDF** (a board snapshot for stakeholder reports). It syncs **bidirectionally with Jira, Asana, and Linear**, and can push events out via webhook - so triage happens in Vortex IQ while execution can continue in your engineering tracker.

## How Kanban connects to other modules

The Kanban Board is downstream of every content-producing module and upstream of your external trackers and long-term memory:

* [Store Audit](/actions/store-audit) findings push to the board.
* [Vortex Mind](/vortex-mind/overview) pushes report actions to the board.
* [Ask Viq](/ask-viq/overview) creates and updates cards from conversation.
* The [SEO + GEO Engine](/actions/seo-geo) publishes content-production cards for the writing team.
* [Bulk Content Edit](/actions/bulk-content-edit) creates cards for batch reviews.
* [Vortex Memory](/vortex-memory/overview) records every card lifecycle event for retroactive analysis and MTTR computation.

## FAQ

<AccordionGroup>
  <Accordion title="Do I have to use the Kanban Board?">
    No. A workspace can disable the board entirely from **Settings → Kanban**. Findings still surface in the Store Audit findings dashboard and can be routed directly to Slack, Jira, or email. The board is the recommended resolution surface, but it is not mandatory.
  </Accordion>

  <Accordion title="Can I have multiple boards in one workspace?">
    Yes. Configure multiple boards (for example, Marketing, Engineering, Finance) with different columns, swimlanes, and automation rules. Cards route by source and severity to the appropriate board. The default workspace board is created on first use.
  </Accordion>

  <Accordion title="Does the board sync with Jira / Asana / Linear?">
    Yes, bidirectionally. Many merchants use Vortex IQ Kanban for triage and Jira for engineering execution, with the two kept in sync.
  </Accordion>

  <Accordion title="How are due dates set?">
    Due dates default to severity-driven (Critical +24h, High +7d, Medium +30d, Low +90d). Automation rules can override per source or finding type, and a manual override per card is always available.
  </Accordion>

  <Accordion title="What happens when the underlying finding is resolved?">
    If the finding is resolved while the card is still in To Do or In Review, the card auto-moves to Done with a *resolved upstream* note. If the card is in Doing, it stays there (someone is actively working on it) but a banner flags that the finding may already be resolved.
  </Accordion>
</AccordionGroup>


# Vortex Agents: turn AI findings into work that ships
Source: https://docs.vortexiq.ai/actions/overview

Vortex Agents surface findings across the AI OS, rank them by revenue at stake, and resolve them with staging-first, approval-gated fixes that are reversible by default with one-click rollback.

Vortex Agents are where the Vortex IQ AI OS turns findings into work that ships. The agents do three things: they **surface** issues and opportunities from across the AI OS and over 200 connectors, **rank** each one by revenue, effort, and confidence, and **resolve** it with an agentic fix. Every capability the platform can perform on your store - running a full store audit, executing the 12-step SEO and GEO Domination Engine, editing thousands of products in a single bulk pass, generating your daily morning briefing - lives here. Crucially, an agent can audit your store and apply a fix **safely**: every change runs staging-first, is gated on your approval, and is reversible by default, with one-click RollbackPro if you ever need to undo it. You decide what runs. You approve what gets applied.

## The four headline surfaces

At the top right of every Vortex Agents screen, four buttons take you into the platform's deepest workflows.

<CardGroup>
  <Card title="Store Audit" icon="magnifying-glass" href="/actions/store-audit">
    Scan every connected source for issues, gaps, and opportunities. Five audit actions including a full store scan, customer journey test, and UI/UX regression testing.
  </Card>

  <Card title="SEO + GEO Engine" icon="chart-line" href="/actions/seo-geo">
    Run the 12-step Domination Engine. Own your brand's search results and AI-search citation surface from competitor analysis through to live ranked content.
  </Card>

  <Card title="Bulk Content Edit" icon="pen-to-square" href="/actions/bulk-content-edit">
    Export products, collections, and content to a spreadsheet-style grid. AI-edit thousands of rows with a Rules Profile, then import the changes back for review.
  </Card>

  <Card title="Rules Library" icon="book" href="/actions/bulk-content-edit">
    Reusable Rules Profiles that define voice, tone, length, schema, and forbidden-word constraints for all AI-generated content across the platform.
  </Card>
</CardGroup>

## Telemetry cards

Below the headline buttons, four cards give you a live read on Vortex Agents activity across your workspace.

| Card                    | What it shows                                                                           |
| ----------------------- | --------------------------------------------------------------------------------------- |
| **Runs This Week**      | How many action runs have completed in the current week.                                |
| **Pending Your Review** | AI-generated changes waiting for your approval before anything is applied to the store. |
| **Active Schedules**    | Audits, briefings, and other actions running on a recurring schedule.                   |
| **Time Saved**          | The platform's estimate of operational time saved versus doing the same work manually.  |

The **Pending Your Review** card is the heart of the approval model. Every AI-generated change - whether it comes from a Store Audit finding, an SEO content draft, or a bulk product edit - sits here until you explicitly approve it. Nothing touches your live store without your sign-off.

## Vortex Mind briefings

Four scheduled briefings sit at the top of Vortex Agents because they are the fastest answer to "what changed in my business?". All four are delivered in text, voice, and email formats.

<Tabs>
  <Tab title="Daily">
    **Daily Morning Briefing** - Today's store health, key shifts, and anomalies. A 2 to 5 minute read or listen that replaces the morning dashboard crawl.
  </Tab>

  <Tab title="Weekly">
    **Weekly Report** - Week-over-week deltas, top movers, cohort shifts, and a prioritised list of what to focus on next week.
  </Tab>

  <Tab title="Monthly">
    **Monthly Report** - Month-over-month business review covering merchandising performance, traffic insights, and channel mix.
  </Tab>

  <Tab title="Quarterly">
    **Quarterly Business Review** - A board-ready QBR pack covering growth, retention, gross-margin percentage, and channel mix.
  </Tab>
</Tabs>

These briefings summarise findings. The deeper diagnostic reports - Payment Performance Intelligence, Decline Recovery Intelligence, Checkout Conversion Failure, Daily Revenue Leakage, Customer Recovery Opportunity, Google Ads Revenue Intelligence, and Paid Traffic Waste - live in the [Vortex Mind](/vortex-mind) module and link back from each briefing.

## The Kanban Board

Every finding from every action lands on the Kanban Board as a ready-to-work card. The board has four default columns:

* **To Do** - new findings waiting to be picked up
* **In Review** - AI-proposed fixes or drafts awaiting your approval
* **Doing** - work actively in flight
* **Done** - resolved items, marked as such in Vortex Memory

Automation rules route cards to the right column, swimlane, or assignee based on source and severity. You can also push any finding to Jira, Slack, or email from the board.

## Safe by default: approve, apply, roll back

Vortex IQ never silently applies changes to your store. Every AI-generated output - a fix proposed by a store audit, a batch of product descriptions from Bulk Content Edit, a content draft from the SEO engine - enters the **Pending Your Review** queue first. You review. You approve. Then it applies, staging-first. Because every approved change is reversible by default, one-click RollbackPro lets you undo it quickly if the result is not what you expected. Audit, apply, and roll back, each step backed by a full audit trail of the source, the evidence, the revenue at stake, and the change proposed.

<Note>
  Store Audit is entirely read-only. The scan reads your connected sources and produces findings, but no change reaches your storefront until you explicitly approve it through Bulk Content Edit, the Ask Viq fix-and-deploy loop, or a manual edit in your platform.
</Note>

## Active Work

The Active Work area at the bottom of the Vortex Agents hub shows every batch currently in flight. Filter tabs scope the view to All, Bulk Edit, Audit, Ask Viq, or SEO/GEO so you can track exactly what is running and what is waiting.

## How Vortex Agents connect to other modules

Vortex Agents are the execution layer. They read findings from [Vortex Mind](/vortex-mind) diagnostic reports and surface their headline indicators as briefings. They tie findings back to specific [Nerve Centre](/nerve-centre) metric cards so you can click from a finding to the KPI that triggered it. They write every resolved item into [Vortex Memory](/vortex-memory) for retroactive analysis. Kanban automation rules read from [Settings](/platform/settings) for routing, and Bulk Content Edit Rules Profiles read from the Brand & AI tab for voice and guardrail constraints.


# Dominate search with Vortex IQ's 12-step SEO + GEO Engine
Source: https://docs.vortexiq.ai/actions/seo-geo

Run the 12-step SEO + GEO Domination Engine to build a complete content programme for Google and AI-search - from keyword research to live position tracking.

The SEO + GEO Domination Engine is the most differentiated surface in the Vortex IQ AI OS. It takes a single merchant brand and runs it through twelve ordered, AI-driven steps that produce a complete, market-specific content programme: every pillar topic the brand should own, every supporting spoke article, the keyword universe behind them, the AI search-engine answer surface, and the live ranking trajectory once the content goes live.

The engine lives at `app.vortexiq.ai/v2/seo-engine/projects/`. One brand equals one project. The project runs twelve sequenced steps. Every step produces artifacts. Every artifact is reviewed and approved before the next step unlocks - the engine never silently moves forward.

<Tip>
  GEO (Generative Engine Optimisation) is folded into every step alongside traditional SEO. The same twelve steps that build pillar-and-spoke Google ranking also build your brand's mention surface in ChatGPT, Perplexity, Gemini, and Claude. Run both in one operation rather than treating them as separate programmes.
</Tip>

## The 12 steps at a glance

| Step | Name                              | Output                                                           |
| ---- | --------------------------------- | ---------------------------------------------------------------- |
| 1    | Brand Discovery                   | Brand profile, product catalogue, technical SEO baseline         |
| 2    | Competitor Discovery              | 2 to 5 ranked competitors with content and keyword inventory     |
| 3    | AI Engine Baseline                | Brand mention rate across ChatGPT, Perplexity, Gemini, Claude    |
| 4    | Content Gap Analysis              | Gaps, blue-ocean keywords, beatable competitor pages             |
| 5    | Keyword Research                  | Master keyword list with real volume and KD scores               |
| 6    | Conversational Query Mining       | Long-tail conversational queries by category                     |
| 7    | Pillar Architecture               | Hub-and-spoke content architecture with 8 to 12 pillars          |
| 8    | Position Estimation               | 90-day projected ranking per URL with confidence intervals       |
| 9    | Content Titles & Internal Linking | H1, title tag, meta description, and internal-link spine per URL |
| 10   | SEO Optimization Layer            | On-page composite score and per-URL fix recommendations          |
| 11   | Deployment Calendar               | 13-week publish schedule with pillar prioritisation              |
| 12   | Operations Pack                   | Runbook, pre-publish checklist, monitoring KPIs, rollback policy |

## The eight named actions

The Vortex Agents hub surfaces eight named actions covering Steps 1 through 8. Each action is a gateway into the corresponding step and can also be triggered by natural-language phrases in Ask Viq.

<Steps>
  <Step title="Own Brand Content (Brand Discovery - Step 1)">
    The engine crawls your website, inventories your product catalogue, catalogues your existing blog, profiles your brand voice and positioning, and produces a Technical SEO baseline covering crawlability, indexability, schema coverage, mobile usability, broken-link count, and redirect chains.

    Typical run time is 8 to 25 minutes depending on site size. If Google Analytics 4 or Google Search Console is connected, Step 1 reads those sources to enrich the brand profile with top-traffic pages, top queries, and audience signals.

    **Artifacts produced:** `brand-profile.md`, `product-taxonomy.json`, `blog-inventory.csv`, `tech-seo-baseline.json`.
  </Step>

  <Step title="Competitor Analysis (Competitor Discovery - Step 2)">
    The engine identifies 2 to 5 real organic competitors by running SERP overlap analysis against your brand's likely keywords, filtering out marketplaces and aggregators, and ranking the remaining sites by overlap density. It then audits each competitor's content (pillar inventory, blog cadence, content depth, schema coverage) and keyword footprint (top-ranking keywords, branded vs non-branded mix, intent split).

    **Artifacts produced:** `competitors.json`, per-competitor `content-inventory.csv`, per-competitor `keyword-footprint.csv`, per-competitor `strengths-weaknesses.md`.
  </Step>

  <Step title="Gap Analysis (Content Gap Analysis - Step 4)">
    The engine cross-references your existing content against competitor inventories and the AI engine baseline to find three things: keyword gaps (terms where 2+ competitors rank in the top 10 but you do not rank in the top 100), blue-ocean keywords (meaningful volume, no competitor ranking strongly), and beatable pages (specific competitor URLs with thin content, missing schema, or outdated dates).

    **Artifacts produced:** `gaps.json`, `blue-ocean.csv`, `beatable-pages.csv`, `gap-summary.md`.

    <Info>
      A keyword gap is a term where competitors rank but you do not. A blue-ocean keyword is a term where nobody ranks well. Gaps require beating the competition; blue-ocean opportunities require simply showing up with quality content.
    </Info>
  </Step>

  <Step title="Keyword Research (Step 5)">
    The engine submits the gap inventory to Google Keyword Planner in batches, pulls 12-month Google Trends curves for each keyword, computes Vortex IQ's own Keyword Difficulty (KD) score from SERP signal strength, deduplicates near-variants, classifies intent (transactional, commercial, informational, navigational), and shortlists the top 1,000 keywords ranked by composite score.

    **Artifacts produced:** `master-keywords.csv`, `top-1000.csv`, per-keyword `trends/{keyword}.json`, `keyword-clusters-preview.json`.
  </Step>

  <Step title="Content Production (Conversational Query Mining - Step 6)">
    The engine mines conversational long-tail queries from People Also Ask, Reddit, Quora, forum discussions, AI-engine completion logs, and voice-search transcripts. It tags each query by buyer intent (awareness, consideration, decision) and maps it to a pillar candidate. For UK Vape World this step surfaced 25,640 conversational queries assigned across 8 pillar categories at 100% category coverage.

    **Artifacts produced:** `conversational-queries.csv`, `query-categories.json`, `recommendations.md`, `gap-coverage.json`.
  </Step>

  <Step title="Current Page Optimisation (Steps 7 and 10)">
    **Step 7 - Pillar Architecture** clusters every keyword and conversational query into 8 to 12 pillars, each with a hub page brief, a spoke list (typically 8 to 20 spokes per pillar), and a cluster-to-pillar mapping. Blue-ocean pillars where competitor coverage is weak are flagged for fast-track treatment.

    **Step 10 - SEO Optimization Layer** scores every URL on a composite covering Technical SEO, Content & on-page, GEO readiness, and Page experience, then produces a per-URL fix list. For UK Vape World the GEO readiness score moved from 6.7 to a target of 85 once the citation blocks from Step 9 were deployed.
  </Step>

  <Step title="Topic / Keywords / KD / Traffic (Position Estimation - Step 8)">
    The engine runs every hub and spoke through a ranking projection model and writes back a 90-day projected position alongside current position, keyword volume, keyword difficulty, confidence rating (low, medium, high), and projected monthly clicks weighted by SERP CTR curves.

    For UK Vape World the run projected 13,007 monthly clicks at the 90-day horizon across 3,961 keyword positions and 8 pillars. On historical projects the engine's projected rank lands within 3 positions of actual rank for 78% of URLs at the 90-day mark when content is published as planned.
  </Step>

  <Step title="Keyword Position Tracker (Steps 11 and 12)">
    **Step 11 - Deployment Calendar** sequences the pillar architecture into a 13-week publish schedule - for UK Vape World that was 105 articles, 8 articles per week, with pillars ordered by projected clicks per pillar. Colour-coded calendar cards show each article's pillar, status (Briefed, In Production, Ready, Live), estimated reach, and owner.

    **Step 12 - Operations Pack** assembles the complete runbook: per-article workflow, pre-publish checklist, post-publish playbook, monitoring KPIs, rollback policy, and quarterly review cadence - all linked to live workspace tools (Kanban, Vortex Apps, Vortex Mind, Ask Viq).
  </Step>
</Steps>

## GEO: building for AI-search alongside Google

GEO (Generative Engine Optimisation) is not a separate module - it is integrated into every step of the engine.

<AccordionGroup>
  <Accordion title="AI-search readiness">
    Step 9 writes a GEO answer-readiness specification for every URL: the standalone-quotable paragraph format, the citation hook, and the brand mention pattern that AI assistants can quote without surrounding context. Step 10 scores each URL's GEO readiness and flags what needs to change.
  </Accordion>

  <Accordion title="Citation surface">
    Step 3 (AI Engine Baseline) measures your brand's current citation rate across ChatGPT, Perplexity, Google AI Overviews, Gemini, and Claude using a structured set of buyer-intent prompts. The missed-prompt list feeds directly into Step 4's gap analysis so content is planned specifically to close the AI-citation gap.
  </Accordion>

  <Accordion title="Brand mention readiness">
    Step 7's pillar briefs include both the traditional SEO target (head term, schema, internal-link signals) and the GEO target: the answer-readiness format, citation pattern, and brand mention pattern. One architecture, both surfaces.
  </Accordion>

  <Accordion title="Knowledge-graph optimisation">
    Schema markup targets are specified per URL in Step 9 - Article, Product, FAQ, HowTo, Review - with the property fields the engine expects to see populated. Correct schema is a primary signal for both Google featured snippets and AI-search citation.
  </Accordion>
</AccordionGroup>

## The approval model

Every step has an approval gate. The agent runs the step and generates the artifacts. You review. If the artifacts look right, click **Approve** and the next step unlocks. If something is off, click **Reset** at the top right to re-run with adjusted inputs. The engine never moves from one step to the next without your explicit approval.

Each approval is recorded with an audit note in Vortex Memory so the team can trace any content or architecture decision back to when it was made and who approved it.

## Cross-links

* Start a new project: navigate to `app.vortexiq.ai/v2/seo-engine/projects/` and click **New project**
* Content planning context: [Vortex Mind](/vortex-mind)
* Resolution tracking: [Kanban Board](/actions/overview#the-kanban-board)
* Voice and tone constraints: [Bulk Content Edit - Rules Profiles](/actions/bulk-content-edit)


# Run a full Vortex IQ store audit
Source: https://docs.vortexiq.ai/actions/store-audit

Store Audit scans every connected source for issues and opportunities, ranks findings by revenue impact, and pushes them to your Kanban Board for resolution.

Store Audit answers the question every merchant asks every morning: what is broken, underperforming, or quietly leaking revenue across my store right now? It lives at `app.vortexiq.ai/v2/store-audit` and it is the most-clicked button on the Vortex Agents hub. One scan. Every connected source. Findings ranked by revenue impact, not by alphabetical order or arbitrary severity. The audit itself is read-only and never changes your store. Each finding becomes a ranked card that a Vortex Agent can resolve with an approval-gated fix that is reversible by default, so you audit and fix safely, with one-click rollback.

Unlike traditional site auditors that hand you a PDF of technical flags, Store Audit reads from every connector wired into your workspace - Shopify or BigCommerce for catalogue and order signals, Google Analytics 4 for traffic and behaviour, Google Search Console for ranking surface, Google Ads for paid spend efficiency, Stripe and PayPal for payment performance, Datadog and New Relic for infrastructure health, and more. Findings come back contextualised: not "page X has a missing meta description" but "16 e-commerce scripts in `<head>` blocking First Contentful Paint, projected revenue impact 0.7% conversion lift if removed."

## The five Store Audit actions

<AccordionGroup>
  <Accordion title="Run Full Store Audit">
    The headline button. One click scans every connected source, scores each finding against the severity model, and pushes the results to the Latest Findings dashboard and (by default) your Kanban Board. Runs are asynchronous - leave the page and come back when it is done. Typical run time is 4 to 12 minutes for 4 to 6 connectors; larger catalogues can take up to 25 minutes.
  </Accordion>

  <Accordion title="Latest Findings">
    The live findings dashboard. Filter by severity (Critical, High, Medium, Low, Warning, Passed) and by source connector (Catalog, Theme, GA4, Ads, Klaviyo, and one chip per live connector). Each finding row shows the finding name, severity badge, source, the time it was first surfaced, and a **Board** button to push it to the Kanban Board.
  </Accordion>

  <Accordion title="Customer Journey Test">
    Ask Viq walks a specific customer journey end-to-end - homepage to purchase, category to add-to-cart, cart abandonment recovery, and more - and reports every point of friction as a Kanban-ready task. Specify the device (desktop, mobile, tablet), locale, and customer profile (new, returning), or write a free-text journey description.
  </Accordion>

  <Accordion title="UI/UX Regression Test">
    Runs a configured script of customer flows on every release event and surfaces any flow that regressed since the previous approved baseline. Catches theme regressions, schema regressions, broken redirects, and layout shifts before customers notice them. Wire it to a Shopify theme-publish webhook or BigCommerce theme-update webhook for automatic post-deploy checks.
  </Accordion>

  <Accordion title="Generate New Page / Design Change">
    The proactive action. Ask Viq reads your audit findings, Vortex Mind context, and SEO project to propose new landing pages or design changes optimised for sales. Each proposal includes a draft artifact, the reasoning behind it, a projected revenue impact range, and a Kanban-ready card for review.
  </Accordion>
</AccordionGroup>

## Running a full store audit

<Steps>
  <Step title="Open Store Audit">
    Navigate to `app.vortexiq.ai/v2/store-audit`. Check the source filter rail to confirm that your expected connectors - Shopify, GA4, Google Search Console, Google Ads, Stripe, and so on - are visible.
  </Step>

  <Step title="Click Run Audit">
    Click **Run Audit** in the top right. The header cards switch to a "running" state. A progress strip across the findings table shows completion percentage by connector. An Agent Log on the right side streams the agent's reasoning in real time.
  </Step>

  <Step title="Wait for results">
    The audit runs asynchronously. You can leave the page and come back. If a connector errors out - for example, an expired token - the run logs it as *partial* and continues with the remaining connectors. The header marks partial sources with an asterisk.
  </Step>

  <Step title="Review the header summary">
    When the run completes, four header cards refresh: **Stores audited**, **Critical issues**, **Warnings**, and **Checks passed**. A right-hand summary card shows your overall **AI Intelligence Score** - for example, 30 of 35 - so you can track absolute store quality from one run to the next.
  </Step>

  <Step title="Explore the findings dashboard">
    The findings table groups results by severity band. Use the severity tabs (All, Critical, High, Low, Warning, Passed) and source tabs (All Sources, Catalog, Theme, GA4, Ads, Klaviyo, ...) to scope the view. Click any finding row to expand the full description, the list of affected items, the recommended fix path, and the history strip.
  </Step>

  <Step title="Push findings to the Kanban Board">
    Click the **Board** button on any finding to send it to your Kanban Board as a card. If automation rules are configured, findings route automatically to the right column, swimlane, or assignee the moment the audit completes - for example, critical findings to In Review for engineering review, SEO findings to a Marketing swimlane.
  </Step>
</Steps>

## What the findings dashboard shows

The findings table groups every result into colour-coded severity bands.

| Severity          | Badge colour | What it means                                                                   |
| ----------------- | ------------ | ------------------------------------------------------------------------------- |
| **Critical**      | Red          | Blocking revenue right now. Act within 24 hours.                                |
| **High**          | Dark orange  | High-impact issues to resolve this week.                                        |
| **Medium**        | Amber        | Issues that should be in the resolution queue but are not yet bleeding revenue. |
| **Low**           | Light amber  | Minor issues - often cosmetic or efficiency-driven.                             |
| **Informational** | Blue         | State descriptions that do not need action but explain the store.               |
| **Checks passed** | Green        | Everything that ran clean.                                                      |

Each finding row shows the finding name, the severity badge, the source connector that surfaced it, when it was first detected, and the **Board** action. Click the row to open the per-finding panel, which includes the full description, the affected items list (every URL, SKU, or transaction the finding applies to), a recommended fix path - often a one-click action to open the right Vortex IQ tool with affected items pre-loaded - a Vortex Mind cross-link if the finding is downstream of a diagnostic report, and the finding's history strip showing recurrence and prior resolution dates.

### How severity is scored

Severity in Store Audit is a composite of three signals, not a single check rule:

1. **Detected impact** - what is this finding actually doing to traffic, conversion, AOV, or revenue right now?
2. **Reach** - how many URLs, products, customers, sessions, or transactions does it affect?
3. **Reversibility** - how hard is it to undo if you act and turn out to be wrong?

The underlying score is inspectable on the per-finding detail panel and stored in Vortex Memory for retroactive analysis.

## When to run a store audit

| Mode          | Cadence                     | Use case                                                                                        |
| ------------- | --------------------------- | ----------------------------------------------------------------------------------------------- |
| **Scheduled** | Daily (typically overnight) | Drift detection, fresh findings for the morning briefing, low time-to-resolution on regressions |
| **On-demand** | After every deploy          | Catch theme regressions, schema regressions, and redirect-chain breakage immediately            |
| **On-demand** | Before every campaign       | Pre-flight check before Black Friday, seasonal launches, or paid-spend bursts                   |

<Note>
  Every AI-generated change that comes out of a Store Audit finding - whether applied through Bulk Content Edit, an Ask Viq fix-and-deploy, or a Generate New Page proposal - goes through your approval queue before it touches the live store. The audit itself is strictly read-only: it never writes back to your storefront or to any connected connector.
</Note>

## Cross-links

* Findings push to: [Kanban Board](/actions/overview#the-kanban-board)
* Bulk fixes applied via: [Bulk Content Edit](/actions/bulk-content-edit)
* Diagnostic context: [Vortex Mind](/vortex-mind)


# Ask Viq example queries by business function
Source: https://docs.vortexiq.ai/ask-viq/examples

Example Ask Viq queries for commerce, payments, ads, fulfilment, customer, and finance teams - showing what to ask and what Ask Viq returns.

Ask Viq handles plain-English questions across every business function in your ecommerce operation. The examples below show the literal question to type into the chat input, the Profile to select from the dropdown, and the shape of the answer Ask Viq returns - including which Nerve Centre cards and Vortex Mind reports back each response. None of the answers below are invented; every claim in a real Ask Viq response carries a citation you can click into.

<Tabs>
  <Tab title="Commerce">
    Select your **commerce-sources** Profile before asking these questions. A commerce-sources Profile typically contains your commerce platform connector (Shopify, BigCommerce, or Adobe Commerce), Stripe, GA4, and Klaviyo - the four sources that together explain most revenue and product questions.

    ***

    **Which SKUs drove the most refunds last week?**

    Ask Viq reads the refund rate card on your commerce connector, breaks it down by SKU for the last 7 days, and ranks the results by refund volume and refund revenue. The answer surfaces a table showing each SKU, its refund count, its refund value, and its refund rate as a percentage of orders - all cited to the `refund_rate` card on the active connector.

    If a Vortex Mind report has run during the period that flagged a quality-control or fulfilment issue behind the spike, Ask Viq cites that finding in the narrative and links through to the full report so you can see the evidence. A SKU-level refund spike almost always has one of three causes - a quality issue on a specific batch, a courier failure on a specific route, or a product description that does not match what arrived - and Ask Viq names which pattern fits the data.

    ***

    **What is my margin by product after landed costs?**

    Ask Viq reads the SKU-level margin card from your commerce connector, layers in the landed-cost trace (wholesale cost, freight, duty, inbound handling), and computes realised margin per product for the period you specify. The answer opens with a headline gross margin figure, then ranks the top contributors to any compression quarter over quarter.

    For each SKU where margin has moved more than your configured threshold, Ask Viq surfaces the specific cause: a freight surcharge that started on a particular date, a supplier wholesale increase, or a discount-promotion calendar that continued to run on a SKU whose cost had already risen. The landed-cost trace is cited to the cost fields in your commerce platform or ERP connector, so you can verify the breakpoint date and the size of the move.

    <Tip>
      Set cost-of-goods on every SKU in your commerce platform. If cost is not set, Ask Viq falls back to retail price and flags the missing-cost SKUs in a data-quality footnote. Accurate landed cost data is what makes the margin answer actionable rather than directional.
    </Tip>
  </Tab>

  <Tab title="Payments">
    Select your **payment-sources** Profile before asking these questions. A payment-sources Profile typically contains your payment gateway connector (Stripe, PayPal, Adyen, or equivalent) plus your commerce platform connector - the order context from the commerce connector is what allows Ask Viq to break down decline rates by currency, customer country, basket value, and card type.

    ***

    **Why did checkout conversion drop on Tuesday?**

    Ask Viq reads the checkout conversion rate card, the auth rate card, and the 3DS abandon rate card across a comparison window centered on Tuesday. It then looks for a Vortex Mind finding - from the Checkout Conversion Failure or Payment Performance Intelligence report - that diagnosed a causal pattern during that period.

    The answer distinguishes between three different failure surfaces: pre-payment abandonment (the customer left before entering card details, visible in the checkout conversion card), issuer decline (the customer submitted payment but the bank declined, visible in the auth rate and decline reason cards), and 3DS abandonment (the customer was challenged and did not complete, visible in the 3DS abandon rate card). Each surface has a different fix. Ask Viq sizes each one and names which was responsible for Tuesday's drop, with BIN-level or device-level detail when that granularity is in the connected data.

    ***

    **Which payment methods have the highest decline rate?**

    Ask Viq reads the decline rate card segmented by payment method - credit card, debit card, PayPal, BNPL, digital wallet - and ranks them for the period you specify. The answer shows each method's decline rate, the primary decline reason codes driving it, and the change versus the prior period.

    For gateway connectors that expose issuer-country breakdowns, Ask Viq also surfaces which card-issuing countries are dragging any particular method's rate. A UK-issued debit card may decline at twice the rate of a US-issued credit card if a UK challenger bank recently tightened its fraud rules. Ask Viq cites the specific decline reason code distribution - "do not honor", "insufficient funds", "fraudulent", "card declined" - so you can distinguish customer-error declines (which your team cannot fix) from issuer-side fraud-rule declines (which you can often recover through Stripe Adaptive Acceptance, retry routing, or a case with the issuer).

    The Decline Recovery Intelligence report run, if recent, is cited inline and contains the sized recoverable pool for each method - the amount of declined revenue that would have approved through a different routing or retry path.
  </Tab>

  <Tab title="Ads">
    Select your **marketing-sources** Profile before asking these questions. A marketing-sources Profile typically contains Google Ads, Meta Ads, Amazon Ads, TikTok, GA4, and your commerce platform - the combination that allows Ask Viq to compare ROAS across channels using cross-platform attribution rather than each platform's own pixel.

    ***

    **Which campaigns are losing money this week?**

    Ask Viq reads campaign-level ROAS from every ad platform in the active Profile, applies the GA4 cross-platform attribution adjustment to de-duplicate conversions claimed by multiple platforms, and ranks campaigns by net loss against your configured break-even ROAS threshold.

    The answer is a ranked pause-list: campaign name, platform, spend in the period, attributed revenue, reported ROAS, cross-platform ROAS, duration below break-even, and the modelled weekly saving from pausing. Ask Viq also surfaces two kill-shot patterns at the top of the list - campaigns sending paid traffic to out-of-stock SKUs (zero revenue, not a low ratio) and campaigns with disapproved ad copy that has been running for more than 24 hours. Both produce zero or near-zero revenue while spend continues.

    The Paid Traffic Waste report, if run for the period, is cited and contains a per-campaign pause recommendation with the sized impact of each.

    ***

    **What is wasted spend across all ad platforms?**

    Ask Viq reads the wasted-spend alert cards from each connected ad platform - overspending cards, disapproved-burst cards, and the cross-platform ads-on-out-of-stock card that joins ad spend to inventory state by SKU - and produces a consolidated wasted-spend figure across all platforms in the Profile.

    The answer breaks wasted spend into categories: spend on out-of-stock or slow-moving SKUs (the cross-platform kill-shot), spend on campaigns below break-even ROAS for more than your configured threshold, spend on disapproved ads, and spend on seasonal SKUs promoted out of season. Each category is sized in the period's currency and cited to the specific card or Vortex Mind finding that identified it.

    For each wasted-spend category, Ask Viq surfaces the modelled saving from addressing it and the modelled lost revenue from doing so - the net weekly improvement number. Ask Viq does not pause campaigns automatically; it surfaces the recommendation and the sized impact so you or your team can act on it.
  </Tab>

  <Tab title="Fulfilment">
    Select your **operations-sources** Profile before asking these questions. An operations Profile typically contains your fulfilment connector (ShipBob, ShipStation, ShipMonk, or equivalent), your courier connectors (Royal Mail, FedEx, DPD, UPS), and your commerce platform for order context.

    ***

    **Which carrier has the worst on-time delivery rate?**

    Ask Viq reads the carrier performance card from your fulfilment connector, which tracks on-time delivery rate per carrier for the active period, and ranks carriers from worst to best. The answer shows each carrier's on-time rate for the last 14 days versus the trailing 30-day baseline, the change in percentage points, and the number of late shipments attributed to each.

    Where the carrier performance drop is concentrated in a specific region, a specific service tier (next-day versus tracked-48), or a specific warehouse origin, Ask Viq surfaces that breakdown using the per-warehouse fulfilment time card and the delayed orders card. The narrative distinguishes between carrier-side delays (the warehouse picked on time but the courier was slow) and warehouse-side delays (the pick time itself has extended, independent of courier performance) - because the fix for each is different.

    If a Vortex Mind Customer Recovery Opportunity report has run recently, Ask Viq cites it and surfaces the count of customers who received a late delivery and are at risk of not returning - giving you both the operational picture and the customer impact in the same answer.
  </Tab>

  <Tab title="Customer">
    Select your **customer-sources** Profile before asking these questions. A customer-sources Profile produces the richest churn and retention answers when it contains your commerce platform, your email connector (Klaviyo or Mailchimp), and your payment gateway - each connector contributes different churn signals that combine into a more complete picture.

    ***

    **Which customers are at risk of churning?**

    Ask Viq runs the Customer Recovery Opportunity churn-signal scanner across the customer-sources Profile and returns a ranked, contactable list of at-risk customers. The scanner detects six signal types: a drop in order frequency versus the customer's historical cadence, an email engagement collapse (open rate falling from a stable baseline to under 10 percent for four consecutive weeks), a subscription pause without restart inside 30 days, a failed payment with no successful retry inside 14 days, a refund or chargeback in the last 30 days, and an unsubscribe from a flow the customer was previously engaged with.

    Each customer in the at-risk pool receives a priority score - likelihood of churn multiplied by lifetime value - which determines their position in the ranked list. The answer opens with headline counts (total at-risk customers, combined lifetime value at risk, customers in the red zone with three or more signals), then renders the top 5 of the ranked list as a preview with a deep link to the full Customer Recovery Opportunity report run for the complete list.

    For each customer in the ranked list, Ask Viq surfaces the recommended outreach channel (personal email, Klaviyo recovery flow, SMS, or automated email with a payment-alternatives link) and the template recommended for that channel - ready for your customer success team to use directly.
  </Tab>

  <Tab title="Marketing">
    Select your **marketing-sources** Profile before asking these questions. A marketing-sources Profile for email attribution questions should contain your email connector (Klaviyo or Mailchimp), your commerce platform, and GA4 - the combination that allows Ask Viq to compute email revenue attribution using cross-platform logic rather than the email platform's own last-click window.

    ***

    **What is my email revenue attribution this month?**

    Ask Viq reads the email revenue per recipient card, the flow revenue card, and the campaign revenue card from your email connector for the current month, then cross-references the GA4 conversion-by-source card to apply a cross-platform attribution adjustment that de-duplicates revenue claimed by both email and paid channels.

    The answer breaks email revenue attribution into two streams: campaign revenue (manually triggered broadcasts) and flow revenue (automated lifecycle messages). Within flows, Ask Viq ranks the top revenue-producing flows - welcome series, abandoned cart, post-purchase, win-back - and surfaces any flow where revenue per recipient has dropped materially from its trailing baseline, with the likely cause named (a subject-line change, a step deleted from the flow, a commerce platform regression that reduced the clickable cart pool).

    If a recent Vortex Mind diagnostic flagged a specific flow as underperforming, Ask Viq cites that finding inline and links to the full report for the evidence and recommended fix.
  </Tab>

  <Tab title="Finance">
    Select your **finance-sources** Profile before asking these questions. A finance-sources Profile typically contains your ERP or accounting connector (NetSuite, Xero, QuickBooks, Sage), your payment gateway, and your commerce platform - the three sources whose revenue numbers must reconcile at month-end.

    ***

    **What is today's revenue leakage vs the GL booking?**

    Ask Viq reads the commerce revenue card and the finance revenue card for the period you specify, computes the gap between them, and decomposes the gap into its constituent causes using the Daily Revenue Leakage report. The cause taxonomy covers the most common reconciliation gaps: pending invoices (commerce-booked orders not yet posted to the GL), voided orders whose reversal did not flow through, unmapped SKUs that have no GL item code, unreconciled returns, currency mismatches, tax mismatches, and marketplace orders that bypass the commerce connector.

    Each cause is sized in your workspace base currency and the answer surfaces the top five orders by gap value for each cause, with deep links into the order detail in both your commerce platform and your finance system. For causes that resolve automatically (pending invoices typically close out by the seventh business day of the new month), Ask Viq says so rather than treating them as a problem requiring action. For causes that require intervention - unmapped SKU item codes, voided orders not reversed in commerce reporting - Ask Viq surfaces the recommended action and the team responsible for it.

    The Daily Revenue Leakage report run is cited at the close of the answer, linking to the full per-order audit list so your finance team has the audit-grade detail alongside the plain-English summary.
  </Tab>
</Tabs>

## Tips for asking effectively

A high-value Ask Viq question carries three pieces of information: the metric or entity you are asking about, the time window the data is from, and an optional comparator (versus last month, by region, ranked by performance). Combine the three and the question shape maps directly onto how Ask Viq's substrate is organised.

<CardGroup>
  <Card title="Patterns that work" icon="check">
    Diagnostic questions ("why did X move?"), time-windowed reads ("what was X last 7 days?"), comparative questions ("which of my campaigns has the highest ROAS?"), dashboard reads ("give me my current KPI summary"), and drill-downs on a prior answer ("now break that down by region").
  </Card>

  <Card title="Patterns to avoid" icon="xmark">
    Vague open-ended questions with no metric or time window, future projection requests ("what will my revenue be next quarter?"), opinion-asking questions ("should I cancel Klaviyo?"), and questions requiring a source not in the active Profile - Ask Viq will name the missing connector in its reply.
  </Card>
</CardGroup>


# Ask Viq: plain-English queries over your store data
Source: https://docs.vortexiq.ai/ask-viq/overview

Ask Viq is Vortex IQ's conversational layer. Ask any question about your store in plain English and get cited, verified answers from your live connector graph.

Ask Viq is the conversational interface of Vortex IQ. You type any question about your store in plain English - "which campaigns are losing money this week?", "why did refunds spike on Tuesday?", "what's my margin by SKU after landed costs?" - and Ask Viq routes the question against your connected sources, finds the relevant data, and returns an answer with cited sources you can click into. Every answer traces back to a real data point. Nothing is invented.

<Note>
  The brand name is always written as two words: **Ask Viq**. Never abbreviate it to "Viq" alone. This applies everywhere - in documentation, in product copy, and in any generated prose.
</Note>

## How Ask Viq differs from a chatbot

Most ecommerce chat tools wrap a language model around one platform's data and call it AI. Ask Viq is different because it sits at the centre of the Vortex IQ AI OS and reads from the entire connected graph: over 200 connectors, more than 7,000 KPI cards, every Vortex Mind report archived in Vortex Memory, and the structured findings the audit engine has produced over time.

When you ask Ask Viq a question, it does not guess. It routes your question against the four bodies of data that make up the AI OS substrate, composes an answer from what it finds, and attaches a citation to every factual claim. You can click any citation and land on the underlying source - the same live data your dashboard shows.

## What you can query

Ask Viq draws answers from four bodies of data, all filtered by your active Profile.

<CardGroup>
  <Card title="Nerve Centre cards" icon="chart-line">
    Over 7,000 live KPI cards across more than 200 connectors. Every metric the active Profile has a connected source for is reachable - total revenue, auth rate, refund rate, ROAS by campaign, and thousands more. Card definitions are stable and reconcile to the vendor's own dashboard.
  </Card>

  <Card title="Vortex Mind reports" icon="magnifying-glass-chart">
    The structured findings from every Vortex Mind diagnostic run: cause, evidence, severity, and suggested action. All seven Vortex Mind report types write findings into the same archive, and Ask Viq reads from all of them without you needing to know which report produced which finding.
  </Card>

  <Card title="Vortex Memory" icon="database">
    Knowledge files you have uploaded (PDFs, spreadsheets, policy documents, supplier catalogues) plus every archived Vortex Mind report run - giving Ask Viq longitudinal context that deepens the longer you use the platform.
  </Card>

  <Card title="The connector graph" icon="diagram-project">
    Cross-connector joins that no single tool in your stack can produce alone: ad spend against inventory state by SKU, Stripe declines against order history by customer, Klaviyo flow recipients against the order index by date.
  </Card>
</CardGroup>

## Hallucination guardrails and citations

Ask Viq is engineered around three layers of guardrails that make hallucination structurally unlikely rather than statistically rare.

<Note>
  Every factual claim in an Ask Viq answer carries a citation. Numbers come from named Nerve Centre cards. Diagnostic narratives come from named Vortex Mind report runs. Reference statements come from named Vortex Memory files. You can click any citation and land on the underlying source in two clicks. Citation enforcement is structural - the model cannot emit a number that did not originate in a cited source.
</Note>

<Steps>
  <Step title="Layer 1 - Required citations">
    Every numerical claim must carry a citation token pointing to a specific card, finding, or file. If the model generates a number it cannot trace to a cited source, the answer is rejected and regenerated before it reaches you. This layer is not configurable - it is a structural property of the AI OS.
  </Step>

  <Step title="Layer 2 - Workspace AI Guardrails">
    Your workspace admin can maintain a forbidden-words list on the Settings, Brand and AI tab. Every Ask Viq generation is filtered against it. Brand-protection language, regulatory claims, and competitor names you want excluded never surface in generated prose - regardless of how a question is phrased or which Brand Voice Profile is active.
  </Step>

  <Step title="Layer 3 - Model-level prohibitions">
    Ask Viq will not project beyond available data, will not opine on plan tier or pricing, will not invent business context that has no uploaded file behind it, and will not produce statements about data outside your active Profile. These rules apply universally and cannot be bypassed through prompt engineering.
  </Step>
</Steps>

When any layer blocks an answer, Ask Viq returns a clear, polite limit message rather than a fabricated response. You always know when data is unavailable and why.

## Query history

Ask Viq is not a stateless chat. Every conversation persists as a named session in the left sidebar, grouped by date band ("Today", "Yesterday", "Apr 2026", "Mar 2026"). You can pin sessions you return to often, search across every session you have ever had, and export any session in three formats.

<Accordion title="What is stored with each session">
  Every session records the question text exactly as typed, the Profile that was active, the user who asked, the full structured response including all citations, the "as of" timestamps from each cited source, and the pin and archive state. History is retained indefinitely by default; workspace admins can configure a retention policy under workspace admin settings.
</Accordion>

<Accordion title="How follow-ups work within a session">
  Within a single session, Ask Viq carries context from prior turns. You do not need to restate the time window or entity on every follow-up. "Now break that down by region" works because the prior turn's metric and window carry forward automatically. Across sessions, context resets unless you pin and reuse a session.
</Accordion>

<Accordion title="Searching across history">
  The search box at the top of the sidebar searches across every session you have access to - matching question text, answer text, session title, and citation source names. A search for "refund\_rate" surfaces every session that ever cited that card. Search respects Profile and permission boundaries.
</Accordion>

<Accordion title="Exporting a session">
  Any session can be exported as HTML (full thread with citations, formatted for sharing), Markdown (prose only, for pasting into a document), or JSON (structured form with question, answer, citations, profile, and timestamps, for programmatic processing or audit review).
</Accordion>

<Accordion title="How memory makes answers richer over time">
  The longer your workspace uses the platform, the more material accumulates in Vortex Memory. After a year, multiple seasonal cycles are captured as archived report runs. Ask Viq can reach into past Novembers to answer "why does refund rate always spike in late November?" and surface recurrence detection - "this looks similar to the issue you saw on 03 Mar 26, here is what was done about it then." That institutional memory survives personnel turnover.
</Accordion>

## How Ask Viq connects to other modules

| Module                 | What Ask Viq draws from it                                                              |
| ---------------------- | --------------------------------------------------------------------------------------- |
| Nerve Centre           | Live KPI cards - the primary substrate for current-value questions                      |
| Vortex Mind            | Structured diagnostic findings - the primary substrate for "why" questions              |
| Vortex Memory          | Knowledge files and archived report runs - longitudinal context and reference documents |
| Settings, Profiles     | The Profile registry that the Profile dropdown reads live                               |
| Settings, Brand and AI | Guardrails configuration and Brand Voice Profile shape                                  |


# Use Profiles to scope Ask Viq to the right data
Source: https://docs.vortexiq.ai/ask-viq/profiles

Profiles group connected sources so each team's Ask Viq questions run only against their relevant data - marketing, finance, or operations sources.

The single most important control in Ask Viq is the **Profile dropdown** at the top of every chat. Every question you type is answered against only the connected sources inside the active Profile. Pick the right Profile before you ask a question and Ask Viq routes against exactly the data you need. Pick the wrong one and you get a polite scope-limit notice instead of an answer.

## What Profiles are

A Profile is a named group of connected sources. When you select a Profile from the dropdown, Ask Viq answers every question in that chat against only the connectors that Profile contains - nothing more, nothing less.

A single workspace can have many Profiles running in parallel. A marketer opens a marketing-sources Profile that contains Google Ads, Klaviyo, and GA4. A finance director opens a finance-sources Profile that contains NetSuite, Stripe, and the commerce platform's payouts feed. Same Ask Viq UI, same workspace, completely different data scope. The right answers reach the right team without manual filtering.

<Tip>
  Create a distinct Profile for each team or business function - marketing, finance, operations, customer success. When a question needs a connector that is not in the current Profile, Ask Viq names the missing connectors in the limit message so you know exactly what to add or which Profile to switch to.
</Tip>

## How to create a Profile

Profiles are created in Settings, not inside Ask Viq itself. The Profile dropdown is a live read of the Profiles tab - any Profile you save on the Settings page appears immediately in the dropdown for every assigned user, with no separate publish step.

<Steps>
  <Step title="Open Settings, Profiles tab">
    Navigate to **Settings** in the workspace header, then select the **Profiles** tab. You see the list of all existing Profiles in the workspace, each showing its name, connector count, and assigned users.
  </Step>

  <Step title="Click New Profile">
    Click **New Profile** to open the Profile editor. Give the Profile a name that maps to its business function - "Marketing sources", "Finance sources", "Operations", or a storefront name like "UK BigCommerce".
  </Step>

  <Step title="Add connectors">
    Select the connectors that belong to this Profile from your workspace's connected sources list. A connector can belong to multiple Profiles - a Shopify storefront commonly sits in a marketing Profile alongside Google Ads and Klaviyo, and also in a finance Profile alongside Stripe and PayPal.
  </Step>

  <Step title="Assign users">
    Select the workspace users who should have access to this Profile. A user sees only the Profiles they are explicitly assigned to in their dropdown. Workspace admins always see every Profile.
  </Step>

  <Step title="Save">
    Click **Save**. The Profile appears immediately in the Ask Viq dropdown for every assigned user. No restart or publish step is required.
  </Step>
</Steps>

## Using the Profile dropdown in Ask Viq

The Profile dropdown sits at the top of every Ask Viq chat, just above the message thread. The currently active Profile is shown as the dropdown label. Click the chevron to open a panel listing every Profile you have access to, each with a small connector-icon strip so you can see at a glance which sources it is wired to.

<Tabs>
  <Tab title="Starting a chat">
    Before you type your first question, confirm that the Profile dropdown shows the right Profile for your question. A finance question asked from a marketing-sources Profile returns a scope-limit notice because Stripe is not in scope. Switching takes one click.
  </Tab>

  <Tab title="Switching mid-chat">
    You can change Profile during a conversation. The chat thread up to that point is preserved and remains readable. New questions after the switch are scoped to the new Profile. Ask Viq inserts a small inline notice - "Profile switched to \[new profile name]" - at the boundary so the conversation history stays readable later. The recommended pattern is one Profile per chat session.
  </Tab>

  <Tab title="Remembering your last selection">
    Ask Viq remembers the Profile you last used per browser session. The next time you open Ask Viq the dropdown defaults to your most recent selection.
  </Tab>
</Tabs>

## Multi-tenant use case

Profiles are the mechanism that makes Ask Viq multi-tenant inside a single workspace. Consider a workspace running three functions:

| Team       | Profile name      | Connectors in scope                      | Questions they ask                                                                     |
| ---------- | ----------------- | ---------------------------------------- | -------------------------------------------------------------------------------------- |
| Marketing  | Marketing sources | Google Ads, Meta, Klaviyo, GA4           | "Which campaigns are losing money?", "What is my email open rate trend?"               |
| Finance    | Finance sources   | Stripe, NetSuite, Shopify payouts        | "Reconcile last month's revenue against the GL", "What is today's auth rate?"          |
| Operations | Operations        | ShipBob, Royal Mail, DPD, Shopify orders | "Which carrier has the worst on-time rate?", "What's our fulfilment SLA breach count?" |

One workspace, one Ask Viq UI, three completely isolated question scopes. A marketer asking from the marketing Profile cannot accidentally surface finance data even if they phrase a finance-sounding question, because the routing layer only has access to the connectors inside the active Profile.

## AI-suggested Profiles

For workspaces with many connectors, the **Auto-Generate More** button on the Profiles tab analyses your connector mix and proposes sensible Profile groupings in a single bulk action. The suggestions are based on common business-function patterns across the connector catalogue. You review, edit, and save the proposed Profiles - the AI does the initial grouping work, you make the final call.

<Tip>
  Workspaces that have not yet organised their connectors into named Profiles see a single default Profile in the dropdown that includes every connected source. This works for getting started, but most workspaces graduate to two or three named Profiles within their first few weeks once the value of scoped questions becomes clear. Use Auto-Generate More to accelerate that step.
</Tip>

## How Profiles connect to sources

Each Profile is a scope filter that applies to everything Ask Viq draws from:

<Accordion title="Nerve Centre cards">
  Cards belonging to connectors outside the active Profile are not queried. Ask Viq only reads the card catalogue for the connectors your Profile contains.
</Accordion>

<Accordion title="Vortex Mind findings">
  Diagnostic findings on connectors outside the active Profile are not surfaced. A finding from the Payment Performance Intelligence report is only visible from a Profile that includes the relevant payment connector.
</Accordion>

<Accordion title="Vortex Memory">
  Knowledge files and archived report runs are filtered to those associated with the connectors in the active Profile. A finance document uploaded into a finance-only Profile is not visible when you are asking from a marketing Profile.
</Accordion>

<Accordion title="Profile permissions">
  A Profile is visible in your dropdown only if you have been assigned to it. A user assigned to two of a workspace's six Profiles sees only those two. The other four are not listed and cannot be discovered through the dropdown UI. There is no per-question override - the boundary is enforced at the data-fetch layer, not just in the UI.
</Accordion>

## Common questions

**Can I have a personal Profile only I can see?**
Yes. Create a Profile, assign only yourself, and it appears in your dropdown but no one else's. This is useful for ad-hoc analysis you do not want to surface in a teammate's dropdown.

**Can a Profile span multiple commerce platforms?**
Yes. A Profile can include Shopify, BigCommerce, and Adobe Commerce at once. Ask Viq joins across the connectors and answers questions like "which storefront has the highest AOV this month?" by querying all three.

**What if my question needs a source outside my current Profile?**
Ask Viq replies with a polite scope-limit notice naming the connectors it would have needed. You can then switch to a Profile that contains those connectors, or ask your admin to extend the current Profile on the Profiles tab.

**Why is one of the Profiles in my dropdown greyed out?**
That Profile exists in the workspace but you have not been assigned access. Ask your workspace admin to add you to the Profile on the Profiles tab. The greyed entry is informational - it lets you know the Profile exists without granting access.


# AbeBooks on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/abebooks

Monitor AbeBooks listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor AbeBooks listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=abebooks)

<CardGroup>
  <Card title="42">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (42)">
    ### Monitor performance

    42 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country**                 | Watch only         | AOV by Country.                                                                                                                                        |
        | **AbeBooks Health Score**          | Merchant rule      | Composite , feed-cycle-success x active-listing-pct x SLA-compliance x inverse stale-listings.                                                         |
        | **Avg Time to Process (hrs)**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Buyer Messages Unread**          | Merchant rule      | Open buyer messages awaiting reply , AbeBooks buyer-SLA tracker; ignored messages hit seller standing.                                                 |
        | **Dispatch SLA Compliance**        | Merchant rule      | % of orders dispatched before dispatch\_due\_by , drives AbeBooks seller standing.                                                                     |
        | **FTPS Connection / Auth Health**  | Merchant rule      | AbeBooks FTPS credentials don't expire on a schedule, but partner-side network drops and TLS-cert rotations happen , surface before the merchant notic |
        | **Inbound Orders File Lag**        | Merchant rule      | Hours since the last order file landed. AbeBooks drops order files multiple times per day; >12h is a probable upstream incident.                       |
        | **Last Successful Upload**         | Merchant rule      | Hours since the last /outbox/listings upload AbeBooks ack'd. Stale = feed cycle broken.                                                                |
        | **Late Order Processing Queue**    | Merchant rule      | Alerts for Late Order Processing Queue.                                                                                                                |
        | **Listings Processed With Errors** | Alert band 5 / 50  | Rows AbeBooks rejected during inbound processing , surface so the merchant fixes them before next upload.                                              |
        | **Listings Uploaded (24h)**        | Merchant rule      | Count of listing rows pushed in the last 24h via /outbox/listings , flat-file equivalent of a sync heartbeat.                                          |
        | **Orders / Day**                   | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Dispatch**               | Alert band 10 / 50 | Orders downloaded from /inbox/orders that haven't been dispatched yet.                                                                                 |
        | **Return Rate**                    | Alert band 5 / 15  | Returns are typical in book-trade (condition mis-match). >5% may signal grading drift on used stock.                                                   |
        | **Top Upload Error Types**         | Watch only         | Cluster of error\_message strings from inbound ack files , drives the 'fix once' feed-side bug list.                                                   |
      </Accordion>

      <Accordion title="Grow revenue (12 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                                      |
        | -------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**          | Alert band 0 / -5 | Useful tripwire for rare-book mix shifts , a falling AOV often means low-condition stock outselling first editions. |
        | **Listings Expiring Soon**       | Merchant rule     | Listings within N days of AbeBooks expiry , auto-relist or re-rank candidates before they drop out of search.       |
        | **Marketplace Fees Paid**        | Watch only        | Total AbeBooks fees in the period , referral + closing + per-item fees off the AbeBooks invoice feed.               |
        | **Oldest Pending Payout (days)** | Alert band 7 / 21 | Days since the oldest unreleased payout was queued , flags settlement delays before they hit working capital.       |
        | **Orders**                       | Watch only        | Description pending editorial review; the signal is live.                                                           |
        | **Pending Payouts**              | Watch only        | Sum of payouts AbeBooks owes but hasn't released , cash-flow visibility for the book-trade channel.                 |
        | **Revenue Over Time**            | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                           |
        | **Suspended / Pending Listings** | Alert band 5 / 50 | AbeBooks has hidden these from search until issues are fixed , direct revenue blocker.                              |
        | **Top Listings by Revenue**      | Watch only        | Top individual listings by revenue , listing-level (complements ab\_top\_titles which groups by ISBN).              |
        | **Top Titles by Revenue**        | Watch only        | Top books by ISBN by revenue , drives reorder-and-list-again decisions on velocity titles.                          |
        | **Total Revenue**                | Alert band 0 / -5 | Order totals from the inbox/orders feed for the period.                                                             |
        | **Total Transactions**           | Watch only        | Line-level transaction count over the period , complements ab\_order\_count (which is order-level).                 |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                       | Alert behaviour   | What it tracks                                                                                                  |
        | -------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------- |
        | **AbeBooks Share of Book-Trade Revenue**     | Watch only        | Channel mix card , flags when AbeBooks share rises / falls vs sibling book marketplaces.                        |
        | **Cancellation Rate**                        | Merchant rule     | Description pending editorial review; the signal is live.                                                       |
        | **Failed Batches (7d)**                      | Alert band 5 / 50 | Outbox files where AbeBooks responded with rejection in /inbox/acks , auth, schema, encoding.                   |
        | **ISBN Drift vs Alibris + Amazon**           | Alert band 5 / 50 | Same ISBN listed at materially different prices across the book-trade channels , MAP-style risk on rare titles. |
        | **Net Revenue (after commission + refunds)** | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                       |
        | **Rare-Book Price Floor Watch**              | Merchant rule     | First-edition / signed copies priced materially below the merchant's own DTC list , margin erosion risk.        |
        | **Revenue at Risk (live)**                   | Merchant rule     | Sum of (suspended\_listings x velocity x ASP) + (failed-upload backlog x avg ASP) , recoverable.                |
        | **Stale Listings (>180d no update)**         | Merchant rule     | Listings with no metadata refresh in 6 months , risk AbeBooks de-prioritising in browse.                        |
        | **Top-Velocity ISBNs Missing on AbeBooks**   | Merchant rule     | Velocity-proven ISBNs not even listed on AbeBooks , cheapest book-trade revenue lift available.                 |
      </Accordion>

      <Accordion title="Catalogue quality (5 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                          |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------- |
        | **Active Listings**           | Merchant rule      | Description pending editorial review; the signal is live.                                               |
        | **Feed Cycle Failure**        | Merchant rule      | Triggered when /outbox/listings has no confirmed ack in 48h , feed is blind, all listing changes stuck. |
        | **ISBN Coverage**             | Alert band 90 / 70 | % of listings with a valid ISBN , listings without ISBN are harder to match across book marketplaces.   |
        | **Listing Error Spike (24h)** | Alert band 5 / 50  | Alerts for Listing Error Spike (24h).                                                                   |
        | **Total Listings**            | Watch only         | Description pending editorial review; the signal is live.                                               |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **4 write** operations across inboxacks, inboxorders, inboxreturns, outboxlistings, outboxprices, outboxquantitys on AbeBooks. 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=abebooks)

    #### Ready to build your first AbeBooks 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | inboxacks         | 1               | 0                |
      | inboxorders       | 1               | 0                |
      | inboxreturns      | 1               | 0                |
      | outboxlistings    | 0               | 1                |
      | outboxprices      | 0               | 1                |
      | outboxquantitys   | 0               | 1                |
      | outboxwithdrawals | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ActiveCampaign on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/activecampaign

Monitor email revenue and deliverability for ActiveCampaign, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for ActiveCampaign, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=activecampaign)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="11">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (12 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                                                                   |
        | ----------------------------- | ----------------- | ------------------------------------------------------------------------------------------------ |
        | **Campaign Status Breakdown** | Merchant rule     | Campaigns grouped by status (sent, draft, scheduled).                                            |
        | **Checkout-to-Order Rate**    | Merchant rule     | Share of started checkouts that became paid orders.                                              |
        | **Click-to-Open Rate**        | Alert band 10 / 3 | Clicks as a share of opens - engagement quality independent of open-rate inflation.              |
        | **Conversion Rate**           | Merchant rule     | Orders as a share of emails sent. Ties send volume to revenue.                                   |
        | **Email Click Rate**          | Alert band 3 / 1  | Share of delivered emails that earned a click. The clearest engagement signal.                   |
        | **List Count**                | Merchant rule     | Number of audiences on the account.                                                              |
        | **Lists Overview**            | Merchant rule     | Every audience with its member count.                                                            |
        | **Revenue per Recipient**     | Merchant rule     | Revenue divided by emails sent. What each address is worth per send.                             |
        | **Revenue per Send**          | Merchant rule     | Revenue divided by emails sent - the efficiency of each send.                                    |
        | **Top Lists by Name**         | Merchant rule     | Largest audiences by member count.                                                               |
        | **Total Revenue**             | Merchant rule     | Placed-order revenue ActiveCampaign claims credit for in the conversion window. The hero number. |
        | **Total Sends**               | Merchant rule     | Total emails sent across campaigns in the window.                                                |
      </Accordion>

      <Accordion title="Run operations (9 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                               |
        | ----------------------------- | ------------------ | ---------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts.                                    |
        | **Email Open Rate**           | Alert band 25 / 15 | iOS Mail Privacy inflates this - pair with click-to-open for a truer signal. |
        | **Flow Count Summary**        | Merchant rule      | How many automations exist on the account.                                   |
        | **Flow Status Breakdown**     | Merchant rule      | Automations split by status (active, draft, paused).                         |
        | **Flow Trigger Types**        | Merchant rule      | Automations grouped by what triggers them.                                   |
        | **Flows List**                | Merchant rule      | Every automation and its current status.                                     |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                    |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to email in the window.                                    |
        | **Segments Overview**         | Merchant rule      | Saved segments and their sizes. Audit AC-LIST-001 fires below 3 segments.    |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                  | Alert behaviour      | What it tracks                                                                                   |
        | ----------------------- | -------------------- | ------------------------------------------------------------------------------------------------ |
        | **Bounce Rate**         | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation; audit AC-DEL-001 fires here. |
        | **Delivery Rate**       | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                        |
        | **Email Health KPIs**   | Merchant rule        | Delivered, bounced and unsubscribed at a glance - your deliverability vitals.                    |
        | **Engagement Funnel**   | Merchant rule        | Sent → Delivered → Opened → Clicked. Drop-offs expose deliverability vs content weakness.        |
        | **Refund Rate**         | Merchant rule        | Share of attributed orders later refunded.                                                       |
        | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam complaints per send. Above 0.1% puts deliverability at risk; AC-DEL-002 fires.              |
        | **Unsubscribe Rate**    | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.                       |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (11)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001, AC05`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Email Bounce Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AC02`
      </Accordion>

      <Accordion title="Inactive Automations">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AC01`
      </Accordion>

      <Accordion title="Limited Lists/Segmentation">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AC04`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AC03`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **2 write** operations across automations, campaigns, contacts, contactlists, lists, segments on ActiveCampaign. 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=activecampaign)

    #### Ready to build your first ActiveCampaign 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.

    <Accordion title="Browse the operations you can build with">
      | Resource     | Read operations | Write operations |
      | ------------ | --------------- | ---------------- |
      | automations  | 1               | 1                |
      | campaigns    | 1               | 0                |
      | contacts     | 1               | 0                |
      | contactlists | 0               | 1                |
      | lists        | 1               | 0                |
      | segments     | 1               | 0                |
      | usermes      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Acumatica on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/acumatica

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Acumatica.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Acumatica.

[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=acumatica)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Run operations (20 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                             |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------ |
        | **AR Aging - 60+ Days**                            | Alert band 5 / 15  | Share of AR balance aged 60+ days from invoice DueDate.                                    |
        | **AR Aging Buckets**                               | Watch only         | Outstanding Invoice.Balance bucketed 0-30 / 31-60 / 61-90 / 90+ days.                      |
        | **AR Balance (live)**                              | Watch only         | Sum of outstanding Invoice.Balance across open AR invoices.                                |
        | **Acumatica Health Score**                         | Merchant rule      | Composite: order-to-cash-sync-clean x inventory-parity x AR-aging-low x GL-batches-posted. |
        | **Customers on Credit Hold**                       | Merchant rule      | Customer.Status = CreditHold - blocks new fulfilment until cleared.                        |
        | **Days Sales Outstanding (DSO)**                   | Alert band 30 / 60 | Description pending editorial review; the signal is live.                                  |
        | **ERP-vs-Ecom Inventory Variance %**               | Alert band 1 / 5   | Acumatica aggregate QtyAvailable vs storefront available qty on SKUs with active orders.   |
        | **Financial Period Close Past Deadline**           | Alert band 0 / 5   | Period close overdue compounds AR/AP reconciliation workload.                              |
        | **Financial Period Close Status**                  | Alert band 0 / 5   | Days the active financial period has stayed open past its scheduled close.                 |
        | **GL Batches Failing to Balance (debit ≠ credit)** | Alert band 0 / 5   | JournalTransaction with DebitTotal ≠ CreditTotal - blocks period close.                    |
        | **Inventory Turns (annualised)**                   | Merchant rule      | COGS / average on-hand value. Distribution-edition stock efficiency signal.                |
        | **Milestone Billing Due / Unbilled**               | Merchant rule      | BudgetedAmount − BilledAmount on milestones past their billing date.                       |
        | **On-Hand Inventory Value**                        | Watch only         | Σ QtyOnHand × StockItem.LastCost across warehouses.                                        |
        | **Order-to-Cash Velocity (days)**                  | Alert band 30 / 60 | Median storefront order timestamp → Acumatica invoice paid. Ties ecom + ERP timestamps.    |
        | **Production Lead Time (days)**                    | Merchant rule      | Median production-order create → complete. Manufacturing edition only.                     |
        | **Project Margin (active projects)**               | Merchant rule      | (BudgetedAmount − ActualAmount) / BudgetedAmount on Active projects.                       |
        | **Stock Days-on-Hand by Warehouse**                | Merchant rule      | QtyOnHand / avg daily ship rate, per WarehouseID.                                          |
        | **Stock Item On-Hand Went Negative**               | Merchant rule      | Negative on-hand = receipt/shipment posting error or oversell.                             |
        | **Unposted GL Batches**                            | Alert band 0 / 50  | JournalTransaction rows in Unposted/OnHold - approval-routing or close-cycle backlog.      |
        | **Work-in-Progress Value (Manufacturing)**         | Watch only         | Open production-order value. Manufacturing edition only.                                   |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                                                   | Alert behaviour | What it tracks                                                                                               |
        | -------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------ |
        | **B2B Customer-Level Revenue Exposure (top 10)**         | Watch only      | Concentration of AR + revenue on the top-10 B2B customers.                                                   |
        | **Multi-Currency Settlement Variance**                   | Merchant rule   | FX gain/loss between order CurrencyID booking rate and invoice settlement rate. Cross-border merchants only. |
        | **Open Sales Order Value (backlog)**                     | Watch only      | Sum of OrderTotal on SalesOrder in Open/BackOrder/Shipping status.                                           |
        | **Order-to-Cash Funnel (order → ship → invoice → paid)** | Watch only      | Counts of SalesOrder progressing through fulfilment + AR invoice stages.                                     |
        | **Revenue Recognition Pending**                          | Watch only      | Deferred / unrecognised revenue awaiting recognition schedule run.                                           |
        | **Revenue by Branch / Entity**                           | Watch only      | Multi-entity / multi-branch revenue consolidation from invoice Branch.                                       |
        | **Revenue by Sales Channel (storefront / EDI / direct)** | Watch only      | Sales orders grouped by OrderType (channel proxy).                                                           |
        | **Sales Orders Stuck on Hold**                           | Merchant rule   | SalesOrder.Status = Hold / PendingApproval blocking fulfilment + invoicing.                                  |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                   | Alert behaviour         | What it tracks                                                                                   |
        | -------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------ |
        | **AR Aging on Customers with Active Ecom Orders**        | Alert band 1000 / 10000 | Credit risk compounding - overdue AR on customers you're still shipping to.                      |
        | **Ecom Customers Absent from Acumatica Customer Master** | Alert band 0 / 10       | Sync gap - B2B-flagged ecom customers missing in Acumatica break AR invoicing on the next batch. |
        | **Ecom Orders Missing a Matching Acumatica Invoice**     | Merchant rule           | Storefront orders never posted to Acumatica = revenue invisible to the GL + understated AR.      |
        | **SKUs with Acumatica-vs-Ecom Inventory Drift >5%**      | Alert band 1 / 5        | Cross-channel oversell / stockout exposure on SKUs with active orders.                           |
        | **Warehouse-Level Stockouts**                            | Merchant rule           | StockItem with QtyAvailable = 0 in a warehouse but active sales orders.                          |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                                     | Alert behaviour | What it tracks                                                                        |
        | ------------------------------------------ | --------------- | ------------------------------------------------------------------------------------- |
        | **BOM Cost Drift (Manufacturing edition)** | Merchant rule   | Rolled-up BOM standard cost vs latest component LastCost. Manufacturing edition only. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **2 write** operations across entitydefaultcompanys, entitydefaultcustomers, entitydefaultinventorysummaryinquirys, entitydefaultinvoices, entitydefaultjournaltransactions, entitydefaultprojects on Acumatica. 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=acumatica)

    #### Ready to build your first Acumatica 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                              | Read operations | Write operations |
      | ------------------------------------- | --------------- | ---------------- |
      | entitydefaultcompanys                 | 1               | 0                |
      | entitydefaultcustomers                | 1               | 0                |
      | entitydefaultinventorysummaryinquirys | 0               | 1                |
      | entitydefaultinvoices                 | 1               | 0                |
      | entitydefaultjournaltransactions      | 1               | 0                |
      | entitydefaultprojects                 | 1               | 0                |
      | entitydefaultsalesorders              | 1               | 0                |
      | entitydefaultstockitems               | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Adobe Commerce on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/adobe-commerce

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Adobe Commerce.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Adobe Commerce.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/adobe-commerce) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=adobe-commerce)

<CardGroup>
  <Card title="46">
    performance signals
  </Card>

  <Card title="47">
    automated checks
  </Card>

  <Card title="35">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (46)">
    ### Monitor performance

    46 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                            |
        | -------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Customer Order Frequency**     | Watch only         | Customer Order Frequency, compared across items.          |
        | **Customer Spend Segments**      | Watch only         | Customer Spend Segments, shown by share.                  |
        | **Customers with Zero Spend**    | Alert band 30 / 60 | Description pending editorial review; the signal is live. |
        | **Email Health**                 | Alert band 95 / 80 | Description pending editorial review; the signal is live. |
        | **Financial Status Breakdown**   | Watch only         | Orders grouped by payment/financial status.               |
        | **Free vs Paid Shipping**        | Watch only         | Free vs Paid Shipping, shown by share.                    |
        | **Fulfillment Rate**             | Alert band 95 / 90 | Percentage of orders successfully fulfilled.              |
        | **Fulfillment Rate Over Time**   | Watch only         | Description pending editorial review; the signal is live. |
        | **Fulfillment Status**           | Watch only         | Distribution of orders by fulfillment status.             |
        | **Guest vs Account Orders**      | Watch only         | Guest vs Account Orders, shown by share.                  |
        | **Line Item Fulfillment Status** | Watch only         | Line Item Fulfillment Status, shown by share.             |
        | **New Customers**                | Watch only         | New customer signups in the selected period.              |
        | **Order State Breakdown**        | Watch only         | Order State Breakdown.                                    |
        | **Orders Over Time**             | Watch only         | Order volume trend over the selected period.              |
        | **Orders by Country**            | Watch only         | Orders by Country.                                        |
        | **Payment Methods**              | Watch only         | Distribution of orders by payment method.                 |
        | **Return Status**                | Watch only         | Return Status, shown by share.                            |
        | **Tax Analysis**                 | Watch only         | Tax Analysis, compared across items.                      |
        | **Tax Collected Over Time**      | Watch only         | Description pending editorial review; the signal is live. |
        | **Unfulfilled Orders**           | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Unique Customers**             | Watch only         | Number of unique customers who placed orders.             |
        | **Unverified Email Customers**   | Merchant rule      | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Grow revenue (16 signals)">
        | Signal                            | Alert behaviour     | What it tracks                                            |
        | --------------------------------- | ------------------- | --------------------------------------------------------- |
        | **Average Order Value**           | Merchant rule       | Average amount customers spend per order.                 |
        | **Customer Acquisition Trend**    | Watch only          | New customer acquisition trend over time.                 |
        | **Daily Order Trends**            | Watch only          | Description pending editorial review; the signal is live. |
        | **Discount % of Revenue**         | Merchant rule       | Discount value as a percentage of total revenue.          |
        | **Discounts Given Over Time**     | Watch only          | Description pending editorial review; the signal is live. |
        | **Repeat Customer Rate**          | Alert band 25 / 10  | Percentage of customers who ordered more than once.       |
        | **Revenue Breakdown**             | Watch only          | Revenue Breakdown.                                        |
        | **Revenue Over Time**             | Watch only          | Revenue trend over the selected period.                   |
        | **Revenue by Day of Week**        | Watch only          | Revenue by Day of Week.                                   |
        | **Revenue by Payment Gateway**    | Watch only          | Revenue by Payment Gateway.                               |
        | **Shipping Cost as % of Revenue** | Alert band 5 / 15   | Description pending editorial review; the signal is live. |
        | **Total Discount Used**           | Watch only          | Total discount amount applied across all orders.          |
        | **Total Orders**                  | Merchant rule       | Number of orders placed in the selected period.           |
        | **Total Revenue**                 | Alert band 10 / -10 | Description pending editorial review; the signal is live. |
        | **Total Shipping Revenue**        | Watch only          | Total shipping charges collected.                         |
        | **Total Tax Collected**           | Watch only          | Total tax collected across all orders.                    |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                         | Alert behaviour  | What it tracks                                            |
        | ------------------------------ | ---------------- | --------------------------------------------------------- |
        | **Cancellation Rate**          | Alert band 1 / 3 | Percentage of orders cancelled before shipping.           |
        | **Cancelled Orders Over Time** | Watch only       | Description pending editorial review; the signal is live. |
        | **Customer Churn Risk**        | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Refund Rate**                | Alert band 2 / 5 | Percentage of orders that were refunded.                  |
        | **Refund Value**               | Watch only       | Total monetary value of refunds issued.                   |
        | **Refunded Orders**            | Watch only       | Number of orders with full refunds.                       |
        | **Refunds Over Time**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Top Refunding Customers**    | Watch only       | Top Refunding Customers, compared across items.           |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (47)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="HTTPS Not Reachable">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        If the storefront is not cleanly reachable over HTTPS, browsers warn customers away and search engines demote the site; trust and traffic drop together.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SC01`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Sitemap Missing or Thin">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without a healthy sitemap, new and updated pages are discovered late or not at all, so products can launch invisible to search.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB03`
      </Accordion>

      <Accordion title="Storefront blocked by Cloudflare - audit cannot reach the store">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Cloudflare is challenging the auditor, so storefront checks cannot run at all; every dependent finding is suppressed rather than invented.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CF01`
      </Accordion>

      <Accordion title="Theme audit blocked by Cloudflare">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        The theme audit could not reach the storefront because Cloudflare is challenging automated access; theme findings are unavailable rather than guessed until access is allowed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `TH00`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Excessive CSS files loaded">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Prepared fix

        Excess CSS files block rendering while they download; consolidating them speeds first paint on every page.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH03`
      </Accordion>

      <Accordion title="Homepage SEO Elements Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        The homepage is the most-linked page on the store; missing titles or descriptions there squander the site's strongest ranking signals.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB05`
      </Accordion>

      <Accordion title="Images missing alt text">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Prepared fix

        Images without alt text are invisible to screen readers and to image search; accessibility risk and free traffic left unclaimed at the same time.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH07`
      </Accordion>

      <Accordion title="Limited or Missing Schema Markup">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Schema markup earns rich results (stars, prices, availability) that lift click-through; without it, listings look plainer than competitors on the same results page.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB04`
      </Accordion>

      <Accordion title="Missing Meta Descriptions">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Search engines improvise snippets for pages without meta descriptions; a written one lifts click-through on impressions the page already earns.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE01`
      </Accordion>

      <Accordion title="Missing Page Titles">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Page titles are the strongest single on-page ranking and click-through signal; missing ones waste impressions the store already gets.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE02`
      </Accordion>

      <Accordion title="Missing Product Images">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Prepared fix

        Products without images barely convert; shoppers skip listings they cannot see.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ01`
      </Accordion>

      <Accordion title="Mobile Viewport Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without a mobile viewport tag the store renders desktop-sized on phones; mobile shoppers pinch, zoom and leave.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB12`
      </Accordion>

      <Accordion title="Mobile responsiveness issues">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Prepared fix

        Layouts that break on mobile lose the majority of ecommerce traffic; most stores see well over half their sessions on phones.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH11`
      </Accordion>

      <Accordion title="No Reviews Platform Detected">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Visible reviews are one of the strongest conversion levers in ecommerce; a store with no social proof converts measurably worse on identical traffic.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB10`
      </Accordion>

      <Accordion title="No analytics tracking detected on storefront">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without analytics on the storefront, marketing and UX decisions run blind and no conversion diagnosis is possible downstream.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SC03`
      </Accordion>

      <Accordion title="Order cancellation/refund rate exceeds 5%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Cancellation plus refund above 5 percent of orders means a meaningful slice of won revenue is being handed back; the causes (stock, delivery promises, payment friction) are usually fixable once identified.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `OH01`
      </Accordion>

      <Accordion title="Product Page SEO Issues">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Product pages are where buying-intent searches land; SEO gaps here cost clicks with direct revenue attached.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB06`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Store Logo: No store logo configured">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        A missing store logo makes transactional emails, invoices and search results look unfinished; small trust losses compound at checkout.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SC02`
      </Accordion>

      <Accordion title="Zero-Price Products">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Prepared fix

        A visible product priced at zero can be added to carts for free and makes the catalogue look broken; each one is either direct revenue leakage or an embarrassment in front of customers.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ02`
      </Accordion>

      <Accordion title="llms.txt Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        AI assistants increasingly answer shopping questions; llms.txt tells them what the store is and which pages matter, the emerging AI-search equivalent of robots.txt.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB02`
      </Accordion>

      <Accordion title="Accessibility issues found">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Accessibility failures exclude customers and carry regulatory risk in a growing list of markets; the common fixes are cheap.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH12`
      </Accordion>

      <Accordion title="Excessive JavaScript files loaded">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Each extra JavaScript file adds a request and parse cost on every page view; script bloat is one of the most common causes of slow storefronts.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH01`
      </Accordion>

      <Accordion title="Font loading not optimized">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Fonts loading without font-display cause invisible text while they download; visitors stare at blank headings on slow connections.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH10`
      </Accordion>

      <Accordion title="High refund rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refund concentration is a direct margin leak and often clusters around specific products, suppliers or delivery windows, which makes it diagnosable and fixable.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `OH02`
      </Accordion>

      <Accordion title="Images missing lazy loading">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Images loading eagerly below the fold compete with the content the shopper actually sees first, inflating LCP and hurting Core Web Vitals rankings.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH02, TH08`
      </Accordion>

      <Accordion title="Long inline styles">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Very long inline styles bloat every page they appear on and defeat caching that external stylesheets would get for free.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH06`
      </Accordion>

      <Accordion title="Missing Product Weight">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Weight-based shipping cannot quote correctly for products without weights, causing checkout errors or mispriced delivery. Irrelevant for flat-rate stores, which is worth recording as a business rule so this never nags.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ04`
      </Accordion>

      <Accordion title="Missing SKUs">
        **Severity** low · **Outcome** Run operations · **Fix status** Prepared fix

        Missing SKUs break inventory reconciliation, courier manifests and marketplace feeds; the problems surface downstream where they are hardest to trace back.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ03`
      </Accordion>

      <Accordion title="Missing Security Headers">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Prepared fix

        Missing security headers leave the storefront easier to attack through clickjacking and script injection, and are flagged by the scanners customers and partners run.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB07`
      </Accordion>

      <Accordion title="Missing Social Meta Tags">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without Open Graph and Twitter tags, shared links render as bare URLs; rich previews carry substantially higher click-through from social and chat.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB09`
      </Accordion>

      <Accordion title="Missing/Short Product Descriptions">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Thin or missing product descriptions hurt conversion on the page and long-tail search rankings off it.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE03`
      </Accordion>

      <Accordion title="No Inventory Tracking">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Without inventory tracking the store cannot warn about stockouts or overselling; every availability signal downstream of this is guesswork.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `IQ01`
      </Accordion>

      <Accordion title="No Remarketing Tags Detected">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without remarketing tags, the roughly 97 percent of visitors who leave cannot be re-engaged, making every paid acquisition channel more expensive.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB11`
      </Accordion>

      <Accordion title="Out of Stock Still Visible">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Shoppers landing on unavailable products bounce, and any paid or organic traffic pointed at them is wasted, unless visibility is deliberate (back-in-stock capture or SEO retention), which is worth recording as a business rule.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `IQ02`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>

      <Accordion title="Render-blocking scripts in <head>">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Scripts loaded in the head without defer block the page from rendering until they finish; moving or deferring them is one of the cheapest speed wins available.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH05`
      </Accordion>

      <Accordion title="Uncategorized Products">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Uncategorised products are unreachable through navigation and category landing pages; they only sell if a customer happens to search for them.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ05`
      </Accordion>

      <Accordion title="console.log statements found in inline scripts">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        console.log calls in production scripts leak implementation detail and add noise; they usually indicate debug code that shipped by accident.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH04`
      </Accordion>

      <Accordion title="robots.txt Missing or Misconfigured">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        A missing or broken robots.txt can accidentally block crawlers from the whole store, or fail to steer them away from junk URLs that waste crawl budget.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB01`
      </Accordion>

      <Accordion title="Tech Stack Detected">
        **Severity** info · **Outcome** Run operations · **Fix status** Prepared fix

        Informational: the technologies detected on the storefront, used to tailor the other checks to the actual stack.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB08, TH09`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **0 write** operations across customer searchs, orders, products on Adobe Commerce. 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=adobe-commerce)

    #### Ready to build your first Adobe Commerce 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | customer searchs | 1               | 0                |
      | orders           | 1               | 0                |
      | products         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# AdRoll on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/adroll

Monitor AdRoll campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor AdRoll campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/adroll) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=adroll)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                  |
        | ----------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------- |
        | **AdRoll Pixel Not Firing on Conversion Pages** | Merchant rule      | Retargeting audiences shrink silently when the Pixel fails , every audit's first check on a new AdRoll account. |
        | **All Conversions**                             | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **CPC by Campaign**                             | Watch only         | CPC by Campaign.                                                                                                |
        | **CTR by Campaign**                             | Watch only         | CTR by Campaign.                                                                                                |
        | **Campaign Comparison**                         | Watch only         | Campaign Comparison, broken down by row.                                                                        |
        | **Clicks vs Conversions**                       | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversion Actions Breakdown**                | Watch only         | Conversion Actions Breakdown.                                                                                   |
        | **Conversion Drop Alert**                       | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversion Funnel**                           | Watch only         | Conversion Funnel, stage by stage.                                                                              |
        | **Conversion Lag**                              | Watch only         | Conversion Lag, compared across items.                                                                          |
        | **Conversion Rate Trend**                       | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversion Rate by Campaign**                 | Watch only         | Conversion Rate by Campaign.                                                                                    |
        | **Conversion Rate by Device**                   | Watch only         | Conversion Rate by Device.                                                                                      |
        | **Conversions Trend**                           | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversions by Campaign**                     | Watch only         | Conversions by Campaign.                                                                                        |
        | **Conversions by Country**                      | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversions by Day of Week**                  | Watch only         | Conversions by Day of Week.                                                                                     |
        | **Conversions by Device**                       | Watch only         | Conversions by Device.                                                                                          |
        | **Conversions by Hour**                         | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Cross-Channel Retargeting ROAS Dropped**      | Alert band 3 / 1.5 | First signal that AdRoll's cross-channel retargeting lift narrative just got harder to defend.                  |
        | **Landing Page Revenue**                        | Watch only         | Landing Page Revenue, broken down by row.                                                                       |
        | **Overspending Campaigns**                      | Watch only         | Overspending Campaigns, broken down by row.                                                                     |
        | **ROAS**                                        | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                       |
        | **ROAS Trend**                                  | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **ROAS by Campaign**                            | Watch only         | ROAS by Campaign.                                                                                               |
        | **ROAS by Day of Week**                         | Watch only         | ROAS by Day of Week.                                                                                            |
        | **ROAS by Device**                              | Watch only         | ROAS by Device.                                                                                                 |
        | **ROAS by Region**                              | Watch only         | ROAS by Region.                                                                                                 |
        | **Revenue by Campaign**                         | Watch only         | Revenue by Campaign.                                                                                            |
        | **Search Terms Report**                         | Watch only         | Search Terms Report, broken down by row.                                                                        |
        | **Spend by Campaign**                           | Watch only         | Spend by Campaign.                                                                                              |
        | **Top Cities by Conversions**                   | Watch only         | Top Cities by Conversions.                                                                                      |
        | **Top Keywords by Conversions**                 | Watch only         | Top Keywords by Conversions.                                                                                    |
        | **Top Performing Campaigns**                    | Watch only         | Top Performing Campaigns, broken down by row.                                                                   |
        | **Total Revenue**                               | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Underspending Campaigns**                     | Watch only         | Underspending Campaigns, broken down by row.                                                                    |
        | **Worst Performing Campaigns**                  | Watch only         | Worst Performing Campaigns, broken down by row.                                                                 |
        | **Zero-Conversion Spend**                       | Watch only         | Description pending editorial review; the signal is live.                                                       |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                         |
        | ------------------------------------ | ------------------ | ---------------------------------------------------------------------- |
        | **Budget Utilisation**               | Alert band 70 / 30 | Description pending editorial review; the signal is live.              |
        | **CPA Trend**                        | Watch only         | Description pending editorial review; the signal is live.              |
        | **CPA by Keyword**                   | Watch only         | CPA by Keyword.                                                        |
        | **CPC Anomaly**                      | Watch only         | Description pending editorial review; the signal is live.              |
        | **CPC Spike Detection**              | Watch only         | Description pending editorial review; the signal is live.              |
        | **CPC Trend**                        | Alert band 0 / 25  | Description pending editorial review; the signal is live.              |
        | **CTR Trend**                        | Watch only         | Description pending editorial review; the signal is live.              |
        | **CTR by Keyword**                   | Watch only         | CTR by Keyword.                                                        |
        | **Impression Share**                 | Alert band 70 / 40 | Description pending editorial review; the signal is live.              |
        | **Impressions Trend**                | Watch only         | Description pending editorial review; the signal is live.              |
        | **Quality Score Distribution**       | Alert band 7 / 4   | Quality Score Distribution, compared across items.                     |
        | **Spend Anomaly**                    | Watch only         | Description pending editorial review; the signal is live.              |
        | **Spend Over Time**                  | Alert band 0 / -10 | Description pending editorial review; the signal is live.              |
        | **Spend vs Budget**                  | Watch only         | Description pending editorial review; the signal is live.              |
        | **Top Keywords by Spend**            | Watch only         | Top Keywords by Spend.                                                 |
        | **Total Spend**                      | Watch only         | Description pending editorial review; the signal is live.              |
        | **Wasted Spend**                     | Watch only         | Description pending editorial review; the signal is live.              |
        | **Wasted-Spend Burst (3-day spike)** | Alert band 5 / 50  | Catches a runaway prospecting test before it eats the SMB-tier budget. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                    |
        | -------------------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------- |
        | **Active Dynamic Ads on Out-of-Stock SKUs**        | Alert band 5 / 50 | AdRoll dynamic catalog ads pointing at SKUs that can't convert. Pause the dynamic creative pool, hold the budget. |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | Retargeting already-warm audiences who would've returned via direct/organic search. Pure margin reclaim.          |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                         |
        | **Landing Pages with Poor Web Vitals**             | Merchant rule     | Retargeting click → slow product page = abandoner abandons again. Names the page so the dev fixes it.             |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on AdRoll dynamic campaigns whose Feedonomics feed has live rejections. Dynamic creative falls back, CR drops.  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across ads, authtokens, campaigns, organizations, report timeserys on AdRoll. 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=adroll)

    #### Ready to build your first AdRoll 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | ads              | 1               | 0                |
      | authtokens       | 0               | 1                |
      | campaigns        | 1               | 0                |
      | organizations    | 1               | 0                |
      | report timeserys | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Adyen on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/adyen

Monitor Adyen payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Adyen payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=adyen)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="96">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (8 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                        |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------- |
        | **Chargeback Rate**             | Alert band 0.5 / 1 | Description pending editorial review; the signal is live.                             |
        | **Chargeback Spike Alert**      | Alert band 0.5 / 1 | Description pending editorial review; the signal is live.                             |
        | **Chargebacks (30d)**           | Merchant rule      | Description pending editorial review; the signal is live.                             |
        | **Dispute Win Rate**            | Watch only         | Description pending editorial review; the signal is live.                             |
        | **Fraud Rate**                  | Merchant rule      | Description pending editorial review; the signal is live.                             |
        | **Payments Health Score**       | Alert band 90 / 70 | Composite: auth rate x (inverse) refusal x (inverse) chargeback x settlement on-time. |
        | **Refunds (30d)**               | Alert band 2 / 5   | Description pending editorial review; the signal is live.                             |
        | **Refunds vs Commerce Returns** | Watch only         | Description pending editorial review; the signal is live.                             |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                            |
        | ------------------------------- | ------------------ | --------------------------------------------------------- |
        | **3DS Challenge Rate**          | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Auth Rate by Payment Method** | Alert band 97 / 92 | Auth Rate by Payment Method.                              |
        | **Avg Transaction Value**       | Watch only         | Description pending editorial review; the signal is live. |
        | **Capture Rate**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Payment Method Mix**          | Watch only         | Payment Method Mix, shown by share.                       |
        | **Refusal Reasons**             | Watch only         | Refusal Reasons, compared across items.                   |
      </Accordion>

      <Accordion title="Control risk and change (5 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                            |
        | -------------------------- | ------------------ | --------------------------------------------------------- |
        | **Active Payment Methods** | Watch only         | Description pending editorial review; the signal is live. |
        | **Auth Rate Drop Alert**   | Alert band 97 / 92 | Description pending editorial review; the signal is live. |
        | **Authorisation Rate**     | Alert band 97 / 92 | Description pending editorial review; the signal is live. |
        | **Stores / Accounts**      | Watch only         | Description pending editorial review; the signal is live. |
        | **Webhooks Configured**    | Merchant rule      | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                            |
        | -------------------------- | ------------------ | --------------------------------------------------------- |
        | **Payment Volume (30d)**   | Alert band 0 / -15 | Description pending editorial review; the signal is live. |
        | **Refusal Rate**           | Alert band 3 / 8   | Description pending editorial review; the signal is live. |
        | **Refusal Spike Alert**    | Alert band 3 / 8   | Description pending editorial review; the signal is live. |
        | **Settlement Delay Alert** | Alert band 2 / 5   | Description pending editorial review; the signal is live. |
        | **Settlement Pending**     | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                                | Alert behaviour | What it tracks                                            |
        | ------------------------------------- | --------------- | --------------------------------------------------------- |
        | **Captured vs Commerce Revenue**      | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Support Spike on Refused Payments** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Chargeback rate above 1% (Visa/Mastercard programme threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Chargebacks above 1 percent cross the card-scheme programme threshold: fines and monitoring programmes begin, and processing itself is at risk.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ADYEN-CHARGEBACK-001`
      </Accordion>

      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Authorisation rate below 92%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Authorisation below 92 percent means real customers with real money are being declined; small routing and retry changes move revenue directly.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ADYEN-AUTH-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Payment volume dropped >15% vs prior period">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Payment volume dropping 15 percent against the prior period is either a real demand problem or a payments problem; distinguishing them fast protects revenue either way.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ADYEN-REVENUE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="Refusal rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        A refusal rate above 8 percent points at issuer mistrust, risk-rule misconfiguration or fraud pressure; every refused legitimate payment is a completed sale lost at the till.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ADYEN-REFUSAL-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>

      <Accordion title="Settlement age above 5 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Settlement aging beyond 5 days is working capital sitting with the processor instead of in the business.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ADYEN-SETTLEMENT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **11 read** and **85 write** operations across grants, grantdisbursements, payment links, storedpaymentmethods, cancels, grantoffers on Adyen. 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=adyen)

    #### Ready to build your first Adyen 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | grants               | 2               | 1                |
      | grantdisbursements   | 2               | 1                |
      | payment links        | 1               | 2                |
      | storedpaymentmethods | 1               | 2                |
      | cancels              | 0               | 2                |
      | grantoffers          | 2               | 0                |
      | payments             | 0               | 2                |
      | sessions             | 1               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Afterpay on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/afterpay

Monitor Afterpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Afterpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=afterpay)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (10 signals)">
        | Signal                                              | Alert behaviour    | What it tracks                                                                                                                                         |
        | --------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **3DS Abandonment Rate**                            | Watch only         | Share of 3DS-challenged Afterpay transactions abandoned at the challenge step - added friction / lost conversion.                                      |
        | **Afterpay Refund Spike × Commerce Returns Spike**  | Merchant rule      | Afterpay refund volume rising in lockstep with commerce returns - a product / fulfilment / quality issue draining BNPL margin, not a payments glitch.  |
        | **Afterpay-vs-Commerce Revenue Reconciliation Gap** | Alert band 0 / 2   | Captured Afterpay volume that doesn't reconcile to commerce-sibling Afterpay-paid order revenue = a sync / capture / settlement gap to chase.          |
        | **Chargeback Rate**                                 | Watch only         | Chargebacks as a share of transactions. Above the 1% Visa/Mastercard programme threshold is monitoring-programme risk.                                 |
        | **Decline Rate**                                    | Alert band 5 / 8   | Share of Afterpay attempts declined by Afterpay's upfront risk model. Pair with Top Decline Reasons to see what's driving it.                          |
        | **Dispute Rate**                                    | Watch only         | Open disputes + inquiries as a share of transactions - early-warning band before formal chargebacks.                                                   |
        | **Refund Rate**                                     | Alert band 3 / 8   | Refunded value as a share of captured Afterpay volume. A spike vs baseline flags returns / quality / fulfilment issues.                                |
        | **Refund Volume**                                   | Merchant rule      | Total value refunded through Afterpay in the period. Subtract from Total Volume for net BNPL revenue.                                                  |
        | **Top Decline Reasons**                             | Merchant rule      | Decline-reason mix across declined Afterpay attempts - where recoverable BNPL revenue is leaking.                                                      |
        | **Total Volume**                                    | Alert band 0 / -15 | Gross Afterpay Pay-in-4 volume captured in the period (status CAPTURED, summed by totalAmount). Gross of refunds + Afterpay's merchant fee; multi-curr |
      </Accordion>

      <Accordion title="Run operations (6 signals)">
        | Signal                           | Alert behaviour | What it tracks                                                                                                                         |
        | -------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Settlement Time (days)**   | Merchant rule   | Mean days from capture to Afterpay payout landing. Afterpay typically settles 1-3 business days after capture.                         |
        | **Oldest Pending Payout (days)** | Watch only      | Age in days of the oldest still-pending payout. Aging past the typical 1-3 day schedule is a cash-flow / settlement-health flag.       |
        | **Pending Payouts**              | Merchant rule   | Gross value of Afterpay settlements still in PENDING / IN\_TRANSIT - cash captured but not yet in the bank.                            |
        | **Top Payment Methods**          | Merchant rule   | Mix of underlying payment instruments / Pay-in-4 channels (web, Cash App) backing Afterpay orders.                                     |
        | **Total Transactions**           | Merchant rule   | Count of successful Afterpay Pay-in-4 orders (APPROVED + CAPTURED). Volume / this gives Afterpay AOV (typically \~25% above card AOV). |
        | **Volume Trend**                 | Merchant rule   | Daily captured Afterpay volume over the window - the shape behind the headline Total Volume number.                                    |
      </Accordion>

      <Accordion title="Customer experience (2 signals)">
        | Signal                  | Alert behaviour    | What it tracks                                                                                                         |
        | ----------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------- |
        | **Average Transaction** | Merchant rule      | Afterpay AOV - total captured volume / captured order count. The BNPL basket-size lift over card checkout.             |
        | **Success Rate**        | Alert band 95 / 90 | Share of Afterpay attempts that approved and captured. Below 90% signals checkout friction or underwriting tightening. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **2 write** operations across disputes, payments, payment refunds, settlements, configurations, disputeresponds on Afterpay. 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=afterpay)

    #### Ready to build your first Afterpay 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | disputes        | 2               | 0                |
      | payments        | 2               | 0                |
      | payment refunds | 1               | 1                |
      | settlements     | 2               | 0                |
      | configurations  | 1               | 0                |
      | disputeresponds | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Agile CRM on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/agile-crm

Monitor Agile CRM pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Agile CRM 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=agile-crm)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="13">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Protect revenue (12 signals)">
        | Signal                              | Alert behaviour      | What it tracks                                                                                                                           |
        | ----------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)**       | Merchant rule        | Estimated subscribed (non-unsubscribed, non-bounced) contacts - the marketable audience size.                                            |
        | **Bounce Rate**                     | Alert band 2 / 5     | Bounces ÷ sent (lower is better). Sentiment band good ≤2% / warn ≥5%.                                                                    |
        | **Campaign Revenue vs Ecom Orders** | Merchant rule        | Ties Agile CRM email sends to real ecom orders - exposes campaigns that look engaged but drive no revenue.                               |
        | **Checkout-to-Order Rate**          | Merchant rule        | Placed orders ÷ checkouts started - where the tail of the funnel leaks.                                                                  |
        | **Delivery Rate**                   | Alert band 98 / 95   | Delivered ÷ sent. Sentiment band good ≥98% / warn ≤95%.                                                                                  |
        | **Email Health KPIs**               | Merchant rule        | Composite email-health roll-up (deliverability + engagement) for an at-a-glance read.                                                    |
        | **Engagement Funnel**               | Merchant rule        | Sent → delivered → opened → clicked → converted funnel. Drop-offs expose where engagement leaks.                                         |
        | **List Health Summary**             | Merchant rule        | Roll-up of list-decay signals (bounced / unsubscribed / inactive share) across lists.                                                    |
        | **Refund Rate**                     | Alert band 2 / 8     | Refunded ÷ placed orders (lower is better) - quality/expectation gap signal.                                                             |
        | **Spam Complaint Rate**             | Alert band 0.1 / 0.3 | Spam complaints ÷ delivered (lower is better). Good ≤0.1% / warn ≥0.3% - sustained breach risks send throttling.                         |
        | **Subscriber vs Customer Drift**    | Merchant rule        | Marketable-audience vs buyer-base gap. Customers off-list = missed lifecycle email; clicking subscribers who never buy = nurture target. |
        | **Unsubscribe Rate**                | Alert band 0.5 / 2   | Unsubscribes ÷ delivered (lower is better). Good ≤0.5% / warn ≥2%.                                                                       |
      </Accordion>

      <Accordion title="Run operations (11 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of two confirmed real Agile CRM Contact properties: share with an email property populated and share with a phone property populated (both u |
        | **Email Click Rate**       | Alert band 2 / 0.5 | Clicks ÷ delivered. Sentiment band good ≥2% / warn ≤0.5%.                                                                                              |
        | **Email Open Rate**        | Alert band 20 / 10 | Opens ÷ delivered. Sentiment band good ≥20% / warn ≤10%.                                                                                               |
        | **Flow Status Breakdown**  | Merchant rule      | Flows grouped by status (active / paused / draft) - quick automation-health glance.                                                                    |
        | **Flow Trigger Types**     | Merchant rule      | Flows grouped by trigger type - shows how automations are being entered.                                                                               |
        | **Flows List**             | Merchant rule      | Tabular list of automation flows with status + enrolment counts.                                                                                       |
        | **List Count**             | Merchant rule      | Number of contact lists in the account.                                                                                                                |
        | **Lists Overview**         | Merchant rule      | Per-list table with name, type and contact count.                                                                                                      |
        | **Placed Orders Total**    | Merchant rule      | Tracked placed orders attributed through Agile CRM in the window.                                                                                      |
        | **Segments Overview**      | Merchant rule      | Per-segment (saved filter) table with name and contact count.                                                                                          |
        | **Top Lists by Name**      | Merchant rule      | Largest lists ranked by contact count.                                                                                                                 |
      </Accordion>

      <Accordion title="Grow revenue (7 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                           |
        | ----------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule   | Count of campaigns by status (draft / scheduled / sent / paused / archived).                             |
        | **Conversion Rate**           | Merchant rule   | Placed orders ÷ recipients - email-to-purchase conversion.                                               |
        | **Flow Count Summary**        | Merchant rule   | Total automation flows / campaigns configured in the account.                                            |
        | **Revenue per Recipient**     | Merchant rule   | Attributed revenue ÷ unique recipients - value extracted per person reached.                             |
        | **Revenue per Send**          | Merchant rule   | Attributed revenue ÷ emails sent - the cleanest send-efficiency signal.                                  |
        | **Total Revenue**             | Merchant rule   | Total email-attributed revenue across campaigns in the window - top-line health for the whole connector. |
        | **Total Sends**               | Merchant rule   | Sum of emails sent across campaigns - denominator for the rate cards below.                              |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                 | Alert behaviour     | What it tracks                                                                                                                                             |
        | ---------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Lead Response Time** | Alert band 60 / 480 | Median minutes from Contact.created\_time to the start\_time of the first logged Event linked to that contact (GET /dev/api/events, contact\_ids\[]). Agil |
        | **Stalled Deal %**     | Alert band 10 / 30  | Open Deals (archived = false) with no note logged in 14 days, as a share of all open Deals. GET /dev/api/opportunity//notes is Agile CRM's co              |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                     |
        | --------------------- | --------------- | ------------------------------------------------------------------ |
        | **Checkouts Started** | Merchant rule   | Tracked checkout-started events from Agile CRM ecommerce tracking. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                 | Alert behaviour   | What it tracks                                                         |
        | ---------------------- | ----------------- | ---------------------------------------------------------------------- |
        | **Click-to-Open Rate** | Alert band 10 / 3 | Clicks ÷ opens - creative/content effectiveness. Good ≥10% / warn ≤3%. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **11 read** and **2 write** operations across devcampaignlogs, devcontacts, devcontactcounts, devcontactedittags, devevents, devfilters on Agile CRM. 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=agile-crm)

    #### Ready to build your first Agile CRM 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | devcampaignlogs    | 1               | 0                |
      | devcontacts        | 1               | 0                |
      | devcontactcounts   | 1               | 0                |
      | devcontactedittags | 0               | 1                |
      | devevents          | 1               | 0                |
      | devfilters         | 1               | 0                |
      | devlists           | 1               | 0                |
      | devopportunitys    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Airtable on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/airtable

Monitor Airtable publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Airtable publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=airtable)

<CardGroup>
  <Card title="11">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (11)">
    ### Monitor performance

    11 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (9 signals)">
        | Signal                             | Alert behaviour      | What it tracks                                                                                                                                         |
        | ---------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Backlog by Status**              | Watch only           | Open records grouped by the Status single-select option.                                                                                               |
        | **Blocked Records**                | Alert band 3 / 8     | Records flagged blocked/impeded in the Status field - the stuck list.                                                                                  |
        | **Finding Resolution Rate (90d)**  | Alert band 75 / 50   | What share of audit findings actually got fixed via the Airtable pipeline. \<50% means we are filing faster than the team drains.                      |
        | **Freshness Lag (minutes)**        | Alert band 60 / 1440 | Minutes since the most recently modified record when a 'Last modified time' field exists, otherwise minutes since the most recently created record (cr |
        | **Oldest Open (days)**             | Merchant rule        | Age of the oldest still-open record, from the record createdTime.                                                                                      |
        | **Open Records**                   | Merchant rule        | Records whose Status is not in the done set - top-of-funnel backlog volume.                                                                            |
        | **Records Created (7d)**           | Merchant rule        | New records created in the table over the last 7 days (createdTime).                                                                                   |
        | **Stale Records (>30d untouched)** | Merchant rule        | Open records not modified in 30 days. Requires a Last modified time field on the table.                                                                |
        | **VortexIQ Findings Open**         | Merchant rule        | Records we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced.                                    |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                 |
        | ----------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the table with no edit for two weeks - the ones losing money silently. Requires a Last modified time field to detect movement. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour   | What it tracks                                                                                                                                        |
        | ---------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Empty Field Rate %** | Alert band 2 / 15 | Share of the table's declared fields left blank across sampled records. Airtable omits empty fields from a record's fields map entirely, so a field's |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Data-source API token invalid or access revoked">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this token fails, VortexIQ stops pulling data from this source entirely, and every card and finding built on it 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: `BYO-AUTH-001`
      </Accordion>

      <Accordion title="Source not updated in over 24h (stale data)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        A source that has not updated in over a day means every conclusion drawn from it describes yesterday; the staleness is invisible unless surfaced.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-FRESH-001`
      </Accordion>

      <Accordion title="Required-field empty rate above 15%">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When required fields are empty in more than 15 percent of rows, every downstream calculation inherits the gaps and quietly under-reports.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-DATA-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **2 write** operations across tableornames, metabas, metabastables, metawhoamis on Airtable. 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=airtable)

    #### Ready to build your first Airtable 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | tableornames  | 1               | 2                |
      | metabas       | 1               | 0                |
      | metabastables | 1               | 0                |
      | metawhoamis   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Alibaba.com (B2B) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/alibaba

Monitor Alibaba.com (B2B) listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Alibaba.com (B2B) listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=alibaba)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (11 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                                   |
        | ------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Alibaba Listings for OOS SKUs on BC**    | Alert band 0 / 5   | Alibaba RFQ inbox / order intake on SKUs you can't fulfil , wastes RFQ-response time + erodes supplier credibility.              |
        | **Alibaba Supplier Health Score**                 | Merchant rule      | Composite: badge-level x response-rate x on-time-delivery x trade-assurance-dispute-inverse.                                     |
        | **B2B vs Retail Pricing Coherence vs AliExpress** | Merchant rule      | B2B wholesale priced HIGHER than retail on AliExpress = supplier credibility crisis. Same parent company surfaces this directly. |
        | **Late Shipments Risking Supplier Badge**         | Merchant rule      | Alerts for Late Shipments Risking Supplier Badge.                                                                                |
        | **Listings Drifting from BC Source-of-Truth**     | Alert band 5 / 50  | B2B Alibaba listings drifting from BC retail source , title/spec divergence confuses B2B buyers verifying via direct site.       |
        | **Listings Failing Feedonomics Feed Validation**  | Alert band 2 / 5   | % of Feedonomics-syndicated B2B listings rejected by Alibaba's product-quality validation.                                       |
        | **Net Revenue (after fees + refunds)**            | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                        |
        | **RFQ Response Rate (30d)**                       | Merchant rule      | % of RFQs responded to within 24h. Below 70% = Verified/Gold Supplier badge at risk.                                             |
        | **Revenue at Risk (live)**                        | Merchant rule      | (unresponded-RFQ-deadlines x conversion-rate x ASP) + (trade-assurance-dispute-escrow-hold) + (badge-loss visibility cost).      |
        | **Supplier Badge KPI Threshold Crossed**          | Alert band 95 / 85 | Composite of Alibaba's three badge KPIs , any crossing risks Verified/Gold downgrade + visibility cut.                           |
        | **Trade Assurance Dispute Rate**                  | Alert band 5 / 15  | Buyers' Trade Assurance escrow disputes (quality / quantity / shipping) , direct hit to badge + new-order escrow holds.          |
      </Accordion>

      <Accordion title="Run operations (11 signals)">
        | Signal                                       | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Buyer Country**                     | Watch only         | AOV by Buyer Country.                                                                                                                                  |
        | **Alibaba Fee % of GMV**                     | Alert band 12 / 18 | Alibaba primary monetisation = annual Gold Supplier subscription; transaction fees lower than retail marketplaces.                                     |
        | **Buyer Messages Unread**                    | Watch only         | Buyer Messages Unread as exposed by the Alibaba integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Days Since Last Payout**                   | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Fees Paid**                    | Watch only         | Marketplace Fees Paid as exposed by the Alibaba integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **On-Time Delivery Rate**                    | Merchant rule      | B2B buyers expect tight delivery windows; misses compound toward badge loss + buyer-blocklist.                                                         |
        | **Orders / Day**                             | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Buyer Country**                  | Watch only         | B2B buyer geography , US/EU vs SE Asia vs Latam mix shapes shipping economics + currency hedging.                                                      |
        | **Pending Payouts**                          | Watch only         | Pending Payouts as exposed by the Alibaba integration. The metric is computed from the latest available data and refreshed on the standard data refres |
        | **Pending Shipment (WAITING\_SELLER\_SEND)** | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Total GMV (B2B)**                          | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (7 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                       |
        | ----------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value (B2B)**             | Alert band 0 / -5  | B2B AOV typically 10-100x retail , sustained drops suggest losing volume buyers to competitors.                      |
        | **GMV Over Time**                         | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                            |
        | **Orders**                                | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Required-Attribute Completeness**       | Alert band 90 / 70 | % of listings with all category-mandated attributes filled , drives search relevance + buyer-trust score.            |
        | **Top Products by Revenue**               | Watch only         | Top Products by Revenue.                                                                                             |
        | **Trade Assurance Revenue Share**         | Watch only         | % of orders using Trade Assurance escrow , higher = buyer-trust signal, but escrow holds tie up capital.             |
        | **Verified / Gold Supplier Badge Status** | Merchant rule      | Alibaba's supplier-credibility tier (BASIC → VERIFIED → GOLD). Higher = more inbox visibility + buyer-trust premium. |
      </Accordion>

      <Accordion title="Catalogue quality (6 signals)">
        | Signal                                         | Alert behaviour   | What it tracks                                                                                                                                         |
        | ---------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Product Listings**                    | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Alibaba Moderation Rejected Listings (24h)** | Alert band 5 / 50 | Alibaba moderation rejects for IP infringement, restricted-goods, image quality. Catch fast before badge impact.                                       |
        | **Listings Expiring Soon**                     | Watch only        | Listings Expiring Soon as exposed by the Alibaba integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Listings with MOQ Tier Inversion**           | Merchant rule     | Listings where a higher-MOQ tier costs more per-unit than a lower-MOQ tier , buyer comparison engines flag these as bad pricing logic.                 |
        | **Rejected / Off-Shelf Listings**              | Alert band 5 / 50 | Listings rejected by Alibaba moderation (often IP infringement, restricted goods, image issues).                                                       |
        | **Total Listings**                             | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                               | Alert behaviour | What it tracks                                                                                   |
        | ------------------------------------ | --------------- | ------------------------------------------------------------------------------------------------ |
        | **Median RFQ Response Time (hours)** | Merchant rule   | Buyers compare suppliers on response speed , median >24h loses to competitors who reply in \<4h. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **2 write** operations across openapiparam2systemoauth2gettokens, order lists, product lists, rfqinboxs, rfqreplys, supplierinfos on Alibaba.com (B2B). 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=alibaba)

    #### Ready to build your first Alibaba.com (B2B) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                           | Read operations | Write operations |
      | ---------------------------------- | --------------- | ---------------- |
      | openapiparam2systemoauth2gettokens | 0               | 1                |
      | order lists                        | 1               | 0                |
      | product lists                      | 1               | 0                |
      | rfqinboxs                          | 1               | 0                |
      | rfqreplys                          | 0               | 1                |
      | supplierinfos                      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Alibris on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/alibris

Monitor Alibris listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Alibris listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=alibris)

<CardGroup>
  <Card title="42">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (42)">
    ### Monitor performance

    42 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (20 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country**                 | Watch only         | AOV by Country.                                                                                                                                        |
        | **Alibris Health Score**           | Merchant rule      | Composite , feed-cycle-success x active-listing-pct x SLA-compliance x inverse stale-listings.                                                         |
        | **Avg Time to Process (hrs)**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Buyer Messages Unread**          | Watch only         | Buyer Messages Unread as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Dispatch SLA Compliance**        | Merchant rule      | % of orders dispatched before dispatch\_due\_by , drives Alibris seller standing.                                                                      |
        | **FTP Connection / Auth Health**   | Merchant rule      | Pure-FTPd does not rotate credentials on a schedule, but partner-side network drops happen , surface before the merchant notices missing orders.       |
        | **Inbound Orders File Lag**        | Merchant rule      | Hours since the last order file landed. Alibris drops order files multiple times per day; >12h is a probable upstream incident.                        |
        | **Last Successful Upload**         | Merchant rule      | Hours since the last /upload/listings drop Alibris ack'd. Stale = feed cycle broken.                                                                   |
        | **Late Order Processing Queue**    | Merchant rule      | Alerts for Late Order Processing Queue.                                                                                                                |
        | **Listings Processed With Errors** | Alert band 5 / 50  | Rows Alibris rejected during inbound processing , surface so the merchant fixes them before the next upload.                                           |
        | **Listings Uploaded (24h)**        | Merchant rule      | Count of listing rows pushed in the last 24h via /upload/listings , flat-file equivalent of a sync heartbeat.                                          |
        | **Marketplace Fees Paid**          | Watch only         | Marketplace Fees Paid as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Oldest Pending Payout (days)**   | Alert band 7 / 21  | Oldest Pending Payout (days) as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standar |
        | **Orders / Day**                   | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Dispatch**               | Alert band 10 / 50 | Orders downloaded from /download/orders that haven't been dispatched yet.                                                                              |
        | **Pending Payouts**                | Watch only         | Pending Payouts as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standard data refres |
        | **Return Rate**                    | Alert band 5 / 15  | Returns are typical in book-trade (condition mis-match). >5% may signal grading drift on used stock.                                                   |
        | **Top Upload Error Types**         | Watch only         | Cluster of error\_message strings from inbound ack files , drives the 'fix once' feed-side bug list.                                                   |
        | **Total Transactions**             | Watch only         | Total Transactions as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standard data ref |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                       | Alert behaviour   | What it tracks                                                                                                  |
        | -------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------- |
        | **Alibris Share of Book-Trade Revenue**      | Watch only        | Channel mix card , flags when Alibris share rises / falls vs sibling book marketplaces.                         |
        | **Cancellation Rate**                        | Merchant rule     | Description pending editorial review; the signal is live.                                                       |
        | **Failed Batches (7d)**                      | Alert band 5 / 50 | Outbox files where Alibris responded with rejection in /download/acks , auth, schema, encoding.                 |
        | **ISBN Drift vs AbeBooks + Amazon**          | Alert band 5 / 50 | Same ISBN listed at materially different prices across the book-trade channels , MAP-style risk on rare titles. |
        | **Net Revenue (after commission + refunds)** | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                       |
        | **Rare-Book Price Floor Watch**              | Merchant rule     | First-edition / signed copies priced materially below the merchant's own DTC list , margin erosion risk.        |
        | **Revenue at Risk (live)**                   | Merchant rule     | Sum of (suspended\_listings x velocity x ASP) + (failed-upload backlog x avg ASP) , recoverable.                |
        | **Stale Listings (>180d no update)**         | Merchant rule     | Listings with no metadata refresh in 6 months , risk Alibris de-prioritising in browse.                         |
        | **Top-Velocity ISBNs Missing on Alibris**    | Merchant rule     | Velocity-proven ISBNs not even listed on Alibris , cheapest book-trade revenue lift available.                  |
      </Accordion>

      <Accordion title="Grow revenue (7 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                                                                         |
        | -------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Order Value**          | Alert band 0 / -5 | Tripwire for academic / library mix shifts , falling AOV often means low-condition stock outpacing first-edition demand.                               |
        | **Orders**                       | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue Over Time**            | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                                                              |
        | **Suspended / Pending Listings** | Alert band 5 / 50 | Alibris has hidden these from search until issues are fixed , direct revenue blocker.                                                                  |
        | **Top Listings by Revenue**      | Watch only        | Top Listings by Revenue as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standard dat |
        | **Top Titles by Revenue**        | Watch only        | Top books by ISBN by revenue , drives reorder-and-list-again decisions on velocity titles.                                                             |
        | **Total Revenue**                | Alert band 0 / -5 | Order totals from the download/orders feed for the period.                                                                                             |
      </Accordion>

      <Accordion title="Catalogue quality (6 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Feed Cycle Failure**        | Merchant rule      | Triggered when /upload/listings has no confirmed ack in 48h , feed is blind, all listing changes stuck.                                                |
        | **ISBN Coverage**             | Alert band 90 / 70 | % of listings with a valid ISBN , listings without ISBN are harder to match across book marketplaces.                                                  |
        | **Listing Error Spike (24h)** | Alert band 5 / 50  | Alerts for Listing Error Spike (24h).                                                                                                                  |
        | **Listings Expiring Soon**    | Watch only         | Listings Expiring Soon as exposed by the Alibris integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Total Listings**            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **4 write** operations across downloadacks, downloadorders, downloadreturns, uploadlistings, uploadprices, uploadquantitys on Alibris. 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=alibris)

    #### Ready to build your first Alibris 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | downloadacks      | 1               | 0                |
      | downloadorders    | 1               | 0                |
      | downloadreturns   | 1               | 0                |
      | uploadlistings    | 0               | 1                |
      | uploadprices      | 0               | 1                |
      | uploadquantitys   | 0               | 1                |
      | uploadwithdrawals | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# AliExpress on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/aliexpress

Monitor AliExpress listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor AliExpress listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=aliexpress)

<CardGroup>
  <Card title="37">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (37)">
    ### Monitor performance

    37 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Buyer Country**                          | Watch only         | AOV by Buyer Country.                                                                                                                                  |
        | **AliExpress Seller Health Score**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Buyer Messages Unread**                         | Watch only         | Buyer Messages Unread as exposed by the AliExpress integration. The metric is computed from the latest available data and refreshed on the standard da |
        | **Days Since Last Payout**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Detailed Rating / Store Level KPI Crossed**     | Alert band 95 / 85 | Alerts for Detailed Rating / Store Level KPI Crossed.                                                                                                  |
        | **Detailed Seller Ratings (Match / Comm / Ship)** | Alert band 95 / 85 | AliExpress's 3-axis seller rating (item match, communication, shipping) , drives store-level placement.                                                |
        | **Marketplace Fees Paid**                         | Watch only         | Marketplace Fees Paid as exposed by the AliExpress integration. The metric is computed from the latest available data and refreshed on the standard da |
        | **Orders / Day**                                  | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Buyer Country**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                               | Watch only         | Pending Payouts as exposed by the AliExpress integration. The metric is computed from the latest available data and refreshed on the standard data ref |
        | **Pending Shipment (WAIT\_SELLER\_SEND\_GOODS)**  | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                | Alert behaviour   | What it tracks                                                                                                   |
        | ------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
        | **AliExpress Fee % of Revenue**       | Watch only        | Transaction fee 5-8% by category + payment-processing fee. Lower than retail marketplaces but adds up at volume. |
        | **Average Order Value**               | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                        |
        | **Net Revenue**                       | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                        |
        | **Orders**                            | Watch only        | Description pending editorial review; the signal is live.                                                        |
        | **Revenue Over Time**                 | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                        |
        | **Revenue by Buyer Currency**         | Watch only        | Cross-border merchants need to know which currencies dominate , drives FX-hedging + pricing decisions.           |
        | **Ship-To Country Coverage**          | Watch only        | % of listings shipping to merchant's target markets , gaps = missed cross-border revenue.                        |
        | **Store Level (Tier1/Gold/Platinum)** | Merchant rule     | AliExpress seller-tier ranking , drives buyer-trust premium and search visibility.                               |
        | **Top Listings by Revenue**           | Watch only        | Top Listings by Revenue.                                                                                         |
        | **Total Revenue**                     | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                        |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                            | Alert behaviour   | What it tracks                                                                                                   |
        | ------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
        | **Active AliExpress Listings for OOS SKUs on BC** | Alert band 0 / 5  | Cross-border OOS = dispute-prone, since buyers expect long lead-times anyway and won't tolerate cancellation.    |
        | **B2B-vs-Retail Pricing Coherence vs Alibaba**    | Merchant rule     | Mirror of alibaba's xc\_price\_parity , same supplier credibility issue from the retail side.                    |
        | **Disputes Judged for Buyer (30d)**               | Alert band 5 / 15 | AliExpress Dispute Centre is buyer-favoured , >50% buyer-wins suggests fulfilment / accuracy issues to fix.      |
        | **Late Shipments / Cainiao SLA Risk**             | Merchant rule     | Alerts for Late Shipments / Cainiao SLA Risk.                                                                    |
        | **Listings Drifting from BC**                     | Alert band 5 / 50 | AliExpress retail listings diverging from BC retail source.                                                      |
        | **Listings Failing Feedonomics Validation**       | Alert band 2 / 5  | Description pending editorial review; the signal is live.                                                        |
        | **Open Disputes**                                 | Merchant rule     | Unresponded disputes auto-rule for buyer at 5d , close-and-refund window before judgment.                        |
        | **Revenue at Risk (live)**                        | Merchant rule     | Description pending editorial review; the signal is live.                                                        |
        | **Shipping-Time Accuracy (promised vs actual)**   | Watch only        | % of orders where actual Cainiao delivery matched promised window. Below 80% = dispute magnet + Cainiao penalty. |
      </Accordion>

      <Accordion title="Catalogue quality (7 signals)">
        | Signal                                 | Alert behaviour   | What it tracks                                                                                                                                         |
        | -------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**                    | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **AliExpress Rejected Listings (24h)** | Alert band 5 / 50 | Alerts for AliExpress Rejected Listings (24h).                                                                                                         |
        | **Listings Expiring Soon**             | Watch only        | Listings Expiring Soon as exposed by the AliExpress integration. The metric is computed from the latest available data and refreshed on the standard d |
        | **Listings with FX Pricing Drift**     | Watch only        | Multi-currency listings whose local-currency price drifted >5% from intended USD-anchor due to FX. Surface for re-pricing.                             |
        | **Rejected / Auditing Listings**       | Alert band 5 / 50 | AliExpress audits IP, restricted goods, image-quality. Rejected listings hidden until fixed.                                                           |
        | **Required-Attribute Completeness**    | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Listings**                     | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across disputelists, oauthtokens, order lists, product lists, selleraccounts on AliExpress. 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=aliexpress)

    #### Ready to build your first AliExpress 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | disputelists   | 1               | 0                |
      | oauthtokens    | 0               | 1                |
      | order lists    | 1               | 0                |
      | product lists  | 1               | 0                |
      | selleraccounts | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Amazon Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/amazon-ads

Monitor Amazon Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Amazon Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/amazon-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=amazon-ads)

<CardGroup>
  <Card title="93">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="5">
    proven workflows
  </Card>

  <Card title="227">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (93)">
    ### Monitor performance

    93 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (54 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **All Conversions**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Audience Overlap (AMC)**                | Watch only         | % of DSP-reached audiences that also saw Sponsored Products / Brands creative - true unduplicated reach.                                               |
        | **Branded Harvest Candidates**            | Watch only         | Branded search terms surfaced in auto campaigns - defensive harvest, claim before competitors do.                                                      |
        | **CPC by Campaign**                       | Watch only         | CPC by Campaign.                                                                                                                                       |
        | **CTR by Campaign**                       | Watch only         | CTR by Campaign.                                                                                                                                       |
        | **Campaign Comparison**                   | Watch only         | Campaign Comparison, broken down by row.                                                                                                               |
        | **Clicks vs Conversions**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Actions Breakdown**          | Watch only         | Conversion Actions Breakdown.                                                                                                                          |
        | **Conversion Drop Alert**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Funnel**                     | Watch only         | Conversion Funnel, stage by stage.                                                                                                                     |
        | **Conversion Lag**                        | Watch only         | Conversion Lag, compared across items.                                                                                                                 |
        | **Conversion Rate Trend**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Rate by Campaign**           | Watch only         | Conversion Rate by Campaign.                                                                                                                           |
        | **Conversion Rate by Device**             | Watch only         | Conversion Rate by Device.                                                                                                                             |
        | **Conversions Trend**                     | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversions by Campaign**               | Watch only         | Conversions by Campaign.                                                                                                                               |
        | **Conversions by Country**                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversions by Day of Week**            | Watch only         | Conversions by Day of Week.                                                                                                                            |
        | **Conversions by Device**                 | Watch only         | Conversions by Device.                                                                                                                                 |
        | **Conversions by Hour**                   | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **DSP Audience Reach**                    | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **DSP Creative Fatigue Alert**            | Merchant rule      | Creatives whose frequency exceeds 5/audience and whose CTR has dropped >25% vs prior period - refresh the asset.                                       |
        | **DSP Retargeting Reach**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Harvest Promotion Lift**                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Harvest Queue (ready to promote)**      | Watch only         | Auto-campaign search terms with >2 orders + ROAS > target that have not yet been promoted to manual targeting. Promote weekly.                         |
        | **Harvest Velocity**                      | Watch only         | Harvest Velocity over time.                                                                                                                            |
        | **Harvest Velocity Trend**                | Watch only         | Weekly count of terms promoted out of auto-campaigns. Tracks whether the buyer is keeping the harvest queue clear.                                     |
        | **Keyword Catalogue**                     | Watch only         | Active keywords (text, match type, state, bid) from /sp/keywords/list. Amazon does not expose per-keyword spend/conversions/CTR on this endpoint, so t |
        | **Landing Page Revenue**                  | Watch only         | Landing Page Revenue, broken down by row.                                                                                                              |
        | **Negative-Keyword Candidates**           | Watch only         | Search terms with >\$X spend and zero conversions - wasted spend that's recoverable on next sweep.                                                     |
        | **Oldest Unpromoted Harvest Term**        | Merchant rule      | Days since the oldest qualifying search term entered the harvest queue without being promoted.                                                         |
        | **Organic Lift from Ads**                 | Watch only         | % of organic-rank growth attributable to recent ad activity - the long-tail value of Sponsored Brands.                                                 |
        | **Overspending Campaigns**                | Watch only         | Overspending Campaigns, broken down by row.                                                                                                            |
        | **Promotion Conversion Lift**             | Merchant rule      | Average conversion-rate uplift on terms after promotion to manual exact targeting (vs auto baseline).                                                  |
        | **ROAS**                                  | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                                                              |
        | **ROAS Trend**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **ROAS by Campaign**                      | Watch only         | ROAS by Campaign.                                                                                                                                      |
        | **ROAS by Day of Week**                   | Watch only         | ROAS by Day of Week.                                                                                                                                   |
        | **ROAS by Device**                        | Watch only         | ROAS by Device.                                                                                                                                        |
        | **ROAS by Region**                        | Watch only         | ROAS by Region.                                                                                                                                        |
        | **Revenue by Campaign**                   | Watch only         | Revenue by Campaign.                                                                                                                                   |
        | **Search Terms Ready to Promote**         | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Search Terms Report**                   | Watch only         | Search Terms Report, broken down by row.                                                                                                               |
        | **Search-Term Harvest Candidates**        | Watch only         | Auto-campaign search terms with >2 orders that haven't been promoted to manual targeting yet - recurring value.                                        |
        | **Spend by Campaign**                     | Watch only         | Spend by Campaign.                                                                                                                                     |
        | **Sponsored Brands Halo Effect**          | Watch only         | VXCORE-268: Sponsored Brands share of total ad-attributed sales (SB sales ÷ total SP+SB+SD sales) - a directional spend-mix proxy, NOT a measured lift |
        | **TACOS**                                 | Watch only         | Total ACOS - ad spend ÷ total sales (organic + ads). Tracks whether advertising is lifting the whole pie or just shifting attribution.                 |
        | **Top Cities by Conversions**             | Watch only         | Top Cities by Conversions.                                                                                                                             |
        | **Top Performing Campaigns**              | Watch only         | Top Performing Campaigns, broken down by row.                                                                                                          |
        | **Total Revenue**                         | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Underspending Campaigns**               | Watch only         | Underspending Campaigns, broken down by row.                                                                                                           |
        | **Wasted Spend (Negative-KW Candidates)** | Alert band 5 / 50  | Roll up of spend on zero-converting search terms - recoverable next sweep.                                                                             |
        | **Worst Performing Campaigns**            | Watch only         | Campaigns with ROAS below 1 over the trailing 30 days - pause or renegotiate bids. The archetype's second condition (CPA more than double a merchant t |
        | **Zero-Conversion Spend**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Run operations (24 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                                                                                                          |
        | ---------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Ads on No-Buy-Box ASINs** | Alert band 5 / 50  | Ad clicks land on a Buy-Box you don't own - competitor wins the sale, you paid for the click.                                           |
        | **Bid-Modifier Coverage**          | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **Branded vs Non-Branded Mix**     | Watch only         | Branded vs Non-Branded Mix, shown by share.                                                                                             |
        | **Branded vs Non-Branded Spend**   | Watch only         | Branded vs Non-Branded Spend, shown by share.                                                                                           |
        | **Budget Utilisation**             | Alert band 70 / 30 | Description pending editorial review; the signal is live.                                                                               |
        | **CPA Trend**                      | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **CPA by Keyword**                 | Watch only         | CPA by Keyword.                                                                                                                         |
        | **CPC Anomaly**                    | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **CPC Spike Detection**            | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **CPC Trend**                      | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                                                               |
        | **CTR Trend**                      | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **CTR by Keyword**                 | Watch only         | CTR by Keyword.                                                                                                                         |
        | **DSP Reach**                      | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **DSP vs Sponsored Spend**         | Watch only         | DSP vs Sponsored Spend, shown by share.                                                                                                 |
        | **DSP vs Sponsored Spend Mix**     | Watch only         | Spend split between DSP and Sponsored surfaces - rebalances when DSP retargeting underperforms or upper-funnel spend is over-allocated. |
        | **Impression Share**               | Alert band 70 / 40 | Description pending editorial review; the signal is live.                                                                               |
        | **Impressions Trend**              | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **Quality Score Distribution**     | Alert band 7 / 4   | Quality Score Distribution, compared across items.                                                                                      |
        | **Spend Anomaly**                  | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **Spend Over Time**                | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                                                               |
        | **Spend vs Budget**                | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **Top Keywords by Spend**          | Watch only         | Top Keywords by Spend.                                                                                                                  |
        | **Total Spend**                    | Watch only         | Description pending editorial review; the signal is live.                                                                               |
        | **Wasted Spend**                   | Watch only         | Description pending editorial review; the signal is live.                                                                               |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                              | Alert behaviour   | What it tracks                                                                        |
        | ----------------------------------- | ----------------- | ------------------------------------------------------------------------------------- |
        | **Active Ads on Out-of-Stock SKUs** | Alert band 5 / 50 | Spend on ASINs that can't convert. Pause immediately or reroute to in-stock siblings. |
        | **CTR Decline Alert**               | Watch only        | Description pending editorial review; the signal is live.                             |
        | **Non-Branded Harvest Candidates**  | Watch only        | Non-branded harvest = new acquisition surface. Higher value but higher bid risk.      |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal   | Alert behaviour    | What it tracks                                                                                                    |
        | -------- | ------------------ | ----------------------------------------------------------------------------------------------------------------- |
        | **ACOS** | Alert band 25 / 40 | Advertising Cost of Sales - ad spend ÷ attributed sales. Below category benchmark = profitable; above = bleeding. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **87 read** and **140 write** operations across budgetrules, adgroups, campaign budgetrules, targets, campaigns, keywords on Amazon Ads. 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=amazon-ads)

    #### Proven workflow templates (5)

    <AccordionGroup>
      <Accordion title="Budget Pacing Guard">
        **For** Performance marketing manager · **Ready to deploy**

        forecasts over/underspend against plan and stages bounded reallocations for approval.

        Also available on: Meta Ads (Facebook), Quora Ads, LinkedIn Ads, Microsoft Ads (Bing), Snapchat Ads, TikTok Ads, AdRoll, Criteo

        Tested alongside: BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Creative Fatigue Watch">
        **For** Performance marketing manager · **Ready to deploy**

        detects declining response by creative/audience and opens a replacement brief.

        Also available on: Meta Ads (Facebook), Quora Ads, LinkedIn Ads, Microsoft Ads (Bing), Snapchat Ads, TikTok Ads, AdRoll, Criteo

        Tested alongside: BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion Activation QA">
        **For** Performance marketing manager · **Ready to deploy**

        verifies ads, dates, URLs, tracking, inventory and storefront offer before spend begins.

        Also available on: Meta Ads (Facebook), Quora Ads, LinkedIn Ads, Microsoft Ads (Bing), Snapchat Ads, TikTok Ads, AdRoll, Criteo

        Tested alongside: BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Search Query Waste Miner">
        **For** Performance marketing manager · **Ready to deploy**

        clusters irrelevant or expensive queries and drafts negative-keyword actions.

        Also available on: Meta Ads (Facebook), Quora Ads, LinkedIn Ads, Microsoft Ads (Bing), Snapchat Ads, TikTok Ads, AdRoll, Criteo

        Tested alongside: BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Wasted Spend Watch">
        **For** Performance marketing manager · **Ready to deploy**

        alerts on spend with no meaningful outcomes and recommends pause, budget or targeting review.

        Also available on: Meta Ads (Facebook), Quora Ads, LinkedIn Ads, Microsoft Ads (Bing), Snapchat Ads, TikTok Ads, AdRoll, Criteo

        Tested alongside: BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | budgetrules          | 6               | 5                |
      | adgroups             | 4               | 5                |
      | campaign budgetrules | 3               | 6                |
      | targets              | 3               | 6                |
      | campaigns            | 3               | 5                |
      | keywords             | 2               | 5                |
      | negativekeywords     | 2               | 5                |
      | negativetargets      | 2               | 5                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    25 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Amazon Prime Shipping (SFP) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/amazon-prime-shipping

Monitor Amazon Prime Shipping (SFP) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Amazon Prime Shipping (SFP) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=amazon-prime-shipping)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                            |
        | ------------------------------- | ---------------- | --------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live. |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                             |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live. |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.          |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live. |
        | **OTD by Route**                | Watch only       | OTD by Route.                                             |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live. |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.        |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                     |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                              |
        | ----------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**                    | Watch only         | Description pending editorial review; the signal is live.                                                                   |
        | **First-Attempt Delivery Rate**           | Watch only         | Description pending editorial review; the signal is live.                                                                   |
        | **Late Shipments**                        | Watch only         | Description pending editorial review; the signal is live.                                                                   |
        | **On-Time Delivery Rate**                 | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                   |
        | **Prime 1-Day / 2-Day Promise Miss Rate** | Merchant rule      | % of Prime-promise (1-day / 2-day) shipments delivered late. Amazon's SFP eligibility hinges on this; >1% triggers warning. |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                           |
        | ----------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Failed Deliveries**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                |
        | **Late-Shipment Buy Box Loss**            | Merchant rule      | Estimated revenue lost from Buy Box drops triggered by late SFP shipments. Hero - the SFP-Amazon Buy Box death-spiral signal.            |
        | **SFP Eligibility Risk by ASIN**          | Merchant rule      | ASINs at risk of losing the Prime badge - sortable table with current OTD vs SFP threshold. Each row = a Buy Box loss waiting to happen. |
        | **SFP On-Time Delivery vs 99% Threshold** | Alert band 95 / 90 | Amazon SFP requires >=99% on-time delivery. Below 99% = Prime-badge revocation risk. The eligibility-defining metric.                    |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **1 write** operations across tbds on Amazon Prime Shipping (SFP). 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=amazon-prime-shipping)

    #### Ready to build your first Amazon Prime Shipping (SFP) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 1               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Amazon (Selling Partner) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/amazon-seller

Monitor Amazon (Selling Partner) listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Amazon (Selling Partner) listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=amazon-seller)

<CardGroup>
  <Card title="59">
    performance signals
  </Card>

  <Card title="17">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="126">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (59)">
    ### Monitor performance

    59 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (22 signals)">
        | Signal                                     | Alert behaviour     | What it tracks                                                                                |
        | ------------------------------------------ | ------------------- | --------------------------------------------------------------------------------------------- |
        | **A+ Content Coverage (top-50 revenue)**   | Alert band 90 / 70  | Description pending editorial review; the signal is live.                                     |
        | **ASIN Conversion Rank by Query**          | Watch only          | ASIN Conversion Rank by Query.                                                                |
        | **ASINs with Third-Party Offers**          | Alert band 5 / 50   | Private-label ASINs where someone else is also offering , hijack candidates.                  |
        | **Amazon Share of Total Revenue**          | Watch only          | Description pending editorial review; the signal is live.                                     |
        | **Average Order Value**                    | Alert band 0 / -5   | Description pending editorial review; the signal is live.                                     |
        | **Buy-Box Trend (top revenue ASINs)**      | Alert band 90 / 70  | Description pending editorial review; the signal is live.                                     |
        | **Buy-Box Win Rate (top-50 ASINs)**        | Alert band 90 / 70  | Sample top-50 revenue ASINs; cached 6h to respect SP-API rate limits.                         |
        | **Catalogue Drift vs DTC**                 | Alert band 5 / 50   | ASINs whose price/title/image diverge from DTC siblings , brand consistency, MAP, SEO impact. |
        | **Estimated Revenue Lost to Buy-Box Loss** | Alert band 0 / 1000 | Buy-box-loss × 30-day units × ASP , recoverable revenue if buy-box reclaimed.                 |
        | **Fees % of Revenue**                      | Alert band 12 / 18  | Description pending editorial review; the signal is live.                                     |
        | **Orders**                                 | Watch only          | Description pending editorial review; the signal is live.                                     |
        | **Organic vs Ad Sales Share**              | Merchant rule       | Organic vs Ad Sales Share, shown by share.                                                    |
        | **Revenue Over Time**                      | Alert band 0 / -5   | Description pending editorial review; the signal is live.                                     |
        | **Review Velocity (30d)**                  | Merchant rule       | Slowing review velocity = SEO / discoverability erosion.                                      |
        | **Sales Volume Anomalies**                 | Merchant rule       | Sales Volume Anomalies over time.                                                             |
        | **Search Query Share (Brand)**             | Merchant rule       | Description pending editorial review; the signal is live.                                     |
        | **Star Rating Drift (top-50 revenue)**     | Merchant rule       | Star Rating Drift (top-50 revenue) over time.                                                 |
        | **Suppressed Listings**                    | Alert band 5 / 50   | Listings hidden from search until missing attrs are filled , direct revenue blocker.          |
        | **Top ASINs by Revenue**                   | Watch only          | Top ASINs by Revenue.                                                                         |
        | **Top Branded Search Terms**               | Watch only          | Top Branded Search Terms, compared across items.                                              |
        | **Top Non-Branded Search Terms**           | Watch only          | Discovery keywords your brand should defend / expand on , SEO + ad-targeting input.           |
        | **Total Revenue**                          | Alert band 0 / -5   | Description pending editorial review; the signal is live.                                     |
      </Accordion>

      <Accordion title="Run operations (21 signals)">
        | Signal                                  | Alert behaviour   | What it tracks                                                                                              |
        | --------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **A-to-z Guarantee Claims (open)**      | Merchant rule     | Alerts for A-to-z Guarantee Claims (open).                                                                  |
        | **ASINs Approaching Long-Term Storage** | Alert band 5 / 50 | Inventory aging past 270 days , long-term storage fees kick in next cycle.                                  |
        | **ASINs Stocking Out \<7 Days**         | Alert band 0 / 5  | Forecast: current\_stock / 30D-velocity ≤ 7. The action queue for replenishment.                            |
        | **Account Health Creep**                | Alert band 1 / 2  | Alerts for Account Health Creep.                                                                            |
        | **Account Health Status**               | Alert band 1 / 2  | Description pending editorial review; the signal is live.                                                   |
        | **Ad on OOS Detected**                  | Alert band 5 / 50 | Alerts for Ad on OOS Detected.                                                                              |
        | **Avg Days to Settlement**              | Alert band 7 / 21 | Description pending editorial review; the signal is live.                                                   |
        | **Buy-Box Loss Burst**                  | Alert band 0 / 3  | Alerts for Buy-Box Loss Burst.                                                                              |
        | **Days of Cover (avg)**                 | Merchant rule     | Description pending editorial review; the signal is live.                                                   |
        | **FBA Fees**                            | Watch only        | Description pending editorial review; the signal is live.                                                   |
        | **FBA Storage Fees**                    | Merchant rule     | Description pending editorial review; the signal is live.                                                   |
        | **Late Shipment Rate**                  | Alert band 1 / 2  | Description pending editorial review; the signal is live.                                                   |
        | **New Suppressions (24h)**              | Alert band 5 / 50 | Alerts for New Suppressions (24h).                                                                          |
        | **Oldest Pending Payout (days)**        | Alert band 7 / 21 | Description pending editorial review; the signal is live.                                                   |
        | **Order Defect Rate**                   | Alert band 1 / 2  | Stays below 1% or your account gets reviewed for suspension.                                                |
        | **Pending Settlement**                  | Watch only        | Description pending editorial review; the signal is live.                                                   |
        | **Referral Fees**                       | Watch only        | Description pending editorial review; the signal is live.                                                   |
        | **Replenishment Recommendations**       | Watch only        | Per-SKU: current stock, 30D velocity, days-of-cover, suggested replenish qty, lead-time-aware reorder date. |
        | **Return Rate**                         | Alert band 5 / 15 | Description pending editorial review; the signal is live.                                                   |
        | **Sell-Through Rate (FBA)**             | Merchant rule     | Description pending editorial review; the signal is live.                                                   |
        | **Stranded Inventory Value**            | Merchant rule     | Stock with no active buy-box or suppressed listing , cash sitting in warehouses.                            |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                                 | Alert behaviour   | What it tracks                                                                                                     |
        | -------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------ |
        | **Ad Spend on Out-of-Stock ASINs**     | Alert band 5 / 50 | Live \$/day burning on ASINs that can't convert. The pause-now alert.                                              |
        | **Catalogue Drift Revenue at Risk**    | Merchant rule     | Description pending editorial review; the signal is live.                                                          |
        | **Channel Mix (Amazon vs DTC)**        | Merchant rule     | Channel Mix (Amazon vs DTC), shown by share.                                                                       |
        | **MAP Violation Risk (vs DTC)**        | Merchant rule     | Alerts for MAP Violation Risk (vs DTC).                                                                            |
        | **Net Revenue (after fees + refunds)** | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                          |
        | **Pre-Fulfilment Cancel Rate**         | Alert band 1 / 2  | Description pending editorial review; the signal is live.                                                          |
        | **Revenue at Risk (live)**             | Merchant rule     | Sum of (suppressed\_listings × velocity × ASP) + (no-buy-box ASINs × loss-share × velocity) , recoverable revenue. |
        | **Top Buy-Box-Loss ASINs**             | Merchant rule     | Per-ASIN breakdown: buy-box %, units lost, \$ at risk. The action queue for the marketplace manager.               |
      </Accordion>

      <Accordion title="Catalogue quality (7 signals)">
        | Signal                             | Alert behaviour   | What it tracks                                                                                                                           |
        | ---------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Listings**                | Watch only        | Description pending editorial review; the signal is live.                                                                                |
        | **Brand Registry Coverage**        | Merchant rule     | % of own-brand ASINs enrolled in Brand Registry. Enrolment unlocks A+/Stores/Sponsored Brands and protects against hijackers.            |
        | **Inactive Listings**              | Alert band 5 / 50 | Description pending editorial review; the signal is live.                                                                                |
        | **Negative Feedback (30d)**        | Alert band 1 / 2  | Description pending editorial review; the signal is live.                                                                                |
        | **Negative Feedback Spike**        | Alert band 1 / 2  | Alerts for Negative Feedback Spike.                                                                                                      |
        | **Per-ASIN Fee Outliers**          | Merchant rule     | ASINs whose fee % is >2× their category median , repackaging / dimensional-weight optimisation candidates.                               |
        | **Return Reason Clusters by ASIN** | Merchant rule     | Reason-coded returns clustered by ASIN , sizing / quality / listing-mismatch signals. (Replaces Brand-Analytics-gated 'top complaints'.) |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                       | Alert behaviour    | What it tracks                                                                                          |
        | ---------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------- |
        | **Marketplace Health Score** | Alert band 95 / 85 | Composite , auth-rate × buy-box × inverse suppressed × inverse account-health-creep. The single number. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (17)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Ad Spend Likely Burning on OOS / Suppressed ASINs">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Ad spend pointed at out-of-stock or suppressed ASINs buys clicks that cannot convert, burning budget at exactly zero return.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AZ10`
      </Accordion>

      <Accordion title="Listing buy-box win rate below 30% (Amazon-specific; non-applicable elsewhere)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Losing the Buy Box means losing the sale even when the listing wins the search; price, delivery promise and account health drive the algorithm.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-002`
      </Accordion>

      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Order Defect Rate">
        **Severity** high · **Outcome** Run operations · **Fix status** Candidate remediation

        Order Defect Rate is Amazon's primary account-health metric; sustained breaches lead to suspension, which is an existential event for a marketplace business.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ05`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Buy-Box Win Rate Below Target">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Losing the Buy Box means losing the sale even when the listing wins the search; price, delivery promise and account health drive the algorithm.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AZ03`
      </Accordion>

      <Accordion title="Catalogue Drift Watch: Amazon vs DTC">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Candidate remediation

        Catalogue drift between marketplace and DTC (price, content, availability) confuses customers and can breach marketplace policy.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ11`
      </Accordion>

      <Accordion title="FBA: ASINs Aging Toward Long-Term Storage">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        FBA stock aging toward long-term storage accrues fees that can exceed the product's margin; act before the fee date, not after.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ08`
      </Accordion>

      <Accordion title="Late Shipment Rate">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Late shipments damage account health and demote listings; the marketplace punishes the seller, not the carrier.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ06`
      </Accordion>

      <Accordion title="Limited A+ Content Coverage">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        A+ content lifts Amazon conversion measurably; ASINs without it convert below their potential on the same traffic.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AZ02`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Pre-Fulfilment Cancel Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Cancelling before fulfilment counts directly against seller metrics and usually traces to inventory sync problems.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ07`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>

      <Accordion title="Stranded FBA Inventory">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Stranded inventory sits in FBA warehouses unsellable, accruing storage fees while earning nothing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ09`
      </Accordion>

      <Accordion title="Suppressed Amazon Listings">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Suppressed listings earn nothing while they sit invisible; each one is inventory paid for and unsellable until the flag is cleared.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AZ01`
      </Accordion>

      <Accordion title="Third-Party Offers on Private-Label ASINs">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Third-party offers on private-label ASINs are usually hijackers or unauthorised resellers, taking sales and risking counterfeit complaints.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AZ04`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **58 read** and **68 write** operations across notification subscriptions, feeds, notification destinations, orders, reports, report schedules on Amazon (Selling Partner). 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=amazon-seller)

    #### Ready to build your first Amazon (Selling Partner) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | notification subscriptions | 3               | 2                |
      | feeds                      | 2               | 2                |
      | notification destinations  | 2               | 2                |
      | orders                     | 4               | 0                |
      | reports                    | 2               | 2                |
      | report schedules           | 2               | 2                |
      | shippingcarrieraccounts    | 0               | 3                |
      | shippingshipments          | 1               | 2                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Amplitude on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/amplitude

Monitor traffic, conversion and tracking integrity from Amplitude, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Amplitude, and catch instrumentation breaks before decisions are made on bad data.

[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=amplitude)

<CardGroup>
  <Card title="40">
    performance signals
  </Card>

  <Card title="14">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (40)">
    ### Monitor performance

    40 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                                             | Alert behaviour | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **D1 Retention %**                                 | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **D30 Retention %**                                | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Daily Active Users**                             | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Event Taxonomy Drift (new / unexpected events)** | Merchant rule   | Sudden new event names = an untracked release or a renamed event breaking historical funnels.                                                          |
        | **Event Volume Drop (>25% vs baseline)**           | Merchant rule   | Alerts for Event Volume Drop (>25% vs baseline).                                                                                                       |
        | **Event Volume by Platform**                       | Watch only      | Event Volume by Platform.                                                                                                                              |
        | **Goal Completions**                               | Watch only      | Goal Completions from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce against  |
        | **Median Time to Convert**                         | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **New vs Returning Users**                         | Watch only      | New vs Returning Users, shown by share.                                                                                                                |
        | **Pageviews per Session**                          | Watch only      | Pageviews per Session from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce  |
        | **Retention Curve (Nday)**                         | Watch only      | Retention Curve (Nday) over time.                                                                                                                      |
        | **Top 10 Events by Volume**                        | Watch only      | Top 10 Events by Volume.                                                                                                                               |
        | **Top Pages**                                      | Watch only      | Top Pages from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Ampl |
        | **Top Traffic Sources**                            | Watch only      | Top Traffic Sources from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce ag |
        | **Total Event Volume**                             | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Weekly Active Users**                            | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (15 signals)">
        | Signal                                            | Alert behaviour  | What it tracks                                                                                                                                         |
        | ------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Amplitude Tracking Health Score**               | Merchant rule    | Composite: core events firing x funnel-conversion-stable x retention-healthy x no-attribution-drift.                                                   |
        | **Avg Events per User**                           | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Session Length**                            | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Checkout Funnel Conversion %**                  | Merchant rule    | End-to-end conversion across the merchant's primary purchase funnel.                                                                                   |
        | **Core Events Firing (purchase / add\_to\_cart)** | Merchant rule    | If a core ecommerce event stops firing, every downstream funnel + attribution card silently lies.                                                      |
        | **Funnel Conversion Drop (>5pp in 24h)**          | Merchant rule    | Alerts for Funnel Conversion Drop (>5pp in 24h).                                                                                                       |
        | **New Users**                                     | Watch only       | New Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amp |
        | **Real-Time Users**                               | Watch only       | Real-Time Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce again |
        | **Returning Users**                               | Watch only       | Returning Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce again |
        | **Session Conversion Rate**                       | Alert band 2 / 1 | Session Conversion Rate from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce a |
        | **Session Count**                                 | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Stickiness (DAU/MAU)**                          | Merchant rule    | DAU/MAU ratio , Amplitude-distinctive product-stickiness metric.                                                                                       |
        | **Top Cohorts by Conversion**                     | Watch only       | Top Cohorts by Conversion.                                                                                                                             |
        | **Top Conversion Paths**                          | Watch only       | Top Conversion Paths, broken down by row.                                                                                                              |
        | **Users**                                         | Watch only       | Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitu |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Amplitude Funnel Conversion vs Ecom Conversion** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Biggest Funnel Step Drop-off**                   | Merchant rule      | Step with the largest single-step abandonment , names where to focus UX work.                                                                          |
        | **Bounce Rate**                                    | Alert band 40 / 60 | Bounce Rate from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Am |
        | **Cart Abandonment Rate**                          | Alert band 60 / 75 | Cart Abandonment Rate from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce aga |
        | **Event Source vs Ecom Revenue Attribution**       | Merchant rule      | Event Source vs Ecom Revenue Attribution, broken down by row.                                                                                          |
        | **Landing Page Performance vs Bounce**             | Merchant rule      | Landing Page Performance vs Bounce, broken down by row.                                                                                                |
        | **Session Engagement vs Cart Abandonment**         | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal             | Alert behaviour | What it tracks                                                        |
        | ------------------ | --------------- | --------------------------------------------------------------------- |
        | **D7 Retention %** | Merchant rule   | Amplitude-distinctive , D7 is the canonical product-stickiness gauge. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                                | Alert behaviour | What it tracks                                                |
        | ----------------------------------------------------- | --------------- | ------------------------------------------------------------- |
        | **Event Tracking Broken (core event stopped firing)** | Merchant rule   | Alerts for Event Tracking Broken (core event stopped firing). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (14)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Active Users but Zero Purchase Events">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Active users with zero purchase events almost always means purchase tracking is broken rather than nobody buying; every revenue metric downstream reads zero.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP09`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Core Ecommerce Event Stopped Firing">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        A core ecommerce event that stopped firing blinds every downstream report and automation that depends on it, and the gap is invisible until someone looks for the data.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP01`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>

      <Accordion title="D7 Retention Below Baseline">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Weak day-7 retention means acquisition spend is filling a leaky bucket; improving early retention compounds every later cohort.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP04`
      </Accordion>

      <Accordion title="Event Volume Drop vs Prior Period">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        A sharp drop in captured events or sessions usually means a tracking break after a site change, not a real traffic collapse; decisions made on the partial data will be wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP02`
      </Accordion>

      <Accordion title="Funnel Conversion Drop">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Conversion falling through a specific funnel step points at a concrete, findable obstacle: a form, a price reveal, a payment option, an error.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP03, AMP06`
      </Accordion>

      <Accordion title="Low Product Stickiness (DAU/MAU)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Low stickiness (DAU/MAU) means the product or store is a destination people rarely return to; lifecycle marketing has little to work with.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP07`
      </Accordion>

      <Accordion title="Event Taxonomy Drift">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Report only

        Event naming drift splits the same behaviour across multiple names, silently corrupting every funnel and report built on it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP08`
      </Accordion>

      <Accordion title="Missing E-commerce Events in Taxonomy">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Missing ecommerce events in the tracking taxonomy mean revenue questions cannot be answered no matter how good the dashboards are.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AMP05`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across eventlists, funnels, retentions, sessionaverages, useractivitys on Amplitude. 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=amplitude)

    #### Ready to build your first Amplitude 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | eventlists      | 1               | 0                |
      | funnels         | 1               | 0                |
      | retentions      | 1               | 0                |
      | sessionaverages | 1               | 0                |
      | useractivitys   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Anthropic (Claude) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/anthropic

Monitor Anthropic (Claude) health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Anthropic (Claude) health, cost and reliability signals, and catch incidents and runaway spend early.

[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=anthropic)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="17">
    proven workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Control risk and change (12 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                            |
        | ------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------- |
        | **Avg Cost per Million Tokens (30d)** | Watch only         | 30d spend / (30d total tokens / 1,000,000); blended effective rate.                       |
        | **Cache Creation Tokens (30d)**       | Watch only         | Sum of cache\_creation input tokens; what it costs to build the cache.                    |
        | **Cache Read Tokens (30d)**           | Watch only         | Sum of cache\_read\_input\_tokens; prompt-cache reuse volume.                             |
        | **Claude Spend (30d)**                | Alert band 10 / 50 | Sum of cost\_report daily amounts over the last 30d. Admin key required.                  |
        | **Daily Tokens Trend**                | Watch only         | Daily total-token buckets over the last 30d.                                              |
        | **Models Available**                  | Watch only         | Count of models the key can see via /v1/models. Renders with any API key.                 |
        | **Output : Input Token Ratio (30d)**  | Watch only         | output\_tokens / (uncached + cache-read input tokens); generation-heavy vs context-heavy. |
        | **Output Tokens (30d)**               | Watch only         | Sum of output\_tokens over the last 30d.                                                  |
        | **Tokens by Model (30d)**             | Watch only         | Total tokens grouped by model.                                                            |
        | **Total Tokens (30d)**                | Alert band 0 / -50 | uncached input + cache reads + cache creation + output tokens summed over the last 30d.   |
        | **Uncached Input Tokens (30d)**       | Watch only         | Sum of uncached\_input\_tokens over the last 30d.                                         |
        | **Usage Stall Alert**                 | Alert band 0 / -50 | Token-volume change vs the prior 30d; a silent stall means the integration or key broke.  |
      </Accordion>

      <Accordion title="Run operations (4 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                 |
        | ------------------------- | ------------------ | ------------------------------------------------------------------------------ |
        | **Avg Daily Spend (30d)** | Watch only         | 30d spend / days with any cost bucket.                                         |
        | **Daily Spend Trend**     | Watch only         | Daily cost buckets from the cost\_report over the last 30d.                    |
        | **Spend Spike Alert**     | Alert band 10 / 50 | Spend change vs the prior 30d; fires on a spike per the ai\_spend\_trend band. |
        | **Top Cost Line (30d)**   | Watch only         | The single largest cost line by 30d amount.                                    |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                      | Alert behaviour | What it tracks                                                         |
        | --------------------------- | --------------- | ---------------------------------------------------------------------- |
        | **Cost by Line Item (30d)** | Watch only      | cost\_report amounts grouped by line description (model / token type). |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                          | Alert behaviour | What it tracks                                                                       |
        | ------------------------------- | --------------- | ------------------------------------------------------------------------------------ |
        | **Prompt Cache Hit Rate (30d)** | Watch only      | cache\_read / (cache\_read + uncached input) x 100. Higher = cheaper repeat prompts. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **0 write** operations across models, organizationcostreports, organizationusagereportmessages on Anthropic (Claude). 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=anthropic)

    #### Proven workflow templates (17)

    <AccordionGroup>
      <Accordion title="Brand Voice Compliance Review">
        **For** Product content manager · **Ready to deploy**

        flags off-brand, unsupported or inconsistent product claims and proposes corrections.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Completeness Guard">
        **For** Product content manager · **Ready to deploy**

        scores required fields by category and routes the highest-revenue gaps first.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Duplicate Copy Resolver">
        **For** Product content manager · **Ready to deploy**

        detects reused descriptions and produces differentiated drafts from verified attributes.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New SKU Content Factory">
        **For** Product content manager · **Ready to deploy**

        turns approved source data into complete draft PDPs with a human review queue.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PDP Enrichment Queue">
        **For** Product content manager · **Ready to deploy**

        finds thin product pages, generates on-brand copy, and batches changes for approval.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Product Claim Evidence Check">
        **For** Product content manager · **Ready to deploy**

        identifies unsubstantiated claims and requires evidence or removal before publish.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Seasonal Content Refresh">
        **For** Product content manager · **Ready to deploy**

        identifies stale seasonal language and prepares date-safe updates with expiry/rollback.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Supplier Copy Normaliser">
        **For** Product content manager · **Ready to deploy**

        converts inconsistent feeds into house style while preserving factual specifications.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Variant Consistency Sweep">
        **For** Product content manager · **Ready to deploy**

        reconciles names, options, specifications and copy across product families.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                        | Read operations | Write operations |
      | ------------------------------- | --------------- | ---------------- |
      | models                          | 1               | 0                |
      | organizationcostreports         | 1               | 0                |
      | organizationusagereportmessages | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    3 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# APC Overnight on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/apc

Monitor APC Overnight delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor APC Overnight delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=apc)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                            |
        | ------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**              | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Avg Shipping Cost**           | Merchant rule      | Description pending editorial review; the signal is live.                                                 |
        | **Claim Value (open)**          | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Cost Per Shipment Trend**     | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Cost by Zone**                | Watch only         | Cost by Zone.                                                                                             |
        | **Days to Token Expiry**        | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Exception Rate**              | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                 |
        | **High-Cost Shipment Outliers** | Watch only         | High-Cost Shipment Outliers, broken down by row.                                                          |
        | **Label Generation Success**    | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **OTD by Origin Depot**         | Alert band 95 / 90 | OTD broken down by APC depot (70+ UK depots). Identifies depot-level weakness for operational escalation. |
        | **OTD by Route**                | Watch only         | OTD by Route.                                                                                             |
        | **Open Claims**                 | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Returned to Sender**          | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Route Volume Concentration**  | Merchant rule      | Route Volume Concentration, compared across items.                                                        |
        | **Shipments**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                 |
        | **Shipments Over Time**         | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Shipments by Destination**    | Watch only         | Description pending editorial review; the signal is live.                                                 |
        | **Shipments by Service**        | Watch only         | Shipments by Service.                                                                                     |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                          |
        | ------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                               |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                               |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                               |
        | **NextDay 9am Service Promise** | Alert band 95 / 90 | % of NextDay-by-9am consignments delivered before 9am - the premium B2B SLA. Customers paid uplift; misses double-hurt. |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                               |
        | **Pallet Shipment OTD**         | Alert band 95 / 90 | Pallet-only OTD - APC's pallet network has different SLAs vs parcel. Surfaces pallet-specific issues.                   |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                       | Alert behaviour    | What it tracks                                            |
        | ---------------------------- | ------------------ | --------------------------------------------------------- |
        | **APC OTD by Sales Channel** | Alert band 95 / 90 | Per-channel APC OTD.                                      |
        | **Failed Deliveries**        | Merchant rule      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **2 write** operations across tbds on APC Overnight. 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=apc)

    #### Ready to build your first APC Overnight 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 1               | 2                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Asana on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/asana

Monitor Asana performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Asana performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=asana)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                    |
        | ----------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                         |
        | **Avg Lead Time (days)**            | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                              |
        | **Backlog by Status**               | Watch only         | Backlog by Status.                                                                                                                |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Tasks in a Blocked / impeded section - the operational queue's stuck list.                                                        |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                           |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings actually got completed via the Asana pipeline. \<50% means we're filing faster than the team drains. |
        | **In Progress**                     | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Oldest Open (days)**              | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Open Tickets**                    | Merchant rule      | Total open Asana tasks across the default project - top-of-funnel backlog volume.                                                 |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | People with >10 open tasks - capacity bottleneck candidates.                                                                      |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Sprint Progress**                 | Alert band 80 / 50 | Description pending editorial review; the signal is live.                                                                         |
        | **Sprint Velocity (avg)**           | Merchant rule      | Sprint Velocity (avg) over time.                                                                                                  |
        | **Throughput Trend**                | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Tickets Resolved (7d)**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                              |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                         |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **VortexIQ Findings Open**          | Merchant rule      | Asana tasks we filed from audit findings that haven't been completed yet - the live backlog of things VortexIQ surfaced.          |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                         |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                              |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **4 write** operations across tasks, projects, projectsections, sectionaddtasks, taskstorys, users on Asana. 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=asana)

    #### Ready to build your first Asana 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | tasks           | 2               | 2                |
      | projects        | 1               | 0                |
      | projectsections | 1               | 0                |
      | sectionaddtasks | 0               | 1                |
      | taskstorys      | 0               | 1                |
      | users           | 1               | 0                |
      | usermes         | 1               | 0                |
      | workspaces      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Australia Post on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/australia-post

Monitor Australia Post delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Australia Post delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=australia-post)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (23 signals)">
        | Signal                                     | Alert behaviour  | What it tracks                                                                                                                              |
        | ------------------------------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**                         | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Avg Shipping Cost**                      | Merchant rule    | Description pending editorial review; the signal is live.                                                                                   |
        | **Charity / Returns Parcel Volume**        | Watch only       | AusPost's reverse-logistics service tier has separate pricing. Volume drift = RMA workflow change.                                          |
        | **Claim Value (open)**                     | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Cost Per Shipment Trend**                | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Cost by Zone**                           | Watch only       | Cost by Zone.                                                                                                                               |
        | **Cost per Parcel by Zone (AUD)**          | Watch only       | AusPost prices by zone (5 metro zones + 4 regional). Annual October price review can shift zones materially.                                |
        | **Days to Token Expiry**                   | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Exception Rate**                         | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                   |
        | **Express Post Address-Eligibility Rate**  | Merchant rule    | % of orders eligible for AusPost Express Post next-business-day service. Drops when AusPost reclassifies postcodes , usually annual review. |
        | **High-Cost Shipment Outliers**            | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                            |
        | **International Destinations , Top 10**    | Watch only       | International Destinations , Top 10, compared across items.                                                                                 |
        | **Label Generation Success**               | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Label Print Failures Spike**             | Alert band 0 / 5 | Alerts for Label Print Failures Spike.                                                                                                      |
        | **OTD by Route**                           | Watch only       | OTD by Route.                                                                                                                               |
        | **Open Claims**                            | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Parcel Post vs Express vs Standard Mix** | Watch only       | Parcel Post vs Express vs Standard Mix, shown by share.                                                                                     |
        | **Returned to Sender**                     | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Route Volume Concentration**             | Merchant rule    | Route Volume Concentration, compared across items.                                                                                          |
        | **Shipments**                              | Merchant rule    | Description pending editorial review; the signal is live.                                                                                   |
        | **Shipments Over Time**                    | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Shipments by Destination**               | Watch only       | Description pending editorial review; the signal is live.                                                                                   |
        | **Shipments by Service**                   | Watch only       | Shipments by Service.                                                                                                                       |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                                             | Alert behaviour    | What it tracks                                                                                                                       |
        | ------------------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **AusPost Cost vs Sendle by Zone**                                 | Merchant rule      | Sendle's flat-rate-by-zone model can beat AusPost on certain metro-to-metro zones. Surface where alternative carrier rates apply.    |
        | **Express Post Next-Business-Day OTD**                             | Alert band 95 / 90 | AusPost Express Post guarantees next-business-day delivery between eligible postcodes , misses trigger automatic refund eligibility. |
        | **Express Post SLA Breach (refund-clause trigger)**                | Merchant rule      | Express Post guarantee triggers automatic-refund eligibility on misses. Surface fast.                                                |
        | **Failed Deliveries**                                              | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Orders with Carrier Dispatch SLA Missed**                        | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Return Rate by Service Code**                                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Shipments with Tracking-Event Gap >24h (domestic) / >5d (intl)** | Alert band 0 / 10  | Different SLAs for domestic vs international , internationals get 5-day grace window for customs clearance.                          |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Transit (days)**                          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **First-Attempt Delivery Rate**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **International Customs Clearance Rate (\<5d)** | Merchant rule      | % of international parcels clearing AU export + destination customs within 5 days. Below 80% suggests paperwork issues (B374 customs declaration) or d |
        | **Late Shipments**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Time Delivery Rate**                       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                     | Alert behaviour | What it tracks                                     |
        | ------------------------------------------ | --------------- | -------------------------------------------------- |
        | **AusPost Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for AusPost Tracking API Unavailable / 5xx. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **2 write** operations across shippingshipments, shippingaccounts, shippingreturns, shippingtracks on Australia Post. 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=australia-post)

    #### Ready to build your first Australia Post 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | shippingshipments | 1               | 1                |
      | shippingaccounts  | 1               | 0                |
      | shippingreturns   | 0               | 1                |
      | shippingtracks    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Authorize.net on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/authorize-net

Monitor Authorize.net payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Authorize.net payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=authorize-net)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (11 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                           |
        | ----------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                  | Watch only         | Customers who saw the Cardinal 3DS challenge and bailed (expired session). UX friction, not issuer rejection.                            |
        | **Captured vs Commerce Revenue**          | Merchant rule      | Reconciliation gap between gateway-captured dollars and commerce order revenue. >2% drift = double-count, refund-timing or routing leak. |
        | **Chargeback Rate**                       | Watch only         | Buyer-initiated reversals / settled. >0.9% triggers Visa AMP / Mastercard ECM monitoring; >1% risks account termination.                 |
        | **Decline Rate**                          | Alert band 5 / 8   | Declined + voided + FDS-rejected over all attempts. 3DS-failed counts here; 3DS-abandoned does not.                                      |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule      | When Authorize.Net declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss.               |
        | **Dispute Rate**                          | Watch only         | Transactions in active dispute (pending + recently resolved). The leading indicator that pairs with chargeback rate.                     |
        | **Refund Rate**                           | Alert band 3 / 8   | Refund value / settled revenue. Merchant-initiated returns view, separate from chargebacks.                                              |
        | **Refund Volume**                         | Merchant rule      | Absolute dollars refunded (full + partial). Subtract from gross volume for a net-of-refunds figure.                                      |
        | **Top Decline Reasons**                   | Watch only         | responseReasonCode breakdown (2 DO\_NOT\_HONOR, 65 exceeds limit, 27 AVS mismatch, 200 3DS failed…). First card to open on a spike.      |
        | **Total Transactions**                    | Alert band 0 / -15 | Count of settled authCapture / captureOnly transactions. Refunds, voids, declines and FDS-held excluded.                                 |
        | **Total Volume**                          | Alert band 0 / -15 | Gross settled dollars through the gateway (pre-refund, pre-fees, pre-chargeback). Gateway-level, not bank-funded.                        |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                               |
        | -------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Settlement Time (days)**   | Watch only         | Average days from capture to acquirer-funded bank deposit. Acquirer-driven (T+1/T+2 cards, T+3/T+5 ACH), not gateway-driven. |
        | **Oldest Pending Payout (days)** | Alert band 2 / 5   | Days since the oldest unfunded capture. Anything past the 5-day acquirer window is stuck money - investigate.                |
        | **Pending Payouts**              | Watch only         | Captured-but-not-yet-acquirer-funded balance. The in-flight money: customer paid, acquirer hasn't disbursed yet.             |
        | **Success Rate**                 | Alert band 95 / 90 | Settled / all-attempts. The best single gauge of auth quality, BIN routing and FDS-rule sanity.                              |
        | **Volume Trend**                 | Alert band 0 / -15 | Daily settled volume by settlement date. Shows batch-cut-off rhythm, B2B weekday pulse and EOM surges.                       |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                                            |
        | ----------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------- |
        | **Average Transaction** | Merchant rule   | SUM(settleAmount) / COUNT(settled). Mostly mix-shift, not basket growth - open the channel split first.                   |
        | **Top Payment Methods** | Watch only      | Visa / MC / Amex / Discover / Diners / JCB / eCheck split by count and volume. Where interchange-optimisation gains hide. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **6 write** operations across report :authenticatetestrequests, report :getsettledbatchlistrequests, report :gettransactiondetailsrequests, report :gettransactionlistforbatchs, report :getunsettledtransactionlistrequests, xmlrequestapis on Authorize.net. 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=authorize-net)

    #### Ready to build your first Authorize.net 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                    | Read operations | Write operations |
      | ------------------------------------------- | --------------- | ---------------- |
      | report :authenticatetestrequests            | 0               | 1                |
      | report :getsettledbatchlistrequests         | 0               | 1                |
      | report :gettransactiondetailsrequests       | 0               | 1                |
      | report :gettransactionlistforbatchs         | 0               | 1                |
      | report :getunsettledtransactionlistrequests | 0               | 1                |
      | xmlrequestapis                              | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# AWeber on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/aweber

Monitor email revenue and deliverability for AWeber, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for AWeber, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=aweber)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (11 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                      |
        | ----------------------------- | ------------------ | ----------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule      | Broadcasts grouped by status (sent, draft, scheduled).                              |
        | **Checkout-to-Order Rate**    | Alert band 60 / 40 | Share of started checkouts that became paid orders.                                 |
        | **Click-to-Open Rate**        | Alert band 10 / 3  | Clicks as a share of opens - engagement quality independent of open-rate inflation. |
        | **Conversion Rate**           | Alert band 3 / 1   | Orders as a share of emails sent. Ties send volume to revenue.                      |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Share of delivered emails that earned a click. The clearest engagement signal.      |
        | **List Count**                | Merchant rule      | Number of audiences on the account.                                                 |
        | **Lists Overview**            | Merchant rule      | Every audience with its member count.                                               |
        | **Revenue per Recipient**     | Merchant rule      | Revenue divided by emails sent. What each address is worth per send.                |
        | **Revenue per Send**          | Merchant rule      | Revenue divided by emails sent - the efficiency of each send.                       |
        | **Top Lists by Name**         | Merchant rule      | Largest audiences by member count.                                                  |
        | **Total Revenue**             | Merchant rule      | Placed-order revenue attributed to AWeber email sends. The hero number.             |
      </Accordion>

      <Accordion title="Run operations (10 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                |
        | ----------------------------- | ------------------ | --------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts.                                                     |
        | **Email Open Rate**           | Alert band 20 / 10 | Share of delivered emails opened. Mailbox privacy can inflate this - pair with click-to-open. |
        | **Flow Count Summary**        | Merchant rule      | How many follow-up automations exist on the account.                                          |
        | **Flow Status Breakdown**     | Merchant rule      | Automations split by status (live, draft, paused).                                            |
        | **Flow Trigger Types**        | Merchant rule      | Automations grouped by what triggers them.                                                    |
        | **Flows List**                | Merchant rule      | Every follow-up automation and its current status.                                            |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                                     |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to AWeber email in the window.                                              |
        | **Segments Overview**         | Merchant rule      | Saved segments and their sizes.                                                               |
        | **Total Sends**               | Merchant rule      | Total emails sent across broadcasts and follow-ups in the window.                             |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                  | Alert behaviour      | What it tracks                                                                                  |
        | ----------------------- | -------------------- | ----------------------------------------------------------------------------------------------- |
        | **Bounce Rate**         | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation; AWE-DEL-001 fires above 5%. |
        | **Delivery Rate**       | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention; AWE-DEL-003 fires.    |
        | **Email Health KPIs**   | Merchant rule        | Delivered, bounced and unsubscribed at a glance - your deliverability vitals.                   |
        | **Engagement Funnel**   | Merchant rule        | Sent → delivered → opened → clicked. Drop-offs expose deliverability vs content weakness.       |
        | **Refund Rate**         | Alert band 2 / 8     | Share of attributed orders later refunded.                                                      |
        | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam complaints per send. Above 0.1% puts deliverability at risk; AWE-DEL-002 fires.            |
        | **Unsubscribe Rate**    | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.                      |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery Rate below 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        When more than 1 in 20 emails fails to arrive at all, every campaign, promotion and transactional message built on that list underperforms, and the gap compounds as the list grows.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AWE-DEL-003`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Spam Complaint Rate above ISP threshold">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AWE-DEL-002`
      </Accordion>

      <Accordion title="Email Bounce Rate too high">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AWE-DEL-001`
      </Accordion>

      <Accordion title="No follow-up automation series live">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AWE-FLOW-001`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Limited segmentation: fewer than 3 lists/segments">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AWE-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **1 write** operations across account listsubscribers, accounts, account lists, account listcampaigns, account listcampaignstats, account listlandingpages on AWeber. 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=aweber)

    #### Ready to build your first AWeber 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | account listsubscribers   | 1               | 1                |
      | accounts                  | 1               | 0                |
      | account lists             | 1               | 0                |
      | account listcampaigns     | 1               | 0                |
      | account listcampaignstats | 1               | 0                |
      | account listlandingpages  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Amazon Web Services on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/aws

Monitor Amazon Web Services health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Amazon Web Services health, cost and reliability signals, and catch incidents and runaway spend early.

[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=aws)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (19 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                           |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AWS Account**                     | Watch only         | Account ID from STS GetCallerIdentity (caller ARN shown as the card detail). Renders with any valid key pair, no Cost Explorer needed.                   |
        | **AWS Spend (30d)**                 | Alert band 10 / 50 | Sum of GetCostAndUsage daily UnblendedCost amounts across all services over the last 30d. Cost Explorer must be enabled.                                 |
        | **AWS Spend (7d)**                  | Watch only         | Sum of daily UnblendedCost amounts over the last 7d.                                                                                                     |
        | **Active Services (30d)**           | Watch only         | Count of distinct SERVICE groups with UnblendedCost > 0 in the last 30d.                                                                                 |
        | **Avg Daily Spend (30d)**           | Watch only         | 30d spend / days with any nonzero daily cost bucket.                                                                                                     |
        | **Cloud Health Score**              | Alert band 90 / 70 | 0-100 composite from the daily cost matrix: 100 minus 20 when 30d spend is up >10% vsP (40 when >50%), minus 10 when the month-end forecast runs         |
        | **Cost by Service (30d)**           | Watch only         | 30d UnblendedCost grouped by the SERVICE dimension (GetCostAndUsage GroupBy DIMENSION SERVICE); top 10 services.                                         |
        | **Daily Spend Trend**               | Watch only         | Daily all-service UnblendedCost totals from GetCostAndUsage over the last 30d.                                                                           |
        | **Forecast Month-End Spend**        | Watch only         | GetCostForecast Total.Amount (UNBLENDED\_COST, MONTHLY) from today to the first day of next month. Best effort: needs at least one day of cost history.  |
        | **Forecast Overrun Alert**          | Alert band 10 / 50 | (GetCostForecast month-end Total.Amount - trailing 30d spend) / trailing 30d spend x 100; fires per the ai\_spend\_trend band when the forecast runs hot |
        | **Month-to-Date Spend**             | Watch only         | Sum of daily UnblendedCost amounts from the 1st of the current month to today.                                                                           |
        | **Peak Daily Spend (30d)**          | Watch only         | The single largest daily all-service UnblendedCost total in the last 30d (date shown as the card detail).                                                |
        | **Previous 30d Spend**              | Watch only         | Sum of daily UnblendedCost amounts for days 31-60 back (the previous 30d comparison window).                                                             |
        | **Spend Change vs Previous 30d**    | Watch only         | (current 30d spend - previous 30d spend) / previous 30d spend x 100.                                                                                     |
        | **Spend Spike Alert**               | Alert band 10 / 50 | Spend change vs the prior 30d window ((current - previous) / previous x 100); fires on a spike per the ai\_spend\_trend band.                            |
        | **Spend Yesterday**                 | Watch only         | All-service UnblendedCost total for yesterday's daily bucket (the most recent complete day).                                                             |
        | **Top 5 Services Share (30d)**      | Watch only         | Sum of the top 5 services' 30d UnblendedCost / total 30d UnblendedCost x 100.                                                                            |
        | **Top Service Concentration (30d)** | Watch only         | Top service 30d UnblendedCost / total 30d UnblendedCost x 100.                                                                                           |
        | **Top Service by Cost (30d)**       | Watch only         | The single largest service by 30d UnblendedCost (service name shown as the card detail).                                                                 |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                                                                         |
        | ----------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Weekend Spend Share (30d)** | Watch only      | Saturday + Sunday UnblendedCost / total 30d UnblendedCost x 100. Always-on infrastructure sits near 28.6% (2 of 7 days); much lower means workloads sc |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **3 write** operations across (getcostandusage)s, (getcostforecast)s, resources on Amazon Web Services. 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=aws)

    #### Ready to build your first Amazon Web Services 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | (getcostandusage)s | 0               | 1                |
      | (getcostforecast)s | 0               | 1                |
      | resources          | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Microsoft Azure on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/azure

Monitor Microsoft Azure health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Microsoft Azure health, cost and reliability signals, and catch incidents and runaway spend early.

[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=azure)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (19 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Services (30d)**        | Watch only         | Count of distinct ServiceName values with Cost > 0 in the last 30d of the cost rows.                                                                   |
        | **Annualised Run Rate**          | Watch only         | Avg daily spend (30d Cost sum / days with spend) x 365; what the current burn costs over a year.                                                       |
        | **Avg Cost per Service (30d)**   | Watch only         | 30d Cost sum / count of distinct ServiceName values with Cost > 0 in the window.                                                                       |
        | **Avg Daily Spend (30d)**        | Watch only         | 30d Cost sum / count of distinct UsageDate values with Cost > 0 in the window.                                                                         |
        | **Azure Spend (30d)**            | Alert band 10 / 50 | Sum of Cost over the last 30d of daily rows from the CostManagement/query 60d Daily ActualCost response; change vs the previous 30d window. Cost Manag |
        | **Azure Spend (7d)**             | Watch only         | Sum of Cost for daily rows with UsageDate in the last 7 days.                                                                                          |
        | **Billing Currency**             | Watch only         | Currency column value from the CostManagement/query rows (e.g. USD, GBP); also drives the currency symbol on every spend card.                         |
        | **Cloud Health Score**           | Alert band 90 / 70 | Composite 0-100: start at 100, minus 30 if 30d spend is up >50% vsP (15 if up >25%), minus 10 if the top service is >80% of 30d spend, minus           |
        | **Cost by Service (30d)**        | Watch only         | Cost summed per ServiceName over the last 30d of the CostManagement/query rows; top 10 services by spend.                                              |
        | **Daily Spend Trend**            | Watch only         | Cost summed per UsageDate over the last 30d of the CostManagement/query Daily rows.                                                                    |
        | **Days with Spend (30d)**        | Watch only         | Count of distinct UsageDate values with Cost > 0 in the last 30d; gaps mean idle days or missing cost data.                                            |
        | **Month-to-Date Spend**          | Watch only         | Sum of Cost for daily rows with UsageDate on or after the 1st of the current month, from the same CostManagement/query response.                       |
        | **New Cost Services (30d)**      | Watch only         | Count of ServiceName values with Cost > 0 in the current 30d window but zero cost in the previous 30d window; new services quietly adding spend.       |
        | **Peak Daily Spend (30d)**       | Watch only         | Max of the per-UsageDate Cost sums over the last 30d; detail names the peak day.                                                                       |
        | **Previous 30d Spend**           | Watch only         | Sum of Cost over the previous 30d window (days 31-60) of the same 60d Daily cost response; the vsP baseline.                                           |
        | **Service Concentration (30d)**  | Watch only         | Top service 30d Cost sum / total 30d Cost sum x 100; a very concentrated bill is a single point of cost failure.                                       |
        | **Spend Change vs Previous 30d** | Watch only         | (current 30d Cost sum - previous 30d Cost sum) / previous 30d Cost sum x 100, from the 60d Daily cost rows.                                            |
        | **Spend Spike Alert**            | Alert band 10 / 50 | Spend change vs the prior 30d from the 60d Daily cost rows; fires on a spike per the ai\_spend\_trend band.                                            |
        | **Top Service by Cost (30d)**    | Watch only         | The single largest ServiceName by 30d Cost sum; detail names the service.                                                                              |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour | What it tracks                                                                                                                        |
        | ---------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
        | **Subscription State** | Watch only      | state from GET /subscriptions/ (api-version=2022-12-01), e.g. Enabled or Disabled; detail shows displayName. Renders with the token + |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **2 write** operations across oauth2tokens, subscriptions, subscription providermicrosoftcostmanagementquerys on Microsoft Azure. 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=azure)

    #### Ready to build your first Microsoft Azure 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                           | Read operations | Write operations |
      | -------------------------------------------------- | --------------- | ---------------- |
      | oauth2tokens                                       | 0               | 1                |
      | subscriptions                                      | 1               | 0                |
      | subscription providermicrosoftcostmanagementquerys | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Azure DevOps on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/azure-devops

Monitor Azure DevOps health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Azure DevOps health, cost and reliability signals, and catch incidents and runaway spend early.

[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=azure-devops)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="836">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                         |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Build Duration**              | Watch only         | Average of (finishTime - startTime) in milliseconds across status=completed builds queued within the last 30d.                         |
        | **Avg Commits / Active Repo (30d)** | Watch only         | 30d commit count / count of scanned repos with at least 1 commit in 30d; concentration of delivery across the fleet.                   |
        | **Build Failure Rate Alert**        | Alert band 95 / 80 | Build success rate (result=succeeded / completed) queued within 30d; fires when it crosses the vc\_ci\_pass\_rate band (bad at \<80%). |
        | **Build Success Rate (30d)**        | Alert band 95 / 80 | Builds with result=succeeded / all completed builds (status=completed) queued within 30d, x100, across the top 10 scanned projects.    |
        | **Builds (30d)**                    | Watch only         | Count of builds queued within the last 30d from GET .../build/builds across the top 10 scanned projects.                               |
        | **Commits by Repository**           | Watch only         | Commits in the last 30d grouped by repo full name (project/name), top 10 by count.                                                     |
        | **Median Open PR Age**              | Alert band 3 / 14  | Median of (now - creationDate) in days across all status=active pull requests; drives vc\_pr\_age\_days (lower is better).             |
        | **Most Active Repo (30d)**          | Watch only         | The scanned repo with the most commits in the last 30d; value = commit count, detail = repo full name (project/name).                  |
        | **Open PRs by Repository**          | Watch only         | Open (status=active) pull requests grouped by repo full name (project/name), top 10 by count.                                          |
        | **PR Age Alert**                    | Alert band 3 / 14  | Median open-PR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d).                                            |
        | **Repositories by Project**         | Watch only         | Scanned repositories grouped by their parent project name, top 10 by count.                                                            |
        | **Stale PRs (>14d)**                | Watch only         | Count of status=active pull requests whose age (now - creationDate) exceeds 14 days.                                                   |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                           |
        | ------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Commits (30d)**         | Alert band 0 / -50 | Count of commits from GET .../repositories//commits (author.date within 30d) summed across the top 15 scanned repos; change\_pct vs the p                |
        | **Completed PRs (30d)**   | Watch only         | Count of pull requests with status=completed and closedDate within the last 30d (searchCriteria.status=completed) across the top 15 scanned repos.       |
        | **Deploy Cadence Trend**  | Alert band 0 / -50 | Daily commit count over the last 30d (author.date), summed across the top 15 scanned repos; value = 30d total, change\_pct vs the prior 30d drives vc\_d |
        | **Deploy Stall Alert**    | Alert band 0 / -50 | Commit-count change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band.                                                            |
        | **Open Pull Requests**    | Watch only         | Count of pull requests with status=active from GET .../pullrequests?searchCriteria.status=active across the top 15 scanned repos.                        |
        | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x build success rate (30d, result=succeeded / completed) + 0.3 x PR-age score (100 at \<=3d median open-PR age, 0 at >=14d)        |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                    | Alert behaviour | What it tracks                                                                                                                                     |
        | ------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned PRs (30d)**   | Watch only      | Count of pull requests with status=abandoned and closedDate within the last 30d (searchCriteria.status=abandoned) across the top 15 scanned repos. |
        | **Canceled Builds (30d)** | Watch only      | Count of builds with result=canceled, queued within the last 30d, across the top 10 scanned projects.                                              |
        | **Failed Builds (30d)**   | Watch only      | Count of builds with result=failed and status=completed, queued within the last 30d, across the top 10 scanned projects.                           |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                                 |
        | ----------------------- | --------------- | -------------------------------------------------------------------------------------------------------------- |
        | **Daily Commits Trend** | Watch only      | Commits grouped by day over the last 30d (author.date), summed across the top 15 scanned repos.                |
        | **Projects**            | Watch only      | Count of projects returned by GET //\_apis/projects (state=wellFormed).                                        |
        | **Repositories**        | Watch only      | Count of repositories returned by GET ...//\_apis/git/repositories, summed across the top 10 scanned projects. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CI pass rate below 80%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CI-001`
      </Accordion>

      <Accordion title="Delivery cadence dropped more than 50% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CADENCE-001`
      </Accordion>

      <Accordion title="Median open pull-request age above 14 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-PR-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **420 read** and **416 write** operations across apidashboarddashboardwidgets, apigitrepositorypullrequestreviewers, apiserviceendpointendpoints, apisymbolrequests, apiauditstreams, apibuildbuilds on Azure DevOps. 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=azure-devops)

    #### Ready to build your first Azure DevOps 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                             | Read operations | Write operations |
      | ------------------------------------ | --------------- | ---------------- |
      | apidashboarddashboardwidgets         | 2               | 6                |
      | apigitrepositorypullrequestreviewers | 2               | 6                |
      | apiserviceendpointendpoints          | 2               | 6                |
      | apisymbolrequests                    | 2               | 6                |
      | apiauditstreams                      | 2               | 4                |
      | apibuildbuilds                       | 2               | 4                |
      | apibuilddefinitions                  | 2               | 4                |
      | apidashboarddashboards               | 2               | 4                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Basecamp on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/basecamp

Monitor Basecamp performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Basecamp performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=basecamp)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (20 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**                      | Alert band 3 / 7   | Mean days from to-do creation to completion.                                                                                                           |
        | **Avg Lead Time (days)**                       | Merchant rule      | Mean days from finding creation to to-do completion.                                                                                                   |
        | **Avg Time-to-Fix (days)**                     | Merchant rule      | Mean days from finding creation to to-do completion.                                                                                                   |
        | **Backlog by Priority**                        | Merchant rule      | Priority derived from VortexIQ name-prefix convention - Basecamp has no priority field.                                                                |
        | **Backlog by Status**                          | Watch only         | Open vs done split - the only two states Basecamp's data model exposes.                                                                                |
        | **Blocked Tickets**                            | Alert band 3 / 8   | To-dos tagged blocked by VortexIQ convention - the operational queue's stuck list.                                                                     |
        | **Critical Findings Without a Basecamp To-do** | Merchant rule      | Critical / high findings older than 7 days with no Basecamp to-do - coverage gap. The auto-dispatch missed these or the merchant disabled it.          |
        | **Cycle Time by Priority**                     | Merchant rule      | Cycle time bucketed by VortexIQ-tagged priority.                                                                                                       |
        | **Finding Resolution Rate (90d)**              | Alert band 75 / 50 | Share of findings ticked complete in 90 days. The most useful single number for a Basecamp owner - Basecamp surfaces no velocity or throughput nativel |
        | **In Progress**                                | Watch only         | Basecamp has no native in-progress status; this maps to-dos VortexIQ tags as started via name-prefix convention.                                       |
        | **Oldest Open (days)**                         | Alert band 30 / 90 | Age of the longest-open to-do - backlog-rot signal Basecamp does not surface natively.                                                                 |
        | **Open Tickets**                               | Merchant rule      | Total open to-dos across the default project - top-of-funnel backlog volume. A to-do counts as open until the checkbox is ticked.                      |
        | **Overloaded Assignees (>10 open)**            | Alert band 0 / 1   | People with >10 open to-dos - capacity bottleneck candidates.                                                                                          |
        | **Throughput Trend**                           | Watch only         | Completions per day over 30 days.                                                                                                                      |
        | **Tickets Resolved (7d)**                      | Merchant rule      | To-dos ticked complete in the last 7 days vs the prior 7 - the closest thing Basecamp has to throughput.                                               |
        | **Tickets by Assignee**                        | Merchant rule      | Open to-dos per assignee - capacity distribution across the team.                                                                                      |
        | **Unassigned Tickets**                         | Alert band 5 / 20  | Open to-dos with no assignee - work nobody owns.                                                                                                       |
        | **VortexIQ Findings In Progress**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings Open**                     | Merchant rule      | Open to-dos VortexIQ created from audit findings - the live backlog of things we surfaced. Basecamp surfaces no rollups, so this is the only place the |
        | **VortexIQ Findings Resolved**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (3 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                                                                                                                          |
        | -------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Scope Added Mid-Sprint** | Merchant rule      | To-dos added after the cadence started - scope creep on the active findings batch.                                                                      |
        | **Sprint Progress**        | Alert band 80 / 50 | Completed-ratio of the active findings cadence (Basecamp's completed\_ratio on the to-do list). Basecamp has no sprints; this models the cadence betwee |
        | **Sprint Velocity (avg)**  | Merchant rule      | To-dos completed per cadence, last 5 cadences.                                                                                                          |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Open to-dos in the Vortex IQ Findings list with no movement in 14+ days. On Basecamp this is the ONLY staleness signal - no priority field, no last-to |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **4 write** operations across buckettodocompletionjsons, buckettodolisttodojsons, bucketrecordingcommentjsons, buckettodos, buckettodolisttodocompletedjsons, buckettodosettodolistjsons on Basecamp. 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=basecamp)

    #### Ready to build your first Basecamp 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                         | Read operations | Write operations |
      | -------------------------------- | --------------- | ---------------- |
      | buckettodocompletionjsons        | 0               | 2                |
      | buckettodolisttodojsons          | 1               | 1                |
      | bucketrecordingcommentjsons      | 0               | 1                |
      | buckettodos                      | 1               | 0                |
      | buckettodolisttodocompletedjsons | 1               | 0                |
      | buckettodosettodolistjsons       | 1               | 0                |
      | myprofilejsons                   | 1               | 0                |
      | projectjsons                     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Baserow on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/baserow

Monitor Baserow publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Baserow publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=baserow)

<CardGroup>
  <Card title="10">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (10)">
    ### Monitor performance

    10 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (7 signals)">
        | Signal                      | Alert behaviour      | What it tracks                                                                                                                           |
        | --------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Field Count**             | Watch only           | Number of columns on the monitored table - baseline for schema-drift detection.                                                          |
        | **Freshness Lag (minutes)** | Alert band 60 / 1440 | Same stale-table detector as Hours Since Last Row Change, in minutes - the byo\_data\_source archetype's freshness\_lag band is minutes. |
        | **Open-Status Rows**        | Alert band 10 / 50   | Rows whose status is not in the done set - the unactioned queue (returns / order exceptions). Gated on a configured status field.        |
        | **Row Count**               | Watch only           | Total rows in the monitored table - from the `count` field on the list-rows response.                                                    |
        | **Rows Added (24h)**        | Merchant rule        | New rows in the last 24h - needs a Created-on field on the table (Baserow does not expose row creation time otherwise).                  |
        | **Saved Views**             | Watch only           | Number of saved views (grid / gallery / form / kanban / calendar) on the table.                                                          |
        | **Tables in Database**      | Watch only           | Inventory of tables in the parent database - id, name, row count. Gated on a configured database\_id.                                    |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                          | Alert behaviour   | What it tracks                                                                                                                 |
        | ------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Hours Since Last Row Change** | Alert band 6 / 24 | Stale-table detector - hours since the most-recent row edit. >24h on a live ops table means the upstream feed has gone silent. |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                       | Alert behaviour | What it tracks                                                                                                                                        |
        | -------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Open Order-Exception Rows on Live Orders** | Merchant rule   | Manual order-exception queue rows that map to live, paid ecom orders still sitting unresolved - revenue stuck in a spreadsheet. Needs an ecom sibling |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour   | What it tracks                                                                                                                                   |
        | ---------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Empty Field Rate %** | Alert band 2 / 15 | Share of field values left blank across the sampled rows (up to the 200-row page cap), measured against every column returned by the Fields API. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Data-source API token invalid or access revoked">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this token fails, VortexIQ stops pulling data from this source entirely, and every card and finding built on it 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: `BYO-AUTH-001`
      </Accordion>

      <Accordion title="Source not updated in over 24h (stale data)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        A source that has not updated in over a day means every conclusion drawn from it describes yesterday; the staleness is invisible unless surfaced.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-FRESH-001`
      </Accordion>

      <Accordion title="Required-field empty rate above 15%">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When required fields are empty in more than 15 percent of rows, every downstream calculation inherits the gaps and quietly under-reports.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-DATA-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **3 write** operations across databaserowtables, databasefieldtables, databasetabledatabases, databaseviewtables, users, workspaces on Baserow. 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=baserow)

    #### Ready to build your first Baserow 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | databaserowtables      | 1               | 3                |
      | databasefieldtables    | 1               | 0                |
      | databasetabledatabases | 1               | 0                |
      | databaseviewtables     | 1               | 0                |
      | users                  | 1               | 0                |
      | workspaces             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Better Uptime on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/better-uptime

Monitor Better Uptime health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Better Uptime health, cost and reliability signals, and catch incidents and runaway spend early.

[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=better-uptime)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="2">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                                 |
        | ---------------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Merchant rule                | Incidents acknowledged by an on-call responder - work is in flight.                            |
        | **Alerts Firing**            | Alert band 0 / 3             | Incidents currently in the Started state - alerts that have fired but not yet been picked up.  |
        | **Incidents Open**           | Alert band 0 / 3             | Unresolved incidents across all monitors right now.                                            |
        | **Incidents Resolved (24h)** | Merchant rule                | Incidents closed in the last 24 hours - recovery throughput.                                   |
        | **Mean Time To Acknowledge** | Alert band 300000 / 900000   | Average gap from incident start to first acknowledgement - responsiveness of the on-call rota. |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Average gap from incident start to resolution - how fast things actually get fixed.            |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Rolling availability vs the SLA target. 99.9% is two-nines-plus; below 99.5% is a breach.      |
        | **Services Degraded**        | Watch only                   | Monitors responding slowly or partially - the early-warning band before down.                  |
        | **Services Down**            | Alert band 0 / 1             | Monitors currently failing their check - customer-facing outage surface.                       |
        | **Services Healthy**         | Alert band 0 / -10           | Monitors reporting up across the fleet.                                                        |
        | **Top Alerting Services**    | Merchant rule                | Monitors generating the most incidents - where to spend reliability effort first.              |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour        | What it tracks                                                                               |
        | ------------------------ | ---------------------- | -------------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Watch only             | Satisfied/tolerating/frustrated ratio derived from monitor response times. 0.94+ is healthy. |
        | **Avg Response Time**    | Alert band 200 / 1000  | Description pending editorial review; the signal is live.                                    |
        | **Error Rate**           | Watch only             | Description pending editorial review; the signal is live.                                    |
        | **Throughput (req/min)** | Alert band 0 / -10     | Throughput (req/min) over time.                                                              |
        | **p95 Latency**          | Alert band 800 / 1500  | Description pending editorial review; the signal is live.                                    |
        | **p99 Latency**          | Alert band 1500 / 3000 | Description pending editorial review; the signal is live.                                    |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                              | Alert behaviour | What it tracks                                                                                        |
        | ----------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
        | **Checkout Monitor Health × Sales** | Merchant rule   | Checkout-monitor up/down overlaid with order volume - when the check fails, sales follow.             |
        | **Revenue at Risk (live)**          | Merchant rule   | Live \$/min loss while any monitor is DOWN and a commerce sibling reports velocity. The COO's number. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                   |
        | ------------------- | --------------- | ---------------------------------------------------------------- |
        | **Top Error Types** | Merchant rule   | Most common failure causes / status codes across failing checks. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (2)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **3 write** operations across monitors, incidents, escalationpolicys, incidentacknowledges, incidentresolves, monitorgroups on Better Uptime. 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=better-uptime)

    #### Ready to build your first Better Uptime 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | monitors             | 2               | 1                |
      | incidents            | 2               | 0                |
      | escalationpolicys    | 1               | 0                |
      | incidentacknowledges | 0               | 1                |
      | incidentresolves     | 0               | 1                |
      | monitorgroups        | 1               | 0                |
      | monitorresponsetimes | 1               | 0                |
      | monitorslas          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Big Cartel on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/bigcartel

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Big Cartel.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Big Cartel.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/bigcartel) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=bigcartel)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Protect revenue (13 signals)">
        | Signal                                      | Alert behaviour  | What it tracks                                                                                               |
        | ------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Ad Spend on Out-of-Stock Products**       | Merchant rule    | Ad Spend on Out-of-Stock Products, broken down by row.                                                       |
        | **Cancellation Rate**                       | Alert band 1 / 3 | Cancelled share of orders. Rising cancellations point to stock or expectation mismatches.                    |
        | **Email Share of Revenue**                  | Merchant rule    | Email Share of Revenue, broken down by row.                                                                  |
        | **High-Value Customers Unengaged on Email** | Merchant rule    | High-Value Customers Unengaged on Email, broken down by row.                                                 |
        | **Low-Stock (Tracked)**                     | Merchant rule    | Tracked products nearing zero - restock prompt before a hero sells out.                                      |
        | **Order Status Mix**                        | Watch only       | Split of pending / paid / shipped / refunded / cancelled. Quick read on where orders sit.                    |
        | **Out-of-Stock (Tracked)**                  | Alert band 0 / 5 | Tracked products at zero stock. Big Cartel exposes per-option stock; OOS-with-demand is recoverable revenue. |
        | **Refund Rate**                             | Alert band 2 / 5 | Refunded share of orders over 30 days. The core product-trust signal for a creator with no support desk.     |
        | **Refund-Rate Spike**                       | Alert band 2 / 5 | Fires when refunds suddenly accelerate - early warning of a product or fulfilment problem.                   |
        | **Refunded Orders**                         | Merchant rule    | Count of refunded orders with a spike alarm against the 30-day baseline.                                     |
        | **Revenue at Risk**                         | Merchant rule    | Estimated revenue exposed by sold-out heroes, stuck orders, and (when siblings connect) cross-channel leaks. |
        | **Slow PDPs Driving Cart Loss**             | Merchant rule    | Slow PDPs Driving Cart Loss, broken down by row.                                                             |
        | **Sold-Out Products**                       | Alert band 0 / 5 | Products marked sold-out. Sold-out bestsellers still on the storefront are quiet revenue leaks.              |
      </Accordion>

      <Accordion title="Run operations (10 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                                                                           |
        | ----------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Time to Ship**          | Merchant rule      | Hours between paid and shipped. Indie makers run slower SLAs; 72h is a sensible nudge threshold.                                                         |
        | **Discount Dependency**       | Alert band 20 / 40 | Share of orders (30d) carrying an order\_adjustments/discount entry with a bracketed code, e.g. \[FREESHIPPING]. Discount codes are a Gold-plan-and-abov |
        | **Fulfillment Rate**          | Alert band 95 / 90 | Share of orders (30d) with shipping\_status = shipped - the real, confirmed Big Cartel field, independent of payment\_status.                            |
        | **Order Processing Backlog**  | Alert band 10 / 50 | Surfaces when unshipped orders pile up beyond the normal pace for the store.                                                                             |
        | **Orders by Country**         | Watch only         | Order count by destination country - matters for makers shipping internationally.                                                                        |
        | **Pending Orders**            | Alert band 10 / 50 | Orders awaiting action. A burst usually means a payment-gateway hiccup or a fulfilment backlog.                                                          |
        | **Plan Product Cap Usage**    | Merchant rule      | Active products vs the plan tier's product cap. Crossing the cap forces an upgrade or delistings.                                                        |
        | **Sold-Out Bestseller Alert** | Alert band 0 / 5   | Flags when a recent bestseller goes sold-out so the maker can restock before momentum dies.                                                              |
        | **Total Customers**           | Watch only         | All-time customer count. Base for the new-vs-returning split.                                                                                            |
        | **Unshipped Paid Orders**     | Alert band 10 / 50 | Paid but not yet shipped beyond 48h - the broken-promise signal for a lean maker shipping by hand.                                                       |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------ |
        | **Average Order Value**          | Alert band 0 / -5  | Revenue / order count. For makers, a drop often means discount over-reliance.                          |
        | **New vs Returning Customers**   | Watch only         | 30-day split of first-time vs repeat buyers. Shows whether growth is acquisition or loyalty led.       |
        | **Order Volume**                 | Alert band 0 / -10 | Count of placed orders with trend. Pairs with revenue to separate volume vs AOV moves.                 |
        | **Products with No Description** | Alert band 5 / 20  | Empty descriptions hurt SEO and conversion. AI-fill is a one-click action target.                      |
        | **Products with No Image**       | Merchant rule      | Listings with zero images convert poorly - free conversion lift to fix.                                |
        | **Repeat Purchase Rate**         | Alert band 25 / 10 | Share of customers with >1 order. For indie brands, repeat rate is the cheapest growth lever.          |
        | **Revenue Trend**                | Watch only         | Daily revenue line over 90 days - spots seasonality and drop campaigns.                                |
        | **Shipping as % of Revenue**     | Alert band 5 / 15  | Shipping charged vs revenue. A high share for a maker often means under-charged international postage. |
        | **Total Revenue**                | Alert band 0 / -5  | Gross revenue across the selected window with vs-previous-period trend. Top of the indie-store pulse.  |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                 |
        | ------------------- | --------------- | ------------------------------------------------------------------------------ |
        | **Active Products** | Watch only      | Count of live listings. Baseline for the plan-cap and catalogue-hygiene cards. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                               |
        | -------------------------- | --------------- | -------------------------------------------------------------------------------------------- |
        | **Top Customers by Spend** | Watch only      | Highest-spend buyers over 90 days - the VIP shortlist for early-access drops and thank-yous. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across account products, accounts, account customers, account orders on Big Cartel. 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=bigcartel)

    #### Ready to build your first Big Cartel 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | account products  | 2               | 0                |
      | accounts          | 1               | 0                |
      | account customers | 1               | 0                |
      | account orders    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# BigCommerce on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/bigcommerce

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to BigCommerce.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to BigCommerce.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/bigcommerce) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=bigcommerce)

<CardGroup>
  <Card title="83">
    performance signals
  </Card>

  <Card title="50">
    automated checks
  </Card>

  <Card title="35">
    prepared fixes
  </Card>

  <Card title="58">
    proven workflows
  </Card>

  <Card title="576">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (83)">
    ### Monitor performance

    83 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (34 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                            |
        | ------------------------------------- | ------------------ | --------------------------------------------------------- |
        | **AOV by Country**                    | Watch only         | AOV by Country.                                           |
        | **Channel-Level AOV**                 | Watch only         | Channel-Level AOV, compared across items.                 |
        | **Channel-Level Order Count**         | Watch only         | Channel-Level Order Count, compared across items.         |
        | **Customer Order Frequency**          | Watch only         | Customer Order Frequency, compared across items.          |
        | **Customer Spend Segments**           | Watch only         | Customer Spend Segments, shown by share.                  |
        | **Customers with Zero Spend**         | Alert band 30 / 60 | Description pending editorial review; the signal is live. |
        | **Email Health**                      | Alert band 95 / 80 | Description pending editorial review; the signal is live. |
        | **File Library by Type**              | Watch only         | File Library by Type.                                     |
        | **Financial Status Breakdown**        | Watch only         | Orders grouped by payment/financial status.               |
        | **Free vs Paid Shipping**             | Watch only         | Free vs Paid Shipping, shown by share.                    |
        | **Fulfillment Rate**                  | Alert band 95 / 90 | Percentage of orders successfully fulfilled.              |
        | **Fulfillment Rate Over Time**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Fulfillment Status**                | Watch only         | Distribution of orders by fulfillment status.             |
        | **Gross Margin**                      | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Guest vs Registered Orders**        | Watch only         | Guest vs Registered Orders, shown by share.               |
        | **Inventory Distribution**            | Watch only         | Inventory Distribution, compared across items.            |
        | **Line Item Fulfillment Status**      | Watch only         | Line Item Fulfillment Status, shown by share.             |
        | **Margin by Brand**                   | Watch only         | Margin by Brand.                                          |
        | **New Customers**                     | Watch only         | New customer signups in the selected period.              |
        | **Orders Over Time**                  | Watch only         | Order volume trend over the selected period.              |
        | **Orders by Country**                 | Watch only         | Orders by Country.                                        |
        | **Orders by State/Region**            | Watch only         | Orders by State/Region.                                   |
        | **Payment Methods**                   | Watch only         | Distribution of orders by payment method.                 |
        | **Products with Zero/Negative Stock** | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Return Status**                     | Watch only         | Return Status, shown by share.                            |
        | **Shipping Methods**                  | Watch only         | Shipping Methods, shown by share.                         |
        | **Stock vs Sales Velocity**           | Watch only         | Stock vs Sales Velocity, compared across items.           |
        | **Store Health Score**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Tax Collected Over Time**           | Watch only         | Description pending editorial review; the signal is live. |
        | **Top 15 Customers**                  | Watch only         | Top 15 Customers, compared across items.                  |
        | **Top Cities by Orders**              | Watch only         | Cities generating the most orders.                        |
        | **Unfulfilled Orders**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Unique Customers**                  | Watch only         | Number of unique customers who placed orders.             |
        | **Unverified Email Customers**        | Merchant rule      | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Grow revenue (28 signals)">
        | Signal                            | Alert behaviour     | What it tracks                                            |
        | --------------------------------- | ------------------- | --------------------------------------------------------- |
        | **AOV (ex-VAT)**                  | Watch only          | Description pending editorial review; the signal is live. |
        | **AOV with/without Discount**     | Watch only          | AOV with/without Discount, compared across items.         |
        | **Average Order Value**           | Merchant rule       | Average amount customers spend per order.                 |
        | **Customer Acquisition Trend**    | Watch only          | New customer acquisition trend over time.                 |
        | **Discount % of Revenue**         | Merchant rule       | Discount value as a percentage of total revenue.          |
        | **Discounts Given Over Time**     | Watch only          | Description pending editorial review; the signal is live. |
        | **Missing SEO Title Count**       | Alert band 10 / 30  | Products missing SEO title metadata.                      |
        | **Repeat Customer Rate**          | Alert band 25 / 10  | Percentage of customers who ordered more than once.       |
        | **Revenue Breakdown**             | Watch only          | Revenue Breakdown.                                        |
        | **Revenue Over Time**             | Watch only          | Revenue trend over the selected period.                   |
        | **Revenue by Brand**              | Watch only          | Revenue by Brand.                                         |
        | **Revenue by Category**           | Watch only          | Revenue by Category.                                      |
        | **Revenue by Channel**            | Watch only          | Revenue by Channel.                                       |
        | **Revenue by Currency**           | Watch only          | Revenue by Currency.                                      |
        | **Revenue by Day of Week**        | Watch only          | Revenue by Day of Week.                                   |
        | **Revenue by Hour**               | Watch only          | Revenue by Hour.                                          |
        | **Revenue by Payment Gateway**    | Watch only          | Revenue by Payment Gateway.                               |
        | **Shipping Cost as % of Revenue** | Alert band 5 / 15   | Description pending editorial review; the signal is live. |
        | **Top Coupons**                   | Watch only          | Top Coupons, compared across items.                       |
        | **Top Products by Revenue**       | Watch only          | Best-selling products ranked by revenue.                  |
        | **Top SKUs by Revenue**           | Watch only          | Top SKUs by Revenue.                                      |
        | **Total Discount Used**           | Watch only          | Total discount amount applied across all orders.          |
        | **Total Orders**                  | Merchant rule       | Number of orders placed in the selected period.           |
        | **Total Revenue**                 | Alert band 10 / -10 | Description pending editorial review; the signal is live. |
        | **Total Revenue (ex-VAT)**        | Watch only          | Description pending editorial review; the signal is live. |
        | **Total Shipping Revenue**        | Watch only          | Total shipping charges collected.                         |
        | **Total Tax Collected**           | Watch only          | Total tax collected across all orders.                    |
        | **Weekend vs Weekday**            | Watch only          | Weekend vs Weekday, shown by share.                       |
      </Accordion>

      <Accordion title="Protect revenue (12 signals)">
        | Signal                         | Alert behaviour  | What it tracks                                            |
        | ------------------------------ | ---------------- | --------------------------------------------------------- |
        | **Cancellation Rate**          | Alert band 1 / 3 | Percentage of orders cancelled before shipping.           |
        | **Cancelled Orders Over Time** | Watch only       | Description pending editorial review; the signal is live. |
        | **Customer Churn Risk**        | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Declined Transaction Rate**  | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Failed Orders Count**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Failed Orders Value**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Most Refunded Products**     | Watch only       | Most Refunded Products, compared across items.            |
        | **Refund Rate**                | Alert band 2 / 5 | Percentage of orders that were refunded.                  |
        | **Refund Value**               | Watch only       | Total monetary value of refunds issued.                   |
        | **Refunded Orders**            | Watch only       | Number of orders with full refunds.                       |
        | **Refunds Over Time**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Top Refunding Customers**    | Watch only       | Top Refunding Customers, compared across items.           |
      </Accordion>

      <Accordion title="Catalogue quality (8 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                            |
        | -------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Collection/Category Count**    | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Product Status**               | Watch only         | Products grouped by active/draft status.                  |
        | **Products Missing Description** | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Products by Type**             | Watch only         | Product catalog breakdown by type.                        |
        | **Products by Vendor**           | Watch only         | Product catalog breakdown by vendor.                      |
        | **SKU Coverage**                 | Alert band 80 / 50 | Description pending editorial review; the signal is live. |
        | **Top Product Tags**             | Watch only         | Top Product Tags, compared across items.                  |
        | **Top SKUs**                     | Watch only         | Top SKUs, compared across items.                          |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                   | Alert behaviour | What it tracks                              |
        | ------------------------ | --------------- | ------------------------------------------- |
        | **Slow-Moving Products** | Watch only      | Products with the lowest sales performance. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (50)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Admin path exposed at /admin">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        A publicly reachable admin login invites automated credential-stuffing; one compromised account means full control of the store.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ASEC-ADMIN`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="HTTPS Not Reachable">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        If the storefront is not cleanly reachable over HTTPS, browsers warn customers away and search engines demote the site; trust and traffic drop together.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SC01`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Sitemap Missing or Thin">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without a healthy sitemap, new and updated pages are discovered late or not at all, so products can launch invisible to search.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB03`
      </Accordion>

      <Accordion title="Storefront blocked by Cloudflare - audit cannot reach the store">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Cloudflare is challenging the auditor, so storefront checks cannot run at all; every dependent finding is suppressed rather than invented.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CF01`
      </Accordion>

      <Accordion title="Theme audit blocked by Cloudflare">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        The theme audit could not reach the storefront because Cloudflare is challenging automated access; theme findings are unavailable rather than guessed until access is allowed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `TH00`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Excessive CSS files loaded">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Prepared fix

        Excess CSS files block rendering while they download; consolidating them speeds first paint on every page.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH03`
      </Accordion>

      <Accordion title="GraphQL Storefront API misconfigured">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Candidate remediation

        The GraphQL storefront API is misconfigured, which breaks headless storefronts and any app relying on it for catalogue or checkout data.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `BCAPI-GQL`
      </Accordion>

      <Accordion title="Homepage SEO Elements Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        The homepage is the most-linked page on the store; missing titles or descriptions there squander the site's strongest ranking signals.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB05`
      </Accordion>

      <Accordion title="Images missing alt text">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Prepared fix

        Images without alt text are invisible to screen readers and to image search; accessibility risk and free traffic left unclaimed at the same time.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH07`
      </Accordion>

      <Accordion title="Limited or Missing Schema Markup">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Schema markup earns rich results (stars, prices, availability) that lift click-through; without it, listings look plainer than competitors on the same results page.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB04`
      </Accordion>

      <Accordion title="Missing Meta Descriptions">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Search engines improvise snippets for pages without meta descriptions; a written one lifts click-through on impressions the page already earns.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE01`
      </Accordion>

      <Accordion title="Missing Page Titles">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Page titles are the strongest single on-page ranking and click-through signal; missing ones waste impressions the store already gets.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE02`
      </Accordion>

      <Accordion title="Missing Product Images">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Prepared fix

        Products without images barely convert; shoppers skip listings they cannot see.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ01`
      </Accordion>

      <Accordion title="Mobile Viewport Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without a mobile viewport tag the store renders desktop-sized on phones; mobile shoppers pinch, zoom and leave.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB12`
      </Accordion>

      <Accordion title="Mobile responsiveness issues">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Prepared fix

        Layouts that break on mobile lose the majority of ecommerce traffic; most stores see well over half their sessions on phones.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH11`
      </Accordion>

      <Accordion title="No Reviews Platform Detected">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Visible reviews are one of the strongest conversion levers in ecommerce; a store with no social proof converts measurably worse on identical traffic.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB10`
      </Accordion>

      <Accordion title="No analytics tracking detected on storefront">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without analytics on the storefront, marketing and UX decisions run blind and no conversion diagnosis is possible downstream.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SC03`
      </Accordion>

      <Accordion title="Order cancellation/refund rate exceeds 5%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Cancellation plus refund above 5 percent of orders means a meaningful slice of won revenue is being handed back; the causes (stock, delivery promises, payment friction) are usually fixable once identified.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `OH01`
      </Accordion>

      <Accordion title="Product Page SEO Issues">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Product pages are where buying-intent searches land; SEO gaps here cost clicks with direct revenue attached.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB06`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Store Logo: No store logo configured">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        A missing store logo makes transactional emails, invoices and search results look unfinished; small trust losses compound at checkout.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SC02`
      </Accordion>

      <Accordion title="Storefront cart API misconfigured">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Candidate remediation

        The storefront cart API is misconfigured, so headless and app integrations that create carts through it will fail at the moment of purchase.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `BCAPI-CART`
      </Accordion>

      <Accordion title="Zero-Price Products">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Prepared fix

        A visible product priced at zero can be added to carts for free and makes the catalogue look broken; each one is either direct revenue leakage or an embarrassment in front of customers.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ02`
      </Accordion>

      <Accordion title="llms.txt Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        AI assistants increasingly answer shopping questions; llms.txt tells them what the store is and which pages matter, the emerging AI-search equivalent of robots.txt.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB02`
      </Accordion>

      <Accordion title="Accessibility issues found">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Accessibility failures exclude customers and carry regulatory risk in a growing list of markets; the common fixes are cheap.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH12`
      </Accordion>

      <Accordion title="Excessive JavaScript files loaded">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Each extra JavaScript file adds a request and parse cost on every page view; script bloat is one of the most common causes of slow storefronts.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH01`
      </Accordion>

      <Accordion title="Font loading not optimized">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Fonts loading without font-display cause invisible text while they download; visitors stare at blank headings on slow connections.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH10`
      </Accordion>

      <Accordion title="High refund rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refund concentration is a direct margin leak and often clusters around specific products, suppliers or delivery windows, which makes it diagnosable and fixable.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `OH02`
      </Accordion>

      <Accordion title="Images missing lazy loading">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Images loading eagerly below the fold compete with the content the shopper actually sees first, inflating LCP and hurting Core Web Vitals rankings.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH02, TH08`
      </Accordion>

      <Accordion title="Long inline styles">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Very long inline styles bloat every page they appear on and defeat caching that external stylesheets would get for free.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH06`
      </Accordion>

      <Accordion title="Missing Product Weight">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Weight-based shipping cannot quote correctly for products without weights, causing checkout errors or mispriced delivery. Irrelevant for flat-rate stores, which is worth recording as a business rule so this never nags.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ04`
      </Accordion>

      <Accordion title="Missing SKUs">
        **Severity** low · **Outcome** Run operations · **Fix status** Prepared fix

        Missing SKUs break inventory reconciliation, courier manifests and marketplace feeds; the problems surface downstream where they are hardest to trace back.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ03`
      </Accordion>

      <Accordion title="Missing Security Headers">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Prepared fix

        Missing security headers leave the storefront easier to attack through clickjacking and script injection, and are flagged by the scanners customers and partners run.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB07`
      </Accordion>

      <Accordion title="Missing Social Meta Tags">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without Open Graph and Twitter tags, shared links render as bare URLs; rich previews carry substantially higher click-through from social and chat.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB09`
      </Accordion>

      <Accordion title="Missing/Short Product Descriptions">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Thin or missing product descriptions hurt conversion on the page and long-tail search rankings off it.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE03`
      </Accordion>

      <Accordion title="No Inventory Tracking">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Without inventory tracking the store cannot warn about stockouts or overselling; every availability signal downstream of this is guesswork.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `IQ01`
      </Accordion>

      <Accordion title="No Remarketing Tags Detected">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without remarketing tags, the roughly 97 percent of visitors who leave cannot be re-engaged, making every paid acquisition channel more expensive.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB11`
      </Accordion>

      <Accordion title="Out of Stock Still Visible">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Shoppers landing on unavailable products bounce, and any paid or organic traffic pointed at them is wasted, unless visibility is deliberate (back-in-stock capture or SEO retention), which is worth recording as a business rule.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `IQ02`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>

      <Accordion title="Render-blocking scripts in <head>">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Scripts loaded in the head without defer block the page from rendering until they finish; moving or deferring them is one of the cheapest speed wins available.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH05`
      </Accordion>

      <Accordion title="Uncategorized Products">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Uncategorised products are unreachable through navigation and category landing pages; they only sell if a customer happens to search for them.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ05`
      </Accordion>

      <Accordion title="console.log statements found in inline scripts">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        console.log calls in production scripts leak implementation detail and add noise; they usually indicate debug code that shipped by accident.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH04`
      </Accordion>

      <Accordion title="robots.txt Missing or Misconfigured">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        A missing or broken robots.txt can accidentally block crawlers from the whole store, or fail to steer them away from junk URLs that waste crawl budget.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB01`
      </Accordion>

      <Accordion title="Tech Stack Detected">
        **Severity** info · **Outcome** Run operations · **Fix status** Prepared fix

        Informational: the technologies detected on the storefront, used to tailor the other checks to the actual stack.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB08, TH09`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **229 read** and **347 write** operations across pages, customers, customer address, redirects, pricelistrecords, products on BigCommerce. 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=bigcommerce)

    #### Proven workflow templates (58)

    <AccordionGroup>
      <Accordion title="Discount Leakage Detector">
        **For** Finance / commercial manager · **Ready to deploy**

        finds stacking, unexpected depth and customer/product misuse.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Price Change Approval Queue">
        **For** Finance / commercial manager · **Ready to deploy**

        supplies cost, margin, competitor/context and customer-group impact for each proposed change.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion Profitability Gate">
        **For** Finance / commercial manager · **Ready to deploy**

        forecasts margin impact and requires commercial approval before activation.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Best-seller Availability Guard">
        **For** E-commerce manager · **Ready to deploy**

        watches hero SKUs and recommends substitutions, replenishment escalation or merchandising changes.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Budget Pacing Guard">
        **For** Performance marketing manager · **Ready to deploy**

        forecasts over/underspend against plan and stages bounded reallocations for approval.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Readiness Gate">
        **For** E-commerce manager · **Ready to deploy**

        checks landing pages, products, inventory, tracking and links before launch; blocks “ready” if critical checks fail.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Checkout Journey Sentinel">
        **For** E-commerce manager · **Ready to deploy**

        scheduled storefront journey checks with screenshot/evidence and urgent escalation.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Creative Fatigue Watch">
        **For** Performance marketing manager · **Ready to deploy**

        detects declining response by creative/audience and opens a replacement brief.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Daily Store Pulse">
        **For** E-commerce manager · **Ready to deploy**

        morning revenue, conversion, AOV, stock and incident briefing with only material changes.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Multi-store Divergence Watch">
        **For** E-commerce manager · **Ready to deploy**

        compares stores/regions and flags unexplained differences in price, availability, content or performance.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New Product Launch Checklist">
        **For** E-commerce manager · **Ready to deploy**

        verifies content, media, inventory, category, SEO and analytics before publish approval.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion Activation QA">
        **For** Performance marketing manager · **Ready to deploy**

        verifies ads, dates, URLs, tracking, inventory and storefront offer before spend begins.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion QA and Rollback Pack">
        **For** E-commerce manager · **Ready to deploy**

        validates price, dates, eligibility and merchandising, then prepares reversible fixes.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Search Query Waste Miner">
        **For** Performance marketing manager · **Ready to deploy**

        clusters irrelevant or expensive queries and drafts negative-keyword actions.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Wasted Spend Watch">
        **For** Performance marketing manager · **Ready to deploy**

        alerts on spend with no meaningful outcomes and recommends pause, budget or targeting review.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Back-in-stock Opportunity Queue">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies high-intent customers and prepares consent-safe notifications.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brand Voice Compliance Review">
        **For** Product content manager · **Ready to deploy**

        flags off-brand, unsupported or inconsistent product claims and proposes corrections.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Preflight Gate">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        validates segment, exclusions, consent, links, stock, offer dates and tracking before send approval.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Completeness Guard">
        **For** Product content manager · **Ready to deploy**

        scores required fields by category and routes the highest-revenue gaps first.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Integrity Night Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        checks SKU identity, variants, price, availability and orphan records across systems.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Deliverability and List Health Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        monitors bounce, complaint, suppression and engagement shifts with safe remediation advice.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Duplicate Copy Resolver">
        **For** Product content manager · **Ready to deploy**

        detects reused descriptions and produces differentiated drafts from verified attributes.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flow Performance Decay Watch">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        detects lifecycle automations whose engagement or revenue has materially deteriorated.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Frequency Pressure Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies over-contacted customers across campaigns and flows.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Fulfilment SLA Breach Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        predicts and escalates orders likely to miss dispatch or delivery promises.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Metadata Optimisation Queue">
        **For** SEO manager · **Ready to deploy**

        generates evidence-based title and description improvements for approval and staged publishing.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New SKU Content Factory">
        **For** Product content manager · **Ready to deploy**

        turns approved source data into complete draft PDPs with a human review queue.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Operations Morning Handover">
        **For** E-commerce operations manager · **Ready to deploy**

        summarises overnight exceptions, actions taken, unresolved risk and accountable owners.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Exception Command Centre">
        **For** E-commerce operations manager · **Ready to deploy**

        detects stuck, failed or unusual orders and routes them with age and value-based urgency.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Issue Triage">
        **For** Customer service manager · **Ready to deploy**

        enriches tickets with order, payment and fulfilment context and assigns the right queue.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Out-of-stock SEO Protector">
        **For** SEO manager · **Ready to deploy**

        detects valuable unavailable pages and prepares safe redirect, substitute or retention actions.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PDP Enrichment Queue">
        **For** Product content manager · **Ready to deploy**

        finds thin product pages, generates on-brand copy, and batches changes for approval.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Peak Freeze Controller">
        **For** E-commerce operations manager · **Ready to deploy**

        pauses writes during trading freezes while continuing all monitoring and alerts.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Proactive Delay List">
        **For** Customer service manager · **Ready to deploy**

        prepares, but does not send, customer communications for affected orders.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Product Claim Evidence Check">
        **For** Product content manager · **Ready to deploy**

        identifies unsubstantiated claims and requires evidence or removal before publish.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Returns Anomaly Monitor">
        **For** E-commerce operations manager · **Ready to deploy**

        surfaces spikes by SKU, supplier, reason or cohort and assigns investigation.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Schema Coverage and Validity Sweep">
        **For** SEO manager · **Ready to deploy**

        validates structured data across page types and stages theme/template fixes.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Seasonal Content Refresh">
        **For** Product content manager · **Ready to deploy**

        identifies stale seasonal language and prepares date-safe updates with expiry/rollback.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Segment Drift Monitor">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        flags unexpected audience growth/shrinkage or overlap before it damages sends.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Supplier Copy Normaliser">
        **For** Product content manager · **Ready to deploy**

        converts inconsistent feeds into house style while preserving factual specifications.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Regression Monitor">
        **For** SEO manager · **Ready to deploy**

        watches broken links, redirect chains, canonicals, robots, schema and indexability after changes.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Variant Consistency Sweep">
        **For** Product content manager · **Ready to deploy**

        reconciles names, options, specifications and copy across product families.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Accessibility Regression Sweep">
        **For** Web / digital product manager · **Ready to deploy**

        monitors high-value templates for newly introduced violations.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Broken Experience Prioritiser">
        **For** Web / digital product manager · **Ready to deploy**

        combines errors, traffic and revenue impact into a ranked product backlog.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Conversion Journey Sentinel">
        **For** Web / digital product manager · **Ready to deploy**

        repeatedly tests priority journeys and captures actionable failure evidence.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Core Web Performance Guard">
        **For** Web / digital product manager · **Ready to deploy**

        detects page/template regressions and routes them to the owning team.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Post-release Regression Watch">
        **For** Web / digital product manager · **Ready to deploy**

        compares critical KPIs and technical signals before/after deploy.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Readiness Gate">
        **For** Web / digital product manager · **Ready to deploy**

        checks staging journeys, accessibility, analytics, SEO, performance and rollback readiness.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Recommendation Pack">
        **For** Web / digital product manager · **Ready to deploy**

        assembles evidence and prepares a reversible action when guardrails fail.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Script Risk Watch">
        **For** Web / digital product manager · **Ready to deploy**

        flags new, slow, failing or unapproved scripts and tags.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: Shopify, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | pages                      | 4               | 8                |
      | customers                  | 3               | 8                |
      | customer address           | 3               | 7                |
      | redirects                  | 3               | 6                |
      | pricelistrecords           | 3               | 5                |
      | products                   | 2               | 6                |
      | carts                      | 2               | 5                |
      | channelcurrencyassignments | 2               | 5                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    62 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Google BigQuery on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/bigquery

Monitor Google BigQuery health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Google BigQuery health, cost and reliability signals, and catch incidents and runaway spend early.

[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=bigquery)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="14">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                                           | Alert behaviour    | What it tracks                                                                                                                                              |
        | ------------------------------------------------ | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Datasets**                              | Watch only         | Count from datasets.list.                                                                                                                                   |
        | **BigQuery Health Score**                        | Merchant rule      | Description pending editorial review; the signal is live.                                                                                                   |
        | **Bytes Scanned (24h)**                          | Merchant rule      | SUM(total\_bytes\_processed) from INFORMATION\_SCHEMA.JOBS. BigQuery-defining - on-demand billing is per byte scanned (\~\$6.25/TiB). This IS the spend sig |
        | **Bytes-Scanned Cost +50% Week-over-Week**       | Merchant rule      | BigQuery-distinctive - un-pruned / runaway query scanning a giant un-partitioned table is the #1 cost surprise.                                             |
        | **Concurrent Query Jobs**                        | Merchant rule      | RUNNING jobs from jobs.list - interactive concurrency quota defaults \~100/project. Approaching cap = queries queue or fail.                                |
        | **Estimated On-Demand Query Cost (24h)**         | Merchant rule      | total\_bytes\_billed × on-demand rate (\$6.25/TiB default; first 1 TiB/month free). Capacity-priced projects show slot cost instead.                        |
        | **Largest Table (GB)**                           | Watch only         | From INFORMATION\_SCHEMA.TABLE\_STORAGE active\_logical\_bytes. Top tables drive storage cost.                                                              |
        | **Last Table Snapshot Age (hours)**              | Alert band 24 / 72 | BigQuery time-travel retains 7 days by default; table snapshots / scheduled exports are the explicit backup. Reflects newest snapshot age.                  |
        | **Long-Term Storage %**                          | Watch only         | long\_term\_bytes ÷ (active + long\_term). Higher = more tables untouched 90d, billed at \~half rate - informational cost lever.                            |
        | **Pending Jobs (waiting for slots)**             | Merchant rule      | Jobs in PENDING state from jobs.list - sustained pending = reservation under-provisioned or concurrency cap hit.                                            |
        | **Query Jobs per Hour (live)**                   | Watch only         | Count of QUERY jobs from INFORMATION\_SCHEMA.JOBS in the last hour. Baseline-relative, no absolute band.                                                    |
        | **Reservation Slot Saturation (>90% sustained)** | Alert band 70 / 90 | Alerts for Reservation Slot Saturation (>90% sustained).                                                                                                    |
        | **Slot Utilisation %**                           | Alert band 70 / 90 | slots/allocated ÷ reservation capacity (Cloud Monitoring). Sustained 100% on a reservation = queueing; on-demand has no slot cap to hit. BigQuery-dist      |
        | **Slot-ms Consumed (24h)**                       | Watch only         | SUM(total\_slot\_ms) from INFORMATION\_SCHEMA.JOBS - the capacity-pricing cost anchor (vs bytes for on-demand).                                             |
        | **Streaming Buffer Lag (s)**                     | Alert band 1 / 10  | Streaming-insert buffer flush lag - high lag means freshly streamed rows aren't queryable yet (ingest pipeline backpressure).                               |
        | **Top 10 Most Expensive Queries**                | Watch only         | Ordered by total\_bytes\_processed from INFORMATION\_SCHEMA.JOBS. The optimisation hit-list - add partitioning / clustering / pruning here.                 |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                     | Alert behaviour      | What it tracks                                                                                                                                       |
        | -------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Query Cache Hit Rate %** | Alert band 95 / 80   | Share of jobs where cache\_hit = true in INFORMATION\_SCHEMA.JOBS - cached results are free, so a rising cache rate cuts cost. BigQuery-distinctive. |
        | **Query Latency p50 (ms)** | Watch only           | Median (end\_time - start\_time) from INFORMATION\_SCHEMA.JOBS.                                                                                      |
        | **Query Latency p95 (ms)** | Alert band 50 / 200  | BigQuery analytics queries measured in seconds - threshold reflects warehouse use case, not OLTP.                                                    |
        | **Query Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                            |
        | **Slow-Query Rate %**      | Alert band 1 / 5     | Share of query jobs with duration > 5s in INFORMATION\_SCHEMA.JOBS.                                                                                  |
        | **Top 10 Slowest Queries** | Watch only           | Top 10 Slowest Queries, broken down by row.                                                                                                          |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                       | Alert behaviour | What it tracks                                                                                                                         |
        | -------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
        | **BigQuery Event Ingest vs Ecom Orders**     | Merchant rule   | Fivetran / Dataflow ingest stall while orders flow = analytics blind spot; dashboards silently go stale.                               |
        | **BigQuery Query Spike vs Ecom Order Rate**  | Merchant rule   | Description pending editorial review; the signal is live.                                                                              |
        | **Bytes-Scanned Cost vs Ecom Order Volume**  | Merchant rule   | BigQuery-distinctive XC - on-demand spend should track ecom volume (more data to analyse = more bytes). Divergence = wasted scan cost. |
        | **Expensive Queries During Checkout Window** | Merchant rule   | Expensive Queries During Checkout Window, broken down by row.                                                                          |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                                                          |
        | ------------------------------------ | ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
        | **Job Error Rate %**                 | Alert band 0.1 / 1 | Share of jobs with error\_result set in INFORMATION\_SCHEMA.JOBS (quota exceeded, permission, syntax, resources).       |
        | **Job Error Rate Spike (>1% in 1h)** | Alert band 0.1 / 1 | Alerts for Job Error Rate Spike (>1% in 1h).                                                                            |
        | **Quota-Exceeded Errors (24h)**      | Merchant rule      | Jobs failing with quotaExceeded reason - concurrency / bytes-billed / API quota hit. BigQuery-distinctive failure mode. |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                                                                          |
        | ------------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Bytes Scanned by User (7d)** | Watch only         | GROUP BY user\_email (hashed) from INFORMATION\_SCHEMA.JOBS. Surfaces the top spenders for cost attribution.                            |
        | **Total Storage (TB)**         | Alert band 70 / 90 | Sum of active + long-term logical bytes across datasets (tables.get / TABLE\_STORAGE). Storage is cost-anchored - growth = bill growth. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (14)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Bytes Scanned +50% Week-over-Week">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Bytes scanned jumping 50 percent week over week is the leading indicator of a runaway query or a new unpartitioned workload; costs follow within the billing cycle.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BQ-COST-001`
      </Accordion>

      <Accordion title="Job Error Rate Spike >1% in 1h">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Job errors spiking past 1 percent breaks the pipelines that dashboards and models silently depend on.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BQ-PERF-004`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Reservation Slot Utilisation >90% Sustained with Jobs Pending">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Sustained reservation-slot saturation with jobs pending means workloads are queuing every day; capacity or scheduling needs a decision.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BQ-CAP-003`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Quota-Exceeded Errors Detected (>0 in 24h)">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Quota-exceeded errors mean jobs are being refused outright; whatever depends on them is already stale.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BQ-PERF-005`
      </Accordion>

      <Accordion title="Single Query Scanning >1 TiB (un-partitioned / un-pruned)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A single query scanning over a tebibyte almost always means a missing partition filter; one WHERE clause can cut its cost by orders of magnitude.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BQ-COST-002`
      </Accordion>

      <Accordion title="Query Cache Hit Rate Below 50% (cost lever unused)">
        **Severity** low · **Outcome** Run operations · **Fix status** Report only

        Cache hit rate below half means the warehouse is recomputing answers it already produced; free savings are being left off.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BQ-COST-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **1 write** operations across projectdatasettables, projectjobs, projectdatasets, projectquerys, projecttimeserys on Google BigQuery. 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=bigquery)

    #### Ready to build your first Google BigQuery 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | projectdatasettables | 2               | 0                |
      | projectjobs          | 2               | 0                |
      | projectdatasets      | 1               | 0                |
      | projectquerys        | 0               | 1                |
      | projecttimeserys     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Bitbucket on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/bitbucket

Monitor Bitbucket health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Bitbucket health, cost and reliability signals, and catch incidents and runaway spend early.

[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=bitbucket)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                          |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Repos (30d)**              | Watch only         | Count of repos with updated\_on within the last 30d.                                                                                                    |
        | **Avg Build Duration (30d)**        | Watch only         | Average build\_seconds\_used / 60 across completed pipelines (state.name=COMPLETED) with created\_on within the last 30d, across the top 10 repos.      |
        | **Avg Comments / PR (30d)**         | Watch only         | Average comment\_count across PRs (state=OPEN or MERGED) updated within the last 30d; comment\_count is a native field on the pull request object.      |
        | **Avg Commits / Active Repo (30d)** | Watch only         | 30d commit count / active-repos-30d; concentration of delivery across the fleet.                                                                        |
        | **Commits by Day (7d)**             | Watch only         | Commits grouped by calendar day over the last 7d (commit date field), summed across the top 10 repos.                                                   |
        | **Languages by Repo Count**         | Watch only         | Repos grouped by their language field (nulls skipped), top 10 by count.                                                                                 |
        | **Median Open PR Age**              | Alert band 3 / 14  | Median of (now - created\_on) in days across all open PRs (state=OPEN); drives vc\_pr\_age\_days (lower is better).                                     |
        | **Merged PRs (30d)**                | Watch only         | Count of PRs with state=MERGED and updated\_on within the last 30d (state=MERGED\&sort=-updated\_on) across the top 10 repos.                           |
        | **Most Active Repo (30d)**          | Watch only         | The repo with the most commits in the last 30d; value = commit count, detail = repo full\_name.                                                         |
        | **Open Pull Requests**              | Watch only         | Count of open PRs from /repositories///pullrequests?state=OPEN across the top 10 repos.                                                                 |
        | **PR Age Alert**                    | Alert band 3 / 14  | Median open-PR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d).                                                             |
        | **Pipeline Runs (30d)**             | Watch only         | Count of pipeline runs with created\_on within the last 30d across the top 10 repos, from /repositories///pipelines/.                                   |
        | **Pipelines Pass Rate (30d)**       | Alert band 95 / 80 | Pipelines with state.result.name=SUCCESSFUL / all completed pipelines (state.name=COMPLETED) with created\_on within 30d, x100, across the top 10 repos |
        | **Private Repos**                   | Watch only         | Count of repos with is\_private=true / total repos, x100.                                                                                               |
        | **Repos with Wiki Enabled**         | Watch only         | Count of repos with has\_wiki=true / total repos, x100 (native boolean field on the repository object).                                                 |
        | **Repositories**                    | Watch only         | Count of repos returned by /repositories/ (pagelen=100).                                                                                                |
        | **Stale PRs (>14d)**                | Watch only         | Count of open PRs (state=OPEN) whose age (now - created\_on) exceeds 14 days.                                                                           |
        | **Total Repo Size**                 | Watch only         | Sum of the size field (bytes) across all repos from /repositories/, converted to MB (divide by 1,048,576).                                              |
      </Accordion>

      <Accordion title="Grow revenue (4 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                    |
        | ------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Commits (30d)**         | Alert band 0 / -50 | Count of commits from /repositories///commits (commit date within 30d) summed across the top 10 most-recently-updated repos; cha                  |
        | **Deploy Cadence (30d)**  | Alert band 0 / -50 | 30d total delivery events (commits + merged PRs); value = 30d total, change\_pct vs the prior 30d drives vc\_deploy\_cadence.                     |
        | **Deploy Stall Alert**    | Alert band 0 / -50 | Delivery-event (commits + merged PRs) change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band.                            |
        | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x Pipelines pass rate (30d) + 0.3 x PR-age score (100 at \<=3d open-PR median age, 0 at >=14d) + 0.3 x deploy-cadence score |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                                                            |
        | -------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------- |
        | **Declined PRs (30d)**     | Watch only      | Count of PRs with state=DECLINED and updated\_on within the last 30d across the top 10 repos.                             |
        | **Failed Pipelines (30d)** | Watch only      | Count of pipelines with state.result.name in (FAILED, ERROR) and created\_on within the last 30d across the top 10 repos. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CI pass rate below 80%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CI-001`
      </Accordion>

      <Accordion title="Delivery cadence dropped more than 50% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CADENCE-001`
      </Accordion>

      <Accordion title="Median open pull-request age above 14 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-PR-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across repositorys, repositorycommits, repositorypipelines, repositorypullrequests, users on Bitbucket. 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=bitbucket)

    #### Ready to build your first Bitbucket 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | repositorys            | 1               | 0                |
      | repositorycommits      | 1               | 0                |
      | repositorypipelines    | 1               | 0                |
      | repositorypullrequests | 1               | 0                |
      | users                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Bonanza on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/bonanza

Monitor Bonanza listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Bonanza listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=bonanza)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by State**                                   | Watch only         | AOV by State.                                                                                                                                          |
        | **Bonanza Booth Health Score**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Booth Rating**                                   | Alert band 95 / 85 | Description pending editorial review; the signal is live.                                                                                              |
        | **Buyer Messages Unread**                          | Watch only         | Buyer Messages Unread as exposed by the Bonanza integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Days Since Last Payout**                         | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Importer Sync / BRA / Rating Threshold Crossed** | Alert band 95 / 85 | Alerts for Importer Sync / BRA / Rating Threshold Crossed.                                                                                             |
        | **Importer Sync Health**                           | Merchant rule      | % of eBay/Amazon/Etsy/Shopify items successfully mirrored to Bonanza via Importer in last 24h. Below 95% = sync gap.                                   |
        | **Late Shipments**                                 | Merchant rule      | Alerts for Late Shipments.                                                                                                                             |
        | **Marketplace Fees Paid**                          | Watch only         | Marketplace Fees Paid as exposed by the Bonanza integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Oldest Pending Payout (days)**                   | Watch only         | Oldest Pending Payout (days) as exposed by the Bonanza integration. The metric is computed from the latest available data and refreshed on the standar |
        | **On-Time Shipping Rate**                          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Orders / Day**                                   | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by State**                                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                                | Watch only         | Pending Payouts as exposed by the Bonanza integration. The metric is computed from the latest available data and refreshed on the standard data refres |
        | **Pending Shipment**                               | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                               |
        | ------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
        | **Average BRA Score (Buy-it-Right Asking)** | Merchant rule      | Bonanza's internal listing-quality metric , drives search rank. Below 70 = systematic listing-quality work needed.           |
        | **Average Order Value**                     | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                    |
        | **Bonanza Fee % of Revenue**                | Alert band 12 / 18 | Bonanza Final Offer Value (FOV) = 3.5% on Bonanza-only sales. Higher % means advertising program (Bonanza Promotion) opt-in. |
        | **Net Revenue (after Bonanza fees)**        | Alert band 0 / -5  | Net of Bonanza's 3.5% Final Offer Value (FOV) fee , lowest among big-three US marketplaces.                                  |
        | **Orders**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                    |
        | **Revenue Over Time**                       | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                    |
        | **Top Listings by Revenue**                 | Watch only         | Top Listings by Revenue.                                                                                                     |
        | **Total Revenue**                           | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                    |
      </Accordion>

      <Accordion title="Catalogue quality (7 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Bonanza Removed Listings (24h)**   | Alert band 5 / 50  | Alerts for Bonanza Removed Listings (24h).                                                                                                             |
        | **Imported vs Manual Listings**      | Watch only         | Split of Bonanza catalog by import source. Helps debug Importer issues per source platform.                                                            |
        | **Listings Expiring Soon**           | Watch only         | Listings Expiring Soon as exposed by the Bonanza integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Required-Attribute Completeness**  | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                              |
        | **Stale Listings (>180d no update)** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Listings**                   | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                         | Alert behaviour   | What it tracks                                                                                                  |
        | ---------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------- |
        | **Active Bonanza Listings for OOS SKUs on BC** | Alert band 0 / 5  | Description pending editorial review; the signal is live.                                                       |
        | **Cancellation Rate**                          | Merchant rule     | Description pending editorial review; the signal is live.                                                       |
        | **Listings Drifting from BC**                  | Alert band 5 / 50 | Listings Drifting from BC, broken down by row.                                                                  |
        | **Listings Failing Feedonomics Validation**    | Alert band 2 / 5  | Bonanza also distributes to Google Shopping Actions feed , Feedonomics validation matters at the upstream feed. |
        | **Price Drift vs eBay / Etsy via Importer**    | Merchant rule     | Bonanza Importer auto-syncs price from source , drift = sync lag or manual override that needs reconciling.     |
        | **Revenue at Risk**                            | Merchant rule     | Description pending editorial review; the signal is live.                                                       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **3 write** operations across apirequeststandardrequestfetchaccountdatas, apirequeststandardrequestfetchitems, apirequeststandardrequestfetchorders on Bonanza. 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=bonanza)

    #### Ready to build your first Bonanza 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                   | Read operations | Write operations |
      | ------------------------------------------ | --------------- | ---------------- |
      | apirequeststandardrequestfetchaccountdatas | 0               | 1                |
      | apirequeststandardrequestfetchitems        | 0               | 1                |
      | apirequeststandardrequestfetchorders       | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Braintree on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/braintree

Monitor Braintree payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Braintree payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=braintree)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (10 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                         |
        | ----------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                  | Alert band 15 / 30   | Customers who hit the 3DS challenge and bail. High = checkout friction.                                                |
        | **Chargeback Rate**                       | Alert band 0.5 / 0.9 | Chargebacks as a share of transactions. Above 0.9% approaches the card-scheme cap.                                     |
        | **Decline Rate**                          | Alert band 5 / 8     | Share of attempts declined / rejected. Soft declines are recoverable.                                                  |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When Braintree declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss. |
        | **Dispute Rate**                          | Alert band 0.5 / 1   | All disputes (chargeback + pre-arbitration + retrieval) as a share of transactions.                                    |
        | **Oldest Pending Payout (days)**          | Alert band 2 / 5     | Age of the oldest unsettled batch - cash-flow risk if it climbs.                                                       |
        | **Recoverable Revenue (decline-driven)**  | Merchant rule        | Total value leaked through soft declines that retry / dunning could recover next month.                                |
        | **Refund Rate**                           | Alert band 3 / 8     | Refunded value as a share of processed value.                                                                          |
        | **Refund Volume**                         | Merchant rule        | Total refunded amount in the window.                                                                                   |
        | **Top Decline Reasons**                   | Merchant rule        | Processor response reasons (insufficient\_funds, do\_not\_honor, expired\_card) - each has a different fix.            |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                        |
        | ------------------------------ | ------------------ | --------------------------------------------------------------------- |
        | **Average Transaction**        | Alert band 0 / -15 | Mean transaction amount - basket-size signal.                         |
        | **Avg Settlement Time (days)** | Alert band 2 / 5   | Mean days from submission to funds settled.                           |
        | **Pending Payouts**            | Merchant rule      | Value submitted for settlement but not yet funded.                    |
        | **Success Rate**               | Alert band 95 / 90 | Share of attempts that authorise / settle. Below 90% needs attention. |
        | **Top Payment Methods**        | Merchant rule      | Mix of card / PayPal / Venmo / wallet instruments.                    |
        | **Total Transactions**         | Watch only         | Count of transactions processed in the window.                        |
        | **Total Volume**               | Alert band 0 / -15 | Gross processed transaction value over the window.                    |
        | **Volume Trend**               | Alert band 0 / -15 | Processed volume over time to spot regressions and seasonality.       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **6 write** operations across graphqls, merchantdisputeadvancedsearchs, merchantdisputeevidences, merchantsettlementbatchsummarys, merchanttransactions, merchanttransactionadvancedsearchs on Braintree. 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=braintree)

    #### Ready to build your first Braintree 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                           | Read operations | Write operations |
      | ---------------------------------- | --------------- | ---------------- |
      | graphqls                           | 0               | 1                |
      | merchantdisputeadvancedsearchs     | 0               | 1                |
      | merchantdisputeevidences           | 0               | 1                |
      | merchantsettlementbatchsummarys    | 0               | 1                |
      | merchanttransactions               | 1               | 0                |
      | merchanttransactionadvancedsearchs | 0               | 1                |
      | merchanttransactionrefunds         | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Brevo (Sendinblue) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/brevo

Monitor email revenue and deliverability for Brevo (Sendinblue), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Brevo (Sendinblue), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=brevo)

<CardGroup>
  <Card title="22">
    performance signals
  </Card>

  <Card title="13">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (22)">
    ### Monitor performance

    22 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (9 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                             |
        | -------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------- |
        | **Abandoned-Cart Recovery Value**      | Watch only           | GBP/\$ per 30D recovered by the abandoned-cart trigger campaign. Goes to zero if no cart campaign is live. |
        | **Blacklisted Contact Share**          | Alert band 2 / 10    | Share of contacts blacklisted (unsub / bounce / complaint). A high share drags deliverability.             |
        | **Bounce Rate**                        | Alert band 2 / 5     | Soft + hard bounces as a share of sends. Rising bounces hurt sender reputation. Audit BR04 fires here.     |
        | **Delivery Rate**                      | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention. BR01 fires.                      |
        | **Email Health KPIs**                  | Merchant rule        | Delivered, bounced and unsubscribed at a glance, your deliverability vitals.                               |
        | **Email Share of Total Store Revenue** | Merchant rule        | Healthy DTC ranges 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk.           |
        | **Engagement Funnel**                  | Merchant rule        | Requested -> Delivered -> Opened -> Clicked. Drop-offs expose deliverability vs content weakness.          |
        | **Spam Complaint Rate**                | Alert band 0.1 / 0.3 | Above 0.1% Gmail starts marking the sender domain. BR03 fires; investigate immediately.                    |
        | **Unsubscribe Rate**                   | Alert band 0.5 / 2   | Unsubscribes per delivered email. A spike signals list fatigue or off-target content.                      |
      </Accordion>

      <Accordion title="Run operations (7 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                 |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------ |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts across all lists.                     |
        | **Email Open Rate**           | Alert band 20 / 10 | Apple Mail Privacy inflates this - pair with click-to-open for a truer signal. |
        | **List Count**                | Merchant rule      | Number of contact lists on the account.                                        |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                      |
        | **Lists Overview**            | Merchant rule      | Every contact list with its subscriber count.                                  |
        | **Segments Overview**         | Merchant rule      | Saved segments. Below 3 signals an under-segmented account (audit BR06).       |
        | **Top Lists by Name**         | Merchant rule      | Largest contact lists by subscriber count.                                     |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                        |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule      | Email campaigns grouped by status (sent, draft, queued, suspended).                   |
        | **Click-to-Open Rate**        | Alert band 10 / 3  | Truer engagement signal than open rate - proxy filtering doesn't pre-click.           |
        | **Conversion Rate**           | Merchant rule      | Orders as a share of emails sent. Requires the Brevo ecommerce tracker.               |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Unique clicks as a share of delivered. The clearest engagement signal.                |
        | **Top Campaigns by Revenue**  | Merchant rule      | Highest-grossing campaigns. Requires the Brevo ecommerce tracker for revenue figures. |
        | **Total Sends**               | Merchant rule      | Total emails requested across marketing + transactional sends in the window.          |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (13)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Spam complaint rate above ISP threshold">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BR03`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Delivery rate below 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        When more than 1 in 20 emails fails to arrive at all, every campaign, promotion and transactional message built on that list underperforms, and the gap compounds as the list grows.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BR01`
      </Accordion>

      <Accordion title="Email bounce rate above 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BR04`
      </Accordion>

      <Accordion title="High blacklisted contact share">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        A high share of blacklisted contacts poisons deliverability for the whole list and usually points at an import or acquisition-source problem worth fixing at the root.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `BR07`
      </Accordion>

      <Accordion title="Unsubscribe rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A rising unsubscribe rate shrinks the reachable audience and usually signals frequency or relevance problems; every lost subscriber removes future campaign and flow revenue.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BR05`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited lists / segmentation">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BR06`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **1 write** operations across accounts, contacts, contactfolders, contactlists, contactlistcontactadds, contactsegments on Brevo (Sendinblue). 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=brevo)

    #### Ready to build your first Brevo (Sendinblue) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                       | Read operations | Write operations |
      | ------------------------------ | --------------- | ---------------- |
      | accounts                       | 1               | 0                |
      | contacts                       | 1               | 0                |
      | contactfolders                 | 1               | 0                |
      | contactlists                   | 1               | 0                |
      | contactlistcontactadds         | 0               | 1                |
      | contactsegments                | 1               | 0                |
      | emailcampaigns                 | 1               | 0                |
      | smtpstatisticaggregatedreports | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Bring (Posten Norge) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/bring

Monitor Bring (Posten Norge) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Bring (Posten Norge) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=bring)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                                            | Alert behaviour  | What it tracks                                                                                                                          |
        | ------------------------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**                                | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Avg Shipping Cost**                             | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Claim Value (open)**                            | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Cost Per Shipment Trend**                       | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Cost by Zone**                                  | Watch only       | Cost by Zone.                                                                                                                           |
        | **Days to Token Expiry**                          | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Exception Rate**                                | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                               |
        | **High-Cost Shipment Outliers**                   | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                        |
        | **Home vs Mypack vs Business Door**               | Watch only       | Home vs Mypack vs Business Door, shown by share.                                                                                        |
        | **Klimanøytrale (Carbon-Neutral) Shipment Share** | Merchant rule    | Bring certifies sellers shipping ≥60% via Klimanøytrale products. Drops here = loses sustainability-badge + customer-side trust signal. |
        | **Label Generation Success**                      | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Label Print Failures Spike**                    | Alert band 0 / 5 | Alerts for Label Print Failures Spike.                                                                                                  |
        | **Mypack Pickup Expiring or SLA Breach**          | Merchant rule    | Mypack pickups expire if uncollected , surface ahead of expiry for proactive customer contact.                                          |
        | **Mypack Pickup Expiry Rate**                     | Merchant rule    | % of Mypack pickup-point shipments expiring before customer collects. Spike = pickup-point notification flow broken.                    |
        | **OTD by Route**                                  | Watch only       | OTD by Route.                                                                                                                           |
        | **Open Claims**                                   | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Returned to Sender**                            | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Route Volume Concentration**                    | Watch only       | Route Volume Concentration, compared across items.                                                                                      |
        | **Shipments**                                     | Merchant rule    | Description pending editorial review; the signal is live.                                                                               |
        | **Shipments Over Time**                           | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Shipments by Destination**                      | Watch only       | Description pending editorial review; the signal is live.                                                                               |
        | **Shipments by Service**                          | Watch only       | Shipments by Service.                                                                                                                   |
      </Accordion>

      <Accordion title="Customer experience (7 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                                                                                      |
        | ------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**                | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **First-Attempt Delivery Rate**       | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **Late Shipments**                    | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **NO Export Customs Clearance Rate**  | Merchant rule      | % of NO→EU shipments clearing customs within 3 days. Bring auto-generates tolldokument (export customs document); failures stall parcels at border. |
        | **Nordic Export OTD (NO → SE/DK/FI)** | Alert band 95 / 90 | OTD on cross-border Nordic exports. Lower threshold than domestic , customs adds 1-2 days.                                                          |
        | **Norway-Domestic OTD**               | Alert band 95 / 90 | OTD on NO-to-NO shipments. Bring's home turf; misses here = Bring-side operational issue, not cross-border friction.                                |
        | **On-Time Delivery Rate**             | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                           |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                       | Alert behaviour   | What it tracks                                                                                                             |
        | -------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
        | **Bring Cost vs PostNord by Nordic Country** | Merchant rule     | Bring vs PostNord head-to-head per destination country. NO-domestic Bring usually wins; cross-Nordic PostNord often beats. |
        | **Failed Deliveries**                        | Watch only        | Description pending editorial review; the signal is live.                                                                  |
        | **Orders with Dispatch SLA Missed**          | Merchant rule     | Description pending editorial review; the signal is live.                                                                  |
        | **Return Rate by Bring Product Code**        | Merchant rule     | Description pending editorial review; the signal is live.                                                                  |
        | **Shipments with Tracking-Event Gap**        | Alert band 0 / 10 | Shipments with Tracking-Event Gap, broken down by row.                                                                     |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                   | Alert behaviour | What it tracks                                   |
        | ---------------------------------------- | --------------- | ------------------------------------------------ |
        | **Bring Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for Bring Tracking API Unavailable / 5xx. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **2 write** operations across bookings, bookingbookingreturns, trackingtrackingjsons on Bring (Posten Norge). 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=bring)

    #### Ready to build your first Bring (Posten Norge) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource              | Read operations | Write operations |
      | --------------------- | --------------- | ---------------- |
      | bookings              | 0               | 1                |
      | bookingbookingreturns | 0               | 1                |
      | trackingtrackingjsons | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Campaign Monitor on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/campaign-monitor

Monitor email revenue and deliverability for Campaign Monitor, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Campaign Monitor, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=campaign-monitor)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (12 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                                                                                                          |
        | ----------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule     | Campaigns grouped by status (sent, draft, scheduled).                                                                                   |
        | **Checkout-to-Order Rate**    | Merchant rule     | Share of started checkouts that became paid orders.                                                                                     |
        | **Click-to-Open Rate**        | Alert band 10 / 3 | Clicks / UniqueOpened - engagement quality independent of open-rate inflation.                                                          |
        | **Conversion Rate**           | Merchant rule     | Orders as a share of emails sent. Ties send volume to revenue.                                                                          |
        | **Email Click Rate**          | Alert band 3 / 1  | Share of delivered emails that earned a click. The clearest engagement signal.                                                          |
        | **List Count**                | Merchant rule     | Number of audiences on the account.                                                                                                     |
        | **Lists Overview**            | Merchant rule     | Every audience with its member count.                                                                                                   |
        | **Revenue per Recipient**     | Merchant rule     | Revenue divided by emails sent. What each address is worth per send.                                                                    |
        | **Revenue per Send**          | Merchant rule     | Email-attributed revenue divided by sends. Requires a commerce sibling for the revenue numerator.                                       |
        | **Top Lists by Name**         | Merchant rule     | Largest audiences by member count.                                                                                                      |
        | **Total Revenue**             | Merchant rule     | Campaign Monitor exposes no native order revenue - this is email-attributed store revenue, only true when a commerce sibling is joined. |
        | **Total Sends**               | Merchant rule     | Sum of Recipients across campaigns sent in the window.                                                                                  |
      </Accordion>

      <Accordion title="Run operations (9 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                    |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule      | Sum of TotalActiveSubscribers across all lists for the client.                                    |
        | **Email Open Rate**           | Alert band 25 / 15 | UniqueOpened / Recipients. Apple Mail Privacy Protection inflates this - pair with click-to-open. |
        | **Flow Count Summary**        | Merchant rule      | How many automations exist on the account.                                                        |
        | **Flow Status Breakdown**     | Merchant rule      | Automations split by status (live, draft, paused).                                                |
        | **Flow Trigger Types**        | Merchant rule      | Automations grouped by what triggers them.                                                        |
        | **Flows List**                | Merchant rule      | Every automation and its current status.                                                          |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                                         |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to a send. Requires a commerce sibling joined on customer\_email.               |
        | **Segments Overview**         | Merchant rule      | Saved segments and their sizes.                                                                   |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                  | Alert behaviour      | What it tracks                                                                                     |
        | ----------------------- | -------------------- | -------------------------------------------------------------------------------------------------- |
        | **Bounce Rate**         | Alert band 2 / 5     | Bounced / Recipients. Above 5% trips ISP throttling. Audit CAM02 fires here.                       |
        | **Delivery Rate**       | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                          |
        | **Email Health KPIs**   | Merchant rule        | Delivered, bounced and unsubscribed at a glance, your deliverability vitals.                       |
        | **Engagement Funnel**   | Merchant rule        | Recipients -> Delivered -> Opened -> Clicked. Drop-offs expose deliverability vs content weakness. |
        | **Refund Rate**         | Merchant rule        | Share of attributed orders later refunded.                                                         |
        | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | SpamComplaints / Recipients. Above 0.1% Gmail starts marking the sender domain. CAM03 fires.       |
        | **Unsubscribe Rate**    | Alert band 0.3 / 1   | Unsubscribes per send. A spike signals list fatigue or off-target content.                         |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="High Bounce Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CAM02`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CAM03`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="High Unsubscribe Rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        A rising unsubscribe rate shrinks the reachable audience and usually signals frequency or relevance problems; every lost subscriber removes future campaign and flow revenue.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CAM04`
      </Accordion>

      <Accordion title="Limited Segmentation">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CAM05`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Low Open Rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        Consistently low opens mean subject lines, send times or list quality are wasting sends, and engagement-based inbox placement then makes future sends perform even worse.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CAM01`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **2 write** operations across campaign summaryjsons, clientcampaignjsons, clientjsons, clientlistjsons, clientsegmentjsons, journeys on Campaign Monitor. 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=campaign-monitor)

    #### Ready to build your first Campaign Monitor 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.

    <Accordion title="Browse the operations you can build with">
      | Resource              | Read operations | Write operations |
      | --------------------- | --------------- | ---------------- |
      | campaign summaryjsons | 1               | 0                |
      | clientcampaignjsons   | 1               | 0                |
      | clientjsons           | 1               | 0                |
      | clientlistjsons       | 1               | 0                |
      | clientsegmentjsons    | 1               | 0                |
      | journeys              | 1               | 0                |
      | journeystatusjsons    | 0               | 1                |
      | listactivejsons       | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Apache Cassandra on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/cassandra

Monitor Apache Cassandra health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Apache Cassandra health, cost and reliability signals, and catch incidents and runaway spend early.

[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=cassandra)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                                                                          |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Cassandra Health Score**                     | Merchant rule      | Composite of node-up ratio, latency percentiles, pending compactions and dropped mutations.                                                             |
        | **Disk Usage %**                               | Alert band 70 / 90 | Load / data-directory usage from nodetool status Load column vs disk capacity.                                                                          |
        | **Hinted Handoffs Pending**                    | Merchant rule      | Cassandra-distinctive - hints stored for unreachable replicas. Growing = a replica is down or slow; data not yet converged.                             |
        | **JVM Heap Used %**                            | Merchant rule      | Cassandra runs on the JVM - heap >75% drives GC pauses; sustained high heap precedes node instability.                                                  |
        | **Key Cache Hit Rate %**                       | Alert band 95 / 80 | KeyCache hit\_ratio from the system\_views.caches CQL virtual table (4.0+) / org.apache.cassandra.metrics:type=Cache,scope=KeyCache,name=HitRate MBean. |
        | **Native-Transport Connections**               | Watch only         | Connected client count from system\_views.clients.                                                                                                      |
        | **Native-Transport Pool Saturation %**         | Alert band 70 / 90 | Native-Transport-Requests active / max threads from system\_views.thread\_pools.                                                                        |
        | **Node Down (DN) or Gossip Flapping**          | Merchant rule      | Cassandra-distinctive - a DN node reduces replica availability; sustained = consistency-level failures imminent. Page on-call.                          |
        | **Nodes Up / Normal (UN)**                     | Merchant rule      | Count of endpoints in UN state from nodetool status / system.peers. Cassandra-defining - DN node = reduced replica availability.                        |
        | **Operations per Second (read + write, live)** | Watch only         | ClientRequest Read + Write count delta from system\_views / org.apache.cassandra.metrics MBeans.                                                        |
        | **Pending Compactions**                        | Merchant rule      | Cassandra-distinctive - from nodetool compactionstats / PendingTasks MBean. Backlog = SSTables stacking up, read amplification rising.                  |
        | **SSTables per Read (avg)**                    | Merchant rule      | SSTablesPerReadHistogram - high count = compaction falling behind, every read touches more files.                                                       |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                 |
        | ------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------- |
        | **Cassandra NTR Saturation vs Ecom Burst**        | Alert band 70 / 90 | Cassandra NTR Saturation vs Ecom Burst, broken down by row.                                                    |
        | **Cassandra Product Table Count vs Ecom Catalog** | Merchant rule      | Cassandra-distinctive XC - many merchants store catalog / inventory in Cassandra; drift = product-sync broken. |
        | **Cassandra Write Spike vs Ecom Order Rate**      | Merchant rule      | Description pending editorial review; the signal is live.                                                      |
        | **Dropped Mutations (24h)**                       | Merchant rule      | DroppedMessages (MUTATION). Coordinator shed a write under load - silent data loss risk if hints also dropped. |
        | **Last Repair Age (hours)**                       | Merchant rule      | Repair recency vs gc\_grace\_seconds (default 10d). Stale repair = zombie data / resurrected deletes risk.     |
        | **Slow Reads During Checkout Window (5m)**        | Merchant rule      | Slow Reads During Checkout Window (5m), broken down by row.                                                    |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                                                                         |
        | -------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Coordinator Read Latency p50 (ms)**  | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Coordinator Read Latency p95 (ms)**  | Alert band 50 / 200  | ClientRequest Read latency p95 from system\_views.coordinator\_read\_latency / Read MBean. Storefront-facing.                                          |
        | **Coordinator Read Latency p99 (ms)**  | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                              |
        | **Coordinator Write Latency p99 (ms)** | Alert band 100 / 500 | ClientRequest Write latency p99. Writes are normally cheap in Cassandra - high p99 = commitlog / GC pressure.                                          |
        | **Slow-Query Rate %**                  | Alert band 1 / 5     | Share of ClientRequest Read+Write samples over 200ms, from the EstimatedHistogram buckets behind org.apache.cassandra.metrics:type=ClientRequest,scope |
        | **Tombstones Scanned per Read**        | Merchant rule        | Cassandra-distinctive - TombstoneScannedHistogram. High tombstone reads cause latency + can trip the 100k failure threshold.                           |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                               |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Read Timeouts (24h)**                  | Merchant rule      | ClientRequest Read Timeouts - coordinator didn't get enough replica responses inside read\_request\_timeout. |
        | **Request Error Rate %**                 | Alert band 0.1 / 1 | ClientRequest Failures + Timeouts + Unavailables as % of total reads + writes.                               |
        | **Request Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Request Error Rate Spike (>1% in 5m).                                                             |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                         |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------ |
        | **Dropped Mutations or Hinted-Handoff Growth** | Merchant rule      | Alerts for Dropped Mutations or Hinted-Handoff Growth.                                                 |
        | **Last Snapshot Age (hours)**                  | Alert band 24 / 72 | Most recent nodetool snapshot (or Medusa / Astra backup). Gated: requires snapshot tooling visibility. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **10 read** and **0 write** operations across nodetool compactionstats, nodetool netstats, nodetool status, nodetool tablestats, nodetool tpstats, select \* from systemlocals on Apache Cassandra. 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=cassandra)

    #### Ready to build your first Apache Cassandra 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                         | Read operations | Write operations |
      | -------------------------------- | --------------- | ---------------- |
      | nodetool compactionstats         | 1               | 0                |
      | nodetool netstats                | 1               | 0                |
      | nodetool status                  | 1               | 0                |
      | nodetool tablestats              | 1               | 0                |
      | nodetool tpstats                 | 1               | 0                |
      | select \* from systemlocals      | 1               | 0                |
      | select \* from systempeers       | 1               | 0                |
      | select \* from systemviewclients | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Chartbeat on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/chartbeat

Monitor traffic, conversion and tracking integrity from Chartbeat, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Chartbeat, and catch instrumentation breaks before decisions are made on bad data.

[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=chartbeat)

<CardGroup>
  <Card title="13">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (13)">
    ### Monitor performance

    13 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (11 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                                                                                |
        | --------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Session Duration**    | Alert band 0 / -10 | Average engaged time per session - Chartbeat's core editorial-quality signal.                                                                 |
        | **Goal Completions**        | Alert band 0 / -10 | Count of completed goals (signups, purchases, key events) in the window.                                                                      |
        | **New Users**               | Alert band 0 / -10 | First-time visitors in the window - the top of the audience funnel.                                                                           |
        | **Pageviews per Session**   | Alert band 3 / 1.5 | Depth of browsing per session - how far readers travel through the site.                                                                      |
        | **Real-Time Users**         | Alert band 0 / -15 | Concurrents on the site right now - Chartbeat's signature live pulse; a collapse to zero means tracking is broken.                            |
        | **Returning Users**         | Alert band 0 / -10 | Loyal audience returning in the window - the retention counterpart to New Users.                                                              |
        | **Session Conversion Rate** | Alert band 2 / 1   | Sessions that complete a goal - cross-checked against the ecom platform's own order-conversion rate to surface engagement-without-conversion. |
        | **Sessions**                | Alert band 0 / -10 | Sessions on the property over the trailing window - the audience-volume baseline every other card is read against.                            |
        | **Top Pages**               | Alert band 0 / -10 | Highest-traffic pages by pageviews / concurrents - where the audience is right now.                                                           |
        | **Top Traffic Sources**     | Alert band 0 / -10 | Referrers driving the audience - search, social, direct and link channels ranked by volume.                                                   |
        | **Users**                   | Alert band 0 / -10 | Total unique users in the window - New plus Returning combined.                                                                               |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                   |
        | ------------------------- | ------------------ | ---------------------------------------------------------------- |
        | **Bounce Rate**           | Alert band 40 / 60 | Share of single-page, low-engagement sessions - lower is better. |
        | **Cart Abandonment Rate** | Alert band 60 / 75 | Share of carts started but not completed - lower is better.      |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across historicalconversionseries, historicaltrafficseries, livequickstats, livereferrers, livetoppages on Chartbeat. 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=chartbeat)

    #### Ready to build your first Chartbeat 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | historicalconversionseries | 1               | 0                |
      | historicaltrafficseries    | 1               | 0                |
      | livequickstats             | 1               | 0                |
      | livereferrers              | 1               | 0                |
      | livetoppages               | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Microsoft Clarity on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/clarity

Monitor traffic, conversion and tracking integrity from Microsoft Clarity, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Microsoft Clarity, and catch instrumentation breaks before decisions are made on bad data.

[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=clarity)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="11">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="1">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (8 signals)">
        | Signal                                | Alert behaviour | What it tracks                                                                                   |
        | ------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------ |
        | **Avg Page Engagement Time**          | Watch only      | Description pending editorial review; the signal is live.                                        |
        | **Avg Session Duration**              | Watch only      | Description pending editorial review; the signal is live.                                        |
        | **Bot Traffic %**                     | Merchant rule   | Clarity flags suspected bot sessions - high share inflates every other metric.                   |
        | **Checkout-Path Frustration Signals** | Merchant rule   | Dead clicks / rage clicks on checkout-path pages - direct conversion blockers.                   |
        | **JavaScript Errors Detected**        | Merchant rule   | Clarity surfaces JS errors observed during sessions - checkout-page errors are revenue blockers. |
        | **Pages per Session**                 | Watch only      | Description pending editorial review; the signal is live.                                        |
        | **Sessions by Country**               | Watch only      | Sessions by Country.                                                                             |
        | **Sessions by Device**                | Watch only      | Sessions by Device.                                                                              |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                            | Alert behaviour | What it tracks                                                                                           |
        | --------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- |
        | **Dead Click Hotspots (by page)** | Watch only      | Dead Click Hotspots (by page), broken down by row.                                                       |
        | **Dead Click Rate %**             | Merchant rule   | Clarity-distinctive - % of sessions with a dead click. Rising = something looks clickable but isn't.     |
        | **Excessive Scrolling Rate %**    | Merchant rule   | Sessions with frantic scrolling - visitor can't find what they came for.                                 |
        | **Quick-Back Rate %**             | Merchant rule   | Clarity-distinctive - visitors who land then immediately go back. High = landing-page / intent mismatch. |
        | **Rage Click Rate %**             | Merchant rule   | Description pending editorial review; the signal is live.                                                |
        | **Sessions Captured**             | Merchant rule   | Description pending editorial review; the signal is live.                                                |
        | **Top Pages by Sessions**         | Watch only      | Top Pages by Sessions.                                                                                   |
        | **Worst Scroll-Depth Pages**      | Watch only      | Pages where visitors scroll least - content / layout reorder candidates.                                 |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                         | Alert behaviour | What it tracks                                                  |
        | ---------------------------------------------- | --------------- | --------------------------------------------------------------- |
        | **Clarity Session Outcome vs Ecom Conversion** | Merchant rule   | Description pending editorial review; the signal is live.       |
        | **Frustration Signals vs Cart Abandonment**    | Merchant rule   | Description pending editorial review; the signal is live.       |
        | **Landing Page Performance vs Quick-Back**     | Merchant rule   | Landing Page Performance vs Quick-Back, broken down by row.     |
        | **Session Source vs Ecom Revenue Attribution** | Merchant rule   | Session Source vs Ecom Revenue Attribution, broken down by row. |
      </Accordion>

      <Accordion title="Customer experience (3 signals)">
        | Signal                              | Alert behaviour | What it tracks                                            |
        | ----------------------------------- | --------------- | --------------------------------------------------------- |
        | **Checkout-Path Frustration Spike** | Merchant rule   | Alerts for Checkout-Path Frustration Spike.               |
        | **Clarity UX Health Score**         | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Frustration Signal Spike**        | Merchant rule   | Alerts for Frustration Signal Spike.                      |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                 | Alert behaviour | What it tracks                                                                               |
        | ---------------------- | --------------- | -------------------------------------------------------------------------------------------- |
        | **Avg Scroll Depth %** | Merchant rule   | Clarity-distinctive - average page scroll reach. Low = key content below the fold is missed. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                     | Alert behaviour | What it tracks                                     |
        | ------------------------------------------ | --------------- | -------------------------------------------------- |
        | **Tracking Gap (session count collapsed)** | Merchant rule   | Alerts for Tracking Gap (session count collapsed). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (11)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="API Credentials Invalid">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        With invalid credentials the tool has stopped collecting entirely; every metric that depends on it is silently stale.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLR05`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Checkout-Path Frustration">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Frustration signals on the checkout path are as close to watching lost sales happen as analytics gets; each cluster is a prioritised fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLR04`
      </Accordion>

      <Accordion title="Session Capture Collapsed">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        A sharp drop in captured events or sessions usually means a tracking break after a site change, not a real traffic collapse; decisions made on the partial data will be wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLR01`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>

      <Accordion title="Dead-Click Concentration">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Dead clicks concentrated on specific elements mean shoppers believe something is clickable and it is not; each cluster is a small usability fix with real conversion upside.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLR02`
      </Accordion>

      <Accordion title="Quick-Back Spike">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Visitors bouncing straight back after arriving signals a broken or misleading landing experience for that traffic source.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLR03`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **0 write** operations across projectliveinsights on Microsoft Clarity. 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=clarity)

    #### Ready to build your first Microsoft Clarity 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | projectliveinsights | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ClickHouse on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/clickhouse

Monitor ClickHouse health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor ClickHouse health, cost and reliability signals, and catch incidents and runaway spend early.

[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=clickhouse)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                  | Alert behaviour    | What it tracks                                                                                  |
        | --------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------- |
        | **Active Replicas**                     | Watch only         | Description pending editorial review; the signal is live.                                       |
        | **ClickHouse Health Score**             | Merchant rule      | Description pending editorial review; the signal is live.                                       |
        | **Connection Pool Saturation %**        | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                       |
        | **Connection Pool at >90% Saturation**  | Alert band 70 / 90 | Alerts for Connection Pool at >90% Saturation.                                                  |
        | **Connections In Use**                  | Watch only         | Description pending editorial review; the signal is live.                                       |
        | **Database Disk Usage %**               | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                       |
        | **Inserts per Second (live)**           | Watch only         | InsertedRows event rate from system.events delta. ClickHouse-distinctive.                       |
        | **Instance Uptime**                     | Watch only         | Description pending editorial review; the signal is live.                                       |
        | **Last Successful Backup (hours ago)**  | Alert band 24 / 72 | Last BACKUP TO S3 / Disk run from system.backups. ClickHouse Cloud: managed snapshots.          |
        | **Merges In Progress**                  | Watch only         | Merge metric from system.metrics. Sustained high = ingest outpacing merge throughput.           |
        | **Partition Count (Top 10 Tables)**     | Merchant rule      | From system.parts GROUP BY table COUNT DISTINCT partition\_id.                                  |
        | **Queries per Second (live)**           | Watch only         | Description pending editorial review; the signal is live.                                       |
        | **Replication Lag (absolute\_delay)**   | Alert band 1 / 10  | From system.replicas.absolute\_delay.                                                           |
        | **Replication Queue Size (Top Tables)** | Merchant rule      | From system.replicas.queue\_size. ClickHouse-distinctive , pending replication tasks per table. |
        | **UncompressedCache Hit Rate %**        | Alert band 95 / 80 | UncompressedCacheHits / (UncompressedCacheHits + UncompressedCacheMisses) from system.events.   |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                            | Alert behaviour     | What it tracks                                                                                                        |
        | ------------------------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **Active Parts (Top 10 Tables)**                  | Merchant rule       | From system.parts WHERE active. >1000 parts on a single table = merge backlog risk; can trigger Too Many Parts error. |
        | **ClickHouse Event Ingest vs Ecom Orders**        | Merchant rule       | ClickHouse-distinctive XC , event ingest typically tracks order/click rate; divergence = pipeline broken.             |
        | **ClickHouse Pool Saturation vs Traffic Burst**   | Alert band 70 / 90  | ClickHouse Pool Saturation vs Traffic Burst, broken down by row.                                                      |
        | **ClickHouse QPS Spike vs Ecom Order Rate**       | Merchant rule       | Description pending editorial review; the signal is live.                                                             |
        | **Failed Queries (24h)**                          | Alert band 20 / 100 | query\_log WHERE type='ExceptionWhileProcessing'.                                                                     |
        | **Slow Analytics Queries During Checkout Window** | Merchant rule       | Slow Analytics Queries During Checkout Window, broken down by row.                                                    |
      </Accordion>

      <Accordion title="Control risk and change (6 signals)">
        | Signal                                                     | Alert behaviour    | What it tracks                                                                          |
        | ---------------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------- |
        | **MEMORY\_LIMIT\_EXCEEDED (24h)**                          | Merchant rule      | Query killed by max\_memory\_usage. Spike = a single heavy query swamping the instance. |
        | **Memory Usage %**                                         | Merchant rule      | MemoryTracking metric from system.metrics / max\_server\_memory.                        |
        | **Query Error Rate %**                                     | Alert band 0.1 / 1 | Description pending editorial review; the signal is live.                               |
        | **Query Error Rate Spike (>1% in 5m)**                     | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                          |
        | **Too Many Parts Error or Parts Count >1000 on Any Table** | Merchant rule      | ClickHouse-distinctive , parts cap hit halts ingest on that table.                      |
        | **Too Many Parts Errors (24h)**                            | Merchant rule      | ClickHouse-distinctive , Code 252 errors from parts cap hit. Any >0 = ingest broken.    |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                     | Alert behaviour      | What it tracks                                             |
        | -------------------------- | -------------------- | ---------------------------------------------------------- |
        | **Query Latency p50 (ms)** | Watch only           | Description pending editorial review; the signal is live.  |
        | **Query Latency p95 (ms)** | Alert band 50 / 200  | From system.query\_log percentile aggregation.             |
        | **Query Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live.  |
        | **Slow-Query Rate %**      | Alert band 1 / 5     | query\_log entries with duration\_ms > 1000 as % of total. |
        | **Top 10 Slowest Queries** | Watch only           | Top 10 Slowest Queries, broken down by row.                |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **0 write** operations across systembackups, systembuildoptions, systemevents, systemmetrics, systemparts, systemquerylogs on ClickHouse. 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=clickhouse)

    #### Ready to build your first ClickHouse 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | systembackups      | 1               | 0                |
      | systembuildoptions | 1               | 0                |
      | systemevents       | 1               | 0                |
      | systemmetrics      | 1               | 0                |
      | systemparts        | 1               | 0                |
      | systemquerylogs    | 1               | 0                |
      | systemreplicas     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ClickUp on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/clickup

Monitor ClickUp performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor ClickUp performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=clickup)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                             |
        | ----------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Avg time from in-progress to closed - how long work takes once it's started.                               |
        | **Avg Lead Time (days)**            | Merchant rule      | Avg time from task creation to closed - total turnaround including queue time.                             |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Avg days from finding creation to ClickUp task close, last 90 days.                                        |
        | **Backlog by Priority**             | Merchant rule      | Open-task distribution across ClickUp priority levels (urgent / high / normal / low).                      |
        | **Backlog by Status**               | Watch only         | Open-task distribution across ClickUp custom statuses.                                                     |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Tasks in a blocked / impeded status - the operational queue's stuck list.                                  |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle time split by priority - urgent work should not sit.                                                 |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings actually got closed via ClickUp. Green >=75%, amber 50-74%, red \<50%.        |
        | **In Progress**                     | Watch only         | Tasks in an in-flight custom status - the active work queue.                                               |
        | **Oldest Open (days)**              | Merchant rule      | Age of the oldest open task - backlog rot signal when it climbs past 90 days.                              |
        | **Open Tickets**                    | Merchant rule      | Open tasks across all VortexIQ Lists (status.type != closed, not archived) - top-of-funnel backlog volume. |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | People with >10 open tasks - capacity bottleneck candidates.                                               |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Tasks added to the active sprint after start - scope-creep signal.                                         |
        | **Sprint Progress**                 | Alert band 80 / 50 | Completed vs total sprint scope for the active sprint folder.                                              |
        | **Sprint Velocity (avg)**           | Merchant rule      | Avg completed points/tasks over the last 5 sprints.                                                        |
        | **Throughput Trend**                | Watch only         | Rolling 30-day closed-task trend.                                                                          |
        | **Tickets Resolved (7d)**           | Merchant rule      | Tasks closed in the last 7 days vs the prior 7 - drain rate.                                               |
        | **Tickets by Assignee**             | Merchant rule      | Open-task count per ClickUp assignee - capacity at a glance.                                               |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Open tasks with no assignee - work nobody owns.                                                            |
        | **VortexIQ Findings In Progress**   | Watch only         | Findings actively being worked - in a custom or done (review-pending) status.                              |
        | **VortexIQ Findings Open**          | Merchant rule      | Tasks we filed from audit findings that aren't closed yet - the live backlog of things VortexIQ surfaced.  |
        | **VortexIQ Findings Resolved**      | Watch only         | Findings closed in the last 90 days - the proof the loop is working.                                       |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                           |
        | ----------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no date\_updated change for two weeks - the ones losing money silently. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **3 write** operations across listtasks, folderlists, lists, listmembers, spacefolders, spacelists on ClickUp. 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=clickup)

    #### Ready to build your first ClickUp 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.

    <Accordion title="Browse the operations you can build with">
      | Resource     | Read operations | Write operations |
      | ------------ | --------------- | ---------------- |
      | listtasks    | 1               | 1                |
      | folderlists  | 1               | 0                |
      | lists        | 1               | 0                |
      | listmembers  | 1               | 0                |
      | spacefolders | 1               | 0                |
      | spacelists   | 1               | 0                |
      | tasks        | 0               | 1                |
      | taskcomments | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Cloudflare on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/cloudflare

Monitor Cloudflare health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Cloudflare health, cost and reliability signals, and catch incidents and runaway spend early.

[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=cloudflare)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="39">
    proven workflows
  </Card>

  <Card title="3,331">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (6 signals)">
        | Signal                          | Alert behaviour        | What it tracks                                                                                                         |
        | ------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------- |
        | **CLS (Mobile)**                | Alert band 0.1 / 0.25  | Cumulative Layout Shift p75 - visual stability while the page loads.                                                   |
        | **INP (Mobile)**                | Alert band 200 / 500   | Interaction to Next Paint p75 - responsiveness to taps and clicks on mobile.                                           |
        | **Performance Score (Desktop)** | Alert band 90 / 50     | Lighthouse desktop performance score (0-100).                                                                          |
        | **Performance Score (Mobile)**  | Alert band 90 / 50     | Lighthouse mobile performance score (0-100). The headline lab number a deploy regression shows up in first.            |
        | **Speed Index**                 | Alert band 3400 / 5800 | How quickly page content is visually populated in the lab run.                                                         |
        | **TTFB (Mobile)**               | Alert band 800 / 1800  | Time to First Byte p75 - origin + edge response time. The metric Cloudflare's cache + edge config most directly moves. |
      </Accordion>

      <Accordion title="Grow revenue (4 signals)">
        | Signal                     | Alert behaviour        | What it tracks                                                                                                                                   |
        | -------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Accessibility Score**    | Alert band 90 / 70     | Lighthouse accessibility audit score - a11y gaps that also affect SEO and legal exposure.                                                        |
        | **CWV Pass Rate (Mobile)** | Alert band 75 / 50     | Share of mobile visits passing all three Core Web Vitals. Below 75% loses the 'good' rank signal; below 50% is a conversion + SEO emergency.     |
        | **LCP (Mobile)**           | Alert band 2500 / 4000 | Largest Contentful Paint p75 for mobile field users on the Cloudflare-fronted origin. Google's primary loading-speed gate for rank + conversion. |
        | **SEO Score**              | Alert band 90 / 70     | Lighthouse on-page SEO score - crawlability, meta, structured-data basics.                                                                       |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                        | Alert behaviour              | What it tracks                                                                                                                 |
        | ----------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Render-Blocking Resources** | Alert band 200 / 500         | Estimated load-time savings from eliminating render-blocking CSS/JS. Often the highest-leverage edge / Cloudflare-Workers fix. |
        | **Total Blocking Time**       | Alert band 200 / 600         | Total time the main thread was blocked - the lab proxy for INP / interactivity.                                                |
        | **Total Page Weight**         | Alert band 1572864 / 3145728 | Total transferred bytes for the page. Creeping weight behind the CDN drives both TTFB and mobile-data cost.                    |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                   | Alert behaviour    | What it tracks                                                            |
        | ------------------------ | ------------------ | ------------------------------------------------------------------------- |
        | **Best Practices Score** | Alert band 90 / 70 | Lighthouse best-practices score - HTTPS, console errors, deprecated APIs. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Cloudflare yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1,638 read** and **1,693 write** operations across account images, account emailsendingsuppressions, account vectorizeindexes, zonefirewallrules, account devicepolicys, account emailsecuritysettingsdomains on Cloudflare. 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=cloudflare)

    #### Proven workflow templates (39)

    <AccordionGroup>
      <Accordion title="API Contract Drift Watch">
        **For** Developer · **Ready to deploy**

        detects connector or internal schema changes before production failure.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Actionable Incident Triage">
        **For** Developer · **Ready to deploy**

        correlates errors, deploys and affected journeys and opens a pre-filled engineering ticket.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Auth Failure Triage">
        **For** Developer · **Ready to deploy**

        distinguishes expiry, scope, rate limit and upstream outage causes.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Dependency Risk Queue">
        **For** Developer · **Ready to deploy**

        surfaces relevant security/end-of-life updates with compatibility and test guidance.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Failed Job Replay Assistant">
        **For** Developer · **Ready to deploy**

        diagnoses and safely retries idempotent work while escalating unsafe cases.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flaky Test Investigator">
        **For** Developer · **Ready to deploy**

        clusters intermittent failures and ranks likely ownership and root cause.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PR Risk Summary">
        **For** Developer · **Ready to deploy**

        reports affected services, missing tests, operational risk and required approvers.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Performance Regression Bisect">
        **For** Developer · **Ready to deploy**

        correlates release changes with latency and frontend performance shifts.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Safe Fix Branch">
        **For** Developer · **Ready to deploy**

        creates a scoped branch/PR with evidence, tests and rollback notes for an approved issue.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Ticket Builder">
        **For** Developer · **Ready to deploy**

        translates crawl/indexation evidence into reproducible developer work.

        Tested alongside: GitHub, Jira Cloud, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Auto-apply Guardrail Approval">
        **For** Security manager · **Ready to deploy**

        requires security sign-off when an automation gains broader write authority.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Blocked Work Escalator">
        **For** Engineering manager · **Ready to deploy**

        detects ageing PRs/tickets and identifies the missing decision or dependency.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Change Failure Rate Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks failed deploys and highlights teams/services with worsening patterns.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Cloud Exposure Watch">
        **For** Security manager · **Ready to deploy**

        detects risky DNS, firewall, storage or edge configuration changes.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Access Review">
        **For** Security manager · **Ready to deploy**

        inventories credentials, scopes, owners, use and age; routes unnecessary access for revocation.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Engineering Dependency Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks vulnerable, unsupported or risky platform dependencies.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Executive Technology Pack">
        **For** Engineering manager · **Ready to deploy**

        translates technical risk and delivery evidence into commercial impact.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Containment Pack">
        **For** Security manager · **Ready to deploy**

        prepares reversible, scoped containment actions for human approval.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Learning Loop">
        **For** Engineering manager · **Ready to deploy**

        creates the timeline, contributing factors, actions and follow-up ownership.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Metadata Optimisation Queue">
        **For** SEO manager · **Ready to deploy**

        generates evidence-based title and description improvements for approval and staged publishing.

        Tested alongside: BigCommerce, Shopify, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Monthly Security Evidence Pack">
        **For** Security manager · **Ready to deploy**

        retains what changed, who approved it, results and rollback availability.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Out-of-stock SEO Protector">
        **For** SEO manager · **Ready to deploy**

        detects valuable unavailable pages and prepares safe redirect, substitute or retention actions.

        Tested alongside: BigCommerce, Shopify, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Privilege Drift Monitor">
        **For** Security manager · **Ready to deploy**

        alerts when repository, cloud or connector permissions exceed policy.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Risk Gate">
        **For** Engineering manager · **Ready to deploy**

        scores change size, test evidence, service health and rollback readiness before approval.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Audit">
        **For** Engineering manager · **Ready to deploy**

        verifies that rollbacks completed and downstream state returned to expected values.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Schema Coverage and Validity Sweep">
        **For** SEO manager · **Ready to deploy**

        validates structured data across page types and stages theme/template fixes.

        Tested alongside: BigCommerce, Shopify, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Suspicious Change Correlator">
        **For** Security manager · **Ready to deploy**

        links identity, code, infrastructure and automation audit events.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Regression Monitor">
        **For** SEO manager · **Ready to deploy**

        watches broken links, redirect chains, canonicals, robots, schema and indexability after changes.

        Tested alongside: BigCommerce, Shopify, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Integration Risk Review">
        **For** Security manager · **Ready to deploy**

        assesses new connectors before activation and on material permission change.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Vulnerability Remediation Queue">
        **For** Security manager · **Ready to deploy**

        ranks findings by exploitability, exposure and affected revenue paths.

        Tested alongside: GitHub, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Weekly Delivery and Reliability Brief">
        **For** Engineering manager · **Ready to deploy**

        combines throughput, failed changes, incidents, rollbacks and ageing work.

        Tested alongside: GitHub, Jira Cloud, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Accessibility Regression Sweep">
        **For** Web / digital product manager · **Ready to deploy**

        monitors high-value templates for newly introduced violations.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Broken Experience Prioritiser">
        **For** Web / digital product manager · **Ready to deploy**

        combines errors, traffic and revenue impact into a ranked product backlog.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Conversion Journey Sentinel">
        **For** Web / digital product manager · **Ready to deploy**

        repeatedly tests priority journeys and captures actionable failure evidence.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Core Web Performance Guard">
        **For** Web / digital product manager · **Ready to deploy**

        detects page/template regressions and routes them to the owning team.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Post-release Regression Watch">
        **For** Web / digital product manager · **Ready to deploy**

        compares critical KPIs and technical signals before/after deploy.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Readiness Gate">
        **For** Web / digital product manager · **Ready to deploy**

        checks staging journeys, accessibility, analytics, SEO, performance and rollback readiness.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Recommendation Pack">
        **For** Web / digital product manager · **Ready to deploy**

        assembles evidence and prepares a reversible action when guardrails fail.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Script Risk Watch">
        **For** Web / digital product manager · **Ready to deploy**

        flags new, slow, failing or unapproved scripts and tags.

        Tested alongside: StagingPro, GitHub, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                             | Read operations | Write operations |
      | ------------------------------------ | --------------- | ---------------- |
      | account images                       | 4               | 7                |
      | account emailsendingsuppressions     | 4               | 5                |
      | account vectorizeindexes             | 4               | 5                |
      | zonefirewallrules                    | 2               | 7                |
      | account devicepolicys                | 3               | 4                |
      | account emailsecuritysettingsdomains | 2               | 5                |
      | account gatewayrules                 | 2               | 5                |
      | account loadbalancerpools            | 2               | 5                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    11 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# CloudHub Insights on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/cloudhub-insights

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to CloudHub Insights.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to CloudHub Insights.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/cloudhub-insights) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=cloudhub-insights)

<CardGroup>
  <Card title="39">
    performance signals
  </Card>

  <Card title="18">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (39)">
    ### Monitor performance

    39 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                                                             |
        | ---------------------------------- | ------------------ | ------------------------------------------------------------------------------------------ |
        | **Avg Buybox Share (24h)**         | Alert band 85 / 60 | AVG(RepriceDailyReport.AvgBuyBoxShareLast24Hours).                                         |
        | **Backlog > 48h**                  | Alert band 10 / 50 | Orders in a non-dispatched stage entered >48h ago (OrderStageChangeLog.CreatedOn).         |
        | **Backordered Units**              | Merchant rule      | SUM(MasterQuantity.BackOrderded).                                                          |
        | **Business (B2B) Order Share**     | Watch only         | Invoice.IsBusinessOrder = 1 share of orders.                                               |
        | **Buybox Win Rate**                | Alert band 85 / 60 | RepriceDailyReport WHERE BuyboxOwner = 1 ÷ total repriced ASINs (24h).                     |
        | **Despatch Rate**                  | Alert band 95 / 90 | Orders in a dispatched OrderStage ÷ total orders (OrderDetails ⋈ OrderStage.IsDispatched). |
        | **Inventory Cost Value**           | Watch only         | SUM(MasterQuantity.AvailableQuantity × Inventory.CostPrice).                               |
        | **Order Despatch Backlog**         | Alert band 10 / 50 | Alerts for Order Despatch Backlog.                                                         |
        | **Orders Awaiting Despatch**       | Alert band 10 / 50 | OrderDetails Active=1 in a non-dispatched stage.                                           |
        | **Prime Order Share**              | Watch only         | Invoice.IsPrime = 1 share of orders.                                                       |
        | **Repricer Coverage**              | Alert band 80 / 50 | SKUs in RepricingInventory ÷ active Amazon SKUs.                                           |
        | **SKUs Awaiting PO**               | Watch only         | Report\_Products WHERE AwaitingPO > 0.                                                     |
        | **SKUs Without Cost Price**        | Merchant rule      | Inventory WHERE CostPrice IS NULL OR CostPrice = 0 (blocks margin reporting).              |
        | **SKUs Without Dimensions/Weight** | Merchant rule      | Inventory WHERE Weight/Height/Length/Width IS NULL (breaks courier rating).                |
        | **SKUs Without Images**            | Merchant rule      | Inventory SKUs with no row in ImageMaster/ImageLinks.                                      |
        | **Stale Inventory (no 30d sales)** | Merchant rule      | masterinventory.Last30Day = 0 with stock on hand.                                          |
        | **Total Available Units**          | Watch only         | SUM(MasterQuantity.AvailableQuantity).                                                     |
      </Accordion>

      <Accordion title="Protect revenue (10 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                            |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------------------- |
        | **Buybox Lost While Advertising**    | Alert band 85 / 60 | Buybox Lost While Advertising, broken down by row.                        |
        | **Cancellation Rate**                | Alert band 1 / 3   | Orders in a cancelled OrderStage ÷ total.                                 |
        | **Catalogue Drift vs Marketplace**   | Merchant rule      | Catalogue Drift vs Marketplace, broken down by row.                       |
        | **Failed Revisions**                 | Merchant rule      | MarketPlaceListingDetails.RevisionResponse LIKE '%error%'.                |
        | **Low-Stock SKUs**                   | Alert band 5 / 50  | MasterQuantity WHERE AvailableQuantity BETWEEN 1 AND low-stock threshold. |
        | **OOS SKUs With Active Ad Spend**    | Alert band 0 / 5   | OOS SKUs With Active Ad Spend, broken down by row.                        |
        | **Out-of-Stock SKUs**                | Alert band 0 / 5   | MasterQuantity WHERE AvailableQuantity \<= 0.                             |
        | **Oversell Risk vs Marketplace Qty** | Alert band 0 / 5   | Description pending editorial review; the signal is live.                 |
        | **Oversell-Risk SKUs**               | Alert band 0 / 5   | MasterQuantity WHERE InfiniteQuantity = 1 AND AvailableQuantity \<= 0.    |
        | **Stockout Spike**                   | Alert band 0 / 5   | Alerts for Stockout Spike.                                                |
      </Accordion>

      <Accordion title="Grow revenue (7 signals)">
        | Signal                   | Alert behaviour    | What it tracks                                                                                                  |
        | ------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**  | Alert band 0 / -5  | revenue ÷ distinct orders.                                                                                      |
        | **Gross Margin %**       | Alert band 0 / -3  | (net revenue − COGS) ÷ net revenue = (per-order TotalExVAT − line ProductCost) ÷ TotalExVAT. Shipping excluded. |
        | **Net Revenue (ex VAT)** | Watch only         | SUM(Report\_SalesReport.TotalExVAT).                                                                            |
        | **Revenue by Channel**   | Watch only         | Revenue grouped by Report\_SalesReport.OrderSource.                                                             |
        | **Total Orders**         | Alert band 0 / -10 | COUNT(DISTINCT Report\_SalesReport.OrderNumber).                                                                |
        | **Total Revenue**        | Alert band 0 / -5  | SUM(Report\_SalesReport.TotalIncVAT) WHERE Active=1, by OrderDate period.                                       |
        | **Units Sold**           | Watch only         | SUM(Report\_SalesReport.OrderQuantity).                                                                         |
      </Accordion>

      <Accordion title="Catalogue quality (5 signals)">
        | Signal                   | Alert behaviour  | What it tracks                                                            |
        | ------------------------ | ---------------- | ------------------------------------------------------------------------- |
        | **Active Listings**      | Watch only       | MarketPlaceListingDetails active rows, grouped by marketplace.            |
        | **Listing Error Rate**   | Alert band 1 / 5 | ProductStatus.Status = 0 (+ RevisionResponse errors) ÷ total active SKUs. |
        | **Listing Errors Spike** | Alert band 1 / 5 | Alerts for Listing Errors Spike.                                          |
        | **Overpriced SKUs**      | Merchant rule    | SUM(RepriceDailyReport.OverPricedCount) , losing buybox on price.         |
        | **Underpriced SKUs**     | Merchant rule    | SUM(RepriceDailyReport.UnderPricedCount) , margin left on table.          |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (18)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Oversell risk , infinite quantity with no stock">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Infinite-quantity listings with no physical stock will oversell; every oversold order becomes a cancellation, a refund and reputation damage.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS02`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Listing failures (ProductStatus error)">
        **Severity** high · **Outcome** Run operations · **Fix status** Candidate remediation

        Listings failing to publish sit invisible on the channel; inventory is committed but nothing can sell.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS03`
      </Accordion>

      <Accordion title="Order despatch backlog older than 48h">
        **Severity** high · **Outcome** Run operations · **Fix status** Candidate remediation

        A despatch backlog older than 48 hours breaches most marketplace SLAs and customer expectations simultaneously; late-shipment penalties follow.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS08`
      </Accordion>

      <Accordion title="Out-of-stock SKUs with open demand">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Out-of-stock SKUs with open demand are sales the store is actively turning away; replenishment or substitution recovers them.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS01`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Failed marketplace revisions">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed marketplace revisions mean price or content changes silently did not apply; the channel is showing stale data customers act on.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CHOPS04`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Repricer coverage gap on active Amazon SKUs">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Candidate remediation

        Active Amazon SKUs outside repricer coverage sit at static prices while competitors move; Buy Box share erodes quietly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS09`
      </Accordion>

      <Accordion title="SKUs without cost price (margin blind spot)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        SKUs without cost prices make margin invisible; repricers and promotions then optimise revenue while possibly destroying profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS05`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>

      <Accordion title="SKUs without dimensions / weight (courier rating gap)">
        **Severity** low · **Outcome** Customer experience · **Fix status** Candidate remediation

        Weight-based shipping cannot quote correctly for products without weights, causing checkout errors or mispriced delivery. Irrelevant for flat-rate stores, which is worth recording as a business rule so this never nags.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS06`
      </Accordion>

      <Accordion title="SKUs without images">
        **Severity** low · **Outcome** Catalogue quality · **Fix status** Candidate remediation

        Products without images barely convert; shoppers skip listings they cannot see.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS07`
      </Accordion>

      <Accordion title="Stale inventory with stock on hand (no 30d sales)">
        **Severity** low · **Outcome** Run operations · **Fix status** Candidate remediation

        Stock with no sales in 30 days ties up capital and storage; flagging it early feeds markdown or clearance decisions.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CHOPS10`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **12 read** and **0 write** operations across companydetails, inventorys, invoices, marketplacelistingdetails, masterquantitys, order details on CloudHub Insights. 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=cloudhub-insights)

    #### Ready to build your first CloudHub Insights 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | companydetails            | 1               | 0                |
      | inventorys                | 1               | 0                |
      | invoices                  | 1               | 0                |
      | marketplacelistingdetails | 1               | 0                |
      | masterquantitys           | 1               | 0                |
      | order details             | 1               | 0                |
      | order stages              | 1               | 0                |
      | order stagechangelogs     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# CockroachDB on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/cockroachdb

Monitor CockroachDB health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor CockroachDB health, cost and reliability signals, and catch incidents and runaway spend early.

[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=cockroachdb)

<CardGroup>
  <Card title="30">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (30)">
    ### Monitor performance

    30 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                              |
        | -------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------- |
        | **Active Nodes (status=live)**         | Watch only         | Description pending editorial review; the signal is live.                                                   |
        | **Cluster Node Count**                 | Merchant rule      | Description pending editorial review; the signal is live.                                                   |
        | **CockroachDB Health Score**           | Merchant rule      | Description pending editorial review; the signal is live.                                                   |
        | **Connection Pool Saturation %**       | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                   |
        | **Connection Pool at >90% Saturation** | Alert band 70 / 90 | Alerts for Connection Pool at >90% Saturation.                                                              |
        | **Connections In Use**                 | Watch only         | Description pending editorial review; the signal is live.                                                   |
        | **Database Disk Usage %**              | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                   |
        | **Decommissioning Nodes**              | Merchant rule      | Nodes in decommission state , long-running = stuck draining ranges.                                         |
        | **Last Successful Backup (hours ago)** | Alert band 24 / 72 | Last BACKUP TO S3 / GCS run. For Cloud: managed backups dashboard.                                          |
        | **Memory Usage %**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                   |
        | **Raft Quiescent Lag (seconds)**       | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                   |
        | **Range Lease Balance Skew %**         | Merchant rule      | (max leaseholder\_count - min leaseholder\_count) / total leases. >25% = hot node. CockroachDB-distinctive. |
        | **Replicas per Node**                  | Watch only         | Replicas per Node, compared across items.                                                                   |
        | **Statements per Second (live)**       | Watch only         | Description pending editorial review; the signal is live.                                                   |
        | **Unavailable Ranges**                 | Merchant rule      | CockroachDB-distinctive , ranges lacking quorum. Any >0 = some data unavailable for reads/writes.           |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                              |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------- |
        | **CRDB Inventory Rows vs Ecom Inventory**       | Merchant rule      | Description pending editorial review; the signal is live.                                   |
        | **CRDB Pool Saturation vs Traffic Burst**       | Alert band 70 / 90 | CRDB Pool Saturation vs Traffic Burst, broken down by row.                                  |
        | **CRDB Statements Spike vs Ecom Order Rate**    | Merchant rule      | Description pending editorial review; the signal is live.                                   |
        | **Slow Statements During Checkout Window (5m)** | Merchant rule      | Slow Statements During Checkout Window (5m), broken down by row.                            |
        | **Unavailable or Under-Replicated Ranges**      | Merchant rule      | CockroachDB-distinctive , quorum loss or replication gap. Any unavailable = data loss risk. |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                         | Alert behaviour      | What it tracks                                                                                                        |
        | ------------------------------ | -------------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **Slow-Query Rate %**          | Alert band 1 / 5     | Description pending editorial review; the signal is live.                                                             |
        | **Statement Latency p50 (ms)** | Watch only           | Description pending editorial review; the signal is live.                                                             |
        | **Statement Latency p95 (ms)** | Alert band 50 / 200  | Description pending editorial review; the signal is live.                                                             |
        | **Statement Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                             |
        | **Top Contended Statements**   | Merchant rule        | CockroachDB-distinctive , distributed transactions surface contention via crdb\_internal.cluster\_contention\_events. |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                                     | Alert behaviour    | What it tracks                                                                                                                                              |
        | ------------------------------------------ | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Block Cache Hit Rate %**                 | Alert band 95 / 80 | rocksdb\_block\_cache\_hits / (hits + misses) from the Admin HTTP API /\_status/vars - cumulative since node start. Requires admin\_http\_url; the SQL-only |
        | **Statement Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live.                                                                                                   |
        | **Statement Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Statement Error Rate Spike (>1% in 5m).                                                                                                          |
        | **Under-Replicated Ranges**                | Merchant rule      | Ranges below configured replication factor , typically self-heals; sustained >0 = balancer overloaded or node down.                                         |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                           |
        | ----------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- |
        | **Transaction Retries (24h)** | Merchant rule   | CockroachDB-distinctive , distributed transactions retry on conflict. High retries = contention hotspot. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **0 write** operations across crdbinternalclustercontentionevents, crdbinternalclustersettings, crdbinternalgossipnodes, crdbinternalnodestatementstatistics, crdbinternalranges, show nodes on CockroachDB. 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=cockroachdb)

    #### Ready to build your first CockroachDB 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                            | Read operations | Write operations |
      | ----------------------------------- | --------------- | ---------------- |
      | crdbinternalclustercontentionevents | 1               | 0                |
      | crdbinternalclustersettings         | 1               | 0                |
      | crdbinternalgossipnodes             | 1               | 0                |
      | crdbinternalnodestatementstatistics | 1               | 0                |
      | crdbinternalranges                  | 1               | 0                |
      | show nodes                          | 1               | 0                |
      | statusvars                          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Coda on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/coda

Monitor Coda publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Coda publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=coda)

<CardGroup>
  <Card title="11">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (11)">
    ### Monitor performance

    11 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (9 signals)">
        | Signal                     | Alert behaviour   | What it tracks                                                                                                                                |
        | -------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Blocked Rows**           | Alert band 0 / 8  | Rows whose status\_column reads blocked / impeded - the stuck list.                                                                           |
        | **Empty Field Rate %**     | Alert band 2 / 15 | Share of column x row cells with no value, measured against every column the doc declares (GET .../tables//columns) across the sampled tracke |
        | **Oldest Open Row (days)** | Merchant rule     | Age of the oldest not-done row from its createdAt - backlog-rot signal.                                                                       |
        | **Open Tracker Rows**      | Merchant rule     | Coda rows whose status\_column is not in the done set - top-of-funnel backlog volume.                                                         |
        | **Rows Resolved (7d)**     | Merchant rule     | Rows moved into a done-group status in the last 7 days (by updatedAt).                                                                        |
        | **Rows by Assignee**       | Merchant rule     | Coda tables have no native assignee primitive - derived from an assignee column when present.                                                 |
        | **Rows by Status**         | Watch only        | Distribution of tracker rows across the status\_column option set.                                                                            |
        | **Throughput Trend**       | Watch only        | Description pending editorial review; the signal is live.                                                                                     |
        | **VortexIQ Findings Open** | Merchant rule     | Coda rows we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced.                         |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                          |
        | ----------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the tracker with no edit for two weeks - these are losing money silently. Coda exposes updatedAt on every row for free. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                          | Alert behaviour      | What it tracks                                                                                               |
        | ------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Doc Freshness Lag (minutes)** | Alert band 60 / 1440 | Minutes since the Coda doc's updatedAt (GET /docs/) - the byo\_data\_source archetype's stale-feed detector. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Data-source API token invalid or access revoked">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this token fails, VortexIQ stops pulling data from this source entirely, and every card and finding built on it 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: `BYO-AUTH-001`
      </Accordion>

      <Accordion title="Source not updated in over 24h (stale data)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        A source that has not updated in over a day means every conclusion drawn from it describes yesterday; the staleness is invisible unless surfaced.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-FRESH-001`
      </Accordion>

      <Accordion title="Required-field empty rate above 15%">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When required fields are empty in more than 15 percent of rows, every downstream calculation inherits the gaps and quietly under-reports.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-DATA-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **3 write** operations across doctablerows, docs, doctables, docaclpermissions, dochookautomations, docpages on Coda. 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=coda)

    #### Ready to build your first Coda 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | doctablerows       | 1               | 2                |
      | docs               | 2               | 0                |
      | doctables          | 2               | 0                |
      | docaclpermissions  | 1               | 0                |
      | dochookautomations | 0               | 1                |
      | docpages           | 1               | 0                |
      | doctablecolumns    | 1               | 0                |
      | whoamis            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Confluence on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/confluence

Monitor Confluence publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Confluence publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=confluence)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                 |
        | ----------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 10  | Description pending editorial review; the signal is live.                                                                                      |
        | **Avg Lead Time (days)**            | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                      |
        | **Avg Time-to-Fix (days)**          | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                      |
        | **Backlog by Priority**             | Alert band 30 / 50 | Backlog by Priority.                                                                                                                           |
        | **Backlog by Status**               | Merchant rule      | Backlog by Status.                                                                                                                             |
        | **Blocked Tickets**                 | Alert band 0 / 8   | Finding-pages with `vortexiq.status = blocked` - the stuck list.                                                                               |
        | **Cycle Time by Priority**          | Alert band 3 / 5   | Cycle Time by Priority.                                                                                                                        |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | Of finding-pages created in the last 90 days, the share closed via a page-property decision. \<50% means inflow outpaces the team.             |
        | **In Progress**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                      |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Description pending editorial review; the signal is live.                                                                                      |
        | **Open Tickets**                    | Alert band 10 / 40 | Finding-pages in the mapped Space whose `vortexiq.status` is in the open set - top-of-funnel queue depth.                                      |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 3   | People with >10 open finding-pages assigned via `vortexiq.assignee` - capacity bottleneck candidates.                                          |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                      |
        | **Sprint Progress**                 | Alert band 80 / 50 | Description pending editorial review; the signal is live.                                                                                      |
        | **Sprint Velocity (avg)**           | Alert band 30 / 15 | Sprint Velocity (avg) over time.                                                                                                               |
        | **Throughput Trend**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                      |
        | **Tickets Resolved (7d)**           | Alert band 10 / 3  | Description pending editorial review; the signal is live.                                                                                      |
        | **Tickets by Assignee**             | Alert band 5 / 10  | Tickets by Assignee.                                                                                                                           |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                      |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                                      |
        | **VortexIQ Findings Open**          | Merchant rule      | Finding-pages we wrote from audit findings whose `vortexiq.status` is still open - the live backlog of things VortexIQ surfaced into the wiki. |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                                      |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                  |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Finding-pages whose `version.when` has not changed for two weeks - the queue-rot indicator. Comments don't reset the clock; only page edits do. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **4 write** operations across pages, pagepropertys, contentchildcomments, contentsearchs, spaces, users on Confluence. 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=confluence)

    #### Ready to build your first Confluence 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | pages                | 2               | 2                |
      | pagepropertys        | 1               | 1                |
      | contentchildcomments | 0               | 1                |
      | contentsearchs       | 1               | 0                |
      | spaces               | 1               | 0                |
      | users                | 1               | 0                |
      | usercurrents         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Constant Contact on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/constant-contact

Monitor email revenue and deliverability for Constant Contact, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Constant Contact, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=constant-contact)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (13 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                                                                               |
        | ----------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Campaign Status Breakdown** | Watch only        | Campaigns grouped by status (sent, draft, scheduled).                                                        |
        | **Checkout-to-Order Rate**    | Merchant rule     | Share of email-driven checkouts that became paid orders. Needs a commerce sibling to confirm the order side. |
        | **Click-to-Open Rate**        | Alert band 10 / 3 | Clicks as a share of opens. A truer engagement signal than open rate.                                        |
        | **Conversion Rate**           | Alert band 3 / 1  | Orders as a share of emails sent. Ties send volume to revenue.                                               |
        | **Email Click Rate**          | Alert band 3 / 1  | Share of delivered emails that earned a click. The clearest engagement signal.                               |
        | **Engagement Funnel**         | Watch only        | Sent to delivered to opened to clicked, showing where engagement drops off.                                  |
        | **List Count**                | Watch only        | Number of audiences on the account.                                                                          |
        | **Lists Overview**            | Watch only        | Every audience with its member count.                                                                        |
        | **Revenue per Recipient**     | Watch only        | Revenue divided by emails sent. What each address is worth per send.                                         |
        | **Revenue per Send**          | Watch only        | Revenue divided by emails sent, the efficiency of each send.                                                 |
        | **Top Lists by Name**         | Watch only        | Largest audiences by member count.                                                                           |
        | **Total Revenue**             | Merchant rule     | Placed-order revenue attributed to Constant Contact sends in the 30-day window. The hero number.             |
        | **Total Sends**               | Watch only        | Total emails sent across campaigns in the window.                                                            |
      </Accordion>

      <Accordion title="Run operations (9 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                             |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------------ |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts.                                                  |
        | **Email Open Rate**           | Alert band 25 / 15 | Share of delivered emails opened. iOS Mail Privacy inflates this; pair with click-to-open. |
        | **Flow Count Summary**        | Watch only         | How many automations exist on the account.                                                 |
        | **Flow Status Breakdown**     | Merchant rule      | Automations split by status (active, draft, paused).                                       |
        | **Flow Trigger Types**        | Watch only         | Automations grouped by what triggers them.                                                 |
        | **Flows List**                | Watch only         | Every automation and its current status.                                                   |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                                  |
        | **Placed Orders Total**       | Watch only         | Orders attributed to email in the window.                                                  |
        | **Segments Overview**         | Merchant rule      | Saved segments and their sizes. Fewer than 3 signals an under-segmented account.           |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                  | Alert behaviour      | What it tracks                                                                                     |
        | ----------------------- | -------------------- | -------------------------------------------------------------------------------------------------- |
        | **Bounce Rate**         | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation; CON02 fires here.              |
        | **Delivery Rate**       | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                          |
        | **Email Health KPIs**   | Watch only           | Delivered, bounced and unsubscribed at a glance, your deliverability vitals.                       |
        | **Refund Rate**         | Merchant rule        | Share of attributed orders later refunded.                                                         |
        | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam complaints per send. Above 0.1% inbox providers start marking the sender domain. CON03 fires. |
        | **Unsubscribe Rate**    | Alert band 0.3 / 1   | Unsubscribes per send. A spike signals list fatigue or off-target content.                         |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Watch only      | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Low Delivery Rate">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        When more than 1 in 20 emails fails to arrive at all, every campaign, promotion and transactional message built on that list underperforms, and the gap compounds as the list grows.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CON05`
      </Accordion>

      <Accordion title="High Bounce Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CON02`
      </Accordion>

      <Accordion title="Inactive Automations">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CON01`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CON03`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited Segmentation">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CON04`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **2 write** operations across contactlists, emails, account summarys, activityaddlistmemberships, contacts, report emailreporttrackingsummarys on Constant Contact. 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=constant-contact)

    #### Ready to build your first Constant Contact 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                  | Read operations | Write operations |
      | ----------------------------------------- | --------------- | ---------------- |
      | contactlists                              | 2               | 1                |
      | emails                                    | 2               | 0                |
      | account summarys                          | 1               | 0                |
      | activityaddlistmemberships                | 0               | 1                |
      | contacts                                  | 1               | 0                |
      | report emailreporttrackingsummarys        | 1               | 0                |
      | report summaryreportemailcampaignsummarys | 1               | 0                |
      | segments                                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ConvertKit (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/convertkit-api

Monitor email revenue and deliverability for ConvertKit (API), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for ConvertKit (API), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=convertkit-api)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                 |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------ |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts.                                      |
        | **Email Open Rate**           | Alert band 25 / 15 | Apple Mail Privacy inflates this - pair with click-to-open for a truer signal. |
        | **Flow Count Summary**        | Watch only         | How many sequences exist on the account.                                       |
        | **Flow Status Breakdown**     | Watch only         | Sequences split by status (active, hold/paused).                               |
        | **Flow Trigger Types**        | Watch only         | Sequences grouped by what triggers enrolment.                                  |
        | **Flows List**                | Watch only         | Every sequence (automation) and its current status.                            |
        | **List Count**                | Watch only         | Number of forms (lists) on the account.                                        |
        | **List Health Summary**       | Watch only         | Total reachable members across all forms.                                      |
        | **Lists Overview**            | Watch only         | Every form (list) with its subscription count.                                 |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to email in the window.                                      |
        | **Segments Overview**         | Watch only         | Tags (saved segments) and their sizes.                                         |
        | **Top Lists by Name**         | Watch only         | Largest forms (lists) by subscription count.                                   |
        | **Total Sends**               | Merchant rule      | Total emails sent across broadcasts in the window.                             |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                             |
        | -------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------- |
        | **Bounce Rate**                        | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation.                                        |
        | **Delivery Rate**                      | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                                  |
        | **Email Health KPIs**                  | Watch only           | Delivered, bounced and unsubscribed at a glance - your deliverability vitals.                              |
        | **Email Share of Total Store Revenue** | Merchant rule        | Healthy creator brands range 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk. |
        | **Engagement Funnel**                  | Watch only           | Sent → Delivered → Opened → Clicked. Drop-offs expose deliverability vs content weakness.                  |
        | **Refund Rate**                        | Merchant rule        | Share of attributed orders later refunded.                                                                 |
        | **Sequence-Driven Recovery Value**     | Watch only           | \$/30D recovered by welcome/nurture sequences. Goes to zero if the sequence is on hold (CK-SEQ-001).       |
        | **Spam Complaint Rate**                | Alert band 0.1 / 0.3 | Spam complaints per send. Above 0.1% puts deliverability at risk.                                          |
        | **Unsubscribe Rate**                   | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.                                 |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                                                           |
        | ----------------------------- | ----------------- | ---------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Watch only        | Broadcasts grouped by status (sent, draft, scheduled).                                   |
        | **Checkout-to-Order Rate**    | Merchant rule     | Share of started checkouts that became paid orders.                                      |
        | **Click-to-Open Rate**        | Alert band 10 / 3 | Clicks as a share of opens - engagement quality independent of open-rate inflation.      |
        | **Conversion Rate**           | Alert band 3 / 1  | Orders as a share of emails sent - ties send volume to revenue.                          |
        | **Email Click Rate**          | Alert band 3 / 1  | Share of delivered emails that earned a click - the clearest engagement signal.          |
        | **Revenue per Recipient**     | Merchant rule     | Revenue divided by emails sent - what each address is worth per send.                    |
        | **Revenue per Send**          | Merchant rule     | Revenue divided by emails sent - the efficiency of each send.                            |
        | **Total Revenue**             | Merchant rule     | Placed-order revenue attributed to ConvertKit broadcasts in the window. The hero number. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                            |
        | --------------------- | --------------- | ------------------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the commerce sibling reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Inactive Sequences">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CK04`
      </Accordion>

      <Accordion title="Limited Lists/Segmentation">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CK05`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CK02`
      </Accordion>

      <Accordion title="Unsubscribe Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A rising unsubscribe rate shrinks the reachable audience and usually signals frequency or relevance problems; every lost subscriber removes future campaign and flow revenue.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CK01`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Low Open Rate">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Consistently low opens mean subject lines, send times or list quality are wasting sends, and engagement-based inbox placement then makes future sends perform even worse.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CK03`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **1 write** operations across sequences, accounts, broadcasts, broadcaststats, forms, sequencesubscriptions on ConvertKit (API). 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=convertkit-api)

    #### Ready to build your first ConvertKit (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource              | Read operations | Write operations |
      | --------------------- | --------------- | ---------------- |
      | sequences             | 1               | 1                |
      | accounts              | 1               | 0                |
      | broadcasts            | 1               | 0                |
      | broadcaststats        | 1               | 0                |
      | forms                 | 1               | 0                |
      | sequencesubscriptions | 1               | 0                |
      | subscribers           | 1               | 0                |
      | tags                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Costco SIP on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/costco-sip

Monitor Costco SIP listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Costco SIP listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=costco-sip)

<CardGroup>
  <Card title="41">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (41)">
    ### Monitor performance

    41 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                                                                         |
        | -------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Order Value**          | Watch only        | Average Order Value as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Average PO Value**             | Watch only        | Average \$ per PO. Falling AVP at steady PO count = Costco buyers ranging fewer SKUs per order.                                                        |
        | **Buyer Messages Unread**        | Watch only        | Buyer Messages Unread as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard da |
        | **Deduction Pattern**            | Watch only        | Top 10 deduction reason codes by \$ value. Identifies systemic issues vs one-off events.                                                               |
        | **Error Pattern (7d)**           | Watch only        | Top 5 parse-error codes across inbound + outbound files. Identifies systemic vs transient issues.                                                      |
        | **File-Volume Anomaly**          | Merchant rule     | Daily inbound + outbound file count vs rolling baseline. Sudden volume drop or spike both deserve attention.                                           |
        | **Fill Rate**                    | Merchant rule     | Units shipped / units ordered across all POs. Below 98% triggers Costco's vendor-scorecard penalty.                                                    |
        | **Invoiced Value (30d)**         | Alert band 0 / -5 | Total \$ invoiced to Costco. Cross-check with weekly\_po\_value; persistent gaps = un-invoiced fulfilled POs.                                          |
        | **Items Active**                 | Watch only        | Total items listed as active in Costco's catalogue. Baseline for delisting alerts.                                                                     |
        | **Items Delisted This Week**     | Merchant rule     | Items flipped from active -> delisted in the last 7 days. Direct shelf-loss; chase reasons within 24h.                                                 |
        | **Items Pending Review**         | Merchant rule     | Items Costco has flagged for review (case-pack mismatch, GTIN error, label issue). Resolve before they delist.                                         |
        | **Items with Field Drift**       | Merchant rule     | Items where description, case-pack, or cost-per-unit differ between our supplier system and Costco's catalogue.                                        |
        | **Last Successful Inbound**      | Merchant rule     | Hours since the last successfully-parsed inbound file. >36h on a working day = something has stopped.                                                  |
        | **Last Successful Outbound**     | Merchant rule     | Hours since the last outbound file Costco ACKed. Stale = our drops aren't being read or are failing parse.                                             |
        | **Marketplace Fees Paid**        | Watch only        | Marketplace Fees Paid as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard da |
        | **Oldest Pending Payout (days)** | Alert band 7 / 21 | Oldest Pending Payout (days) as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the stan |
        | **PO Acknowledgment Rate**       | Merchant rule     | % of inbound POs that we sent an ACK file for. Missing ACKs = Costco assumes we're offline.                                                            |
        | **POs Missing ASN**              | Merchant rule     | Open POs where the ship-by has passed and no ASN has been dropped to /outbox. Action immediately.                                                      |
        | **Payments Overdue**             | Merchant rule     | Invoices past Costco's standard 30-day net term with no paid\_at. Reach out to AP before write-off.                                                    |
        | **Pending Payouts**              | Watch only        | Pending Payouts as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard data ref |
        | **Sync Error Count (7d)**        | Merchant rule     | Item-master-update files we sent that Costco rejected. Each rejection blocks the related items from updating.                                          |
        | **Total Transactions**           | Watch only        | Total Transactions as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard data  |
      </Accordion>

      <Accordion title="Protect revenue (10 signals)">
        | Signal                           | Alert behaviour | What it tracks                                                                                                                           |
        | -------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Chargeback Risk (30d)**        | Merchant rule   | Estimated \$ chargebacks from late ASNs + fill-rate misses + ACK failures. Costco aggressively charges back; this is recoverable margin. |
        | **Costco Account Health Score**  | Merchant rule   | Composite , feed-uptime × on-time-ASN-rate × inverse(chargeback-value) × inverse(delisted-items).                                        |
        | **Costco Issues in Jira**        | Merchant rule   | Open Jira tickets referencing a Costco PO or chargeback. Ageing tickets = unrecovered chargebacks + un-resolved ranging risk.            |
        | **Costco POs via ShipBob (SLA)** | Merchant rule   | Costco PO ship-by SLA isolated to orders fulfilled through ShipBob , separates 3PL performance from internal-warehouse performance.      |
        | **Costco vs DTC Pricing Parity** | Merchant rule   | Items where the wholesale unit cost we charge Costco is materially below our own DTC list price , MAP-compliance + margin signal.        |
        | **Item-Master Sync Status**      | Merchant rule   | Items currently flagged 'pending review' or 'delisted' in Costco's catalogue , proxy for ranging risk.                                   |
        | **Late ASN Burst**               | Merchant rule   | Burst of ASNs sent past Costco's ship-by window. Each is a chargeback; clusters mean a fulfilment-side breakage to chase.                |
        | **Late ASN Count (30d)**         | Merchant rule   | ASNs sent AFTER Costco's ship-by window. Each one is an automatic chargeback under Costco's supplier rules.                              |
        | **On-Time ASN Rate**             | Merchant rule   | % of POs that received an ASN before Costco's ship-by window. Direct chargeback driver.                                                  |
        | **Revenue at Risk (live)**       | Merchant rule   | Sum of (delisted\_items × velocity × ASP) + (open POs past ship-by × chargeback rate). Recoverable if action taken.                      |
      </Accordion>

      <Accordion title="Grow revenue (5 signals)">
        | Signal                         | Alert behaviour   | What it tracks                                                                                                                                         |
        | ------------------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Daily PO Count**             | Watch only        | POs received per day. Steady-state cadence; flat days are usually weekends/holidays.                                                                   |
        | **Item Delisting Burst (24h)** | Merchant rule     | Multiple items moved from active -> delisted in 24h , usually a category-wide ranging review. Direct revenue blocker; investigate the same day.        |
        | **Top Listings by Revenue**    | Watch only        | Top Listings by Revenue as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard  |
        | **Total Revenue**              | Watch only        | Total Revenue as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard data refre |
        | **Weekly PO Value**            | Alert band 0 / -5 | Sum of POs received this week. Costco PO cadence is steady , sudden drops signal ranging changes.                                                      |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                                                                                         |
        | -------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**        | Watch only      | Active Listings as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard data ref |
        | **Listings Expiring Soon** | Watch only      | Listings Expiring Soon as exposed by the Costco SIP integration. The metric is computed from the latest available data and refreshed on the standard d |
        | **Missing Overnight Feed** | Merchant rule   | Costco's daily PO drop typically lands by 2am UK. No file by 7am working-day = either Costco's side has stopped OR our pickup has stopped.             |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                      | Alert behaviour | What it tracks                                                                                                                               |
        | --------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
        | **SFTP Connection Failure** | Merchant rule   | SFTP handshake or auth failures in a row. Most common cause: AIOS egress IP not allowlisted by Costco , file with the supplier-portal admin. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across inboxs, outboxs, archives on Costco SIP. 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=costco-sip)

    #### Ready to build your first Costco SIP 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | inboxs   | 2               | 0                |
      | outboxs  | 1               | 1                |
      | archives | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Crisp on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/crisp

Monitor Crisp pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Crisp 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=crisp)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour     | What it tracks                                                                                                                             |
        | ----------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7    | Mean days from first-response (work started) to resolved - how long active work takes.                                                     |
        | **Avg Lead Time (days)**            | Alert band 5 / 14   | Mean days from created\_at to resolved\_at - total time in the system including queue wait.                                                |
        | **Avg Time-to-Fix (days)**          | Alert band 3 / 14   | Mean days from finding created\_at to resolved\_at over the window.                                                                        |
        | **Backlog by Priority**             | Alert band 25 / 50  | Open conversations split by priority segment - is the queue top-heavy with urgent work?                                                    |
        | **Backlog by Status**               | Merchant rule       | Open conversations split by state (pending / unresolved) - the shape of the working inbox.                                                 |
        | **Blocked Tickets**                 | Alert band 0 / 8    | Open conversations tagged blocked/waiting - cannot progress until an external dependency clears. Warn 3 / critical 8.                      |
        | **Cycle Time by Priority**          | Alert band 2 / 5    | Mean cycle time bucketed by priority - are urgent items actually moving faster?                                                            |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50  | resolved\_in\_90d / created\_in\_90d x 100. Is the team fixing what Vortex IQ surfaces, or is the audit just noise?                        |
        | **First Response Time (min)**       | Alert band 30 / 240 | Crisp's own 'First Response Time' Analytics metric (POST /website//analytics/generate, confirmed real route per the official Go SDK's rout |
        | **In Progress**                     | Merchant rule       | Conversations in unresolved state with an operator assigned - being handled right now.                                                     |
        | **Oldest Open (days)**              | Alert band 14 / 90  | Age in days of the oldest still-open conversation - the maximum-age outlier.                                                               |
        | **Open Tickets**                    | Alert band 50 / 200 | Every unresolved Crisp conversation (customer chat + findings) - the whole open inbox.                                                     |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1    | Count of operators carrying more than 10 open conversations - redistribution signal.                                                       |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15   | % of findings added after the sprint started - work preempting committed audit follow-up.                                                  |
        | **Sprint Progress**                 | Alert band 90 / 70  | % of the current sprint committed findings resolved against time elapsed - burn-down health.                                               |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20   | Findings resolved per sprint, averaged over the last 5 sprints - capacity trend.                                                           |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25   | Conversations moved to resolved in the last 7 days vs the prior 7 - weekly outflow.                                                        |
        | **Tickets by Assignee**             | Alert band 5 / 10   | Open conversations per operator - where the work is concentrated.                                                                          |
        | **Unassigned Tickets**              | Alert band 0 / 20   | Open conversations with no operator assigned - nobody owns these. Warn 5 / critical 20.                                                    |
        | **VortexIQ Findings In Progress**   | Merchant rule       | Findings in unresolved state with an assigned operator - actively being worked.                                                            |
        | **VortexIQ Findings Open**          | Alert band 5 / 20   | Crisp conversations tagged vortexiq:finding in pending/unresolved state - open audit work the team has not closed.                         |
        | **VortexIQ Findings Resolved**      | Merchant rule       | Findings moved to resolved state in the trailing 90 days - the raw outflow count behind resolution rate.                                   |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour  | What it tracks                                                                                                  |
        | ----------------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 0 / 5 | Findings with no agent activity in 14 days - quietly losing money while everyone assumes they are in the queue. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal               | Alert behaviour | What it tracks                                                                         |
        | -------------------- | --------------- | -------------------------------------------------------------------------------------- |
        | **Throughput Trend** | Merchant rule   | Daily resolved-count sparkline over 30 days - is the team speeding up or slowing down? |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **4 write** operations across websites, websiteanalyticsgenerates, websiteconversations, websiteconversationmessages, websiteconversationmetas, websiteconversationroutings on Crisp. 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=crisp)

    #### Ready to build your first Crisp 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | websites                    | 1               | 0                |
      | websiteanalyticsgenerates   | 0               | 1                |
      | websiteconversations        | 1               | 0                |
      | websiteconversationmessages | 1               | 0                |
      | websiteconversationmetas    | 1               | 0                |
      | websiteconversationroutings | 0               | 1                |
      | websiteconversationsegments | 0               | 1                |
      | websiteconversationstates   | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Criteo on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/criteo

Monitor Criteo campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Criteo campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/criteo) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=criteo)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                        |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**                             | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **CPC by Campaign**                             | Watch only         | CPC by Campaign.                                                                                                                      |
        | **CTR by Campaign**                             | Watch only         | CTR by Campaign.                                                                                                                      |
        | **Campaign Comparison**                         | Watch only         | Campaign Comparison, broken down by row.                                                                                              |
        | **Clicks vs Conversions**                       | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Conversion Actions Breakdown**                | Watch only         | Conversion Actions Breakdown.                                                                                                         |
        | **Conversion Drop Alert**                       | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Conversion Funnel**                           | Watch only         | Conversion Funnel, stage by stage.                                                                                                    |
        | **Conversion Lag**                              | Watch only         | Conversion Lag, compared across items.                                                                                                |
        | **Conversion Rate Trend**                       | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Conversion Rate by Campaign**                 | Watch only         | Conversion Rate by Campaign.                                                                                                          |
        | **Conversion Rate by Device**                   | Watch only         | Conversion Rate by Device.                                                                                                            |
        | **Conversions Trend**                           | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Conversions by Campaign**                     | Watch only         | Conversions by Campaign.                                                                                                              |
        | **Conversions by Country**                      | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Conversions by Day of Week**                  | Watch only         | Conversions by Day of Week.                                                                                                           |
        | **Conversions by Device**                       | Watch only         | Conversions by Device.                                                                                                                |
        | **Conversions by Hour**                         | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Criteo One Tag / First-Party Audience Decay** | Merchant rule      | Criteo lives or dies on first-party retargeting signal. Tag-without-cookie pattern = ITP catching up , audiences shrink in next sync. |
        | **Landing Page Revenue**                        | Watch only         | Landing Page Revenue, broken down by row.                                                                                             |
        | **Overspending Campaigns**                      | Watch only         | Overspending Campaigns, broken down by row.                                                                                           |
        | **ROAS**                                        | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                                             |
        | **ROAS Trend**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **ROAS by Campaign**                            | Watch only         | ROAS by Campaign.                                                                                                                     |
        | **ROAS by Day of Week**                         | Watch only         | ROAS by Day of Week.                                                                                                                  |
        | **ROAS by Device**                              | Watch only         | ROAS by Device.                                                                                                                       |
        | **ROAS by Region**                              | Watch only         | ROAS by Region.                                                                                                                       |
        | **Retargeting ROAS Dropped Below Threshold**    | Alert band 3 / 1.5 | Criteo's defensive retargeting ROAS , first signal that cookie deprecation or ITP rules just got stricter.                            |
        | **Revenue by Campaign**                         | Watch only         | Revenue by Campaign.                                                                                                                  |
        | **Search Terms Report**                         | Watch only         | Search Terms Report, broken down by row.                                                                                              |
        | **Spend by Campaign**                           | Watch only         | Spend by Campaign.                                                                                                                    |
        | **Top Cities by Conversions**                   | Watch only         | Top Cities by Conversions.                                                                                                            |
        | **Top Keywords by Conversions**                 | Watch only         | Top Keywords by Conversions.                                                                                                          |
        | **Top Performing Campaigns**                    | Watch only         | Top Performing Campaigns, broken down by row.                                                                                         |
        | **Total Revenue**                               | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Underspending Campaigns**                     | Watch only         | Underspending Campaigns, broken down by row.                                                                                          |
        | **Worst Performing Campaigns**                  | Watch only         | Worst Performing Campaigns, broken down by row.                                                                                       |
        | **Zero-Conversion Spend**                       | Watch only         | Description pending editorial review; the signal is live.                                                                             |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                                | Alert behaviour   | What it tracks                                                                                                                                       |
        | ----------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Dynamic Ads on Out-of-Stock SKUs**           | Alert band 5 / 50 | Criteo's whole model is dynamic product retargeting , OOS SKUs in the creative pool are pure waste.                                                  |
        | **Branded Paid Clicks Cannibalising Organic**         | Merchant rule     | Retargeting cookie-pool users who already know the brand and would have come back via direct/organic , pure margin reclaim on the retargeting cycle. |
        | **CTR Decline Alert**                                 | Watch only        | Description pending editorial review; the signal is live.                                                                                            |
        | **Landing Pages with Poor Web Vitals**                | Merchant rule     | Dynamic ads send users to product detail pages , LCP regression there kills the retargeting cycle's whole purpose.                                   |
        | **Spend on Campaigns with Active Feed Rejections**    | Merchant rule     | Highest-leverage card in this manifest , Criteo IS feed-driven. Feed rejections = no creative renders = wasted spend.                                |
        | **Wasted-Spend Burst (feed-failed dynamic creative)** | Alert band 5 / 50 | Most common cause: feed rejected → dynamic creative falls back to generic → CR drops to \~0.                                                         |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **2 write** operations across advertisers, marketingsolutioncampaigns, marketingsolutioncreatives, oauth2tokens, statisticreports on Criteo. 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=criteo)

    #### Ready to build your first Criteo 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | advertisers                | 1               | 0                |
      | marketingsolutioncampaigns | 1               | 0                |
      | marketingsolutioncreatives | 1               | 0                |
      | oauth2tokens               | 0               | 1                |
      | statisticreports           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Customer.io (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/customer-io

Monitor email revenue and deliverability for Customer.io (API), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Customer.io (API), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=customer-io)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (8 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                                                      |
        | ----------------------------- | ----------------- | ----------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Watch only        | Newsletters and broadcasts grouped by status (sent, draft, scheduled).              |
        | **Click-to-Open Rate**        | Alert band 10 / 3 | Clicks as a share of opens - engagement quality independent of open-rate inflation. |
        | **Conversion Rate**           | Alert band 3 / 1  | Converted / sent - ties send volume to the campaign goal.                           |
        | **Email Click Rate**          | Alert band 3 / 1  | Clicked / delivered - the clearest engagement signal.                               |
        | **Flow Count Summary**        | Watch only        | How many campaigns exist on the workspace.                                          |
        | **Flow Status Breakdown**     | Merchant rule     | Campaigns split by state (running, draft, stopped).                                 |
        | **Flows List**                | Watch only        | Every campaign (triggered journey) and its current state.                           |
        | **Total Sends**               | Watch only        | Total emails sent across campaigns and newsletters in the window.                   |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                            |
        | -------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------- |
        | **Abandoned-Cart Recovery Value**      | Watch only           | \$/30D recovered by the abandoned-cart campaign. Goes to zero if the campaign is in draft (CIO-CAMP-001). |
        | **Bounce Rate**                        | Alert band 2 / 5     | Bounced / sent. Bounce >5% trips ISP throttling. Audit CIO02 fires here.                                  |
        | **Delivery Rate**                      | Alert band 98 / 95   | Delivered / sent. Below 95% needs attention.                                                              |
        | **Email Share of Total Store Revenue** | Merchant rule        | Healthy DTC ranges 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk.          |
        | **Engagement Funnel**                  | Watch only           | Sent -> Delivered -> Opened -> Clicked. Drop-offs expose deliverability vs content weakness.              |
        | **Spam Complaint Rate**                | Alert band 0.1 / 0.3 | Spammed / delivered. Above 0.1% Gmail starts marking sender domain. CIO03 fires.                          |
        | **Unsubscribe Rate**                   | Alert band 0.5 / 2   | Unsubscribed / delivered. A spike signals list fatigue or off-target content.                             |
      </Accordion>

      <Accordion title="Run operations (3 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                     |
        | ----------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Watch only         | Estimated subscribed, reachable customers (total minus unsubscribed).                              |
        | **Email Open Rate**           | Alert band 25 / 15 | Opened / delivered. Apple Mail Privacy inflates this - pair with click-to-open for a truer signal. |
        | **Segments Overview**         | Merchant rule      | Saved segments and their member counts. Audit CIO04 fires below 3 segments.                        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Email Bounce Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CIO02`
      </Accordion>

      <Accordion title="High Unsubscribe Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A rising unsubscribe rate shrinks the reachable audience and usually signals frequency or relevance problems; every lost subscriber removes future campaign and flow revenue.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CIO05`
      </Accordion>

      <Accordion title="Inactive Campaigns">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CIO01`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CIO03`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited Segmentation">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CIO04`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **12 read** and **0 write** operations across campaigns, broadcasts, broadcastmetrics, campaign actions, campaign metrics, customers on Customer.io (API). 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=customer-io)

    #### Ready to build your first Customer.io (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | campaigns        | 2               | 0                |
      | broadcasts       | 1               | 0                |
      | broadcastmetrics | 1               | 0                |
      | campaign actions | 1               | 0                |
      | campaign metrics | 1               | 0                |
      | customers        | 1               | 0                |
      | messages         | 1               | 0                |
      | newsletters      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# CyberSource on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/cybersource

Monitor CyberSource payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor CyberSource payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=cybersource)

<CardGroup>
  <Card title="59">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (59)">
    ### Monitor performance

    59 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (33 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                                                |
        | ----------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **3DS Challenge Abandon Rate**            | Alert band 15 / 25   | When customers see the 3DS challenge and bail. High abandon = friction; consider smart routing.                                               |
        | **3DS Friction Revenue Loss**             | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **3DS Frictionless Volume**               | Watch only           | Description pending editorial review; the signal is live.                                                                                     |
        | **3DS Success Rate**                      | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **3DS-Authenticated Transactions**        | Watch only           | Description pending editorial review; the signal is live.                                                                                     |
        | **Avg Dispute Response Time**             | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Card Brand Performance**                | Watch only           | Visa / MC / Amex / Discover × auth-rate / decline-rate / dispute-rate matrix.                                                                 |
        | **Chargeback Rate**                       | Alert band 0.5 / 0.9 | Description pending editorial review; the signal is live.                                                                                     |
        | **Chargeback Reason Codes**               | Merchant rule        | Reason 4853 (fraud), 4855 (goods/services not received), 4863 (cardholder doesn't recognise) , each has different prevention.                 |
        | **Chargeback Value (30d)**                | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Decision Manager Score Mix**            | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Decline Rate**                          | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                                                     |
        | **Decline Rate Spike Alert**              | Merchant rule        | Alerts for Decline Rate Spike Alert.                                                                                                          |
        | **Decline Rate by Card-Country**          | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                                                     |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When CS declines spike, do we see commerce checkout completion drop? If yes, declines are causing real revenue loss , not just buyer remorse. |
        | **Declined Transactions**                 | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                                                     |
        | **Dispute Rate**                          | Alert band 0.5 / 1   | Description pending editorial review; the signal is live.                                                                                     |
        | **Dispute Threshold Watch**               | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Dispute Win Rate**                      | Merchant rule        | Industry baseline \~35-40%. Below that means evidence packs are weak or response too slow.                                                    |
        | **Disputes vs Returns Correlation**       | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Fraud Velocity Alert**                  | Merchant rule        | Alerts for Fraud Velocity Alert.                                                                                                              |
        | **Net Revenue (after refunds + fees)**    | Alert band 0 / -5    | Description pending editorial review; the signal is live.                                                                                     |
        | **Open Chargebacks**                      | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Payment Health Score**                  | Merchant rule        | Composite , auth-rate × inverse decline × inverse dispute × settlement-on-time. The CFO single-number.                                        |
        | **Recoverable Declines (soft)**           | Merchant rule        | Soft-decline value (do\_not\_honor, insufficient\_funds, expired) , recoverable via retry / dunning.                                          |
        | **Recoverable Revenue (decline-driven)**  | Merchant rule        | Total \$ leaked through soft declines that retry / dunning could recover next month.                                                          |
        | **Refund Count**                          | Alert band 10 / 50   | Description pending editorial review; the signal is live.                                                                                     |
        | **Refund Rate**                           | Alert band 2 / 5     | Description pending editorial review; the signal is live.                                                                                     |
        | **Refund Value**                          | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Refund Velocity Trend**                 | Merchant rule        | Description pending editorial review; the signal is live.                                                                                     |
        | **Revenue at Risk (live)**                | Merchant rule        | Live decline-driven revenue loss while the spike is active.                                                                                   |
        | **Top Decline Reasons**                   | Merchant rule        | Reason-coded declines (insufficient\_funds, do\_not\_honor, fraud\_suspected, expired\_card) , each has a different fix.                      |
        | **Top Declining Issuers**                 | Merchant rule        | Issuer-bank decline rates ('Capital One declines 18% of yours'). Leads to recoverable revenue via dunning / token retry.                      |
      </Accordion>

      <Accordion title="Run operations (14 signals)">
        | Signal                               | Alert behaviour   | What it tracks                                            |
        | ------------------------------------ | ----------------- | --------------------------------------------------------- |
        | **3DS Failure Alert**                | Merchant rule     | Alerts for 3DS Failure Alert.                             |
        | **Avg Settlement Time (days)**       | Alert band 7 / 21 | Description pending editorial review; the signal is live. |
        | **Card vs Billing Country Mismatch** | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Corporate vs Consumer Cards**      | Watch only        | Corporate vs Consumer Cards, shown by share.              |
        | **Cross-Border Transaction Share**   | Watch only        | Description pending editorial review; the signal is live. |
        | **Dunning Recovery Rate**            | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Oldest Pending Payout (days)**     | Alert band 7 / 21 | Description pending editorial review; the signal is live. |
        | **Pending Settlement**               | Watch only        | Description pending editorial review; the signal is live. |
        | **Prepaid Card Share**               | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Recurring Charge Failure Rate**    | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Recurring Charge Volume**          | Watch only        | Recurring Charge Volume over time.                        |
        | **Settlement Batch Success Rate**    | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Settlement Stuck**                 | Merchant rule     | Alerts for Settlement Stuck.                              |
        | **Total Transaction Value**          | Alert band 0 / -5 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                            |
        | ----------------------------- | ----------------- | --------------------------------------------------------- |
        | **Average Transaction Value** | Watch only        | Description pending editorial review; the signal is live. |
        | **High-Value Transactions**   | Merchant rule     | High-Value Transactions, broken down by row.              |
        | **Revenue Over Time**         | Alert band 0 / -5 | Description pending editorial review; the signal is live. |
        | **Revenue by Country**        | Watch only        | Description pending editorial review; the signal is live. |
        | **Revenue by Currency**       | Watch only        | Revenue by Currency.                                      |
        | **Sales Volume Anomalies**    | Merchant rule     | Sales Volume Anomalies over time.                         |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                      | Alert behaviour | What it tracks                                            |
        | --------------------------- | --------------- | --------------------------------------------------------- |
        | **AVS Match Rate**          | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Successful Transactions** | Watch only      | Description pending editorial review; the signal is live. |
        | **Total Transactions**      | Watch only      | Description pending editorial review; the signal is live. |
        | **Under-Review Rate**       | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Authorisation Success Rate** | Alert band 97 / 92 | Description pending editorial review; the signal is live. |
        | **Stored-Token Health**        | Merchant rule      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **1 write** operations across report ingchargebacks, report ingconversiondetails, report ingpaymentbatchsummarys, report ingreports, riskdecisions, tsssearches on CyberSource. 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=cybersource)

    #### Ready to build your first CyberSource 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                       | Read operations | Write operations |
      | ------------------------------ | --------------- | ---------------- |
      | report ingchargebacks          | 1               | 0                |
      | report ingconversiondetails    | 1               | 0                |
      | report ingpaymentbatchsummarys | 1               | 0                |
      | report ingreports              | 1               | 0                |
      | riskdecisions                  | 1               | 0                |
      | tsssearches                    | 0               | 1                |
      | tsstransactions                | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Databricks on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/databricks

Monitor Databricks health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Databricks health, cost and reliability signals, and catch incidents and runaway spend early.

[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=databricks)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Clusters**                   | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Active SQL Sessions**               | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Active SQL Warehouses**             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg DBU per Job Run**               | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **DBU Burn +50% Week-over-Week**      | Merchant rule      | Alerts for DBU Burn +50% Week-over-Week.                                                                                                               |
        | **DBU Burned (24h)**                  | Merchant rule      | From billable usage API. Databricks-defining cost metric. Includes job compute + SQL warehouse + interactive.                                          |
        | **DBU by Cluster (7d)**               | Watch only         | DBU by Cluster (7d).                                                                                                                                   |
        | **Databricks Health Score**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Idle Cluster DBU Wasted (24h)**     | Merchant rule      | DBU spent while cluster had no active jobs. Auto-termination tuning signal.                                                                            |
        | **Last Delta Lake Vacuum / Optimize** | Alert band 24 / 72 | Delta Lake doesn't have traditional backup , Time Travel (default 7d retention) + table OPTIMIZE/VACUUM stand in. This tracks last successful OPTIMIZE |
        | **Long-Running Jobs (>1h)**           | Merchant rule      | Jobs still running past expected duration , common cost-runaway pattern.                                                                               |
        | **Pipeline Lag (since last success)** | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                                                              |
        | **SQL Queries per Hour (live)**       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **SQL Warehouse Saturation %**        | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                                                              |
        | **Top 10 Failing Workflows (7d)**     | Watch only         | Top 10 Failing Workflows (7d), broken down by row.                                                                                                     |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                                      | Alert behaviour | What it tracks                                                                                                |
        | ------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------- |
        | **DBU Burn vs Ecom Order Volume**           | Merchant rule   | Databricks-distinctive XC , DBU burn should track ecom volume. Divergence = inefficient pipelines.            |
        | **DLT Pipeline Status Distribution**        | Watch only      | Running / Idle / Failed / Stopped , from /pipelines/list.                                                     |
        | **Databricks SQL Spike vs Ecom Order Rate** | Merchant rule   | Description pending editorial review; the signal is live.                                                     |
        | **Failed Job Burst (>5 failures in 1h)**    | Merchant rule   | Databricks-distinctive , pipeline failures cascade fast across dependent jobs.                                |
        | **Failed Jobs (24h)**                       | Merchant rule   | result\_state=FAILED OR TIMEDOUT. Triage queue.                                                               |
        | **Job Success Rate (24h)**                  | Merchant rule   | From /jobs/runs/list , Databricks-distinctive defining metric. Failed scheduled runs = data pipelines broken. |
        | **Pipeline Lag vs Ecom Order Flow**         | Merchant rule   | Description pending editorial review; the signal is live.                                                     |
        | **Slow SQL Queries During Checkout Window** | Merchant rule   | Slow SQL Queries During Checkout Window, broken down by row.                                                  |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                            | Alert behaviour      | What it tracks                                                                           |
        | --------------------------------- | -------------------- | ---------------------------------------------------------------------------------------- |
        | **Avg Cluster CPU Utilisation %** | Merchant rule        | Databricks-distinctive , drives right-sizing decisions for cost + performance.           |
        | **SQL Query Latency p50 (ms)**    | Watch only           | Description pending editorial review; the signal is live.                                |
        | **SQL Query Latency p95 (ms)**    | Alert band 50 / 200  | Lakehouse SQL p95 measured in seconds typically , threshold reflects warehouse workload. |
        | **SQL Query Latency p99 (ms)**    | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                |
        | **Slow-Query Rate %**             | Alert band 1 / 5     | Description pending editorial review; the signal is live.                                |
        | **Top 10 Slowest SQL Queries**    | Watch only           | Top 10 Slowest SQL Queries, broken down by row.                                          |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                     | Alert behaviour    | What it tracks                                            |
        | ------------------------------------------ | ------------------ | --------------------------------------------------------- |
        | **SQL Query Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. |
        | **SQL Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for SQL Query Error Rate Spike (>1% in 5m).        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across billableusagedownloads, clusterlists, jobrunlists, pipelines, sqlhistoryquerys, sqlwarehous on Databricks. 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=databricks)

    #### Ready to build your first Databricks 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | billableusagedownloads | 1               | 0                |
      | clusterlists           | 1               | 0                |
      | jobrunlists            | 1               | 0                |
      | pipelines              | 1               | 0                |
      | sqlhistoryquerys       | 1               | 0                |
      | sqlwarehous            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Datadog on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/datadog

Monitor Datadog health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Datadog health, cost and reliability signals, and catch incidents and runaway spend early.

[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=datadog)

<CardGroup>
  <Card title="62">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="1,757">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (62)">
    ### Monitor performance

    62 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Control risk and change (24 signals)">
        | Signal                                | Alert behaviour      | What it tracks                                                                                      |
        | ------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------- |
        | **5xx Response Rate**                 | Alert band 0.5 / 2   | Description pending editorial review; the signal is live.                                           |
        | **API Monitor Failures (24h)**        | Merchant rule        | Description pending editorial review; the signal is live.                                           |
        | **Apdex / Error-Rate Anomaly**        | Alert band 0 / 1     | Description pending editorial review; the signal is live.                                           |
        | **Container Restart Storm**           | Merchant rule        | Container Restart Storm over time.                                                                  |
        | **Error Budget Remaining**            | Alert band 50 / 20   | Description pending editorial review; the signal is live.                                           |
        | **Error Rate**                        | Alert band 0.5 / 2   | Description pending editorial review; the signal is live.                                           |
        | **Error Spike Detection**             | Merchant rule        | Error Spike Detection over time.                                                                    |
        | **Error-level Log Rate**              | Alert band 2 / 10    | Error-level Log Rate over time.                                                                     |
        | **Errors by Endpoint**                | Merchant rule        | Errors by Endpoint.                                                                                 |
        | **Fatal-level Log Volume**            | Alert band 0 / 100   | Fatal-level Log Volume over time.                                                                   |
        | **High-Cardinality Tag Warnings**     | Merchant rule        | High-cardinality tags blow up custom-metric counts and cost - warning surface from /api/v1/metrics. |
        | **Host Uptime Distribution**          | Watch only           | Description pending editorial review; the signal is live.                                           |
        | **Hosts with CPU Saturation >85%**    | Alert band 0 / 4     | Description pending editorial review; the signal is live.                                           |
        | **Hosts with Disk >90% Full**         | Alert band 0 / 1     | Description pending editorial review; the signal is live.                                           |
        | **Hosts with Memory Saturation >85%** | Alert band 0 / 4     | Description pending editorial review; the signal is live.                                           |
        | **Hosts with Stale Agent (>24h)**     | Alert band 0 / 1     | Description pending editorial review; the signal is live.                                           |
        | **Infrastructure Spend Trend**        | Merchant rule        | Description pending editorial review; the signal is live.                                           |
        | **JS Errors / Session**               | Alert band 0.1 / 0.5 | Description pending editorial review; the signal is live.                                           |
        | **Monitor Coverage by Service**       | Merchant rule        | % of services with at least one error-rate + latency monitor wired up. Coverage gaps = blind spots. |
        | **New Error Types (last 24h)**        | Alert band 0 / 1     | Errors that didn't appear in the prior 7 days - highest-signal regression.                          |
        | **Reporting Hosts**                   | Merchant rule        | Description pending editorial review; the signal is live.                                           |
        | **SLO Compliance (current period)**   | Merchant rule        | SLO Compliance (current period), compared across items.                                             |
        | **Top Error Log Patterns**            | Watch only           | Top Error Log Patterns, broken down by row.                                                         |
        | **Top Error Messages**                | Merchant rule        | Top Error Messages, broken down by row.                                                             |
      </Accordion>

      <Accordion title="Run operations (22 signals)">
        | Signal                                    | Alert behaviour        | What it tracks                                                                                           |
        | ----------------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------- |
        | **Active Incidents**                      | Alert band 0 / 1       | Description pending editorial review; the signal is live.                                                |
        | **Alerts Summary**                        | Alert band 0 / 6       | Alerts for Alerts Summary.                                                                               |
        | **Browser Test Latency p95**              | Alert band 2000 / 5000 | Browser Test Latency p95 over time.                                                                      |
        | **Currently Triggered Monitors**          | Alert band 0 / 1       | Alerts for Currently Triggered Monitors.                                                                 |
        | **Custom Metric Quota Used**              | Alert band 50 / 85     | Description pending editorial review; the signal is live.                                                |
        | **Days Until SLO Breach (forecast)**      | Alert band 14 / 6      | Description pending editorial review; the signal is live.                                                |
        | **Ingestion Freshness (sec)**             | Alert band 60 / 300    | Description pending editorial review; the signal is live.                                                |
        | **Log Indexing Cost Trend**               | Merchant rule          | Description pending editorial review; the signal is live.                                                |
        | **Log Indexing Volume Trend**             | Merchant rule          | Description pending editorial review; the signal is live.                                                |
        | **Log Volume (events/sec)**               | Merchant rule          | Volume spikes mean either real activity or runaway logging - both deserve attention.                     |
        | **Mobile vs Desktop p95**                 | Watch only             | Mobile vs Desktop p95, compared across items.                                                            |
        | **Monitors Without Notification Channel** | Alert band 0 / 1       | Monitors that fire silently - when they trigger, nobody knows. Highest-leverage fix in this section.     |
        | **Monitors in 'No Data' State**           | Alert band 0 / 1       | Lost telemetry - agent down, metric renamed, integration broken. Looks healthy but isn't.                |
        | **Operational Health Score**              | Alert band 90 / 70     | Composite - apdex × inverse error-rate × inverse incident-count × SLO compliance. The CXO single-number. |
        | **Page Load p95**                         | Alert band 2500 / 4000 | Description pending editorial review; the signal is live.                                                |
        | **SLO Burn Rate (1h)**                    | Alert band 1 / 14.4    | Multi-window burn-rate alerting - anything above 14.4× will eat the monthly budget in a day.             |
        | **Slowest Pages by Visits**               | Alert band 2500 / 5000 | Slowest Pages by Visits.                                                                                 |
        | **Sustained Threshold Breaches**          | Alert band 0 / 1       | Alerts for Sustained Threshold Breaches.                                                                 |
        | **Synthetic Uptime**                      | Alert band 99.9 / 99.5 | Description pending editorial review; the signal is live.                                                |
        | **Throughput (req/s)**                    | Alert band 0 / -10     | Description pending editorial review; the signal is live.                                                |
        | **Uptime by Region**                      | Merchant rule          | Uptime by Region.                                                                                        |
        | **p95 Response Time**                     | Alert band 200 / 1000  | Description pending editorial review; the signal is live.                                                |
      </Accordion>

      <Accordion title="Customer experience (8 signals)">
        | Signal                         | Alert behaviour       | What it tracks                                                                                                                                          |
        | ------------------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Apdex Score**                | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live.                                                                                               |
        | **Apdex Trend**                | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live.                                                                                               |
        | **Database Query Latency p95** | Alert band 50 / 200   | Database Query Latency p95 over time.                                                                                                                   |
        | **Deploy Markers vs Latency**  | Watch only            | Latency line with deploy events overlaid - turns 'why is it slow?' into 'which deploy did it'.                                                          |
        | **Error Rate by Service**      | Alert band 0.5 / 2    | Error Rate by Service.                                                                                                                                  |
        | **Latency & APM Monitors**     | Merchant rule         | Monitors tagged latency / apm and how many are firing. Per-endpoint p95 slicing needs a by-resource\_name query the engine does not run, so this surfac |
        | **Throughput by Service**      | Watch only            | Throughput by Service.                                                                                                                                  |
        | **p99 Response Time**          | Alert band 200 / 1000 | Description pending editorial review; the signal is live.                                                                                               |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                    | Alert behaviour | What it tracks                                                                                                                          |
        | ----------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Cart Abandonment During 5xx Spikes**    | Merchant rule   | Cart Abandonment During 5xx Spikes over time.                                                                                           |
        | **Checkout Service Health × Sales**       | Merchant rule   | Latency on the checkout service overlaid with order volume - when checkout slows, sales follow.                                         |
        | **Conversion Drop During Incidents**      | Merchant rule   | Conversion Drop During Incidents, compared across items.                                                                                |
        | **Critical-Path Tests Status**            | Merchant rule   | Login, browse, add-to-cart, checkout - the customer journey synthetics. Any failure = revenue at risk.                                  |
        | **Revenue Lost / Min (active incidents)** | Merchant rule   | Live \$/min loss while incidents are open. Stops being academic and starts being the COO's number.                                      |
        | **Revenue at Risk (live)**                | Merchant rule   | Datadog state × commerce-sibling baseline = \$/hour at risk while the incident is open. The single most-valuable card in this manifest. |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                              | Alert behaviour  | What it tracks                                                                               |
        | ----------------------------------- | ---------------- | -------------------------------------------------------------------------------------------- |
        | **Frustrated User Sessions**        | Alert band 1 / 5 | Sessions where load >4s or rage-click detected - proxy for conversion drop.                  |
        | **Recently Flapped Monitors (24h)** | Alert band 0 / 4 | Monitors flipping repeatedly = noisy / threshold wrong / real instability - all need triage. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **752 read** and **1,005 write** operations across apikeys, downtimes, users, applicationkeys, dashboards, appbuilderapps on Datadog. 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=datadog)

    #### Ready to build your first Datadog 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | apikeys                   | 4               | 6                |
      | downtimes                 | 4               | 6                |
      | users                     | 4               | 6                |
      | applicationkeys           | 4               | 5                |
      | dashboards                | 2               | 5                |
      | appbuilderapps            | 2               | 4                |
      | events                    | 4               | 2                |
      | integrationaweventbridges | 2               | 4                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Depop on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/depop

Monitor Depop listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Depop listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=depop)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Grow revenue (12 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                     |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Average Sale Price**              | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                          |
        | **Depop Fee % of Revenue**          | Alert band 12 / 18 | Description pending editorial review; the signal is live.                                          |
        | **Depop Shop Health Score**         | Merchant rule      | Composite: save-rate x follower-growth x listing-recency x rating-average.                         |
        | **Follower Count**                  | Merchant rule      | Depop algo favours follower-active sellers. Net-negative growth = systematic visibility loss.      |
        | **Listings with \<5 Hashtags**      | Alert band 10 / 25 | Depop discovery is hashtag-driven , listings with fewer than 5 hashtags miss most search surfaces. |
        | **Net Revenue (after Depop fees)**  | Alert band 0 / -5  | Net of Depop's 10% selling fee + 4.3%+£0.30 payment processing.                                    |
        | **Orders**                          | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Revenue Over Time**               | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                          |
        | **Save Rate (per 1000 views)**      | Merchant rule      | Depop's primary engagement signal. Below 2/1000 = photo or tag misalignment with target aesthetic. |
        | **Stale Listings (>30d no update)** | Merchant rule      | Depop recency boost is short , relist or refresh to recover search visibility.                     |
        | **Top Listings by Revenue**         | Watch only         | Top Listings by Revenue.                                                                           |
        | **Total Revenue**                   | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                          |
      </Accordion>

      <Accordion title="Run operations (12 signals)">
        | Signal                                              | Alert behaviour    | What it tracks                                                                                                                                         |
        | --------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country**                                  | Watch only         | AOV by Country.                                                                                                                                        |
        | **Average Rating**                                  | Alert band 95 / 85 | Description pending editorial review; the signal is live.                                                                                              |
        | **Buyer Messages Unread**                           | Watch only         | Buyer Messages Unread as exposed by the Depop integration. The metric is computed from the latest available data and refreshed on the standard data re |
        | **Days Since Last Payout**                          | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments**                                  | Merchant rule      | Alerts for Late Shipments.                                                                                                                             |
        | **Marketplace Fees Paid**                           | Watch only         | Marketplace Fees Paid as exposed by the Depop integration. The metric is computed from the latest available data and refreshed on the standard data re |
        | **On-Time Shipping Rate**                           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Orders / Day**                                    | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country**                               | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                                 | Watch only         | Pending Payouts as exposed by the Depop integration. The metric is computed from the latest available data and refreshed on the standard data refresh  |
        | **Pending Shipment**                                | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Save-Rate / Follower / Rating Threshold Crossed** | Alert band 95 / 85 | Alerts for Save-Rate / Follower / Rating Threshold Crossed.                                                                                            |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                               | Alert behaviour   | What it tracks                                                        |
        | ---------------------------------------------------- | ----------------- | --------------------------------------------------------------------- |
        | **Active Depop Listings for Sold-Elsewhere Items**   | Alert band 0 / 5  | Description pending editorial review; the signal is live.             |
        | **Dispute / Refund Rate**                            | Alert band 5 / 15 | Description pending editorial review; the signal is live.             |
        | **Listings Drifting from BC**                        | Alert band 5 / 50 | Listings Drifting from BC, broken down by row.                        |
        | **Listings Failing Feedonomics Validation**          | Alert band 2 / 5  | Description pending editorial review; the signal is live.             |
        | **Revenue at Risk**                                  | Merchant rule     | Description pending editorial review; the signal is live.             |
        | **Same Item Priced Differently vs Mercari / Vinted** | Merchant rule     | Same Item Priced Differently vs Mercari / Vinted, broken down by row. |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                          |
        | -------------------------------- | ------------------ | ----------------------------------------------------------------------- |
        | **Active Listings**              | Merchant rule      | Description pending editorial review; the signal is live.               |
        | **Depop Removed Listings (24h)** | Alert band 5 / 50  | Alerts for Depop Removed Listings (24h).                                |
        | **Listings with \<3 Photos**     | Alert band 10 / 25 | Photo aesthetics drive save-rate. Single-photo listings convert poorly. |
        | **Total Listings**               | Watch only         | Description pending editorial review; the signal is live.               |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **1 write** operations across oauthtokens, orders, shops, shopproducts on Depop. 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=depop)

    #### Ready to build your first Depop 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.

    <Accordion title="Browse the operations you can build with">
      | Resource     | Read operations | Write operations |
      | ------------ | --------------- | ---------------- |
      | oauthtokens  | 0               | 1                |
      | orders       | 1               | 0                |
      | shops        | 1               | 0                |
      | shopproducts | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Deutsche Post / DHL Parcel on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/deutsche-post

Monitor Deutsche Post / DHL Parcel delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Deutsche Post / DHL Parcel delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=deutsche-post)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (24 signals)">
        | Signal                                                | Alert behaviour  | What it tracks                                                                                                                                         |
        | ----------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Error Rate**                                    | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Shipping Cost**                                 | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Claim Value (open)**                                | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Cost Per Shipment Trend**                           | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Cost by Zone**                                      | Watch only       | Cost by Zone.                                                                                                                                          |
        | **Cost per Parcel by Zone (EUR)**                     | Watch only       | DHL Parcel zone structure: Inland (DE) / EU (EU member states) / Welt (rest of world). Annual rate review typically Jan 1st.                           |
        | **Days to Token Expiry**                              | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Dispatch SLA Breach on N Orders Today**             | Merchant rule    | Alerts for Dispatch SLA Breach on N Orders Today.                                                                                                      |
        | **Exception Rate**                                    | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                              |
        | **High-Cost Shipment Outliers**                       | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                                       |
        | **Label / Retouren-Etikett Print Failures Spike**     | Alert band 0 / 5 | Alerts for Label / Retouren-Etikett Print Failures Spike.                                                                                              |
        | **Label Generation Success**                          | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **OTD by Route**                                      | Watch only       | OTD by Route.                                                                                                                                          |
        | **Open Claims**                                       | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Packstation Delivery Rate**                         | Watch only       | % of German parcels delivered via DHL's Packstation locker network , higher first-attempt-delivery success vs home delivery.                           |
        | **Retouren-Etikett Generation Failure Rate**          | Alert band 1 / 2 | % of /parcel/de/shipping/v2/returns calls failing. Spike = blocks German Widerruf compliance, customers can't return goods easily.                     |
        | **Retouren-Etikett Volume (German Widerruf returns)** | Watch only       | Daily volume of pre-paid German return labels generated. German law (BGB §312g) requires merchants to provide these for B2C orders.                    |
        | **Returned to Sender**                                | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Returns Within 14-day Widerruf Window**             | Watch only       | Returns initiated within the German 14-day legal Widerruf window. Helps distinguish Widerruf returns from defect (Mangel) or wrong-item (Falschlieferu |
        | **Route Volume Concentration**                        | Watch only       | Route Volume Concentration, compared across items.                                                                                                     |
        | **Shipments**                                         | Merchant rule    | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments Over Time**                               | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments by Destination**                          | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments by Service**                              | Watch only       | Shipments by Service.                                                                                                                                  |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                       | Alert behaviour   | What it tracks                                                                                                                     |
        | ------------------------------------------------------------ | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
        | **DHL Parcel Cost vs DPD / PostNord by Zone**                | Merchant rule     | DPD / Hermes / PostNord compete with DHL Parcel in German market , surface zones where alternatives are cheaper for renegotiation. |
        | **Failed Deliveries**                                        | Watch only        | Description pending editorial review; the signal is live.                                                                          |
        | **Orders with DHL Dispatch SLA Missed**                      | Merchant rule     | Description pending editorial review; the signal is live.                                                                          |
        | **Return Rate by DHL Product Code**                          | Merchant rule     | Description pending editorial review; the signal is live.                                                                          |
        | **Shipments with Tracking-Event Gap (24h domestic / 3d EU)** | Alert band 0 / 10 | Shipments with Tracking-Event Gap (24h domestic / 3d EU), broken down by row.                                                      |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                               |
        | ------------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**                            | Watch only         | Description pending editorial review; the signal is live.                                                                    |
        | **EU Cross-Border Customs Clearance Rate (\<3d)** | Merchant rule      | % of EU cross-border parcels (DE to AT/CH) clearing CN23 customs within 3 days. Below 80% = CN23 paperwork generation issue. |
        | **First-Attempt Delivery Rate**                   | Watch only         | Description pending editorial review; the signal is live.                                                                    |
        | **Late Shipments**                                | Watch only         | Description pending editorial review; the signal is live.                                                                    |
        | **On-Time Delivery Rate**                         | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                    |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                 | Alert behaviour | What it tracks                                 |
        | -------------------------------------- | --------------- | ---------------------------------------------- |
        | **DHL Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for DHL Tracking API Unavailable / 5xx. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                                     | Alert behaviour | What it tracks                                                                                                              |
        | ------------------------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------------------- |
        | **DHL Express vs DHL Parcel Volume Split** | Watch only      | When the merchant also uses DHL Express (separate API + product), this shows the volume mix to inform contract negotiation. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **3 write** operations across authtokens, parceldeshippingorders, parceldeshippingreturns, parceldetrackingshipments on Deutsche Post / DHL Parcel. 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=deutsche-post)

    #### Ready to build your first Deutsche Post / DHL Parcel 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | authtokens                | 0               | 1                |
      | parceldeshippingorders    | 0               | 1                |
      | parceldeshippingreturns   | 0               | 1                |
      | parceldetrackingshipments | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# DHL InExpress on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/dhl-inexpress

Monitor DHL InExpress delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor DHL InExpress delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=dhl-inexpress)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                                                                                                                        |
        | ------------------------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live.                                                                                             |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                                                                                                                         |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Duty-Billing Mismatch Rate**  | Merchant rule    | % of shipments where DHL's duty-billing line differs from the merchant-quoted figure (over- or under-charged customer). Direct cash-and-trust signal. |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                             |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                                      |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **OTD by Route**                | Watch only       | OTD by Route.                                                                                                                                         |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.                                                                                                    |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live.                                                                                             |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live.                                                                                             |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                                                                                                                 |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **International Express OTD**   | Alert band 95 / 90 | International Express OTD - the DHL flagship service promise. Customs friction is the typical breakage point. |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                     |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                         | Alert behaviour | What it tracks                                                                                                                                         |
        | ------------------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Customs Dwell Time by Lane** | Merchant rule   | Per-lane customs dwell time (hours). Surfaces specific origin/destination combos where commercial-invoice or HS-code data is causing repeated friction |
        | **Failed Deliveries**          | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **1 write** operations across tbds on DHL InExpress. 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=dhl-inexpress)

    #### Ready to build your first DHL InExpress 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 2               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# DigitalOcean on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/digitalocean

Monitor DigitalOcean health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor DigitalOcean health, cost and reliability signals, and catch incidents and runaway spend early.

[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=digitalocean)

<CardGroup>
  <Card title="28">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (28)">
    ### Monitor performance

    28 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                                                                                                                          |
        | ---------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Account Balance**                | Watch only         | account\_balance field from GET /v2/customers/my/balance (a negative value means credit owed by the customer, positive means credit remaining).         |
        | **Account Status Alert**           | Watch only         | account.status field from GET /v2/account; flags when not 'active' (e.g. 'warning' or 'locked', which blocks provisioning and can indicate a billing o  |
        | **Active Droplets**                | Watch only         | Count of droplets\[] with status == active from GET /v2/droplets.                                                                                       |
        | **Billing Events (30d)**           | Watch only         | Count of billing\_history\[] entries with date >= 30 days ago from GET /v2/customers/my/billing\_history.                                               |
        | **Block Storage Volumes**          | Watch only         | Count of volumes\[] from GET /v2/volumes.                                                                                                               |
        | **Databases by Engine**            | Watch only         | databases\[] grouped by engine from GET /v2/databases.                                                                                                  |
        | **Kubernetes Clusters**            | Watch only         | Count of kubernetes\_clusters\[] from GET /v2/kubernetes/clusters.                                                                                      |
        | **Kubernetes Clusters by Version** | Watch only         | kubernetes\_clusters\[] grouped by version from GET /v2/kubernetes/clusters.                                                                            |
        | **Load Balancers Total**           | Watch only         | Count of load\_balancers\[] from GET /v2/load\_balancers.                                                                                               |
        | **Managed Databases**              | Watch only         | Count of databases\[] from GET /v2/databases.                                                                                                           |
        | **Month-to-Date Spend**            | Watch only         | month\_to\_date\_balance field from GET /v2/customers/my/balance (spend accrued so far this billing cycle).                                             |
        | **Month-to-Date Usage**            | Watch only         | month\_to\_date\_usage field from GET /v2/customers/my/balance.                                                                                         |
        | **Most Recent Invoice**            | Watch only         | amount field of the most recent entry in invoices\[] (sorted by invoice\_period desc) from GET /v2/customers/my/invoices.                               |
        | **Previous Invoice**               | Watch only         | amount field of the second-most-recent entry in invoices\[] from GET /v2/customers/my/invoices; the comparison base for the spend trend.                |
        | **Spend Spike Alert**              | Alert band 10 / 50 | Same calculation as dig\_spend\_trend (invoices\[] latest vs prior amount); duplicated into the Alerts section so it fires as a tunable Alert Rule.     |
        | **Spend Trend vs Last Cycle**      | Alert band 10 / 50 | Percent change between the two most recent entries in invoices\[] (sorted by invoice\_period desc) from GET /v2/customers/my/invoices: (latest amount - |
        | **Total Database Nodes**           | Watch only         | SUM(num\_nodes) across databases\[] from GET /v2/databases.                                                                                             |
        | **Total Volume Size (GB)**         | Watch only         | SUM(size\_gigabytes) across volumes\[] from GET /v2/volumes.                                                                                            |
      </Accordion>

      <Accordion title="Control risk and change (8 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                                                          |
        | --------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Cloud Health Score**            | Alert band 90 / 70 | 0-100 composite over whatever is readable: token valid (100) + account.status == active (100/0) from GET /v2/account + pct of droplets\[] with status = |
        | **Droplets Total**                | Watch only         | Count of droplets\[] from GET /v2/droplets.                                                                                                             |
        | **Droplets by Region**            | Watch only         | droplets\[] grouped by region.slug from GET /v2/droplets.                                                                                               |
        | **Droplets by Size**              | Watch only         | droplets\[] grouped by size\_slug from GET /v2/droplets.                                                                                                |
        | **Load Balancers Not Active**     | Watch only         | Count of load\_balancers\[] with status != active (e.g. new or errored) from GET /v2/load\_balancers.                                                   |
        | **Locked Droplets**               | Watch only         | Count of droplets\[] with locked == true from GET /v2/droplets; a locked droplet cannot take new actions (resize, power-cycle) until the current action |
        | **Total Memory Provisioned (GB)** | Watch only         | SUM(memory) across droplets\[] from GET /v2/droplets, converted from MB to GB (memory / 1024).                                                          |
        | **Total vCPUs Provisioned**       | Watch only         | SUM(vcpus) across droplets\[] from GET /v2/droplets.                                                                                                    |
      </Accordion>

      <Accordion title="Catalogue quality (2 signals)">
        | Signal                                   | Alert behaviour | What it tracks                                                                                                                           |
        | ---------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Cost by Product (Latest Invoice)**     | Watch only      | amount from invoice\_items\[] grouped by product for the most recent invoice\_uuid, via GET /v2/customers/my/invoices/; top 10 products. |
        | **Top Product by Cost (Latest Invoice)** | Watch only      | The single largest product by amount from the most recent invoice's invoice\_items\[]; the product name is the card detail.              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **10 read** and **0 write** operations across customer myinvoices, accounts, customer mybalances, customer mybillinghistorys, databas, droplets on DigitalOcean. 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=digitalocean)

    #### Ready to build your first DigitalOcean 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | customer myinvoices        | 2               | 0                |
      | accounts                   | 1               | 0                |
      | customer mybalances        | 1               | 0                |
      | customer mybillinghistorys | 1               | 0                |
      | databas                    | 1               | 0                |
      | droplets                   | 1               | 0                |
      | kuberneteclusters          | 1               | 0                |
      | loadbalancers              | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Discord on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/discord

Monitor Discord performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Discord performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=discord)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Discord yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **2 write** operations across channelmessages, webhooks, channels, guildchannels on Discord. 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=discord)

    #### Ready to build your first Discord 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | channelmessages | 1               | 1                |
      | webhooks        | 1               | 1                |
      | channels        | 1               | 0                |
      | guildchannels   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Dotdigital on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/dotdigital

Monitor email revenue and deliverability for Dotdigital, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Dotdigital, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=dotdigital)

<CardGroup>
  <Card title="16">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="29">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (16)">
    ### Monitor performance

    16 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (9 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                      |
        | ------------------------- | ------------------ | --------------------------------------------------- |
        | **Campaign Performance**  | Watch only         | Top campaigns ranked by unique opens.               |
        | **Campaign Status**       | Watch only         | Campaigns grouped by status.                        |
        | **Email Click Rate**      | Alert band 3 / 1   | Aggregate email click rate across recent campaigns. |
        | **Email Open Rate**       | Alert band 25 / 15 | Aggregate email open rate across recent campaigns.  |
        | **Email Sends Over Time** | Watch only         | Email send volume over time.                        |
        | **Open Rate Trend**       | Watch only         | Open rate trend across recent campaigns.            |
        | **Subscriber Growth**     | Watch only         | Subscriber growth over time.                        |
        | **Total Campaigns**       | Watch only         | Total number of email campaigns.                    |
        | **Unsubscribe Rate**      | Alert band 0.3 / 1 | Aggregate unsubscribe rate across recent campaigns. |
      </Accordion>

      <Accordion title="Run operations (6 signals)">
        | Signal                    | Alert behaviour | What it tracks                                 |
        | ------------------------- | --------------- | ---------------------------------------------- |
        | **Active Programs**       | Watch only      | Number of active automation programs.          |
        | **Address Books**         | Watch only      | Total number of address books.                 |
        | **Automation Programs**   | Watch only      | Total automation programs.                     |
        | **Largest Address Books** | Watch only      | Largest address books ranked by contact count. |
        | **Program Status**        | Watch only      | Automation programs grouped by status.         |
        | **Total Contacts**        | Watch only      | Total contacts across all address books.       |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal          | Alert behaviour  | What it tracks                                 |
        | --------------- | ---------------- | ---------------------------------------------- |
        | **Bounce Rate** | Alert band 2 / 5 | Aggregate bounce rate across recent campaigns. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="High Bounce Rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DD01`
      </Accordion>

      <Accordion title="High Unsubscribe Rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        A rising unsubscribe rate shrinks the reachable audience and usually signals frequency or relevance problems; every lost subscriber removes future campaign and flow revenue.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DD02`
      </Accordion>

      <Accordion title="Inactive Programs">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DD04, DD05`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Low Click Rate">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Opens without clicks mean the content is not converting attention into store visits; the list is paying attention but the message is not earning the click.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DD06`
      </Accordion>

      <Accordion title="Low Open Rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        Consistently low opens mean subject lines, send times or list quality are wasting sends, and engagement-based inbox placement then makes future sends perform even worse.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DD03`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **13 read** and **16 write** operations across contacts, insightdataaccounts, insightdatacontacts, insightdatacollections, contactdeletes, contactimports on Dotdigital. 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=dotdigital)

    #### Ready to build your first Dotdigital 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | contacts               | 2               | 4                |
      | insightdataaccounts    | 3               | 2                |
      | insightdatacontacts    | 2               | 2                |
      | insightdatacollections | 1               | 2                |
      | contactdeletes         | 1               | 1                |
      | contactimports         | 1               | 1                |
      | insightdataimports     | 1               | 1                |
      | insightdataasyncs      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# DPD on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/dpd

Monitor DPD delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor DPD delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=dpd)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                            |
        | ------------------------------- | ---------------- | --------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live. |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                             |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live. |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.          |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live. |
        | **OTD by Route**                | Watch only       | OTD by Route.                                             |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live. |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.        |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                     |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Transit (days)**                      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **First-Attempt Delivery Rate**             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments**                          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Time Delivery Rate**                   | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                              |
        | **Predict Slot Accuracy (30-min / 1-hour)** | Alert band 90 / 75 | DPD's flagship 'Predict' promise - did the parcel arrive in the customer-notified 30-min / 1-hour window? Below 92% means the brand promise is breakin |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                      |
        | ---------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **DPD OTD by Sales Channel**             | Alert band 95 / 90 | Per-channel DPD OTD - which sales surface is suffering most.                                                                                        |
        | **Failed Deliveries**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                           |
        | **UK -> EU Cross-Border Exception Rate** | Merchant rule      | Post-Brexit cross-border lanes (UK -> EU mainland) fail in distinctive ways - customs documentation, IOSS / VAT, refused delivery. Surfaces specifi |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **1 write** operations across tbds on DPD. 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=dpd)

    #### Ready to build your first DPD 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 2               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# DPDLocal on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/dpdlocal

Monitor DPDLocal delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor DPDLocal delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=dpdlocal)

<CardGroup>
  <Card title="51">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (51)">
    ### Monitor performance

    51 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (32 signals)">
        | Signal                                  | Alert behaviour       | What it tracks                                                                                                                                            |
        | --------------------------------------- | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**                      | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Ageing Claim Watchlist**              | Merchant rule         | Open claims ageing past 7 days, sorted by value. Each row is cash trapped + a customer not chased.                                                        |
        | **Avg Shipping Cost**                   | Merchant rule         | Description pending editorial review; the signal is live.                                                                                                 |
        | **Claim Resolution Time (median days)** | Merchant rule         | Median days from claim opened to settled / denied. Above 14 days = the carrier is ageing your cash.                                                       |
        | **Claim Value (open)**                  | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Collections Booked**                  | Watch only            | Trend of collections booked - sets capacity-planning context for the warehouse.                                                                           |
        | **Cost Per Shipment Trend**             | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Cost by Zone**                        | Watch only            | Cost by Zone.                                                                                                                                             |
        | **DPDLocal Health Score**               | Alert band 90 / 70    | Composite - OTD x first-attempt x inverse exception x inverse open-claim age. The single number an ops manager checks at 9am Monday.                      |
        | **Days to Token Expiry**                | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Exception Rate**                      | Alert band 2 / 5      | Description pending editorial review; the signal is live.                                                                                                 |
        | **Exception Rate Spike**                | Alert band 0 / 10     | Exception count spike vs trailing 30-day baseline. Catches sudden carrier-side breakdowns (depot fire, weather, IT outage).                               |
        | **Exception Reasons (top 10)**          | Watch only            | Top 10 exception reasons by volume - feeds operational triage (refused vs damaged vs missing). Shifts in the mix surface emerging issues.                 |
        | **High-Cost Shipment Outliers**         | Watch only            | High-Cost Shipment Outliers, broken down by row.                                                                                                          |
        | **Label Generation Success**            | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **OTD SLA Breach**                      | Merchant rule         | Live SLA-breach indicator on the Nerve Centre - immediate ops trigger; archetype hero dpd\_otd\_rate covers the 30D rollup.                               |
        | **OTD Today**                           | Alert band 95 / 90    | Today's on-time delivery rate vs DPDLocal's \~98% contracted SLA. Drives the Monday-9am question; archetype dpd\_otd\_rate is the canonical hero on the 3 |
        | **OTD by Route**                        | Watch only            | OTD by Route.                                                                                                                                             |
        | **OTD by UK Region**                    | Alert band 95 / 90    | OTD broken down by UK postcode area (London, North-West, Scotland, NI, etc.). Identifies regional carrier weakness.                                       |
        | **Open Claim Value**                    | Alert band 100 / 1000 | Total monetary value of unsettled claims. Direct cash-flow signal for finance.                                                                            |
        | **Open Claims**                         | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Parcels In Flight**                   | Watch only            | Live count of shipments not yet delivered or returned. Sets context for every delay alert.                                                                |
        | **Premium-Service Uplift vs Standard**  | Merchant rule         | Marginal cost of paying for Predict / Sunday / EU vs standard NextDay. >40% uplift may not be justified by the OTD lift; finance trigger.                 |
        | **Returned to Sender**                  | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Route Degradation Alerts**            | Merchant rule         | UK postcode-area routes whose OTD dropped >5 percentage points week-over-week. Early warning of carrier-side regional issues.                             |
        | **Route Volume Concentration**          | Merchant rule         | Route Volume Concentration, compared across items.                                                                                                        |
        | **Shipments**                           | Merchant rule         | Description pending editorial review; the signal is live.                                                                                                 |
        | **Shipments Over Time**                 | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Shipments by Destination**            | Watch only            | Description pending editorial review; the signal is live.                                                                                                 |
        | **Shipments by Service**                | Watch only            | Shipments by Service.                                                                                                                                     |
        | **Shipments by Service Code**           | Watch only            | How merchant volume splits across DPDLocal service codes (NextDay, Predict, Sunday, EU). Drives carrier negotiation when imbalance emerges.               |
        | **UK Postcode Delivery Heatmap**        | Watch only            | UK choropleth (postcode-area level) of shipment volume + median transit time. Surfaces hard-to-serve regions (Highlands, NI, IoM).                        |
      </Accordion>

      <Accordion title="Protect revenue (11 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                      |
        | ---------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **3PL vs Carrier Delay Attribution**     | Merchant rule      | For every late shipment - was the delay at the warehouse (ShipBob picked late) or on the carrier (DPDLocal in transit)? Hero.                       |
        | **Carrier OTD by Sales Channel**         | Alert band 95 / 90 | Joins shipment timing to commerce-sibling orders by order\_ref - which sales channel is suffering most from carrier delays. Hero.                   |
        | **Claim Value as % of DPDLocal Revenue** | Merchant rule      | Claim value as a fraction of DPDLocal-fulfilled revenue. >2% = the carrier is materially eroding margin; carrier-renegotiation trigger.             |
        | **Failed Deliveries**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                           |
        | **Failed Pickup Alerts**                 | Merchant rule      | Today's failed collections - each row is a missed-cutoff parcel that will arrive a day late.                                                        |
        | **Failed Pickup Rate**                   | Merchant rule      | % of scheduled collections where the driver failed to pick up. >3% = the carrier-side relationship is decaying; renegotiate or switch carriers on t |
        | **GeoSession Auth Risk**                 | Alert band 30 / 7  | GeoSession JWTs expire \~1h - count of /user/ re-auth failures in the last 24h. Persistent failures signal credential rotation needed.              |
        | **Late-Delivery Revenue at Risk**        | Merchant rule      | Estimated revenue exposed to refund / chargeback / churn from late deliveries this week. Hero - the finance-CFO wake-up call.                       |
        | **Open Claims Without Jira Ticket**      | Merchant rule      | Open DPDLocal claims that don't have a corresponding Jira ticket - direct CS coverage gap. Each row = a customer waiting and nobody is on it.       |
        | **Open Claims by Age**                   | Merchant rule      | Histogram of open claims by days-since-opened. Anything in the >14d bin = abandoned cash + customer goodwill at risk.                               |
        | **Sunday Delivery Success Rate**         | Alert band 95 / 85 | Sunday delivery is a paid premium - misses double-hurt (refund + customer trust).                                                                   |
      </Accordion>

      <Accordion title="Customer experience (7 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Transit (days)**                      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Delivery Experience Score**               | Alert band 90 / 70 | Composite from DPD app interactions (rate-your-driver feedback). 5-point scale; below 4.0 = flag the route.                                            |
        | **First-Attempt Delivery Rate**             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments**                          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments by Route**                 | Merchant rule      | Top routes by late-count this week - feeds the second 9am-Monday question (which route is dropping the ball).                                          |
        | **On-Time Delivery Rate**                   | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                              |
        | **Predict Slot Accuracy (30-min / 1-hour)** | Alert band 90 / 75 | DPD's flagship 'Predict' promise - did the parcel arrive in the customer-notified 30-min / 1-hour window? Below 92% means the brand promise is breakin |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                   | Alert behaviour | What it tracks                                                                                                  |
        | ------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------- |
        | **Cost by Service Code** | Watch only      | Spend split by DPDLocal service tier (Predict, NextDay, Sunday, EU, etc.) - feeds finance carrier-mix analysis. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **3 write** operations across shippingclaims, shippingcollections, shippingshipments, shippingservices, shippingtrackings, users on DPDLocal. 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=dpdlocal)

    #### Ready to build your first DPDLocal 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | shippingclaims      | 1               | 1                |
      | shippingcollections | 1               | 1                |
      | shippingshipments   | 1               | 1                |
      | shippingservices    | 1               | 0                |
      | shippingtrackings   | 1               | 0                |
      | users               | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Drip (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/drip-api

Monitor email revenue and deliverability for Drip (API), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Drip (API), catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=drip-api)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="11">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (13 signals)">
        | Signal                        | Alert behaviour     | What it tracks                                                                          |
        | ----------------------------- | ------------------- | --------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule       | Campaigns grouped by status (sent, draft, scheduled).                                   |
        | **Checkout-to-Order Rate**    | Alert band 80 / 60  | Share of started checkouts that became paid orders.                                     |
        | **Click-to-Open Rate**        | Alert band 10 / 3   | Truer engagement signal than open rate - proxy filtering does not pre-click.            |
        | **Conversion Rate**           | Alert band 3 / 1    | Orders as a share of emails sent. Ties send volume to revenue.                          |
        | **Email Click Rate**          | Alert band 3 / 1    | Share of delivered emails that earned a click. The clearest engagement signal.          |
        | **List Count**                | Merchant rule       | Number of audiences on the account.                                                     |
        | **Lists Overview**            | Merchant rule       | Every audience with its member count.                                                   |
        | **Revenue per Recipient**     | Alert band 1 / 0    | Revenue divided by emails sent. What each address is worth per send.                    |
        | **Revenue per Send**          | Merchant rule       | Revenue divided by emails sent, the efficiency of each send.                            |
        | **Segments Overview**         | Merchant rule       | Drip segments are saved campaign audiences. Below 3 signals an under-segmented account. |
        | **Top Lists by Name**         | Merchant rule       | Largest audiences by member count.                                                      |
        | **Total Revenue**             | Alert band 10 / -15 | Placed-order revenue Drip claims credit for in the conversion window. The hero number.  |
        | **Total Sends**               | Watch only          | Total emails sent across campaigns in the window.                                       |
      </Accordion>

      <Accordion title="Protect revenue (10 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                       |
        | -------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------- |
        | **Abandoned-Cart Recovery Value**      | Merchant rule        | Recovered revenue from the abandoned-cart workflow. Goes to zero if the workflow is drafted (DRI01). |
        | **Bounce Rate**                        | Alert band 2 / 5     | Bounce >5% trips ISP throttling. Audit DRI02 fires here.                                             |
        | **Delivery Rate**                      | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                            |
        | **Email Health KPIs**                  | Merchant rule        | Delivered, bounced and unsubscribed at a glance, your deliverability vitals.                         |
        | **Email Share of Total Store Revenue** | Merchant rule        | Healthy DTC ranges 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk.     |
        | **Engagement Funnel**                  | Merchant rule        | Sent -> Delivered -> Opened -> Clicked. Drop-offs expose deliverability vs content weakness.         |
        | **Flow Status Breakdown**              | Merchant rule        | Active vs draft vs paused workflows. Drafted abandoned-cart workflow fires audit DRI01.              |
        | **Refund Rate**                        | Alert band 2 / 5     | Share of attributed orders later refunded.                                                           |
        | **Spam Complaint Rate**                | Alert band 0.1 / 0.3 | Above 0.1% Gmail starts marking the sender domain. DRI03 fires; investigate immediately.             |
        | **Unsubscribe Rate**                   | Alert band 0.3 / 1   | Unsubscribes per send. A spike signals list fatigue or off-target content.                           |
      </Accordion>

      <Accordion title="Run operations (7 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                               |
        | ----------------------------- | ------------------ | ---------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Alert band 5 / -5  | Estimated subscribed, reachable contacts.                                    |
        | **Email Open Rate**           | Alert band 25 / 15 | iOS Mail Privacy inflates this - pair with click-to-open for a truer signal. |
        | **Flow Count Summary**        | Merchant rule      | How many automations exist on the account.                                   |
        | **Flow Trigger Types**        | Merchant rule      | Automations grouped by what triggers them.                                   |
        | **Flows List**                | Merchant rule      | Every automation and its current status.                                     |
        | **List Health Summary**       | Alert band 90 / 70 | Total reachable members across all lists.                                    |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to email in the window.                                    |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (11)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-001, DRI05`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Email Bounce Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `DRI02`
      </Accordion>

      <Accordion title="Inactive Workflows">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `DRI01`
      </Accordion>

      <Accordion title="Limited Lists/Segmentation">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DRI04`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DRI03`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **3 write** operations across tags, accounts, broadcasts, campaigns, events, orders on Drip (API). 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=drip-api)

    #### Ready to build your first Drip (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource    | Read operations | Write operations |
      | ----------- | --------------- | ---------------- |
      | tags        | 1               | 1                |
      | accounts    | 1               | 0                |
      | broadcasts  | 1               | 0                |
      | campaigns   | 1               | 0                |
      | events      | 1               | 0                |
      | orders      | 1               | 0                |
      | subscribers | 1               | 0                |
      | workflows   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Dryrunpro on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/dryrunpro

Monitor Dryrunpro performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Dryrunpro performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=dryrunpro)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Dryrunpro yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **4 write** operations across connectordryrunprosaves, connectordryrunprovalidates, crewdryruns, crewdryrunlaunchs, crewdryrunteardowns on Dryrunpro. 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=dryrunpro)

    #### Ready to build your first Dryrunpro 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | connectordryrunprosaves     | 0               | 1                |
      | connectordryrunprovalidates | 0               | 1                |
      | crewdryruns                 | 1               | 0                |
      | crewdryrunlaunchs           | 0               | 1                |
      | crewdryrunteardowns         | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Amazon DynamoDB on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/dynamodb

Monitor Amazon DynamoDB health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Amazon DynamoDB health, cost and reliability signals, and catch incidents and runaway spend early.

[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=dynamodb)

<CardGroup>
  <Card title="30">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (30)">
    ### Monitor performance

    30 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | Signal                                       | Alert behaviour    | What it tracks                                                                                                                                      |
        | -------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Account Capacity Utilisation %**           | Alert band 70 / 90 | AccountProvisionedReadCapacityUtilization - how close the account is to its DescribeLimits quota.                                                   |
        | **Active Tables**                            | Watch only         | Count of tables in ACTIVE status from ListTables / DescribeTable.                                                                                   |
        | **Consumed Capacity (RCU+WCU, live)**        | Watch only         | ConsumedReadCapacityUnits + ConsumedWriteCapacityUnits Sum over the last minute.                                                                    |
        | **Last On-Demand Backup (hours ago)**        | Alert band 24 / 72 | Newest on-demand backup CreationDateTime from ListBackups. PITR covers continuous recovery; on-demand backups are the explicit snapshot trail.      |
        | **On-Demand Consumed Units (24h)**           | Merchant rule      | Consumed RCU+WCU on PAY\_PER\_REQUEST tables - proxy for on-demand spend (cost surface; precise \$ needs Cost Explorer / CUR).                      |
        | **Provisioned Capacity at >80% Utilisation** | Alert band 0 / 1   | Alerts for Provisioned Capacity at >80% Utilisation.                                                                                                |
        | **Provisioned Write Utilisation %**          | Alert band 70 / 90 | ConsumedWriteCapacityUnits / ProvisionedWriteCapacityUnits (PROVISIONED tables).                                                                    |
        | **Read Throttle Events (24h)**               | Merchant rule      | Sum of ReadThrottleEvents. Spike = under-provisioned reads or a hot partition.                                                                      |
        | **Table Storage (Top 10 by size)**           | Watch only         | TableSizeBytes from DescribeTable (approximate, \~6h lag). Drives storage cost.                                                                     |
        | **Throttle Events by Table (Top 10)**        | Merchant rule      | ThrottledRequests grouped by TableName dimension - pinpoints the offending table / GSI.                                                             |
        | **Throttle Rate %**                          | Alert band 0.1 / 1 | ThrottledRequests / (ThrottledRequests + successful requests). DynamoDB-distinctive - anything >1% means customers are seeing ProvisionedThroughput |
        | **Throttled Requests (5m)**                  | Merchant rule      | Sum of ThrottledRequests across all tables. DynamoDB-distinctive - the #1 incident signal; any sustained >0 means requests are being rejected.      |
        | **Throttled Requests Spike (any table)**     | Merchant rule      | DynamoDB-distinctive - throttling means requests rejected; surface the offending table / GSI immediately.                                           |
        | **Write Throttle Events (24h)**              | Merchant rule      | Sum of WriteThrottleEvents. Writes throttle faster than reads on hot partitions.                                                                    |
      </Accordion>

      <Accordion title="Control risk and change (6 signals)">
        | Signal                                     | Alert behaviour   | What it tracks                                                                                                                    |
        | ------------------------------------------ | ----------------- | --------------------------------------------------------------------------------------------------------------------------------- |
        | **DynamoDB Health Score**                  | Merchant rule     | Composite of throttle rate, error rate, latency p95 and capacity utilisation.                                                     |
        | **Global Table Replicas (state)**          | Watch only        | From DescribeGlobalTableSettings - replica region + ReplicaStatus. Gated on global tables being configured.                       |
        | **Global Table Replication Lag (seconds)** | Alert band 1 / 10 | CloudWatch ReplicationLatency for global tables, converted to seconds. Gated - only meaningful when global tables are configured. |
        | **System Error (5xx) Spike**               | Merchant rule     | Alerts for System Error (5xx) Spike.                                                                                              |
        | **System Errors (5xx, 5m)**                | Merchant rule     | SystemErrors - DynamoDB-side 5xx (InternalServerError). Any sustained >0 is an AWS-side incident.                                 |
        | **User Errors (4xx, 5m)**                  | Merchant rule     | UserErrors - client-side 4xx (validation, access-denied). Spike = a bad deploy hitting the table wrong.                           |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                                                               |
        | ------------------------------------------------------ | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Conditional Check Failures (1h)**                    | Merchant rule      | ConditionalCheckFailedRequests - DynamoDB-distinctive; a spike often signals an optimistic-locking contention storm.                         |
        | **Consumed Capacity Spike vs Ecom Order Rate**         | Merchant rule      | Description pending editorial review; the signal is live.                                                                                    |
        | **DynamoDB Products Table vs Ecom Catalog Size**       | Merchant rule      | DynamoDB-distinctive XC - many headless storefronts hold the product catalog in DynamoDB; item-count drift = sync failure.                   |
        | **Provisioned Read Utilisation %**                     | Alert band 70 / 90 | ConsumedReadCapacityUnits / ProvisionedReadCapacityUnits (PROVISIONED tables). >80% sustained = throttle risk; check auto-scaling.           |
        | **Tables Without PITR Enabled**                        | Merchant rule      | Count of tables where DescribeContinuousBackups.PointInTimeRecoveryStatus != ENABLED. Any production table without PITR is a data-loss risk. |
        | **Throttling on Cart/Inventory Table During Checkout** | Merchant rule      | DynamoDB-distinctive XC - the cart / session / inventory table throttling during checkout is revenue lost to capacity, not code.             |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                       | Alert behaviour      | What it tracks                                                                                                                                         |
        | ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **GetItem Latency p95 (ms)** | Alert band 50 / 200  | SuccessfulRequestLatency p95 with Operation=GetItem. DynamoDB targets single-digit ms - p95 over baseline is a real regression.                        |
        | **Latency p95 by Operation** | Watch only           | SuccessfulRequestLatency p95 broken out by Operation dimension (GetItem / Query / Scan / PutItem / ...).                                               |
        | **Query Latency p99 (ms)**   | Alert band 100 / 500 | SuccessfulRequestLatency p99 with Operation=Query.                                                                                                     |
        | **Slow-Query Rate %**        | Alert band 1 / 5     | CloudWatch Percentile Rank (Stat=PR(200:)) on SuccessfulRequestLatency - the % of samples above 200ms, computed server-side by CloudWatch from the und |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **9 write** operations across cloudwatch:getmetricdatas, cloudwatch:listmetrics, describecontinuousbackups, describeglobaltablesettings, describelimits, describetables on Amazon DynamoDB. 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=dynamodb)

    #### Ready to build your first Amazon DynamoDB 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | cloudwatch:getmetricdatas   | 0               | 1                |
      | cloudwatch:listmetrics      | 0               | 1                |
      | describecontinuousbackups   | 0               | 1                |
      | describeglobaltablesettings | 0               | 1                |
      | describelimits              | 0               | 1                |
      | describetables              | 0               | 1                |
      | listbackups                 | 0               | 1                |
      | listglobaltables            | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# EasyPost on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/easypost

Monitor EasyPost delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor EasyPost delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=easypost)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (24 signals)">
        | Signal                                              | Alert behaviour    | What it tracks                                                                                                                                |
        | --------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Avg Shipping Cost**                               | Merchant rule      | Description pending editorial review; the signal is live.                                                                                     |
        | **Carrier Accounts with Incomplete Credentials**    | Merchant rule      | EasyPost CarrierAccount objects with credentials\_complete=false , that carrier won't show up in rate shops until merchant completes setup.   |
        | **Carrier Failover Events (rate-shop rejections)**  | Merchant rule      | Times the rate-shop picked carrier B because carrier A rejected. Spike usually = credential expiry on primary carrier.                        |
        | **Carrier-Mix Savings vs Single-Carrier Baseline**  | Watch only         | How much rate shopping saved vs always picking the merchant's default carrier. EasyPost's ROI lives here , surfaces value of the integration. |
        | **Claim Value (open)**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Cost Per Shipment Trend**                         | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Cost by Zone**                                    | Watch only         | Cost by Zone.                                                                                                                                 |
        | **Days to Token Expiry**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Dispatch SLA Breached on N Orders Today**         | Merchant rule      | Alerts for Dispatch SLA Breached on N Orders Today.                                                                                           |
        | **Exception Rate**                                  | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                                                     |
        | **High-Cost Shipment Outliers**                     | Watch only         | High-Cost Shipment Outliers, broken down by row.                                                                                              |
        | **Label Generation Success**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Label Generation Success Rate (vendor override)** | Alert band 99 / 95 | Description pending editorial review; the signal is live.                                                                                     |
        | **Label Print Failures Spike**                      | Alert band 0 / 5   | EasyPost API failing to issue labels , blocks dispatch operations and stalls the whole fulfilment queue. P1.                                  |
        | **OTD by Route**                                    | Watch only         | OTD by Route.                                                                                                                                 |
        | **Open Claims**                                     | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Returned to Sender**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Route Volume Concentration**                      | Merchant rule      | Route Volume Concentration, compared across items.                                                                                            |
        | **Shipments**                                       | Merchant rule      | Description pending editorial review; the signal is live.                                                                                     |
        | **Shipments Over Time**                             | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Shipments by Destination**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Shipments by Service**                            | Watch only         | Shipments by Service.                                                                                                                         |
        | **Shipments by Underlying Carrier**                 | Watch only         | Split across USPS / FedEx / UPS / DHL / others. Mix shapes reveal which carrier renegotiations would matter most.                             |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                                | Alert behaviour   | What it tracks                                                                                                                                         |
        | ----------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cost per Parcel by Zone vs Direct-Carrier Pricing** | Merchant rule     | Validates EasyPost's rate-shop savings against direct-carrier integrations. Zones where EasyPost is consistently higher = renegotiation or platform-sw |
        | **Failed Deliveries**                                 | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Orders with Carrier Dispatch SLA Missed**           | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Rate-Shop API Latency p95**                         | Merchant rule     | EasyPost's POST /v2/shipments returns rates across all linked carriers , slow p95 = customer-side abandonment at checkout while waiting for shipping o |
        | **Return Rate by Underlying Carrier**                 | Merchant rule     | Surfaces underlying carriers whose service quality drives returns. EasyPost rate-shopper can be retuned to deprioritise problem carriers.              |
        | **Shipments with Tracking-Event Gap >24h**            | Alert band 0 / 10 | Shipments with Tracking-Event Gap >24h, broken down by row.                                                                                            |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                             |
        | ------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                  |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                  |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                  |
        | **OTD by Underlying Carrier**   | Alert band 95 / 90 | Per-underlying-carrier OTD when shipped via EasyPost. Surfaces which carrier renegotiation pays back most. |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                  |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                             | Alert behaviour | What it tracks                             |
        | ---------------------------------- | --------------- | ------------------------------------------ |
        | **Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for Tracking API Unavailable / 5xx. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **2 write** operations across shipments, carrieraccounts, claims, refunds, trackers, users on EasyPost. 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=easypost)

    #### Ready to build your first EasyPost 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | shipments       | 1               | 1                |
      | carrieraccounts | 1               | 0                |
      | claims          | 1               | 0                |
      | refunds         | 0               | 1                |
      | trackers        | 1               | 0                |
      | users           | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# eBay on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/ebay

Monitor eBay listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor eBay listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=ebay)

<CardGroup>
  <Card title="37">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (37)">
    ### Monitor performance

    37 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                           | Alert behaviour      | What it tracks                                                                                                                                         |
        | -------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Buyer Messages Unread**        | Watch only           | Buyer Messages Unread as exposed by the eBay integration. The metric is computed from the latest available data and refreshed on the standard data ref |
        | **Cases Closed w/o Resolution**  | Alert band 0.3 / 0.6 | Description pending editorial review; the signal is live.                                                                                              |
        | **Defect Rate**                  | Alert band 1 / 2     | Description pending editorial review; the signal is live.                                                                                              |
        | **INR Cases Burst (24h)**        | Merchant rule        | Alerts for INR Cases Burst (24h).                                                                                                                      |
        | **Late Shipment Rate**           | Alert band 3 / 6     | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Fees**             | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **OAuth Token Expiry**           | Merchant rule        | eBay refresh tokens last \~18 months but rotate , silent expiry kills sync.                                                                            |
        | **Oldest Pending Payout (days)** | Alert band 7 / 21    | Oldest Pending Payout (days) as exposed by the eBay integration. The metric is computed from the latest available data and refreshed on the standard d |
        | **Pending Payouts**              | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Seller Standards Drop Alert**  | Alert band 0 / 1     | Alerts for Seller Standards Drop Alert.                                                                                                                |
        | **Seller Standards Level**       | Alert band 95 / 85   | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Transactions**           | Watch only           | Total Transactions as exposed by the eBay integration. The metric is computed from the latest available data and refreshed on the standard data refres |
        | **eBay Health Score**            | Merchant rule        | Composite of seller-standards level, defect rate and the open-inquiry (INR proxy) count. Single CXO number.                                            |
      </Accordion>

      <Accordion title="Grow revenue (12 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                                                                                        |
        | ------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**               | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                             |
        | **Fees % of Revenue**                 | Alert band 12 / 18 | Description pending editorial review; the signal is live.                                                                                             |
        | **Listings Missing Attributes**       | Alert band 5 / 50  | Listings missing a title, item-specifics (aspects) or images. A generic completeness heuristic, not the per-category required-aspects ruleset. Direct |
        | **Orders**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Promoted Listings ACOS**            | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Promoted Listings Spend**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Promoted Listings Waste Burst**     | Alert band 5 / 50  | Alerts for Promoted Listings Waste Burst.                                                                                                             |
        | **Revenue Over Time**                 | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                             |
        | **Revenue by Marketplace**            | Watch only         | Revenue by Marketplace.                                                                                                                               |
        | **Top Listings by Revenue**           | Watch only         | Top Listings by Revenue.                                                                                                                              |
        | **Total Revenue**                     | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                             |
        | **Zero-Conversion Promoted Listings** | Alert band 5 / 50  | Promoted listings with spend >\$X but zero conversions , wasted ad fees, recoverable next sweep.                                                      |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                              | Alert behaviour   | What it tracks                                                                                                                                |
        | ----------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Amazon Top SKUs Missing on eBay** | Merchant rule     | Velocity-proven SKUs absent from eBay , cheapest channel-expansion lift.                                                                      |
        | **Catalogue Drift vs Amazon**       | Alert band 5 / 50 | Same SKU listed at materially different prices on eBay vs Amazon UK , MAP / brand-consistency risk.                                           |
        | **Fulfilment SLA (via ShipBob)**    | Merchant rule     | Description pending editorial review; the signal is live.                                                                                     |
        | **Open INR Cases**                  | Alert band 0 / 5  | Proxy from buyer-opened cancellation / return inquiries (IN\_INQUIRY state). The dedicated item-not-received cases endpoint is not yet wired. |
        | **Revenue at Risk (live)**          | Merchant rule     | Description pending editorial review; the signal is live.                                                                                     |
        | **eBay vs Amazon Revenue Share**    | Watch only        | eBay vs Amazon Revenue Share, shown by share.                                                                                                 |
      </Accordion>

      <Accordion title="Catalogue quality (6 signals)">
        | Signal                       | Alert behaviour | What it tracks                                                                                                                                         |
        | ---------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**          | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Condition Mix**            | Watch only      | Condition Mix, shown by share.                                                                                                                         |
        | **Feedback Score (90d)**     | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Listings Expiring Soon**   | Watch only      | Listings Expiring Soon as exposed by the eBay integration. The metric is computed from the latest available data and refreshed on the standard data re |
        | **Listings by Category**     | Watch only      | Listings by Category.                                                                                                                                  |
        | **Zero-View Listings (30d)** | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **0 write** operations across sellaccountprivileges, sellanalyticssellerstandardprofiles, sellfinancepayouts, sellfinancetransactions, sellfulfillmentorders, sellinventoryinventoryitems on eBay. 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=ebay)

    #### Ready to build your first eBay 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                            | Read operations | Write operations |
      | ----------------------------------- | --------------- | ---------------- |
      | sellaccountprivileges               | 1               | 0                |
      | sellanalyticssellerstandardprofiles | 1               | 0                |
      | sellfinancepayouts                  | 1               | 0                |
      | sellfinancetransactions             | 1               | 0                |
      | sellfulfillmentorders               | 1               | 0                |
      | sellinventoryinventoryitems         | 1               | 0                |
      | sellmarketingadcampaigns            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Ecwid by Lightspeed on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/ecwid

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Ecwid by Lightspeed.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Ecwid by Lightspeed.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/ecwid) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=ecwid)

<CardGroup>
  <Card title="41">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (41)">
    ### Monitor performance

    41 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                        | Alert behaviour    | What it tracks                                                                                                                               |
        | --------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AOV by Country**                            | Watch only         | AOV by Country.                                                                                                                              |
        | **Active Storefront Surfaces**                | Watch only         | Count of enabled storefront surfaces (embed / Instant Site / Facebook / Instagram / Square POS etc.). Top of the multi-channel health stack. |
        | **Average Order Value**                       | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                    |
        | **Avg Order Fulfillment Time**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                    |
        | **Awaiting Payment Orders**                   | Merchant rule      | Orders stuck in AWAITING\_PAYMENT > 24h usually = payment-gateway issue or customer-side dropoff.                                            |
        | **Channel-Specific Order Drop**               | Merchant rule      | If one storefront surface stops producing orders while others continue, indicates surface-specific outage or sync break.                     |
        | **Fulfillment Rate**                          | Alert band 95 / 90 | % of orders (30d) with fulfillmentStatus SHIPPED or DELIVERED.                                                                               |
        | **New Customers (30d)**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                    |
        | **Order Processing Backlog**                  | Alert band 10 / 50 | Alerts for Order Processing Backlog.                                                                                                         |
        | **Order Volume**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                    |
        | **Orders by Country**                         | Watch only         | Description pending editorial review; the signal is live.                                                                                    |
        | **Pending Orders**                            | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                    |
        | **Products on Unlimited Stock (no tracking)** | Merchant rule      | Ecwid's unlimited-stock flag skips inventory tracking. High % = either intentional (digital products) or sloppy (missing stock setup).       |
        | **Stock-Out Burst (>5 SKUs in \<1h)**         | Merchant rule      | Alerts for Stock-Out Burst (>5 SKUs in \<1h).                                                                                                |
        | **Total Customers**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                    |
      </Accordion>

      <Accordion title="Protect revenue (11 signals)">
        | Signal                                             | Alert behaviour  | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cancellation Rate**                              | Alert band 1 / 3 | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Rate**                                | Alert band 3 / 1 | Conversion Rate from Ecwid by Lightspeed, grouped under Revenue at Risk. Computes when a live Ecwid by Lightspeed integration is connected; reconciles |
        | **Ecwid Inventory vs Active Marketplace Listings** | Merchant rule    | Ecwid Inventory vs Active Marketplace Listings.                                                                                                        |
        | **High-Value Customers Unengaged on Email**        | Merchant rule    | High-Value Customers Unengaged on Email, broken down by row.                                                                                           |
        | **Inventory Sync Drift Across Storefronts**        | Merchant rule    | Same SKU showing different stock counts across embed vs Instant Site vs Facebook shop = sync logic gap; risks overselling.                             |
        | **Low-Stock Products**                             | Watch only       | Low-Stock Products from Ecwid by Lightspeed, grouped under Catalogue Health. Computes when a live Ecwid by Lightspeed integration is connected; reconc |
        | **Orders → Email Campaign Attribution**            | Merchant rule    | Orders → Email Campaign Attribution, broken down by row.                                                                                               |
        | **Out-of-Stock Products**                          | Alert band 0 / 5 | Description pending editorial review; the signal is live.                                                                                              |
        | **Refund Rate**                                    | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue at Risk**                                | Merchant rule    | Description pending editorial review; the signal is live.                                                                                              |
        | **Top-Velocity SKUs vs Ad Spend**                  | Merchant rule    | Top-Velocity SKUs vs Ad Spend, broken down by row.                                                                                                     |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                          |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Coupon Code Usage Rate**               | Alert band 20 / 40 | % of orders (30d) with a discount coupon code applied , an order-count share, not the \$-discount-to-revenue ratio some other platforms show under this |
        | **Guest vs Registered Order Split**      | Watch only         | Ecwid permits guest checkout. High guest share = lower email reach for re-engagement.                                                                   |
        | **Orders by Status**                     | Watch only         | Orders by Status from Ecwid by Lightspeed, grouped under Revenue & Growth. Computes when a live Ecwid by Lightspeed integration is connected; reconcil  |
        | **Orders to Email Campaign Attribution** | Watch only         | Orders to Email Campaign Attribution from Ecwid by Lightspeed, grouped under Order Issues. Computes when a live Ecwid by Lightspeed integration is con  |
        | **Products Missing SEO Title**           | Alert band 10 / 30 | Products where seoTitle is empty , distinct from the display name, so search engines and social previews have nothing written for them.                 |
        | **Repeat Customer Rate**                 | Alert band 25 / 10 | Description pending editorial review; the signal is live.                                                                                               |
        | **Revenue Trend**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                               |
        | **Revenue by Storefront Surface**        | Watch only         | Per-storefront revenue split. Reveals which surfaces are pulling weight and which are dormant.                                                          |
        | **Top Products by Revenue**              | Watch only         | Top Products by Revenue from Ecwid by Lightspeed, grouped under Revenue & Growth. Computes when a live Ecwid by Lightspeed integration is connected; r  |
        | **Total Revenue (30d)**                  | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                               |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                              |
        | -------------------------------- | ----------------- | ------------------------------------------------------------------------------------------- |
        | **Disabled Products**            | Watch only        | Description pending editorial review; the signal is live.                                   |
        | **Products Missing Description** | Alert band 5 / 20 | Products where description is empty (HTML markup with no real text also counts as missing). |
        | **Total Products**               | Watch only        | Description pending editorial review; the signal is live.                                   |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                           | Alert behaviour | What it tracks                           |
        | -------------------------------- | --------------- | ---------------------------------------- |
        | **Ecwid API Failure Rate Spike** | Merchant rule   | Alerts for Ecwid API Failure Rate Spike. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                              | Alert behaviour | What it tracks                                                                                                                             |
        | ----------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Storefronts on Deprecated Theme** | Merchant rule   | Themes deprecated by Ecwid's twice-yearly design refresh. Old themes silently lose features (cart UX improvements, accessibility patches). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across customers, orders, products, profiles, storefronts on Ecwid by Lightspeed. 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=ecwid)

    #### Ready to build your first Ecwid by Lightspeed 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.

    <Accordion title="Browse the operations you can build with">
      | Resource    | Read operations | Write operations |
      | ----------- | --------------- | ---------------- |
      | customers   | 1               | 0                |
      | orders      | 1               | 0                |
      | products    | 1               | 0                |
      | profiles    | 1               | 0                |
      | storefronts | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Elasticsearch on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/elasticsearch

Monitor Elasticsearch health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Elasticsearch health, cost and reliability signals, and catch incidents and runaway spend early.

[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=elasticsearch)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Grow revenue (15 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                 |
        | ----------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------- |
        | **Cluster Not Green (yellow or red)**     | Merchant rule        | Elasticsearch-distinctive , RED = data unavailable on affected indexes. Page on-call.                          |
        | **Cluster Status (green / yellow / red)** | Merchant rule        | From /\_cluster/health.status. Elasticsearch-defining: YELLOW = replicas missing, RED = primary unallocated.   |
        | **Elasticsearch Health Score**            | Merchant rule        | Description pending editorial review; the signal is live.                                                      |
        | **GC Pause Time (5m total ms)**           | Merchant rule        | From jvm.gc.collectors. Long pauses = node temporarily unavailable for search/indexing.                        |
        | **Indexing Rate (docs/sec)**              | Watch only           | From indices.indexing.index\_total delta. Elasticsearch-distinctive , drives sync-lag investigations.          |
        | **JVM Heap Used %**                       | Merchant rule        | Elasticsearch-distinctive , JVM heap >75% triggers GC pressure + circuit breakers; >90% = node may OOM.        |
        | **Search Error Rate %**                   | Alert band 0.1 / 1   | Description pending editorial review; the signal is live.                                                      |
        | **Search Error Rate Spike (>1% in 5m)**   | Alert band 0.1 / 1   | Alerts for Search Error Rate Spike (>1% in 5m).                                                                |
        | **Search Latency p50 (ms)**               | Watch only           | Description pending editorial review; the signal is live.                                                      |
        | **Search Latency p95 (ms)**               | Alert band 50 / 200  | From indices.search.query\_time\_in\_millis / query\_total delta. Storefront-facing , directly user-impacting. |
        | **Search Latency p99 (ms)**               | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                      |
        | **Search Queries per Second (live)**      | Watch only           | Description pending editorial review; the signal is live.                                                      |
        | **Shard Size Skew %**                     | Merchant rule        | (max shard size - min shard size) / avg. >25% = hot shard. Elasticsearch-distinctive.                          |
        | **Slow-Query Rate %**                     | Alert band 1 / 5     | Searches exceeding slowlog threshold (default 1s) as % of total.                                               |
        | **Top 10 Slow Searches**                  | Watch only           | Top 10 Slow Searches, broken down by row.                                                                      |
      </Accordion>

      <Accordion title="Run operations (13 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                                                                  |
        | ------------------------------------------------------ | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Node Count**                                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                       |
        | **Avg Index Refresh Time (ms)**                        | Merchant rule      | indices.refresh.total\_time\_in\_millis / refresh.total. Climbing = segments stacking up.                                                       |
        | **Circuit Breaker Trips (24h)**                        | Merchant rule      | From breakers tripped count. Requests rejected to prevent OOM.                                                                                  |
        | **HTTP Connection Saturation %**                       | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                                                       |
        | **HTTP Connections In Use**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                       |
        | **Initializing / Relocating Shards**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                       |
        | **JVM Heap >85% Sustained or Circuit Breaker Tripped** | Merchant rule      | Alerts for JVM Heap >85% Sustained or Circuit Breaker Tripped.                                                                                  |
        | **Last Snapshot Age (hours)**                          | Alert band 24 / 72 | Last successful \_snapshot run from registered repository.                                                                                      |
        | **Pending Cluster Tasks**                              | Merchant rule      | From /\_cluster/pending\_tasks. High = master node overloaded with cluster-state updates.                                                       |
        | **Query Cache Hit Rate %**                             | Alert band 95 / 80 | Sum of indices.query\_cache.hit\_count / (hit\_count + miss\_count) across all nodes from /\_nodes/stats/indices - cumulative since node start. |
        | **Replica Sync Lag**                                   | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                                                       |
        | **Storage Usage %**                                    | Alert band 70 / 90 | Disk usage relative to flood-stage watermark (default 95%). Hitting marks indexes read-only.                                                    |
        | **Total Shards (primary + replica)**                   | Watch only         | Description pending editorial review; the signal is live.                                                                                       |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                               |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Bulk Rejections (24h)**                      | Merchant rule      | thread\_pool.write.rejected. Indexing backpressure = client retry / data loss risk.                          |
        | **ES Product Index Doc Count vs Ecom Catalog** | Merchant rule      | Elasticsearch-distinctive XC , drift = product-sync to search broken; merchants miss SKUs in search results. |
        | **ES Search Pool Saturation vs Ecom Burst**    | Alert band 70 / 90 | ES Search Pool Saturation vs Ecom Burst, broken down by row.                                                 |
        | **Search QPS Spike vs Ecom Traffic**           | Merchant rule      | Description pending editorial review; the signal is live.                                                    |
        | **Slow Searches During Checkout Window (5m)**  | Merchant rule      | Slow Searches During Checkout Window (5m), broken down by row.                                               |
        | **Unassigned Shards**                          | Merchant rule      | From /\_cluster/health.unassigned\_shards. Any unassigned = data loss risk for that shard's replicas.        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **0 write** operations across catindices, catshards, clusterhealths, clusterpendingtasks, clusterstats, nodestats on Elasticsearch. 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=elasticsearch)

    #### Ready to build your first Elasticsearch 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | catindices          | 1               | 0                |
      | catshards           | 1               | 0                |
      | clusterhealths      | 1               | 0                |
      | clusterpendingtasks | 1               | 0                |
      | clusterstats        | 1               | 0                |
      | nodestats           | 1               | 0                |
      | nodestathttps       | 1               | 0                |
      | snapshotstatus      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Etsy on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/etsy

Monitor Etsy listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Etsy listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=etsy)

<CardGroup>
  <Card title="39">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (39)">
    ### Monitor performance

    39 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (15 signals)">
        | Signal                                                             | Alert behaviour    | What it tracks                                                                                                                  |
        | ------------------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**                                            | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                       |
        | **Average Review Rating (Star Seller KPI)**                        | Alert band 95 / 85 | Star Seller requires 4.8+ avg review over rolling 90d. Drops below = badge loss + visibility penalty.                           |
        | **Etsy Ads Revenue vs Organic**                                    | Watch only         | Split of revenue from Etsy Ads (paid) vs natural-search (organic). High Ads share = consider organic SEO investment.            |
        | **Etsy Fee % of Revenue**                                          | Alert band 12 / 18 | Total fees / gross revenue. Etsy: 6.5% transaction + $0.20/listing/4mo renewal + 3% + $0.25 payment + Ads if running.           |
        | **Etsy Shop Health Score**                                         | Merchant rule      | Composite: review-rate x on-time-ship-rate x active-listing-pct x search-rank-stability.                                        |
        | **Listings with SEO-Weak Titles**                                  | Alert band 5 / 50  | Titles below 70 chars OR missing key search terms OR repeating brand-only , drives page-rank drop.                              |
        | **Orders**                                                         | Watch only         | Description pending editorial review; the signal is live.                                                                       |
        | **Revenue Over Time**                                              | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                       |
        | **Stale Listings (>180d no update)**                               | Merchant rule      | Stale listings get deprioritised in Etsy search , even a minor edit (title, tag, photo) refreshes the freshness signal.         |
        | **Star Seller KPI (Review / OnTime / Response) Crossed Threshold** | Alert band 95 / 85 | Composite of Etsy's three Star Seller KPIs , any one crossing causes badge loss and visibility cut.                             |
        | **Star Seller Status**                                             | Merchant rule      | Etsy's seller-quality badge. Requires 95% on-time ship + 5★ avg review + ≤1 response-rate breach in 30d. Loss = visibility cut. |
        | **Tag Completeness (13 tags max)**                                 | Alert band 90 / 70 | % of listings using all 13 Etsy tag slots , Etsy search algorithm rewards full tag-set use.                                     |
        | **Top Listings by Revenue**                                        | Watch only         | Top Listings by Revenue.                                                                                                        |
        | **Total Revenue**                                                  | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                       |
        | **Views → Favourites Conversion**                                  | Merchant rule      | Soft-conversion signal , low rate suggests photo/title/price mismatch with what buyers expected from search.                    |
      </Accordion>

      <Accordion title="Run operations (11 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country**                          | Watch only         | AOV by Country.                                                                                                                                        |
        | **Buyer Messages Unread**                   | Watch only         | Buyer Messages Unread as exposed by the Etsy integration. The metric is computed from the latest available data and refreshed on the standard data ref |
        | **Days Since Last Payout**                  | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Fees Paid**                   | Watch only         | Marketplace Fees Paid as exposed by the Etsy integration. The metric is computed from the latest available data and refreshed on the standard data ref |
        | **Oldest Pending Payout (days)**            | Watch only         | Oldest Pending Payout (days) as exposed by the Etsy integration. The metric is computed from the latest available data and refreshed on the standard d |
        | **On-Time Shipping Rate (Star Seller KPI)** | Merchant rule      | Star Seller requires 95% of orders shipped within seller-declared processing window. Below threshold = badge loss.                                     |
        | **Orders / Day**                            | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                         | Watch only         | Pending Payouts as exposed by the Etsy integration. The metric is computed from the latest available data and refreshed on the standard data refresh   |
        | **Pending Shipment**                        | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Return Rate**                             | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                                                   | Alert behaviour   | What it tracks                                                                                                                             |
        | -------------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Etsy Listings for OOS SKUs on BC**              | Alert band 0 / 5  | Etsy orders you can't fulfil → cancellations → Star Seller demotion. Top-priority sync gap.                                                |
        | **Cancellation Rate**                                    | Merchant rule     | Description pending editorial review; the signal is live.                                                                                  |
        | **Late Shipments Risking Star Seller**                   | Merchant rule     | Star Seller threshold is 95% on-time over 90d , each late shipment compounds the badge-loss risk.                                          |
        | **Listings Drifting from BC Source-of-Truth**            | Alert band 5 / 50 | Etsy listings where title/price/photo differs from BC source , Etsy's search algorithm weights title heavily.                              |
        | **Listings Failing Feedonomics Validation**              | Alert band 2 / 5  | Etsy doesn't formally take Feedonomics feeds, but Etsy Ads can be syndicated via Feedonomics where applicable.                             |
        | **Net Revenue (after Etsy fees + refunds)**              | Alert band 0 / -5 | Net of 6.5% transaction fee + \$0.20/listing/4mo renewal + Etsy Ads spend if applicable.                                                   |
        | **Revenue at Risk (live)**                               | Merchant rule     | (expiring-listings-without-renewal x velocity x ASP) + (page-rank-dropped listings x prior earnings) + (Star Seller loss visibility cost). |
        | **Same-Item Priced Differently on Etsy vs eBay / Depop** | Merchant rule     | Same handmade/vintage item priced very differently across resale marketplaces , buyers find this via Google Shopping.                      |
      </Accordion>

      <Accordion title="Catalogue quality (5 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                                             |
        | ---------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
        | **Active Listings**                            | Merchant rule      | Description pending editorial review; the signal is live.                                                                  |
        | **Etsy Suspended Listings (24h)**              | Alert band 5 / 50  | Etsy suspends listings for handmade-policy violations, prohibited materials, or trademark complaints.                      |
        | **Listings Expiring in 30 Days (renewal due)** | Merchant rule      | Etsy listings expire after 4 months. Auto-renew costs \$0.20/each , surface so you can decide which to renew vs let lapse. |
        | **Required-Attribute Completeness**            | Alert band 90 / 70 | % of listings with all category-mandated attributes filled (colour, size, material, etc.).                                 |
        | **Total Listings**                             | Watch only         | Description pending editorial review; the signal is live.                                                                  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across applicationshops, applicationshoplistingactives, applicationshopreceipts, applicationshopreviews, publicoauthtokens on Etsy. 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=etsy)

    #### Ready to build your first Etsy 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                      | Read operations | Write operations |
      | ----------------------------- | --------------- | ---------------- |
      | applicationshops              | 1               | 0                |
      | applicationshoplistingactives | 1               | 0                |
      | applicationshopreceipts       | 1               | 0                |
      | applicationshopreviews        | 1               | 0                |
      | publicoauthtokens             | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Meta Ads (Facebook) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/facebook-ads

Monitor Meta Ads (Facebook) campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Meta Ads (Facebook) campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[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=facebook-ads)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="154">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                             |
        | -------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**              | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **CAPI/Pixel Tracking Broken**   | Merchant rule      | Tag fires fail silently and Aggregated Event Measurement throttles delivery. Catch within the same iOS-attribution window. |
        | **CPC by Campaign**              | Watch only         | CPC by Campaign.                                                                                                           |
        | **CTR by Campaign**              | Watch only         | CTR by Campaign.                                                                                                           |
        | **Campaign Comparison**          | Watch only         | Campaign Comparison, broken down by row.                                                                                   |
        | **Clicks vs Conversions**        | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Conversion Actions Breakdown** | Watch only         | Conversion Actions Breakdown.                                                                                              |
        | **Conversion Drop Alert**        | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Conversion Funnel**            | Watch only         | Conversion Funnel, stage by stage.                                                                                         |
        | **Conversion Lag**               | Watch only         | Conversion Lag, compared across items.                                                                                     |
        | **Conversion Rate Trend**        | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Conversion Rate by Campaign**  | Watch only         | Conversion Rate by Campaign.                                                                                               |
        | **Conversion Rate by Device**    | Watch only         | Conversion Rate by Device.                                                                                                 |
        | **Conversions Trend**            | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Conversions by Campaign**      | Watch only         | Conversions by Campaign.                                                                                                   |
        | **Conversions by Country**       | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Conversions by Day of Week**   | Watch only         | Conversions by Day of Week.                                                                                                |
        | **Conversions by Device**        | Watch only         | Conversions by Device.                                                                                                     |
        | **Conversions by Hour**          | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Landing Page Revenue**         | Watch only         | Landing Page Revenue, broken down by row.                                                                                  |
        | **Overspending Campaigns**       | Watch only         | Overspending Campaigns, broken down by row.                                                                                |
        | **ROAS**                         | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                                  |
        | **ROAS Dropped Below Threshold** | Alert band 3 / 1.5 | First number to ping when the ad team's morning is going to be bad.                                                        |
        | **ROAS Trend**                   | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **ROAS by Campaign**             | Watch only         | ROAS by Campaign.                                                                                                          |
        | **ROAS by Day of Week**          | Watch only         | ROAS by Day of Week.                                                                                                       |
        | **ROAS by Device**               | Watch only         | ROAS by Device.                                                                                                            |
        | **ROAS by Region**               | Watch only         | ROAS by Region.                                                                                                            |
        | **Revenue by Campaign**          | Watch only         | Revenue by Campaign.                                                                                                       |
        | **Search Terms Report**          | Watch only         | Search Terms Report, broken down by row.                                                                                   |
        | **Spend by Campaign**            | Watch only         | Spend by Campaign.                                                                                                         |
        | **Top Cities by Conversions**    | Watch only         | Top Cities by Conversions.                                                                                                 |
        | **Top Keywords by Conversions**  | Watch only         | Top Keywords by Conversions.                                                                                               |
        | **Top Performing Campaigns**     | Watch only         | Top Performing Campaigns, broken down by row.                                                                              |
        | **Total Revenue**                | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Underspending Campaigns**      | Watch only         | Underspending Campaigns, broken down by row.                                                                               |
        | **Worst Performing Campaigns**   | Watch only         | Worst Performing Campaigns, broken down by row.                                                                            |
        | **Zero-Conversion Spend**        | Watch only         | Description pending editorial review; the signal is live.                                                                  |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                               |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------ |
        | **Budget Utilisation**               | Alert band 70 / 30 | Description pending editorial review; the signal is live.    |
        | **CPA Trend**                        | Watch only         | Description pending editorial review; the signal is live.    |
        | **CPA by Keyword**                   | Watch only         | CPA by Keyword.                                              |
        | **CPC Anomaly**                      | Watch only         | Description pending editorial review; the signal is live.    |
        | **CPC Spike Detection**              | Watch only         | Description pending editorial review; the signal is live.    |
        | **CPC Trend**                        | Alert band 0 / 25  | Description pending editorial review; the signal is live.    |
        | **CTR Trend**                        | Watch only         | Description pending editorial review; the signal is live.    |
        | **CTR by Keyword**                   | Watch only         | CTR by Keyword.                                              |
        | **Impression Share**                 | Alert band 70 / 40 | Description pending editorial review; the signal is live.    |
        | **Impressions Trend**                | Watch only         | Description pending editorial review; the signal is live.    |
        | **Quality Score Distribution**       | Alert band 7 / 4   | Quality Score Distribution, compared across items.           |
        | **Spend Anomaly**                    | Watch only         | Description pending editorial review; the signal is live.    |
        | **Spend Over Time**                  | Alert band 0 / -10 | Description pending editorial review; the signal is live.    |
        | **Spend vs Budget**                  | Watch only         | Description pending editorial review; the signal is live.    |
        | **Top Keywords by Spend**            | Watch only         | Top Keywords by Spend.                                       |
        | **Total Spend**                      | Watch only         | Description pending editorial review; the signal is live.    |
        | **Wasted Spend**                     | Watch only         | Description pending editorial review; the signal is live.    |
        | **Wasted-Spend Burst (3-day spike)** | Alert band 5 / 50  | Runaway budget on a broken creative before it eats the week. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Ads on Out-of-Stock SKUs**                | Alert band 5 / 50 | Spend on Advantage+ Catalog or DPA ads pointing at SKUs that can't convert. Pause the ad, hold the budget, recover within minutes.                     |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | % of branded paid clicks on Meta that would have come in free via organic search. Pure margin reclaim. Pause the branded campaign or exclude the keywo |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
        | **Mobile Landing Pages with Poor Web Vitals**      | Merchant rule     | Meta traffic skews mobile. Slow mobile landing pages convert worse; names the page so the dev fixes it the same day.                                   |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on a catalog campaign whose linked Feedonomics export has live rejections; bid signal degrades, ROAS bleeds, until the feed clears.                  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **107 read** and **47 write** operations across adlabels, copys, insights, ads, adcreatives, budgetschedules on Meta Ads (Facebook). 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=facebook-ads)

    #### Ready to build your first Meta Ads (Facebook) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | adlabels               | 1               | 5                |
      | copys                  | 3               | 3                |
      | insights               | 6               | 0                |
      | ads                    | 4               | 1                |
      | adcreatives            | 3               | 1                |
      | budgetschedules        | 2               | 2                |
      | adrulegoverneds        | 3               | 0                |
      | targetingsentencelines | 3               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# FedEx on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/fedex

Monitor FedEx delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor FedEx delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=fedex)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                            |
        | ------------------------------- | ---------------- | --------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live. |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                             |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live. |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.          |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live. |
        | **OTD by Route**                | Watch only       | OTD by Route.                                             |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live. |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.        |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                     |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                    |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **First-Attempt Delivery Rate**        | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Late Shipments**                     | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **On-Time Delivery Rate**              | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                         |
        | **Priority Overnight Service Promise** | Alert band 95 / 90 | % of FedEx Priority Overnight / First Overnight consignments delivered next-business-day-by-10:30. The flagship FedEx promise (\~99% contracted). |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Failed Deliveries**                       | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **FedEx OTD by Sales Channel**              | Alert band 95 / 90 | Per-channel FedEx OTD.                                                                                                                                 |
        | **Hazmat Shipment Acceptance Rate**         | Merchant rule      | FedEx has strict hazmat / dangerous-goods screening. Acceptance rate \< 98% means documentation gaps - fines + service-suspension risk.                |
        | **International Customs-Hold Rate by Lane** | Merchant rule      | Per-lane customs-hold rate for international shipments. Surfaces specific origin/destination combos where commercial-invoice or HS-code data needs wor |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **4 write** operations across oauthtokens, rateratequotes, shipshipments, tracktrackingnumbers on FedEx. 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=fedex)

    #### Ready to build your first FedEx 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | oauthtokens          | 0               | 1                |
      | rateratequotes       | 0               | 1                |
      | shipshipments        | 0               | 1                |
      | tracktrackingnumbers | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Firestore on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/firestore

Monitor Google Firestore health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Google Firestore health, cost and reliability signals, and catch incidents and runaway spend early.

[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=firestore)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (10 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                         |
        | ----------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------- |
        | **Active Realtime Connections**           | Watch only         | network/active\_connections - concurrent SDK / realtime connections to the database.                                   |
        | **Active Snapshot Listeners**             | Watch only         | network/snapshot\_listeners - Firestore-distinctive realtime listener count (onSnapshot subscriptions).                |
        | **Document Operations per Second (live)** | Watch only         | read\_ops\_count + write\_ops\_count + delete\_ops\_count rate from Cloud Monitoring.                                  |
        | **Document Reads (24h)**                  | Watch only         | document/read\_ops\_count summed over 24h - Firestore bills per document read.                                         |
        | **Document Writes (24h)**                 | Watch only         | document/write\_ops\_count summed over 24h.                                                                            |
        | **Index Builds In Progress**              | Merchant rule      | Firestore-distinctive - composite indexes in CREATING state. A build stuck many hours blocks the queries that need it. |
        | **Point-in-Time Recovery Window (hours)** | Alert band 24 / 72 | PITR retention from pointInTimeRecoveryEnablement (7d on Enterprise). No PITR = no rollback path on bad writes.        |
        | **Request Latency p95 >200ms Sustained**  | Alert band 0 / 1   | Alerts for Request Latency p95 >200ms Sustained.                                                                       |
        | **Stored Bytes**                          | Watch only         | Estimated stored bytes (documents + index entries). Firestore bills per GB-month.                                      |
        | **Total Document Count**                  | Watch only         | document/count across the database - drives storage cost.                                                              |
      </Accordion>

      <Accordion title="Control risk and change (5 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                |
        | ------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------- |
        | **API Request Error Rate %**                      | Alert band 0.1 / 1 | api/request\_count filtered by response\_code != OK over total requests.                      |
        | **API Request Error Rate Spike (>1% in 5m)**      | Alert band 0.1 / 1 | Alerts for API Request Error Rate Spike (>1% in 5m).                                          |
        | **Firestore Health Score**                        | Merchant rule      | Composite of latency, error rate, op trend and index health.                                  |
        | **Index in NEEDS\_REPAIR / ERROR or Build Stuck** | Merchant rule      | Alerts for Index in NEEDS\_REPAIR / ERROR or Build Stuck.                                     |
        | **Indexes in NEEDS\_REPAIR / ERROR**              | Merchant rule      | Composite indexes in NEEDS\_REPAIR / ERROR state - queries depending on them fail at runtime. |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                                      | Alert behaviour      | What it tracks                                                                                                                                           |
        | ------------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Request Latency p95 (ms)**            | Alert band 50 / 200  | 95th percentile of api/request\_latencies distribution (receive → finish-send).                                                                          |
        | **API Request Latency p99 (ms)**            | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                                |
        | **Highest-Latency Request Shapes (top 10)** | Watch only           | api/request\_latencies grouped by api\_method + collection group.                                                                                        |
        | **Read:Write Op Ratio**                     | Watch only           | read\_ops\_count / write\_ops\_count. Firestore-distinctive - a sudden read spike vs writes = unindexed query fan-out or listener amplification.         |
        | **Slow-Query Rate %**                       | Alert band 1 / 5     | Share of api/request\_latencies samples over 200ms, computed from the metric's raw DISTRIBUTION bucketCounts (Cloud Monitoring, ALIGN\_DELTA/unaggregate |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                                | Alert behaviour | What it tracks                                                                                            |
        | ----------------------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------- |
        | **Firestore Op Spike vs Ecom Order Rate**             | Merchant rule   | Firestore bills per read - a read spike with no order spike burns money for nothing.                      |
        | **Firestore Products Collection vs Ecom Catalog**     | Merchant rule   | Firestore-distinctive XC - many headless storefronts keep the catalog in Firestore; drift = sync failure. |
        | **High-Latency Requests During Checkout Window (5m)** | Merchant rule   | High-Latency Requests During Checkout Window (5m), broken down by row.                                    |
        | **Realtime Connections vs Traffic Burst**             | Merchant rule   | Realtime Connections vs Traffic Burst, broken down by row.                                                |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across projectdatabas, projectdatabascollectiongroupfields, projectdatabascollectiongroupindexes, projectdatabasoperations, projecttimeserys on Google Firestore. 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=firestore)

    #### Ready to build your first Google Firestore 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                             | Read operations | Write operations |
      | ------------------------------------ | --------------- | ---------------- |
      | projectdatabas                       | 1               | 0                |
      | projectdatabascollectiongroupfields  | 1               | 0                |
      | projectdatabascollectiongroupindexes | 1               | 0                |
      | projectdatabasoperations             | 1               | 0                |
      | projecttimeserys                     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# FreshBooks on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/freshbooks

Monitor FreshBooks payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor FreshBooks payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=freshbooks)

<CardGroup>
  <Card title="10">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (10)">
    ### Monitor performance

    10 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (6 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------ |
        | **AR Aging - 60+ Days**          | Alert band 5 / 15  | Share of total outstanding AR aged 60+ days. The cash least likely to be recovered without escalation. |
        | **AR Aging Buckets**             | Watch only         | Outstanding invoice value bucketed current / 1-30 / 31-60 / 60+ days from due\_date.                   |
        | **Days Sales Outstanding (DSO)** | Alert band 30 / 60 | Average days from invoice issue to payment over trailing 30d. Rising DSO signals collections drag.     |
        | **Expense Total (90d)**          | Watch only         | Total expense.amount over trailing 90d vs the prior period.                                            |
        | **Outstanding AR (live)**        | Watch only         | Sum of invoice.outstanding across sent / partial / overdue invoices - cash you are owed right now.     |
        | **Overdue Invoices**             | Alert band 5 / 15  | Invoices past due\_date in sent / partial / overdue state. Backlog = collections rhythm broken.        |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                        | Alert behaviour   | What it tracks                                                                                               |
        | --------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Ecom Customers Absent from FreshBooks**     | Alert band 0 / 10 | Sync gap - ecom customers invisible to FreshBooks means invoicing/AR runs against an incomplete client list. |
        | **Ecom Orders Missing a FreshBooks Invoice**  | Merchant rule     | Completed ecom orders with no matching FreshBooks invoice = revenue uninvoiced and AR understated.           |
        | **PSP Payments Missing a FreshBooks Payment** | Merchant rule     | Stripe/PayPal payouts not recorded as FreshBooks payments = AR overstated, double-count risk at month-end.   |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                           | Alert behaviour | What it tracks                                                                                  |
        | -------------------------------- | --------------- | ----------------------------------------------------------------------------------------------- |
        | **Uncategorised Expenses (90d)** | Merchant rule   | Expenses with no categoryid in the last 90d - each one makes the quarterly tax estimate harder. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **11 read** and **1 write** operations across account ingaccountbillbills, account ingaccountbillvendorbillvendors, account ingaccountestimateestimates, account ingaccountexpensexpens, account ingaccountinvoiceinvoices, account ingaccountitemitems on FreshBooks. 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=freshbooks)

    #### Ready to build your first FreshBooks 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                | Read operations | Write operations |
      | --------------------------------------- | --------------- | ---------------- |
      | account ingaccountbillbills             | 1               | 0                |
      | account ingaccountbillvendorbillvendors | 1               | 0                |
      | account ingaccountestimateestimates     | 1               | 0                |
      | account ingaccountexpensexpens          | 1               | 0                |
      | account ingaccountinvoiceinvoices       | 1               | 0                |
      | account ingaccountitemitems             | 1               | 0                |
      | account ingaccountpaymentpayments       | 1               | 0                |
      | account ingaccounttaxetaxes             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Freshdesk on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/freshdesk

Monitor Freshdesk pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Freshdesk 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=freshdesk)

<CardGroup>
  <Card title="27">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (27)">
    ### Monitor performance

    27 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour     | What it tracks                                                                                                                                             |
        | ----------------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 2 / 5    | Mean days from first agent action (in-progress) to resolution.                                                                                             |
        | **Avg Lead Time (days)**            | Alert band 5 / 14   | Mean days from created\_at to resolution (full lead time).                                                                                                 |
        | **Avg Time-to-Fix (days)**          | Alert band 5 / 14   | Mean days from filing to Resolved/Closed for Vortex IQ findings.                                                                                           |
        | **Backlog by Priority**             | Alert band 20 / 100 | Backlog by Priority.                                                                                                                                       |
        | **Backlog by Status**               | Merchant rule       | Backlog by Status.                                                                                                                                         |
        | **Blocked Tickets**                 | Alert band 3 / 8    | Tickets in a blocked/on-hold custom status; warn at 3, critical at 8.                                                                                      |
        | **Cycle Time by Priority**          | Alert band 2 / 5    | Cycle Time by Priority.                                                                                                                                    |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50  | resolved\_or\_closed\_findings\_90d / all\_findings\_filed\_90d × 100, anchored on the filing date.                                                        |
        | **In Progress**                     | Merchant rule       | Description pending editorial review; the signal is live.                                                                                                  |
        | **Oldest Open (days)**              | Alert band 14 / 90  | Description pending editorial review; the signal is live.                                                                                                  |
        | **Open Tickets**                    | Alert band 0 / 20   | Description pending editorial review; the signal is live.                                                                                                  |
        | **Overloaded Assignees (>10 open)** | Merchant rule       | Description pending editorial review; the signal is live.                                                                                                  |
        | **SLA Attainment**                  | Alert band 95 / 80  | 100 x (1 - fr\_escalated rate) over tickets created in the window whose first-response SLA clock has already closed (fr\_due\_by in the past). fr\_escalat |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15   | Description pending editorial review; the signal is live.                                                                                                  |
        | **Sprint Progress**                 | Alert band 90 / 70  | Description pending editorial review; the signal is live.                                                                                                  |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20   | Avg tickets resolved per sprint over the trailing 5 sprints.                                                                                               |
        | **Throughput Trend**                | Merchant rule       | Description pending editorial review; the signal is live.                                                                                                  |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25   | Description pending editorial review; the signal is live.                                                                                                  |
        | **Tickets by Assignee**             | Alert band 5 / 10   | Tickets by Assignee.                                                                                                                                       |
        | **Unassigned Tickets**              | Alert band 5 / 20   | Open tickets with no responder\_id; warn at 5, critical at 20.                                                                                             |
        | **VortexIQ Findings In Progress**   | Merchant rule       | Description pending editorial review; the signal is live.                                                                                                  |
        | **VortexIQ Findings Resolved**      | Merchant rule       | Description pending editorial review; the signal is live.                                                                                                  |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                         |
        | ----------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Open Vortex IQ findings whose updated\_at is older than now()-14d - the silent-drain gauge.                            |
        | **Abandoned Findings vs Refund Rate**     | Merchant rule     | Description pending editorial review; the signal is live.                                                              |
        | **High-Value Customer Waiting**           | Merchant rule     | High-Value Customer Waiting, broken down by row.                                                                       |
        | **VortexIQ Findings Open**                | Alert band 5 / 20 | Vortex-IQ-tagged tickets (tag:vortex\_iq, status open/pending) still unresolved - the unactioned-revenue-leak counter. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                        | Alert behaviour     | What it tracks                                                                                                                                             |
        | ----------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **First Response Time (min)** | Alert band 30 / 240 | created\_at to the confirmed real stats.first\_responded\_at field (?include=stats, already fetched for cycle time), converted to minutes. Bare support\_h |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="First-response SLA breached on open conversations">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Breached first-response SLAs compound: late answers create chase messages, which create more queue, which creates later answers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-SLA-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **2 write** operations across tickets, agents, agentmes, groups, searchtickets on Freshdesk. 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=freshdesk)

    #### Ready to build your first Freshdesk 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | tickets       | 1               | 2                |
      | agents        | 1               | 0                |
      | agentmes      | 1               | 0                |
      | groups        | 1               | 0                |
      | searchtickets | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Freshsales on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/freshsales

Monitor Freshsales pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Freshsales 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=freshsales)

<CardGroup>
  <Card title="30">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (30)">
    ### Monitor performance

    30 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                                                                                                                           |
        | -------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of two confirmed real Freshsales Contact fields (via GET /contacts/view/\[view\_id]): share with email populated and share with mobile\_number |
        | **Click-to-Open Rate**     | Alert band 10 / 3  | Clicks / opens - message relevance. Gauge bands: good ≥10%, warn ≤3%.                                                                                    |
        | **Email Click Rate**       | Alert band 2 / 0.5 | Clicks / delivered. Gauge bands: good ≥2%, warn ≤0.5%.                                                                                                   |
        | **Email Open Rate**        | Alert band 20 / 10 | Opens / delivered. Gauge bands: good ≥20%, warn ≤10%.                                                                                                    |
        | **Flow Count Summary**     | Merchant rule      | Total sequences (flows) and how many are active.                                                                                                         |
        | **Flow Trigger Types**     | Merchant rule      | Sequences grouped by trigger type (manual/list-join/segment/deal-stage/property).                                                                        |
        | **Flows List**             | Merchant rule      | Tabular list of sequences with status, trigger and 30d enrollment.                                                                                       |
        | **Lists Overview**         | Merchant rule      | Per-list table: name, type, member count, active members.                                                                                                |
        | **Placed Orders Total**    | Merchant rule      | Orders attributed to email sends in the window (Placed Order metric).                                                                                    |
        | **Segments Overview**      | Merchant rule      | Dynamic segments with member counts and last refresh.                                                                                                    |
        | **Top Lists by Name**      | Merchant rule      | Largest lists ranked by member count.                                                                                                                    |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                                           |
        | ----------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------ |
        | **Campaign Status Breakdown** | Merchant rule   | Count of sales campaigns by status (draft/scheduled/sending/sent/paused/archived).                                       |
        | **Checkout-to-Order Rate**    | Merchant rule   | Of email-driven checkouts started, the share that became orders; reconciled with the ecom sibling's order events.        |
        | **Conversion Rate**           | Merchant rule   | Orders / delivered emails - overall email conversion.                                                                    |
        | **Engagement Funnel**         | Merchant rule   | Sent → delivered → opened → clicked → converted funnel for outbound email.                                               |
        | **List Health Summary**       | Merchant rule   | Active-member share across lists - low = stale/decaying audience.                                                        |
        | **Revenue per Recipient**     | Merchant rule   | Attributed revenue divided by unique recipients.                                                                         |
        | **Revenue per Send**          | Merchant rule   | Attributed revenue divided by total sends.                                                                               |
        | **Total Revenue**             | Merchant rule   | Email-attributed revenue from Freshsales sales campaigns; cross-checked against the ecom sibling's actual order revenue. |
        | **Total Sends**               | Merchant rule   | Total emails sent across sales campaigns in the window.                                                                  |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                        | Alert behaviour      | What it tracks                                                                                                       |
        | ----------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule        | Estimated subscribed/deliverable contacts (subscription\_status = subscribed).                                       |
        | **Bounce Rate**               | Alert band 2 / 5     | Bounces / sent (inverse gauge). Bands: good ≤2%, warn ≥5%. Sustained high = list-hygiene or auth (SPF/DKIM) problem. |
        | **Delivery Rate**             | Alert band 98 / 95   | Delivered / sent. Gauge bands: good ≥98%, warn ≤95%.                                                                 |
        | **Email Health KPIs**         | Merchant rule        | Composite email-health roll-up (delivery, open, click, bounce) in one card.                                          |
        | **Flow Status Breakdown**     | Merchant rule        | Sequences grouped by status (active/paused/draft/archived) - paused-heavy = abandoned automation.                    |
        | **Refund Rate**               | Alert band 1 / 5     | Refunded share of email-attributed revenue - high = post-purchase dissatisfaction or returns leakage.                |
        | **Spam Complaint Rate**       | Alert band 0.1 / 0.3 | Spam reports / delivered (inverse gauge). Bands: good ≤0.1%, warn ≥0.3%. Above 0.3% risks sender-reputation damage.  |
        | **Unsubscribe Rate**          | Alert band 0.5 / 2   | Unsubscribes / delivered (inverse gauge). Bands: good ≤0.5%, warn ≥2%.                                               |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                |
        | --------------------- | --------------- | ------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts started attributed to email activity in the window. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal         | Alert behaviour | What it tracks                                 |
        | -------------- | --------------- | ---------------------------------------------- |
        | **List Count** | Merchant rule   | Total contact lists configured in the account. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **1 write** operations across contacts, contactfilters, contactviews, deals, lists, salecampaigns on Freshsales. 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=freshsales)

    #### Ready to build your first Freshsales 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | contacts       | 1               | 0                |
      | contactfilters | 1               | 0                |
      | contactviews   | 1               | 0                |
      | deals          | 1               | 0                |
      | lists          | 1               | 0                |
      | salecampaigns  | 1               | 0                |
      | sequences      | 1               | 0                |
      | sequencepauses | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Fruugo on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/fruugo

Monitor Fruugo listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Fruugo listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=fruugo)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country**               | Watch only         | AOV by Country.                                                                                                                                        |
        | **Active Country Marketplaces**  | Watch only         | Count of Fruugo country marketplaces this merchant is enabled in (max 46).                                                                             |
        | **Buyer Messages Unread**        | Watch only         | Buyer Messages Unread as exposed by the Fruugo integration. The metric is computed from the latest available data and refreshed on the standard data r |
        | **Days Since Last Payout**       | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Fruugo Merchant Health Score** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments**               | Merchant rule      | Alerts for Late Shipments.                                                                                                                             |
        | **Marketplace Fees Paid**        | Watch only         | Marketplace Fees Paid as exposed by the Fruugo integration. The metric is computed from the latest available data and refreshed on the standard data r |
        | **On-Time Shipping Rate**        | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Orders / Day**                 | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country**            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**              | Watch only         | Pending Payouts as exposed by the Fruugo integration. The metric is computed from the latest available data and refreshed on the standard data refresh |
        | **Pending Shipment**             | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Catalogue quality (8 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                        |
        | ---------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Listings (across all locales)** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Feed Ingestion Success (last 24h)**    | Alert band 90 / 70 | % of feed import lines accepted by Fruugo's twice-daily ingestion. Below 95% = schema or VAT-metadata regression.                                     |
        | **Fruugo Rejected Listings (24h)**       | Alert band 5 / 50  | Alerts for Fruugo Rejected Listings (24h).                                                                                                            |
        | **Listings Expiring Soon**               | Watch only         | Listings Expiring Soon as exposed by the Fruugo integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Listings Missing VAT Metadata**        | Alert band 5 / 50  | Listings missing per-country VAT registration, OSS threshold flags, or HS commodity codes. Fruugo blocks distribution.                                |
        | **Rejected / Reviewing Listings**        | Alert band 5 / 50  | Description pending editorial review; the signal is live.                                                                                             |
        | **Required-Attribute Completeness**      | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                             |
        | **Total Listings**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Order Value**                   | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Fruugo Commission % of Revenue**        | Alert band 12 / 18 | Description pending editorial review; the signal is live.                                                                                              |
        | **Net Revenue (after Fruugo commission)** | Alert band 0 / -5  | Net of Fruugo's 15% commission (paid by merchant, with Fruugo handling VAT remittance for cross-border).                                               |
        | **Orders**                                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue Mix by Country**                | Watch only         | 46-country revenue split , drives shipping zone optimisation + locale-pricing decisions.                                                               |
        | **Revenue Over Time**                     | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Top Listings by Revenue**               | Watch only         | Top Listings by Revenue as exposed by the Fruugo integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Total Revenue**                         | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                            |
        | ----------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------- |
        | **Active Fruugo Listings for OOS SKUs on BC**   | Alert band 0 / 5   | Description pending editorial review; the signal is live.                                                 |
        | **Cancellation Rate**                           | Merchant rule      | Description pending editorial review; the signal is live.                                                 |
        | **Feed Ingestion / VAT-Gap / Cancel Threshold** | Alert band 95 / 85 | Alerts for Feed Ingestion / VAT-Gap / Cancel Threshold.                                                   |
        | **Listings Drifting from BC**                   | Alert band 5 / 50  | Listings Drifting from BC, broken down by row.                                                            |
        | **Listings Failing Feedonomics Validation**     | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                 |
        | **Price Drift vs Amazon EU / eBay EU**          | Merchant rule      | Cross-marketplace EU price coherence , Fruugo's locale-aware pricing vs Amazon/eBay per-country listings. |
        | **Revenue at Risk**                             | Merchant rule      | Description pending editorial review; the signal is live.                                                 |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across products, feedimports, merchants, orders on Fruugo. 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=fruugo)

    #### Ready to build your first Fruugo 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.

    <Accordion title="Browse the operations you can build with">
      | Resource    | Read operations | Write operations |
      | ----------- | --------------- | ---------------- |
      | products    | 1               | 1                |
      | feedimports | 1               | 0                |
      | merchants   | 1               | 0                |
      | orders      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# FullStory on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/fullstory

Monitor traffic, conversion and tracking integrity from FullStory, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from FullStory, and catch instrumentation breaks before decisions are made on bad data.

[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=fullstory)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="14">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                                              | Alert behaviour | What it tracks                                                                                                                                         |
        | --------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Scroll Depth %**                              | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Session Duration**                            | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Goal Completions**                                | Watch only      | Goal Completions from FullStory, grouped under Funnel Analysis. Computes when a live FullStory integration is connected; reconciles ecommerce against  |
        | **Page Load to First Interaction**                  | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Pages per Session**                               | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Replay Capture Coverage %**                       | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Returning Visitor Rate %**                        | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Session Capture Broken (replay count collapsed)** | Merchant rule   | Alerts for Session Capture Broken (replay count collapsed).                                                                                            |
        | **Sessions Captured**                               | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Sessions by Device Type**                         | Watch only      | Sessions by Device Type.                                                                                                                               |
        | **Top Pages**                                       | Watch only      | Top Pages from FullStory, grouped under Customer Behaviour. Computes when a live FullStory integration is connected; reconciles ecommerce against Full |
        | **Top Traffic Sources**                             | Watch only      | Top Traffic Sources from FullStory, grouped under Customer Behaviour. Computes when a live FullStory integration is connected; reconciles ecommerce ag |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                                       | Alert behaviour | What it tracks                                                                                                  |
        | -------------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------- |
        | **Avg Frustration Score**                    | Merchant rule   | FullStory-distinctive composite , the single number for how frustrated visitors are.                            |
        | **Checkout-Path Frustration Spike**          | Merchant rule   | Alerts for Checkout-Path Frustration Spike.                                                                     |
        | **Cursor Thrashing Rate %**                  | Merchant rule   | Erratic mouse movement , a confused or lost visitor.                                                            |
        | **Dead Click Hotspots (by element)**         | Watch only      | Element selectors receiving the most dead clicks , names exactly what to fix.                                   |
        | **Dead Click Rate %**                        | Merchant rule   | Clicks on elements that do nothing , a non-interactive thing looks clickable.                                   |
        | **Error Click Rate %**                       | Merchant rule   | Clicks that trigger a console / JS error , direct evidence of a broken interaction.                             |
        | **Frustration Signal Volume Anomaly**        | Merchant rule   | Alerts for Frustration Signal Volume Anomaly.                                                                   |
        | **FullStory UX Health Score**                | Merchant rule   | Composite: low-frustration x replay-capture-healthy x no-dead-click-hotspots x checkout-path-clean.             |
        | **High-Frustration Sessions (review queue)** | Merchant rule   | Sessions above the frustration threshold , a prioritised replay-review queue.                                   |
        | **Rage Click Rate %**                        | Merchant rule   | FullStory-distinctive , % of sessions with a rage-click event. Rising = a UI element is broken or unresponsive. |
        | **Worst Frustration Pages**                  | Watch only      | Pages ranked by frustration score , names where to focus UX work first.                                         |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                           | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Bounce Rate**                                  | Alert band 40 / 60 | Bounce Rate from FullStory, grouped under Customer Behaviour. Computes when a live FullStory integration is connected; reconciles ecommerce against Fu |
        | **Cart Abandonment Rate**                        | Alert band 60 / 75 | Cart Abandonment Rate from FullStory, grouped under Funnel Analysis. Computes when a live FullStory integration is connected; reconciles ecommerce aga |
        | **Form Abandonment Rate %**                      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **FullStory Session Outcome vs Ecom Conversion** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Landing Page Performance vs Frustration**      | Merchant rule      | Landing Page Performance vs Frustration, broken down by row.                                                                                           |
        | **Session Frustration vs Cart Abandonment**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Session Source vs Ecom Revenue Attribution**   | Merchant rule      | Session Source vs Ecom Revenue Attribution, broken down by row.                                                                                        |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                               | Alert behaviour  | What it tracks                                                                                                                                         |
        | ------------------------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Checkout-Path Frustration Events** | Merchant rule    | Frustration events on cart / checkout pages , direct revenue blockers.                                                                                 |
        | **New Users**                        | Watch only       | New Users from FullStory, grouped under Traffic Acquisition. Computes when a live FullStory integration is connected; reconciles ecommerce against Ful |
        | **Real-Time Users**                  | Watch only       | Real-Time Users from FullStory, grouped under Traffic Acquisition. Computes when a live FullStory integration is connected; reconciles ecommerce again |
        | **Session Conversion Rate**          | Alert band 2 / 1 | Session Conversion Rate from FullStory, grouped under Funnel Analysis. Computes when a live FullStory integration is connected; reconciles ecommerce a |
        | **Sessions**                         | Watch only       | Sessions from FullStory, grouped under Traffic Acquisition. Computes when a live FullStory integration is connected; reconciles ecommerce against Full |
        | **Users**                            | Watch only       | Users from FullStory, grouped under Traffic Acquisition. Computes when a live FullStory integration is connected; reconciles ecommerce against FullSto |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (14)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="API Credentials Invalid">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        With invalid credentials the tool has stopped collecting entirely; every metric that depends on it is silently stale.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS06`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Checkout-Path Frustration">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Frustration signals on the checkout path are as close to watching lost sales happen as analytics gets; each cluster is a prioritised fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS05`
      </Accordion>

      <Accordion title="Session Capture Collapsed">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        A sharp drop in captured events or sessions usually means a tracking break after a site change, not a real traffic collapse; decisions made on the partial data will be wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS01`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Avg Frustration Score Above Baseline">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        A rising average frustration score means the experience is degrading in aggregate even if no single page stands out yet.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS07, FS08`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>

      <Accordion title="Dead-Click Concentration">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Dead clicks concentrated on specific elements mean shoppers believe something is clickable and it is not; each cluster is a small usability fix with real conversion upside.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS03`
      </Accordion>

      <Accordion title="Error-Click Rate Elevated">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Error clicks mean interface actions are visibly failing for real users; each one is a defect with a session recording attached.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS04`
      </Accordion>

      <Accordion title="Rage-Click Rate Spike">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Rage clicks mark moments of user fury at an unresponsive interface; they cluster on the exact elements worth fixing first.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS02`
      </Accordion>

      <Accordion title="Sessions Without Frustration Signals">
        **Severity** low · **Outcome** Customer experience · **Fix status** Report only

        Sessions with no frustration signals at all can indicate instrumentation gaps rather than universal delight; worth confirming the capture is complete.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FS09`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **1 write** operations across eventaggregates, segmentexports, sessions, userindividuals on FullStory. 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=fullstory)

    #### Ready to build your first FullStory 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | eventaggregates | 1               | 0                |
      | segmentexports  | 0               | 1                |
      | sessions        | 1               | 0                |
      | userindividuals | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Cloud Platform on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/gcp

Monitor Google Cloud Platform health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Google Cloud Platform health, cost and reliability signals, and catch incidents and runaway spend early.

[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=gcp)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                   |
        | ------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Projects**             | Watch only         | Count of projects\[] with lifecycleState == ACTIVE from GET /v1/projects.                                                        |
        | **Avg Daily Spend (30d)**       | Watch only         | 30d net\_cost / count of distinct usage days with net\_cost > 0.                                                                 |
        | **Billing Accounts**            | Watch only         | Count of billingAccounts\[] from GET /v1/billingAccounts.                                                                        |
        | **Closed Billing Accounts**     | Watch only         | Count of billingAccounts\[] with open == false; a closed account with live projects stops workloads.                             |
        | **Daily Spend Trend**           | Watch only         | net\_cost summed per usage day over the last 30d of the billing export.                                                          |
        | **GCP Spend (30d)**             | Alert band 10 / 50 | SUM(net\_cost) from the BigQuery billing export (SUM(cost) + credits) where usage date >= 30d ago. Needs billing\_export\_table. |
        | **GCP Spend (7d)**              | Watch only         | SUM(net\_cost) from the billing export where usage date >= 7d ago.                                                               |
        | **Largest Daily Spend (30d)**   | Watch only         | MAX over usage days of the per-day net\_cost sum in the last 30d; spots one-off blowout days.                                    |
        | **Month-to-Date Spend**         | Watch only         | SUM(net\_cost) from the billing export where usage date >= first day of the current month.                                       |
        | **Open Billing Accounts**       | Watch only         | Count of billingAccounts\[] with open == true from GET /v1/billingAccounts.                                                      |
        | **Previous 30d Spend**          | Watch only         | SUM(net\_cost) for usage days 31-60 ago; the comparison base for the spend trend.                                                |
        | **Projects Pending Delete**     | Watch only         | Count of projects\[] with lifecycleState DELETE\_REQUESTED or DELETE\_IN\_PROGRESS; anything here is disappearing in \<=30 days. |
        | **Projects Total**              | Watch only         | Count of projects\[] from GET /v1/projects. Renders with any working service account.                                            |
        | **Projects by Lifecycle State** | Watch only         | projects\[] grouped by lifecycleState from GET /v1/projects.                                                                     |
        | **Service Concentration (30d)** | Watch only         | Top service 30d net\_cost / total 30d net\_cost x 100; how concentrated the bill is in one service.                              |
        | **Spend Spike Alert**           | Alert band 10 / 50 | 30d net\_cost change vs the prior 30d from the billing export; fires on a spike per the ai\_spend\_trend band.                   |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                         |
        | ----------------------------- | --------------- | ------------------------------------------------------------------------------------------------------ |
        | **Active Services (30d)**     | Watch only      | Count of distinct service.description values with net\_cost > 0 in the last 30d of the billing export. |
        | **Cost by Service (30d)**     | Watch only      | net\_cost grouped by service.description over the last 30d of the billing export; top 10 services.     |
        | **Top Service by Cost (30d)** | Watch only      | The single largest service.description by 30d net\_cost; the service name is the card detail.          |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cloud Health Score** | Alert band 90 / 70 | 0-100 composite over whatever is readable: token exchange ok (100) + pct of projects ACTIVE (/v1/projects) + pct of billing accounts open (/v1/billing |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **2 write** operations across https:bigquerygoogleapicombigqueryprojectquerys, https:cloudbillinggoogleapicombillingaccounts, https:oauth2googleapicomtokens, projects on Google Cloud Platform. 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=gcp)

    #### Ready to build your first Google Cloud Platform 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                        | Read operations | Write operations |
      | ----------------------------------------------- | --------------- | ---------------- |
      | https:bigquerygoogleapicombigqueryprojectquerys | 0               | 1                |
      | https:cloudbillinggoogleapicombillingaccounts   | 1               | 0                |
      | https:oauth2googleapicomtokens                  | 0               | 1                |
      | projects                                        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Gemini on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/gemini

Monitor Google Gemini health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Google Gemini health, cost and reliability signals, and catch incidents and runaway spend early.

[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=gemini)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="17">
    proven workflows
  </Card>

  <Card title="1">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Catalogue quality (8 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                                                         |
        | --------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Input Token Limit**         | Watch only         | Mean of inputTokenLimit over models that report one, from /v1beta/models.                                                                              |
        | **Gemini API Health**             | Alert band 90 / 70 | Composite 0-100: 60 for the API being reachable and the key authenticating on /v1beta/models, plus up to 40 for a non-empty model catalogue. No spend  |
        | **Latest Model**                  | Watch only         | displayName (or name) of the model with the highest numeric leading version parsed from the version field across /v1beta/models.                       |
        | **Max Context Window**            | Watch only         | Maximum inputTokenLimit across all models in /v1beta/models (largest input context available).                                                         |
        | **Max Output Tokens**             | Watch only         | Maximum outputTokenLimit across all models in /v1beta/models.                                                                                          |
        | **Model Families**                | Watch only         | Distinct model families from /v1beta/models, grouping name by its family stem (e.g. gemini-2.5, gemini-2.0, gemini-1.5, text-embedding). Counted per f |
        | **Preview / Experimental Models** | Watch only         | Count of models whose name or version contains 'preview' or 'exp' from /v1beta/models (not yet GA).                                                    |
        | **Vision-Capable Models**         | Watch only         | Count of models whose description or displayName matches a multimodal keyword (vision, image, audio, multimodal) from /v1beta/models. Heuristic: Gemin |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                       | Alert behaviour    | What it tracks                                                                                                                                           |
        | ---------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Gemini Spend (30d)**       | Alert band 10 / 50 | Gemini spend is NOT exposed by generativelanguage.googleapis.com; it is billed through Google Cloud. Degrades with reason billing\_via\_gcp unless a lin |
        | **Gemini Usage Trend (30d)** | Alert band 0 / -50 | Gemini request/token usage is NOT exposed by the Gemini API (no usage endpoint). Degrades with reason billing\_via\_gcp unless a linked GCP billing expo |
        | **Models Available**         | Watch only         | Count of entries in GET /v1beta/models the key can see. Renders with any valid Gemini API key.                                                           |
      </Accordion>

      <Accordion title="Customer experience (3 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                                  |
        | -------------------------- | --------------- | ----------------------------------------------------------------------------------------------- |
        | **countTokens Models**     | Watch only      | Count of models whose supportedGenerationMethods includes countTokens, from /v1beta/models.     |
        | **embedContent Models**    | Watch only      | Count of models whose supportedGenerationMethods includes embedContent, from /v1beta/models.    |
        | **generateContent Models** | Watch only      | Count of models whose supportedGenerationMethods includes generateContent, from /v1beta/models. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **0 write** operations across v1betamodels on Google Gemini. 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=gemini)

    #### Proven workflow templates (17)

    <AccordionGroup>
      <Accordion title="Brand Voice Compliance Review">
        **For** Product content manager · **Ready to deploy**

        flags off-brand, unsupported or inconsistent product claims and proposes corrections.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Completeness Guard">
        **For** Product content manager · **Ready to deploy**

        scores required fields by category and routes the highest-revenue gaps first.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Duplicate Copy Resolver">
        **For** Product content manager · **Ready to deploy**

        detects reused descriptions and produces differentiated drafts from verified attributes.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New SKU Content Factory">
        **For** Product content manager · **Ready to deploy**

        turns approved source data into complete draft PDPs with a human review queue.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PDP Enrichment Queue">
        **For** Product content manager · **Ready to deploy**

        finds thin product pages, generates on-brand copy, and batches changes for approval.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Product Claim Evidence Check">
        **For** Product content manager · **Ready to deploy**

        identifies unsubstantiated claims and requires evidence or removal before publish.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Seasonal Content Refresh">
        **For** Product content manager · **Ready to deploy**

        identifies stale seasonal language and prepares date-safe updates with expiry/rollback.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Supplier Copy Normaliser">
        **For** Product content manager · **Ready to deploy**

        converts inconsistent feeds into house style while preserving factual specifications.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Variant Consistency Sweep">
        **For** Product content manager · **Ready to deploy**

        reconciles names, options, specifications and copy across product families.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: OpenAI, DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude)

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource     | Read operations | Write operations |
      | ------------ | --------------- | ---------------- |
      | v1betamodels | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    3 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Ghost on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/ghost

Monitor Ghost publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Ghost publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=ghost)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (9 signals)">
        | Signal                          | Alert behaviour        | What it tracks                                                                                         |
        | ------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------ |
        | **Accessibility Score**         | Alert band 90 / 70     | Description pending editorial review; the signal is live.                                              |
        | **CLS (Mobile)**                | Alert band 0.1 / 0.25  | Description pending editorial review; the signal is live.                                              |
        | **CWV Pass Rate (Mobile)**      | Alert band 75 / 50     | % of mobile origin visits passing all three Core Web Vitals - Google's own ranking-relevant threshold. |
        | **INP (Mobile)**                | Alert band 200 / 500   | Description pending editorial review; the signal is live.                                              |
        | **LCP (Mobile)**                | Alert band 2500 / 4000 | Field LCP at the 75th percentile for mobile readers - the single biggest perceived-speed signal.       |
        | **Performance Score (Desktop)** | Alert band 90 / 50     | Description pending editorial review; the signal is live.                                              |
        | **Performance Score (Mobile)**  | Alert band 90 / 50     | Description pending editorial review; the signal is live.                                              |
        | **Speed Index**                 | Alert band 3400 / 5800 | Description pending editorial review; the signal is live.                                              |
        | **TTFB (Mobile)**               | Alert band 800 / 1800  | Description pending editorial review; the signal is live.                                              |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                        | Alert behaviour              | What it tracks                                                                               |
        | ----------------------------- | ---------------------------- | -------------------------------------------------------------------------------------------- |
        | **Render-Blocking Resources** | Alert band 200 / 500         | Description pending editorial review; the signal is live.                                    |
        | **Total Blocking Time**       | Alert band 200 / 600         | Description pending editorial review; the signal is live.                                    |
        | **Total Page Weight**         | Alert band 1572864 / 3145728 | Total transferred bytes for the page - bloat from third-party scripts and unoptimised media. |
      </Accordion>

      <Accordion title="Run operations (1 signals)">
        | Signal                   | Alert behaviour    | What it tracks                                            |
        | ------------------------ | ------------------ | --------------------------------------------------------- |
        | **Best Practices Score** | Alert band 90 / 70 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal        | Alert behaviour    | What it tracks                                            |
        | ------------- | ------------------ | --------------------------------------------------------- |
        | **SEO Score** | Alert band 90 / 70 | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Site views dropped > 20% vs prior period">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Site views dropping over 20 percent needs a cause before it needs a reaction: seasonality, tracking, or a real ranking loss all look identical at the top line.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-TRAFFIC-001`
      </Accordion>

      <Accordion title="Comment moderation backlog above 20">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A moderation backlog above 20 leaves genuine questions unanswered in public and spam visible on the store's own pages.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-MODERATION-001`
      </Accordion>

      <Accordion title="Over 40% of content not updated in 12 months">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When over 40 percent of content has not been touched in a year, decay outpaces creation; rankings quietly rot page by page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-STALE-001`
      </Accordion>

      <Accordion title="Publishing pipeline stalled (no post in 30 days)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A stalled publishing pipeline slowly starves organic traffic; content compounds only while it keeps shipping.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CMS-PUBLISH-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **0 write** operations across https:chromeuxreportgoogleapicomrecords:queryrecords, runpagespeeds on Ghost. 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=ghost)

    #### Ready to build your first Ghost 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                             | Read operations | Write operations |
      | ---------------------------------------------------- | --------------- | ---------------- |
      | https:chromeuxreportgoogleapicomrecords:queryrecords | 1               | 0                |
      | runpagespeeds                                        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# GitHub on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/github

Monitor GitHub health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor GitHub health, cost and reliability signals, and catch incidents and runaway spend early.

[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=github)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="35">
    proven workflows
  </Card>

  <Card title="1,221">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                       |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Repos (30d)**              | Watch only         | Count of repos with pushed\_at within the last 30d and archived=false.                                                               |
        | **Avg Commits / Active Repo (30d)** | Watch only         | 30d commit count / active-repos-30d; concentration of delivery across the fleet.                                                     |
        | **CI Pass Rate (30d)**              | Alert band 95 / 80 | workflow\_runs with conclusion=success / all completed runs (conclusion not null) created within 30d, x100, across the top 10 repos. |
        | **Languages by Repo Count**         | Watch only         | Repos grouped by their primary language field (nulls skipped), top 10 by count.                                                      |
        | **Median Open PR Age**              | Alert band 3 / 14  | Median of (now - created\_at) in days across all open PRs; drives vc\_pr\_age\_days (lower is better).                               |
        | **Merged PRs (30d)**                | Watch only         | Count of closed PRs with merged\_at within the last 30d (state=closed\&sort=updated) across the top 10 repos.                        |
        | **Most Active Repo (30d)**          | Watch only         | The repo with the most commits in the last 30d; value = commit count, detail = repo full\_name.                                      |
        | **Open Pull Requests**              | Watch only         | Count of open PRs from /repos///pulls?state=open across the top 10 repos.                                                            |
        | **PR Age Alert**                    | Alert band 3 / 14  | Median open-PR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d).                                          |
        | **Releases (30d)**                  | Watch only         | Count of releases with published\_at within the last 30d from /repos///releases across the top 10 repos.                             |
        | **Repositories**                    | Watch only         | Count of repos returned by /user/repos (affiliation=owner,organization\_member).                                                     |
        | **Stale PRs (>14d)**                | Watch only         | Count of open PRs whose age (now - created\_at) exceeds 14 days.                                                                     |
        | **Total Stars**                     | Watch only         | Sum of stargazers\_count across all repos.                                                                                           |
        | **Workflow Runs (30d)**             | Watch only         | Count of Actions workflow\_runs created within the last 30d across the top 10 repos.                                                 |
      </Accordion>

      <Accordion title="Grow revenue (4 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                     |
        | ------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Commits (30d)**         | Alert band 0 / -50 | Count of commits from /repos///commits (author date within 30d) summed across the top 10 repos; change\_pct vs the prior 30d drives vc\_dep        |
        | **Deploy Cadence Trend**  | Alert band 0 / -50 | Daily count of delivery events (commits + releases) over 30d; value = 30d total, change\_pct vs the prior 30d drives vc\_deploy\_cadence.          |
        | **Deploy Stall Alert**    | Alert band 0 / -50 | Delivery-event (commits + releases) change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band.                               |
        | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x CI pass rate + 0.3 x PR-age score (100 at \<=3d, 0 at >=14d) + 0.3 x deploy-cadence score (100 + cadence change\_pct, clam |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                        |
        | ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
        | **Daily Commits Trend** | Watch only      | Commits grouped by day over the last 30d (author date), summed across the top 10 repos.               |
        | **Open Issues**         | Watch only      | Sum of open\_issues\_count across all repos (the field counts issues plus open PRs per the REST API). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CI pass rate below 80%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CI-001`
      </Accordion>

      <Accordion title="Delivery cadence dropped more than 50% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CADENCE-001`
      </Accordion>

      <Accordion title="Median open pull-request age above 14 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-PR-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **637 read** and **584 write** operations across gists, repoissuecomments, repopullcomments, userfollowings, userpackages, userpackageversions on GitHub. 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=github)

    #### Proven workflow templates (35)

    <AccordionGroup>
      <Accordion title="API Contract Drift Watch">
        **For** Developer · **Ready to deploy**

        detects connector or internal schema changes before production failure.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Actionable Incident Triage">
        **For** Developer · **Ready to deploy**

        correlates errors, deploys and affected journeys and opens a pre-filled engineering ticket.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Auth Failure Triage">
        **For** Developer · **Ready to deploy**

        distinguishes expiry, scope, rate limit and upstream outage causes.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Dependency Risk Queue">
        **For** Developer · **Ready to deploy**

        surfaces relevant security/end-of-life updates with compatibility and test guidance.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Failed Job Replay Assistant">
        **For** Developer · **Ready to deploy**

        diagnoses and safely retries idempotent work while escalating unsafe cases.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flaky Test Investigator">
        **For** Developer · **Ready to deploy**

        clusters intermittent failures and ranks likely ownership and root cause.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PR Risk Summary">
        **For** Developer · **Ready to deploy**

        reports affected services, missing tests, operational risk and required approvers.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Performance Regression Bisect">
        **For** Developer · **Ready to deploy**

        correlates release changes with latency and frontend performance shifts.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Safe Fix Branch">
        **For** Developer · **Ready to deploy**

        creates a scoped branch/PR with evidence, tests and rollback notes for an approved issue.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Ticket Builder">
        **For** Developer · **Ready to deploy**

        translates crawl/indexation evidence into reproducible developer work.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Auto-apply Guardrail Approval">
        **For** Security manager · **Ready to deploy**

        requires security sign-off when an automation gains broader write authority.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Blocked Work Escalator">
        **For** Engineering manager · **Ready to deploy**

        detects ageing PRs/tickets and identifies the missing decision or dependency.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Change Failure Rate Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks failed deploys and highlights teams/services with worsening patterns.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Cloud Exposure Watch">
        **For** Security manager · **Ready to deploy**

        detects risky DNS, firewall, storage or edge configuration changes.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Access Review">
        **For** Security manager · **Ready to deploy**

        inventories credentials, scopes, owners, use and age; routes unnecessary access for revocation.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Engineering Dependency Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks vulnerable, unsupported or risky platform dependencies.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Executive Technology Pack">
        **For** Engineering manager · **Ready to deploy**

        translates technical risk and delivery evidence into commercial impact.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Containment Pack">
        **For** Security manager · **Ready to deploy**

        prepares reversible, scoped containment actions for human approval.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Learning Loop">
        **For** Engineering manager · **Ready to deploy**

        creates the timeline, contributing factors, actions and follow-up ownership.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Monthly Security Evidence Pack">
        **For** Security manager · **Ready to deploy**

        retains what changed, who approved it, results and rollback availability.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Privilege Drift Monitor">
        **For** Security manager · **Ready to deploy**

        alerts when repository, cloud or connector permissions exceed policy.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Risk Gate">
        **For** Engineering manager · **Ready to deploy**

        scores change size, test evidence, service health and rollback readiness before approval.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Audit">
        **For** Engineering manager · **Ready to deploy**

        verifies that rollbacks completed and downstream state returned to expected values.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Suspicious Change Correlator">
        **For** Security manager · **Ready to deploy**

        links identity, code, infrastructure and automation audit events.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Integration Risk Review">
        **For** Security manager · **Ready to deploy**

        assesses new connectors before activation and on material permission change.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Vulnerability Remediation Queue">
        **For** Security manager · **Ready to deploy**

        ranks findings by exploitability, exposure and affected revenue paths.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Cloudflare, StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Weekly Delivery and Reliability Brief">
        **For** Engineering manager · **Ready to deploy**

        combines throughput, failed changes, incidents, rollbacks and ageing work.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: Jira Cloud, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Accessibility Regression Sweep">
        **For** Web / digital product manager · **Ready to deploy**

        monitors high-value templates for newly introduced violations.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Broken Experience Prioritiser">
        **For** Web / digital product manager · **Ready to deploy**

        combines errors, traffic and revenue impact into a ranked product backlog.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Conversion Journey Sentinel">
        **For** Web / digital product manager · **Ready to deploy**

        repeatedly tests priority journeys and captures actionable failure evidence.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Core Web Performance Guard">
        **For** Web / digital product manager · **Ready to deploy**

        detects page/template regressions and routes them to the owning team.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Post-release Regression Watch">
        **For** Web / digital product manager · **Ready to deploy**

        compares critical KPIs and technical signals before/after deploy.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Readiness Gate">
        **For** Web / digital product manager · **Ready to deploy**

        checks staging journeys, accessibility, analytics, SEO, performance and rollback readiness.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Recommendation Pack">
        **For** Web / digital product manager · **Ready to deploy**

        assembles evidence and prepares a reversible action when guardrails fail.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Script Risk Watch">
        **For** Web / digital product manager · **Ready to deploy**

        flags new, slow, failing or unapproved scripts and tags.

        Also available on: Azure DevOps, Bitbucket, GitLab

        Tested alongside: StagingPro, Cloudflare, Jira Cloud, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                            | Read operations | Write operations |
      | ----------------------------------- | --------------- | ---------------- |
      | gists                               | 3               | 3                |
      | repoissuecomments                   | 3               | 3                |
      | repopullcomments                    | 3               | 3                |
      | userfollowings                      | 4               | 2                |
      | userpackages                        | 4               | 2                |
      | userpackageversions                 | 4               | 2                |
      | enterpriscodesecurityconfigurations | 2               | 3                |
      | enterpristeams                      | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    5 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# GitLab on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/gitlab

Monitor GitLab health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor GitLab health, cost and reliability signals, and catch incidents and runaway spend early.

[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=gitlab)

<CardGroup>
  <Card title="21">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (21)">
    ### Monitor performance

    21 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                                 | Alert behaviour   | What it tracks                                                                                                     |
        | -------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------ |
        | **Active Projects (30d)**              | Watch only        | Count of projects with last\_activity\_at within the last 30d and archived=false.                                  |
        | **Avg Commits / Active Project (30d)** | Watch only        | 30d commit count / active-projects-30d; concentration of delivery across the fleet.                                |
        | **Daily Commits Trend**                | Watch only        | Commits grouped by day over the last 30d (created\_at), summed across the top 10 projects.                         |
        | **MR Age Alert**                       | Alert band 3 / 14 | Median open-MR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d).                        |
        | **Median Open MR Age**                 | Alert band 3 / 14 | Median of (now - created\_at) in days across all open MRs; drives vc\_pr\_age\_days (lower is better).             |
        | **Merged MRs (30d)**                   | Watch only        | Count of MRs with merged\_at within the last 30d (state=merged\&order\_by=updated\_at) across the top 10 projects. |
        | **Most Active Project (30d)**          | Watch only        | The project with the most commits in the last 30d; value = commit count, detail = path\_with\_namespace.           |
        | **Open Issues**                        | Watch only        | Sum of open\_issues\_count across all projects returned by /projects.                                              |
        | **Open Merge Requests**                | Watch only        | Count of open MRs from /projects//merge\_requests?state=opened across the top 10 projects.                         |
        | **Pipelines Run (30d)**                | Watch only        | Count of pipelines created within the last 30d across the top 10 projects.                                         |
        | **Projects**                           | Watch only        | Count of projects returned by /projects (membership=true).                                                         |
        | **Stale MRs (>14d)**                   | Watch only        | Count of open MRs whose age (now - created\_at) exceeds 14 days.                                                   |
        | **Total Stars**                        | Watch only        | Sum of star\_count across all projects.                                                                            |
      </Accordion>

      <Accordion title="Grow revenue (5 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                                                                                                                      |
        | -------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Commits (30d)**          | Alert band 0 / -50 | Count of commits from /projects//repository/commits (created\_at within 30d) summed across the top 10 projects; change\_pct vs the prior 30d drives |
        | **Deploy Cadence Trend**   | Alert band 0 / -50 | Daily count of commits over 30d; value = 30d total, change\_pct vs the prior 30d drives vc\_deploy\_cadence.                                        |
        | **Deploy Stall Alert**     | Alert band 0 / -50 | Commit-count change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band.                                                       |
        | **Pipeline Health Score**  | Alert band 90 / 70 | 0-100 composite = 0.4 x pipeline success rate + 0.3 x MR-age score (100 at \<=3d, 0 at >=14d) + 0.3 x deploy-cadence score (100 + cadence change\_  |
        | **Projects by Visibility** | Watch only         | Projects grouped by the visibility field (private, internal, public).                                                                               |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                                      |
        | ------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Failed Pipelines (30d)**      | Watch only         | Count of pipelines with status=failed created within the last 30d across the top 10 projects.                                                       |
        | **Pipeline Success Rate (30d)** | Alert band 95 / 80 | Pipelines with status=success / all completed pipelines (status in success, failed, canceled) created within 30d, x100, across the top 10 projects. |
        | **Pipelines by Status (30d)**   | Watch only         | Pipelines created within the last 30d grouped by status field (success, failed, canceled, skipped, etc.) across the top 10 projects.                |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CI pass rate below 80%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CI-001`
      </Accordion>

      <Accordion title="Delivery cadence dropped more than 50% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-CADENCE-001`
      </Accordion>

      <Accordion title="Median open pull-request age above 14 days">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `VC-PR-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across projects, projectmergerequests, projectpipelines, projectrepositorycommits, users on GitLab. 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=gitlab)

    #### Ready to build your first GitLab 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | projects                 | 1               | 0                |
      | projectmergerequests     | 1               | 0                |
      | projectpipelines         | 1               | 0                |
      | projectrepositorycommits | 1               | 0                |
      | users                    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Gmail_Read on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/gmail-read

Monitor Gmail_Read performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Gmail\_Read performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=gmail-read)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="79">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Gmail\_Read yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **30 read** and **49 write** operations across users.messages, users.settings, users.settings.sendas, users.drafts, users.labels, users.settings.cse.keypairs on Gmail\_Read. 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=gmail-read)

    #### Ready to build your first Gmail\_Read 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                      | Read operations | Write operations |
      | ----------------------------- | --------------- | ---------------- |
      | users.messages                | 2               | 9                |
      | users.settings                | 5               | 5                |
      | users.settings.sendas         | 2               | 5                |
      | users.drafts                  | 2               | 4                |
      | users.labels                  | 2               | 4                |
      | users.settings.cse.keypairs   | 2               | 4                |
      | users.threads                 | 2               | 4                |
      | users.settings.cse.identities | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-ads

Monitor Google Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Google Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/google-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=google-ads)

<CardGroup>
  <Card title="65">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (65)">
    ### Monitor performance

    65 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (36 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                            |
        | -------------------------------- | ------------------ | --------------------------------------------------------- |
        | **All Conversions**              | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC by Campaign**              | Watch only         | CPC by Campaign.                                          |
        | **CTR by Campaign**              | Watch only         | CTR by Campaign.                                          |
        | **Campaign Comparison**          | Watch only         | Campaign Comparison, broken down by row.                  |
        | **Clicks vs Conversions**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Conversion Actions Breakdown** | Watch only         | Conversion Actions Breakdown.                             |
        | **Conversion Drop Alert**        | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Conversion Funnel**            | Watch only         | Conversion Funnel, stage by stage.                        |
        | **Conversion Lag**               | Watch only         | Conversion Lag, compared across items.                    |
        | **Conversion Rate Trend**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Conversion Rate by Campaign**  | Watch only         | Conversion Rate by Campaign.                              |
        | **Conversion Rate by Device**    | Watch only         | Conversion Rate by Device.                                |
        | **Conversions Trend**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Conversions by Campaign**      | Watch only         | Conversions by Campaign.                                  |
        | **Conversions by Country**       | Watch only         | Description pending editorial review; the signal is live. |
        | **Conversions by Day of Week**   | Watch only         | Conversions by Day of Week.                               |
        | **Conversions by Device**        | Watch only         | Conversions by Device.                                    |
        | **Conversions by Hour**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Landing Page Revenue**         | Watch only         | Landing Page Revenue, broken down by row.                 |
        | **Overspending Campaigns**       | Merchant rule      | Overspending Campaigns, broken down by row.               |
        | **ROAS**                         | Alert band 3 / 1.5 | Return on ad spend (revenue / cost).                      |
        | **ROAS Trend**                   | Watch only         | Description pending editorial review; the signal is live. |
        | **ROAS by Campaign**             | Watch only         | ROAS by Campaign.                                         |
        | **ROAS by Day of Week**          | Watch only         | ROAS by Day of Week.                                      |
        | **ROAS by Device**               | Watch only         | ROAS by Device.                                           |
        | **ROAS by Region**               | Watch only         | ROAS by Region.                                           |
        | **Revenue by Campaign**          | Watch only         | Revenue by Campaign.                                      |
        | **Search Terms Report**          | Watch only         | Search Terms Report, broken down by row.                  |
        | **Spend by Campaign**            | Watch only         | Spend by Campaign.                                        |
        | **Top Cities by Conversions**    | Watch only         | Top Cities by Conversions.                                |
        | **Top Keywords by Conversions**  | Watch only         | Top Keywords by Conversions.                              |
        | **Top Performing Campaigns**     | Watch only         | Top Performing Campaigns, broken down by row.             |
        | **Total Revenue**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Underspending Campaigns**      | Merchant rule      | Underspending Campaigns, broken down by row.              |
        | **Worst Performing Campaigns**   | Watch only         | Worst Performing Campaigns, broken down by row.           |
        | **Zero-Conversion Spend**        | Alert band 5 / 50  | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Merchant rule      | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Percentage of eligible impressions your ads received.     |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Watch only         | Ad spend trend over the selected period.                  |
        | **Spend vs Budget**            | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Alert band 5 / 50  | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                            |
        | --------------------- | --------------- | --------------------------------------------------------- |
        | **CTR Decline Alert** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Search impression share lost to budget > 20%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Losing more than a fifth of impression share to budget means demand exists that the account cannot buy; either budget or efficiency has to move.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TARGET-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-CREATIVE-001`
      </Accordion>

      <Accordion title="Ghost Campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Enabled campaigns with no spend or delivery are silently dead: the account looks covered while nothing is actually running.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GD05`
      </Accordion>

      <Accordion title="Low ROAS Campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Campaigns running below breakeven ROAS consume budget that profitable campaigns could compound; pausing or restructuring them is found money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GD01`
      </Accordion>

      <Accordion title="Underscaled Branded Search">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Underinvesting in branded search hands the cheapest, highest-intent clicks to competitors bidding on the brand.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GD04`
      </Accordion>

      <Accordion title="Campaign Clutter">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Dozens of tiny fragmented campaigns starve the learning algorithms of data; consolidation typically improves performance with the same spend.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GD03`
      </Accordion>

      <Accordion title="Negative Keyword Candidates (Repeat Non-Converters)">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        Search terms that repeatedly consume spend without converting are negative-keyword candidates; adding them stops the same money leaking every month.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GD06`
      </Accordion>

      <Accordion title="Wasted Keyword Spend">
        **Severity** low · **Outcome** Run operations · **Fix status** Report only

        Keywords that spend without ever converting are the purest form of wasted budget, and the list is exact: these terms, this spend, zero return.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GD02`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **3 write** operations across customer googleads:searchs, customer googleads:searchstreams, tokens on Google Ads. 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=google-ads)

    #### Ready to build your first Google Ads 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                         | Read operations | Write operations |
      | -------------------------------- | --------------- | ---------------- |
      | customer googleads:searchs       | 0               | 1                |
      | customer googleads:searchstreams | 0               | 1                |
      | tokens                           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Analytics on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-analytics

Monitor traffic, conversion and tracking integrity from Google Analytics, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Google Analytics, and catch instrumentation breaks before decisions are made on bad data.

[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=google-analytics)

<CardGroup>
  <Card title="80">
    performance signals
  </Card>

  <Card title="14">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="66">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (80)">
    ### Monitor performance

    80 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (37 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                            |
        | ----------------------------------- | ------------------ | --------------------------------------------------------- |
        | **AI Conversion Rate**              | Merchant rule      | Description pending editorial review; the signal is live. |
        | **AI Engagement**                   | Alert band 30 / 10 | Description pending editorial review; the signal is live. |
        | **AI Revenue**                      | Alert band 1 / 0   | Description pending editorial review; the signal is live. |
        | **AI vs Search Traffic**            | Merchant rule      | AI vs Search Traffic, compared across items.              |
        | **Add-to-Cart Rate**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Average Order Value**             | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Avg Engagement Time per Session** | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Campaign Performance**            | Watch only         | Campaign Performance, compared across items.              |
        | **Checkout Completion Rate**        | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Conversion Rate (Session)**       | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Conversion Rate (User)**          | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Conversion Rate by Device**       | Watch only         | Conversion Rate by Device.                                |
        | **Conversion by Landing Page**      | Watch only         | Conversion by Landing Page.                               |
        | **Conversion by Source**            | Watch only         | Conversion by Source.                                     |
        | **Conversion: New vs Returning**    | Watch only         | Conversion: New vs Returning, compared across items.      |
        | **Engagement Rate**                 | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Organic Search Traffic Share**    | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Organic vs Paid Traffic**         | Watch only         | Organic vs Paid Traffic, shown by share.                  |
        | **Product Brand Revenue**           | Watch only         | Product Brand Revenue, compared across items.             |
        | **Product Conversion Rate**         | Watch only         | Product Conversion Rate, compared across items.           |
        | **Purchases Trend**                 | Watch only         | Description pending editorial review; the signal is live. |
        | **Referral Traffic**                | Watch only         | Referral Traffic, compared across items.                  |
        | **Returning Customer Revenue**      | Watch only         | Description pending editorial review; the signal is live. |
        | **Revenue Trend**                   | Watch only         | GA-attributed revenue trend over time.                    |
        | **Revenue by Category**             | Watch only         | Revenue by Category.                                      |
        | **Revenue by Channel**              | Watch only         | Revenue by Channel.                                       |
        | **Revenue by Country**              | Watch only         | Revenue by Country.                                       |
        | **Revenue by Device**               | Watch only         | Revenue by Device.                                        |
        | **Revenue per Session**             | Watch only         | Description pending editorial review; the signal is live. |
        | **Revenue per User**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Sessions by Channel**             | Watch only         | Sessions by Channel.                                      |
        | **Social Traffic**                  | Watch only         | Social Traffic, compared across items.                    |
        | **Source / Medium**                 | Watch only         | Source / Medium, compared across items.                   |
        | **Top Landing Pages**               | Watch only         | Top Landing Pages, compared across items.                 |
        | **Traffic Trend**                   | Watch only         | Description pending editorial review; the signal is live. |
        | **Unattributed Revenue Share**      | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Users by Channel**                | Watch only         | Users by Channel.                                         |
      </Accordion>

      <Accordion title="Run operations (26 signals)">
        | Signal                                   | Alert behaviour | What it tracks                                            |
        | ---------------------------------------- | --------------- | --------------------------------------------------------- |
        | **AI Traffic Overview**                  | Merchant rule   | Description pending editorial review; the signal is live. |
        | **AI Traffic Trend**                     | Merchant rule   | Description pending editorial review; the signal is live. |
        | **AOV by Device**                        | Watch only      | AOV by Device.                                            |
        | **Active Users by Country**              | Watch only      | Active Users by Country.                                  |
        | **Active Users by Device**               | Watch only      | Active Users by Device.                                   |
        | **Active Users by Source**               | Watch only      | Active Users by Source.                                   |
        | **Average Session Duration**             | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Funnel Drop-off**                      | Watch only      | Funnel Drop-off, compared across items.                   |
        | **Funnel Trend**                         | Watch only      | Description pending editorial review; the signal is live. |
        | **Funnel by Channel**                    | Watch only      | Funnel by Channel.                                        |
        | **Funnel by Device**                     | Watch only      | Funnel by Device.                                         |
        | **New vs Returning Users**               | Watch only      | New vs Returning Users, shown by share.                   |
        | **Page Views**                           | Watch only      | Description pending editorial review; the signal is live. |
        | **Pages per Session**                    | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Purchase Funnel**                      | Watch only      | Purchase Funnel, compared across items.                   |
        | **Purchases by Days Since Last Session** | Watch only      | Purchases by Days Since Last Session.                     |
        | **Real-Time Active Users**               | Watch only      | Description pending editorial review; the signal is live. |
        | **Real-Time Add to Cart**                | Watch only      | Description pending editorial review; the signal is live. |
        | **Real-Time Events Stream**              | Watch only      | Real-Time Events Stream, compared across items.           |
        | **Real-Time Page Views**                 | Watch only      | Description pending editorial review; the signal is live. |
        | **Real-Time Purchases**                  | Watch only      | Description pending editorial review; the signal is live. |
        | **Sessions by Browser**                  | Watch only      | Sessions by Browser.                                      |
        | **Sessions by Device**                   | Watch only      | Sessions by Device.                                       |
        | **Users by City**                        | Watch only      | Users by City.                                            |
        | **Users by Country**                     | Watch only      | Users by Country.                                         |
        | **Users by Language**                    | Watch only      | Users by Language.                                        |
      </Accordion>

      <Accordion title="Catalogue quality (7 signals)">
        | Signal                                 | Alert behaviour | What it tracks                                            |
        | -------------------------------------- | --------------- | --------------------------------------------------------- |
        | **Key Events Configuration Health**    | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Missing Required E-commerce Events** | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Product Cart Additions**             | Watch only      | Product Cart Additions, compared across items.            |
        | **Product Views vs Purchases**         | Watch only      | Product Views vs Purchases, compared across items.        |
        | **Purchase Event Not Seen**            | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Top Products**                       | Watch only      | Top Products, compared across items.                      |
        | **Unattributed Traffic Share**         | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour | What it tracks                                            |
        | ------------------------ | --------------- | --------------------------------------------------------- |
        | **Category Performance** | Watch only      | Category Performance, compared across items.              |
        | **New Users Trend**      | Watch only      | Description pending editorial review; the signal is live. |
        | **Real-Time Checkouts**  | Watch only      | Description pending editorial review; the signal is live. |
        | **Top Events**           | Watch only      | Top Events, compared across items.                        |
        | **Top Pages**            | Watch only      | Top Pages, compared across items.                         |
        | **Total Users**          | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                                     | Alert behaviour | What it tracks                                            |
        | ---------------------------------------------------------- | --------------- | --------------------------------------------------------- |
        | **Bounce Rate**                                            | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Cart Abandonment Rate**                                  | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Desktop vs Mobile Bounce Rate Gap**                      | Merchant rule   | Description pending editorial review; the signal is live. |
        | **High-Bounce Landing Pages (500+ sessions, 60%+ bounce)** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (14)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Conversion Key Events Not Configured">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        The store has real traffic and real users (this check only fires when both are already confirmed present), so this is a tracking gap, not a lack of shoppers. Every revenue-based finding in this dashboard for this property, and any ad channel bidding on GA4 conversion signals, is reading the same pur

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA09`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>

      <Accordion title="Desktop vs Mobile Performance Gap">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        For most stores mobile carries the larger share of sessions, so a device gap this size is not a rounding error, it means the device most shoppers actually use performs worse, and the loss compounds across the largest slice of traffic rather than a minority of it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA02`
      </Accordion>

      <Accordion title="High Bounce Rate Landing Pages">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        These pages already earn meaningful traffic, so the store paid for or earned the click, but more than 6 in 10 visitors leave without looking at a second page. That is spend or organic ranking effort converting into almost nothing, and it is concentrated on named pages rather than spread evenly acros

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA01`
      </Accordion>

      <Accordion title="Low Add-to-Cart Rate">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Add-to-cart is the first real purchase intent signal after a visitor lands, and it moves weeks before a revenue drop would show up anywhere else. A low rate here means people are seeing products without deciding to buy, which points at the product page or the traffic quality, not at checkout.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA05`
      </Accordion>

      <Accordion title="Organic Search Dependency">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Organic search is normally the highest-margin channel because it carries no per-click cost, so a share this low means the store is leaning almost entirely on paid or referral traffic instead. That works until a cost-per-click increase or an ad account issue hits, at which point there is no free-traf

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA06`
      </Accordion>

      <Accordion title="Session Duration Anomaly">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Sessions this short are rarely a real visitor browsing; they usually mean bot or scraper traffic inflating the session count, a tag that fires but under-reports engaged time, or visitors landing on a page that does not match what brought them there. Whichever it is, it distorts every other GA4 metri

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA08`
      </Accordion>

      <Accordion title="Unattributed Revenue">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        This is real revenue GA4 cannot tie to a source, so every other channel's reported return is being calculated against an incomplete revenue base. That understates true ROI and risks a decision to cut a channel that is actually performing, based on numbers that were never seeing its full contribution

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA07`
      </Accordion>

      <Accordion title="Missing E-commerce Events">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        These are the events GA4 and Google Ads use to know a sale happened at all. When they are missing, especially `purchase`, GA4 cannot see revenue that is genuinely occurring, which understates ROAS for every ad channel reading GA4 conversion data and starves automated bid strategies of the signal the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA04`
      </Accordion>

      <Accordion title="Unattributed Traffic">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        A session GA4 cannot tie to a channel is a session that cannot inform which marketing spend is working. As this share grows, every other channel's reported ROI is being measured against a shrinking, skewed slice of true traffic, so budget decisions (which channel to fund, which to cut) are made on i

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GA03`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **29 read** and **37 write** operations across properties, accounts, properties.conversionevents, properties.customdimensions, properties.custommetrics, properties.datastreams.measurementprotocolsecrets on Google Analytics. 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=google-analytics)

    #### Ready to build your first Google Analytics 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                          | Read operations | Write operations |
      | ------------------------------------------------- | --------------- | ---------------- |
      | properties                                        | 9               | 7                |
      | accounts                                          | 3               | 5                |
      | properties.conversionevents                       | 2               | 3                |
      | properties.customdimensions                       | 2               | 3                |
      | properties.custommetrics                          | 2               | 3                |
      | properties.datastreams.measurementprotocolsecrets | 2               | 3                |
      | properties.datastreams                            | 2               | 3                |
      | properties.keyevents                              | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google_Calendar on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-calendar

Monitor Google_Calendar performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Google\_Calendar performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=google-calendar)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="38">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Google\_Calendar yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **11 read** and **27 write** operations across events, acls, calendarlists, calendars, settings, channels on Google\_Calendar. 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=google-calendar)

    #### Ready to build your first Google\_Calendar 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | events        | 3               | 8                |
      | acls          | 2               | 5                |
      | calendarlists | 2               | 5                |
      | calendars     | 1               | 6                |
      | settings      | 2               | 1                |
      | channels      | 0               | 1                |
      | colors        | 1               | 0                |
      | freebusys     | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google_Docs on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-docs

Monitor Google_Docs performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Google\_Docs performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=google-docs)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Google\_Docs yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **2 write** operations across documents on Google\_Docs. 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=google-docs)

    #### Ready to build your first Google\_Docs 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.

    <Accordion title="Browse the operations you can build with">
      | Resource  | Read operations | Write operations |
      | --------- | --------------- | ---------------- |
      | documents | 1               | 2                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google_Drive on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-drive

Monitor Google_Drive performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Google\_Drive performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=google-drive)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="64">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Google\_Drive yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **29 read** and **35 write** operations across files, approvals, drives, comments, permissions, replies on Google\_Drive. 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=google-drive)

    #### Ready to build your first Google\_Drive 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.

    <Accordion title="Browse the operations you can build with">
      | Resource    | Read operations | Write operations |
      | ----------- | --------------- | ---------------- |
      | files       | 7               | 7                |
      | approvals   | 2               | 6                |
      | drives      | 2               | 5                |
      | comments    | 2               | 3                |
      | permissions | 2               | 3                |
      | replies     | 2               | 3                |
      | teamdrives  | 2               | 3                |
      | revisions   | 2               | 2                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google_Merchant_Center on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-merchant-center

Monitor Google_Merchant_Center performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Google\_Merchant\_Center performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=google-merchant-center)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="125">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Google\_Merchant\_Center yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **50 read** and **75 write** operations across accounts, liasettings, datafeeds, pos, shippingsettings, conversionsources on Google\_Merchant\_Center. 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=google-merchant-center)

    #### Ready to build your first Google\_Merchant\_Center 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | accounts          | 4               | 9                |
      | liasettings       | 4               | 7                |
      | datafeeds         | 2               | 5                |
      | pos               | 2               | 5                |
      | shippingsettings  | 5               | 2                |
      | conversionsources | 2               | 4                |
      | products          | 2               | 4                |
      | regions           | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Search Console on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-search-console

Monitor traffic, conversion and tracking integrity from Google Search Console, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Google Search Console, and catch instrumentation breaks before decisions are made on bad data.

[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=google-search-console)

<CardGroup>
  <Card title="70">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (70)">
    ### Monitor performance

    70 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (39 signals)">
        | Signal                            | Alert behaviour | What it tracks                                            |
        | --------------------------------- | --------------- | --------------------------------------------------------- |
        | **Average CTR**                   | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Average Position**              | Merchant rule   | Description pending editorial review; the signal is live. |
        | **CTR Trend**                     | Watch only      | Description pending editorial review; the signal is live. |
        | **CTR by Page**                   | Watch only      | CTR by Page.                                              |
        | **Clicks Trend**                  | Watch only      | Description pending editorial review; the signal is live. |
        | **Clicks by Country**             | Watch only      | Clicks by Country.                                        |
        | **Clicks by Device**              | Watch only      | Clicks by Device.                                         |
        | **Clicks vs Impressions**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Country CTR Comparison**        | Watch only      | Country CTR Comparison, compared across items.            |
        | **Country Growth**                | Watch only      | Country Growth, broken down by row.                       |
        | **Country Position Comparison**   | Watch only      | Country Position Comparison, compared across items.       |
        | **Device Trend**                  | Watch only      | Description pending editorial review; the signal is live. |
        | **High Impressions / Low Clicks** | Watch only      | Description pending editorial review; the signal is live. |
        | **Impressions Trend**             | Watch only      | Description pending editorial review; the signal is live. |
        | **Impressions by Country**        | Watch only      | Impressions by Country.                                   |
        | **Informational Queries**         | Watch only      | Informational Queries, broken down by row.                |
        | **Mobile Ranking Distribution**   | Watch only      | Description pending editorial review; the signal is live. |
        | **Mobile vs Desktop**             | Watch only      | Description pending editorial review; the signal is live. |
        | **New Query Rate**                | Watch only      | New Query Rate over time.                                 |
        | **Page Performance Trend**        | Watch only      | Description pending editorial review; the signal is live. |
        | **Pages Gaining Traffic**         | Watch only      | Pages Gaining Traffic, broken down by row.                |
        | **Pages Losing Traffic**          | Watch only      | Pages Losing Traffic, broken down by row.                 |
        | **Performance by Page Type**      | Watch only      | Description pending editorial review; the signal is live. |
        | **Position by Country**           | Watch only      | Position by Country.                                      |
        | **Position by Device**            | Watch only      | Position by Device.                                       |
        | **Position by Page**              | Watch only      | Position by Page.                                         |
        | **Query Length Trend**            | Watch only      | Description pending editorial review; the signal is live. |
        | **Question Queries**              | Watch only      | Question Queries, broken down by row.                     |
        | **Rich Results CTR**              | Watch only      | Rich Results CTR, compared across items.                  |
        | **Rich Results Impressions**      | Watch only      | Rich Results Impressions, compared across items.          |
        | **Rich Results Performance**      | Watch only      | Rich Results Performance, broken down by row.             |
        | **Search Appearance Trend**       | Watch only      | Description pending editorial review; the signal is live. |
        | **Search Appearance Types**       | Watch only      | Search Appearance Types, shown by share.                  |
        | **Top Pages by Clicks**           | Watch only      | Top Pages by Clicks.                                      |
        | **Top Pages by Impressions**      | Watch only      | Top Pages by Impressions.                                 |
        | **Total Clicks**                  | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Total Impressions**             | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Total Pages Indexed**           | Watch only      | Description pending editorial review; the signal is live. |
        | **Zero-Click Indicators**         | Watch only      | Zero-Click Indicators, broken down by row.                |
      </Accordion>

      <Accordion title="Run operations (19 signals)">
        | Signal                           | Alert behaviour | What it tracks                                            |
        | -------------------------------- | --------------- | --------------------------------------------------------- |
        | **CTR Opportunity Pages**        | Watch only      | CTR Opportunity Pages, broken down by row.                |
        | **CTR Opportunity Queries**      | Watch only      | CTR Opportunity Queries, broken down by row.              |
        | **CTR by Country**               | Watch only      | CTR by Country.                                           |
        | **CTR by Device**                | Watch only      | CTR by Device.                                            |
        | **CTR by Position Bucket**       | Watch only      | CTR by Position Bucket.                                   |
        | **CTR vs Impressions**           | Watch only      | Description pending editorial review; the signal is live. |
        | **Indexed Pages**                | Watch only      | Description pending editorial review; the signal is live. |
        | **Indexing Trend**               | Watch only      | Description pending editorial review; the signal is live. |
        | **Low Impression Pages**         | Watch only      | Low Impression Pages, broken down by row.                 |
        | **Position Change**              | Watch only      | Position Change, broken down by row.                      |
        | **Position Histogram**           | Watch only      | Description pending editorial review; the signal is live. |
        | **Position Trend**               | Watch only      | Description pending editorial review; the signal is live. |
        | **Queries Dropping from Top 10** | Watch only      | Queries Dropping from Top 10, broken down by row.         |
        | **Queries Entering Top 10**      | Watch only      | Queries Entering Top 10, broken down by row.              |
        | **Ranking Volatility**           | Merchant rule   | Ranking Volatility over time.                             |
        | **Ranking by Intent**            | Watch only      | Description pending editorial review; the signal is live. |
        | **Ranking by Page Type**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Sitemap Status**               | Watch only      | Sitemap Status, broken down by row.                       |
        | **Zero-Click Pages**             | Watch only      | Zero-Click Pages, broken down by row.                     |
      </Accordion>

      <Accordion title="Customer experience (10 signals)">
        | Signal                          | Alert behaviour | What it tracks                                            |
        | ------------------------------- | --------------- | --------------------------------------------------------- |
        | **Branded vs Non-Branded**      | Watch only      | Branded vs Non-Branded, shown by share.                   |
        | **Long-Tail Analysis**          | Watch only      | Long-Tail Analysis, compared across items.                |
        | **Low CTR / High Impressions**  | Watch only      | Description pending editorial review; the signal is live. |
        | **New Queries**                 | Watch only      | New Queries, broken down by row.                          |
        | **Queries with Highest CTR**    | Watch only      | Queries with Highest CTR, compared across items.          |
        | **Query Intent Classification** | Watch only      | Query Intent Classification, shown by share.              |
        | **Ranking Distribution**        | Watch only      | Description pending editorial review; the signal is live. |
        | **Rising Queries**              | Watch only      | Rising Queries, broken down by row.                       |
        | **Top Queries by Clicks**       | Watch only      | Top Queries by Clicks.                                    |
        | **Top Queries by Impressions**  | Watch only      | Top Queries by Impressions.                               |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                | Alert behaviour | What it tracks                         |
        | --------------------- | --------------- | -------------------------------------- |
        | **Declining Queries** | Watch only      | Declining Queries, broken down by row. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                                 | Alert behaviour | What it tracks                                          |
        | -------------------------------------- | --------------- | ------------------------------------------------------- |
        | **Title/Meta Optimisation Candidates** | Watch only      | Title/Meta Optimisation Candidates, broken down by row. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Mobile Search Performance Gap">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Ranking worse on mobile than desktop for the same queries points at mobile experience problems, and mobile is where most ecommerce searches happen.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GSC03`
      </Accordion>

      <Accordion title="No Rich Results Detected in Search">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        No rich results means competitors' listings show stars and prices where this store shows plain text on the same results page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GSC04`
      </Accordion>

      <Accordion title="Sitemap(s) With Errors / Warnings">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Candidate remediation

        Sitemap errors mean Google's map of the store is wrong; new products and updates propagate late or not at all.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `GSC05`
      </Accordion>

      <Accordion title="Low Indexing Coverage">
        **Severity** low · **Outcome** Run operations · **Fix status** Report only

        Pages Google has seen but not indexed earn nothing; low coverage usually traces to quality thresholds, redirects or crawl blocks that are fixable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GSC01`
      </Accordion>

      <Accordion title="Pages With High Impressions But < 1% CTR">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        High impressions with under 1 percent click-through means the store is being seen and skipped; titles and snippets on these exact pages are the highest-leverage rewrite list available.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `GSC02`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **6 write** operations across sitemaps, sites, searchanalytics, urlinspection.indexs, urltestingtools.mobilefriendlytests on Google Search Console. 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=google-search-console)

    #### Ready to build your first Google Search Console 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                            | Read operations | Write operations |
      | ----------------------------------- | --------------- | ---------------- |
      | sitemaps                            | 2               | 2                |
      | sites                               | 2               | 2                |
      | searchanalytics                     | 1               | 0                |
      | urlinspection.indexs                | 0               | 1                |
      | urltestingtools.mobilefriendlytests | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Sheets on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-sheets

Monitor Google Sheets publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Google Sheets publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=google-sheets)

<CardGroup>
  <Card title="12">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="17">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (12)">
    ### Monitor performance

    12 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Control risk and change (3 signals)">
        | Signal                      | Alert behaviour      | What it tracks                                                                                                                                          |
        | --------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Empty Field Rate %**      | Alert band 2 / 15    | Share of cells left blank across the read range's data rows, measured against the header row's column count (values.get FORMATTED\_VALUE). Distinct fro |
        | **Error-Cell Rate %**       | Alert band 0 / 1     | Share of read rows containing #REF!/#N/A/#DIV/0!/#VALUE! when rendered FORMATTED\_VALUE. These poison any importer that trusts the cell.                |
        | **Freshness Lag (minutes)** | Alert band 60 / 1440 | Drive files.get modifiedTime -> now, in minutes (the byo\_data\_source archetype's freshness\_lag band is minutes, not hours - same source as Hours Si  |
      </Accordion>

      <Accordion title="Run operations (3 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                                                                         |
        | ----------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Header Schema Drift** | Merchant rule   | Diff of the header row (row 1 of the range) against the last-known-good header signature. Catches renamed/reordered/deleted columns the importer depen |
        | **Populated Rows**      | Watch only      | Non-blank rows in the read range. Track the trend - a sudden drop signals an over-write or truncated export.                                           |
        | **Tab Count**           | Watch only      | Number of tabs (sheets\[]) in the workbook.                                                                                                            |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                        | Alert behaviour | What it tracks                                                                                                                                     |
        | --------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Grid Size (rows × cols)**                   | Watch only      | gridProperties.rowCount × columnCount of the primary tab. Near the 10M-cell workbook ceiling = bloat risk.                                         |
        | **Sheet Price/Cost vs Live Storefront Drift** | Merchant rule   | The pricing/cost master sheet and the live store disagree for the same SKU - either the store is selling at the wrong price or the sheet is stale. |
        | **Sheet SKUs Missing From Catalogue**         | Merchant rule   | SKUs in the source-of-truth sheet that don't exist in the live catalogue - orphaned overrides, typos, or a feed that ran ahead of the store sync.  |
      </Accordion>

      <Accordion title="Catalogue quality (2 signals)">
        | Signal                    | Alert behaviour     | What it tracks                                                                                                        |
        | ------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **Blank-Row Rate %**      | Alert band 2 / 10   | Empty rows inside the populated range - usually deleted-content gaps that break range-based importers.                |
        | **Hours Since Last Edit** | Alert band 24 / 168 | Drive files.get modifiedTime → now. A feed sheet that hasn't moved in a week is almost always a stalled upstream job. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                                  | Alert behaviour     | What it tracks                                                                                                                                |
        | --------------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Source Sheet Not Updated in >7 Days** | Alert band 24 / 168 | Fires when the spreadsheet has not been edited within the expected refresh cadence - the single highest-signal failure mode for a feed sheet. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Data-source API token invalid or access revoked">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this token fails, VortexIQ stops pulling data from this source entirely, and every card and finding built on it 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: `BYO-AUTH-001`
      </Accordion>

      <Accordion title="Source not updated in over 24h (stale data)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        A source that has not updated in over a day means every conclusion drawn from it describes yesterday; the staleness is invisible unless surfaced.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-FRESH-001`
      </Accordion>

      <Accordion title="Required-field empty rate above 15%">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When required fields are empty in more than 15 percent of rows, every downstream calculation inherits the gaps and quietly under-reports.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `BYO-DATA-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **13 write** operations across spreadsheets.values, spreadsheets, spreadsheets.developermetadatas, spreadsheets.sheets on Google Sheets. 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=google-sheets)

    #### Ready to build your first Google Sheets 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                        | Read operations | Write operations |
      | ------------------------------- | --------------- | ---------------- |
      | spreadsheets.values             | 2               | 8                |
      | spreadsheets                    | 1               | 3                |
      | spreadsheets.developermetadatas | 1               | 1                |
      | spreadsheets.sheets             | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Google Tag Manager on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/google-tag-manager

Monitor traffic, conversion and tracking integrity from Google Tag Manager, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Google Tag Manager, and catch instrumentation breaks before decisions are made on bad data.

[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=google-tag-manager)

<CardGroup>
  <Card title="21">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="106">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (21)">
    ### Monitor performance

    21 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | Signal                                              | Alert behaviour | What it tracks                                                                                                                            |
        | --------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
        | **Consent Coverage Gap (pixel firing pre-consent)** | Merchant rule   | Alerts for Consent Coverage Gap (pixel firing pre-consent).                                                                               |
        | **Container Version Count**                         | Watch only      | Description pending editorial review; the signal is live.                                                                                 |
        | **Container Version Status**                        | Merchant rule   | GTM-distinctive - whether the live version is the latest. Unpublished changes = the site isn't measured the way the team thinks.          |
        | **Days Since Last Publish**                         | Watch only      | Description pending editorial review; the signal is live.                                                                                 |
        | **Open Workspaces**                                 | Merchant rule   | Description pending editorial review; the signal is live.                                                                                 |
        | **Paused Tags**                                     | Watch only      | Description pending editorial review; the signal is live.                                                                                 |
        | **Tag Manager Health Score**                        | Merchant rule   | Composite penalising paused tags, unpublished workspace changes, consent gaps, and unused-trigger clutter.                                |
        | **Tags by Type**                                    | Watch only      | Configured tags grouped by GTM tag type (GTM API exposes no per-tag fire counts, so this is a live inventory breakdown, not fire volume). |
        | **Total Tags in Container**                         | Watch only      | Description pending editorial review; the signal is live.                                                                                 |
        | **Total Triggers**                                  | Watch only      | Description pending editorial review; the signal is live.                                                                                 |
        | **Unpublished Workspace Changes**                   | Merchant rule   | Workspace edits not yet published - stale workspaces drift from the live container.                                                       |
        | **Unused Triggers (0 attached tags)**               | Merchant rule   | Triggers attached to no tag - container clutter / cleanup candidates.                                                                     |
        | **Unused Variables (0 references)**                 | Merchant rule   | Description pending editorial review; the signal is live.                                                                                 |
        | **dataLayer Variables**                             | Watch only      | Description pending editorial review; the signal is live.                                                                                 |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                     | Alert behaviour | What it tracks                                                                                                             |
        | ---------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------- |
        | **Consent Coverage vs Marketing Pixels Live**              | Merchant rule   | Consent Coverage vs Marketing Pixels Live, broken down by row.                                                             |
        | **Consent Mode Coverage %**                                | Merchant rule   | GTM-distinctive - share of ad / analytics tags correctly gated behind Consent Mode. Gaps = compliance + data-quality risk. |
        | **Conversion-Tag Fire Count vs Ad-Platform Conversions**   | Merchant rule   | If the GTM conversion tag under-fires vs what the ad platform expects, the merchant is mis-measuring ROAS.                 |
        | **GA4 Config Tag Fires vs GA4 Pageviews**                  | Merchant rule   | Description pending editorial review; the signal is live.                                                                  |
        | **Pixel Parity - GTM Tags vs Ad-Platform Pixels Expected** | Merchant rule   | Pixel Parity - GTM Tags vs Ad-Platform Pixels Expected, broken down by row.                                                |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                             | Alert behaviour | What it tracks                                                                                  |
        | ---------------------------------- | --------------- | ----------------------------------------------------------------------------------------------- |
        | **Tag Consent-State Distribution** | Watch only      | Tag Consent-State Distribution, shown by share.                                                 |
        | **Tags Missing Consent Gating**    | Merchant rule   | Tags with consent\_status = needed\_not\_set - fire before consent. Names exactly which to fix. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Core Web Vitals failing on mobile (LCP > 2.5s OR CLS > 0.1 OR INP > 200ms)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Failing Core Web Vitals on mobile suppresses rankings sitewide and correlates directly with conversion loss; this is the field data Google actually uses.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-CWV-001`
      </Accordion>

      <Accordion title="CWV pass rate below 75% on mobile">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        When fewer than three quarters of sampled pages pass Core Web Vitals, slow experiences are the norm rather than the exception for real visitors.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-CWV-002`
      </Accordion>

      <Accordion title="Lighthouse performance score below 50 on mobile">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        A mobile performance score below 50 means most shoppers meet a visibly slow store; speed is a ranking factor and a conversion factor at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-PERF-001`
      </Accordion>

      <Accordion title="Lighthouse SEO score below 90">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Lighthouse SEO failures are basic crawlability and metadata problems that suppress pages regardless of how good the content is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-SEO-001`
      </Accordion>

      <Accordion title="Lighthouse accessibility score below 90">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        An accessibility score below 90 means common assistive-technology journeys are breaking; lost customers and legal exposure in several markets.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-A11Y-001`
      </Accordion>

      <Accordion title="Render-blocking resources blocking > 500ms">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Render-blocking resources delay the first paint beyond half a second; the store feels slower than it needs to be on every single visit.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-RENDER-001`
      </Accordion>

      <Accordion title="Total page weight above 3 MiB">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Candidate remediation

        Pages heavier than 3 MiB punish mobile and slow-connection shoppers hardest, exactly the visitors with the least patience for it.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `WEBPERF-WEIGHT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **38 read** and **68 write** operations across account s.containers.workspaces, account s.containers, account s.containers.workspaces.folders, account s.containers.versions, account s.containers.workspaces.templates, account s.containers.environments on Google Tag Manager. 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=google-tag-manager)

    #### Ready to build your first Google Tag Manager 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                  | Read operations | Write operations |
      | ----------------------------------------- | --------------- | ---------------- |
      | account s.containers.workspaces           | 3               | 8                |
      | account s.containers                      | 4               | 5                |
      | account s.containers.workspaces.folders   | 2               | 6                |
      | account s.containers.versions             | 2               | 5                |
      | account s.containers.workspaces.templates | 2               | 5                |
      | account s.containers.environments         | 2               | 4                |
      | account s.containers.workspaces.clients   | 2               | 4                |
      | account s.containers.workspaces.tags      | 2               | 4                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Gorgias on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/gorgias

Monitor Gorgias pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Gorgias 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=gorgias)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                        |
        | ----------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                             |
        | **Avg Lead Time (days)**            | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                             |
        | **Avg Time-to-Fix (days)**          | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                             |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                                                  |
        | **Backlog by Status**               | Merchant rule      | Backlog by Status.                                                                                                                                    |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Open tickets tagged blocked / waiting-on-customer - the operational queue's stuck list.                                                               |
        | **Cycle Time by Priority**          | Alert band 3 / 5   | Cycle Time by Priority.                                                                                                                               |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings filed in the last 90d actually got fixed via Gorgias. Healthy band on Gorgias is higher (>75%) thanks to inline order    |
        | **In Progress**                     | Merchant rule      | Open tickets with an assignee and recent activity - work actively being handled.                                                                      |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Age in days of the oldest still-open ticket - backlog-rot signal.                                                                                     |
        | **Open Tickets**                    | Alert band 0 / 100 | Total open tickets across the connected storefronts - top-of-funnel backlog volume.                                                                   |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | Agents with >10 open tickets - capacity bottleneck candidates.                                                                                        |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                             |
        | **Sprint Progress**                 | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                             |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20  | Sprint Velocity (avg) over time.                                                                                                                      |
        | **Throughput Trend**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                                                                             |
        | **Tickets by Assignee**             | Alert band 5 / 10  | Tickets by Assignee.                                                                                                                                  |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                             |
        | **VortexIQ Findings In Progress**   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **VortexIQ Findings Open**          | Alert band 5 / 20  | Tickets we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced, in the same inbox as live shopper |
        | **VortexIQ Findings Resolved**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                        |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no team movement for two weeks - these are the ones losing money silently while the team works live shopper queries. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="First-response SLA breached on open conversations">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Breached first-response SLAs compound: late answers create chase messages, which create more queue, which creates later answers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-SLA-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **3 write** operations across tickets, accounts, integrations, ticketmessages, users on Gorgias. 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=gorgias)

    #### Ready to build your first Gorgias 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | tickets        | 2               | 2                |
      | accounts       | 1               | 0                |
      | integrations   | 1               | 0                |
      | ticketmessages | 0               | 1                |
      | users          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Grafana on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/grafana

Monitor Grafana health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Grafana health, cost and reliability signals, and catch incidents and runaway spend early.

[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=grafana)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (10 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                                          |
        | ---------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Alert band 0 / 5             | Description pending editorial review; the signal is live.                                               |
        | **Alerts Firing**            | Alert band 0 / 5             | Grafana-managed alert instances currently in the Alerting state.                                        |
        | **Incidents Open**           | Alert band 0 / 3             | Description pending editorial review; the signal is live.                                               |
        | **Incidents Resolved (24h)** | Alert band 0 / -1            | Description pending editorial review; the signal is live.                                               |
        | **Mean Time To Acknowledge** | Alert band 300000 / 1800000  | Mean elapsed time from incident creation to first acknowledgement - gated on the Grafana Incident plan. |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Description pending editorial review; the signal is live.                                               |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Description pending editorial review; the signal is live.                                               |
        | **Services Degraded**        | Alert band 0 / 2             | Description pending editorial review; the signal is live.                                               |
        | **Services Healthy**         | Alert band 0 / -1            | Description pending editorial review; the signal is live.                                               |
        | **Top Alerting Services**    | Alert band 0 / 5             | Services ranked by firing-alert count over the window - where the noise concentrates.                   |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour        | What it tracks                                                                                 |
        | ------------------------ | ---------------------- | ---------------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.94 / 0.85 | Apdex(t) computed from request-duration histogram in PromQL - good below 0.85 is unacceptable. |
        | **Avg Response Time**    | Alert band 200 / 1000  | Description pending editorial review; the signal is live.                                      |
        | **Error Rate**           | Alert band 0.5 / 2     | 5xx / errored requests as a share of total, from PromQL via the data-source proxy.             |
        | **Throughput (req/min)** | Alert band 0 / -30     | Throughput (req/min) over time.                                                                |
        | **p95 Latency**          | Alert band 800 / 1500  | Description pending editorial review; the signal is live.                                      |
        | **p99 Latency**          | Alert band 1500 / 3000 | Description pending editorial review; the signal is live.                                      |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                              | Alert behaviour  | What it tracks                                                                                                       |
        | ----------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Services Down × Revenue at Risk** | Alert band 0 / 1 | Down services joined to a commerce sibling's revenue/min baseline - turns 'a service is down' into '\$/min on fire'. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour  | What it tracks                                                                |
        | ------------------- | ---------------- | ----------------------------------------------------------------------------- |
        | **Top Error Types** | Alert band 0 / 5 | Error classes ranked by count via LogQL/PromQL through the data-source proxy. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **1 write** operations across alertmanagergrafanaalerts, alertmanagergrafanaalertgroups, dquerys, datasources, incidents, prometheugrafanarules on Grafana. 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=grafana)

    #### Ready to build your first Grafana 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                       | Read operations | Write operations |
      | ------------------------------ | --------------- | ---------------- |
      | alertmanagergrafanaalerts      | 1               | 0                |
      | alertmanagergrafanaalertgroups | 1               | 0                |
      | dquerys                        | 0               | 1                |
      | datasources                    | 1               | 0                |
      | incidents                      | 1               | 0                |
      | prometheugrafanarules          | 1               | 0                |
      | provisioningalertrules         | 1               | 0                |
      | searchs                        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Height on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/height

Monitor Height performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Height performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=height)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (24 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**                   | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Lead Time (days)**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Time-to-Fix (days)**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Backlog by Priority**                     | Merchant rule      | Backlog by Priority.                                                                                                                                   |
        | **Backlog by Status**                       | Watch only         | Backlog by Status.                                                                                                                                     |
        | **Blocked Tickets**                         | Alert band 3 / 8   | Tasks flagged blocked / impeded - the operational queue's stuck list.                                                                                  |
        | **Critical Findings Without a Height Task** | Merchant rule      | Critical / high audit findings older than 7 days with no Height task - coverage gap. Auto-dispatch missed these or the merchant disabled it; either wa |
        | **Cycle Time by Priority**                  | Merchant rule      | Cycle Time by Priority.                                                                                                                                |
        | **Finding Resolution Rate (90d)**           | Alert band 75 / 50 | Share of audit findings actually fixed via the Height pipeline. \<50% means we're filing faster than the team drains. Height runs 5-12 pts higher th   |
        | **Finding-to-Task Dispatch Lag**            | Merchant rule      | How fast we get findings into Height after detection. Slow dispatch = cold leads by the time the ops team sees them.                                   |
        | **In Progress**                             | Watch only         | Tasks with status.state = started - work actively in flight.                                                                                           |
        | **Oldest Open (days)**                      | Merchant rule      | Age of the longest-running open task - backlog-rot signal.                                                                                             |
        | **Open Tickets**                            | Merchant rule      | Total open tasks across the connected workspace - top-of-funnel backlog volume.                                                                        |
        | **Overloaded Assignees (>10 open)**         | Alert band 0 / 1   | People with >10 open tasks - capacity bottleneck candidates.                                                                                           |
        | **Scope Added Mid-Sprint**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Sprint Progress**                         | Alert band 80 / 50 | Active-cycle burn - uses Height Cycles, the workspace must have Cycles enabled.                                                                        |
        | **Sprint Velocity (avg)**                   | Merchant rule      | Sprint Velocity (avg) over time.                                                                                                                       |
        | **Throughput Trend**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets Resolved (7d)**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets by Assignee**                     | Merchant rule      | Tickets by Assignee.                                                                                                                                   |
        | **Unassigned Tickets**                      | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings In Progress**           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings Open**                  | Merchant rule      | Tasks we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced. Calibrated 20% looser than Jira beca |
        | **VortexIQ Findings Resolved**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                           |
        | ----------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Open Height tasks with vortexiq\_finding\_id set, not completed, and lastActivityAt older than 14 days - findings losing money silently. Copilot-accepte |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **3 write** operations across tasks, lists, activitys, fieldtemplates, taskcomments, users on Height. 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=height)

    #### Ready to build your first Height 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | tasks          | 2               | 2                |
      | lists          | 2               | 0                |
      | activitys      | 1               | 0                |
      | fieldtemplates | 1               | 0                |
      | taskcomments   | 0               | 1                |
      | users          | 1               | 0                |
      | workspaces     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Help Scout on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/helpscout

Monitor Help Scout pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Help Scout 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=helpscout)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                        |
        | ----------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                             |
        | **Avg Lead Time (days)**            | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                             |
        | **Avg Time-to-Fix (days)**          | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                             |
        | **Backlog by Priority**             | Merchant rule      | Help Scout has no native priority field - priority is derived from priority/urgency workflow tags.                                                    |
        | **Backlog by Status**               | Merchant rule      | Backlog by Status.                                                                                                                                    |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Pending conversations carrying a blocked/waiting-on workflow tag - the operational queue's stuck list. Warn at >3, critical at >8.                    |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                                               |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings filed in the last 90d actually got fixed via the Help Scout pipeline. Anchored on the filing date; \<50% means we file   |
        | **In Progress**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Description pending editorial review; the signal is live.                                                                                             |
        | **Open Tickets**                    | Alert band 0 / 100 | Total active+pending conversations across the connected mailboxes - top-of-funnel backlog volume.                                                     |
        | **Overloaded Assignees (>10 open)** | Merchant rule      | People with >10 open conversations - capacity bottleneck candidates.                                                                                  |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                             |
        | **Sprint Progress**                 | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                             |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20  | Sprint Velocity (avg) over time.                                                                                                                      |
        | **Throughput Trend**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                                                                             |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                                                  |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Active conversations with no assignee - work nobody owns. Warn at >5, critical at >20.                                                                |
        | **VortexIQ Findings In Progress**   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **VortexIQ Findings Open**          | Alert band 5 / 20  | Conversations we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced. Refreshed every 60 seconds. |
        | **VortexIQ Findings Resolved**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
      </Accordion>

      <Accordion title="Customer experience (2 signals)">
        | Signal                        | Alert behaviour     | What it tracks                                                                                                                                          |
        | ----------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **CSAT**                      | Alert band 90 / 70  | GET /v2/reports/happiness - greatCount / ratingsCount \* 100 (share of rated conversations customers marked Great, the two/three-tier Great/Okay/Not Go |
        | **First Response Time (min)** | Alert band 30 / 240 | Confirmed real GET /v2/reports/productivity field firstResponseTime (seconds), converted to minutes. Same fetch this manifest already uses for cycle/l  |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                           |
        | ----------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently. Warn at >5, critical at >15. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **3 write** operations across conversations, conversationnotes, mailboxes, report companys, report conversations, report happiness on Help Scout. 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=helpscout)

    #### Ready to build your first Help Scout 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | conversations        | 1               | 2                |
      | conversationnotes    | 0               | 1                |
      | mailboxes            | 1               | 0                |
      | report companys      | 1               | 0                |
      | report conversations | 1               | 0                |
      | report happiness     | 1               | 0                |
      | report productivitys | 1               | 0                |
      | tags                 | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Evri (formerly Hermes UK) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/hermes-evri

Monitor Evri (formerly Hermes UK) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Evri (formerly Hermes UK) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=hermes-evri)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                                                                                                                  |
        | ------------------------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live.                                                                                       |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                                                                                                                   |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                       |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                                |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Lost-Parcel Rate**            | Merchant rule    | % of shipments resulting in a lost-parcel claim. Evri's historical reputation - if the rate is climbing, time to renegotiate or switch carrier. |
        | **OTD by Route**                | Watch only       | OTD by Route.                                                                                                                                   |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.                                                                                              |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live.                                                                                       |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live.                                                                                       |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                                                                                                           |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Evri OTD by Sales Channel**        | Alert band 95 / 90 | Per-channel Evri OTD.                                                                                                                                  |
        | **Failed Deliveries**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **ParcelShop Drop-off Failure Rate** | Merchant rule      | Evri-specific failure mode - the courier never picks up from the ParcelShop, leaving the parcel in limbo. Below 97% means specific shops need flagging |
        | **Redelivery Attempts > 3**          | Merchant rule      | Evri's multi-attempt delivery cap. Anything past 3 attempts = a parcel returning to sender. Each row is a refund + customer trust hit.                 |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                            |
        | ------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live. |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live. |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live. |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **1 write** operations across tbds on Evri (formerly Hermes UK). 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=hermes-evri)

    #### Ready to build your first Evri (formerly Hermes UK) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 2               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Hotjar on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/hotjar

Monitor traffic, conversion and tracking integrity from Hotjar, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Hotjar, and catch instrumentation breaks before decisions are made on bad data.

[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=hotjar)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="11">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (10 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                             |
        | --------------------------- | ------------------ | ------------------------------------------------------------------------------------------ |
        | **Goal Completions**        | Alert band 0 / -15 | Count of completed Hotjar goals - direct conversion-event volume.                          |
        | **New Users**               | Alert band 0 / -25 | First-time visitors - acquisition health for the period.                                   |
        | **Pageviews per Session**   | Alert band 3 / 1.5 | Pages viewed per session - depth of browsing before exit.                                  |
        | **Real-Time Users**         | Alert band 0 / -25 | Visitors active in the most recent polled window - a near-live activity pulse.             |
        | **Returning Users**         | Alert band 0 / -25 | Repeat visitors - loyalty / retention signal for the period.                               |
        | **Session Conversion Rate** | Alert band 2 / 1   | Share of sessions that complete a goal - the headline conversion gauge.                    |
        | **Sessions**                | Alert band 0 / -25 | Total Hotjar sessions captured in the window - the denominator for every behavioural rate. |
        | **Top Pages**               | Alert band 0 / -15 | Highest-traffic pages by sessions - where attention concentrates.                          |
        | **Top Traffic Sources**     | Alert band 0 / -15 | Highest-volume referral sources - where visitors arrive from.                              |
        | **Users**                   | Alert band 0 / -25 | Distinct visitors captured by Hotjar in the window.                                        |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                   |
        | ----------------------------------------- | ------------------ | -------------------------------------------------------------------------------- |
        | **Avg Session Duration**                  | Alert band 0 / -15 | Average time per session - falling duration is an early engagement-leak signal.  |
        | **Bounce Rate**                           | Alert band 40 / 60 | Share of single-page sessions - high values flag landing-page / intent mismatch. |
        | **Cart Abandonment Rate**                 | Alert band 60 / 75 | Share of carts started but not completed - rising values name a checkout leak.   |
        | **High-Bounce Pages vs Cart Abandonment** | Merchant rule      | Description pending editorial review; the signal is live.                        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (11)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="API Credentials Invalid">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        With invalid credentials the tool has stopped collecting entirely; every metric that depends on it is silently stale.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `HOT05`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Session Capture Collapsed">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        A sharp drop in captured events or sessions usually means a tracking break after a site change, not a real traffic collapse; decisions made on the partial data will be wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `HOT01`
      </Accordion>

      <Accordion title="Session Conversion Rate Below Floor">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Session conversion below the floor while traffic holds means the store is buying visits it cannot convert; the cause is usually specific and findable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `HOT03`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce Rate Spike">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A bounce-rate spike after a release or campaign change is the earliest cheap warning that something on the landing experience broke.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `HOT02`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>

      <Accordion title="Cart Abandonment Climbing">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Climbing cart abandonment concentrates revenue loss at the final step; shipping surprises, payment friction and errors are the usual culprits.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `HOT04`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **0 write** operations across siteinsightgoals, siteinsightpages, siteinsightsessions, siteinsightsources on Hotjar. 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=hotjar)

    #### Ready to build your first Hotjar 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | siteinsightgoals    | 1               | 0                |
      | siteinsightpages    | 1               | 0                |
      | siteinsightsessions | 1               | 0                |
      | siteinsightsources  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# HubSpot on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/hubspot

Monitor email revenue and deliverability for HubSpot, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for HubSpot, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=hubspot)

<CardGroup>
  <Card title="74">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="16">
    proven workflows
  </Card>

  <Card title="424">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (74)">
    ### Monitor performance

    74 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (31 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Subscribers (Est.)**             | Watch only         | Estimated subscribed, reachable contacts.                                                                                                              |
        | **Active Workflows**                      | Watch only         | Active Workflows from HubSpot, grouped under Email Automation. Computes when a live HubSpot integration is connected; reconciles ecommerce against Hub |
        | **Average Deal Cycle (days)**             | Watch only         | Average Deal Cycle (days) from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce agains |
        | **Companies**                             | Watch only         | Companies from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce against HubSpot data.  |
        | **Contact Lifecycle Stage Distribution**  | Watch only         | % of contacts at each lifecyclestage (subscriber/lead/MQL/SQL/opportunity/customer/evangelist). Shapes funnel investment.                              |
        | **Deal Pipeline by Stage**                | Watch only         | Open deal value grouped by dealstage. Surfaces stage-bottlenecks visually.                                                                             |
        | **Deal Win Rate (30d)**                   | Merchant rule      | % of closed deals that were won. Below 20% = either deal-qualification problem OR pipeline noise from unqualified leads.                               |
        | **Deals Closing This Month**              | Watch only         | Deals Closing This Month from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce against |
        | **Deals Closing in Next 14 Days**         | Watch only         | Deals Closing in Next 14 Days from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce ag |
        | **Email Open Rate**                       | Alert band 25 / 15 | Share of delivered emails opened. iOS Mail Privacy inflates this, pair with click-to-open for a truer read.                                            |
        | **Flow Count Summary**                    | Watch only         | How many automations exist on the account.                                                                                                             |
        | **Flow Status Breakdown**                 | Watch only         | Automations split by status (live, draft, paused).                                                                                                     |
        | **Flow Trigger Types**                    | Watch only         | Automations grouped by what triggers them.                                                                                                             |
        | **Flows List**                            | Watch only         | Every automation and its current status.                                                                                                               |
        | **Form Submissions (30D)**                | Watch only         | Form Submissions (30D) from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce against H |
        | **List Health Summary**                   | Watch only         | Total reachable members across all lists.                                                                                                              |
        | **New Contacts (period)**                 | Watch only         | New Contacts (period) from HubSpot, grouped under Customer Lifecycle. Computes when a live HubSpot integration is connected; reconciles ecommerce agai |
        | **Open Deal Pipeline Value**              | Watch only         | Sum of `amount` across all open deals. Top-level CRM health metric - drives forecast.                                                                  |
        | **Pipeline Drop Alert**                   | Watch only         | Pipeline Drop Alert from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce against HubS |
        | **Placed Orders Total**                   | Watch only         | Orders attributed to email in the window.                                                                                                              |
        | **Predictive Contact Score Distribution** | Watch only         | Predictive Contact Score Distribution from HubSpot, grouped under Customer Lifecycle. Computes when a live HubSpot integration is connected; reconcile |
        | **SQLs (Sales Qualified Leads)**          | Watch only         | SQLs (Sales Qualified Leads) from HubSpot, grouped under Customer Lifecycle. Computes when a live HubSpot integration is connected; reconciles ecommer |
        | **Segments Overview**                     | Watch only         | Saved segments and their sizes.                                                                                                                        |
        | **Top 10 Deals by Amount**                | Watch only         | Top 10 Deals by Amount from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce against H |
        | **Top Companies by Deal Value**           | Watch only         | Top Companies by Deal Value from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce agai |
        | **Top Customers Without HubSpot Contact** | Watch only         | Top Customers Without HubSpot Contact from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecom |
        | **Top Forms by Submission Volume**        | Watch only         | Top Forms by Submission Volume from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce a |
        | **Top Workflows by Enrolments**           | Watch only         | Top Workflows by Enrolments from HubSpot, grouped under Email Automation. Computes when a live HubSpot integration is connected; reconciles ecommerce  |
        | **Total Contacts**                        | Watch only         | Total Contacts from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce against HubSpot d |
        | **Workflow Enrollments (30d)**            | Watch only         | Top workflows ranked by 30d enrollment count. Quick health check on automation activity.                                                               |
        | **Workflow Stopped Enrolling (>24h)**     | Merchant rule      | Alerts for Workflow Stopped Enrolling (>24h).                                                                                                          |
      </Accordion>

      <Accordion title="Grow revenue (27 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Campaign Status Breakdown**                  | Watch only         | Campaigns grouped by status (sent, draft, scheduled).                                                                                                  |
        | **Checkout-to-Order Rate**                     | Watch only         | Share of started checkouts that became paid orders.                                                                                                    |
        | **Click-to-Open Rate**                         | Alert band 10 / 3  | Clicks as a share of opens, engagement quality independent of open-rate inflation.                                                                     |
        | **Conversion Rate**                            | Watch only         | Orders as a share of emails sent. Ties send volume to revenue.                                                                                         |
        | **Deal Close-Won Without Matching Ecom Order** | Merchant rule      | Revenue-recognition gap - sales marks deal won but no ecom transaction posts. Either CRM data entry error or ecom integration drift.                   |
        | **Deals Stuck >30d in Current Stage**          | Merchant rule      | Deals with hs\_lastmodifieddate >30d ago = stalled revenue. Either close or kill.                                                                      |
        | **Email Click Rate**                           | Alert band 3 / 1   | Share of delivered emails that earned a click. The clearest engagement signal.                                                                         |
        | **Email Send Volume (trend)**                  | Watch only         | Email Send Volume (trend) from HubSpot, grouped under Email & Marketing. Computes when a live HubSpot integration is connected; reconciles ecommerce a |
        | **Email Unsubscribe Rate**                     | Alert band 0.5 / 2 | Email Unsubscribe Rate from HubSpot, grouped under Email & Marketing. Computes when a live HubSpot integration is connected; reconciles ecommerce agai |
        | **Engagement Funnel**                          | Watch only         | Sent to delivered to opened to clicked, showing where engagement drops off.                                                                            |
        | **Lead → MQL Conversion %**                    | Watch only         | Lead → MQL Conversion % from HubSpot, grouped under Customer Lifecycle. Computes when a live HubSpot integration is connected; reconciles ecommerce ag |
        | **List Count**                                 | Watch only         | Number of audiences on the account.                                                                                                                    |
        | **Lists Overview**                             | Watch only         | Every audience with its member count.                                                                                                                  |
        | **MQL → SQL Conversion Rate (30d)**            | Merchant rule      | % of marketing-qualified leads advanced to sales-qualified within 30 days. Low = MQL scoring too generous OR sales team not actioning.                 |
        | **MQLs (Marketing Qualified Leads)**           | Watch only         | MQLs (Marketing Qualified Leads) from HubSpot, grouped under Customer Lifecycle. Computes when a live HubSpot integration is connected; reconciles eco |
        | **MQLs Not Advanced After 60d**                | Merchant rule      | MQLs that hit the stage >60d ago but never advanced = cold leads. Re-engagement candidates or pipeline removal.                                        |
        | **Marketing Emails Sent**                      | Watch only         | Marketing Emails Sent from HubSpot, grouped under Email & Marketing. Computes when a live HubSpot integration is connected; reconciles ecommerce again |
        | **Pipeline-vs-Realised Revenue Gap**           | Watch only         | Pipeline-vs-Realised Revenue Gap from HubSpot, grouped under CRM Pipeline. Computes when a live HubSpot integration is connected; reconciles ecommerce |
        | **Revenue per Recipient**                      | Watch only         | Revenue divided by emails sent. What each address is worth per send.                                                                                   |
        | **Revenue per Send**                           | Watch only         | Revenue divided by emails sent, the efficiency of each send.                                                                                           |
        | **SQL → Customer Conversion Rate (30d)**       | Merchant rule      | % of sales-qualified leads converted to customer. Cleanest sales-side performance signal.                                                              |
        | **Top Emails by Clicks (90D)**                 | Watch only         | Top Emails by Clicks (90D) from HubSpot, grouped under Email & Marketing. Computes when a live HubSpot integration is connected; reconciles ecommerce  |
        | **Top Lists by Name**                          | Watch only         | Largest audiences by member count.                                                                                                                     |
        | **Total Revenue**                              | Watch only         | Placed-order revenue attributed to email sends. The hero number.                                                                                       |
        | **Total Sends**                                | Watch only         | Total emails sent across campaigns in the window.                                                                                                      |
        | **Workflow-Triggered Commerce Revenue**        | Watch only         | Workflow-Triggered Commerce Revenue from HubSpot, grouped under Email Automation. Computes when a live HubSpot integration is connected; reconciles ec |
        | **Workflows Blocked / Stale**                  | Merchant rule      | Enabled workflows with last\_enrolled\_at >24h ago = trigger criteria broken or contact-property rename. Investigate before next campaign goes out.    |
      </Accordion>

      <Accordion title="Protect revenue (13 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Bounce Rate**                             | Alert band 2 / 5   | Share of sends that bounced. Rising bounces hurt sender reputation.                                                                                    |
        | **Contact Properties Missing vs Ecom Data** | Merchant rule      | Contact records that exist in HubSpot but missing core CRM properties (name, lifecycle, lead\_status) yet have ecom purchase history. Sync gap to fix. |
        | **Deal Pipeline vs Repeat Ecom Orders**     | Merchant rule      | Repeat customers on ecom side = open expansion opportunities. If HubSpot deals aren't tracking them, sales team is missing the signal.                 |
        | **Delivery Rate**                           | Alert band 98 / 95 | Share of sends accepted by the inbox provider. Below 95% needs attention.                                                                              |
        | **Email Deliverability Drop**               | Alert band 0 / -5  | Email Deliverability Drop from HubSpot, grouped under Nerve Centre. Computes when a live HubSpot integration is connected; reconciles ecommerce agains |
        | **Email Health KPIs**                       | Watch only         | Delivered, bounced and unsubscribed at a glance, your deliverability vitals.                                                                           |
        | **Email-Attributed Commerce Revenue**       | Watch only         | Email-Attributed Commerce Revenue from HubSpot, grouped under Cross-Channel: Revenue at Risk. Computes when a live HubSpot integration is connected; r |
        | **Hard Bounce Spike on Email Send**         | Merchant rule      | HubSpot suspends sends when bounces sustained - escalate to list cleanup.                                                                              |
        | **Lifecycle Stage vs Ecom Revenue**         | Merchant rule      | Reveals lifecycle mis-classification - customers stuck at MQL despite paid orders, or 'customers' with no actual revenue.                              |
        | **MQL → Paid Customer Funnel**              | Merchant rule      | Full MQL → SQL → opportunity → customer (with first ecom purchase) funnel. Drops anywhere expose where the GTM funnel is leaking.                      |
        | **Refund Rate**                             | Watch only         | Share of attributed orders later refunded.                                                                                                             |
        | **Spam Complaint Rate**                     | Merchant rule      | Spam complaints per send. Above 0.1% puts deliverability at risk.                                                                                      |
        | **Unsubscribe Rate**                        | Alert band 0.3 / 1 | Unsubscribes per send. A spike signals list fatigue or off-target content.                                                                             |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                    | Alert behaviour | What it tracks                                                                                                                                         |
        | ------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Workflow Error Spike**  | Watch only      | Workflow Error Spike from HubSpot, grouped under Email Automation. Computes when a live HubSpot integration is connected; reconciles ecommerce against |
        | **Workflows With Errors** | Watch only      | Workflows With Errors from HubSpot, grouped under Email Automation. Computes when a live HubSpot integration is connected; reconciles ecommerce agains |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Watch only      | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **97 read** and **327 write** operations across crmobjects, crmobjectassociations, crmobjectassociationdefaults, cmblogauthors, cmblogposts, cmblogtags on HubSpot. 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=hubspot)

    #### Proven workflow templates (16)

    <AccordionGroup>
      <Accordion title="Back-in-stock Opportunity Queue">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies high-intent customers and prepares consent-safe notifications.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Preflight Gate">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        validates segment, exclusions, consent, links, stock, offer dates and tracking before send approval.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Deliverability and List Health Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        monitors bounce, complaint, suppression and engagement shifts with safe remediation advice.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flow Performance Decay Watch">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        detects lifecycle automations whose engagement or revenue has materially deteriorated.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Frequency Pressure Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies over-contacted customers across campaigns and flows.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Segment Drift Monitor">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        flags unexpected audience growth/shrinkage or overlap before it damages sends.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Issue Triage">
        **For** Customer service manager · **Ready to deploy**

        enriches tickets with order, payment and fulfilment context and assigns the right queue.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Proactive Delay List">
        **For** Customer service manager · **Ready to deploy**

        prepares, but does not send, customer communications for affected orders.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: Klaviyo, Dotdigital, Mailchimp, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | crmobjects                   | 5               | 12               |
      | crmobjectassociations        | 3               | 12               |
      | crmobjectassociationdefaults | 0               | 6                |
      | cmblogauthors                | 2               | 3                |
      | cmblogposts                  | 2               | 3                |
      | cmblogtags                   | 2               | 3                |
      | cmhubdbtablerowdrafts        | 2               | 3                |
      | cmpagelandingpages           | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    24 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Insightly on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/insightly

Monitor Insightly pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Insightly 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=insightly)

<CardGroup>
  <Card title="33">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (33)">
    ### Monitor performance

    33 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                                                                          |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated active (non-opted-out) subscribers across Insightly lists.                                                                                    |
        | **CRM Data Hygiene Score**    | Alert band 95 / 80 | Composite of two confirmed real Insightly Contact fields: share with EMAIL\_ADDRESS populated and share with PHONE populated. A genuine multi-field com |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Clicks / delivered across sends in the window.                                                                                                          |
        | **Email Open Rate**           | Alert band 20 / 10 | Opens / delivered across sends in the window.                                                                                                           |
        | **Flow Status Breakdown**     | Merchant rule      | Active / paused / draft / archived split across flows - surfaces dormant automation.                                                                    |
        | **Flow Trigger Types**        | Merchant rule      | Distribution of flows by trigger type (date / property / list-add).                                                                                     |
        | **Flows List**                | Merchant rule      | Every flow with status and enrolment count for automation review.                                                                                       |
        | **List Count**                | Merchant rule      | Total number of Insightly email lists.                                                                                                                  |
        | **Lists Overview**            | Merchant rule      | Every list with member counts and freshness for hygiene review.                                                                                         |
        | **Placed Orders Total**       | Merchant rule      | Orders placed attributed to Insightly outreach in the window.                                                                                           |
        | **Segments Overview**         | Merchant rule      | Dynamic segments and their sizes - surfaces segments that have collapsed to empty.                                                                      |
        | **Stalled Deal Rate**         | Alert band 10 / 30 | Share of OPEN opportunities with no linked Insightly Event (call/meeting) in the last 14 days - joined via the confirmed real EVENTLINKS.OPPORTUNITY\_I |
        | **Top Lists by Name**         | Merchant rule      | Largest lists by member count - where send volume concentrates.                                                                                         |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                      | Alert behaviour      | What it tracks                                                                                                 |
        | ------------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------- |
        | **Bounce Rate**                             | Alert band 2 / 5     | Bounced / sent. Above 5% signals list rot or reputation damage.                                                |
        | **Click-to-Open Rate**                      | Alert band 10 / 3    | Clicks / opens - message-relevance signal independent of deliverability.                                       |
        | **Delivery Rate**                           | Alert band 98 / 95   | Delivered / sent. Below 95% is a deliverability problem.                                                       |
        | **Email Health KPIs**                       | Merchant rule        | Roll-up of open / click / bounce / unsubscribe into a single health pulse.                                     |
        | **Engaged Contacts with Zero Ecom Revenue** | Merchant rule        | Contacts your email is reaching and engaging but who never buy - the nurture-to-revenue leak.                  |
        | **Refund Rate**                             | Alert band 2 / 8     | Refunded / attributed orders - quality check on outreach-driven revenue.                                       |
        | **Spam Complaint Rate**                     | Alert band 0.1 / 0.3 | Spam complaints / delivered. Above 0.3% risks sender blocklisting.                                             |
        | **Unsubscribe Rate**                        | Alert band 0.5 / 2   | Unsubscribes / delivered. Above 2% means content-audience mismatch.                                            |
        | **Won Opportunities Missing Ecom Order**    | Merchant rule        | Sales marked the deal won but no ecom transaction posted - revenue-recognition gap or off-platform fulfilment. |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                          |
        | ----------------------------- | --------------- | ----------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule   | Draft / scheduled / sending / sent / archived split across campaigns.   |
        | **Checkout-to-Order Rate**    | Merchant rule   | Orders / checkouts started - closing efficiency of attributed sessions. |
        | **Conversion Rate**           | Merchant rule   | Orders / recipients attributed to Insightly outreach.                   |
        | **Engagement Funnel**         | Merchant rule   | Sent → delivered → opened → clicked → converted funnel for the window.  |
        | **List Health Summary**       | Merchant rule   | Composite list-hygiene read - growth vs churn vs opt-out across lists.  |
        | **Revenue per Recipient**     | Merchant rule   | Attributed revenue / unique recipients - list monetisation efficiency.  |
        | **Revenue per Send**          | Merchant rule   | Attributed revenue / emails sent - the headline send-economics metric.  |
        | **Total Revenue**             | Merchant rule   | Total revenue attributed to Insightly email in the window.              |
        | **Total Sends**               | Merchant rule   | Total emails sent across campaigns in the window.                       |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                      |
        | --------------------- | --------------- | ------------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts initiated attributed to Insightly outreach in the window. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour | What it tracks                                    |
        | ---------------------- | --------------- | ------------------------------------------------- |
        | **Flow Count Summary** | Merchant rule   | Total automation flows configured on the account. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **2 write** operations across opportunitys, contacts, emails, events, flows, lists on Insightly. 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=insightly)

    #### Ready to build your first Insightly 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | opportunitys  | 1               | 1                |
      | contacts      | 1               | 0                |
      | emails        | 1               | 0                |
      | events        | 1               | 0                |
      | flows         | 1               | 0                |
      | lists         | 1               | 0                |
      | listmembers   | 0               | 1                |
      | organisations | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Instagram on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/instagram

Monitor Instagram publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Instagram publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=instagram)

<CardGroup>
  <Card title="28">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (28)">
    ### Monitor performance

    28 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (16 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                |
        | ----------------------------- | ------------------ | ----------------------------------------------------------------------------- |
        | **Accounts Engaged (30d)**    | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Comments (30d)**            | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Engagement Drop Alert**     | Alert band 3 / 1   | Description pending editorial review; the signal is live.                     |
        | **Engagement Rate**           | Alert band 3 / 1   | (likes + comments) on recent posts / followers, averaged over the window.     |
        | **Engagement Rate Trend**     | Alert band 3 / 1   | Description pending editorial review; the signal is live.                     |
        | **Engagement-to-Conversion**  | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Followers Trend**           | Alert band 0 / -2  | Description pending editorial review; the signal is live.                     |
        | **Following**                 | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Likes (30d)**               | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Posting Cadence**           | Alert band 0 / -40 | Description pending editorial review; the signal is live.                     |
        | **Profile Views (30d)**       | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Reach Trend**               | Alert band 0 / -20 | Description pending editorial review; the signal is live.                     |
        | **Social Health Score**       | Alert band 90 / 70 | Composite: engagement rate x reach trend x posting cadence x follower growth. |
        | **Social-Attributed Revenue** | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Top Posts by Engagement**   | Watch only         | Top Posts by Engagement.                                                      |
        | **Total Engagement (30d)**    | Watch only         | Description pending editorial review; the signal is live.                     |
      </Accordion>

      <Accordion title="Run operations (7 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Days Since Last Post**       | Alert band 0 / -40 | Description pending editorial review; the signal is live. |
        | **Followers**                  | Alert band 0 / -2  | Description pending editorial review; the signal is live. |
        | **Reach (30d)**                | Alert band 0 / -20 | Description pending editorial review; the signal is live. |
        | **Reach Drop Alert**           | Alert band 0 / -20 | Description pending editorial review; the signal is live. |
        | **Social-Attributed Sessions** | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Posts Driving Traffic**  | Watch only         | Top Posts Driving Traffic, broken down by row.            |
        | **Total Posts**                | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                    | Alert behaviour | What it tracks                                            |
        | ------------------------- | --------------- | --------------------------------------------------------- |
        | **Avg Comments per Post** | Watch only      | Description pending editorial review; the signal is live. |
        | **Avg Likes per Post**    | Watch only      | Description pending editorial review; the signal is live. |
        | **Content Type Mix**      | Watch only      | Image / Video / Carousel / Reels split of recent posts.   |
        | **Posts Published Trend** | Watch only      | Description pending editorial review; the signal is live. |
        | **Saves (30d)**           | Watch only      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Engagement rate below 1%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Engagement below 1 percent means content is reaching feeds and being scrolled past; format and hook need work before spend goes behind it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-ENGAGEMENT-001`
      </Accordion>

      <Accordion title="Reach dropped > 20% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Reach dropping over 20 percent usually means the algorithm has deprioritised the account or a format change landed badly; catching it early keeps the slide shallow.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-REACH-001`
      </Accordion>

      <Accordion title="Posting cadence collapsed (no post in 14 days)">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Posting cadence collapsing to zero lets the audience's attention lapse; reach compounds only while the account stays present.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-CADENCE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **0 write** operations across businessaccounts, insights, medias on Instagram. 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=instagram)

    #### Ready to build your first Instagram 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | businessaccounts | 1               | 0                |
      | insights         | 1               | 0                |
      | medias           | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Intercom on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/intercom

Monitor Intercom pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Intercom 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=intercom)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="150">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                | Alert behaviour   | What it tracks                                                                                |
        | ------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------- |
        | **Avg Replies per Conversation**      | Watch only        | Back-and-forth depth: high means unclear answers or complex issues.                           |
        | **Conversation Volume Trend**         | Watch only        | Description pending editorial review; the signal is live.                                     |
        | **New Conversations Today**           | Watch only        | Description pending editorial review; the signal is live.                                     |
        | **New vs Closed**                     | Merchant rule     | Description pending editorial review; the signal is live.                                     |
        | **Oldest Open Conversation**          | Merchant rule     | Age (hours) of the oldest still-open conversation.                                            |
        | **Open Backlog Trend**                | Alert band 0 / 20 | Description pending editorial review; the signal is live.                                     |
        | **Open Conversations**                | Alert band 0 / 20 | Description pending editorial review; the signal is live.                                     |
        | **Open Tickets**                      | Merchant rule     | Description pending editorial review; the signal is live.                                     |
        | **SLA Breaches (live)**               | Alert band 0 / 5  | Alerts for SLA Breaches (live).                                                               |
        | **Snoozed Conversations**             | Watch only        | Description pending editorial review; the signal is live.                                     |
        | **Top Topics (Tags)**                 | Merchant rule     | Top Topics (Tags), compared across items.                                                     |
        | **Unanswered (awaiting first reply)** | Merchant rule     | Open conversations with no admin reply yet, waiting\_since older than the first-response SLA. |
        | **Unassigned Open Conversations**     | Merchant rule     | Description pending editorial review; the signal is live.                                     |
        | **Volume Spike**                      | Merchant rule     | Description pending editorial review; the signal is live.                                     |
        | **Volume by Channel**                 | Watch only        | By source.type (email, chat, messenger, etc.).                                                |
      </Accordion>

      <Accordion title="Customer experience (14 signals)">
        | Signal                             | Alert behaviour       | What it tracks                                                                    |
        | ---------------------------------- | --------------------- | --------------------------------------------------------------------------------- |
        | **CSAT**                           | Alert band 90 / 70    | % positive conversation\_rating (4-5★) over rated conversations in the window.    |
        | **CSAT Drop Alert**                | Alert band 90 / 70    | Description pending editorial review; the signal is live.                         |
        | **CSAT Trend**                     | Alert band 90 / 70    | Description pending editorial review; the signal is live.                         |
        | **CSAT by Agent**                  | Alert band 90 / 70    | CSAT by Agent.                                                                    |
        | **Conversation Volume by Hour**    | Watch only            | Hour-of-day (0-23) breakdown of when conversations are created - drives staffing. |
        | **Conversations Handled by Agent** | Watch only            | Conversations Handled by Agent.                                                   |
        | **First-Response SLA Attainment**  | Alert band 95 / 80    | Description pending editorial review; the signal is live.                         |
        | **First-Response Time by Team**    | Alert band 30 / 240   | First-Response Time by Team.                                                      |
        | **Median Resolution Time**         | Alert band 240 / 1440 | Minutes from created\_at to close (statistics.time\_to\_last\_close), median.     |
        | **Negative-Rated Conversations**   | Merchant rule         | Negative-Rated Conversations, broken down by row.                                 |
        | **Rating Response Rate**           | Watch only            | Description pending editorial review; the signal is live.                         |
        | **Reopen Rate**                    | Alert band 5 / 15     | % of closed conversations reopened (state went closed→open) in the window.        |
        | **Resolution Time by Agent**       | Alert band 240 / 1440 | Resolution Time by Agent.                                                         |
        | **Workload by Team**               | Watch only            | Workload by Team.                                                                 |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                               | Alert behaviour | What it tracks                                            |
        | ------------------------------------ | --------------- | --------------------------------------------------------- |
        | **Complaints on Out-of-Stock SKUs**  | Merchant rule   | Complaints on Out-of-Stock SKUs, broken down by row.      |
        | **High-Value Customer Waiting**      | Merchant rule   | High-Value Customer Waiting, broken down by row.          |
        | **Support Contacts per 100 Orders**  | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Support Spike on Failed Payments** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                         | Alert behaviour     | What it tracks                                                                                         |
        | ------------------------------ | ------------------- | ------------------------------------------------------------------------------------------------------ |
        | **Median First-Response Time** | Alert band 30 / 240 | Minutes to first admin reply (conversation.statistics.time\_to\_admin\_reply), median over the window. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                   | Alert behaviour    | What it tracks                                                                      |
        | ------------------------ | ------------------ | ----------------------------------------------------------------------------------- |
        | **Support Health Score** | Alert band 90 / 70 | Composite: SLA attainment x CSAT x (inverse) backlog growth x first-response speed. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="First-response SLA breached on open conversations">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Breached first-response SLAs compound: late answers create chase messages, which create more queue, which creates later answers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-SLA-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **67 read** and **83 write** operations across aicontentimportsources, aiexternalpages, articles, companys, contacts, conversations on Intercom. 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=intercom)

    #### Ready to build your first Intercom 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | aicontentimportsources | 2               | 3                |
      | aiexternalpages        | 2               | 3                |
      | articles               | 2               | 3                |
      | companys               | 2               | 3                |
      | contacts               | 2               | 3                |
      | conversations          | 2               | 3                |
      | customobjectinstances  | 2               | 3                |
      | helpcentercollections  | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Interlink Express on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/interlink-express

Monitor Interlink Express delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Interlink Express delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=interlink-express)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                            |
        | ------------------------------- | ---------------- | --------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live. |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                             |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live. |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.          |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live. |
        | **OTD by Route**                | Watch only       | OTD by Route.                                             |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live. |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.        |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                     |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                                      |
        | ------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                           |
        | **Pre-10:30 Service Promise**   | Alert band 95 / 90 | % of Pre-10:30 consignments delivered before 10:30am - the contracted Interlink premium-service promise. Customers paid uplift; misses double-hurt. |
        | **Pre-12 Service Promise**      | Alert band 95 / 90 | % of Pre-12 consignments delivered before noon.                                                                                                     |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                            |
        | ---------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Failed Deliveries**              | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Interlink OTD by Sales Channel** | Alert band 95 / 90 | Per-channel Interlink Express OTD.                        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **1 write** operations across tbds on Interlink Express. 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=interlink-express)

    #### Ready to build your first Interlink Express 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 2               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Iterable on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/iterable

Monitor email revenue and deliverability for Iterable, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Iterable, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=iterable)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (12 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                      |
        | ----------------------------- | ------------------ | ----------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule      | Campaigns grouped by state (Draft, Scheduled, Running, Finished).                   |
        | **Checkout-to-Order Rate**    | Alert band 70 / 50 | Share of started checkouts that became paid orders.                                 |
        | **Click-to-Open Rate**        | Alert band 10 / 3  | Clicks as a share of opens - engagement quality independent of open-rate inflation. |
        | **Conversion Rate**           | Alert band 3 / 1   | Purchases as a share of emails sent. Ties send volume to revenue.                   |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Unique clicks over delivered. The clearest engagement signal.                       |
        | **List Count**                | Merchant rule      | Number of audiences on the account.                                                 |
        | **Lists Overview**            | Merchant rule      | Every audience with its member count.                                               |
        | **Revenue per Recipient**     | Merchant rule      | Revenue divided by emails sent - what each address is worth per send.               |
        | **Revenue per Send**          | Merchant rule      | Revenue divided by emails sent - the efficiency of each send.                       |
        | **Top Lists by Name**         | Merchant rule      | Largest audiences by member count.                                                  |
        | **Total Revenue**             | Merchant rule      | Placed-order revenue Iterable attributes to email sends in the conversion window.   |
        | **Total Sends**               | Merchant rule      | Total emails sent across campaigns in the window.                                   |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                     |
        | -------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------- |
        | **Abandoned-Cart Recovery Value**      | Merchant rule        | Currency recovered per 30D by the abandoned-cart journey. Goes to zero if the journey is disabled. |
        | **Bounce Rate**                        | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation.                                |
        | **Delivery Rate**                      | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                          |
        | **Email Health KPIs**                  | Merchant rule        | Delivered, bounced and unsubscribed at a glance - your deliverability vitals.                      |
        | **Email Share of Total Store Revenue** | Merchant rule        | Healthy DTC ranges 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk.   |
        | **Engagement Funnel**                  | Merchant rule        | Sent -> Delivered -> Opened -> Clicked. Drop-offs expose deliverability vs content weakness.       |
        | **Refund Rate**                        | Alert band 2 / 8     | Share of attributed orders later refunded.                                                         |
        | **Spam Complaint Rate**                | Alert band 0.1 / 0.3 | Complaints per send. Above 0.1% Gmail/Yahoo start marking the sender domain.                       |
        | **Unsubscribe Rate**                   | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.                         |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                        |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts.                                             |
        | **Email Open Rate**           | Alert band 20 / 10 | Unique opens over delivered. iOS Mail Privacy inflates this; pair with click-to-open. |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                             |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to email in the window.                                             |
        | **Segments Overview**         | Merchant rule      | Saved segments and their sizes.                                                       |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                    | Alert behaviour | What it tracks                                                |
        | ------------------------- | --------------- | ------------------------------------------------------------- |
        | **Checkouts Started**     | Merchant rule   | Checkouts begun from email clicks, where Iterable reports it. |
        | **Flow Count Summary**    | Merchant rule   | How many journeys exist on the account.                       |
        | **Flow Status Breakdown** | Merchant rule   | Journeys split by enabled vs disabled.                        |
        | **Flow Trigger Types**    | Merchant rule   | Journeys grouped by what triggers them.                       |
        | **Flows List**            | Merchant rule   | Every Iterable journey and its current status.                |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="API key missing required permissions">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        When the key lacks read access, 20+ cards silently render "No data yet" and the merchant cannot diagnose without our logs. The audit surfaces exactly which read scope to enable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ITE06`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001, ITE03`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Spam Complaint Rate too high">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ITE02`
      </Accordion>

      <Accordion title="Email Bounce Rate too high">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ITE01`
      </Accordion>

      <Accordion title="Inactive workflows (disabled journeys)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ITE04`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited lists / segmentation">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ITE05`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **4 write** operations across campaigns, campaign metrics, channels, exportdatajsons, lists, listgetusers on Iterable. 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=iterable)

    #### Ready to build your first Iterable 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | campaigns        | 1               | 0                |
      | campaign metrics | 1               | 0                |
      | channels         | 1               | 0                |
      | exportdatajsons  | 1               | 0                |
      | lists            | 1               | 0                |
      | listgetusers     | 1               | 0                |
      | listsubscribes   | 0               | 1                |
      | listunsubscribes | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Japan Post (EMS / Yu-Pack) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/japan-post

Monitor Japan Post (EMS / Yu-Pack) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Japan Post (EMS / Yu-Pack) delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=japan-post)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                                                    | Alert behaviour  | What it tracks                                                                                                                             |
        | --------------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Error Rate**                                        | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Avg Shipping Cost**                                     | Merchant rule    | Description pending editorial review; the signal is live.                                                                                  |
        | **Claim Value (open)**                                    | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Cool Yu-Pack (Chilled/Frozen) Volume**                  | Watch only       | Cool Yu-Pack (chilled / frozen) shipment volume. Peak winter / Oshogatsu (New Year, Jan 1-3) drives massive volume spikes.                 |
        | **Cool Yu-Pack Temperature Alert OR Dispatch SLA Breach** | Merchant rule    | Cool Yu-Pack temperature breaks are P0 (product safety) , escalate above standard dispatch-SLA alerts.                                     |
        | **Cost Per Shipment Trend**                               | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Cost by Zone**                                          | Watch only       | Cost by Zone.                                                                                                                              |
        | **Days to Token Expiry**                                  | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **EMS CN23 Customs Document Generation Failure Rate**     | Merchant rule    | % of CN23 (international customs declaration) auto-generation calls failing. Manual fallback delays EMS exports by 1-2 days at JP customs. |
        | **Exception Rate**                                        | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                  |
        | **High-Cost Shipment Outliers**                           | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                           |
        | **Label / Customs Doc Print Failures Spike**              | Alert band 0 / 5 | Alerts for Label / Customs Doc Print Failures Spike.                                                                                       |
        | **Label Generation Success**                              | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **OTD by Route**                                          | Watch only       | OTD by Route.                                                                                                                              |
        | **Open Claims**                                           | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Returned to Sender**                                    | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Route Volume Concentration**                            | Merchant rule    | Route Volume Concentration, compared across items.                                                                                         |
        | **Shipments**                                             | Merchant rule    | Description pending editorial review; the signal is live.                                                                                  |
        | **Shipments Over Time**                                   | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Shipments by Destination**                              | Watch only       | Description pending editorial review; the signal is live.                                                                                  |
        | **Shipments by Service**                                  | Watch only       | Shipments by Service.                                                                                                                      |
        | **Yu-Pack Cost by Prefecture Zone**                       | Watch only       | Japan Post prices Yu-Pack by prefecture-zone. Annual March review can reclassify prefectures.                                              |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                                        | Alert behaviour   | What it tracks                                                                                                                           |
        | ------------------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Cool Yu-Pack Temperature-Track Gaps**                       | Merchant rule     | Cool Yu-Pack shipments with gaps in temperature telemetry. Chilled/frozen line breaks compromise product integrity , perishable risk.    |
        | **Failed Deliveries**                                         | Merchant rule     | Description pending editorial review; the signal is live.                                                                                |
        | **Orders with Dispatch SLA Missed**                           | Merchant rule     | Description pending editorial review; the signal is live.                                                                                |
        | **Return Rate by Service Type**                               | Merchant rule     | Description pending editorial review; the signal is live.                                                                                |
        | **Shipments with Tracking-Event Gap (24h domestic / 5d EMS)** | Alert band 0 / 10 | Shipments with Tracking-Event Gap (24h domestic / 5d EMS), broken down by row.                                                           |
        | **Yu-Pack Cost vs Sibling Carriers per Zone**                 | Merchant rule     | Limited JP carrier-sibling overlap , most JP merchants run single-carrier Japan Post. Card hides via only\_when when no carrier sibling. |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                                                         |
        | ------------------------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**               | Watch only         | Description pending editorial review; the signal is live.                                                              |
        | **First-Attempt Delivery Rate**      | Watch only         | Description pending editorial review; the signal is live.                                                              |
        | **Late Shipments**                   | Watch only         | Description pending editorial review; the signal is live.                                                              |
        | **On-Time Delivery Rate**            | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                              |
        | **Yu-Pack Same-Day Tokyo Metro OTD** | Alert band 95 / 90 | Tokyo metro Yu-Pack shipments before 12:00 noon get same-day delivery. Drops here = Yu-Pack-network operational issue. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                                                                     |
        | ------------------------------------------------------ | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **EMS OTD by Destination Corridor (JP→US/EU/AU/Asia)** | Alert band 95 / 90 | EMS transit-time SLAs differ by destination , North America 3-5d, Europe 5-7d, Asia 2-4d. Per-corridor visibility surfaces which routes degrading. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                        | Alert behaviour | What it tracks                                        |
        | --------------------------------------------- | --------------- | ----------------------------------------------------- |
        | **Japan Post Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for Japan Post Tracking API Unavailable / 5xx. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **2 write** operations across servicecustoms, serviceshippings, servicetrackings on Japan Post (EMS / Yu-Pack). 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=japan-post)

    #### Ready to build your first Japan Post (EMS / Yu-Pack) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | servicecustoms   | 0               | 1                |
      | serviceshippings | 0               | 1                |
      | servicetrackings | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# JD.com on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/jd-com

Monitor JD.com listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor JD.com listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=jd-com)

<CardGroup>
  <Card title="38">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (38)">
    ### Monitor performance

    38 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Chinese Province**                            | Watch only         | AOV by Chinese Province.                                                                                                                               |
        | **Buyer Messages Unread**                              | Watch only         | Buyer Messages Unread as exposed by the JD.com integration. The metric is computed from the latest available data and refreshed on the standard data r |
        | **DSR / Brand-Auth / Logistics-SLA Threshold Crossed** | Alert band 95 / 85 | Alerts for DSR / Brand-Auth / Logistics-SLA Threshold Crossed.                                                                                         |
        | **Days Since Last Payout**                             | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **JD Logistics SLA Compliance**                        | Merchant rule      | % of JD-Logistics-enabled orders meeting the 24h same-day-doorstep promise. Below 95% drops Premium Buyer eligibility.                                 |
        | **Marketplace Fees Paid**                              | Watch only         | Marketplace Fees Paid as exposed by the JD.com integration. The metric is computed from the latest available data and refreshed on the standard data r |
        | **Oldest Pending Payout (days)**                       | Watch only         | Oldest Pending Payout (days) as exposed by the JD.com integration. The metric is computed from the latest available data and refreshed on the standard |
        | **Orders / Day**                                       | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Chinese Province**                         | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **POP Self-Fulfilled Dispatch Rate**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                                    | Watch only         | Pending Payouts as exposed by the JD.com integration. The metric is computed from the latest available data and refreshed on the standard data refresh |
        | **Pending Shipment**                                   | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Return Rate (7-day no-reason)**                      | Alert band 5 / 15  | JD honours the Chinese 7-day no-reason return policy strictly , return rate typically 5-15%.                                                           |
      </Accordion>

      <Accordion title="Grow revenue (11 signals)">
        | Signal                                                          | Alert behaviour    | What it tracks                                                                                                                   |
        | --------------------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value (CNY)**                                   | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                        |
        | **Detailed Seller Ratings (Description / Service / Logistics)** | Alert band 95 / 85 | JD's 3-axis seller rating , drives search placement + buyer-trust premium.                                                       |
        | **JD Commission % of Revenue**                                  | Alert band 12 / 18 | 3-10% by category + JD Logistics fees if opted-in + JD Direct (1P) wholesale margin if applicable.                               |
        | **JD Logistics vs POP-Fulfilled Revenue**                       | Watch only         | Mix of orders fulfilled by JD Logistics vs seller-self-fulfilled. JD Logistics commands premium AOV but lower margin.            |
        | **Listings with Chinese-Character Title**                       | Alert band 90 / 70 | % of listings whose title\_zh is populated. Chinese buyers search hanzi; English-only or Pinyin titles miss most search surface. |
        | **Net Revenue (after JD commission)**                           | Alert band 0 / -5  | Net of JD's commission (3-10% by category) + JD Logistics fees if opted-in.                                                      |
        | **Orders**                                                      | Watch only         | Description pending editorial review; the signal is live.                                                                        |
        | **Required-Attribute Completeness**                             | Alert band 90 / 70 | JD's category-level attribute schemas are strict , missing attrs = listings deprioritised in search.                             |
        | **Revenue Over Time**                                           | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                        |
        | **Top Listings by Revenue**                                     | Watch only         | Top Listings by Revenue.                                                                                                         |
        | **Total Revenue (CNY)**                                         | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                        |
      </Accordion>

      <Accordion title="Catalogue quality (8 signals)">
        | Signal                                       | Alert behaviour   | What it tracks                                                                                                                                        |
        | -------------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Listings**                          | Merchant rule     | Description pending editorial review; the signal is live.                                                                                             |
        | **Brand Authorisations Expiring in 30 Days** | Merchant rule     | Brand authorisations approaching expiry , renew before JD blocks listings under that brand.                                                           |
        | **Brand-Authorisation Coverage**             | Merchant rule     | % of restricted-category listings with valid brand-authorisation. Gaps = listings blocked at next JD audit.                                           |
        | **JD Off-Shelved Listings (24h)**            | Alert band 5 / 50 | Alerts for JD Off-Shelved Listings (24h).                                                                                                             |
        | **JD.com Shop Health Score**                 | Merchant rule     | Composite of DSR scores (Description, Service, Logistics) + active listing % + brand-auth coverage.                                                   |
        | **Listings Expiring Soon**                   | Watch only        | Listings Expiring Soon as exposed by the JD.com integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Rejected / Off-Shelf Listings**            | Alert band 5 / 50 | Description pending editorial review; the signal is live.                                                                                             |
        | **Total Listings**                           | Watch only        | Description pending editorial review; the signal is live.                                                                                             |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                      | Alert behaviour   | What it tracks                                                                                                                |
        | ------------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
        | **Active JD Listings for OOS SKUs on BC**   | Alert band 0 / 5  | Description pending editorial review; the signal is live.                                                                     |
        | **China-Domestic vs Cross-Border Pricing**  | Merchant rule     | China-domestic JD vs cross-border AliExpress/Alibaba pricing , same supplier often sells both, big spreads erode credibility. |
        | **Late Dispatches Risking DSR-Logistics**   | Merchant rule     | Alerts for Late Dispatches Risking DSR-Logistics.                                                                             |
        | **Listings Drifting from BC**               | Alert band 5 / 50 | Listings Drifting from BC, broken down by row.                                                                                |
        | **Listings Failing Feedonomics Validation** | Alert band 2 / 5  | Description pending editorial review; the signal is live.                                                                     |
        | **Revenue at Risk**                         | Merchant rule     | Description pending editorial review; the signal is live.                                                                     |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across brandauthorisations, oauthtokens, order lists, selleraccounts, warelists on JD.com. 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=jd-com)

    #### Ready to build your first JD.com 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | brandauthorisations | 1               | 0                |
      | oauthtokens         | 0               | 1                |
      | order lists         | 1               | 0                |
      | selleraccounts      | 1               | 0                |
      | warelists           | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Jira on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/jira-cloud

Monitor Jira health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Jira health, cost and reliability signals, and catch incidents and runaway spend early.

[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=jira-cloud)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="43">
    proven workflows
  </Card>

  <Card title="629">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (29 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Rate-Limit Headroom**                 | Merchant rule      | If we approach the limit, finding-creation slows or fails , surfaces here before it bites.                                                             |
        | **Active Sprint Progress**                  | Alert band 80 / 50 | Per-board active-sprint burn , uses /agile/1.0/board//sprint, not the archetype's metric-driven gauge.                                                 |
        | **Avg Cycle Time (days)**                   | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Lead Time (days)**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Time-to-Fix (days)**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Backlog by Priority**                     | Merchant rule      | Backlog by Priority.                                                                                                                                   |
        | **Backlog by Status**                       | Watch only         | Backlog by Status.                                                                                                                                     |
        | **Blocked Tickets**                         | Alert band 3 / 8   | Issues flagged blocked / impeded , the operational queue's stuck list.                                                                                 |
        | **Critical Findings Without a Jira Ticket** | Merchant rule      | Critical / high audit findings older than 7 days with no Jira ticket , coverage gap. The auto-dispatch missed these or the merchant disabled it; eithe |
        | **Cycle Time by Priority**                  | Merchant rule      | Cycle Time by Priority.                                                                                                                                |
        | **Finding Resolution Rate (90d)**           | Alert band 75 / 50 | What share of audit findings actually got fixed via the Jira pipeline. \<50% means we're filing faster than the team drains.                           |
        | **Finding-to-Ticket Dispatch Lag**          | Merchant rule      | How fast we get findings into Jira after detection. Slow dispatch = cold leads by the time the ops team sees them.                                     |
        | **In Progress**                             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Oldest Open (days)**                      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Tickets**                            | Merchant rule      | Total open issues across the default project , top-of-funnel backlog volume.                                                                           |
        | **Overloaded Assignees (>10 open)**         | Alert band 0 / 1   | People with >10 open tickets , capacity bottleneck candidates.                                                                                         |
        | **Rate-Limit Exhausted**                    | Merchant rule      | Atlassian is throttling us , finding dispatch will stall. Back off bulk-create and warn the merchant.                                                  |
        | **Scope Added Mid-Sprint**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Sprint Progress**                         | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Sprint Velocity (avg)**                   | Merchant rule      | Sprint Velocity (avg) over time.                                                                                                                       |
        | **Throughput Trend**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets Resolved (7d)**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets by Assignee**                     | Merchant rule      | Tickets by Assignee.                                                                                                                                   |
        | **Unassigned Critical Tickets**             | Merchant rule      | High-priority work nobody owns , escalate or auto-assign before SLA breach.                                                                            |
        | **Unassigned Tickets**                      | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                              |
        | **Velocity (Last 5 Sprints)**               | Watch only         | Velocity (Last 5 Sprints), compared across items.                                                                                                      |
        | **VortexIQ Findings In Progress**           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings Open**                  | Merchant rule      | Tickets we filed from audit findings that haven't been resolved yet , the live backlog of things VortexIQ surfaced.                                    |
        | **VortexIQ Findings Resolved**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                              |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks , these are the ones losing money silently. |
        | **Abandoned-Findings Burst**              | Alert band 5 / 15 | Sudden spike in findings hitting the 14d abandonment threshold , capacity issue or process breakdown.       |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                              | Alert behaviour | What it tracks                                                                                                             |
        | ----------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------- |
        | **Atlassian Token Expiry Imminent** | Merchant rule   | If the API token expires we silently stop creating tickets , every audit finding goes into the void. Surface 7 days early. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **283 read** and **346 write** operations across issuepropertys, issues, issuecomments, issueremotelinks, issueworklogs, roles on Jira. 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=jira-cloud)

    #### Proven workflow templates (43)

    <AccordionGroup>
      <Accordion title="API Contract Drift Watch">
        **For** Developer · **Ready to deploy**

        detects connector or internal schema changes before production failure.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Actionable Incident Triage">
        **For** Developer · **Ready to deploy**

        correlates errors, deploys and affected journeys and opens a pre-filled engineering ticket.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Auth Failure Triage">
        **For** Developer · **Ready to deploy**

        distinguishes expiry, scope, rate limit and upstream outage causes.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Dependency Risk Queue">
        **For** Developer · **Ready to deploy**

        surfaces relevant security/end-of-life updates with compatibility and test guidance.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Failed Job Replay Assistant">
        **For** Developer · **Ready to deploy**

        diagnoses and safely retries idempotent work while escalating unsafe cases.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flaky Test Investigator">
        **For** Developer · **Ready to deploy**

        clusters intermittent failures and ranks likely ownership and root cause.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PR Risk Summary">
        **For** Developer · **Ready to deploy**

        reports affected services, missing tests, operational risk and required approvers.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Performance Regression Bisect">
        **For** Developer · **Ready to deploy**

        correlates release changes with latency and frontend performance shifts.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Safe Fix Branch">
        **For** Developer · **Ready to deploy**

        creates a scoped branch/PR with evidence, tests and rollback notes for an approved issue.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Ticket Builder">
        **For** Developer · **Ready to deploy**

        translates crawl/indexation evidence into reproducible developer work.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Auto-apply Guardrail Approval">
        **For** Security manager · **Ready to deploy**

        requires security sign-off when an automation gains broader write authority.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Blocked Work Escalator">
        **For** Engineering manager · **Ready to deploy**

        detects ageing PRs/tickets and identifies the missing decision or dependency.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Integrity Night Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        checks SKU identity, variants, price, availability and orphan records across systems.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: BigCommerce, Shopify, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Change Failure Rate Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks failed deploys and highlights teams/services with worsening patterns.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Cloud Exposure Watch">
        **For** Security manager · **Ready to deploy**

        detects risky DNS, firewall, storage or edge configuration changes.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Access Review">
        **For** Security manager · **Ready to deploy**

        inventories credentials, scopes, owners, use and age; routes unnecessary access for revocation.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Engineering Dependency Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks vulnerable, unsupported or risky platform dependencies.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Executive Technology Pack">
        **For** Engineering manager · **Ready to deploy**

        translates technical risk and delivery evidence into commercial impact.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Fulfilment SLA Breach Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        predicts and escalates orders likely to miss dispatch or delivery promises.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: BigCommerce, Shopify, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Containment Pack">
        **For** Security manager · **Ready to deploy**

        prepares reversible, scoped containment actions for human approval.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Learning Loop">
        **For** Engineering manager · **Ready to deploy**

        creates the timeline, contributing factors, actions and follow-up ownership.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Monthly Security Evidence Pack">
        **For** Security manager · **Ready to deploy**

        retains what changed, who approved it, results and rollback availability.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Operations Morning Handover">
        **For** E-commerce operations manager · **Ready to deploy**

        summarises overnight exceptions, actions taken, unresolved risk and accountable owners.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: BigCommerce, Shopify, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Exception Command Centre">
        **For** E-commerce operations manager · **Ready to deploy**

        detects stuck, failed or unusual orders and routes them with age and value-based urgency.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: BigCommerce, Shopify, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Issue Triage">
        **For** Customer service manager · **Ready to deploy**

        enriches tickets with order, payment and fulfilment context and assigns the right queue.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: HubSpot, BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Peak Freeze Controller">
        **For** E-commerce operations manager · **Ready to deploy**

        pauses writes during trading freezes while continuing all monitoring and alerts.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: BigCommerce, Shopify, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Privilege Drift Monitor">
        **For** Security manager · **Ready to deploy**

        alerts when repository, cloud or connector permissions exceed policy.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Proactive Delay List">
        **For** Customer service manager · **Ready to deploy**

        prepares, but does not send, customer communications for affected orders.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: HubSpot, BigCommerce, Shopify, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Risk Gate">
        **For** Engineering manager · **Ready to deploy**

        scores change size, test evidence, service health and rollback readiness before approval.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Returns Anomaly Monitor">
        **For** E-commerce operations manager · **Ready to deploy**

        surfaces spikes by SKU, supplier, reason or cohort and assigns investigation.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: BigCommerce, Shopify, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Audit">
        **For** Engineering manager · **Ready to deploy**

        verifies that rollbacks completed and downstream state returned to expected values.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Suspicious Change Correlator">
        **For** Security manager · **Ready to deploy**

        links identity, code, infrastructure and automation audit events.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Integration Risk Review">
        **For** Security manager · **Ready to deploy**

        assesses new connectors before activation and on material permission change.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Vulnerability Remediation Queue">
        **For** Security manager · **Ready to deploy**

        ranks findings by exploitability, exposure and affected revenue paths.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: Cloudflare, GitHub, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Weekly Delivery and Reliability Brief">
        **For** Engineering manager · **Ready to deploy**

        combines throughput, failed changes, incidents, rollbacks and ageing work.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: GitHub, Cloudflare, StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Accessibility Regression Sweep">
        **For** Web / digital product manager · **Ready to deploy**

        monitors high-value templates for newly introduced violations.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Broken Experience Prioritiser">
        **For** Web / digital product manager · **Ready to deploy**

        combines errors, traffic and revenue impact into a ranked product backlog.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Conversion Journey Sentinel">
        **For** Web / digital product manager · **Ready to deploy**

        repeatedly tests priority journeys and captures actionable failure evidence.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Core Web Performance Guard">
        **For** Web / digital product manager · **Ready to deploy**

        detects page/template regressions and routes them to the owning team.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Post-release Regression Watch">
        **For** Web / digital product manager · **Ready to deploy**

        compares critical KPIs and technical signals before/after deploy.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Readiness Gate">
        **For** Web / digital product manager · **Ready to deploy**

        checks staging journeys, accessibility, analytics, SEO, performance and rollback readiness.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Recommendation Pack">
        **For** Web / digital product manager · **Ready to deploy**

        assembles evidence and prepares a reversible action when guardrails fail.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Script Risk Watch">
        **For** Web / digital product manager · **Ready to deploy**

        flags new, slow, failing or unapproved scripts and tags.

        Also available on: Wrike, Height, Basecamp, ClickUp, Asana, Trello (API), Teamwork, Smartsheet (API)

        Tested alongside: StagingPro, Cloudflare, GitHub, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | issuepropertys   | 2               | 5                |
      | issues           | 1               | 5                |
      | issuecomments    | 2               | 4                |
      | issueremotelinks | 2               | 4                |
      | issueworklogs    | 2               | 4                |
      | roles            | 2               | 4                |
      | status           | 3               | 3                |
      | components       | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    17 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Keap (Infusionsoft) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/keap

Monitor Keap (Infusionsoft) pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Keap (Infusionsoft) 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=keap)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="2">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (17 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                  |
        | ----------------------------- | ------------------ | ----------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule      | Email broadcasts grouped by status (sent, draft, scheduled).                                    |
        | **Checkout-to-Order Rate**    | Merchant rule      | Share of started checkouts (draft orders) that became paid orders.                              |
        | **Click-to-Open Rate**        | Alert band 10 / 3  | Clicks as a share of opens - engagement quality independent of open-rate inflation.             |
        | **Conversion Rate**           | Merchant rule      | Orders as a share of emails sent - ties send volume to revenue.                                 |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Share of delivered emails that earned a click. The clearest engagement signal.                  |
        | **Engagement Funnel**         | Merchant rule      | Sent → delivered → opened → clicked, showing where engagement drops off.                        |
        | **Flow Count Summary**        | Merchant rule      | How many automation campaigns exist on the account.                                             |
        | **Flow Status Breakdown**     | Merchant rule      | Automation campaigns split by status (published, draft).                                        |
        | **Flow Trigger Types**        | Merchant rule      | Automation campaigns grouped by what triggers them (goals / sequences).                         |
        | **Flows List**                | Merchant rule      | Every automation campaign and its current status.                                               |
        | **List Count**                | Merchant rule      | Number of tags / audiences on the account.                                                      |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all tags / audiences.                                            |
        | **Lists Overview**            | Merchant rule      | Every audience (tag) with its member count.                                                     |
        | **Revenue per Recipient**     | Merchant rule      | Revenue divided by emails sent - what each address is worth per send.                           |
        | **Revenue per Send**          | Merchant rule      | Revenue divided by emails sent - the efficiency of each send.                                   |
        | **Top Lists by Name**         | Merchant rule      | Largest audiences (tags) by member count.                                                       |
        | **Total Revenue**             | Merchant rule      | Order/transaction revenue attributed to Keap email + checkout over the window. The hero number. |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                                         | Alert behaviour      | What it tracks                                                                                                                                       |
        | ---------------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Bounce Rate**                                | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation - investigate list quality.                                                       |
        | **Delivery Rate**                              | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.                                                                            |
        | **Email Health KPIs**                          | Merchant rule        | Delivered, bounced and unsubscribed at a glance - your deliverability vitals.                                                                        |
        | **Keap Email Revenue vs Storefront Revenue**   | Merchant rule        | Reconciles Keap-attributed revenue against the storefront's own order revenue for the same customers - exposes attribution gaps and double-counting. |
        | **Refund Rate**                                | Merchant rule        | Share of attributed orders later refunded (status REFUNDED / PARTIALLY\_REFUNDED).                                                                   |
        | **Spam Complaint Rate**                        | Alert band 0.1 / 0.3 | Spam complaints per send. Above 0.1% puts deliverability at risk.                                                                                    |
        | **Storefront Buyers Not in Any Keap Campaign** | Merchant rule        | Paying storefront customers who never enter a Keap automation - missed lifecycle revenue. Enrol them.                                                |
        | **Unsubscribe Rate**                           | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.                                                                           |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                                                                           |
        | ----------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts (marketable email\_status).                                                                                     |
        | **CRM Data Hygiene Score**    | Alert band 95 / 80 | Composite of two confirmed real Keap Contact fields (requested via the /contacts optional\_properties param): share with a populated email\_addresses en |
        | **Email Open Rate**           | Alert band 20 / 10 | Share of delivered emails opened. iOS Mail Privacy inflates this - pair with click-to-open.                                                              |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to Keap in the window.                                                                                                                 |
        | **Total Sends**               | Merchant rule      | Total email broadcasts sent across the window.                                                                                                           |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                           |
        | --------------------- | --------------- | ------------------------------------------------------------------------ |
        | **Checkouts Started** | Merchant rule   | Checkouts begun (draft orders) from email clicks, where Keap reports it. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                   |
        | --------------------- | --------------- | ------------------------------------------------ |
        | **Segments Overview** | Merchant rule   | Saved segments (tag categories) and their sizes. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (2)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **3 write** operations across campaigns, tagcontacts, account profiles, campaign sequencecontacts, contacts, emails on Keap (Infusionsoft). 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=keap)

    #### Ready to build your first Keap (Infusionsoft) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | campaigns                 | 2               | 0                |
      | tagcontacts               | 1               | 1                |
      | account profiles          | 1               | 0                |
      | campaign sequencecontacts | 0               | 1                |
      | contacts                  | 1               | 0                |
      | emails                    | 1               | 0                |
      | orders                    | 1               | 0                |
      | tags                      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Klarna (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/klarna-api

Monitor Klarna (API) payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Klarna (API) payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=klarna-api)

<CardGroup>
  <Card title="16">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (16)">
    ### Monitor performance

    16 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (9 signals)">
        | Signal                   | Alert behaviour      | What it tracks                                                                                                                                         |
        | ------------------------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **3DS Abandonment Rate** | Alert band 15 / 30   | Klarna does not use card 3DS; this tracks Klarna-app / email-OTP authentication abandonment (started login, did not complete).                         |
        | **Chargeback Rate**      | Alert band 0.5 / 0.9 | Klarna 'buyer protection' claims - chargeback equivalent. Generally lower than card chargebacks.                                                       |
        | **Decline Rate**         | Alert band 5 / 8     | Klarna underwriting rejection rate - consumer-credit-side, distinct from card issuer decline.                                                          |
        | **Dispute Rate**         | Alert band 0.5 / 1   | Active + recently-resolved Klarna disputes; leading indicator for buyer-protection-claim (chargeback) rate.                                            |
        | **Pending Payouts**      | Watch only           | Captured-but-not-yet-paid-out balance (less merchant fee, less refunds). Plan \~7 days of revenue in flight on weekly.                                 |
        | **Refund Rate**          | Alert band 3 / 8     | Share of Klarna revenue refunded; BNPL 'try and return' runs 2-4pp above card refund rate.                                                             |
        | **Refund Volume**        | Merchant rule        | Total refund value; Klarna debits this from the pending payout balance.                                                                                |
        | **Top Decline Reasons**  | Watch only           | Klarna decline reason mix (insufficient data, existing debt, address verification, fraud flag, max amount). Only address-verification is merchant-acti |
        | **Total Volume**         | Alert band 0 / -15   | Gross Klarna BNPL volume captured (Pay in 4 + Pay in 30 + Slice it), pre-fee, pre-refund.                                                              |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                           |
        | -------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------- |
        | **Average Transaction**          | Merchant rule      | Klarna mean order value; structurally 30-45% above card AOV. Slice it dominates the blend.               |
        | **Avg Settlement Time (days)**   | Alert band 2 / 5   | Average days from Klarna capture to merchant payout on the configured schedule.                          |
        | **Oldest Pending Payout (days)** | Alert band 2 / 5   | Days since the oldest unpaid Klarna capture - stuck-money signal (or a reserve hold).                    |
        | **Success Rate**                 | Alert band 95 / 90 | Share of Klarna BNPL attempts Klarna approved and the merchant captured. Reflects Klarna's underwriting. |
        | **Total Transactions**           | Merchant rule      | Count of captured Klarna orders; volume / this = Klarna AOV.                                             |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                                       |
        | ----------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Top Payment Methods** | Watch only      | Klarna product mix by country: Pay in 4 / Pay in 30 (Pay later) / Slice it (Financing). Drives AOV and merchant fee. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal           | Alert behaviour    | What it tracks                                                                        |
        | ---------------- | ------------------ | ------------------------------------------------------------------------------------- |
        | **Volume Trend** | Alert band 0 / -15 | Daily captured volume; reveals German payday clusters and Klarna campaign-day spikes. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **2 write** operations across order managementorders, checkoutorders, disputes, disputedisputecontests, order managementorderrefunds, settlementpayouts on Klarna (API). 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=klarna-api)

    #### Ready to build your first Klarna (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | order managementorders       | 2               | 0                |
      | checkoutorders               | 1               | 0                |
      | disputes                     | 1               | 0                |
      | disputedisputecontests       | 0               | 1                |
      | order managementorderrefunds | 0               | 1                |
      | settlementpayouts            | 1               | 0                |
      | settlementtransactions       | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Klaviyo on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/klaviyo

Monitor email revenue and deliverability for Klaviyo, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Klaviyo, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=klaviyo)

<CardGroup>
  <Card title="67">
    performance signals
  </Card>

  <Card title="14">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="345">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (67)">
    ### Monitor performance

    67 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (27 signals)">
        | Signal                        | Alert behaviour   | What it tracks                                            |
        | ----------------------------- | ----------------- | --------------------------------------------------------- |
        | **Campaign Ranking**          | Watch only        | Campaign Ranking, compared across items.                  |
        | **Campaign Revenue Trend**    | Watch only        | Description pending editorial review; the signal is live. |
        | **Campaign Sends Trend**      | Watch only        | Description pending editorial review; the signal is live. |
        | **Campaign Status Breakdown** | Watch only        | Campaign Status Breakdown.                                |
        | **Campaign vs Flow Revenue**  | Watch only        | Description pending editorial review; the signal is live. |
        | **Channel Distribution**      | Watch only        | Channel Distribution, shown by share.                     |
        | **Checkout-to-Order Rate**    | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Click Rate Trend**          | Watch only        | Description pending editorial review; the signal is live. |
        | **Click-to-Open Rate**        | Alert band 10 / 3 | Description pending editorial review; the signal is live. |
        | **Clicked Trend**             | Watch only        | Description pending editorial review; the signal is live. |
        | **Conversion Rate**           | Alert band 3 / 1  | Description pending editorial review; the signal is live. |
        | **Conversion Rate Trend**     | Watch only        | Description pending editorial review; the signal is live. |
        | **Email Health KPIs**         | Watch only        | Description pending editorial review; the signal is live. |
        | **Emails Received Trend**     | Watch only        | Description pending editorial review; the signal is live. |
        | **Engagement Funnel**         | Watch only        | Engagement Funnel, stage by stage.                        |
        | **Open Rate Trend**           | Watch only        | Description pending editorial review; the signal is live. |
        | **Opened Trend**              | Watch only        | Description pending editorial review; the signal is live. |
        | **Orders Trend**              | Watch only        | Description pending editorial review; the signal is live. |
        | **Recent Campaigns Detail**   | Watch only        | Recent Campaigns Detail, broken down by row.              |
        | **Repeat Purchasers**         | Watch only        | Description pending editorial review; the signal is live. |
        | **Revenue Trend**             | Watch only        | Description pending editorial review; the signal is live. |
        | **Revenue per Recipient**     | Watch only        | Description pending editorial review; the signal is live. |
        | **Revenue per Send**          | Watch only        | Description pending editorial review; the signal is live. |
        | **SMS Conversion**            | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Sends vs Opens**            | Watch only        | Description pending editorial review; the signal is live. |
        | **Subscriber Growth Rate**    | Watch only        | Description pending editorial review; the signal is live. |
        | **Total Revenue**             | Watch only        | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Run operations (23 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                            |
        | ----------------------------- | ------------------ | --------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Watch only         | Description pending editorial review; the signal is live. |
        | **Added to List Trend**       | Watch only         | Description pending editorial review; the signal is live. |
        | **Added vs Unsubscribed**     | Watch only         | Description pending editorial review; the signal is live. |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Percentage of delivered emails with at least one click.   |
        | **Email Open Rate**           | Alert band 20 / 10 | Percentage of delivered emails that were opened.          |
        | **Flow Count Summary**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Flow Sends Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Flow Status Breakdown**     | Watch only         | Flow Status Breakdown.                                    |
        | **Flow Trigger Types**        | Watch only         | Flow Trigger Types, shown by share.                       |
        | **Flows List**                | Watch only         | Flows List.                                               |
        | **Lifecycle Funnel**          | Watch only         | Lifecycle Funnel, stage by stage.                         |
        | **List Count**                | Watch only         | Description pending editorial review; the signal is live. |
        | **List Health Summary**       | Watch only         | Description pending editorial review; the signal is live. |
        | **Lists Overview**            | Watch only         | Lists Overview.                                           |
        | **Placed Orders Total**       | Watch only         | Description pending editorial review; the signal is live. |
        | **Post-Purchase Flow**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Segments Overview**         | Watch only         | Segments Overview.                                        |
        | **Tags Overview**             | Watch only         | Tags Overview.                                            |
        | **Top Lists by Name**         | Watch only         | Top Lists by Name.                                        |
        | **Total Sends**               | Watch only         | Description pending editorial review; the signal is live. |
        | **Unsubscribe Trend**         | Watch only         | Description pending editorial review; the signal is live. |
        | **Updated Email Preferences** | Watch only         | Updated Email Preferences over time.                      |
        | **Welcome Flow**              | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (11 signals)">
        | Signal                     | Alert behaviour      | What it tracks                                            |
        | -------------------------- | -------------------- | --------------------------------------------------------- |
        | **Abandoned Cart Metrics** | Watch only           | Description pending editorial review; the signal is live. |
        | **Bounce Rate**            | Alert band 2 / 5     | Percentage of emails that bounced.                        |
        | **Bounce Trend**           | Watch only           | Description pending editorial review; the signal is live. |
        | **Deliverability Summary** | Watch only           | Description pending editorial review; the signal is live. |
        | **Delivery Rate**          | Alert band 98 / 95   | Description pending editorial review; the signal is live. |
        | **Dropped Emails**         | Watch only           | Description pending editorial review; the signal is live. |
        | **Refund Rate**            | Merchant rule        | Description pending editorial review; the signal is live. |
        | **Refunds Trend**          | Watch only           | Description pending editorial review; the signal is live. |
        | **Spam Complaint Rate**    | Alert band 0.1 / 0.3 | Description pending editorial review; the signal is live. |
        | **Spam Complaint Trend**   | Watch only           | Description pending editorial review; the signal is live. |
        | **Unsubscribe Rate**       | Alert band 0.5 / 2   | Percentage of recipients who unsubscribed.                |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                 | Alert behaviour | What it tracks                                            |
        | ---------------------- | --------------- | --------------------------------------------------------- |
        | **Checkouts Started**  | Watch only      | Description pending editorial review; the signal is live. |
        | **SMS Clicks**         | Watch only      | Description pending editorial review; the signal is live. |
        | **SMS Opt-in Trend**   | Watch only      | Description pending editorial review; the signal is live. |
        | **SMS Overview**       | Watch only      | Description pending editorial review; the signal is live. |
        | **SMS Sends**          | Watch only      | Description pending editorial review; the signal is live. |
        | **SMS vs Email Sends** | Watch only      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (14)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="API key missing required permissions">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        When the key lacks scopes, 20+ cards silently render "No data yet" and the merchant cannot diagnose without looking at our logs. The audit surfaces the exact scopes they need to enable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `KL08`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001, KL06`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="No Catalog Sync: product catalog is empty">
        **Severity** high · **Outcome** Run operations · **Fix status** Candidate remediation

        Without the product catalogue synced, flows cannot recommend products or build dynamic content, so the highest-converting email formats are unavailable.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `KL05`
      </Accordion>

      <Accordion title="Email Bounce Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `KL02`
      </Accordion>

      <Accordion title="High Refund Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Refunds triggered from email-attributed orders erode the channel's real revenue; concentration here often traces to overclaiming creative or mismatched landing pages.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `KL07`
      </Accordion>

      <Accordion title="Inactive Flows">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `KL01`
      </Accordion>

      <Accordion title="Limited Lists/Segmentation">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `KL04`
      </Accordion>

      <Accordion title="Spam Complaint Rate">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `KL03`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **204 read** and **141 write** operations across campaigns, catalog categorys, catalog items, catalog variants, coupons, couponcodes on Klaviyo. 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=klaviyo)

    #### Ready to build your first Klaviyo 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | campaigns         | 2               | 3                |
      | catalog categorys | 2               | 3                |
      | catalog items     | 2               | 3                |
      | catalog variants  | 2               | 3                |
      | coupons           | 2               | 3                |
      | couponcodes       | 2               | 3                |
      | custommetrics     | 2               | 3                |
      | flows             | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Leadfeeder on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/leadfeeder

Monitor Leadfeeder performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Leadfeeder performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=leadfeeder)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="67">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Leadfeeder yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **33 read** and **34 write** operations across customfields, lists, tags, webvisitcustomfeeds, buyerpersonas, campaigns on Leadfeeder. 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=leadfeeder)

    #### Ready to build your first Leadfeeder 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | customfields        | 2               | 3                |
      | lists               | 2               | 3                |
      | tags                | 2               | 3                |
      | webvisitcustomfeeds | 2               | 3                |
      | buyerpersonas       | 2               | 1                |
      | campaigns           | 2               | 1                |
      | companys            | 2               | 1                |
      | contacts            | 2               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Linear on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/linear

Monitor Linear performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Linear performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=linear)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="1">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (19 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                               |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Mean days from `started` to `completed` - how fast work clears once picked up.               |
        | **Avg Lead Time (days)**            | Merchant rule      | Mean days from `createdAt` to `completedAt` - full time-in-system.                           |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Mean days from finding-issue creation to completion - Linear's richest cycle-time read.      |
        | **Backlog by Priority**             | Merchant rule      | Open issues grouped by priority - skew toward Urgent/High flags a firefighting backlog.      |
        | **Backlog by Status**               | Watch only         | Open issues grouped by Linear state.type - the queue's shape at a glance.                    |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Issues labelled blocked / flagged blocked - the operational queue's stuck list.              |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle time split by priority - Urgent should clear fastest.                                  |
        | **In Progress**                     | Watch only         | Issues in the `started` state - work an engineer has actively pulled.                        |
        | **Oldest Open (days)**              | Merchant rule      | Age in days of the oldest open issue - backlog-rot signal.                                   |
        | **Open Tickets**                    | Merchant rule      | Linear issues with state.type ∈  across connected teams - top-of-funnel backlog volume.      |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | Engineers with >10 open issues - capacity-bottleneck and single-point-of-failure candidates. |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Issues added to the active cycle after it started - reactive vs proactive signal.            |
        | **Sprint Progress**                 | Alert band 80 / 50 | Active Linear cycle completion fraction - burn against the cycle commitment.                 |
        | **Sprint Velocity (avg)**           | Merchant rule      | Issues completed per cycle averaged over the last 5 cycles - the team's capacity ceiling.    |
        | **Throughput Trend**                | Watch only         | 30-day completion trend - the slope of the team's output.                                    |
        | **Tickets Resolved (7d)**           | Merchant rule      | Issues moved to completed in the last 7 days vs the prior week.                              |
        | **Tickets by Assignee**             | Merchant rule      | Open issue count per engineer - where the queue concentrates.                                |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Open issues with no assignee - work nobody owns yet.                                         |
        | **VortexIQ Findings In Progress**   | Watch only         | Findings an engineer has actively pulled (state.type = started).                             |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15  | Open findings whose updatedAt hasn't moved in 14+ days - on Linear's cycle-driven culture this is a louder signal than other PM tools.                 |
        | **Finding Resolution Rate (90d)**         | Alert band 75 / 50 | Share of findings created in 90d that reached completed/canceled. \<50% is the universal floor; on Linear, \<65% is already early warning.             |
        | **VortexIQ Findings Open**                | Merchant rule      | Issues we filed from audit findings still open (label vortex-iq-finding, state.type not completed/canceled) - the live backlog of things VortexIQ surf |
        | **VortexIQ Findings Resolved**            | Watch only         | Findings resolved (completed or canceled) in the last 90 days.                                                                                         |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **1 write** operations across graphqls on Linear. 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=linear)

    #### Ready to build your first Linear 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | graphqls | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# LinkedIn Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/linkedin-ads

Monitor LinkedIn Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor LinkedIn Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/linkedin-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=linkedin-ads)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (39 signals)">
        | Signal                                       | Alert behaviour      | What it tracks                                                                                                   |
        | -------------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**                          | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **CPC by Campaign**                          | Watch only           | CPC by Campaign.                                                                                                 |
        | **CTR by Campaign**                          | Watch only           | CTR by Campaign.                                                                                                 |
        | **Campaign Comparison**                      | Watch only           | Campaign Comparison, broken down by row.                                                                         |
        | **Clicks vs Conversions**                    | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Conversion Actions Breakdown**             | Watch only           | Conversion Actions Breakdown.                                                                                    |
        | **Conversion Drop Alert**                    | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Conversion Funnel**                        | Watch only           | Conversion Funnel, stage by stage.                                                                               |
        | **Conversion Lag**                           | Watch only           | Conversion Lag, compared across items.                                                                           |
        | **Conversion Rate Trend**                    | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Conversion Rate by Campaign**              | Watch only           | Conversion Rate by Campaign.                                                                                     |
        | **Conversion Rate by Device**                | Watch only           | Conversion Rate by Device.                                                                                       |
        | **Conversions Trend**                        | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Conversions by Campaign**                  | Watch only           | Conversions by Campaign.                                                                                         |
        | **Conversions by Country**                   | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Conversions by Day of Week**               | Watch only           | Conversions by Day of Week.                                                                                      |
        | **Conversions by Device**                    | Watch only           | Conversions by Device.                                                                                           |
        | **Conversions by Hour**                      | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Cost-per-MQL Spiked Above Threshold**      | Alert band 100 / 300 | B2B equivalent of ROAS-drop , cost-per-qualified-lead is the metric LinkedIn buyers stare at first thing Monday. |
        | **Landing Page Revenue**                     | Watch only           | Landing Page Revenue, broken down by row.                                                                        |
        | **Lead Gen Form Sync to CRM Broken**         | Merchant rule        | Leads captured but not synced = revenue silently lost. Most expensive tracking failure in the platform.          |
        | **Overspending Campaigns**                   | Watch only           | Overspending Campaigns, broken down by row.                                                                      |
        | **ROAS**                                     | Alert band 3 / 1.5   | Description pending editorial review; the signal is live.                                                        |
        | **ROAS Trend**                               | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **ROAS by Campaign**                         | Watch only           | ROAS by Campaign.                                                                                                |
        | **ROAS by Day of Week**                      | Watch only           | ROAS by Day of Week.                                                                                             |
        | **ROAS by Device**                           | Watch only           | ROAS by Device.                                                                                                  |
        | **ROAS by Region**                           | Watch only           | ROAS by Region.                                                                                                  |
        | **Revenue by Campaign**                      | Watch only           | Revenue by Campaign.                                                                                             |
        | **Search Terms Report**                      | Watch only           | Search Terms Report, broken down by row.                                                                         |
        | **Spend by Campaign**                        | Watch only           | Spend by Campaign.                                                                                               |
        | **Top Cities by Conversions**                | Watch only           | Top Cities by Conversions.                                                                                       |
        | **Top Keywords by Conversions**              | Watch only           | Top Keywords by Conversions.                                                                                     |
        | **Top Performing Campaigns**                 | Watch only           | Top Performing Campaigns, broken down by row.                                                                    |
        | **Total Revenue**                            | Watch only           | Description pending editorial review; the signal is live.                                                        |
        | **Underspending Campaigns**                  | Watch only           | Underspending Campaigns, broken down by row.                                                                     |
        | **Wasted-Spend Burst (audience exhaustion)** | Alert band 5 / 50    | LinkedIn CPCs are 5-10× Google , wasted spend compounds fast. Catch within 72h.                                  |
        | **Worst Performing Campaigns**               | Watch only           | Worst Performing Campaigns, broken down by row.                                                                  |
        | **Zero-Conversion Spend**                    | Watch only           | Description pending editorial review; the signal is live.                                                        |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                                                   |
        | -------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Campaigns on Out-of-Stock SKUs**          | Alert band 5 / 50 | Rare on LinkedIn (mostly B2B SaaS), but B2B-commerce campaigns can still drive spend at OOS SKUs. Card hides when no commerce sibling connected. |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | Branded queries paid on LinkedIn that already rank #1 organically on Google , pure margin reclaim.                                               |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                                                        |
        | **Landing Pages with Poor Web Vitals**             | Merchant rule     | LinkedIn campaigns often land on long-form B2B content pages , LCP regressions kill MQL conversion before the form even loads.                   |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on a campaign whose linked product feed has live Feedonomics rejections.                                                                       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **1 write** operations across adaccounts, adanalytics, adcampaigns, adcreatives, adformrespons, oauthaccesstokens on LinkedIn Ads. 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=linkedin-ads)

    #### Ready to build your first LinkedIn Ads 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | adaccounts        | 1               | 0                |
      | adanalytics       | 1               | 0                |
      | adcampaigns       | 1               | 0                |
      | adcreatives       | 1               | 0                |
      | adformrespons     | 1               | 0                |
      | oauthaccesstokens | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# LiveAgent on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/liveagent

Monitor LiveAgent pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor LiveAgent 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=liveagent)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                     |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                          |
        | **Avg Lead Time (days)**            | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                          |
        | **Avg Time-to-Fix (days)**          | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                          |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                                               |
        | **Backlog by Status**               | Merchant rule      | Backlog by Status.                                                                                                                                 |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Tickets in a blocked / SLA-breached state - the operational queue's stuck list.                                                                    |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                                            |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings filed in the last 90d actually got fixed via the LiveAgent pipeline. \<50% means we file faster than the team drains. |
        | **In Progress**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                          |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Description pending editorial review; the signal is live.                                                                                          |
        | **Open Tickets**                    | Alert band 0 / 100 | Total open tickets across the connected departments - top-of-funnel backlog volume.                                                                |
        | **Overloaded Assignees (>10 open)** | Merchant rule      | People with >10 open tickets - capacity bottleneck candidates.                                                                                     |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                          |
        | **Sprint Progress**                 | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                          |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20  | Sprint Velocity (avg) over time.                                                                                                                   |
        | **Throughput Trend**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                          |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                                                                          |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                                               |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                          |
        | **VortexIQ Findings In Progress**   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                          |
        | **VortexIQ Findings Open**          | Merchant rule      | Tickets we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced.                                |
        | **VortexIQ Findings Resolved**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                          |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                              |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="First-response SLA breached on open conversations">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Breached first-response SLAs compound: late answers create chase messages, which create more queue, which creates later answers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-SLA-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **3 write** operations across tickets, agents, contacts, departments, ticketmessages on LiveAgent. 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=liveagent)

    #### Ready to build your first LiveAgent 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | tickets        | 2               | 2                |
      | agents         | 1               | 0                |
      | contacts       | 1               | 0                |
      | departments    | 1               | 0                |
      | ticketmessages | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# LiveChat on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/livechat

Monitor LiveChat pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor LiveChat 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=livechat)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                       |
        | ----------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                            |
        | **Avg Lead Time (days)**            | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                            |
        | **Avg Time-to-Fix (days)**          | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                            |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                                                 |
        | **Backlog by Status**               | Merchant rule      | Backlog by Status.                                                                                                                                   |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Tickets in a pending/blocked state - the Tickets module's stuck list.                                                                                |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                                              |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings filed in the last 90d actually got fixed via the LiveChat Tickets pipeline. \<50% means we file faster than the chat-fi |
        | **In Progress**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                            |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Description pending editorial review; the signal is live.                                                                                            |
        | **Open Tickets**                    | Alert band 0 / 60  | Total open tickets in the LiveChat Tickets module - top-of-funnel backlog volume.                                                                    |
        | **Overloaded Assignees (>10 open)** | Merchant rule      | People with >10 open tickets - capacity bottleneck candidates.                                                                                       |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                            |
        | **Sprint Progress**                 | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                            |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20  | Sprint Velocity (avg) over time.                                                                                                                     |
        | **Throughput Trend**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                            |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                                                                            |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                                                 |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                            |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                                            |
        | **VortexIQ Findings Open**          | Merchant rule      | Tickets we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced (Tickets module, not Chats).      |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                                            |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                  |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently while the team focuses on live chat. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                        | Alert behaviour     | What it tracks                                                                                                                                         |
        | ----------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **First Response Time (min)** | Alert band 30 / 240 | GET /v1/reports/responseTime - confirmed real HelpDesk.com Reports endpoint (api.helpdesk.com/docs Reports section), same base and auth this engine al |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **5 write** operations across agentactioncreatetickets, agentactionlistarchives, agentactionlisttickets, agentactionupdatetickets, configurationactionlistagents, https:apihelpdeskcomreportresponsetimes on LiveChat. 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=livechat)

    #### Ready to build your first LiveChat 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                | Read operations | Write operations |
      | --------------------------------------- | --------------- | ---------------- |
      | agentactioncreatetickets                | 0               | 1                |
      | agentactionlistarchives                 | 0               | 1                |
      | agentactionlisttickets                  | 0               | 1                |
      | agentactionupdatetickets                | 0               | 1                |
      | configurationactionlistagents           | 1               | 0                |
      | https:apihelpdeskcomreportresponsetimes | 1               | 0                |
      | report ticketlists                      | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Mailchimp on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mailchimp

Monitor email revenue and deliverability for Mailchimp, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for Mailchimp, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=mailchimp)

<CardGroup>
  <Card title="41">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="14">
    proven workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (41)">
    ### Monitor performance

    41 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (17 signals)">
        | Signal                                            | Alert behaviour      | What it tracks                                                                                                                                          |
        | ------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Cart Recovery Revenue**               | Watch only           | Revenue from Mailchimp's Abandoned Cart automation. One of the highest-ROI automations Mailchimp ships - track regression aggressively.                 |
        | **Abandoned-Cart Automation Status**              | Watch only           | Abandoned-Cart Automation Status from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles e  |
        | **Abuse / Spam-Complaint Spike**                  | Alert band 0.1 / 0.3 | Abuse / Spam-Complaint Spike from Mailchimp, grouped under Nerve Centre. Computes when a live Mailchimp integration is connected; reconciles ecommerce  |
        | **Avg Member Engagement Score (1-5)**             | Merchant rule        | Average of Mailchimp's 1-5 list engagement star rating (list\_rating) across all audiences. Below 3 = list quality declining; re-engagement campaign ov |
        | **Cart Abandonment → Email Open → Ecom Recovery** | Merchant rule        | Full abandoned-cart funnel: abandonment → email sent → open → click → recovered order. Drops anywhere in the funnel surface where the automation is le  |
        | **Customers in Ecom Not Subscribed in Mailchimp** | Merchant rule        | Customers buying from your store but missing from your email list = recurring marketing leak. Sync via Mailchimp's ecom integration or manual list-add  |
        | **Deliverability Drop**                           | Alert band 0 / -5    | Deliverability Drop from Mailchimp, grouped under Nerve Centre. Computes when a live Mailchimp integration is connected; reconciles ecommerce against   |
        | **Email AOV**                                     | Watch only           | Email AOV from Mailchimp, grouped under Cross-Channel: Revenue at Risk. Computes when a live Mailchimp integration is connected; reconciles ecommerce   |
        | **Email Share of Total Store Revenue**            | Watch only           | % of total store revenue attributed to Mailchimp email sends. Computes once a live Mailchimp integration and an ecommerce sibling are both connected.   |
        | **Email-Attributed Revenue**                      | Watch only           | Email-Attributed Revenue from Mailchimp, grouped under Cross-Channel: Revenue at Risk. Computes when a live Mailchimp integration is connected; reconc  |
        | **Hard Bounce Spike (>5% on a campaign)**         | Merchant rule        | Mailchimp throttles sends from accounts with sustained >5% hard bounce - escalate to list-cleanup immediately.                                          |
        | **Inbox Placement Rate (deliverability)**         | Merchant rule        | % of sent emails landing in primary inbox (vs spam folder). Estimated from seed-list services if connected. Drops here = sender-reputation issue ahead  |
        | **Mailchimp Campaigns → Ecom Revenue (90d)**      | Merchant rule        | Per-campaign ecom revenue attribution. Surfaces high-engagement campaigns that don't convert (broken CTA or wrong audience).                            |
        | **Refund Rate (Email Orders)**                    | Watch only           | Refund Rate (Email Orders) from Mailchimp, grouped under Cross-Channel: Revenue at Risk. Computes when a live Mailchimp integration is connected; reco  |
        | **Sender-Reputation Risk**                        | Watch only           | Sender-Reputation Risk from Mailchimp, grouped under Nerve Centre. Computes when a live Mailchimp integration is connected; reconciles ecommerce again  |
        | **Top Email Clients (open distribution)**         | Watch only           | Apple Mail / Gmail / Outlook split across opens. Drives template-testing decisions; Apple MPP inflates open-rate signal.                                |
        | **Top Spenders Unengaged on Email (90d)**         | Merchant rule        | Highest-revenue customers ignoring your email = at-risk churn cohort. Build a VIP-only re-engagement segment.                                           |
      </Accordion>

      <Accordion title="Grow revenue (16 signals)">
        | Signal                                     | Alert behaviour | What it tracks                                                                                                                                         |
        | ------------------------------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **A/B Test Winners (last 90D)**            | Watch only      | A/B Test Winners (last 90D) from Mailchimp, grouped under Email & Marketing. Computes when a live Mailchimp integration is connected; reconciles ecomm |
        | **Audience Count**                         | Watch only      | Total subscribed contacts across all audiences.                                                                                                        |
        | **Audience Coverage of Customer Base**     | Watch only      | % of the store's customer base that is also a subscribed Mailchimp member. Computes once a live Mailchimp integration and an ecommerce sibling are bot |
        | **Audiences Overview**                     | Watch only      | Audiences Overview from Mailchimp, grouped under Email & Marketing. Computes when a live Mailchimp integration is connected; reconciles ecommerce agai |
        | **Automation vs Campaign Revenue Mix**     | Watch only      | Automation vs Campaign Revenue Mix from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles |
        | **Campaign Revenue Attribution (30d)**     | Watch only      | Per-campaign ecom revenue attributed via Mailchimp's ecom integration. Top-of-list = scale; bottom = kill or rework.                                   |
        | **Campaign Status**                        | Watch only      | Campaign Status from Mailchimp, grouped under Email & Marketing. Computes when a live Mailchimp integration is connected; reconciles ecommerce against |
        | **Net Audience Growth (30d)**              | Merchant rule   | Subscribes minus unsubscribes minus cleaned over 30 days. Net-negative for sustained periods = list shrinking and reaching fewer customers each cycle. |
        | **Segments**                               | Watch only      | Segments from Mailchimp, grouped under Email & Marketing. Computes when a live Mailchimp integration is connected; reconciles ecommerce against Mailch |
        | **Send Cadence (campaigns/wk)**            | Watch only      | Send Cadence (campaigns/wk) from Mailchimp, grouped under Email & Marketing. Computes when a live Mailchimp integration is connected; reconciles ecomm |
        | **Suppressed / Cleaned Members**           | Watch only      | Suppressed / Cleaned Members from Mailchimp, grouped under Email & Marketing. Computes when a live Mailchimp integration is connected; reconciles ecom |
        | **Top Automations by Revenue**             | Watch only      | Top Automations by Revenue from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles ecommer |
        | **Top Sends → Purchase Lag**               | Watch only      | Median time between a campaign send and the resulting order, for the top-performing sends. Computes once a live Mailchimp integration and an ecommerce |
        | **Unsubs Within 7d of Purchase**           | Watch only      | Members who unsubscribed within 7 days of placing an order - a signal of post-purchase send fatigue. Computes once a live Mailchimp integration and an |
        | **Unsubscribe Burst (>3x 7-day baseline)** | Merchant rule   | Pace check - sustained 3x usually means content / segmentation issue. Pause sends and investigate before the next campaign goes out.                   |
        | **Win-Back Automation Recovery Rate**      | Merchant rule   | % of lapsed subscribers who re-engaged via Win-Back series. Low % is normal (3-8%); 0% suggests broken flow.                                           |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                             | Alert behaviour | What it tracks                                                                                                                                         |
        | ---------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Automation Status**              | Watch only      | Automation Status from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles ecommerce agains |
        | **Automations**                    | Watch only      | Automations from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles ecommerce against Mail |
        | **Placed Orders (Email)**          | Watch only      | Placed Orders (Email) from Mailchimp, grouped under Customer Lifecycle. Computes when a live Mailchimp integration is connected; reconciles ecommerce  |
        | **Welcome Automation Status**      | Watch only      | Welcome Automation Status from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles ecommerc |
        | **Welcome Series Completion Rate** | Merchant rule   | First impression matters - % of new subscribers who complete the Welcome Series (typically 3-5 emails). Low completion = subject lines or pacing need  |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                | Alert behaviour | What it tracks                                                                                                                       |
        | ------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **Automation Series Completion Rate** | Merchant rule   | % of members who started a multi-step automation and reached the final email. Sharp drops = broken trigger or template-render error. |
        | **Automation Stopped Firing (>24h)**  | Merchant rule   | Status=sending with no recent sends = trigger broken or template-render error after Mailchimp UI version change.                     |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                                                                                                         |
        | --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Customer Journeys** | Watch only      | Customer Journeys from Mailchimp, grouped under Email Automation. Computes when a live Mailchimp integration is connected; reconciles ecommerce agains |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **0 write** operations across automations, campaigns, lists, listmembers on Mailchimp. 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=mailchimp)

    #### Proven workflow templates (14)

    <AccordionGroup>
      <Accordion title="Back-in-stock Opportunity Queue">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies high-intent customers and prepares consent-safe notifications.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Preflight Gate">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        validates segment, exclusions, consent, links, stock, offer dates and tracking before send approval.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Deliverability and List Health Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        monitors bounce, complaint, suppression and engagement shifts with safe remediation advice.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flow Performance Decay Watch">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        detects lifecycle automations whose engagement or revenue has materially deteriorated.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Frequency Pressure Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies over-contacted customers across campaigns and flows.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Segment Drift Monitor">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        flags unexpected audience growth/shrinkage or overlap before it damages sends.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: HubSpot, Klaviyo, Dotdigital, SendGrid, Iterable, Drip (API), Constant Contact, ConvertKit (API)

        Tested alongside: BigCommerce, Shopify, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource    | Read operations | Write operations |
      | ----------- | --------------- | ---------------- |
      | automations | 1               | 0                |
      | campaigns   | 1               | 0                |
      | lists       | 1               | 0                |
      | listmembers | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    6 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# MariaDB on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mariadb

Monitor MariaDB health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor MariaDB health, cost and reliability signals, and catch incidents and runaway spend early.

[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=mariadb)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                                               | Alert behaviour    | What it tracks                                                                                                            |
        | ---------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------- |
        | **Aborted Connects (24h)**                           | Merchant rule      | Description pending editorial review; the signal is live.                                                                 |
        | **Active Async Replicas**                            | Watch only         | Description pending editorial review; the signal is live.                                                                 |
        | **Async Replication Lag (seconds)**                  | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                                 |
        | **Connection Pool Saturation %**                     | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                                 |
        | **Connection Pool at >90% Saturation**               | Alert band 70 / 90 | Alerts for Connection Pool at >90% Saturation.                                                                            |
        | **Connections In Use**                               | Watch only         | Description pending editorial review; the signal is live.                                                                 |
        | **Database Disk Usage %**                            | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                                 |
        | **Failover Readiness**                               | Merchant rule      | Description pending editorial review; the signal is live.                                                                 |
        | **Galera Cluster Not in Primary State or Node Lost** | Merchant rule      | MariaDB-distinctive , Galera quorum loss = cluster goes read-only across all nodes.                                       |
        | **Galera Flow Control Paused %**                     | Merchant rule      | wsrep\_flow\_control\_paused , fraction of 5m window cluster was throttling writes. High = slow node pulling others back. |
        | **InnoDB / XtraDB Buffer Pool Hit Rate %**           | Alert band 95 / 80 | Description pending editorial review; the signal is live.                                                                 |
        | **Instance Uptime**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                 |
        | **Last Successful Backup (hours ago)**               | Alert band 24 / 72 | mariabackup / Percona XtraBackup last successful run.                                                                     |
        | **MariaDB Health Score**                             | Merchant rule      | Description pending editorial review; the signal is live.                                                                 |
        | **Memory Usage %**                                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                 |
        | **Queries per Second (live)**                        | Watch only         | Description pending editorial review; the signal is live.                                                                 |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                           |
        | -------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------- |
        | **Galera Cluster Size**                            | Merchant rule      | wsrep\_cluster\_size. MariaDB-distinctive Galera signal , node loss = quorum risk.                       |
        | **Galera Cluster Status**                          | Merchant rule      | wsrep\_cluster\_status. 'Primary' = healthy quorum. Non-Primary = split-brain risk; node refuses writes. |
        | **MariaDB Inventory Rows vs Ecom Inventory Count** | Merchant rule      | Description pending editorial review; the signal is live.                                                |
        | **MariaDB QPS Spike vs Ecom Order Rate**           | Merchant rule      | Description pending editorial review; the signal is live.                                                |
        | **Pool Saturation Across Galera Nodes vs Traffic** | Alert band 70 / 90 | Pool Saturation Across Galera Nodes vs Traffic, broken down by row.                                      |
        | **Slow Queries During Checkout Window (5m)**       | Merchant rule      | Slow Queries During Checkout Window (5m), broken down by row.                                            |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                              | Alert behaviour      | What it tracks                                            |
        | ----------------------------------- | -------------------- | --------------------------------------------------------- |
        | **InnoDB Deadlocks (last 5m)**      | Alert band 0 / 5     | Description pending editorial review; the signal is live. |
        | **Query Latency p50 (ms)**          | Watch only           | Description pending editorial review; the signal is live. |
        | **Query Latency p95 (ms)**          | Alert band 50 / 200  | Description pending editorial review; the signal is live. |
        | **Query Latency p99 (ms)**          | Alert band 100 / 500 | Description pending editorial review; the signal is live. |
        | **Slow-Query Rate %**               | Alert band 1 / 5     | Description pending editorial review; the signal is live. |
        | **Top 10 Slowest Queries (digest)** | Watch only           | Top 10 Slowest Queries (digest), broken down by row.      |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                            |
        | -------------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Connection Errors (24h)**            | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Query Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).            |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across informationschemaglobalstatus where like 'wsrep%'s, performanceschemaeventstatementsummarybydigests, performanceschemaprocesslists, show global status, show replica status, show variables on MariaDB. 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=mariadb)

    #### Ready to build your first MariaDB 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                           | Read operations | Write operations |
      | -------------------------------------------------- | --------------- | ---------------- |
      | informationschemaglobalstatus where like 'wsrep%'s | 1               | 0                |
      | performanceschemaeventstatementsummarybydigests    | 1               | 0                |
      | performanceschemaprocesslists                      | 1               | 0                |
      | show global status                                 | 1               | 0                |
      | show replica status                                | 1               | 0                |
      | show variables                                     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Matomo on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/matomo

Monitor traffic, conversion and tracking integrity from Matomo, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Matomo, and catch instrumentation breaks before decisions are made on bad data.

[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=matomo)

<CardGroup>
  <Card title="13">
    performance signals
  </Card>

  <Card title="10">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (13)">
    ### Monitor performance

    13 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (11 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                         |
        | --------------------------- | ------------------ | -------------------------------------------------------------------------------------- |
        | **Avg Session Duration**    | Merchant rule      | Average visit duration (avg\_time\_on\_site, seconds) from VisitsSummary.get.          |
        | **Goal Completions**        | Alert band 0 / -10 | Total goal conversions (nb\_conversions) from Goals.get across all configured goals.   |
        | **New Users**               | Alert band 0 / -10 | First-time visitors from VisitFrequency.get (nb\_uniq\_visitors\_new).                 |
        | **Pageviews per Session**   | Alert band 3 / 1.5 | Actions per visit (nb\_actions\_per\_visit) from VisitsSummary.get.                    |
        | **Real-Time Users**         | Merchant rule      | Visitors active in the last N minutes from Live.getCounters.                           |
        | **Returning Users**         | Alert band 0 / -10 | Returning visitors from VisitFrequency.get (nb\_uniq\_visitors\_returning).            |
        | **Session Conversion Rate** | Alert band 3 / 1   | Visits-converted rate (conversion\_rate) from Goals.get - joins to actual ecom orders. |
        | **Sessions**                | Alert band 0 / -10 | Total visits (sessions) from Matomo VisitsSummary.get - top-line audience volume.      |
        | **Top Pages**               | Merchant rule      | Most-viewed page URLs from Actions.getPageUrls (top 25 by pageviews).                  |
        | **Top Traffic Sources**     | Merchant rule      | Visit volume by referrer type from Referrers.getReferrerType.                          |
        | **Users**                   | Merchant rule      | Unique visitors (nb\_uniq\_visitors) over the period.                                  |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                 |
        | ------------------------- | ------------------ | ---------------------------------------------------------------------------------------------- |
        | **Bounce Rate**           | Alert band 35 / 60 | Single-action visits (bounce\_rate) from VisitsSummary.get - lower is better.                  |
        | **Cart Abandonment Rate** | Alert band 65 / 85 | Abandoned carts vs orders from the Goals ecommerceAbandonedCart pseudo-goal - higher is worse. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (10)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Sessions Present but Zero Goal Completions (tracking broken)">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Goals present but never completing typically means the goal or its tracking broke, not that every visitor changed their mind on the same day.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MAT01`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart Abandonment Above Ceiling">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Climbing cart abandonment concentrates revenue loss at the final step; shipping surprises, payment friction and errors are the usual culprits.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MAT04`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Session Conversion Rate Below Floor">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Session conversion below the floor while traffic holds means the store is buying visits it cannot convert; the cause is usually specific and findable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MAT02`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce Rate Above Ceiling">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A bounce-rate spike after a release or campaign change is the earliest cheap warning that something on the landing experience broke.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MAT03`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **0 write** operations across indexphp?module=api\&method=actiongetpageurls, indexphp?module=api\&method=goalgets, indexphp?module=api\&method=livegetcounters, indexphp?module=api\&method=referrergetalls, indexphp?module=api\&method=referrergetreferrertypes, indexphp?module=api\&method=sitesmanagergetsitefromids on Matomo. 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=matomo)

    #### Ready to build your first Matomo 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                               | Read operations | Write operations |
      | ------------------------------------------------------ | --------------- | ---------------- |
      | indexphp?module=api\&method=actiongetpageurls          | 1               | 0                |
      | indexphp?module=api\&method=goalgets                   | 1               | 0                |
      | indexphp?module=api\&method=livegetcounters            | 1               | 0                |
      | indexphp?module=api\&method=referrergetalls            | 1               | 0                |
      | indexphp?module=api\&method=referrergetreferrertypes   | 1               | 0                |
      | indexphp?module=api\&method=sitesmanagergetsitefromids | 1               | 0                |
      | indexphp?module=api\&method=visitfrequencygets         | 1               | 0                |
      | indexphp?module=api\&method=visitssummarygets          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# MediaMath (T1) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mediamath

Monitor MediaMath (T1) campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor MediaMath (T1) campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/mediamath) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=mediamath)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                             |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------ |
        | **All Conversions**                  | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **CPC by Campaign**                  | Watch only         | CPC by Campaign.                                                                           |
        | **CTR by Campaign**                  | Watch only         | CTR by Campaign.                                                                           |
        | **Campaign Comparison**              | Watch only         | Campaign Comparison, broken down by row.                                                   |
        | **Clicks vs Conversions**            | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Conversion Actions Breakdown**     | Watch only         | Conversion Actions Breakdown.                                                              |
        | **Conversion Drop Alert**            | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Conversion Funnel**                | Watch only         | Conversion Funnel, stage by stage.                                                         |
        | **Conversion Lag**                   | Watch only         | Conversion Lag, compared across items.                                                     |
        | **Conversion Rate Trend**            | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Conversion Rate by Campaign**      | Watch only         | Conversion Rate by Campaign.                                                               |
        | **Conversion Rate by Device**        | Watch only         | Conversion Rate by Device.                                                                 |
        | **Conversions Trend**                | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Conversions by Campaign**          | Watch only         | Conversions by Campaign.                                                                   |
        | **Conversions by Country**           | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Conversions by Day of Week**       | Watch only         | Conversions by Day of Week.                                                                |
        | **Conversions by Device**            | Watch only         | Conversions by Device.                                                                     |
        | **Conversions by Hour**              | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Landing Page Revenue**             | Watch only         | Landing Page Revenue, broken down by row.                                                  |
        | **Overspending Campaigns**           | Watch only         | Overspending Campaigns, broken down by row.                                                |
        | **ROAS**                             | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                  |
        | **ROAS Dropped Below Threshold**     | Alert band 3 / 1.5 | T1 programmatic ROAS shifts mean inventory or audience decay , investigate within the day. |
        | **ROAS Trend**                       | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **ROAS by Campaign**                 | Watch only         | ROAS by Campaign.                                                                          |
        | **ROAS by Day of Week**              | Watch only         | ROAS by Day of Week.                                                                       |
        | **ROAS by Device**                   | Watch only         | ROAS by Device.                                                                            |
        | **ROAS by Region**                   | Watch only         | ROAS by Region.                                                                            |
        | **Revenue by Campaign**              | Watch only         | Revenue by Campaign.                                                                       |
        | **Search Terms Report**              | Watch only         | Search Terms Report, broken down by row.                                                   |
        | **Spend by Campaign**                | Watch only         | Spend by Campaign.                                                                         |
        | **T1 Audit Pixel Firing Rate Decay** | Merchant rule      | T1's older identity layer is hit hardest by ITP , pixel decay = audience signal collapse.  |
        | **Top Cities by Conversions**        | Watch only         | Top Cities by Conversions.                                                                 |
        | **Top Keywords by Conversions**      | Watch only         | Top Keywords by Conversions.                                                               |
        | **Top Performing Campaigns**         | Watch only         | Top Performing Campaigns, broken down by row.                                              |
        | **Total Revenue**                    | Watch only         | Description pending editorial review; the signal is live.                                  |
        | **Underspending Campaigns**          | Watch only         | Underspending Campaigns, broken down by row.                                               |
        | **Worst Performing Campaigns**       | Watch only         | Worst Performing Campaigns, broken down by row.                                            |
        | **Zero-Conversion Spend**            | Watch only         | Description pending editorial review; the signal is live.                                  |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                                       | Alert behaviour    | What it tracks                                                                                     |
        | -------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Budget Utilisation**                       | Alert band 70 / 30 | Description pending editorial review; the signal is live.                                          |
        | **CPA Trend**                                | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CPA by Keyword**                           | Watch only         | CPA by Keyword.                                                                                    |
        | **CPC Anomaly**                              | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CPC Spike Detection**                      | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CPC Trend**                                | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                          |
        | **CTR Trend**                                | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CTR by Keyword**                           | Watch only         | CTR by Keyword.                                                                                    |
        | **Impression Share**                         | Alert band 70 / 40 | Description pending editorial review; the signal is live.                                          |
        | **Impressions Trend**                        | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Quality Score Distribution**               | Alert band 7 / 4   | Quality Score Distribution, compared across items.                                                 |
        | **Spend Anomaly**                            | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Spend Over Time**                          | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                          |
        | **Spend vs Budget**                          | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Top Keywords by Spend**                    | Watch only         | Top Keywords by Spend.                                                                             |
        | **Total Spend**                              | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Wasted Spend**                             | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Wasted-Spend Burst (flight pacing drift)** | Alert band 5 / 50  | T1 flight pacing drift = under-deliver-then-burn-end-of-flight; catches before the last 48h surge. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                 |
        | -------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------- |
        | **Active PMP Catalog Deals on Out-of-Stock SKUs**  | Alert band 5 / 50 | T1 PMP deals are expensive , running them at OOS SKUs burns through the agreed floor with no conversion.       |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | Defensive branded targeting on T1 cannibalising free organic , common pattern in agency-trading-desk accounts. |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                      |
        | **Landing Pages with Poor Web Vitals**             | Merchant rule     | T1 display/video click-throughs land on the same merchant pages , LCP regression breaks the whole funnel.      |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on T1 catalog/PMP campaigns whose Feedonomics feed has rejections. Creative falls back, CR drops.            |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across advertisers, campaigns, creatives, logins, report ingstdperformances on MediaMath (T1). 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=mediamath)

    #### Ready to build your first MediaMath (T1) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | advertisers               | 1               | 0                |
      | campaigns                 | 1               | 0                |
      | creatives                 | 1               | 0                |
      | logins                    | 0               | 1                |
      | report ingstdperformances | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Medusa on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/medusa

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Medusa.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Medusa.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/medusa) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=medusa)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (14 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                        |
        | ------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Cancellation Rate**                       | Alert band 1 / 3   | Canceled orders / total orders. Rising cancellation = fulfilment, fraud, or stock-promise problems.                                                   |
        | **Cart Loss from Slow Pages**               | Merchant rule      | Estimated revenue lost where slow Core Web Vitals on top storefront pages drive cart abandonment. Headless stores own their own front end, so this is |
        | **Catalogue Drift vs Marketplace Listings** | Merchant rule      | Same SKU OOS or mispriced on Medusa vs a marketplace = oversell risk and catalogue drift.                                                             |
        | **High-Value Customers Unengaged on Email** | Merchant rule      | Top spenders going cold in the email tool. Trigger a win-back before they churn.                                                                      |
        | **Low-Stock Products**                      | Merchant rule      | Variants approaching zero inventory from the inventory module. Reorder-window trigger.                                                                |
        | **OOS SKUs with Active Ad Spend**           | Merchant rule      | Spend burning on SKUs the inventory module says can't ship. Pause immediately.                                                                        |
        | **Out-of-Stock Products**                   | Alert band 0 / 5   | Variants with inventory\_quantity \<= 0 and manage\_inventory true. Direct lost-sales signal.                                                         |
        | **Refund Rate**                             | Alert band 2 / 5   | Refunded order count / total orders. The headline returns-health metric; spikes flag product or fulfilment issues.                                    |
        | **Refund Value**                            | Merchant rule      | Total refunded\_total in the window. Tracks the cash impact of returns, not just the count.                                                           |
        | **Refund-Rate Spike**                       | Alert band 2 / 5   | Sudden refund surge = product defect, fraud wave, or fulfilment failure. Surfaces to the ops feed immediately.                                        |
        | **Refunded Order Count**                    | Merchant rule      | Count of orders with a refund in the window. Volume companion to refund rate.                                                                         |
        | **Revenue at Risk**                         | Merchant rule      | Live estimate of revenue exposed by OOS SKUs, unfulfilled aged orders, and refund spikes. Top-of-screen risk gauge.                                   |
        | **Stock-Out Burst (>5 SKUs in \<1h)**       | Merchant rule      | A burst of SKUs going OOS at once usually means an inventory-sync break or a flash-sale stockout.                                                     |
        | **Unfulfilled Orders**                      | Alert band 10 / 50 | Orders in not\_fulfilled / partially\_fulfilled from the fulfilment module. Backlog = customer-promise risk.                                          |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                                  | Alert behaviour    | What it tracks                                                                                                                                           |
        | ------------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**                                 | Alert band 0 / -5  | Revenue / order count. Falling AOV with flat volume signals discount creep or basket-size erosion.                                                       |
        | **Catalogue Gaps (missing desc / image / SKU / price)** | Alert band 5 / 20  | Products missing description, thumbnail, variant SKU, or price. Headless storefronts have no SaaS guard-rails, so gaps silently suppress conversion.     |
        | **Coupon Usage Rate**                                   | Alert band 20 / 40 | Share of orders (30d) with a linked promotion requiring a customer-entered code (Promotion.is\_automatic=false), from /admin/orders?fields=\*promotions. |
        | **New vs Returning Customers**                          | Watch only         | Split of first-time vs repeat purchasers in the window. Acquisition-vs-retention balance.                                                                |
        | **Order Count**                                         | Alert band 0 / -10 | Count of orders placed in the window. Pairs with revenue to separate volume from value moves.                                                            |
        | **Repeat Purchase Rate**                                | Alert band 25 / 10 | Share of customers with orders\_count > 1. Low repeat rate = retention problem worth a win-back flow.                                                    |
        | **Revenue Trend**                                       | Watch only         | Daily revenue over 90 days. Visual baseline the alert thresholds read against.                                                                           |
        | **Revenue by Currency**                                 | Watch only         | Revenue grouped by currency\_code. Multi-currency is first-class in Medusa, so currency mix matters for FX and pricing.                                  |
        | **Revenue by Region**                                   | Watch only         | Per-region revenue split from the Medusa region model. Reveals which regions carry the business and which are dormant.                                   |
        | **Total Revenue**                                       | Alert band 0 / -5  | Captured order revenue across the selected window, summed from /admin/orders. Headline pulse metric.                                                     |
      </Accordion>

      <Accordion title="Run operations (4 signals)">
        | Signal                       | Alert behaviour    | What it tracks                                                                                                                                           |
        | ---------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Awaiting Payment Orders**  | Merchant rule      | Orders stuck in awaiting / not\_paid > 24h usually = payment-provider issue or customer-side dropoff.                                                    |
        | **Fulfillment Rate**         | Alert band 95 / 90 | Orders with fulfillment\_status fulfilled or shipped ÷ total orders (30d), from the same /admin/orders fetch used elsewhere. partially\_shipped and othe |
        | **Fulfilment Status Mix**    | Watch only         | Distribution of fulfillment\_status across orders. Shows where orders pile up in the fulfilment pipeline.                                                |
        | **Order Processing Backlog** | Alert band 10 / 50 | Unfulfilled orders piling up above baseline - fulfilment provider or warehouse bottleneck.                                                               |
      </Accordion>

      <Accordion title="Catalogue quality (2 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                                                                         |
        | -------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Products Missing Description** | Alert band 5 / 20 | Share of fetched products with an empty description field, from /admin/products. A single-concept percent cut of the description component already fol |
        | **Total Products**               | Watch only        | Published product count from /admin/products. Catalogue-size baseline.                                                                                 |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                         | Alert behaviour | What it tracks                                                                                                              |
        | ------------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------------------- |
        | **Region-Specific Order Drop** | Merchant rule   | If one region stops producing orders while others continue, indicates a region-specific checkout/payment/storefront outage. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                |
        | ------------------- | --------------- | --------------------------------------------- |
        | **Total Customers** | Watch only      | Total customer records from /admin/customers. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **0 write** operations across customers, inventory items, orders, products, product variants, regions on Medusa. 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=medusa)

    #### Ready to build your first Medusa 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | customers        | 1               | 0                |
      | inventory items  | 1               | 0                |
      | orders           | 1               | 0                |
      | products         | 1               | 0                |
      | product variants | 1               | 0                |
      | regions          | 1               | 0                |
      | returns          | 1               | 0                |
      | usermes          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Mercari on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mercari

Monitor Mercari listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Mercari listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=mercari)

<CardGroup>
  <Card title="37">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (37)">
    ### Monitor performance

    37 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country**                                | Watch only         | AOV by Country.                                                                                                                                        |
        | **Buyer Messages Unread**                         | Watch only         | Buyer Messages Unread as exposed by the Mercari integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Days Since Last Payout**                        | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Fees Paid**                         | Watch only         | Marketplace Fees Paid as exposed by the Mercari integration. The metric is computed from the latest available data and refreshed on the standard data  |
        | **Mercari Health Score**                          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Oldest Pending Payout (days)**                  | Watch only         | Oldest Pending Payout (days) as exposed by the Mercari integration. The metric is computed from the latest available data and refreshed on the standar |
        | **Orders / Day**                                  | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country**                             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                               | Watch only         | Pending Payouts as exposed by the Mercari integration. The metric is computed from the latest available data and refreshed on the standard data refres |
        | **Pending Shipment**                              | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Return Rate**                                   | Alert band 5 / 15  | Resale return rates run higher than retail (5-15%). Spike on Good-condition items = grading drift signal.                                              |
        | **Returns on 'Good / Like New' Items**            | Alert band 5 / 15  | Returns on items graded 'Good' or better with reason 'condition mismatch' = grading drift to fix in next intake.                                       |
        | **Seller Rating**                                 | Alert band 95 / 85 | Description pending editorial review; the signal is live.                                                                                              |
        | **Seller Rating / Return Rate Threshold Crossed** | Alert band 95 / 85 | Alerts for Seller Rating / Return Rate Threshold Crossed.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                   |
        | ---------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------- |
        | **Average Sale Price**                   | Alert band 0 / -5  | Resale ASP varies widely by category , drops often signal Smart Pricing erosion vs your floor.                   |
        | **Listings in 7-Day Freshness Boost**    | Merchant rule      | Mercari aggressively boosts listings \<7d old in search. Below 40% in-boost = systematic re-listing opportunity. |
        | **Listings with Brand Attribute Filled** | Alert band 90 / 70 | Mercari search heavily weights brand attribute , missing brand = lost-by-default search filter.                  |
        | **Mercari Fee % of Revenue**             | Alert band 12 / 18 | 10% selling fee + 2.9%+\$0.50 payment processing.                                                                |
        | **Net Revenue (after fees)**             | Alert band 0 / -5  | Net of Mercari's 10% selling fee + 2.9%+\$0.50 payment processing.                                               |
        | **Orders**                               | Watch only         | Description pending editorial review; the signal is live.                                                        |
        | **Revenue Over Time**                    | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                        |
        | **Ships-Within-3-Days Rate**             | Merchant rule      | Mercari's recommended ship-window , sustained \<90% lowers Fast Shipper badge and search visibility.             |
        | **Top Listings by Revenue**              | Watch only         | Top Listings by Revenue.                                                                                         |
        | **Total Revenue**                        | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                        |
      </Accordion>

      <Accordion title="Catalogue quality (7 signals)">
        | Signal                                     | Alert behaviour   | What it tracks                                                                                                                                         |
        | ------------------------------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**                        | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Listing Age (days)**             | Merchant rule     | Mercari's freshness boost decays sharply after 7d , average >14d = re-listing strategy needed.                                                         |
        | **Listings Expiring Soon**                 | Watch only        | Listings Expiring Soon as exposed by the Mercari integration. The metric is computed from the latest available data and refreshed on the standard data |
        | **Listings Where Smart Pricing Hit Floor** | Merchant rule     | Smart Pricing reached the seller-defined floor and held , review whether the floor itself needs raising or item needs delisting.                       |
        | **Mercari Suspended Listings (24h)**       | Alert band 5 / 50 | Alerts for Mercari Suspended Listings (24h).                                                                                                           |
        | **Suspended Listings**                     | Alert band 5 / 50 | Mercari suspends for prohibited items, IP infringement, or policy violations.                                                                          |
        | **Total Listings**                         | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                               | Alert behaviour   | What it tracks                                                                                                                         |
        | ---------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Mercari Listings for Sold-Elsewhere Items** | Alert band 0 / 5  | Resale-specific risk: one-of-a-kind items sold on another platform but still active on Mercari → buyer pays, then refund + bad review. |
        | **Late Shipments Risking Fast Shipper Badge**        | Merchant rule     | Alerts for Late Shipments Risking Fast Shipper Badge.                                                                                  |
        | **Listings Drifting from BC**                        | Alert band 5 / 50 | Listings Drifting from BC, broken down by row.                                                                                         |
        | **Listings Failing Feedonomics Validation**          | Alert band 2 / 5  | Mercari isn't a typical Feedonomics destination but some merchants distribute via it.                                                  |
        | **Revenue at Risk (live)**                           | Merchant rule     | Description pending editorial review; the signal is live.                                                                              |
        | **Same Item Priced Differently vs Depop / Vinted**   | Merchant rule     | Same one-of-a-kind item cross-listed at very different prices across resale platforms , buyers Google for cheapest.                    |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **1 write** operations across listings, oauthtokens, orders, selleraccounts on Mercari. 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=mercari)

    #### Ready to build your first Mercari 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | listings       | 1               | 0                |
      | oauthtokens    | 0               | 1                |
      | orders         | 1               | 0                |
      | selleraccounts | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Microsoft Ads (Bing) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/microsoft-ads

Monitor Microsoft Ads (Bing) campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Microsoft Ads (Bing) campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/microsoft-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=microsoft-ads)

<CardGroup>
  <Card title="73">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (73)">
    ### Monitor performance

    73 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (40 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                                        |
        | ----------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**                             | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **CPC by Campaign**                             | Watch only         | CPC by Campaign.                                                                                                                                      |
        | **CTR by Campaign**                             | Watch only         | CTR by Campaign.                                                                                                                                      |
        | **Campaign Comparison**                         | Watch only         | Campaign Comparison, broken down by row.                                                                                                              |
        | **Clicks vs Conversions**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Conversion Actions Breakdown**                | Watch only         | Conversion Actions Breakdown.                                                                                                                         |
        | **Conversion Drop Alert**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Conversion Funnel**                           | Watch only         | Conversion Funnel, stage by stage.                                                                                                                    |
        | **Conversion Lag**                              | Watch only         | Conversion Lag, compared across items.                                                                                                                |
        | **Conversion Rate Trend**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Conversion Rate by Campaign**                 | Watch only         | Conversion Rate by Campaign.                                                                                                                          |
        | **Conversion Rate by Device**                   | Watch only         | Conversion Rate by Device.                                                                                                                            |
        | **Conversions Trend**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Conversions by Campaign**                     | Watch only         | Conversions by Campaign.                                                                                                                              |
        | **Conversions by Country**                      | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Conversions by Day of Week**                  | Watch only         | Conversions by Day of Week.                                                                                                                           |
        | **Conversions by Device**                       | Watch only         | Conversions by Device.                                                                                                                                |
        | **Conversions by Hour**                         | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Impression Share Lost (Budget)**              | Alert band 5 / 20  | % of eligible search impressions not shown because daily budget ran out, impressions-weighted across the reported campaigns. Fix: raise budget on the |
        | **Landing Page Revenue**                        | Watch only         | Landing Page Revenue, broken down by row.                                                                                                             |
        | **Overspending Campaigns**                      | Watch only         | Overspending Campaigns, broken down by row.                                                                                                           |
        | **ROAS**                                        | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                                                             |
        | **ROAS Dropped Below Threshold**                | Alert band 3 / 1.5 | First number to ping when the hedge-against-Google narrative is going to look bad on Monday.                                                          |
        | **ROAS Trend**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **ROAS by Campaign**                            | Watch only         | ROAS by Campaign.                                                                                                                                     |
        | **ROAS by Day of Week**                         | Watch only         | ROAS by Day of Week.                                                                                                                                  |
        | **ROAS by Device**                              | Watch only         | ROAS by Device.                                                                                                                                       |
        | **ROAS by Region**                              | Watch only         | ROAS by Region.                                                                                                                                       |
        | **Revenue by Campaign**                         | Watch only         | Revenue by Campaign.                                                                                                                                  |
        | **Search Terms Report**                         | Watch only         | Search Terms Report, broken down by row.                                                                                                              |
        | **Spend by Campaign**                           | Watch only         | Spend by Campaign.                                                                                                                                    |
        | **Top Cities by Conversions**                   | Watch only         | Top Cities by Conversions.                                                                                                                            |
        | **Top Keywords by Conversions**                 | Watch only         | Top Keywords by Conversions.                                                                                                                          |
        | **Top Performing Campaigns**                    | Watch only         | Top Performing Campaigns, broken down by row.                                                                                                         |
        | **Total Revenue**                               | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **UET Tag Tracking Broken**                     | Merchant rule      | UET tag silently failing on ITP/AdBlock-heavy audiences. Smart Bidding retrains on degraded signal within 24h.                                        |
        | **Underspending Campaigns**                     | Watch only         | Underspending Campaigns, broken down by row.                                                                                                          |
        | **Wasted-Spend Burst (Audience Network drift)** | Alert band 5 / 50  | Audience Network auto-extension can drift to low-quality publishers fast , catch before the week's budget eaten.                                      |
        | **Worst Performing Campaigns**                  | Watch only         | Worst Performing Campaigns, broken down by row.                                                                                                       |
        | **Zero-Conversion Spend**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Shopping Ads on Out-of-Stock SKUs**       | Alert band 5 / 50 | Spend on Microsoft Shopping ads pointing at out-of-stock SKUs. Pause the product group, hold the budget.                                               |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | Branded keywords running on Bing that also rank #1 organically on Google. Cross-engine cannibalisation , pause Bing branded or restrict to genuinely i |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
        | **Landing Pages with Poor Web Vitals**             | Merchant rule     | Bing traffic skews desktop , LCP regression on landing pages drops Quality Score same as Google.                                                       |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on a Microsoft Shopping campaign whose Feedonomics feed has live rejections. Bid signal degrades until cleared.                                      |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Search impression share lost to budget > 20%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Losing more than a fifth of impression share to budget means demand exists that the account cannot buy; either budget or efficiency has to move.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-TARGET-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **4 write** operations across campaign managementadquerys, campaign managementcampaignquerys, commonoauth2tokens, customer managementaccounts, report inggeneratereports on Microsoft Ads (Bing). 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=microsoft-ads)

    #### Ready to build your first Microsoft Ads (Bing) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                          | Read operations | Write operations |
      | --------------------------------- | --------------- | ---------------- |
      | campaign managementadquerys       | 0               | 1                |
      | campaign managementcampaignquerys | 0               | 1                |
      | commonoauth2tokens                | 0               | 1                |
      | customer managementaccounts       | 1               | 0                |
      | report inggeneratereports         | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Microsoft Dynamics 365 Finance on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/microsoft-dynamics

Monitor Microsoft Dynamics 365 Finance performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Microsoft Dynamics 365 Finance performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=microsoft-dynamics)

<CardGroup>
  <Card title="86">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (86)">
    ### Monitor performance

    86 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (61 signals)">
        | Signal                                                    | Alert behaviour      | What it tracks                                                                                                                                         |
        | --------------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AP Aging , 60+ Days**                                   | Alert band 10 / 30   | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Aging Buckets**                                      | Watch only           | AR Aging Buckets, compared across items.                                                                                                               |
        | **AR Aging , 60+ Days**                                   | Alert band 5 / 15    | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Balance (live, by Legal Entity)**                    | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Accrual Reversals (last close)**                        | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Active Customers**                                      | Watch only           | Active Customers from Microsoft Dynamics 365 Finance, grouped under Customer Master. Computes when a live Microsoft Dynamics 365 Finance tenant is con |
        | **Active Vendors**                                        | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Landed Cost per Unit**                          | Alert band 0 / 10    | Average Landed Cost per Unit from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance ten |
        | **Average Sales Order Value**                             | Alert band 0 / -5    | Average Sales Order Value from Microsoft Dynamics 365 Finance, grouped under Sales Orders. Computes when a live Microsoft Dynamics 365 Finance tenant  |
        | **B2B Payment Terms Mix**                                 | Watch only           | B2B Payment Terms Mix from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is co |
        | **Cash Application Rate**                                 | Alert band 95 / 85   | Cash Application Rate from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is co |
        | **Cash Applied Today**                                    | Watch only           | Cash Applied Today from Microsoft Dynamics 365 Finance, grouped under Executive Overview. Computes when a live Microsoft Dynamics 365 Finance tenant i |
        | **Company Health Roll-up**                                | Watch only           | Company Health Roll-up from Microsoft Dynamics 365 Finance, grouped under Executive Overview. Computes when a live Microsoft Dynamics 365 Finance tena |
        | **Credit Hold Spike**                                     | Watch only           | Credit Hold Spike from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is connec |
        | **Customer Churn Signals**                                | Watch only           | Customer Churn Signals from Microsoft Dynamics 365 Finance, grouped under Customer Master. Computes when a live Microsoft Dynamics 365 Finance tenant  |
        | **Customer Credit Utilisation**                           | Alert band 60 / 85   | Customer Credit Utilisation from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant |
        | **Customers on Credit Hold (IsCreditHold=true)**          | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **D365 Finance Health Score**                             | Merchant rule        | Composite: batch-error-clean x flow-runs-healthy x AR-aging-low x inventory-variance-low.                                                              |
        | **DSO Increase Alert**                                    | Watch only           | DSO Increase Alert from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is conne |
        | **Days Sales Outstanding (DSO)**                          | Alert band 30 / 60   | Description pending editorial review; the signal is live.                                                                                              |
        | **Dead Stock Threshold Breach**                           | Watch only           | Dead Stock Threshold Breach from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365 Finance tenant i |
        | **ERP-vs-Ecom Inventory Variance %**                      | Alert band 1 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Ecom Customers Absent from D365**                       | Alert band 0 / 10    | Description pending editorial review; the signal is live.                                                                                              |
        | **FX Currency Exposure**                                  | Alert band 5 / 15    | FX Currency Exposure from Microsoft Dynamics 365 Finance, grouped under Executive Overview. Computes when a live Microsoft Dynamics 365 Finance tenant |
        | **Gross Margin Percentage**                               | Alert band 0 / 5     | Gross Margin Percentage from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance tenant i |
        | **High-Value Overdue Invoices**                           | Watch only           | High-Value Overdue Invoices from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant |
        | **Intercompany Operating-Unit Imbalances**                | Merchant rule        | Cross-legal-entity / cross-OU journals that don't balance. Blocks consolidation in Microsoft Financial Reporting.                                      |
        | **Inventory Aging**                                       | Alert band 5 / 15    | Inventory Aging from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365 Finance tenant is connected; |
        | **Inventory Carrying Cost**                               | Watch only           | Inventory Carrying Cost from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance tenant i |
        | **Inventory On-Hand Went Negative (any Warehouse)**       | Merchant rule        | Alerts for Inventory On-Hand Went Negative (any Warehouse).                                                                                            |
        | **Inventory Turnover Ratio**                              | Alert band 4 / 2     | Inventory Turnover Ratio from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365 Finance tenant is c |
        | **Inventory Value by Warehouse**                          | Watch only           | Inventory Value by Warehouse.                                                                                                                          |
        | **Journal Imbalances (rejected at posting)**              | Alert band 0 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Journals Rejected at Posting (PostingStatus=Rejected)** | Alert band 0 / 5     | Alerts for Journals Rejected at Posting (PostingStatus=Rejected).                                                                                      |
        | **Journals by Source Module**                             | Watch only           | AR / AP / GL / Inventory / Project / Bank split. Ecom-driven AR share creep = integration scaling.                                                     |
        | **Landed Cost Variance vs Standard**                      | Alert band 2 / 5     | Landed Cost Variance vs Standard from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance |
        | **Ledger Period Close Past Deadline**                     | Alert band 0 / 5     | Alerts for Ledger Period Close Past Deadline.                                                                                                          |
        | **Ledger Period Close Status**                            | Alert band 0 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Manual Journals as % of Total**                         | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Margin Compression**                                    | Watch only           | Margin Compression from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance tenant is con |
        | **Margin Erosion Alerts**                                 | Alert band 0 / 5     | Margin Erosion Alerts from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance tenant is  |
        | **New Customers (30d)**                                   | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Hand Inventory Value (by Warehouse)**                | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Open (Not Posted) Journal Entries**                     | Alert band 0 / 50    | LedgerJournalTrans rows in NotPosted / ReadyToPost / InProcess. Surface stuck-in-process queue.                                                        |
        | **Open Sales Order Value**                                | Watch only           | Open Sales Order Value from Microsoft Dynamics 365 Finance, grouped under Sales Orders. Computes when a live Microsoft Dynamics 365 Finance tenant is  |
        | **Open Sales Orders**                                     | Watch only           | Open Sales Orders from Microsoft Dynamics 365 Finance, grouped under Sales Orders. Computes when a live Microsoft Dynamics 365 Finance tenant is conne |
        | **Orders on Credit Hold**                                 | Alert band 0 / 5     | Orders on Credit Hold from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is co |
        | **Overdue Invoice Value**                                 | Alert band 0 / 50000 | Overdue Invoice Value from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is co |
        | **Period Close On-Time Rate (12mo)**                      | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Power Automate Flow Failures (ecom integration)**       | Merchant rule        | Power Automate flows linking ecom triggers to F\&O actions. Spike = trigger source down OR F\&O connector throttled.                                   |
        | **Returns Count**                                         | Alert band 5 / 20    | Returns Count from Microsoft Dynamics 365 Finance, grouped under Sales Orders. Computes when a live Microsoft Dynamics 365 Finance tenant is connected |
        | **Sales Order State Breakdown**                           | Watch only           | Sales Order State Breakdown from Microsoft Dynamics 365 Finance, grouped under Sales Orders. Computes when a live Microsoft Dynamics 365 Finance tenan |
        | **Sales Order to Invoice Lead Time**                      | Alert band 3 / 7     | Sales Order to Invoice Lead Time from Microsoft Dynamics 365 Finance, grouped under Sales Orders. Computes when a live Microsoft Dynamics 365 Finance  |
        | **Sales Orders Blocked on Inventory or Credit**           | Alert band 0 / 5     | Sales Orders Blocked on Inventory or Credit from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365  |
        | **Slow-Moving Inventory (>90d no movement)**              | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Top Findings Across Companys**                          | Watch only           | Top Findings Across Companys from Microsoft Dynamics 365 Finance, grouped under Multi-Entity. Computes when a live Microsoft Dynamics 365 Finance tena |
        | **Top SKUs by Inventory Value**                           | Watch only           | Top SKUs by Inventory Value from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365 Finance tenant i |
        | **Total COGS**                                            | Watch only           | Total COGS from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance tenant is connected;  |
        | **Total Inventory Value**                                 | Watch only           | Total Inventory Value from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365 Finance tenant is conn |
        | **Unpaid Invoice Count**                                  | Watch only           | Unpaid Invoice Count from Microsoft Dynamics 365 Finance, grouped under AP/AR Cycle. Computes when a live Microsoft Dynamics 365 Finance tenant is con |
        | **Vendor Payment On-Time Rate**                           | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (14 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cash Collected**                              | Alert band 0 / -15 | Cash Collected from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant is conne |
        | **Consolidated Revenue Trend**                  | Watch only         | Consolidated Revenue Trend from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance ten |
        | **Customers in Dataverse Not Promoted to D365** | Merchant rule      | Dual-write integration gap , Dataverse contact created but D365 customer master entry never landed. Common F\&O+CE sync failure.                       |
        | **Invoiced Revenue**                            | Alert band 0 / -5  | Invoiced Revenue from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant is con |
        | **Revenue Booked Over Time**                    | Watch only         | Revenue Booked Over Time from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenan |
        | **Revenue Booked into GL**                      | Watch only         | Revenue Booked into GL from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant  |
        | **Revenue Gap Spike**                           | Watch only         | Revenue Gap Spike from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant is co |
        | **Revenue Gap vs Commerce**                     | Alert band 0 / 5   | Revenue Gap vs Commerce from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant |
        | **Revenue by Company**                          | Watch only         | Revenue by Company from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant is c |
        | **Revenue by Currency**                         | Watch only         | Revenue by Currency from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant is  |
        | **Revenue by Segment**                          | Watch only         | Revenue by Segment from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant is c |
        | **Sales Credit Memo Value**                     | Watch only         | Sales Credit Memo Value from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenant |
        | **Top B2B Accounts by Revenue**                 | Watch only         | Top B2B Accounts by Revenue from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance te |
        | **Top Customers by Revenue**                    | Watch only         | Top Customers by Revenue from Microsoft Dynamics 365 Finance, grouped under Revenue & Sales. Computes when a live Microsoft Dynamics 365 Finance tenan |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                                                  | Alert behaviour         | What it tracks                                                                                                                                         |
        | ------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AR Aging on Customers with Active Ecom Orders**       | Alert band 1000 / 10000 | Should auto-flag IsCreditHold=true via Power Automate flow when this triggers.                                                                         |
        | **Dead Stock with Active Ad Spend**                     | Alert band 5 / 15       | Dead Stock with Active Ad Spend from Microsoft Dynamics 365 Finance, grouped under Cross-Channel: Revenue at Risk. Computes when a live Microsoft Dyna |
        | **Ecom Customers Absent from D365 Customer Master**     | Alert band 0 / 10       | Description pending editorial review; the signal is live.                                                                                              |
        | **Ecom Orders Missing Matching D365 Free-Text Invoice** | Merchant rule           | Ecom orders the merchant fulfilled but D365 never billed. Common cause: Power Automate flow trigger silently missed an event.                          |
        | **Low Stock Alerts**                                    | Alert band 0 / 5        | Low Stock Alerts from Microsoft Dynamics 365 Finance, grouped under Inventory. Computes when a live Microsoft Dynamics 365 Finance tenant is connected |
        | **OOS with Open Sales Order Demand**                    | Alert band 0 / 5        | OOS with Open Sales Order Demand from Microsoft Dynamics 365 Finance, grouped under Cross-Channel: Revenue at Risk. Computes when a live Microsoft Dyn |
        | **Revenue Gap**                                         | Watch only              | Revenue Gap from Microsoft Dynamics 365 Finance, grouped under Cross-Channel: Revenue at Risk. Computes when a live Microsoft Dynamics 365 Finance ten |
        | **SKUs with D365-vs-Ecom Inventory Drift >5%**          | Alert band 1 / 5        | SKUs with D365-vs-Ecom Inventory Drift >5%, broken down by row.                                                                                        |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                          | Alert behaviour | What it tracks                                                                                                                   |
        | ------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Batch Job Error Queue (24h)** | Merchant rule   | F\&O Data Import/Export Framework batch jobs in Error status. Common F\&O failure mode , easy to miss without active monitoring. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                                                                                        |
        | ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Company Performance** | Watch only      | Company Performance from Microsoft Dynamics 365 Finance, grouped under Executive Overview. Computes when a live Microsoft Dynamics 365 Finance tenant |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal            | Alert behaviour | What it tracks                                                                                                                                         |
        | ----------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Margin by SKU** | Watch only      | Margin by SKU from Microsoft Dynamics 365 Finance, grouped under Margin & Cost. Computes when a live Microsoft Dynamics 365 Finance tenant is connecte |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **1 write** operations across datacustomersv3s, datainventoryonhands, dataledgerjournaltrans, datamainaccounts, datavendorsv2s, oauth2tokens on Microsoft Dynamics 365 Finance. 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=microsoft-dynamics)

    #### Ready to build your first Microsoft Dynamics 365 Finance 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | datacustomersv3s       | 1               | 0                |
      | datainventoryonhands   | 1               | 0                |
      | dataledgerjournaltrans | 1               | 0                |
      | datamainaccounts       | 1               | 0                |
      | datavendorsv2s         | 1               | 0                |
      | oauth2tokens           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Microsoft Teams on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/microsoft-teams

Monitor Microsoft Teams performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Microsoft Teams performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=microsoft-teams)

<CardGroup>
  <Card title="21">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="37">
    proven workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (21)">
    ### Monitor performance

    21 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                          |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active User Drop Alert**             | Alert band 0 / -30 | Active-users change vs the prior 30d; fires when adoption drops sharply per the collab\_active\_users\_trend band.                                      |
        | **Active Users (30d)**                 | Alert band 0 / -30 | Distinct users from getTeamsUserActivityUserDetail(D90) whose Last Activity Date is within the last 30d. change\_pct = avg daily active-users proxy cur |
        | **Avg Daily Messages (30d)**           | Watch only         | 30d total messages / number of days with any message activity in getTeamsUserActivityCounts(D90).                                                       |
        | **Avg Messages per Active User (30d)** | Watch only         | 30d total messages (team + private) / distinct 30d active users.                                                                                        |
        | **Calls (30d)**                        | Watch only         | Sum of Calls from getTeamsUserActivityCounts(D90) over the last 30d.                                                                                    |
        | **Calls per Active User (30d)**        | Watch only         | 30d calls / distinct 30d active users.                                                                                                                  |
        | **Collaboration Health Score**         | Alert band 80 / 55 | Composite 0-100: 100, minus 30 for active-users drop >30% vsP (15 for >15%), minus 25 for message volume drop >40% vsP (12 for >20%), minu              |
        | **Daily Calls Trend**                  | Watch only         | Daily Calls buckets from getTeamsUserActivityCounts(D90) over the last 30d.                                                                             |
        | **Daily Messages Trend**               | Watch only         | Daily Team Chat + Private Chat Messages buckets from getTeamsUserActivityCounts(D90) over the last 30d.                                                 |
        | **Meetings (30d)**                     | Watch only         | Sum of Meetings from getTeamsUserActivityCounts(D90) over the last 30d.                                                                                 |
        | **Meetings per Active User (30d)**     | Watch only         | 30d meetings / distinct 30d active users.                                                                                                               |
        | **Message Volume Drop Alert**          | Alert band 0 / -40 | Message-volume change vs the prior 30d; fires when a team goes quiet per the collab\_message\_volume\_trend band.                                       |
        | **Private Chat Messages (30d)**        | Watch only         | Sum of Private Chat Messages from getTeamsUserActivityCounts(D90) over the last 30d.                                                                    |
        | **Team Chat Messages (30d)**           | Watch only         | Sum of Team Chat Messages from getTeamsUserActivityCounts(D90) over the last 30d.                                                                       |
        | **Total Messages (30d)**               | Alert band 0 / -40 | Sum of Team Chat Messages + Private Chat Messages from getTeamsUserActivityCounts(D90) over the last 30d. change\_pct = 30d messages vs the prior 30d.  |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Users Change (vsP)**   | Alert band 0 / -30 | Percentage change in avg daily active-users proxy current 30d vs prior 30d from getTeamsUserActivityUserCounts(D90).                                   |
        | **Daily Active Users Trend**    | Watch only         | Daily active-users proxy from getTeamsUserActivityUserCounts(D90): max across the four per-activity user counts (team chat, private chat, calls, meeti |
        | **Engagement Rate (30d)**       | Watch only         | Distinct 30d active users / total (non-deleted) users from getTeamsUserActivityUserDetail(D90) x 100.                                                  |
        | **Inactive Users (30d)**        | Watch only         | Total (non-deleted) users minus distinct 30d active users from getTeamsUserActivityUserDetail(D90).                                                    |
        | **Message Volume Change (vsP)** | Alert band 0 / -40 | Percentage change in 30d total messages vs the prior 30d from getTeamsUserActivityCounts(D90).                                                         |
        | **Peak Activity Day (30d)**     | Watch only         | The single day with the highest Team Chat + Private Chat Messages in the last 30d; value is that day's message total, detail names the date.           |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Token invalid, expired or lacking the report scope the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        With invalid credentials the tool has stopped collecting entirely; every metric that depends on it is silently stale.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COLLAB-AUTH-001`
      </Accordion>

      <Accordion title="Active users dropped more than 30% vs the prior period">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Active users dropping by a third signals adoption failure or licence waste; both are worth catching within the billing cycle.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COLLAB-USERS-001`
      </Accordion>

      <Accordion title="Message volume dropped more than 40% vs the prior period (team going quiet)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Message volume collapsing usually means the team moved channels or an integration broke; either way the record of work is going dark.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COLLAB-MSG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **1 write** operations across oauth2tokens, report getteamsuseractivitycounts, report getteamsuseractivityusercounts, report getteamsuseractivityuserdetails on Microsoft Teams. 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=microsoft-teams)

    #### Proven workflow templates (37)

    <AccordionGroup>
      <Accordion title="Best-seller Availability Guard">
        **For** E-commerce manager · **Ready to deploy**

        watches hero SKUs and recommends substitutions, replenishment escalation or merchandising changes.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Budget Pacing Guard">
        **For** Performance marketing manager · **Ready to deploy**

        forecasts over/underspend against plan and stages bounded reallocations for approval.

        Tested alongside: Amazon Ads, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Readiness Gate">
        **For** E-commerce manager · **Ready to deploy**

        checks landing pages, products, inventory, tracking and links before launch; blocks “ready” if critical checks fail.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Checkout Journey Sentinel">
        **For** E-commerce manager · **Ready to deploy**

        scheduled storefront journey checks with screenshot/evidence and urgent escalation.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Creative Fatigue Watch">
        **For** Performance marketing manager · **Ready to deploy**

        detects declining response by creative/audience and opens a replacement brief.

        Tested alongside: Amazon Ads, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Daily Store Pulse">
        **For** E-commerce manager · **Ready to deploy**

        morning revenue, conversion, AOV, stock and incident briefing with only material changes.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Multi-store Divergence Watch">
        **For** E-commerce manager · **Ready to deploy**

        compares stores/regions and flags unexplained differences in price, availability, content or performance.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New Product Launch Checklist">
        **For** E-commerce manager · **Ready to deploy**

        verifies content, media, inventory, category, SEO and analytics before publish approval.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion Activation QA">
        **For** Performance marketing manager · **Ready to deploy**

        verifies ads, dates, URLs, tracking, inventory and storefront offer before spend begins.

        Tested alongside: Amazon Ads, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion QA and Rollback Pack">
        **For** E-commerce manager · **Ready to deploy**

        validates price, dates, eligibility and merchandising, then prepares reversible fixes.

        Tested alongside: BigCommerce, Shopify, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Search Query Waste Miner">
        **For** Performance marketing manager · **Ready to deploy**

        clusters irrelevant or expensive queries and drafts negative-keyword actions.

        Tested alongside: Amazon Ads, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Wasted Spend Watch">
        **For** Performance marketing manager · **Ready to deploy**

        alerts on spend with no meaningful outcomes and recommends pause, budget or targeting review.

        Tested alongside: Amazon Ads, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Auto-apply Guardrail Approval">
        **For** Security manager · **Ready to deploy**

        requires security sign-off when an automation gains broader write authority.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Blocked Work Escalator">
        **For** Engineering manager · **Ready to deploy**

        detects ageing PRs/tickets and identifies the missing decision or dependency.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Integrity Night Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        checks SKU identity, variants, price, availability and orphan records across systems.

        Tested alongside: BigCommerce, Shopify, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Change Failure Rate Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks failed deploys and highlights teams/services with worsening patterns.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Cloud Exposure Watch">
        **For** Security manager · **Ready to deploy**

        detects risky DNS, firewall, storage or edge configuration changes.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Connector Access Review">
        **For** Security manager · **Ready to deploy**

        inventories credentials, scopes, owners, use and age; routes unnecessary access for revocation.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Engineering Dependency Watch">
        **For** Engineering manager · **Ready to deploy**

        tracks vulnerable, unsupported or risky platform dependencies.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Executive Technology Pack">
        **For** Engineering manager · **Ready to deploy**

        translates technical risk and delivery evidence into commercial impact.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Fulfilment SLA Breach Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        predicts and escalates orders likely to miss dispatch or delivery promises.

        Tested alongside: BigCommerce, Shopify, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Containment Pack">
        **For** Security manager · **Ready to deploy**

        prepares reversible, scoped containment actions for human approval.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Incident Learning Loop">
        **For** Engineering manager · **Ready to deploy**

        creates the timeline, contributing factors, actions and follow-up ownership.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Monthly Security Evidence Pack">
        **For** Security manager · **Ready to deploy**

        retains what changed, who approved it, results and rollback availability.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Operations Morning Handover">
        **For** E-commerce operations manager · **Ready to deploy**

        summarises overnight exceptions, actions taken, unresolved risk and accountable owners.

        Tested alongside: BigCommerce, Shopify, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Exception Command Centre">
        **For** E-commerce operations manager · **Ready to deploy**

        detects stuck, failed or unusual orders and routes them with age and value-based urgency.

        Tested alongside: BigCommerce, Shopify, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Issue Triage">
        **For** Customer service manager · **Ready to deploy**

        enriches tickets with order, payment and fulfilment context and assigns the right queue.

        Tested alongside: HubSpot, BigCommerce, Shopify, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Peak Freeze Controller">
        **For** E-commerce operations manager · **Ready to deploy**

        pauses writes during trading freezes while continuing all monitoring and alerts.

        Tested alongside: BigCommerce, Shopify, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Privilege Drift Monitor">
        **For** Security manager · **Ready to deploy**

        alerts when repository, cloud or connector permissions exceed policy.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Proactive Delay List">
        **For** Customer service manager · **Ready to deploy**

        prepares, but does not send, customer communications for affected orders.

        Tested alongside: HubSpot, BigCommerce, Shopify, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Risk Gate">
        **For** Engineering manager · **Ready to deploy**

        scores change size, test evidence, service health and rollback readiness before approval.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Returns Anomaly Monitor">
        **For** E-commerce operations manager · **Ready to deploy**

        surfaces spikes by SKU, supplier, reason or cohort and assigns investigation.

        Tested alongside: BigCommerce, Shopify, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Audit">
        **For** Engineering manager · **Ready to deploy**

        verifies that rollbacks completed and downstream state returned to expected values.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Suspicious Change Correlator">
        **For** Security manager · **Ready to deploy**

        links identity, code, infrastructure and automation audit events.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Integration Risk Review">
        **For** Security manager · **Ready to deploy**

        assesses new connectors before activation and on material permission change.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Vulnerability Remediation Queue">
        **For** Security manager · **Ready to deploy**

        ranks findings by exploitability, exposure and affected revenue paths.

        Tested alongside: Cloudflare, GitHub, StagingPro, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Weekly Delivery and Reliability Brief">
        **For** Engineering manager · **Ready to deploy**

        combines throughput, failed changes, incidents, rollbacks and ageing work.

        Tested alongside: GitHub, Jira Cloud, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                               | Read operations | Write operations |
      | -------------------------------------- | --------------- | ---------------- |
      | oauth2tokens                           | 0               | 1                |
      | report getteamsuseractivitycounts      | 1               | 0                |
      | report getteamsuseractivityusercounts  | 1               | 0                |
      | report getteamsuseractivityuserdetails | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    23 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Mixpanel on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mixpanel

Monitor traffic, conversion and tracking integrity from Mixpanel, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Mixpanel, and catch instrumentation breaks before decisions are made on bad data.

[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=mixpanel)

<CardGroup>
  <Card title="38">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (38)">
    ### Monitor performance

    38 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (20 signals)">
        | Signal                                   | Alert behaviour | What it tracks                                                                                                                                         |
        | ---------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Session Duration**                 | Watch only      | Avg Session Duration from Mixpanel, grouped under Customer Behaviour. Computes when a live Mixpanel integration is connected; reconciles ecommerce aga |
        | **Avg Time to Convert**                  | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Biggest Funnel Step Drop-off**         | Merchant rule   | Biggest Funnel Step Drop-off, compared across items.                                                                                                   |
        | **Cohort Retention D30 %**               | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Cohort Retention D7 %**                | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Core Events Firing**                   | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Daily Active Users**                   | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Event Ingestion Lag**                  | Merchant rule   | Delay between client event timestamp and ingestion , high lag = SDK batching issue or pipeline backpressure.                                           |
        | **Event Volume Drop (>25% vs baseline)** | Merchant rule   | Alerts for Event Volume Drop (>25% vs baseline).                                                                                                       |
        | **Fastest-Decaying Cohort**              | Merchant rule   | Fastest-Decaying Cohort, broken down by row.                                                                                                           |
        | **Goal Completions**                     | Watch only      | Goal Completions from Mixpanel, grouped under Funnel Analysis. Computes when a live Mixpanel integration is connected; reconciles ecommerce against Mi |
        | **Monthly Active Users**                 | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Pageviews per Session**                | Watch only      | Pageviews per Session from Mixpanel, grouped under Customer Behaviour. Computes when a live Mixpanel integration is connected; reconciles ecommerce ag |
        | **Retention Curve**                      | Watch only      | Retention Curve over time.                                                                                                                             |
        | **Top 10 Events by Volume**              | Watch only      | Top 10 Events by Volume.                                                                                                                               |
        | **Top Exit Event**                       | Watch only      | Top Exit Event, broken down by row.                                                                                                                    |
        | **Top Pages**                            | Watch only      | Top Pages from Mixpanel, grouped under Customer Behaviour. Computes when a live Mixpanel integration is connected; reconciles ecommerce against Mixpan |
        | **Top Traffic Sources**                  | Watch only      | Top Traffic Sources from Mixpanel, grouped under Customer Behaviour. Computes when a live Mixpanel integration is connected; reconciles ecommerce agai |
        | **Top User Path (Flows)**                | Watch only      | Mixpanel-distinctive , the most-travelled event sequence. Shifts here = users finding a new (or broken) route.                                         |
        | **Total Event Volume**                   | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                   | Alert behaviour | What it tracks                                                                                                                                         |
        | ---------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Events per User**                  | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion-Path Share %**              | Merchant rule   | % of sessions whose path reaches the purchase event , falling = users drifting off the happy path.                                                     |
        | **Funnel Conversion Drop (>5pp in 24h)** | Merchant rule   | Alerts for Funnel Conversion Drop (>5pp in 24h).                                                                                                       |
        | **Funnel Conversion by Segment**         | Watch only      | Funnel Conversion by Segment.                                                                                                                          |
        | **New Users**                            | Watch only      | New Users from Mixpanel, grouped under Traffic Acquisition. Computes when a live Mixpanel integration is connected; reconciles ecommerce against Mixpa |
        | **New vs Returning Users**               | Watch only      | New vs Returning Users, shown by share.                                                                                                                |
        | **Primary Funnel Conversion %**          | Merchant rule   | Primary Funnel Conversion %, stage by stage.                                                                                                           |
        | **Real-Time Users**                      | Watch only      | Real-Time Users from Mixpanel, grouped under Traffic Acquisition. Computes when a live Mixpanel integration is connected; reconciles ecommerce against |
        | **Sessions**                             | Watch only      | Sessions from Mixpanel, grouped under Traffic Acquisition. Computes when a live Mixpanel integration is connected; reconciles ecommerce against Mixpan |
        | **Stickiness (DAU/MAU)**                 | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Bounce Rate**                                   | Alert band 40 / 60 | Bounce Rate from Mixpanel, grouped under Customer Behaviour. Computes when a live Mixpanel integration is connected; reconciles ecommerce against Mixp |
        | **Cart Abandonment Rate**                         | Alert band 60 / 75 | Cart Abandonment Rate from Mixpanel, grouped under Funnel Analysis. Computes when a live Mixpanel integration is connected; reconciles ecommerce again |
        | **Event Source vs Ecom Revenue Attribution**      | Merchant rule      | Event Source vs Ecom Revenue Attribution, broken down by row.                                                                                          |
        | **Landing Page Performance vs Bounce**            | Merchant rule      | Landing Page Performance vs Bounce, broken down by row.                                                                                                |
        | **Mixpanel Funnel Conversion vs Ecom Conversion** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Session Engagement vs Cart Abandonment**        | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                                | Alert behaviour | What it tracks                                                |
        | ----------------------------------------------------- | --------------- | ------------------------------------------------------------- |
        | **Event Tracking Broken (core event stopped firing)** | Merchant rule   | Alerts for Event Tracking Broken (core event stopped firing). |
        | **Mixpanel Tracking Health Score**                    | Merchant rule   | Description pending editorial review; the signal is live.     |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across engages, events, funnels, retentions, segmentations on Mixpanel. 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=mixpanel)

    #### Ready to build your first Mixpanel 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | engages       | 1               | 0                |
      | events        | 1               | 0                |
      | funnels       | 1               | 0                |
      | retentions    | 1               | 0                |
      | segmentations | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Mollie on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mollie

Monitor Mollie payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Mollie payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=mollie)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (8 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                      |
        | ----------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                  | Alert band 15 / 30   | Customers who saw the 3DS / SCA challenge and bailed. High abandon = checkout friction.                             |
        | **Chargeback Rate**                       | Alert band 0.5 / 0.9 | Chargebacks / total payments. Above \~0.9% risks network monitoring programmes.                                     |
        | **Decline Rate**                          | Alert band 5 / 8     | Description pending editorial review; the signal is live.                                                           |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When Mollie declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss. |
        | **Dispute Rate**                          | Alert band 0.5 / 1   | Description pending editorial review; the signal is live.                                                           |
        | **Refund Rate**                           | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                           |
        | **Refund Volume**                         | Merchant rule        | Description pending editorial review; the signal is live.                                                           |
        | **Top Decline Reasons**                   | Merchant rule        | Mollie failureReason coded (insufficient\_funds, card\_declined, invalid\_card\_number) - each has a different fix. |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                          |
        | -------------------------------- | ------------------ | --------------------------------------------------------------------------------------- |
        | **Average Transaction**          | Merchant rule      | Description pending editorial review; the signal is live.                               |
        | **Avg Settlement Time (days)**   | Alert band 2 / 5   | Capture-to-payout lag in days.                                                          |
        | **Oldest Pending Payout (days)** | Alert band 2 / 5   | Description pending editorial review; the signal is live.                               |
        | **Pending Payouts**              | Merchant rule      | Captured value not yet paid out to the merchant bank.                                   |
        | **Success Rate**                 | Alert band 95 / 90 | Paid / total attempts. The headline payments-health number.                             |
        | **Top Payment Methods**          | Merchant rule      | iDEAL vs card vs Bancontact vs PayPal vs Klarna mix - watch for rail-specific breakage. |
        | **Total Transactions**           | Merchant rule      | Description pending editorial review; the signal is live.                               |
        | **Total Volume**                 | Merchant rule      | Gross payment value captured over the window.                                           |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                   |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------ |
        | **Captured vs Commerce Revenue** | Merchant rule      | Reconciliation gap between what Mollie captured and what the commerce sibling booked as revenue. |
        | **Volume Trend**                 | Alert band 0 / -15 | Captured volume over time - spot weekly cadence and dips.                                        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **1 write** operations across payments, payment refunds, chargebacks, methods, organizationmes, refunds on Mollie. 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=mollie)

    #### Ready to build your first Mollie 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | payments           | 2               | 0                |
      | payment refunds    | 1               | 1                |
      | chargebacks        | 1               | 0                |
      | methods            | 1               | 0                |
      | organizationmes    | 1               | 0                |
      | refunds            | 1               | 0                |
      | settlements        | 1               | 0                |
      | settlementpayments | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Monday.com on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/monday

Monitor Monday.com performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Monday.com performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=monday)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (20 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                       |
        | --------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**         | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                            |
        | **Avg Lead Time (days)**          | Merchant rule      | Description pending editorial review; the signal is live.                                                            |
        | **Avg Time-to-Fix (days)**        | Merchant rule      | Description pending editorial review; the signal is live.                                                            |
        | **Backlog by Priority**           | Merchant rule      | Backlog by Priority.                                                                                                 |
        | **Backlog by Status**             | Watch only         | Backlog by Status.                                                                                                   |
        | **Blocked Tickets**               | Alert band 3 / 8   | Items in Monday's Stuck-style labels - the operational queue's stuck list.                                           |
        | **Cycle Time by Priority**        | Merchant rule      | Cycle Time by Priority.                                                                                              |
        | **Finding Resolution Rate (90d)** | Alert band 75 / 50 | Share of audit findings actually closed on the Monday board. \<50% means we're filing faster than the team drains.   |
        | **In Progress**                   | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Oldest Open (days)**            | Merchant rule      | Description pending editorial review; the signal is live.                                                            |
        | **Open Tickets**                  | Merchant rule      | Items on the Findings board whose Status label is not in the closed set - top-of-funnel queue depth.                 |
        | **Scope Added Mid-Sprint**        | Merchant rule      | Description pending editorial review; the signal is live.                                                            |
        | **Sprint Velocity (avg)**         | Merchant rule      | Sprint Velocity (avg) over time.                                                                                     |
        | **Throughput Trend**              | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Tickets Resolved (7d)**         | Merchant rule      | Description pending editorial review; the signal is live.                                                            |
        | **Tickets by Assignee**           | Merchant rule      | Tickets by Assignee.                                                                                                 |
        | **Unassigned Tickets**            | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                            |
        | **VortexIQ Findings In Progress** | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **VortexIQ Findings Open**        | Merchant rule      | Items we filed from audit findings whose Status label is not in the closed set - the live backlog VortexIQ surfaced. |
        | **VortexIQ Findings Resolved**    | Watch only         | Description pending editorial review; the signal is live.                                                            |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Items sat on the board with no updated\_at change for two weeks - Monday's visual board hides these; this card surfaces them. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                              | Alert behaviour  | What it tracks                                                                                                                   |
        | ----------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1 | People with >10 open items - capacity bottleneck candidates; on Monday teams the queue often clusters on the marketing-ops lead. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour    | What it tracks                                                                         |
        | ------------------- | ------------------ | -------------------------------------------------------------------------------------- |
        | **Sprint Progress** | Alert band 80 / 50 | Monday has no built-in cycle; this reads a configured weekly-batch group on the board. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **8 write** operations across boards, changecolumnvalues, createitems, createupdates, itempages, mes on Monday.com. 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=monday)

    #### Ready to build your first Monday.com 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | boards             | 0               | 1                |
      | changecolumnvalues | 0               | 1                |
      | createitems        | 0               | 1                |
      | createupdates      | 0               | 1                |
      | itempages          | 0               | 1                |
      | mes                | 0               | 1                |
      | resources          | 0               | 1                |
      | users              | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# MongoDB on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mongodb

Monitor MongoDB health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor MongoDB health, cost and reliability signals, and catch incidents and runaway spend early.

[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=mongodb)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                             |
        | ------------------------------------------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------- |
        | **Active Readers**                                     | Watch only         | globalLock.activeClients.readers.                                                                          |
        | **Chunks Pending Migration**                           | Merchant rule      | Sharded clusters only , pending chunk migrations from balancer. Large pending = balancer overloaded.       |
        | **Connection Pool Saturation %**                       | Alert band 70 / 90 | connections.current / (connections.current + connections.available).                                       |
        | **Connection Pool at >90% Saturation**                 | Alert band 70 / 90 | Alerts for Connection Pool at >90% Saturation.                                                             |
        | **Connections In Use**                                 | Watch only         | Description pending editorial review; the signal is live.                                                  |
        | **Database Disk Usage %**                              | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                  |
        | **Elections (24h)**                                    | Merchant rule      | MongoDB-distinctive , frequent elections = primary flapping = network or hardware instability.             |
        | **Instance Uptime**                                    | Watch only         | Description pending editorial review; the signal is live.                                                  |
        | **Last Successful Backup (hours ago)**                 | Alert band 24 / 72 | Last mongodump / Atlas continuous backup / snapshot. Atlas: Cloud backups dashboard.                       |
        | **Memory Resident (MB)**                               | Watch only         | mem.resident from serverStatus.                                                                            |
        | **MongoDB Health Score**                               | Merchant rule      | Description pending editorial review; the signal is live.                                                  |
        | **Operations per Second (live)**                       | Watch only         | opcounters delta from serverStatus (query + insert + update + delete + getmore + command).                 |
        | **Replica Lag (seconds)**                              | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                  |
        | **Replica Set Member Lag >10s or in RECOVERING State** | Alert band 0 / 1   | Alerts for Replica Set Member Lag >10s or in RECOVERING State.                                             |
        | **Replica Set Members (state)**                        | Watch only         | From rs.status().members , name + stateStr (PRIMARY / SECONDARY / RECOVERING / etc).                       |
        | **Shard Balance Skew %**                               | Merchant rule      | (max chunks per shard - min chunks per shard) / total chunks. >20% = hot shard.                            |
        | **WiredTiger Cache Hit Rate %**                        | Alert band 95 / 80 | 1 - (cache.bytes-read-into-cache / cache.bytes-currently-in-the-cache). MongoDB-distinctive cache surface. |
      </Accordion>

      <Accordion title="Customer experience (7 signals)">
        | Signal                        | Alert behaviour      | What it tracks                                                                                                                                     |
        | ----------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **COLLSCAN Operations (24h)** | Merchant rule        | MongoDB-distinctive , full collection scans indicate missing indexes. Spike = recent code path bypassing index.                                    |
        | **Query Latency p50 (ms)**    | Watch only           | Description pending editorial review; the signal is live.                                                                                          |
        | **Query Latency p95 (ms)**    | Alert band 50 / 200  | latencies.reads.latency / latencies.reads.ops from serverStatus.                                                                                   |
        | **Query Latency p99 (ms)**    | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                          |
        | **Slow Ops (15m, >100ms)**    | Alert band 2 / 10    | Profiler entries with millis > slowms threshold (default 100ms).                                                                                   |
        | **Slow-Query Rate %**         | Alert band 1 / 5     | Slow-op count (system.profile, millis > slowms) in the trailing 15m divided by an estimated op count for that same window (serverStatus.opcounters |
        | **Top 10 Slow Operations**    | Watch only           | Top 10 Slow Operations, broken down by row.                                                                                                        |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                       |
        | -------------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------- |
        | **MongoDB OPS Spike vs Ecom Order Rate**           | Merchant rule      | Description pending editorial review; the signal is live.                                            |
        | **MongoDB Pool Saturation vs Traffic Burst**       | Alert band 70 / 90 | MongoDB Pool Saturation vs Traffic Burst, broken down by row.                                        |
        | **MongoDB Product Doc Count vs Ecom Catalog Size** | Merchant rule      | MongoDB-distinctive XC , many merchants store full product catalog in MongoDB; drift = sync failure. |
        | **Slow Ops During Checkout Window (5m)**           | Merchant rule      | Slow Ops During Checkout Window (5m), broken down by row.                                            |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                               |
        | -------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------- |
        | **Connection Errors (24h)**            | Merchant rule      | Description pending editorial review; the signal is live.                                    |
        | **Query Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live.                                    |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                               |
        | **WiredTiger Dirty Cache %**           | Merchant rule      | cache.tracked dirty bytes / cache.maximum bytes configured. >20% triggers eviction pressure. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across dbcurrentop()s, dbserverstatus()s, dbstats()s, dbsystemprofilefind()s, rstatus()s, shstatus()s on MongoDB. 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=mongodb)

    #### Ready to build your first MongoDB 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | dbcurrentop()s         | 1               | 0                |
      | dbserverstatus()s      | 1               | 0                |
      | dbstats()s             | 1               | 0                |
      | dbsystemprofilefind()s | 1               | 0                |
      | rstatus()s             | 1               | 0                |
      | shstatus()s            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Microsoft SQL Server on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mssql

Monitor Microsoft SQL Server health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Microsoft SQL Server health, cost and reliability signals, and catch incidents and runaway spend early.

[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=mssql)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                                       | Alert behaviour    | What it tracks                                                                                                                                    |
        | -------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AG Replica Health (state)**                | Watch only         | Always On AG only - synchronization\_health\_desc + synchronization\_state\_desc per replica from sys.dm\_hadr\_database\_replica\_states.        |
        | **AG Secondary NOT SYNCHRONIZED / Lag >10s** | Alert band 1 / 10  | Always On AG only - gated when no AG is configured.                                                                                               |
        | **Active Sessions**                          | Watch only         | COUNT of sys.dm\_exec\_sessions where status != 'sleeping'.                                                                                       |
        | **Blocked Sessions**                         | Merchant rule      | sys.dm\_exec\_requests where blocking\_session\_id != 0. Long blocking chains stall the app.                                                      |
        | **Blocking Chain >30s**                      | Merchant rule      | Alerts for Blocking Chain >30s.                                                                                                                   |
        | **Connection Saturation %**                  | Alert band 70 / 90 | Active sessions / @@MAX\_CONNECTIONS (or Azure SQL workload-group cap). >90% = login timeouts imminent.                                           |
        | **Database Disk Usage %**                    | Alert band 70 / 90 | Data + log file used vs allocated from sys.dm\_db\_file\_space\_usage / sys.master\_files. Azure SQL: sys.dm\_db\_resource\_stats.                |
        | **Instance Uptime**                          | Watch only         | GETDATE() - sqlserver\_start\_time from sys.dm\_os\_sys\_info.                                                                                    |
        | **Last Log Backup (minutes ago)**            | Merchant rule      | FULL/BULK\_LOGGED recovery DBs only - gap in log backups grows the transaction log and shrinks the recovery window (RPO).                         |
        | **Last Successful Backup (hours ago)**       | Alert band 24 / 72 | MAX(backup\_finish\_date) from msdb.dbo.backupset per database. Azure SQL backups are automatic (PITR) - use sys.dm\_db\_log\_stats / Azure REST. |
        | **Page Life Expectancy (sec)**               | Merchant rule      | SQL Server-distinctive - Page life expectancy counter. Sharp drop = memory pressure flushing the buffer pool.                                     |
        | **SQL Server Health Score**                  | Merchant rule      | Composite of wait-stats, blocking, AG health, backup recency. \<70 = investigate.                                                                 |
        | **TempDB Space Used %**                      | Merchant rule      | SQL Server-distinctive - sys.dm\_db\_file\_space\_usage on tempdb. Full tempdb stalls every sort/hash/version-store op server-wide.               |
      </Accordion>

      <Accordion title="Customer experience (10 signals)">
        | Signal                                  | Alert behaviour     | What it tracks                                                                                                                                |
        | --------------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Query Duration (ms)**             | Alert band 50 / 200 | total\_elapsed\_time / execution\_count across sys.dm\_exec\_query\_stats. p95/p99 not natively percentile - derived from per-query averages. |
        | **Batch Requests / Second (live)**      | Watch only          | Batch Requests/sec delta from sys.dm\_os\_performance\_counters - primary throughput signal.                                                  |
        | **Buffer Cache Hit Ratio %**            | Alert band 95 / 80  | Buffer cache hit ratio from sys.dm\_os\_performance\_counters. Low = data being read from disk not memory.                                    |
        | **Deadlocks (last 5m)**                 | Alert band 0 / 5    | Number of Deadlocks/sec counter delta (sys.dm\_os\_performance\_counters) - corroborated by system\_health XEvent ring buffer.                |
        | **Lock Waits / Second**                 | Merchant rule       | Lock Waits/sec from sys.dm\_os\_performance\_counters. Climbing = contention building before deadlocks appear.                                |
        | **Missing-Index Recommendations**       | Merchant rule       | SQL Server-distinctive - sys.dm\_db\_missing\_index\_details + group\_stats. High avg\_user\_impact rows = index candidates.                  |
        | **Query Error Rate %**                  | Alert band 0.1 / 1  | Errors/sec counter (sys.dm\_os\_performance\_counters) over batch requests. Spikes flag failing queries / app retry storms.                   |
        | **Slow-Query Rate %**                   | Alert band 1 / 5    | Share of executions over the slow threshold (default 200ms) from sys.dm\_exec\_query\_stats deltas.                                           |
        | **Top 10 Slowest Queries**              | Watch only          | Ordered by total\_worker\_time / total\_logical\_reads from sys.dm\_exec\_query\_stats + sql\_text.                                           |
        | **Top Wait Types (signal vs resource)** | Watch only          | SQL Server-distinctive - sys.dm\_os\_wait\_stats grouped by wait\_type. CXPACKET / PAGEIOLATCH / LCK\_M\_\* climbing = bottleneck.            |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                               | Alert behaviour    | What it tracks                                                                                                                                          |
        | ---------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AG Redo Queue (KB)**                               | Merchant rule      | Always On AG only - redo\_queue\_size from sys.dm\_hadr\_database\_replica\_states. Large backlog = secondary falling behind / failover-readiness risk. |
        | **Blocking / Slow Queries During Checkout Window**   | Merchant rule      | Blocking / Slow Queries During Checkout Window, broken down by row.                                                                                     |
        | **Failed Logins (24h)**                              | Merchant rule      | Logins Failed/sec counter or error log scrape (msg 18456). Bursts = brute force or stale app credentials.                                               |
        | **SQL Connection Saturation vs Traffic Burst**       | Alert band 70 / 90 | SQL Connection Saturation vs Traffic Burst, broken down by row.                                                                                         |
        | **SQL Load Spike vs Ecom Order Rate**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                               |
        | **SQL Product Table Row Count vs Ecom Catalog Size** | Merchant rule      | SQL Server-distinctive XC - many merchants keep their product master in SQL Server; row-count drift vs ecom = sync failure.                             |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                                  |
        | -------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AG Secondary Lag (seconds)**         | Alert band 1 / 10  | Always On AG only - estimated from redo\_queue\_size / redo\_rate or last\_commit\_time delta in sys.dm\_hadr\_database\_replica\_states. Gated when no AG is c |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                                                                                                  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **12 read** and **0 write** operations across msdbdbobackupsets, sydmdbfilespaceusages, sydmdbmissingindexdetails, sydmdbresourcestats, sydmexecconnections, sydmexecquerystats on Microsoft SQL Server. 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=mssql)

    #### Ready to build your first Microsoft SQL Server 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | msdbdbobackupsets         | 1               | 0                |
      | sydmdbfilespaceusages     | 1               | 0                |
      | sydmdbmissingindexdetails | 1               | 0                |
      | sydmdbresourcestats       | 1               | 0                |
      | sydmexecconnections       | 1               | 0                |
      | sydmexecquerystats        | 1               | 0                |
      | sydmexecrequests          | 1               | 0                |
      | sydmexecsessions          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# MySQL on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/mysql

Monitor MySQL health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor MySQL health, cost and reliability signals, and catch incidents and runaway spend early.

[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=mysql)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                                                   | Alert behaviour    | What it tracks                                                                                                                 |
        | -------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Replicas**                                      | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Binlog Backlog (MB) on Primary**                       | Merchant rule      | Sum of binlog file sizes ahead of replica position. Growing backlog = replica falling behind.                                  |
        | **Connection Pool Saturation %**                         | Alert band 70 / 90 | Threads\_connected / max\_connections.                                                                                         |
        | **Connection Pool at >90% Saturation**                   | Alert band 0 / 1   | Alerts for Connection Pool at >90% Saturation.                                                                                 |
        | **Connections In Use**                                   | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Database Disk Usage %**                                | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                                                      |
        | **InnoDB Buffer Pool Hit Rate %**                        | Alert band 95 / 80 | 1 - (Innodb\_buffer\_pool\_reads / Innodb\_buffer\_pool\_read\_requests). MySQL-distinctive , drives every OLTP workload.      |
        | **InnoDB Dirty Pages %**                                 | Merchant rule      | Innodb\_buffer\_pool\_pages\_dirty / Innodb\_buffer\_pool\_pages\_total. High = checkpoint pressure, async write storms.       |
        | **InnoDB Free Pages**                                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                      |
        | **Instance Uptime**                                      | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Last Successful Backup (hours ago)**                   | Alert band 24 / 72 | Last successful mysqldump / Percona XtraBackup / RDS snapshot.                                                                 |
        | **Memory Usage %**                                       | Merchant rule      | Description pending editorial review; the signal is live.                                                                      |
        | **MySQL Health Score**                                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                      |
        | **Queries per Second (live)**                            | Watch only         | Questions\_per\_sec from SHOW GLOBAL STATUS, sampled every 5s.                                                                 |
        | **Replication Lag (Seconds\_Behind\_Source)**            | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                                      |
        | **Replication Thread Health (IO/SQL)**                   | Merchant rule      | Replica\_IO\_Running + Replica\_SQL\_Running must both be Yes. MySQL-distinctive , either thread stopped = replication broken. |
        | **Replication Threads Stopped or Lag Exceeds Threshold** | Alert band 0 / 1   | Alerts for Replication Threads Stopped or Lag Exceeds Threshold.                                                               |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                              | Alert behaviour      | What it tracks                                                 |
        | ----------------------------------- | -------------------- | -------------------------------------------------------------- |
        | **InnoDB Deadlocks (last 5m)**      | Alert band 0 / 5     | Innodb\_deadlocks delta from SHOW ENGINE INNODB STATUS.        |
        | **Query Latency p50 (ms)**          | Watch only           | Description pending editorial review; the signal is live.      |
        | **Query Latency p95 (ms)**          | Alert band 50 / 200  | Description pending editorial review; the signal is live.      |
        | **Query Latency p99 (ms)**          | Alert band 100 / 500 | Description pending editorial review; the signal is live.      |
        | **Slow-Query Rate %**               | Alert band 1 / 5     | Slow\_queries delta / Questions delta from SHOW GLOBAL STATUS. |
        | **Top 10 Slowest Queries (digest)** | Watch only           | Top 10 Slowest Queries (digest), broken down by row.           |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                           | Alert behaviour    | What it tracks                                                |
        | ------------------------------------------------ | ------------------ | ------------------------------------------------------------- |
        | **MySQL Inventory Rows vs Ecom Inventory Count** | Merchant rule      | Description pending editorial review; the signal is live.     |
        | **MySQL Pool Saturation vs Traffic Burst**       | Alert band 70 / 90 | MySQL Pool Saturation vs Traffic Burst, broken down by row.   |
        | **MySQL QPS Spike vs Ecom Order Rate**           | Merchant rule      | Description pending editorial review; the signal is live.     |
        | **Slow Queries During Checkout Window (5m)**     | Merchant rule      | Slow Queries During Checkout Window (5m), broken down by row. |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                               |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Aborted Connects (24h)**             | Merchant rule      | Aborted\_connects from SHOW GLOBAL STATUS. Spike = wrong creds, network issues, or max\_connect\_errors hit. |
        | **Connection Errors (24h)**            | Merchant rule      | Description pending editorial review; the signal is live.                                                    |
        | **Query Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live.                                                    |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                                               |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across performanceschemaeventstatementsummarybydigests, performanceschemaprocesslists, show engine innodb status, show global status, show replica status, show variables on MySQL. 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=mysql)

    #### Ready to build your first MySQL 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                        | Read operations | Write operations |
      | ----------------------------------------------- | --------------- | ---------------- |
      | performanceschemaeventstatementsummarybydigests | 1               | 0                |
      | performanceschemaprocesslists                   | 1               | 0                |
      | show engine innodb status                       | 1               | 0                |
      | show global status                              | 1               | 0                |
      | show replica status                             | 1               | 0                |
      | show variables                                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Neo4j on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/neo4j

Monitor Neo4j health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Neo4j health, cost and reliability signals, and catch incidents and runaway spend early.

[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=neo4j)

<CardGroup>
  <Card title="21">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (21)">
    ### Monitor performance

    21 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (9 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                          |
        | -------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Bolt Connections In Use**                        | Watch only         | Active connections from dbms.listConnections().                                                                                         |
        | **Cluster Member Not FOLLOWER/LEADER or Lag >10s** | Alert band 0 / 1   | Alerts for Cluster Member Not FOLLOWER/LEADER or Lag >10s.                                                                              |
        | **Cluster Members (role + state)**                 | Watch only         | From dbms.cluster.overview() - address, role (LEADER / FOLLOWER / READ\_REPLICA), databases hosted.                                     |
        | **Cluster Replication Lag (seconds)**              | Alert band 1 / 10  | Max last-applied-tx lag of any FOLLOWER vs LEADER (dbms.cluster.overview()). Enterprise cluster only.                                   |
        | **Database Status (ONLINE / OFFLINE)**             | Merchant rule      | currentStatus from SHOW DATABASES - surfaces STORE\_COPYING / OFFLINE / STARTING states.                                                |
        | **Long-Running Transaction Holding Locks (>60s)**  | Merchant rule      | Alerts for Long-Running Transaction Holding Locks (>60s).                                                                               |
        | **Page Cache Hit Ratio %**                         | Alert band 95 / 80 | Neo4j-distinctive - page-cache hits / (hits + faults) from db.stats / metrics. \<95% = store no longer fits in page cache, IO climbing. |
        | **Page Cache Hit Ratio Below 95%**                 | Alert band 0 / 1   | Alerts for Page Cache Hit Ratio Below 95%.                                                                                              |
        | **Queries per Second (live)**                      | Watch only         | Transaction-committed rate delta from db.stats / metrics - graph query throughput.                                                      |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                               | Alert behaviour     | What it tracks                                                                                                                                |
        | ------------------------------------ | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Long-Running Transactions (>30s)** | Merchant rule       | Neo4j-distinctive - open transactions from SHOW TRANSACTIONS with elapsedTime >30s hold locks + heap. Runaway Cypher / un-terminated session. |
        | **Query Latency p95 (ms)**           | Alert band 50 / 200 | p95 elapsedTime across transactions sampled from SHOW TRANSACTIONS over the window.                                                           |
        | **Top 10 Slow Transactions**         | Watch only          | From SHOW TRANSACTIONS ordered by elapsedTime - currentQuery, database, owner (hashed), elapsed.                                              |
        | **Transaction Rollback Rate %**      | Alert band 0.1 / 1  | Rolled-back / committed transactions from db.stats counters. Spike = deadlocks, constraint violations, or app retry storms.                   |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                       |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **Connection Pool Saturation %**         | Alert band 70 / 90 | Active bolt connections / configured bolt thread-pool max. Saturation = new sessions queue or time out.                              |
        | **Last Successful Snapshot (hours ago)** | Alert band 24 / 72 | Aura-managed only - newest snapshot from the Aura management API. Self-managed merchants run neo4j-admin backup out of band (gated). |
        | **Neo4j Health Score**                   | Merchant rule      | Composite: p95 latency healthy x error-free x cluster-healthy x page-cache-warm x pool-headroom.                                     |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                         | Alert behaviour | What it tracks                                                                                                                     |
        | ---------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
        | **JVM Heap Usage %**                           | Merchant rule   | JVM heap used / committed from dbms.queryJmx('java.lang:type=Memory'). Sustained >85% = GC pressure, OOM risk.                     |
        | **Neo4j Query Spike vs Ecom Order Rate**       | Merchant rule   | Recommendation graphs get hammered by scrapers - QPS up while orders flat = bot traffic on the recommendation endpoint.            |
        | **Slow Graph Ops During Checkout Window (5m)** | Merchant rule   | Graph powering on-site recommendations stalls → checkout pages slow → conversion drops. Surfaces graph latency as revenue at risk. |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                                                                                    |
        | -------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Leader Elections (24h)** | Merchant rule   | Neo4j-distinctive - repeated leader elections = primary flapping (network / GC pause / hardware). Requires storing the leader identity over time. |
        | **Store Size**             | Watch only      | Total store size in bytes. Trend matters more than absolute - sudden growth = bulk import or runaway write.                                       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **1 write** operations across dbquerys, dbstats, dbmclusteroverview()s, dbmlistconnections()s, dbmqueryjmxs, instances on Neo4j. 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=neo4j)

    #### Ready to build your first Neo4j 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.

    <Accordion title="Browse the operations you can build with">
      | Resource              | Read operations | Write operations |
      | --------------------- | --------------- | ---------------- |
      | dbquerys              | 0               | 1                |
      | dbstats               | 1               | 0                |
      | dbmclusteroverview()s | 1               | 0                |
      | dbmlistconnections()s | 1               | 0                |
      | dbmqueryjmxs          | 1               | 0                |
      | instances             | 1               | 0                |
      | show databases        | 1               | 0                |
      | show transactions     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# NetDispatch on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/net-dispatch

Monitor NetDispatch delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor NetDispatch delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=net-dispatch)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                                                                                                                      |
        | ------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live.                                                                                           |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                                                                                                                       |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Dispatch-to-Collection Lag**  | Merchant rule    | Hours from NetDispatch dispatch event to carrier-side collection scan. The core NetDispatch SLA - >24h lag means warehouse cutoff missed or carrier |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                           |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                                    |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **OTD by Route**                | Watch only       | OTD by Route.                                                                                                                                       |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.                                                                                                  |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live.                                                                                           |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live.                                                                                           |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                                                                                                               |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                            |
        | ------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live. |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live. |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live. |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                            |
        | ------------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Failed Deliveries**                | Merchant rule      | Description pending editorial review; the signal is live. |
        | **NetDispatch OTD by Sales Channel** | Alert band 95 / 90 | Per-channel NetDispatch OTD.                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **0 write** operations across tbds on NetDispatch. 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=net-dispatch)

    #### Ready to build your first NetDispatch 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 2               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# NetSuite ERP on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/netsuite

Monitor NetSuite ERP performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor NetSuite ERP performance signals, run automated checks, and prepare approved work through Vortex IQ.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/netsuite) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=netsuite)

<CardGroup>
  <Card title="27">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (27)">
    ### Monitor performance

    27 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (19 signals)">
        | Signal                                                  | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AP Aging - 60+ Days**                                 | Alert band 10 / 30 | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Aging - 60+ Days**                                 | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Aging Buckets**                                    | Watch only         | AR Aging Buckets, compared across items.                                                                                                               |
        | **AR Balance (live, by Subsidiary)**                    | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Accounting Period Close Past Deadline**               | Alert band 0 / 5   | Alerts for Accounting Period Close Past Deadline.                                                                                                      |
        | **Accounting Period Close Status**                      | Alert band 0 / 5   | Description pending editorial review; the signal is live.                                                                                              |
        | **Accrual Reversals (last close)**                      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Active Vendors**                                      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Customers on Credit Hold (onCreditHold=ON or AUTO)**  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Days Sales Outstanding (DSO)**                        | Alert band 30 / 60 | Description pending editorial review; the signal is live.                                                                                              |
        | **ERP-vs-Ecom Inventory Variance %**                    | Alert band 1 / 5   | Compares NetSuite location on-hand to a separate storefront's availability; dormant for NetSuite-as-store merchants (no external storefront to compare |
        | **Ecom Customers Absent from NetSuite**                 | Alert band 0 / 10  | Buyers on a separate storefront with no NetSuite customer record; dormant for NetSuite-as-store merchants.                                             |
        | **Inventory Item On-Hand Went Negative (any Location)** | Merchant rule      | Alerts for Inventory Item On-Hand Went Negative (any Location).                                                                                        |
        | **Items Below Reorder Point**                           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Manual Journal Entries as % of Total**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **New Customers (30d)**                                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Hand Inventory Value (by Location)**               | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Transactions by Type**                                | Watch only         | CashSale/CustInvc/VendBill/JournalEntry split. CashSale spike = ecom integration scaling; JE spike = manual override creep.                            |
        | **Vendor Payment On-Time Rate**                         | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                                        | Alert behaviour         | What it tracks                                                                                                                      |
        | ------------------------------------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
        | **AR Aging on Customers with Active Ecom Orders**             | Alert band 1000 / 10000 | Should auto-flag onCreditHold=ON via SuiteScript. Manual review needed when this fires.                                             |
        | **Ecom Customers Absent from NetSuite Customer Record**       | Alert band 0 / 10       | Ecom buyers without NetSuite Customer = Cash Sale / Invoice can't post under correct entity; revenue recognition rules don't apply. |
        | **Ecom Orders Missing Matching NetSuite Cash Sale / Invoice** | Merchant rule           | Ecom orders the merchant fulfilled but NetSuite never billed for. Common cause: SuiteScript order-import script failing silently.   |
        | **SKUs with NetSuite-vs-Ecom Inventory Drift >5%**            | Alert band 1 / 5        | Location-level NetSuite available vs ecom availability. Drives overselling on multi-channel SKUs.                                   |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                                    | Alert behaviour | What it tracks                                                                                                       |
        | ----------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **NetSuite Health Score**                 | Merchant rule   | Composite: integration-error-free x saved-search-fast x AR-aging-low x inventory-variance-low.                       |
        | **OneWorld Customers Missing Subsidiary** | Merchant rule   | OneWorld-account customer records without Subsidiary assignment break intercompany flows + revenue rule application. |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                                | Alert behaviour   | What it tracks                                                                                                               |
        | ----------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |
        | **Open Transactions (Pending Approval / Error)**      | Alert band 0 / 50 | Transactions in PENDING\_APPROVAL or REJECTED status. Spike = SuiteScript integration error or approval-routing rule broken. |
        | **Transactions Failing to Save (SuiteScript errors)** | Alert band 0 / 5  | SuiteScript record-save failures block transactions. P1 because they often happen silently inside background scripts.        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **2 write** operations across serviceauthoauth2tokens, servicequerysuiteqls, servicerecordaccounts, servicerecordcustomers, servicerecordinventoryitems, servicerecordtransactions on NetSuite ERP. 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=netsuite)

    #### Ready to build your first NetSuite ERP 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | serviceauthoauth2tokens     | 0               | 1                |
      | servicequerysuiteqls        | 0               | 1                |
      | servicerecordaccounts       | 1               | 0                |
      | servicerecordcustomers      | 1               | 0                |
      | servicerecordinventoryitems | 1               | 0                |
      | servicerecordtransactions   | 1               | 0                |
      | servicerecordvendors        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Newegg on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/newegg

Monitor Newegg listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Newegg listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=newegg)

<CardGroup>
  <Card title="39">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (39)">
    ### Monitor performance

    39 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                                               | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by State**                                     | Watch only         | AOV by State.                                                                                                                                          |
        | **Buyer Messages Unread**                            | Watch only         | Buyer Messages Unread as exposed by the Newegg Marketplace integration. The metric is computed from the latest available data and refreshed on the sta |
        | **DOA (Dead On Arrival) Claim Rate**                 | Alert band 5 / 15  | Tech category DOA rate , sustained >2% suggests QA issues or counterfeit inventory entering supply chain.                                              |
        | **Days Since Last Payout**                           | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments**                                   | Merchant rule      | Alerts for Late Shipments.                                                                                                                             |
        | **Listings Without Brand Authorisation**             | Alert band 5 / 50  | Brand authorisation required for listing protected-brand inventory. Missing = listings hidden from brand pages.                                        |
        | **MAP / Warranty-SLA / Egg-Badge Threshold Crossed** | Merchant rule      | Alerts for MAP / Warranty-SLA / Egg-Badge Threshold Crossed.                                                                                           |
        | **Marketplace Fees Paid**                            | Watch only         | Marketplace Fees Paid as exposed by the Newegg Marketplace integration. The metric is computed from the latest available data and refreshed on the sta |
        | **Newegg Seller Health Score**                       | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Time Shipping Rate**                            | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Warranty Claims (overdue)**                   | Merchant rule      | Newegg's warranty SLA varies by claim type (DOA = faster). Overdue claims drop Egg badges and brand-page placement.                                    |
        | **Orders / Day**                                     | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by State**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                                  | Watch only         | Pending Payouts as exposed by the Newegg Marketplace integration. The metric is computed from the latest available data and refreshed on the standard  |
        | **Pending Shipment**                                 | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Seller Rating**                                    | Alert band 95 / 85 | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Transactions**                               | Watch only         | Total Transactions as exposed by the Newegg Marketplace integration. The metric is computed from the latest available data and refreshed on the standa |
      </Accordion>

      <Accordion title="Grow revenue (11 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                           |
        | ----------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**             | Alert band 0 / -5  | Tech AOV typically high (\$100-1000+) , sustained drops suggest mix shift toward low-margin accessories.                                 |
        | **B2B (Bizmember) Revenue Share**   | Watch only         | Newegg bizmember revenue split , B2B buyers convert at higher AOV + lower return rate. Track growth lever.                               |
        | **B2B-Eligible Listings Coverage**  | Merchant rule      | B2B-relevant SKUs (servers, networking, bulk) without B2B-eligible flag are invisible to Newegg's bizmember filter , missed B2B revenue. |
        | **Egg Badge Status**                | Merchant rule      | Newegg's seller-quality badge (Gold / Silver / Bronze). Drives brand-page placement + bizmember-tier visibility.                         |
        | **Net Revenue (after Newegg fees)** | Alert band 0 / -5  | Net of Newegg's commission (10-15% for tech / electronics) + Newegg Logistics fees if opted-in.                                          |
        | **Newegg Fee % of Revenue**         | Alert band 12 / 18 | 10-15% by category for tech / electronics. Higher with Newegg Logistics fulfilment.                                                      |
        | **Orders**                          | Watch only         | Description pending editorial review; the signal is live.                                                                                |
        | **Required-Attribute Completeness** | Alert band 90 / 70 | Tech category attributes are strict (chipset, socket, form factor, etc.) , missing = lost search filter visibility.                      |
        | **Revenue Over Time**               | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                |
        | **Top Listings by Revenue**         | Watch only         | Top Listings by Revenue.                                                                                                                 |
        | **Total Revenue**                   | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                |
      </Accordion>

      <Accordion title="Catalogue quality (6 signals)">
        | Signal                                           | Alert behaviour   | What it tracks                                                                                                                                         |
        | ------------------------------------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings**                              | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Listings Expiring Soon**                       | Watch only        | Listings Expiring Soon as exposed by the Newegg Marketplace integration. The metric is computed from the latest available data and refreshed on the st |
        | **MAP Violations (Selling Below Brand MAP)**     | Merchant rule     | Newegg flags listings selling below brand-set Minimum Advertised Price. Major brands (Intel, NVIDIA, ASUS) enforce strictly via takedown notices.      |
        | **Newegg Rejected / MAP-Flagged Listings (24h)** | Alert band 5 / 50 | Alerts for Newegg Rejected / MAP-Flagged Listings (24h).                                                                                               |
        | **Rejected Listings**                            | Alert band 5 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Listings**                               | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                        | Alert behaviour   | What it tracks                                                                                          |
        | --------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------- |
        | **Active Newegg Listings for OOS SKUs on BC** | Alert band 0 / 5  | Description pending editorial review; the signal is live.                                               |
        | **Listings Drifting from BC**                 | Alert band 5 / 50 | Listings Drifting from BC, broken down by row.                                                          |
        | **Listings Failing Feedonomics Validation**   | Alert band 2 / 5  | Description pending editorial review; the signal is live.                                               |
        | **MAP Parity vs Amazon / Walmart**            | Merchant rule     | Brands enforce MAP across all retail channels , if any marketplace violates, all sellers risk takedown. |
        | **Revenue at Risk**                           | Merchant rule     | Description pending editorial review; the signal is live.                                               |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listing buy-box win rate below 30% (Amazon-specific; non-applicable elsewhere)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Losing the Buy Box means losing the sale even when the listing wins the search; price, delivery promise and account health drive the algorithm.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-002`
      </Accordion>

      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across marketplacefeedinventorys, marketplaceorders, marketplaceselleraccounts, marketplaceselleritemmgmts, marketplacewarrantyclaims on Newegg. 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=newegg)

    #### Ready to build your first Newegg 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | marketplacefeedinventorys  | 0               | 1                |
      | marketplaceorders          | 1               | 0                |
      | marketplaceselleraccounts  | 1               | 0                |
      | marketplaceselleritemmgmts | 1               | 0                |
      | marketplacewarrantyclaims  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# New Relic on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/newrelic

Monitor New Relic health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor New Relic health, cost and reliability signals, and catch incidents and runaway spend early.

[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=newrelic)

<CardGroup>
  <Card title="16">
    performance signals
  </Card>

  <Card title="14">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="1">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (16)">
    ### Monitor performance

    16 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (9 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                    |
        | ----------------------- | --------------- | ----------------------------------------------------------------- |
        | **Apdex Score**         | Watch only      | Application performance index score (0-1). Closer to 1 is better. |
        | **Apdex Trend**         | Watch only      | Apdex score trend over the selected period.                       |
        | **Avg AJAX Response**   | Watch only      | Average AJAX request response time in milliseconds.               |
        | **Avg DOM Processing**  | Watch only      | Average DOM processing duration in milliseconds.                  |
        | **Avg Page Load Time**  | Watch only      | Average browser page load time in milliseconds.                   |
        | **Error Rate Trend**    | Watch only      | Error rate trend over the selected period.                        |
        | **JS Error Count**      | Watch only      | Total number of JavaScript errors captured by the browser agent.  |
        | **Response Time Trend** | Watch only      | Response time trend over the selected period.                     |
        | **Throughput Trend**    | Watch only      | Throughput trend over the selected period.                        |
      </Accordion>

      <Accordion title="Control risk and change (6 signals)">
        | Signal                   | Alert behaviour | What it tracks                                      |
        | ------------------------ | --------------- | --------------------------------------------------- |
        | **Avg Response Time**    | Watch only      | Average transaction response time in milliseconds.  |
        | **Error Rate**           | Watch only      | Percentage of transactions resulting in an error.   |
        | **HTTP Status Codes**    | Watch only      | Distribution of HTTP response status codes.         |
        | **Slowest Transactions** | Watch only      | Slowest transactions ranked by average duration.    |
        | **Top Error Classes**    | Watch only      | Most frequent error classes in the selected period. |
        | **Total Errors**         | Watch only      | Total number of transaction errors.                 |
      </Accordion>

      <Accordion title="Run operations (1 signals)">
        | Signal         | Alert behaviour | What it tracks                                            |
        | -------------- | --------------- | --------------------------------------------------------- |
        | **Throughput** | Watch only      | Average requests per minute processed by the application. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (14)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Slow AJAX Requests">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Slow AJAX calls make an otherwise-loaded page feel broken, spinners where content should be; the offending endpoints are listed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR07`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>

      <Accordion title="Top Error Classes">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        The top error classes account for most failures; fixing the first few usually collapses the whole error rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR08`
      </Accordion>

      <Accordion title="HTTP 5xx Errors">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Report only

        HTTP 5xx responses are the server refusing service; even a low rate means some customers hit a dead end at full price.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR09`
      </Accordion>

      <Accordion title="High Error Rate">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Report only

        An elevated error rate means requests are failing for real users right now; the error classes behind it name the code paths to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR02`
      </Accordion>

      <Accordion title="High JavaScript Error Count">
        **Severity** low · **Outcome** Customer experience · **Fix status** Report only

        JavaScript errors break interactions silently: buttons that do nothing, forms that never submit. Each error class comes with the page and stack to fix it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR06`
      </Accordion>

      <Accordion title="Low Apdex Score">
        **Severity** low · **Outcome** Customer experience · **Fix status** Report only

        A falling Apdex means real users find the application slower than the tolerable threshold; it is the single-number summary of experienced performance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR01`
      </Accordion>

      <Accordion title="Slow Page Load">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Slow page loads cost conversions directly; browser-side timing shows what users actually experienced rather than what the server sent.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR05`
      </Accordion>

      <Accordion title="Slow Response Time">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Report only

        Slow server responses cap how fast any page can feel, no matter how optimised the frontend is; the slowest transactions name the culprits.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR03`
      </Accordion>

      <Accordion title="Slow Transactions">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Report only

        Slow server responses cap how fast any page can feel, no matter how optimised the frontend is; the slowest transactions name the culprits.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR10`
      </Accordion>

      <Accordion title="Throughput">
        **Severity** info · **Outcome** Control risk and change · **Fix status** Report only

        Informational: the technologies detected on the storefront, used to tailor the other checks to the actual stack.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `NR04`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **1 write** operations across graphqls on New Relic. 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=newrelic)

    #### Ready to build your first New Relic 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | graphqls | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Nimble on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/nimble

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)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | 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.                                                                                       |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | 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.                 |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | 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.                                                                   |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                            |
        | --------------------- | --------------- | --------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### 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.

    <Accordion title="Browse the operations you can build with">
      | 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.
    </Accordion>
  </Tab>
</Tabs>


# Notion on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/notion

Monitor Notion publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Notion publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=notion)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                 |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                      |
        | **Avg Lead Time (days)**            | Merchant rule      | Description pending editorial review; the signal is live.                                                                      |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                      |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                           |
        | **Backlog by Status**               | Watch only         | Backlog by Status.                                                                                                             |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Rows flagged blocked / impeded in the Status property - the stuck list.                                                        |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                        |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings actually got fixed via the Notion pipeline. \<50% means we're filing faster than the team drains. |
        | **In Progress**                     | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Description pending editorial review; the signal is live.                                                                      |
        | **Open Tickets**                    | Merchant rule      | Notion rows whose Status is not in the done set - top-of-funnel backlog volume.                                                |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | People with >10 open rows - capacity bottleneck candidates.                                                                    |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                      |
        | **Sprint Progress**                 | Merchant rule      | Notion has no native sprint; progress is derived from a Sprint select property and row completion.                             |
        | **Sprint Velocity (avg)**           | Merchant rule      | Sprint Velocity (avg) over time.                                                                                               |
        | **Throughput Trend**                | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Tickets Resolved (7d)**           | Alert band 0 / -25 | Description pending editorial review; the signal is live.                                                                      |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                           |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                      |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **VortexIQ Findings Open**          | Merchant rule      | Notion rows we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced.        |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                      |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                          |
        | ----------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the database with no edit for two weeks - these are the ones losing money silently. Notion exposes last\_edited\_time on every page for |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **4 write** operations across pages, comments, databas, databasquerys, users, usermes on Notion. 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=notion)

    #### Ready to build your first Notion 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | pages         | 1               | 2                |
      | comments      | 1               | 1                |
      | databas       | 1               | 0                |
      | databasquerys | 0               | 1                |
      | users         | 1               | 0                |
      | usermes       | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Odoo on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/odoo

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Odoo.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Odoo.

[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=odoo)

<CardGroup>
  <Card title="34">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (34)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Protect revenue (13 signals)">
        | Signal                                           | Alert behaviour   | What it tracks                                                                                                    |
        | ------------------------------------------------ | ----------------- | ----------------------------------------------------------------------------------------------------------------- |
        | **Active Ad Spend on Out-of-Stock Products**     | Alert band 1 / 5  | Pause immediately - spend on products Odoo says can't ship. Single-DB stock makes this exact.                     |
        | **At-Risk (Churn) Customers**                    | Merchant rule     | Customers whose last sale.order is older than their typical cadence - win-back targets.                           |
        | **Confirmed Orders Missing Posted Invoice**      | Merchant rule     | Revenue recognised in commerce but never invoiced in the books - VAT/tax base + cash-flow understated.            |
        | **Draft vs Confirmed Order Mix**                 | Watch only        | sale.order state split (draft/sent vs sale/done). High draft share = abandoned quotes or stuck checkout.          |
        | **Email Share of Confirmed Revenue**             | Merchant rule     | How much realised Odoo revenue email drives - falling share = lifecycle programme decay.                          |
        | **Low-Stock Products**                           | Merchant rule     | Products with available\_quantity below the configured reorder point - restock before stockout.                   |
        | **Marketplace / Ecom Price-Title Drift vs Odoo** | Merchant rule     | Catalogue divergence between Odoo (source of record) and external channels - pricing leaks + brand inconsistency. |
        | **Order Cancellation Rate**                      | Merchant rule     | sale.order state=cancel / total. Spikes flag payment, stock, or fraud-hold problems.                              |
        | **Out-of-Stock Products**                        | Merchant rule     | Published products with available\_quantity \<= 0 in stock.quant. Lost-sale exposure on the storefront.           |
        | **Products Missing Image**                       | Merchant rule     | Published product.product rows with no image\_1920 - conversion + SEO leak on the storefront.                     |
        | **Products with Negative On-Hand**               | Merchant rule     | stock.quant rows with quantity \< 0 - oversell or stock-move integrity failure that becomes a refund.             |
        | **Refund / Credit Note Rate**                    | Merchant rule     | account.move out\_refund value / out\_invoice value. Rising = returns or fulfilment quality problem.              |
        | **Repeat Ecom Customers Absent from Odoo**       | Alert band 0 / 10 | Sync gap - repeat buyers invisible to Odoo CRM/invoicing means broken tax lines + missed win-back.                |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                              | Alert behaviour   | What it tracks                                                                                                     |
        | ----------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------ |
        | **New vs Repeat Customers**         | Watch only        | res.partner customer\_rank + sale.order history split. Repeat share is the retention pulse.                        |
        | **Orders Stuck in Draft**           | Merchant rule     | Confirmed-intent orders that never progressed past draft/sent - payment or stock hold blocking revenue.            |
        | **Revenue Trend**                   | Alert band 0 / -5 | Daily confirmed-revenue series over 90 days from date\_order.                                                      |
        | **Revenue by Company**              | Watch only        | Confirmed revenue split by company\_id for groups running several legal entities in one Odoo DB.                   |
        | **Revenue by Currency**             | Watch only        | Confirmed revenue split by currency\_id for multi-currency groups.                                                 |
        | **Revenue by Payment Method**       | Watch only        | Paid invoice value grouped by payment journal/method. Enterprise Accounting.                                       |
        | **Sale Order Count**                | Watch only        | Count of confirmed sale.order rows in window. Pairs with revenue + AOV for the exec pulse.                         |
        | **Top Customers by Lifetime Spend** | Watch only        | res.partner ranked by summed confirmed sale.order amount\_total.                                                   |
        | **Total Revenue (confirmed)**       | Alert band 0 / -5 | Sum of amount\_total on sale.order where state in (sale,done). Default-renders today; toggles 7/30/90-day windows. |
      </Accordion>

      <Accordion title="Run operations (5 signals)">
        | Signal                                  | Alert behaviour   | What it tracks                                                                                       |
        | --------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------- |
        | **Average Order Value**                 | Alert band 0 / -5 | amount\_total summed / confirmed order count over the window.                                        |
        | **Customer Invoice Past Due**           | Alert band 5 / 15 | account.move customer invoices over their invoice\_date\_due and still owing - collections worklist. |
        | **Inventory Went Negative**             | Merchant rule     | Live oversell signal - surfaces the product + location the instant on-hand crosses below zero.       |
        | **Products Missing Internal Reference** | Merchant rule     | product.product with empty default\_code (SKU) - breaks every cross-channel SKU join and stock sync. |
        | **Slow-Moving Inventory Value (>90d)**  | Merchant rule     | On-hand value of products with no stock-move (sale) in 90 days - tied-up working capital.            |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                               | Alert behaviour         | What it tracks                                                                                                                                          |
        | ------------------------------------ | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Invoiced vs Paid**                 | Watch only              | account.move out\_invoice posted total vs payment\_state=paid total. Widening gap = collections lag. Enterprise Accounting.                             |
        | **Overdue Receivables**              | Alert band 1000 / 10000 | Sum of amount\_residual on posted out\_invoice where invoice\_date\_due \< today and not paid.                                                          |
        | **Period Close Overdue**             | Alert band 0 / 5        | res.company.fiscalyear\_lock\_date vs the oldest calendar month it hasn't yet covered - days the books have gone unclosed past that month's end.        |
        | **Unbalanced Draft Journal Entries** | Alert band 0 / 5        | account.move.line debit/credit summed per DRAFT account.move (move\_type=entry) - Odoo only enforces debit==credit at posting, so an unbalanced draft c |
        | **Unposted Journal Entries**         | Alert band 0 / 50       | Distinct DRAFT account.move (move\_type=entry) journal entries - Odoo validates debit==credit only at post time, so entries can sit unposted (and unnot |
      </Accordion>

      <Accordion title="Catalogue quality (2 signals)">
        | Signal                           | Alert behaviour | What it tracks                                                                                     |
        | -------------------------------- | --------------- | -------------------------------------------------------------------------------------------------- |
        | **Products Missing Description** | Merchant rule   | Published products with empty description\_sale - thin content, weak organic ranking.              |
        | **Products Missing Price**       | Merchant rule   | Published products with list\_price = 0 or null - unsellable or mis-priced rows on the storefront. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **3 write** operations across jsonrpcs, xmlrpccommons, xmlrpcobjects on Odoo. 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=odoo)

    #### Ready to build your first Odoo 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | jsonrpcs      | 0               | 1                |
      | xmlrpccommons | 0               | 1                |
      | xmlrpcobjects | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# OnBuy on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/onbuy

Monitor OnBuy listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor OnBuy listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=onbuy)

<CardGroup>
  <Card title="46">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (46)">
    ### Monitor performance

    46 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by UK Region**           | Watch only         | AOV by UK Region.                                                                                                                                      |
        | **Avg Discount vs RRP**        | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Time to Dispatch (hrs)** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Courier Mix**                | Watch only         | Courier Mix, shown by share.                                                                                                                           |
        | **Dispatch SLA Compliance**    | Merchant rule      | % of orders dispatched before dispatch\_due\_by. OnBuy penalises stale account standing.                                                               |
        | **Dispatch Time by Region**    | Merchant rule      | Dispatch Time by Region.                                                                                                                               |
        | **Late Dispatch Count (30d)**  | Merchant rule      | Orders dispatched after dispatch\_due\_by - hits seller rating.                                                                                        |
        | **Late Dispatch Queue**        | Merchant rule      | Alerts for Late Dispatch Queue.                                                                                                                        |
        | **Marketplace Fees Paid**      | Watch only         | Marketplace Fees Paid as exposed by the OnBuy integration. The metric is computed from the latest available data and refreshed on the standard data re |
        | **OnBuy Health Score**         | Alert band 95 / 85 | Composite - listing-active-pct x order-fulfil-rate x SLA-compliance x inverse stale-listings.                                                          |
        | **Orders by Status**           | Merchant rule      | Orders by Status.                                                                                                                                      |
        | **Orders by UK Region**        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Dispatch**           | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Price Distribution**         | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Zero-Stock Active Listings** | Alert band 0 / 5   | Active listings with stock\_level=0 - show on browse but can't fulfil.                                                                                 |
      </Accordion>

      <Accordion title="Catalogue quality (11 signals)">
        | Signal                              | Alert behaviour   | What it tracks                                                           |
        | ----------------------------------- | ----------------- | ------------------------------------------------------------------------ |
        | **Active Listings**                 | Merchant rule     | Description pending editorial review; the signal is live.                |
        | **Category Coverage**               | Merchant rule     | % of relevant OnBuy categories the merchant has at least one listing in. |
        | **Inactive Listings**               | Alert band 5 / 50 | Description pending editorial review; the signal is live.                |
        | **Listings Discounted >20%**        | Watch only        | Description pending editorial review; the signal is live.                |
        | **Listings Missing RRP**            | Alert band 5 / 50 | Without RRP, OnBuy can't show 'Save X%' badges that drive click-through. |
        | **Listings Suspension Burst (24h)** | Alert band 5 / 50 | Alerts for Listings Suspension Burst (24h).                              |
        | **Listings by Age**                 | Watch only        | Description pending editorial review; the signal is live.                |
        | **Listings per Brand**              | Watch only        | Listings per Brand, compared across items.                               |
        | **Sales Velocity by Category**      | Watch only        | Sales Velocity by Category.                                              |
        | **Total Listings**                  | Watch only        | Description pending editorial review; the signal is live.                |
        | **Uncategorised Listings**          | Alert band 5 / 50 | Listings missing category\_id - invisible to category-based browse.      |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                         |
        | --------------------------------- | ------------------ | -------------------------------------------------------------------------------------- |
        | **Average Order Value**           | Alert band 0 / -5  | Description pending editorial review; the signal is live.                              |
        | **OnBuy Commission % of Revenue** | Alert band 12 / 18 | Per-category commission tracking - flags categories where OnBuy fees outpace margin.   |
        | **Orders**                        | Watch only         | Description pending editorial review; the signal is live.                              |
        | **Revenue Drop Alert**            | Alert band 0 / -5  | Alerts for Revenue Drop Alert.                                                         |
        | **Revenue Over Time**             | Alert band 0 / -5  | Description pending editorial review; the signal is live.                              |
        | **Suspended Listings**            | Alert band 5 / 50  | Listings OnBuy has hidden from search until issues are fixed - direct revenue blocker. |
        | **Top Brands by Revenue**         | Watch only         | Top Brands by Revenue.                                                                 |
        | **Top Categories by Revenue**     | Watch only         | Top Categories by Revenue.                                                             |
        | **Top Listings by Revenue**       | Watch only         | Top Listings by Revenue.                                                               |
        | **Total Revenue**                 | Alert band 0 / -5  | Description pending editorial review; the signal is live.                              |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                       | Alert behaviour   | What it tracks                                                                                            |
        | -------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------- |
        | **Amazon UK Top SKUs Missing on OnBuy**      | Merchant rule     | Velocity-proven SKUs that aren't even listed on OnBuy - the cheapest revenue lift available.              |
        | **Cancellation Rate**                        | Merchant rule     | Description pending editorial review; the signal is live.                                                 |
        | **Catalogue Drift vs Amazon UK**             | Alert band 5 / 50 | Same SKU listed at materially different prices on OnBuy vs Amazon UK - MAP/brand-consistency risk.        |
        | **Net Revenue (after commission + refunds)** | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                 |
        | **OnBuy Orders via ShipBob (SLA)**           | Merchant rule     | OnBuy SLA compliance specifically for orders fulfilled by ShipBob - isolates 3PL performance per channel. |
        | **OnBuy Share of UK Revenue**                | Watch only        | OnBuy Share of UK Revenue, shown by share.                                                                |
        | **OnBuy vs DTC Price Gap**                   | Merchant rule     | OnBuy vs DTC Price Gap, compared across items.                                                            |
        | **Revenue at Risk (live)**                   | Merchant rule     | Sum of (suspended\_listings x velocity x ASP) + (mis-categorised listings x velocity loss) - recoverable. |
        | **Stale Listings (>180d no update)**         | Merchant rule     | Listings with no metadata refresh in 6 months - risk OnBuy de-prioritising in search.                     |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                                                            |
        | --------------------- | --------------- | --------------------------------------------------------------------------------------------------------- |
        | **Auth Token Health** | Merchant rule   | OnBuy tokens expire after 1h; if refresh fails the dashboard goes blind. Surface before merchants notice. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listing buy-box win rate below 30% (Amazon-specific; non-applicable elsewhere)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Losing the Buy Box means losing the sale even when the listing wins the search; price, delivery promise and account health drive the algorithm.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-002`
      </Accordion>

      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **1 write** operations across listings, orders, authrequesttokens, brands, categorys on OnBuy. 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=onbuy)

    #### Ready to build your first OnBuy 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | listings          | 2               | 0                |
      | orders            | 2               | 0                |
      | authrequesttokens | 0               | 1                |
      | brands            | 1               | 0                |
      | categorys         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# OpenAI on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/openai

Monitor OpenAI health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor OpenAI health, cost and reliability signals, and catch incidents and runaway spend early.

[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=openai)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="27">
    proven workflows
  </Card>

  <Card title="288">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Control risk and change (11 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                         |
        | ------------------------------------ | ------------------ | -------------------------------------------------------------------------------------- |
        | **API Requests (30d)**               | Alert band 0 / -50 | Sum of num\_model\_requests from /v1/organization/usage/completions over the last 30d. |
        | **Avg Tokens per Request (30d)**     | Watch only         | (input+output tokens) / num\_model\_requests.                                          |
        | **Cached Input Tokens (30d)**        | Watch only         | Sum of input\_cached\_tokens; prompt-cache effectiveness in absolute terms.            |
        | **Cost by Line Item (30d)**          | Watch only         | Costs grouped by line\_item (e.g. per-model input/output token charges).               |
        | **Input Tokens (30d)**               | Watch only         | Sum of input\_tokens over the last 30d.                                                |
        | **Models Available**                 | Watch only         | Count of models the key can see via /v1/models. Renders with any API key.              |
        | **OpenAI Spend (30d)**               | Alert band 10 / 50 | Sum of /v1/organization/costs daily amounts over the last 30d. Admin API key required. |
        | **Output : Input Token Ratio (30d)** | Watch only         | output\_tokens / input\_tokens; generation-heavy vs context-heavy workloads.           |
        | **Output Tokens (30d)**              | Watch only         | Sum of output\_tokens over the last 30d.                                               |
        | **Tokens by Model (30d)**            | Watch only         | input+output tokens grouped by model.                                                  |
        | **Total Tokens (30d)**               | Watch only         | input\_tokens + output\_tokens summed over the last 30d.                               |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                             |
        | ------------------------------ | ------------------ | ------------------------------------------------------------------------------------------ |
        | **Avg Cost per Request (30d)** | Watch only         | 30d spend / 30d num\_model\_requests.                                                      |
        | **Avg Daily Spend (30d)**      | Watch only         | 30d spend / days with any cost bucket.                                                     |
        | **Daily Requests Trend**       | Watch only         | Daily num\_model\_requests buckets over the last 30d.                                      |
        | **Daily Spend Trend**          | Watch only         | Daily cost buckets from /v1/organization/costs over the last 30d.                          |
        | **Requests by Model (30d)**    | Watch only         | num\_model\_requests grouped by model.                                                     |
        | **Spend Spike Alert**          | Alert band 10 / 50 | Spend change vs the prior 30d; fires on a spike per the ai\_spend\_trend band.             |
        | **Top Cost Line Item (30d)**   | Watch only         | The single largest line\_item by 30d cost.                                                 |
        | **Usage Stall Alert**          | Alert band 0 / -50 | Request-volume change vs the prior 30d; a silent stall means the integration or key broke. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                          | Alert behaviour | What it tracks                                                                |
        | ------------------------------- | --------------- | ----------------------------------------------------------------------------- |
        | **Prompt Cache Hit Rate (30d)** | Watch only      | input\_cached\_tokens / input\_tokens x 100. Higher = cheaper repeat prompts. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it 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: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **122 read** and **166 write** operations across assistants, audiovoiceconsents, chatcompletions, evals, evalruns, organizationcertificates on OpenAI. 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=openai)

    #### Proven workflow templates (27)

    <AccordionGroup>
      <Accordion title="Back-in-stock Opportunity Queue">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies high-intent customers and prepares consent-safe notifications.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: Mailchimp, HubSpot, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brand Voice Compliance Review">
        **For** Product content manager · **Ready to deploy**

        flags off-brand, unsupported or inconsistent product claims and proposes corrections.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Preflight Gate">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        validates segment, exclusions, consent, links, stock, offer dates and tracking before send approval.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: Mailchimp, HubSpot, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Completeness Guard">
        **For** Product content manager · **Ready to deploy**

        scores required fields by category and routes the highest-revenue gaps first.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Deliverability and List Health Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        monitors bounce, complaint, suppression and engagement shifts with safe remediation advice.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: Mailchimp, HubSpot, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Duplicate Copy Resolver">
        **For** Product content manager · **Ready to deploy**

        detects reused descriptions and produces differentiated drafts from verified attributes.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flow Performance Decay Watch">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        detects lifecycle automations whose engagement or revenue has materially deteriorated.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: Mailchimp, HubSpot, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Frequency Pressure Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies over-contacted customers across campaigns and flows.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: Mailchimp, HubSpot, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Metadata Optimisation Queue">
        **For** SEO manager · **Ready to deploy**

        generates evidence-based title and description improvements for approval and staged publishing.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New SKU Content Factory">
        **For** Product content manager · **Ready to deploy**

        turns approved source data into complete draft PDPs with a human review queue.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Out-of-stock SEO Protector">
        **For** SEO manager · **Ready to deploy**

        detects valuable unavailable pages and prepares safe redirect, substitute or retention actions.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PDP Enrichment Queue">
        **For** Product content manager · **Ready to deploy**

        finds thin product pages, generates on-brand copy, and batches changes for approval.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Product Claim Evidence Check">
        **For** Product content manager · **Ready to deploy**

        identifies unsubstantiated claims and requires evidence or removal before publish.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Schema Coverage and Validity Sweep">
        **For** SEO manager · **Ready to deploy**

        validates structured data across page types and stages theme/template fixes.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Seasonal Content Refresh">
        **For** Product content manager · **Ready to deploy**

        identifies stale seasonal language and prepares date-safe updates with expiry/rollback.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Segment Drift Monitor">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        flags unexpected audience growth/shrinkage or overlap before it damages sends.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: Mailchimp, HubSpot, BigCommerce, Shopify

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Supplier Copy Normaliser">
        **For** Product content manager · **Ready to deploy**

        converts inconsistent feeds into house style while preserving factual specifications.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Regression Monitor">
        **For** SEO manager · **Ready to deploy**

        watches broken links, redirect chains, canonicals, robots, schema and indexability after changes.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Cloudflare, StagingPro

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Variant Consistency Sweep">
        **For** Product content manager · **Ready to deploy**

        reconciles names, options, specifications and copy across product families.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: DigitalOcean, Google Cloud Platform, Amazon Web Services, Microsoft Azure, Anthropic (Claude), Google Gemini

        Tested alongside: BigCommerce, Shopify, HubSpot, Mailchimp, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                           | Read operations | Write operations |
      | ---------------------------------- | --------------- | ---------------- |
      | assistants                         | 2               | 3                |
      | audiovoiceconsents                 | 2               | 3                |
      | chatcompletions                    | 2               | 3                |
      | evals                              | 2               | 3                |
      | evalruns                           | 2               | 3                |
      | organizationcertificates           | 2               | 3                |
      | organizationgroups                 | 2               | 3                |
      | organizationprojectserviceaccounts | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    13 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# OpenCart on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/opencart

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to OpenCart.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to OpenCart.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/opencart) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=opencart)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                      |
        | -------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**                | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                           |
        | **Extension / Modification Conflicts** | Merchant rule      | OpenCart-distinctive , OCmod / vQmod modifications conflicting (common after a core update). Each conflict can silently break a storefront feature. |
        | **Installed Extensions / Modules**     | Watch only         | Count of installed vQmod / OCmod / extensions , OpenCart installs are extension-heavy.                                                              |
        | **New Customers (30d)**                | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **Newsletter Opt-In Rate**             | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **Order Processing Backlog**           | Alert band 10 / 50 | Alerts for Order Processing Backlog.                                                                                                                |
        | **Order Status Distribution**          | Watch only         | Order Status Distribution, shown by share.                                                                                                          |
        | **Order Volume**                       | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                                                                           |
        | **Pending Orders**                     | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                           |
        | **Processing Orders**                  | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
        | **Stock-Out Burst**                    | Merchant rule      | Alerts for Stock-Out Burst.                                                                                                                         |
        | **Total Customers**                    | Watch only         | Description pending editorial review; the signal is live.                                                                                           |
      </Accordion>

      <Accordion title="Protect revenue (10 signals)">
        | Signal                                         | Alert behaviour   | What it tracks                                               |
        | ---------------------------------------------- | ----------------- | ------------------------------------------------------------ |
        | **Cancellation Rate**                          | Alert band 1 / 3  | Description pending editorial review; the signal is live.    |
        | **Failed Orders (24h)**                        | Alert band -2 / 2 | Description pending editorial review; the signal is live.    |
        | **High-Value Customers Unengaged on Email**    | Merchant rule     | High-Value Customers Unengaged on Email, broken down by row. |
        | **Low-Stock SKUs**                             | Alert band 5 / 50 | Description pending editorial review; the signal is live.    |
        | **OpenCart Inventory vs Marketplace Listings** | Merchant rule     | OpenCart Inventory vs Marketplace Listings.                  |
        | **Orders → Email Attribution**                 | Merchant rule     | Orders → Email Attribution, broken down by row.              |
        | **Out-of-Stock Products**                      | Alert band 0 / 5  | Description pending editorial review; the signal is live.    |
        | **Refund Rate**                                | Alert band 2 / 5  | Description pending editorial review; the signal is live.    |
        | **Revenue at Risk (live)**                     | Merchant rule     | Description pending editorial review; the signal is live.    |
        | **Top-Velocity SKUs vs Ad Spend**              | Merchant rule     | Top-Velocity SKUs vs Ad Spend, broken down by row.           |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                            | Alert behaviour   | What it tracks                                            |
        | --------------------------------- | ----------------- | --------------------------------------------------------- |
        | **Disabled Products**             | Watch only        | Description pending editorial review; the signal is live. |
        | **Empty Categories (0 products)** | Alert band 0 / 3  | Description pending editorial review; the signal is live. |
        | **Products Missing SKU / Model**  | Alert band 5 / 50 | Description pending editorial review; the signal is live. |
        | **Total Products**                | Watch only        | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                         | Alert behaviour | What it tracks                                                                                                                  |
        | ---------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------- |
        | **Error Log Volume (24h)**                     | Merchant rule   | OpenCart writes a system error log , a volume spike flags a freshly broken extension or template.                               |
        | **OpenCart Version Status**                    | Merchant rule   | OpenCart-distinctive , self-hosted means version drift is the merchant's problem. Behind a security release = exploit exposure. |
        | **Platform Error Spike or Extension Conflict** | Merchant rule   | OpenCart-distinctive , self-hosted platform failures surface here first.                                                        |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                   | Alert behaviour    | What it tracks                                            |
        | ------------------------ | ------------------ | --------------------------------------------------------- |
        | **Repeat Customer Rate** | Alert band 25 / 10 | Description pending editorial review; the signal is live. |
        | **Total Revenue (30d)**  | Alert band 0 / -5  | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across categorys, customers, logins, orders, products on OpenCart. 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=opencart)

    #### Ready to build your first OpenCart 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.

    <Accordion title="Browse the operations you can build with">
      | Resource  | Read operations | Write operations |
      | --------- | --------------- | ---------------- |
      | categorys | 1               | 0                |
      | customers | 1               | 0                |
      | logins    | 0               | 1                |
      | orders    | 1               | 0                |
      | products  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Opsgenie on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/opsgenie

Monitor Opsgenie performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Opsgenie performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=opsgenie)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                       | Alert behaviour        | What it tracks                                                                                     |
        | ---------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Merchant rule          | Alerts a human has acknowledged - the gap vs Alerts Firing is the un-routed / no-coverage backlog. |
        | **Alerts Firing**            | Alert band 0 / 50      | Open, un-closed alerts right now - the front-line load on the on-call rotation.                    |
        | **Incidents Open**           | Alert band 0 / 3       | Declared incidents not yet resolved - escalations beyond a single alert.                           |
        | **Incidents Resolved (24h)** | Merchant rule          | Throughput of the response process over the last day.                                              |
        | **Mean Time To Acknowledge** | Alert band 120 / 600   | createdAt -> acknowledgedAt across alerts. Rising MTTA = on-call routing or coverage gaps.         |
        | **Mean Time To Resolve**     | Alert band 1800 / 7200 | createdAt -> resolvedAt across incidents. The customer-impact-duration number.                     |
        | **SLA Compliance**           | Alert band 99.9 / 99.5 | % of the period inside SLA across services. The headline reliability commitment number.            |
        | **Services Degraded**        | Alert band 0 / 2       | Services with open alerts but not fully down - early-warning surface.                              |
        | **Services Down**            | Alert band 0 / 1       | Services with an open incident impacting them - any value above zero is customer-facing.           |
        | **Services Healthy**         | Merchant rule          | Services reporting healthy with no open alerts or incidents.                                       |
        | **Top Alerting Services**    | Alert band 0 / 100     | Services ranked by alert volume - where the noise (and the on-call burden) concentrates.           |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour       | What it tracks                                            |
        | ------------------------ | --------------------- | --------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live. |
        | **Avg Response Time**    | Alert band 200 / 1000 | Description pending editorial review; the signal is live. |
        | **Error Rate**           | Alert band 0.5 / 2    | Description pending editorial review; the signal is live. |
        | **Throughput (req/min)** | Alert band 0 / -10    | Throughput (req/min) over time.                           |
        | **p95 Latency**          | Alert band 200 / 1000 | Description pending editorial review; the signal is live. |
        | **p99 Latency**          | Alert band 800 / 3000 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                                        | Alert behaviour | What it tracks                                                                                                            |
        | --------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------- |
        | **Alert Storm on Commerce-Critical Services** | Merchant rule   | Alert volume on services that front checkout / payments / search, overlaid with order velocity - noise on the money path. |
        | **Revenue Lost / Min (open incidents)**       | Merchant rule   | Live \$/min loss while incidents impacting commerce-critical services are open. The COO's number.                         |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour    | What it tracks                                                                               |
        | ------------------- | ------------------ | -------------------------------------------------------------------------------------------- |
        | **Top Error Types** | Alert band 0 / 100 | Alert messages clustered by error type - the recurring failure modes worth fixing at source. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **2 write** operations across accounts, alerts, alertacknowledges, alertcloses, alertcounts, incidents on Opsgenie. 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=opsgenie)

    #### Ready to build your first Opsgenie 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | accounts          | 1               | 0                |
      | alerts            | 1               | 0                |
      | alertacknowledges | 0               | 1                |
      | alertcloses       | 0               | 1                |
      | alertcounts       | 1               | 0                |
      | incidents         | 1               | 0                |
      | services          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Oracle Database on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/oracle

Monitor Oracle Database health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Oracle Database health, cost and reliability signals, and catch incidents and runaway spend early.

[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=oracle)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="16">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                             |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Sessions**                    | Watch only         | COUNT of V\$SESSION WHERE STATUS='ACTIVE' AND TYPE='USER'.                                                                                 |
        | **Archive Log Apply Gap**              | Merchant rule      | Data Guard only - sequence gap between primary archived and standby applied (V\$ARCHIVED\_LOG). A growing gap shrinks the recovery window. |
        | **Blocked Sessions**                   | Merchant rule      | V$SESSION WHERE BLOCKING_SESSION IS NOT NULL (corroborated by V$LOCK / DBA\_BLOCKERS). Long blocker chains stall the app.                  |
        | **Buffer Cache Hit Ratio %**           | Alert band 95 / 80 | 1 - (physical reads / (db block gets + consistent gets)) from V\$SYSSTAT. Low = SGA / buffer cache undersized, data read from disk.        |
        | **Data Guard Transport Lag (seconds)** | Merchant rule      | Data Guard only - 'transport lag' from V\$DATAGUARD\_STATS. Growing transport lag = redo not shipping (network / archiver stuck).          |
        | **Instance Uptime**                    | Watch only         | SYSDATE - STARTUP\_TIME from V\$INSTANCE. Drop = unplanned restart / instance crash.                                                       |
        | **Library Cache Hit Ratio %**          | Merchant rule      | Oracle-distinctive - GETHITRATIO from V\$LIBRARYCACHE. Low = excessive hard parses (no bind variables) thrashing the shared pool.          |
        | **Oracle Health Score**                | Merchant rule      | Composite of wait-class health, blocking, Data Guard lag, cache hit ratios, and backup recency. \<70 = investigate.                        |
        | **PGA Memory Usage %**                 | Merchant rule      | Total PGA allocated / PGA aggregate target from V\$PGASTAT. Over target = work areas spilling to temp tablespace.                          |
        | **SQL Executions / Second (live)**     | Watch only         | 'execute count' delta from V\$SYSSTAT - primary throughput signal.                                                                         |
        | **Session Saturation %**               | Alert band 70 / 90 | CURRENT\_UTILIZATION / LIMIT\_VALUE for resource\_name='sessions' from V\$RESOURCE\_LIMIT. >90% = ORA-00018 imminent.                      |
        | **Standby Apply State**                | Watch only         | Data Guard only - RECOVERY\_MODE / managed-recovery state per standby destination from V\$ARCHIVE\_DEST\_STATUS.                           |
        | **Tablespace Usage >90%**              | Alert band 70 / 90 | DBA\_TABLESPACE\_USAGE\_METRICS - a tablespace hitting its autoextend MAXSIZE stalls every write to it (ORA-01653).                        |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                                  | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Blocking / Slow SQL During Checkout Window**          | Merchant rule      | Blocking / Slow SQL During Checkout Window, broken down by row.                                                                                        |
        | **Failed Logins (24h)**                                 | Merchant rule      | 'logon failures' delta from V\$SYSSTAT (or DBA\_AUDIT\_SESSION when auditing is on). Bursts = brute force or stale app credentials.                    |
        | **Oracle Load Spike vs Ecom Order Rate**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Oracle Product Table Row Count vs Ecom Catalog Size** | Merchant rule      | Oracle-distinctive XC - many enterprise merchants keep their product / inventory master in Oracle; row-count drift vs ecom = sync failure / oversell r |
        | **Oracle Session Saturation vs Traffic Burst**          | Alert band 70 / 90 | Oracle Session Saturation vs Traffic Burst, broken down by row.                                                                                        |
        | **Tablespace Usage %**                                  | Alert band 70 / 90 | Max used\_percent across permanent tablespaces from DBA\_TABLESPACE\_USAGE\_METRICS. >90% = autoextend exhaustion risk.                                |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                              | Alert behaviour     | What it tracks                                                                                                                                            |
        | ----------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg SQL Elapsed per Exec (ms)**   | Alert band 50 / 200 | ELAPSED\_TIME / EXECUTIONS across V\$SQLSTATS. Oracle exposes per-statement averages, not native percentiles - p95/p99 derived.                           |
        | **Slow-SQL Rate %**                 | Alert band 1 / 5    | Share of executions over the slow threshold (default 200ms) from V\$SQLSTATS deltas between polls.                                                        |
        | **Top 10 SQL by Elapsed Time**      | Watch only          | Ordered by ELAPSED\_TIME / BUFFER\_GETS from V\$SQLSTATS + SQL\_TEXT. The Top SQL surface DBAs tune first.                                                |
        | **Top Wait Events (by wait class)** | Watch only          | Oracle-distinctive - V$SYSTEM_EVENT / V$ACTIVE\_SESSION\_HISTORY grouped by WAIT\_CLASS. 'db file sequential read', 'log file sync', 'enq: TX' climbing = |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                              |
        | -------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Blocking Lock Chain >30s**           | Merchant rule      | V\$SESSION.BLOCKING\_SESSION chain sustained - row-lock contention stalling the app.                                                                        |
        | **Enqueue (Lock) Waits**               | Merchant rule      | Oracle-distinctive - 'enq: TX - row lock contention' / 'enq: TM' waits from V\$SYSTEM\_EVENT. Climbing = lock contention building.                          |
        | **Last Successful Backup (hours ago)** | Alert band 24 / 72 | MAX(COMPLETION\_TIME) for a successful full / L0 backup from V\$RMAN\_BACKUP\_JOB\_DETAILS. Autonomous / RDS: automatic backups - derive from the managed b |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                                | Alert behaviour    | What it tracks                                                                                                           |
        | ----------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
        | **Data Guard Apply Lag (seconds)**                    | Alert band 1 / 10  | Data Guard only - 'apply lag' from V\$DATAGUARD\_STATS. Gated when no standby is configured.                             |
        | **Data Guard Apply Lag >10s or Standby Not Applying** | Alert band 1 / 10  | Data Guard only - gated when no standby is configured.                                                                   |
        | **User Error Rate %**                                 | Alert band 0.1 / 1 | 'user errors' delta from V\$SYSSTAT over execute count. Spikes flag failing statements / app retry storms (ORA- errors). |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **16 read** and **0 write** operations across dbatablespaceusagemetrics, v$archivedeststatus, v$archivedlogs, v$databases, v$dataguardstats, v\$instances on Oracle Database. 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=oracle)

    #### Ready to build your first Oracle Database 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | dbatablespaceusagemetrics | 1               | 0                |
      | v\$archivedeststatus      | 1               | 0                |
      | v\$archivedlogs           | 1               | 0                |
      | v\$databases              | 1               | 0                |
      | v\$dataguardstats         | 1               | 0                |
      | v\$instances              | 1               | 0                |
      | v\$librarycaches          | 1               | 0                |
      | v\$locks                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Oracle ERP Cloud (Fusion) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/oracle-erp

Monitor Oracle ERP Cloud (Fusion) performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Oracle ERP Cloud (Fusion) performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=oracle-erp)

<CardGroup>
  <Card title="89">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (89)">
    ### Monitor performance

    89 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (61 signals)">
        | Signal                                          | Alert behaviour      | What it tracks                                                                                                                                         |
        | ----------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **A/R Aging Detail**                            | Alert band 5 / 25    | A/R Aging Detail from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconc |
        | **AP Aging , 60+ Days**                         | Alert band 10 / 30   | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Aging Buckets**                            | Watch only           | AR Aging Buckets, compared across items.                                                                                                               |
        | **AR Aging , 60+ Days**                         | Alert band 5 / 15    | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Balance (live, by Business Unit)**         | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Accrual Reversals (last close)**              | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Active Customers**                            | Watch only           | Active Customers from Oracle ERP Cloud (Fusion), grouped under Customer Master. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; re |
        | **Active Suppliers**                            | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Landed Cost per Unit**                | Alert band 0 / 10    | Average Landed Cost per Unit from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is con |
        | **Average Sales Order Value**                   | Alert band 0 / -5    | Average Sales Order Value from Oracle ERP Cloud (Fusion), grouped under Sales Orders. Computes when a live Oracle ERP Cloud (Fusion) tenant is connect |
        | **B2B Payment Terms Mix**                       | Watch only           | B2B Payment Terms Mix from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Business Unit Health Roll-up**                | Watch only           | Business Unit Health Roll-up from Oracle ERP Cloud (Fusion), grouped under Executive Overview. Computes when a live Oracle ERP Cloud (Fusion) tenant i |
        | **Cash Application Rate**                       | Alert band 95 / 85   | Cash Application Rate from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Cash Applied Today**                          | Watch only           | Cash Applied Today from Oracle ERP Cloud (Fusion), grouped under Executive Overview. Computes when a live Oracle ERP Cloud (Fusion) tenant is connecte |
        | **Credit Hold Spike**                           | Watch only           | Credit Hold Spike from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; recon |
        | **Customer Churn Signals**                      | Watch only           | Customer Churn Signals from Oracle ERP Cloud (Fusion), grouped under Customer Master. Computes when a live Oracle ERP Cloud (Fusion) tenant is connect |
        | **Customer Credit Utilisation**                 | Alert band 60 / 85   | Customer Credit Utilisation from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connec |
        | **DSO Increase Alert**                          | Watch only           | DSO Increase Alert from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reco |
        | **Days Sales Outstanding (DSO)**                | Alert band 30 / 60   | Description pending editorial review; the signal is live.                                                                                              |
        | **Dead Stock Threshold Breach**                 | Watch only           | Dead Stock Threshold Breach from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) tenant is connecte |
        | **Dead Stock Value**                            | Alert band 5 / 15    | Dead Stock Value from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconcil |
        | **ERP-vs-Ecom Inventory Variance %**            | Alert band 1 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Ecom Customers Absent from Fusion Party**     | Alert band 0 / 10    | Description pending editorial review; the signal is live.                                                                                              |
        | **FX Currency Exposure**                        | Alert band 5 / 15    | FX Currency Exposure from Oracle ERP Cloud (Fusion), grouped under Executive Overview. Computes when a live Oracle ERP Cloud (Fusion) tenant is connec |
        | **GL Period Close Past Deadline**               | Alert band 0 / 5     | Alerts for GL Period Close Past Deadline.                                                                                                              |
        | **GL Period Close Status**                      | Alert band 0 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Gross Margin Percentage**                     | Watch only           | Gross Margin Percentage from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is connecte |
        | **High-Value Overdue Invoices**                 | Watch only           | High-Value Overdue Invoices from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connec |
        | **Intercompany Balance**                        | Watch only           | Intercompany Balance from Oracle ERP Cloud (Fusion), grouped under Multi-Entity. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Intercompany Business Unit Imbalances**       | Merchant rule        | Cross-Business-Unit journals failing intercompany balance check. Blocks Cloud EPM consolidation.                                                       |
        | **Inventory Aging**                             | Alert band 5 / 15    | Inventory Aging from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconcile |
        | **Inventory AvailableQuantity Went Negative**   | Merchant rule        | Alerts for Inventory AvailableQuantity Went Negative.                                                                                                  |
        | **Inventory Carrying Cost**                     | Watch only           | Inventory Carrying Cost from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is connecte |
        | **Inventory Turnover Ratio**                    | Alert band 4 / 2     | Inventory Turnover Ratio from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected;  |
        | **Inventory Value by Inventory Org**            | Watch only           | Inventory Value by Inventory Org.                                                                                                                      |
        | **Journals by Source (JeSource)**               | Watch only           | Manual / Receivables / Payables / Inventory / Spreadsheet split. Receivables spike from ecom integration = good; Manual spike = controls gap.          |
        | **Landed Cost Variance vs Standard**            | Alert band 2 / 5     | Landed Cost Variance vs Standard from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is |
        | **Manual JEs as % of Total**                    | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Margin Compression**                          | Watch only           | Margin Compression from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; re |
        | **Margin Erosion Alerts**                       | Watch only           | Margin Erosion Alerts from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; |
        | **Margin by SKU**                               | Watch only           | Margin by SKU from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconci |
        | **New Party Records (30d)**                     | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **OIC Integration Flow Failures (24h)**         | Merchant rule        | Oracle Integration Cloud flows that mediate ecom→Fusion. Spike = trigger source down OR Fusion endpoint changed.                                       |
        | **On-Hand Inventory Value (by Inventory Org)**  | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Open (Unposted) Journals**                    | Alert band 0 / 50    | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Sales Order Value**                      | Watch only           | Open Sales Order Value from Oracle ERP Cloud (Fusion), grouped under Sales Orders. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; |
        | **Open Sales Orders**                           | Watch only           | Open Sales Orders from Oracle ERP Cloud (Fusion), grouped under Sales Orders. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reco |
        | **Oracle Fusion Health Score**                  | Merchant rule        | Composite: subledger-gl-posting-clean x intercompany-balanced x OIC-flows-healthy x AR-aging-low.                                                      |
        | **Orders on Credit Hold**                       | Watch only           | Orders on Credit Hold from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Overdue Invoice Value**                       | Alert band 0 / 50000 | Overdue Invoice Value from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Period Close On-Time Rate (12mo)**            | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Returns Count**                               | Alert band 5 / 20    | Returns Count from Oracle ERP Cloud (Fusion), grouped under Sales Orders. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconcil |
        | **Sales Order State Breakdown**                 | Watch only           | Sales Order State Breakdown from Oracle ERP Cloud (Fusion), grouped under Sales Orders. Computes when a live Oracle ERP Cloud (Fusion) tenant is conne |
        | **Sales Order to Invoice Lead Time**            | Alert band 3 / 7     | Sales Order to Invoice Lead Time from Oracle ERP Cloud (Fusion), grouped under Sales Orders. Computes when a live Oracle ERP Cloud (Fusion) tenant is  |
        | **Sales Orders Blocked on Inventory or Credit** | Alert band 0 / 5     | Sales Orders Blocked on Inventory or Credit from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) te |
        | **Slow-Moving Items (>90d no movement)**        | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Top Findings Across Business Units**          | Watch only           | Top Findings Across Business Units from Oracle ERP Cloud (Fusion), grouped under Multi-Entity. Computes when a live Oracle ERP Cloud (Fusion) tenant i |
        | **Top SKUs by Inventory Value**                 | Watch only           | Top SKUs by Inventory Value from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) tenant is connecte |
        | **Total COGS**                                  | Watch only           | Total COGS from Oracle ERP Cloud (Fusion), grouped under Margin & Cost. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconciles |
        | **Unpaid Invoice Count**                        | Watch only           | Unpaid Invoice Count from Oracle ERP Cloud (Fusion), grouped under AP/AR Cycle. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; re |
        | **Vendor Payment On-Time Rate**                 | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (13 signals)">
        | Signal                                                          | Alert behaviour         | What it tracks                                                                                                                                         |
        | --------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AR Aging on Customers with Active Ecom Orders**               | Alert band 1000 / 10000 | Fusion Credit Management should auto-classify these as high-risk via Credit Authorization rules.                                                       |
        | **Commerce Orders Without Oracle ERP Cloud Sales Order**        | Watch only              | Commerce Orders Without Oracle ERP Cloud Sales Order from Oracle ERP Cloud (Fusion), grouped under Cross-Channel: Revenue at Risk. Computes when a liv |
        | **Customers with TaxRegistrationNumber Mismatch (B2B)**         | Merchant rule           | B2B customers where ecom-stored VAT/Tax ID differs from Fusion Party , reverse-charge accounting risk.                                                 |
        | **Dead Stock with Active Ad Spend**                             | Watch only              | Dead Stock with Active Ad Spend from Oracle ERP Cloud (Fusion), grouped under Cross-Channel: Revenue at Risk. Computes when a live Oracle ERP Cloud (F |
        | **Ecom Orders Missing Matching Fusion Receivables Transaction** | Merchant rule           | Common cause: OIC flow that posts Receivables Transactions failed silently. SOX-audit gap on top of the missed revenue.                                |
        | **High-Credit-Risk Customers**                                  | Merchant rule           | Customers classified as high-risk in Fusion Credit Management. Spike = collections / underwriting tightening needed.                                   |
        | **Inventory Sync Drift**                                        | Watch only              | Inventory Sync Drift from Oracle ERP Cloud (Fusion), grouped under Cross-Channel: Revenue at Risk. Computes when a live Oracle ERP Cloud (Fusion) tena |
        | **Low Stock Alerts**                                            | Watch only              | Low Stock Alerts from Oracle ERP Cloud (Fusion), grouped under Inventory. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reconcil |
        | **OOS with Open Sales Order Demand**                            | Watch only              | OOS with Open Sales Order Demand from Oracle ERP Cloud (Fusion), grouped under Cross-Channel: Revenue at Risk. Computes when a live Oracle ERP Cloud ( |
        | **Revenue Gap**                                                 | Watch only              | Revenue Gap from Oracle ERP Cloud (Fusion), grouped under Cross-Channel: Revenue at Risk. Computes when a live Oracle ERP Cloud (Fusion) tenant is con |
        | **SKUs with Fusion-vs-Ecom Inventory Drift >5%**                | Alert band 1 / 5        | SKUs with Fusion-vs-Ecom Inventory Drift >5%, broken down by row.                                                                                      |
        | **Subledger-to-GL Posting Failed (any source)**                 | Alert band 0 / 5        | Fusion's strict GL validation rejects on COA segment issues. Blocks Receivables from flowing to GL.                                                    |
        | **Subledger-to-GL Posting Interface Errors (24h)**              | Merchant rule           | Fusion-specific: Receivables / Payables / Inventory subledger transactions failed to post to GL. Often dimension validation fail.                      |
      </Accordion>

      <Accordion title="Grow revenue (13 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cash Collected**              | Alert band 0 / -15 | Cash Collected from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; reco |
        | **Consolidated Revenue Trend**  | Watch only         | Consolidated Revenue Trend from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is con |
        | **Credit Memo Value**           | Watch only         | Credit Memo Value from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Invoiced Revenue**            | Alert band 0 / -5  | Invoiced Revenue from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; re |
        | **Revenue Booked Over Time**    | Watch only         | Revenue Booked Over Time from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is conne |
        | **Revenue Booked into GL**      | Watch only         | Revenue Booked into GL from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connect |
        | **Revenue Gap Spike**           | Watch only         | Revenue Gap Spike from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; r |
        | **Revenue Gap vs Commerce**     | Alert band 0 / 5   | Revenue Gap vs Commerce from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connec |
        | **Revenue by Business Unit**    | Watch only         | Revenue by Business Unit from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is conne |
        | **Revenue by Currency**         | Watch only         | Revenue by Currency from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected; |
        | **Revenue by Segment**          | Watch only         | Revenue by Segment from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is connected;  |
        | **Top B2B Accounts by Revenue** | Watch only         | Top B2B Accounts by Revenue from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is co |
        | **Top Customers by Revenue**    | Watch only         | Top Customers by Revenue from Oracle ERP Cloud (Fusion), grouped under Revenue & Sales. Computes when a live Oracle ERP Cloud (Fusion) tenant is conne |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                               | Alert behaviour  | What it tracks                                                                                                                  |
        | ------------------------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------- |
        | **Journals in Error (PostedFlag=E)** | Alert band 0 / 5 | Fusion rejects on account combination invalid, segment value disabled, or balance mismatch. Common after COA segment additions. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                                                                         |
        | ----------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Business Unit Performance** | Watch only      | Business Unit Performance from Oracle ERP Cloud (Fusion), grouped under Executive Overview. Computes when a live Oracle ERP Cloud (Fusion) tenant is c |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across fscmrestapiresourcecustomersv2s, fscmrestapiresourceitemsv2s, fscmrestapiresourcejournals, fscmrestapiresourcesuppliers, oauth2tokens on Oracle ERP Cloud (Fusion). 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=oracle-erp)

    #### Ready to build your first Oracle ERP Cloud (Fusion) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                        | Read operations | Write operations |
      | ------------------------------- | --------------- | ---------------- |
      | fscmrestapiresourcecustomersv2s | 1               | 0                |
      | fscmrestapiresourceitemsv2s     | 1               | 0                |
      | fscmrestapiresourcejournals     | 1               | 0                |
      | fscmrestapiresourcesuppliers    | 1               | 0                |
      | oauth2tokens                    | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Outbrain on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/outbrain

Monitor Outbrain campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Outbrain campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/outbrain) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=outbrain)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                                        | Alert behaviour    | What it tracks                                                                                                      |
        | --------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**                           | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **CPC by Campaign**                           | Watch only         | CPC by Campaign.                                                                                                    |
        | **CTR by Campaign**                           | Watch only         | CTR by Campaign.                                                                                                    |
        | **Campaign Comparison**                       | Watch only         | Campaign Comparison, broken down by row.                                                                            |
        | **Clicks vs Conversions**                     | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Conversion Actions Breakdown**              | Watch only         | Conversion Actions Breakdown.                                                                                       |
        | **Conversion Drop Alert**                     | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Conversion Funnel**                         | Watch only         | Conversion Funnel, stage by stage.                                                                                  |
        | **Conversion Lag**                            | Watch only         | Conversion Lag, compared across items.                                                                              |
        | **Conversion Rate Trend**                     | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Conversion Rate by Campaign**               | Watch only         | Conversion Rate by Campaign.                                                                                        |
        | **Conversion Rate by Device**                 | Watch only         | Conversion Rate by Device.                                                                                          |
        | **Conversions Trend**                         | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Conversions by Campaign**                   | Watch only         | Conversions by Campaign.                                                                                            |
        | **Conversions by Country**                    | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Conversions by Day of Week**                | Watch only         | Conversions by Day of Week.                                                                                         |
        | **Conversions by Device**                     | Watch only         | Conversions by Device.                                                                                              |
        | **Conversions by Hour**                       | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Landing Page Revenue**                      | Watch only         | Landing Page Revenue, broken down by row.                                                                           |
        | **Outbrain Conversion Pixel Tracking Broken** | Merchant rule      | Multi-step native funnel , pixel decay degrades Smart Bidding training within 24h, ROAS collapses.                  |
        | **Overspending Campaigns**                    | Watch only         | Overspending Campaigns, broken down by row.                                                                         |
        | **ROAS**                                      | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                           |
        | **ROAS Dropped Below Threshold**              | Alert band 3 / 1.5 | Outbrain ROAS shifts mean publisher whitelist drift OR Smart Bidding model regression , investigate within the day. |
        | **ROAS Trend**                                | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **ROAS by Campaign**                          | Watch only         | ROAS by Campaign.                                                                                                   |
        | **ROAS by Day of Week**                       | Watch only         | ROAS by Day of Week.                                                                                                |
        | **ROAS by Device**                            | Watch only         | ROAS by Device.                                                                                                     |
        | **ROAS by Region**                            | Watch only         | ROAS by Region.                                                                                                     |
        | **Revenue by Campaign**                       | Watch only         | Revenue by Campaign.                                                                                                |
        | **Search Terms Report**                       | Watch only         | Search Terms Report, broken down by row.                                                                            |
        | **Spend by Campaign**                         | Watch only         | Spend by Campaign.                                                                                                  |
        | **Top Cities by Conversions**                 | Watch only         | Top Cities by Conversions.                                                                                          |
        | **Top Keywords by Conversions**               | Watch only         | Top Keywords by Conversions.                                                                                        |
        | **Top Performing Campaigns**                  | Watch only         | Top Performing Campaigns, broken down by row.                                                                       |
        | **Total Revenue**                             | Watch only         | Description pending editorial review; the signal is live.                                                           |
        | **Underspending Campaigns**                   | Watch only         | Underspending Campaigns, broken down by row.                                                                        |
        | **Worst Performing Campaigns**                | Watch only         | Worst Performing Campaigns, broken down by row.                                                                     |
        | **Zero-Conversion Spend**                     | Watch only         | Description pending editorial review; the signal is live.                                                           |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                     |
        | -------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Budget Utilisation**                             | Alert band 70 / 30 | Description pending editorial review; the signal is live.                                          |
        | **CPA Trend**                                      | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CPA by Keyword**                                 | Watch only         | CPA by Keyword.                                                                                    |
        | **CPC Anomaly**                                    | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CPC Spike Detection**                            | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CPC Trend**                                      | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                          |
        | **CTR Trend**                                      | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **CTR by Keyword**                                 | Watch only         | CTR by Keyword.                                                                                    |
        | **Impression Share**                               | Alert band 70 / 40 | Description pending editorial review; the signal is live.                                          |
        | **Impressions Trend**                              | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Quality Score Distribution**                     | Alert band 7 / 4   | Quality Score Distribution, compared across items.                                                 |
        | **Spend Anomaly**                                  | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Spend Over Time**                                | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                          |
        | **Spend vs Budget**                                | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Top Keywords by Spend**                          | Watch only         | Top Keywords by Spend.                                                                             |
        | **Total Spend**                                    | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Wasted Spend**                                   | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Wasted-Spend Burst (long-tail publisher drift)** | Alert band 5 / 50  | Premium placements drifting into long-tail = wasted spend at premium CPC. Catches the drift early. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                  | Alert behaviour   | What it tracks                                                                                                           |
        | ------------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------ |
        | **Active Product-Feed Native Ads on Out-of-Stock SKUs** | Alert band 5 / 50 | Outbrain product-feed native ads on OOS SKUs , pause the feed entry, recover the premium-publisher spend.                |
        | **Branded Paid Clicks Cannibalising Organic**           | Merchant rule     | Premium-publisher native ads targeting branded audiences who already find the brand via Google , pure margin reclaim.    |
        | **CTR Decline Alert**                                   | Watch only        | Description pending editorial review; the signal is live.                                                                |
        | **Landing Pages with Poor Web Vitals**                  | Merchant rule     | Premium-native click-throughs are already cold leads , slow pages compound abandonment, esp. on international 3G mobile. |
        | **Spend on Campaigns with Active Feed Rejections**      | Merchant rule     | £ on Outbrain product-feed campaigns whose Feedonomics feed has rejections.                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **2 write** operations across amplifycampaignpromotedlinks, amplifymarketers, amplifymarketercampaigns, amplifyoauthtokens, amplifyreportmarketercampaigns on Outbrain. 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=outbrain)

    #### Ready to build your first Outbrain 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                       | Read operations | Write operations |
      | ------------------------------ | --------------- | ---------------- |
      | amplifycampaignpromotedlinks   | 1               | 0                |
      | amplifymarketers               | 1               | 0                |
      | amplifymarketercampaigns       | 1               | 0                |
      | amplifyoauthtokens             | 0               | 1                |
      | amplifyreportmarketercampaigns | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PagerDuty on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/pagerduty

Monitor PagerDuty performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor PagerDuty performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=pagerduty)

<CardGroup>
  <Card title="21">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (21)">
    ### Monitor performance

    21 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                                   | Alert behaviour        | What it tracks                                                                                                      |
        | ---------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **Active Incidents**                     | Alert band 0 / 1       | Open triggered/acknowledged incidents right now. Sev1/sev2 = someone should be paged and moving.                    |
        | **Inactive Webhook Subscriptions**       | Alert band 0 / 1       | Subscriptions toggled off - state changes stop flowing back with no error, the quietest failure mode.               |
        | **Mean Time to Acknowledge**             | Alert band 300 / 900   | Median alert-generation → acknowledgement. The headline on-call responsiveness number.                              |
        | **Median Submission Latency**            | Alert band 1000 / 5000 | Time from alert generation to PagerDuty acceptance. Latency here delays the page.                                   |
        | **On-Call Schedule Gaps (next 24h)**     | Alert band 0 / 1       | Uncovered windows in the on-call schedule - a page during the gap escalates to nobody.                              |
        | **Retried Submissions (429/5xx)**        | Merchant rule          | Events that needed exponential-backoff retry. A spike means PagerDuty-side throttling or an outage.                 |
        | **Routing Key Health**                   | Alert band 100 / 95    | % of services with an active, mapped routing key. Any revoked/rotated/unmapped key = a page that goes nowhere.      |
        | **Sev1 Policies Without Always-On Rota** | Merchant rule          | Sev1-mapped escalation policies that lack a 24/7 rota or any escalation step - looks wired, isn't.                  |
        | **Severity Tiers Without a Service**     | Merchant rule          | A Vortex IQ severity tier (sev1/sev2/sev3) with no PagerDuty service mapped - those alerts have nowhere to route.   |
        | **Submission Success by Service**        | Merchant rule          | Per-service acceptance rate - isolates which routing key / service is dropping events.                              |
        | **Webhook Back-Sync Lag**                | Alert band 30 / 300    | Time between a PagerDuty state change (ack/escalate/resolve) and Vortex IQ ingest. Lag = a stale incident timeline. |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                         | Alert behaviour         | What it tracks                                                                                              |
        | ------------------------------ | ----------------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Escalation Rate**            | Alert band 10 / 30      | % of incidents that escalated past the first responder. Rising = first-line is overloaded or under-staffed. |
        | **Incident Volume by Service** | Merchant rule           | Which services page most - the noisiest surfaces to tune or invest in.                                      |
        | **MTTA by Severity**           | Merchant rule           | Acknowledgement speed split sev1/sev2/sev3 - sev1 must be fastest.                                          |
        | **Mean Time to Resolve**       | Alert band 3600 / 14400 | Trigger → resolved, the incident lifecycle length. Trending up means incidents are getting stickier.        |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                             | Alert behaviour      | What it tracks                                                                                                     |
        | ---------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------ |
        | **Event Submission Success Rate**  | Alert band 99.9 / 99 | Events accepted by the Events API v2 / total submitted. Below 99% = pages are being dropped.                       |
        | **Fail-Open Audit-Logged Events**  | Merchant rule        | Events the API could not accept that fell back to the audit log - investigate each, none should be silently lost.  |
        | **Revoked / Rotated Routing Keys** | Merchant rule        | Services whose Events API v2 key is revoked or rotated - Vortex IQ pages here silently fail. Highest-leverage fix. |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                    | Alert behaviour | What it tracks                                                                                               |
        | ----------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Revenue at Risk (open sev1 incidents)** | Merchant rule   | Live $/min loss while a sev1 incident sits open. Turns 'an incident is on' into 'this is costing $X/min'.    |
        | **Un-Acked Pages During Peak Sales**      | Merchant rule   | A sev1 page nobody acknowledged while orders were flowing - the worst-case missed-page during revenue hours. |
        | **Webhook Delivery Failures (24h)**       | Merchant rule   | Webhook subscriptions with a failed last delivery - back-sync is broken until they recover.                  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for PagerDuty yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **2 write** operations across incidents, abilitys, analyticsmetricsincidentalls, enqueues, escalationpolicys, schedules on PagerDuty. 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=pagerduty)

    #### Ready to build your first PagerDuty 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | incidents                    | 2               | 0                |
      | abilitys                     | 1               | 0                |
      | analyticsmetricsincidentalls | 0               | 1                |
      | enqueues                     | 0               | 1                |
      | escalationpolicys            | 1               | 0                |
      | schedules                    | 1               | 0                |
      | services                     | 1               | 0                |
      | webhooksubscriptions         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Parcelforce Worldwide on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/parcelforce

Monitor Parcelforce Worldwide delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Parcelforce Worldwide delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=parcelforce)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                           | Alert behaviour  | What it tracks                                                                                                   |
        | -------------------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**               | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Avg Shipping Cost**            | Merchant rule    | Description pending editorial review; the signal is live.                                                        |
        | **Claim Value (open)**           | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Cost Per Shipment Trend**      | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Cost by Zone**                 | Watch only       | Cost by Zone.                                                                                                    |
        | **Days to Token Expiry**         | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Exception Rate**               | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                        |
        | **High-Cost Shipment Outliers**  | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                 |
        | **Label Generation Success**     | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **OTD by Route**                 | Watch only       | OTD by Route.                                                                                                    |
        | **Open Claims**                  | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Returned to Sender**           | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Route Volume Concentration**   | Merchant rule    | Route Volume Concentration, compared across items.                                                               |
        | **Saturday Delivery Uplift ROI** | Merchant rule    | Marginal cost of paying Saturday-delivery uplift vs OTD lift - if uplift is paying for nothing, finance trigger. |
        | **Shipments**                    | Merchant rule    | Description pending editorial review; the signal is live.                                                        |
        | **Shipments Over Time**          | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Shipments by Destination**     | Watch only       | Description pending editorial review; the signal is live.                                                        |
        | **Shipments by Service**         | Watch only       | Shipments by Service.                                                                                            |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                           |
        | --------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Transit (days)**            | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Express24 Service Day Promise** | Alert band 95 / 90 | % of Express24 consignments delivered next working day - the contracted Parcelforce premium-service promise (\~98% SLA). |
        | **First-Attempt Delivery Rate**   | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Late Shipments**                | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **On-Time Delivery Rate**         | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                       |
        | ------------------------------------ | ------------------ | -------------------------------------------------------------------- |
        | **Failed Deliveries**                | Merchant rule      | Description pending editorial review; the signal is live.            |
        | **Parcelforce OTD by Sales Channel** | Alert band 95 / 90 | Per-channel Parcelforce OTD - which sales surface is suffering most. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **1 write** operations across tbds on Parcelforce Worldwide. 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=parcelforce)

    #### Ready to build your first Parcelforce Worldwide 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 1               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PayPal on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/paypal

Monitor PayPal payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor PayPal payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/paypal) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=paypal)

<CardGroup>
  <Card title="4">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="115">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (4)">
    ### Monitor performance

    4 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (2 signals)">
        | Signal                    | Alert behaviour | What it tracks                          |
        | ------------------------- | --------------- | --------------------------------------- |
        | **Avg Transaction Value** | Watch only      | Average PayPal transaction value.       |
        | **Total Revenue**         | Watch only      | Total revenue from PayPal transactions. |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal            | Alert behaviour | What it tracks              |
        | ----------------- | --------------- | --------------------------- |
        | **Total Refunds** | Merchant rule   | Total PayPal refund amount. |
      </Accordion>

      <Accordion title="Run operations (1 signals)">
        | Signal                | Alert behaviour | What it tracks                 |
        | --------------------- | --------------- | ------------------------------ |
        | **Transaction Count** | Watch only      | Number of PayPal transactions. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **38 read** and **77 write** operations across payment experiencewebprofiles, invoicinginvoices, invoicingtemplates, notification webhooks, billingplans, catalog products on PayPal. 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=paypal)

    #### Ready to build your first PayPal 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                      | Read operations | Write operations |
      | ----------------------------- | --------------- | ---------------- |
      | payment experiencewebprofiles | 2               | 4                |
      | invoicinginvoices             | 2               | 3                |
      | invoicingtemplates            | 2               | 3                |
      | notification webhooks         | 2               | 3                |
      | billingplans                  | 2               | 2                |
      | catalog products              | 2               | 2                |
      | notification webhooklookups   | 2               | 2                |
      | shippingtrackers              | 2               | 2                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Pingdom on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/pingdom

Monitor Pingdom health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Pingdom health, cost and reliability signals, and catch incidents and runaway spend early.

[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=pingdom)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                                                       |
        | ---------------------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Merchant rule                | Alerts a responder has acknowledged in the window - the leading edge of MTTA.                                        |
        | **Alerts Firing**            | Merchant rule                | Alert events raised by Pingdom checks in the window.                                                                 |
        | **Incidents Open**           | Alert band 0 / 3             | Outage windows currently open (down or degraded) across all checks.                                                  |
        | **Incidents Resolved (24h)** | Merchant rule                | Outage windows closed in the last 24 hours - recovery throughput.                                                    |
        | **Mean Time To Acknowledge** | Alert band 300000 / 900000   | Median gap between an incident opening and a responder acknowledging it.                                             |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Median gap between an incident opening and being resolved.                                                           |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Uptime measured against the SLA target across the window.                                                            |
        | **Services Degraded**        | Alert band 0 / 2             | Checks responding slowly or intermittently but not fully down.                                                       |
        | **Services Down**            | Alert band 0 / 1             | Checks fully unreachable. When the storefront URL is down, join to a commerce sibling to price the outage in \$/min. |
        | **Services Healthy**         | Alert band 1 / 0             | Checks currently reporting an up / healthy state.                                                                    |
        | **Top Alerting Services**    | Merchant rule                | Checks that raised the most alerts in the window - the noisiest / least-stable services.                             |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour        | What it tracks                                                                         |
        | ------------------------ | ---------------------- | -------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.94 / 0.85 | Satisfied vs tolerating vs frustrated response-time buckets rolled into one 0-1 score. |
        | **Avg Response Time**    | Alert band 200 / 1500  | Average probe response time across all locations.                                      |
        | **Error Rate**           | Alert band 0.5 / 2     | Share of probe checks returning an error / down state.                                 |
        | **Throughput (req/min)** | Alert band 0 / -10     | Probe checks executed per minute across all locations.                                 |
        | **p95 Latency**          | Alert band 800 / 1500  | 95th-percentile probe response time - the slow-tail experience.                        |
        | **p99 Latency**          | Alert band 1500 / 3000 | 99th-percentile probe response time - worst-case slow checks.                          |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                                         |
        | ------------------- | --------------- | ------------------------------------------------------------------------------------------------------ |
        | **Top Error Types** | Merchant rule   | Most common probe error reasons (timeout, connection refused, status code, DNS) across failing checks. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **1 write** operations across checks, actions, credits, results, summaryaverages, summaryoutages on Pingdom. 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=pingdom)

    #### Ready to build your first Pingdom 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | checks              | 2               | 1                |
      | actions             | 1               | 0                |
      | credits             | 1               | 0                |
      | results             | 1               | 0                |
      | summaryaverages     | 1               | 0                |
      | summaryoutages      | 1               | 0                |
      | summaryperformances | 1               | 0                |
      | tmchecks            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Pinterest Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/pinterest-ads

Monitor Pinterest Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Pinterest Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/pinterest-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=pinterest-ads)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (39 signals)">
        | Signal                                              | Alert behaviour    | What it tracks                                                                                                  |
        | --------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**                                 | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **CPC by Campaign**                                 | Watch only         | CPC by Campaign.                                                                                                |
        | **CTR by Campaign**                                 | Watch only         | CTR by Campaign.                                                                                                |
        | **Campaign Comparison**                             | Watch only         | Campaign Comparison, broken down by row.                                                                        |
        | **Clicks vs Conversions**                           | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversion Actions Breakdown**                    | Watch only         | Conversion Actions Breakdown.                                                                                   |
        | **Conversion Drop Alert**                           | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversion Funnel**                               | Watch only         | Conversion Funnel, stage by stage.                                                                              |
        | **Conversion Lag**                                  | Watch only         | Conversion Lag, compared across items.                                                                          |
        | **Conversion Rate Trend**                           | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversion Rate by Campaign**                     | Watch only         | Conversion Rate by Campaign.                                                                                    |
        | **Conversion Rate by Device**                       | Watch only         | Conversion Rate by Device.                                                                                      |
        | **Conversions Trend**                               | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversions by Campaign**                         | Watch only         | Conversions by Campaign.                                                                                        |
        | **Conversions by Country**                          | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Conversions by Day of Week**                      | Watch only         | Conversions by Day of Week.                                                                                     |
        | **Conversions by Device**                           | Watch only         | Conversions by Device.                                                                                          |
        | **Conversions by Hour**                             | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Landing Page Revenue**                            | Watch only         | Landing Page Revenue, broken down by row.                                                                       |
        | **Overspending Campaigns**                          | Watch only         | Overspending Campaigns, broken down by row.                                                                     |
        | **Pinterest Tag + Conversions API Tracking Broken** | Merchant rule      | Pinterest's iOS attribution depends on Tag + CAPI dedup , broken dedup = doubled conversions = lying ROAS.      |
        | **ROAS**                                            | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                       |
        | **ROAS Dropped Below Threshold**                    | Alert band 3 / 1.5 | Pinterest's save-to-purchase lag means ROAS shifts trail by days , watch the leading indicator (save rate) too. |
        | **ROAS Trend**                                      | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **ROAS by Campaign**                                | Watch only         | ROAS by Campaign.                                                                                               |
        | **ROAS by Day of Week**                             | Watch only         | ROAS by Day of Week.                                                                                            |
        | **ROAS by Device**                                  | Watch only         | ROAS by Device.                                                                                                 |
        | **ROAS by Region**                                  | Watch only         | ROAS by Region.                                                                                                 |
        | **Revenue by Campaign**                             | Watch only         | Revenue by Campaign.                                                                                            |
        | **Search Terms Report**                             | Watch only         | Search Terms Report, broken down by row.                                                                        |
        | **Spend by Campaign**                               | Watch only         | Spend by Campaign.                                                                                              |
        | **Top Cities by Conversions**                       | Watch only         | Top Cities by Conversions.                                                                                      |
        | **Top Keywords by Conversions**                     | Watch only         | Top Keywords by Conversions.                                                                                    |
        | **Top Performing Campaigns**                        | Watch only         | Top Performing Campaigns, broken down by row.                                                                   |
        | **Total Revenue**                                   | Watch only         | Description pending editorial review; the signal is live.                                                       |
        | **Underspending Campaigns**                         | Watch only         | Underspending Campaigns, broken down by row.                                                                    |
        | **Wasted-Spend Burst (3-day spike)**                | Alert band 5 / 50  | Catches a runaway Promoted Pin before it eats the visual-brand budget.                                          |
        | **Worst Performing Campaigns**                      | Watch only         | Worst Performing Campaigns, broken down by row.                                                                 |
        | **Zero-Conversion Spend**                           | Watch only         | Description pending editorial review; the signal is live.                                                       |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                       | Alert behaviour   | What it tracks                                                                                                                                     |
        | ------------------------------------------------------------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Shopping Pins on Out-of-Stock SKUs**                | Alert band 5 / 50 | Pinterest Shopping Pins ARE the SKU , OOS Pins still serve to Pinners but can't convert. Pause and recover spend.                                  |
        | **Branded Paid Clicks Cannibalising Organic**                | Merchant rule     | Pinterest discovery overlaps Google for visual-product brand searches , branded Promoted Pins often cannibalise free organic.                      |
        | **CTR Decline Alert**                                        | Watch only        | Description pending editorial review; the signal is live.                                                                                          |
        | **Catalog Feed Rejections Hurting Verified Merchant Status** | Merchant rule     | Verified Merchant Programme status drops when rejection rate >5%. Loss of VMP = loss of Shopping Pin distribution. Highest-stakes Feedonomics card |
        | **Landing Pages with Poor Web Vitals**                       | Merchant rule     | Pinterest save-to-purchase lag means landing pages re-load weeks after save , LCP regression breaks the deferred-buyer click-through.              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **2 write** operations across adaccounts, adaccountads, adaccountcampaigns, adaccountreports, oauthtokens on Pinterest Ads. 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=pinterest-ads)

    #### Ready to build your first Pinterest Ads 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | adaccounts         | 1               | 0                |
      | adaccountads       | 1               | 0                |
      | adaccountcampaigns | 1               | 0                |
      | adaccountreports   | 0               | 1                |
      | oauthtokens        | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Pipedrive on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/pipedrive

Monitor Pipedrive pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Pipedrive 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=pipedrive)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                        | Alert behaviour     | What it tracks                                                                                                                                            |
        | ----------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule       | Estimated count of active persons/contacts in the CRM over the trailing window.                                                                           |
        | **CRM Data Hygiene Score**    | Alert band 95 / 80  | Composite of confirmed-real Pipedrive fields: share of persons with an email on file (GET /persons email\[]) and share of persons assigned an owner\_id.  |
        | **Click-to-Open Rate**        | Alert band 10 / 3   | Clicks divided by opens on outbound email to persons. Higher is better.                                                                                   |
        | **Email Click Rate**          | Alert band 2 / 0.5  | Unique clicks divided by delivered emails to persons. Higher is better.                                                                                   |
        | **Email Open Rate**           | Alert band 20 / 10  | Opens divided by delivered emails to persons. Higher is better.                                                                                           |
        | **Flow Count Summary**        | Merchant rule       | Count of active automation flows / scheduled activity sequences.                                                                                          |
        | **Flow Status Breakdown**     | Merchant rule       | Automation flows grouped by status (done vs pending activities).                                                                                          |
        | **Flow Trigger Types**        | Merchant rule       | Distribution of activity/flow trigger types (call, email, task, meeting).                                                                                 |
        | **Flows List**                | Merchant rule       | Tabular list of automation flows / activity sequences with status and counts.                                                                             |
        | **Lead Response Time**        | Alert band 60 / 480 | Median minutes from a person's add\_time to their first logged Activity (GET /activities carries person\_id + add\_time for every call/email/meeting/task |
        | **List Count**                | Merchant rule       | Number of CRM lists / saved filters (organizations grouping).                                                                                             |
        | **Lists Overview**            | Merchant rule       | Tabular overview of CRM lists with member counts and last-update times.                                                                                   |
        | **Placed Orders Total**       | Merchant rule       | Total orders placed by CRM-tracked persons. Needs an ecommerce sibling.                                                                                   |
        | **Segments Overview**         | Merchant rule       | Tabular overview of CRM segments / person filters with member counts.                                                                                     |
        | **Stalled Deal %**            | Alert band 10 / 30  | Open deals with no logged activity in 14 days, as a share of all open deals. GET /deals returns last\_activity\_date per deal (confirmed real Pipedrive   |
        | **Top Lists by Name**         | Merchant rule       | Largest CRM lists ranked by member count, labelled by name.                                                                                               |
        | **Total Sends**               | Merchant rule       | Total outbound emails sent to persons over the window.                                                                                                    |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                        |
        | ----------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule   | Distribution of campaign/deal records by status (open/won/lost).                                      |
        | **Checkout-to-Order Rate**    | Merchant rule   | Of attributed checkouts, the share that converted to a placed ecom order. Needs an ecommerce sibling. |
        | **Conversion Rate**           | Merchant rule   | Won deals divided by total deals over the window. Higher is better.                                   |
        | **Email Health KPIs**         | Merchant rule   | Rolled-up email engagement health summary across persons (sends/opens/clicks).                        |
        | **Engagement Funnel**         | Merchant rule   | Sent → delivered → opened → clicked funnel for outbound email to persons.                             |
        | **List Health Summary**       | Merchant rule   | Aggregate list-health summary across CRM lists (size, freshness, engagement).                         |
        | **Revenue per Recipient**     | Merchant rule   | Attributed revenue divided by recipients reached. Needs an ecommerce sibling.                         |
        | **Revenue per Send**          | Merchant rule   | Attributed revenue divided by emails sent. Needs an ecommerce sibling.                                |
        | **Total Revenue**             | Merchant rule   | Total won-deal value over the window - top-level CRM revenue pulse.                                   |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                  | Alert behaviour      | What it tracks                                                                |
        | ----------------------- | -------------------- | ----------------------------------------------------------------------------- |
        | **Bounce Rate**         | Alert band 2 / 5     | Share of outbound emails to persons that hard/soft bounced. Higher is worse.  |
        | **Delivery Rate**       | Alert band 98 / 95   | Share of outbound emails to persons successfully delivered. Higher is better. |
        | **Refund Rate**         | Merchant rule        | Refund rate on orders attributed to CRM persons. Needs an ecommerce sibling.  |
        | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Share of delivered emails marked as spam by recipients. Lower is better.      |
        | **Unsubscribe Rate**    | Alert band 0.5 / 2   | Share of delivered emails that resulted in an unsubscribe. Lower is better.   |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                                 |
        | --------------------- | --------------- | ------------------------------------------------------------------------------ |
        | **Checkouts Started** | Merchant rule   | Checkouts initiated by persons tracked in the CRM. Needs an ecommerce sibling. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **2 write** operations across activitys, deals, organizations, persons, stages, usermes on Pipedrive. 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=pipedrive)

    #### Ready to build your first Pipedrive 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | activitys     | 1               | 1                |
      | deals         | 1               | 1                |
      | organizations | 1               | 0                |
      | persons       | 1               | 0                |
      | stages        | 1               | 0                |
      | usermes       | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PlanetScale on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/planetscale

Monitor PlanetScale health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor PlanetScale health, cost and reliability signals, and catch incidents and runaway spend early.

[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=planetscale)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (7 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                                                              |
        | ------------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------------------- |
        | **Connection Saturation >90%** | Alert band 70 / 90 | Alerts for Connection Saturation >90%.                                                                                      |
        | **Deploy Request Open >24h**   | Merchant rule      | Alerts for Deploy Request Open >24h.                                                                                        |
        | **PlanetScale Health Score**   | Merchant rule      | Composite of query latency, usage-vs-plan burn, deploy-request hygiene and backup recency. \<70 = investigate.              |
        | **Row Reads >90% of Plan Cap** | Merchant rule      | Alerts for Row Reads >90% of Plan Cap.                                                                                      |
        | **Row Reads vs Plan Cap %**    | Merchant rule      | PlanetScale-distinctive - rows read in the billing period / plan row-read cap. >90% = overage charges or throttle imminent. |
        | **Rows Read (24h)**            | Watch only         | PlanetScale-distinctive - rows read is the primary billed metric. Reads, not queries, drive the bill.                       |
        | **Storage Usage %**            | Alert band 70 / 90 | storage\_bytes / plan storage cap from the usage surface.                                                                   |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                           | Alert behaviour    | What it tracks                                                                                                                                |
        | ------------------------------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Backup Failures (7d)**                         | Merchant rule      | Backups in state=failed in the last 7 days from the backups API.                                                                              |
        | **Connection Saturation vs Traffic Burst**       | Alert band 70 / 90 | Connection Saturation vs Traffic Burst, broken down by row.                                                                                   |
        | **Deploy Requests Stuck >24h**                   | Merchant rule      | Open deploy requests older than 24h not yet deployed to production - schema-drift / stalled-migration risk.                                   |
        | **Errored Deploy Requests (7d)**                 | Merchant rule      | Deploy requests that errored during apply - failed schema migrations needing attention.                                                       |
        | **Product Table Row Count vs Ecom Catalog Size** | Merchant rule      | PlanetScale-distinctive XC - merchants frequently keep the product / inventory master in PlanetScale; row-count drift vs ecom = sync failure. |
        | **Row-Read Spike vs Ecom Order Rate**            | Merchant rule      | PlanetScale-distinctive XC - a read storm with no order growth burns billed rows for nothing.                                                 |
        | **Slow Queries During Checkout Window**          | Merchant rule      | Slow Queries During Checkout Window, broken down by row.                                                                                      |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                               |
        | -------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
        | **Connection Saturation %**            | Alert band 70 / 90 | Open connections / branch connection cap. >90% = connection-refused errors imminent.                                         |
        | **Open Deploy Requests**               | Merchant rule      | PlanetScale-distinctive - deploy requests in 'open' state from the deploy-requests API. The Git-like schema-change workflow. |
        | **Query Error Rate %**                 | Alert band 0.1 / 1 | Share of queries returning an error at the vtgate proxy layer in the trailing 5-minute window.                               |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                                                               |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                       | Alert behaviour      | What it tracks                                                                                                                    |
        | ---------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
        | **Query Latency p95 (ms)**   | Alert band 50 / 200  | p95 query time from Insights. Insights coverage is plan-gated - see grant note.                                                   |
        | **Query Latency p99 (ms)**   | Alert band 100 / 500 | p99 query time from Insights.                                                                                                     |
        | **Slow-Query Rate %**        | Alert band 1 / 5     | Share of executions over the slow threshold from Insights query statistics.                                                       |
        | **Top Queries by Rows Read** | Watch only           | PlanetScale-distinctive - Insights query patterns ranked by rows read. Highest rows-read = highest billed cost; index candidates. |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                          |
        | -------------------------------------- | ------------------ | --------------------------------------------------------------------------------------- |
        | **Active Branches**                    | Watch only         | Count of branches from the branches API - production + dev branches.                    |
        | **Connections In Use**                 | Watch only         | Active connections to the production branch cluster (vtgate).                           |
        | **Last Successful Backup (hours ago)** | Alert band 24 / 72 | Hours since the most recent successful backup (state=success) on the production branch. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **0 write** operations across organizationdatabasbranches, organizationdatabas, organizationdatabasbranchebackups, organizationdatabasbrancheclusters, organizationdatabasbranchekeyspaces, organizationdatabasdeployrequests on PlanetScale. 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=planetscale)

    #### Ready to build your first PlanetScale 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                            | Read operations | Write operations |
      | ----------------------------------- | --------------- | ---------------- |
      | organizationdatabasbranches         | 2               | 0                |
      | organizationdatabas                 | 1               | 0                |
      | organizationdatabasbranchebackups   | 1               | 0                |
      | organizationdatabasbrancheclusters  | 1               | 0                |
      | organizationdatabasbranchekeyspaces | 1               | 0                |
      | organizationdatabasdeployrequests   | 1               | 0                |
      | organizationdatabasinsights         | 1               | 0                |
      | organizationdatabasusages           | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Plausible Analytics on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/plausible

Monitor traffic, conversion and tracking integrity from Plausible Analytics, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Plausible Analytics, and catch instrumentation breaks before decisions are made on bad data.

[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=plausible)

<CardGroup>
  <Card title="13">
    performance signals
  </Card>

  <Card title="11">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (13)">
    ### Monitor performance

    13 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (11 signals)">
        | Signal                      | Alert behaviour     | What it tracks                                                                  |
        | --------------------------- | ------------------- | ------------------------------------------------------------------------------- |
        | **Avg Session Duration**    | Alert band 120 / 30 | Average visit\_duration in seconds over the window.                             |
        | **Goal Completions**        | Merchant rule       | Total conversions across configured goals over the window.                      |
        | **New Users**               | Merchant rule       | First-time visitors (visitors filtered to visit:is\_returning=false).           |
        | **Pageviews per Session**   | Alert band 3 / 1.5  | views\_per\_visit - depth-of-visit signal.                                      |
        | **Real-Time Users**         | Merchant rule       | Current visitors on the site right now (Realtime API).                          |
        | **Returning Users**         | Merchant rule       | Returning visitors (visitors filtered to visit:is\_returning=true).             |
        | **Session Conversion Rate** | Alert band 3 / 1    | Goal conversions ÷ sessions - the headline funnel-health gauge.                 |
        | **Sessions**                | Merchant rule       | Total visits (sessions) over the window - the headline Plausible traffic pulse. |
        | **Top Pages**               | Watch only          | Top pages by pageviews (dimension event:page).                                  |
        | **Top Traffic Sources**     | Watch only          | Top referrer sources by visitors (dimension visit:source).                      |
        | **Users**                   | Merchant rule       | Unique visitors over the window.                                                |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Bounce Rate**           | Alert band 35 / 60 | Share of single-page visits. Higher is worse.                                                                                                          |
        | **Cart Abandonment Rate** | Alert band 65 / 85 | Visitors who hit a cart/checkout goal but not a purchase goal ÷ cart-goal visitors. Cross-verified against ecom abandonment when a sibling is connecte |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (11)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Goal Stopped Converting">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Goals present but never completing typically means the goal or its tracking broke, not that every visitor changed their mind on the same day.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PLA01`
      </Accordion>

      <Accordion title="Plausible Conversions but Zero Ecom Orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PLA05`
      </Accordion>

      <Accordion title="Session Conversion Rate Below Floor">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Session conversion below the floor while traffic holds means the store is buying visits it cannot convert; the cause is usually specific and findable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PLA02`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce Rate Spike">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A bounce-rate spike after a release or campaign change is the earliest cheap warning that something on the landing experience broke.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PLA03`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>

      <Accordion title="Session Volume Drop vs Prior Period">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        A sharp drop in captured events or sessions usually means a tracking break after a site change, not a real traffic collapse; decisions made on the partial data will be wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PLA04`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across querys, stataggregates, statbreakdowns, statrealtimevisitors, stattimeserys on Plausible Analytics. 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=plausible)

    #### Ready to build your first Plausible Analytics 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | querys               | 0               | 1                |
      | stataggregates       | 1               | 0                |
      | statbreakdowns       | 1               | 0                |
      | statrealtimevisitors | 1               | 0                |
      | stattimeserys        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PostgreSQL on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/postgresql

Monitor PostgreSQL health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor PostgreSQL health, cost and reliability signals, and catch incidents and runaway spend early.

[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=postgresql)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                                                       | Alert behaviour    | What it tracks                                                                                          |
        | ------------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------- |
        | **Active Streaming Replicas**                                | Watch only         | Description pending editorial review; the signal is live.                                               |
        | **Connection Pool at >90% Saturation**                       | Alert band 0 / 1   | Alerts for Connection Pool at >90% Saturation.                                                          |
        | **Connections In Use**                                       | Watch only         | Description pending editorial review; the signal is live.                                               |
        | **Database Disk Usage %**                                    | Alert band 70 / 90 | Description pending editorial review; the signal is live.                                               |
        | **Failover Readiness**                                       | Alert band 1 / 0   | Description pending editorial review; the signal is live.                                               |
        | **Instance Uptime**                                          | Watch only         | Seconds since pg\_postmaster\_start\_time(). Drop = unplanned restart.                                  |
        | **Last Successful Backup (hours ago)**                       | Alert band 24 / 72 | Last successful pg\_basebackup / WAL archive. For RDS: derived from CloudWatch backup events.           |
        | **Memory Usage %**                                           | Merchant rule      | Description pending editorial review; the signal is live.                                               |
        | **Queries per Second (live)**                                | Watch only         | Description pending editorial review; the signal is live.                                               |
        | **Replication Lag (seconds)**                                | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                               |
        | **Replication Lag Exceeds Threshold or Standby Unreachable** | Alert band 0 / 1   | Alerts for Replication Lag Exceeds Threshold or Standby Unreachable.                                    |
        | **Top Tables by Dead Tuples**                                | Watch only         | n\_dead\_tup from pg\_stat\_user\_tables. Hot table accumulating dead tuples = needs autovacuum tuning. |
      </Accordion>

      <Accordion title="Protect revenue (7 signals)">
        | Signal                                                | Alert behaviour    | What it tracks                                                                                            |
        | ----------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------- |
        | **Connection Pool Saturation %**                      | Alert band 70 / 90 | active+idle-in-tx / max\_connections. PgBouncer / pgpool pools tracked separately if present.             |
        | **Idle-in-Transaction Backends**                      | Alert band 5 / 10  | state='idle in transaction'. Stuck transactions hold locks + bloat the pool. PostgreSQL-distinctive risk. |
        | **Oldest Autovacuum Age (hours)**                     | Alert band 12 / 24 | Hottest table not vacuumed in >24h = autovacuum starved. PostgreSQL-distinctive , TXID wraparound risk.   |
        | **PgBouncer Pool Saturation vs Traffic Burst**        | Alert band 70 / 90 | PgBouncer Pool Saturation vs Traffic Burst, broken down by row.                                           |
        | **PostgreSQL Inventory Rows vs Ecom Inventory Count** | Merchant rule      | Description pending editorial review; the signal is live.                                                 |
        | **PostgreSQL QPS Spike vs Ecom Order Rate**           | Merchant rule      | Description pending editorial review; the signal is live.                                                 |
        | **Slow Queries During Checkout Window (5m)**          | Merchant rule      | Slow Queries During Checkout Window (5m), broken down by row.                                             |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                     | Alert behaviour      | What it tracks                                                                     |
        | -------------------------- | -------------------- | ---------------------------------------------------------------------------------- |
        | **Deadlocks (last 5m)**    | Alert band 0 / 5     | deadlocks column from pg\_stat\_database, delta over 5m window.                    |
        | **Query Latency p50 (ms)** | Watch only           | Description pending editorial review; the signal is live.                          |
        | **Query Latency p95 (ms)** | Alert band 50 / 200  | Description pending editorial review; the signal is live.                          |
        | **Query Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live.                          |
        | **Slow-Query Rate %**      | Alert band 1 / 5     | Queries where mean\_exec\_time > 100ms as % of total calls (pg\_stat\_statements). |
        | **Top 10 Slowest Queries** | Watch only           | Top queries by total\_exec\_time from pg\_stat\_statements.                        |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                          |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------- |
        | **Connection Errors (24h)**            | Merchant rule      | Description pending editorial review; the signal is live.                                               |
        | **PostgreSQL Health Score**            | Alert band 80 / 70 | Composite: p95 latency healthy x error-free x replication-healthy x autovacuum-current x pool-headroom. |
        | **Query Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live.                                               |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                                          |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                                                       |
        | --------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------- |
        | **Buffer Cache Hit Rate %** | Alert band 95 / 80 | blks\_hit / (blks\_hit + blks\_read) from pg\_stat\_database. \<95% on production OLTP = shared\_buffers undersized. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                                 | Alert behaviour                   | What it tracks                                                                                         |
        | -------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------ |
        | **WAL Lag Bytes (primary -> standby)** | Alert band 104857600 / 1073741824 | pg\_wal\_lsn\_diff(primary, standby) , bytes still to ship. Sustained growth = standby falling behind. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across pgsettings, pgstatactivitys, pgstatdatabases, pgstatreplications, pgstatstatements, pgstatusertables on PostgreSQL. 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=postgresql)

    #### Ready to build your first PostgreSQL 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | pgsettings         | 1               | 0                |
      | pgstatactivitys    | 1               | 0                |
      | pgstatdatabases    | 1               | 0                |
      | pgstatreplications | 1               | 0                |
      | pgstatstatements   | 1               | 0                |
      | pgstatusertables   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PostHog on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/posthog

Monitor traffic, conversion and tracking integrity from PostHog, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from PostHog, and catch instrumentation breaks before decisions are made on bad data.

[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=posthog)

<CardGroup>
  <Card title="41">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (41)">
    ### Monitor performance

    41 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (24 signals)">
        | Signal                                       | Alert behaviour | What it tracks                                                                                                                                         |
        | -------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Feature Flags**                     | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Replay Duration**                      | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Session Duration**                     | Watch only      | Avg Session Duration from PostHog, grouped under Customer Behaviour. Computes when a live PostHog integration is connected; reconciles ecommerce again |
        | **Avg Time to Convert**                      | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Biggest Funnel Step Drop-off**             | Merchant rule   | Biggest Funnel Step Drop-off, compared across items.                                                                                                   |
        | **Core Events Firing**                       | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **D30 Retention %**                          | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **D7 Retention %**                           | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Daily Active Users**                       | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **Event Volume Drop (>25% vs baseline)**     | Merchant rule   | Alerts for Event Volume Drop (>25% vs baseline).                                                                                                       |
        | **Feature Flag Rollout Status**              | Watch only      | PostHog-distinctive , per-flag rollout %. Surfaces flags stuck mid-rollout or fully on when they should be gradual.                                    |
        | **Goal Completions**                         | Watch only      | Goal Completions from PostHog, grouped under Funnel Analysis. Computes when a live PostHog integration is connected; reconciles ecommerce against Post |
        | **Monthly Active Users**                     | Watch only      | Description pending editorial review; the signal is live.                                                                                              |
        | **New vs Returning Users**                   | Watch only      | New vs Returning Users, shown by share.                                                                                                                |
        | **Pageviews per Session**                    | Watch only      | Pageviews per Session from PostHog, grouped under Customer Behaviour. Computes when a live PostHog integration is connected; reconciles ecommerce agai |
        | **Session Replay Coverage %**                | Merchant rule   | Replays captured / sessions observed. Low coverage = sampling too aggressive or capture broken.                                                        |
        | **Session Replays Captured**                 | Watch only      | PostHog-distinctive , replay count should track session count; a gap means capture is failing.                                                         |
        | **Stale Feature Flags (>90d, 100% rollout)** | Merchant rule   | Flags fully rolled out >90d ago , code-cleanup candidates; each is dead conditional logic.                                                             |
        | **Stickiness (DAU/MAU)**                     | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Top 10 Events by Volume**                  | Watch only      | Top 10 Events by Volume.                                                                                                                               |
        | **Top Pages**                                | Watch only      | Top Pages from PostHog, grouped under Customer Behaviour. Computes when a live PostHog integration is connected; reconciles ecommerce against PostHog  |
        | **Top Traffic Sources**                      | Watch only      | Top Traffic Sources from PostHog, grouped under Customer Behaviour. Computes when a live PostHog integration is connected; reconciles ecommerce agains |
        | **Top User Path**                            | Watch only      | Top User Path, broken down by row.                                                                                                                     |
        | **Total Event Volume**                       | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                                   | Alert behaviour  | What it tracks                                                                                                                                         |
        | ---------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Funnel Conversion Drop (>5pp in 24h)** | Merchant rule    | Alerts for Funnel Conversion Drop (>5pp in 24h).                                                                                                       |
        | **New Users**                            | Watch only       | New Users from PostHog, grouped under Traffic Acquisition. Computes when a live PostHog integration is connected; reconciles ecommerce against PostHog |
        | **Primary Funnel Conversion %**          | Merchant rule    | Primary Funnel Conversion %, stage by stage.                                                                                                           |
        | **Real-Time Users**                      | Watch only       | Real-Time Users from PostHog, grouped under Traffic Acquisition. Computes when a live PostHog integration is connected; reconciles ecommerce against P |
        | **Returning Users**                      | Watch only       | Returning Users from PostHog, grouped under Traffic Acquisition. Computes when a live PostHog integration is connected; reconciles ecommerce against P |
        | **Session Conversion Rate**              | Alert band 2 / 1 | Session Conversion Rate from PostHog, grouped under Funnel Analysis. Computes when a live PostHog integration is connected; reconciles ecommerce again |
        | **Sessions**                             | Watch only       | Sessions from PostHog, grouped under Traffic Acquisition. Computes when a live PostHog integration is connected; reconciles ecommerce against PostHog  |
        | **Users**                                | Watch only       | Users from PostHog, grouped under Traffic Acquisition. Computes when a live PostHog integration is connected; reconciles ecommerce against PostHog dat |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                           | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Bounce Rate**                                  | Alert band 40 / 60 | Bounce Rate from PostHog, grouped under Customer Behaviour. Computes when a live PostHog integration is connected; reconciles ecommerce against PostHo |
        | **Cart Abandonment Rate**                        | Alert band 60 / 75 | Cart Abandonment Rate from PostHog, grouped under Funnel Analysis. Computes when a live PostHog integration is connected; reconciles ecommerce against |
        | **Event Source vs Ecom Revenue Attribution**     | Merchant rule      | Event Source vs Ecom Revenue Attribution, broken down by row.                                                                                          |
        | **Landing Page Performance vs Bounce**           | Merchant rule      | Landing Page Performance vs Bounce, broken down by row.                                                                                                |
        | **PostHog Funnel Conversion vs Ecom Conversion** | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Session Quality vs Cart Abandonment**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                                | Alert behaviour | What it tracks                                                |
        | ----------------------------------------------------- | --------------- | ------------------------------------------------------------- |
        | **Event Tracking Broken (core event stopped firing)** | Merchant rule   | Alerts for Event Tracking Broken (core event stopped firing). |
        | **PostHog Tracking Health Score**                     | Merchant rule   | Description pending editorial review; the signal is live.     |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                             | Alert behaviour | What it tracks                                                                              |
        | ---------------------------------- | --------------- | ------------------------------------------------------------------------------------------- |
        | **Replays Containing Rage Clicks** | Merchant rule   | Replays flagged with rage-click events , direct queue of UX-frustration sessions to review. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across projectevents, projectfeatureflags, projectinsights, projectpersons, projectsessionrecordings on PostHog. 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=posthog)

    #### Ready to build your first PostHog 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | projectevents            | 1               | 0                |
      | projectfeatureflags      | 1               | 0                |
      | projectinsights          | 1               | 0                |
      | projectpersons           | 1               | 0                |
      | projectsessionrecordings | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PostNord on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/postnord

Monitor PostNord delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor PostNord delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=postnord)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                                       | Alert behaviour    | What it tracks                                                                                                                                    |
        | -------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Avg Shipping Cost**                        | Merchant rule      | Description pending editorial review; the signal is live.                                                                                         |
        | **Claim Value (open)**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Cost Per Shipment Trend**                  | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Cost by Zone**                             | Watch only         | Cost by Zone.                                                                                                                                     |
        | **Days to Token Expiry**                     | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Dispatch SLA Breach on N Orders Today**    | Merchant rule      | Alerts for Dispatch SLA Breach on N Orders Today.                                                                                                 |
        | **Exception Rate**                           | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                                                         |
        | **High-Cost Shipment Outliers**              | Watch only         | High-Cost Shipment Outliers, broken down by row.                                                                                                  |
        | **Label Generation Success**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Label Print Failures Spike**               | Alert band 0 / 5   | Alerts for Label Print Failures Spike.                                                                                                            |
        | **MyPack Mailbox vs Home Delivery Split**    | Watch only         | PostNord's MyPack Mailbox (fits standard Nordic letterbox) vs MyPack Home (driver hand-off) split , drives shipping cost + first-attempt success. |
        | **OTD by Route**                             | Watch only         | OTD by Route.                                                                                                                                     |
        | **Open Claims**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Pan-Nordic Cost per Parcel by Country**    | Watch only         | Cost per parcel split by destination country. PostNord's pan-Nordic contract averages across markets , see which countries subsidise others.      |
        | **Returned to Sender**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Route Volume Concentration**               | Merchant rule      | Route Volume Concentration, compared across items.                                                                                                |
        | **Shipments**                                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                         |
        | **Shipments Over Time**                      | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Shipments by Destination**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                         |
        | **Shipments by Service**                     | Watch only         | Shipments by Service.                                                                                                                             |
        | **Sunday Delivery Coverage (where offered)** | Alert band 95 / 85 | % of Sunday-delivery-eligible parcels delivered on Sunday. Coverage varies by country + postcode within PostNord network.                         |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                                     | Alert behaviour    | What it tracks                                                                                                                |
        | ------------------------------------------ | ------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**                     | Watch only         | Description pending editorial review; the signal is live.                                                                     |
        | **First-Attempt Delivery Rate**            | Watch only         | Description pending editorial review; the signal is live.                                                                     |
        | **Late Shipments**                         | Watch only         | Description pending editorial review; the signal is live.                                                                     |
        | **OTD by Nordic Country**                  | Alert band 95 / 90 | Per-country OTD across SE/NO/DK/FI. Country-specific drift signals local PostNord operational issues.                         |
        | **On-Time Delivery Rate**                  | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                     |
        | **SE-to-NO Customs Clearance Rate (\<3d)** | Merchant rule      | % of SE-to-NO parcels clearing border within 3 days. Norway is non-EU so customs paperwork applies even for Nordic-to-Nordic. |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                     | Alert behaviour   | What it tracks                                              |
        | ------------------------------------------ | ----------------- | ----------------------------------------------------------- |
        | **Failed Deliveries**                      | Merchant rule     | Description pending editorial review; the signal is live.   |
        | **Orders with Dispatch SLA Missed**        | Merchant rule     | Description pending editorial review; the signal is live.   |
        | **PostNord Cost vs Bring/DPD per Country** | Merchant rule     | PostNord Cost vs Bring/DPD per Country, broken down by row. |
        | **Return Rate by PostNord Service Code**   | Merchant rule     | Description pending editorial review; the signal is live.   |
        | **Shipments with Tracking-Event Gap**      | Alert band 0 / 10 | Shipments with Tracking-Event Gap, broken down by row.      |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                      | Alert behaviour | What it tracks                                      |
        | ------------------------------------------- | --------------- | --------------------------------------------------- |
        | **PostNord Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for PostNord Tracking API Unavailable / 5xx. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                                          | Alert behaviour | What it tracks                                                                           |
        | ----------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------- |
        | **Revenue Mix by Nordic Country (SE/NO/DK/FI)** | Watch only      | Pan-Nordic 4-country split. Shapes shipping economics + per-country marketing decisions. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **2 write** operations across restapishipmentshipments, restapishipmentreturns, restapishipmenttracks on PostNord. 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=postnord)

    #### Ready to build your first PostNord 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | restapishipmentshipments | 1               | 1                |
      | restapishipmentreturns   | 0               | 1                |
      | restapishipmenttracks    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PrestaShop on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/prestashop

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to PrestaShop.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to PrestaShop.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/prestashop) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=prestashop)

<CardGroup>
  <Card title="47">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (47)">
    ### Monitor performance

    47 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (19 signals)">
        | Signal                                        | Alert behaviour    | What it tracks                                                                                                             |
        | --------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
        | **Active Ads on Out-of-Stock SKUs**           | Merchant rule      | Active Ads on Out-of-Stock SKUs, broken down by row.                                                                       |
        | **Cancellation Rate**                         | Alert band 1 / 3   | Description pending editorial review; the signal is live.                                                                  |
        | **Churn-Risk (Inactive) Customers**           | Alert band 20 / 50 | Customers with no order/visit in 90d - last\_visit + orders recency.                                                       |
        | **Combination (Variant) Stock at Zero**       | Merchant rule      | id\_product\_attribute>0 rows at quantity\<=0 while the parent product is active - silent variant stockouts.               |
        | **High-Value Customers Unengaged on Email**   | Merchant rule      | High-Value Customers Unengaged on Email, broken down by row.                                                               |
        | **Low-Stock Products**                        | Merchant rule      | Description pending editorial review; the signal is live.                                                                  |
        | **Order Status Mix**                          | Watch only         | Awaiting payment / processing / shipped / delivered / refunded / cancelled distribution via current\_state → order\_state. |
        | **Orders → Email Campaign Attribution**       | Merchant rule      | Orders → Email Campaign Attribution, broken down by row.                                                                   |
        | **Out-of-Stock Products**                     | Alert band 0 / 5   | stock\_available.quantity\<=0 on active products still visible on storefront.                                              |
        | **Pagespeed-Driven Cart Loss**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                  |
        | **Partial vs Full Refund Mix**                | Watch only         | Split of partial vs full refunds from order\_slip amounts.                                                                 |
        | **Per-Shop Health Matrix**                    | Watch only         | Revenue / refund-rate / OOS / repeat-rate per shop in one matrix.                                                          |
        | **PrestaShop vs Marketplace Catalogue Drift** | Merchant rule      | PrestaShop vs Marketplace Catalogue Drift, broken down by row.                                                             |
        | **Products Missing SEO Meta**                 | Alert band 10 / 30 | Empty meta\_title / meta\_description - organic-traffic leak.                                                              |
        | **Products with Stock Tracking Disabled**     | Merchant rule      | out\_of\_stock=1 (allow ordering when empty) with depends\_on\_stock=false - no real tracking.                             |
        | **Refund Rate**                               | Alert band 2 / 5   | Refunded orders (REFUNDED order\_state / order\_slip) as % of orders.                                                      |
        | **Refund-Rate Spike**                         | Merchant rule      | Alerts for Refund-Rate Spike.                                                                                              |
        | **Refunded Order Count**                      | Merchant rule      | Description pending editorial review; the signal is live.                                                                  |
        | **Revenue at Risk**                           | Merchant rule      | Estimated revenue exposed by OOS bestsellers, stuck payments, and refund spikes.                                           |
      </Accordion>

      <Accordion title="Grow revenue (13 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------- |
        | **Awaiting Payment Orders**      | Merchant rule      | Orders stuck in an awaiting-payment order\_state >24h usually = gateway issue or customer dropoff.            |
        | **Discount Dependency**          | Alert band 20 / 40 | total\_discounts as % of revenue - promo-dependency / margin-erosion signal.                                  |
        | **New vs Returning Customers**   | Watch only         | First-order vs repeat-order customers derived from orders per id\_customer.                                   |
        | **Order Status Spike**           | Merchant rule      | Description pending editorial review; the signal is live.                                                     |
        | **Products Missing Description** | Alert band 5 / 20  | Empty description / description\_short - free conversion + SEO lift.                                          |
        | **Repeat Purchase Rate**         | Alert band 25 / 10 | Description pending editorial review; the signal is live.                                                     |
        | **Revenue Trend**                | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **Revenue by Currency**          | Watch only         | Split by id\_currency join to currencies resource - multi-currency shops.                                     |
        | **Revenue by Shop (Multistore)** | Watch only         | Per-shop revenue split via id\_shop for merchants running multiple PrestaShop shops on one back office.       |
        | **Shipping as % of Revenue**     | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                     |
        | **Top Products by Revenue**      | Watch only         | Aggregated from order\_detail total\_price\_tax\_incl by product.                                             |
        | **Total Revenue**                | Alert band 0 / -5  | Sum of valid orders' total\_paid, currency-aware across multi-currency shops.                                 |
        | **VAT / Tax Collected**          | Watch only         | total\_paid\_tax\_incl minus total\_paid\_tax\_excl, aggregated - useful for cross-EU OSS threshold tracking. |
      </Accordion>

      <Accordion title="Run operations (11 signals)">
        | Signal                                  | Alert behaviour    | What it tracks                                                                                        |
        | --------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------- |
        | **AOV by Country**                      | Watch only         | AOV by Country.                                                                                       |
        | **Average Order Value**                 | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                             |
        | **Fulfillment Rate**                    | Alert band 95 / 90 | Paid orders whose order\_states.shipped flag is true, over all paid orders in the window.             |
        | **OOS Bestseller Still Visible**        | Merchant rule      | Alerts for OOS Bestseller Still Visible.                                                              |
        | **Order Count**                         | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                             |
        | **Order Processing Backlog**            | Alert band 10 / 50 | Alerts for Order Processing Backlog.                                                                  |
        | **Order Volume by Shop**                | Watch only         | Order Volume by Shop.                                                                                 |
        | **Orders by Country**                   | Watch only         | Order delivery country from the addresses resource.                                                   |
        | **PrestaShop Webservice Failure Spike** | Merchant rule      | Webservice key revoked, resource permission removed, or store unreachable (Hosted Cloud maintenance). |
        | **Top Customers by Spend**              | Watch only         | Top Customers by Spend.                                                                               |
        | **Total Customers**                     | Watch only         | Description pending editorial review; the signal is live.                                             |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                       | Alert behaviour   | What it tracks                                               |
        | ---------------------------- | ----------------- | ------------------------------------------------------------ |
        | **Disabled Products**        | Watch only        | active=false products - hidden from storefront.              |
        | **Products Missing EAN/UPC** | Merchant rule     | Missing ean13 blocks Google Shopping + marketplace listings. |
        | **Products Missing Image**   | Alert band 5 / 20 | Description pending editorial review; the signal is live.    |
        | **Total Products**           | Watch only        | Description pending editorial review; the signal is live.    |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **10 read** and **0 write** operations across address, currencys, customers, orders, order details, order slips on PrestaShop. 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=prestashop)

    #### Ready to build your first PrestaShop 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | address       | 1               | 0                |
      | currencys     | 1               | 0                |
      | customers     | 1               | 0                |
      | orders        | 1               | 0                |
      | order details | 1               | 0                |
      | order slips   | 1               | 0                |
      | order states  | 1               | 0                |
      | products      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Prismic on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/prismic

Monitor Prismic publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Prismic publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=prismic)

<CardGroup>
  <Card title="16">
    performance signals
  </Card>

  <Card title="2">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="3">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (16)">
    ### Monitor performance

    16 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (9 signals)">
        | Signal                          | Alert behaviour        | What it tracks                                                                                |
        | ------------------------------- | ---------------------- | --------------------------------------------------------------------------------------------- |
        | **Accessibility Score**         | Alert band 90 / 70     | Lighthouse Accessibility category score.                                                      |
        | **CLS (Mobile)**                | Alert band 0.1 / 0.25  | Cumulative Layout Shift, 75th percentile, mobile - slice changes are the usual culprit.       |
        | **CWV Pass Rate (Mobile)**      | Alert band 75 / 50     | % of rendered front-end origin visits passing all three Core Web Vitals (CrUX field, mobile). |
        | **INP (Mobile)**                | Alert band 200 / 500   | Interaction to Next Paint, 75th percentile, mobile field data.                                |
        | **LCP (Mobile)**                | Alert band 2500 / 4000 | Largest Contentful Paint, 75th percentile, mobile field data.                                 |
        | **Performance Score (Desktop)** | Alert band 90 / 50     | Lighthouse lab Performance score, desktop strategy.                                           |
        | **Performance Score (Mobile)**  | Alert band 90 / 50     | Lighthouse lab Performance score, mobile strategy.                                            |
        | **Speed Index**                 | Alert band 3400 / 5800 | How quickly content is visually populated (Lighthouse Speed Index).                           |
        | **TTFB (Mobile)**               | Alert band 800 / 1800  | Time to First Byte, 75th percentile, mobile field data.                                       |
      </Accordion>

      <Accordion title="Catalogue quality (5 signals)">
        | Signal                        | Alert behaviour              | What it tracks                                                                                             |
        | ----------------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------------------- |
        | **Best Practices Score**      | Alert band 90 / 70           | Lighthouse Best Practices category score.                                                                  |
        | **Render-Blocking Resources** | Alert band 200 / 500         | Estimated ms savings from eliminating render-blocking JS/CSS (Lighthouse render-blocking-resources audit). |
        | **Stale Content**             | Alert band 10 / 40           | % of published documents (sampled, up to 500) not updated in the last 12 months.                           |
        | **Total Blocking Time**       | Alert band 200 / 600         | Total time the main thread was blocked (Lighthouse TBT).                                                   |
        | **Total Page Weight**         | Alert band 1572864 / 3145728 | Total transferred byte weight of the rendered page (Lighthouse total-byte-weight audit).                   |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                 | Alert behaviour    | What it tracks                                                       |
        | ---------------------- | ------------------ | -------------------------------------------------------------------- |
        | **Publishing Cadence** | Alert band 4 / 1   | Documents first-published across the repository in the last 30 days. |
        | **SEO Score**          | Alert band 90 / 70 | Lighthouse SEO category score for the rendered front-end.            |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (2)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Over 40% of content not updated in 12 months">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When over 40 percent of content has not been touched in a year, decay outpaces creation; rankings quietly rot page by page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-STALE-001`
      </Accordion>

      <Accordion title="Publishing pipeline stalled (no post in 30 days)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A stalled publishing pipeline slowly starves organic traffic; content compounds only while it keeps shipping.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CMS-PUBLISH-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **0 write** operations across documentsearchs, pagespeedonlinerunpagespeeds, resources on Prismic. 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=prismic)

    #### Ready to build your first Prismic 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | documentsearchs              | 1               | 0                |
      | pagespeedonlinerunpagespeeds | 1               | 0                |
      | resources                    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Prometheus on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/prometheus

Monitor Prometheus health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Prometheus health, cost and reliability signals, and catch incidents and runaway spend early.

[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=prometheus)

<CardGroup>
  <Card title="19">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="12">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (19)">
    ### Monitor performance

    19 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (8 signals)">
        | Signal                       | Alert behaviour        | What it tracks                                                                                |
        | ---------------------------- | ---------------------- | --------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Watch only             | Firing alerts matched by an active Alertmanager silence - the ack proxy.                      |
        | **Incidents Resolved (24h)** | Watch only             | Alert groups that transitioned firing→inactive in the last 24h, evaluated from ALERTS series. |
        | **Mean Time To Acknowledge** | Merchant rule          | Mean gap between alert activeAt and first matching silence/ack - needs stored alert history.  |
        | **Mean Time To Resolve**     | Merchant rule          | Mean gap between alert activeAt and firing→inactive transition - needs stored alert history.  |
        | **SLA Compliance**           | Alert band 99.9 / 99.5 | avg\_over\_time(up\[30d]) - uptime ratio expressed as an SLA percentage.                      |
        | **Services Down**            | Alert band 0 / 1       | count(up == 0) by (job) - targets Prometheus can't scrape.                                    |
        | **Services Healthy**         | Watch only             | count(up == 1) by (job) - targets reporting up across the window.                             |
        | **Top Alerting Services**    | Watch only             | Services ranked by firing-alert count - count by (service) over ALERTS.                       |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour       | What it tracks                                                                                |
        | ------------------------ | --------------------- | --------------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.95 / 0.7 | histogram\_quantile-derived satisfaction score from http\_request\_duration\_seconds\_bucket. |
        | **Avg Response Time**    | Alert band 200 / 1000 | rate(http\_request\_duration\_seconds\_sum) / rate(\_count) over the window.                  |
        | **Error Rate**           | Alert band 0.5 / 2    | rate(http\_requests\_total) / rate(http\_requests\_total).                                    |
        | **Throughput (req/min)** | Alert band 0 / -10    | sum(rate(http\_requests\_total\[5m])) × 60 - request volume per minute.                       |
        | **p95 Latency**          | Alert band 200 / 1000 | histogram\_quantile(0.95, sum(rate(http\_request\_duration\_seconds\_bucket\[5m])) by (le)).  |
        | **p99 Latency**          | Alert band 200 / 1000 | histogram\_quantile(0.99, ...) - the tail customers feel worst.                               |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                | Alert behaviour  | What it tracks                                                                              |
        | --------------------- | ---------------- | ------------------------------------------------------------------------------------------- |
        | **Alerts Firing**     | Alert band 0 / 3 | Count of alerts in state=firing from /api/v2/alerts.                                        |
        | **Incidents Open**    | Alert band 0 / 3 | Active (non-suppressed) alert groups from /api/v2/alerts/groups - one group = one incident. |
        | **Services Degraded** | Merchant rule    | Services breaching p95/error-rate SLO but still up - derived from rules eval + query.       |
        | **Top Error Types**   | Watch only       | Alertnames ranked by occurrence - count by (alertname) over ALERTS.                         |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                              | Alert behaviour | What it tracks                                                                                                                        |
        | ----------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
        | **Revenue at Risk (firing alerts)** | Merchant rule   | Live \$/min loss while critical/warning alerts overlap a commerce sibling's traffic window. Prometheus state becomes a dollar figure. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **10 read** and **2 write** operations across silences, alerts, alertgroups, querys, queryranges, rules on Prometheus. 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=prometheus)

    #### Ready to build your first Prometheus 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | silences         | 1               | 2                |
      | alerts           | 2               | 0                |
      | alertgroups      | 1               | 0                |
      | querys           | 1               | 0                |
      | queryranges      | 1               | 0                |
      | rules            | 1               | 0                |
      | series           | 1               | 0                |
      | statusbuildinfos | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Pushover on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/pushover

Monitor Pushover performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Pushover performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=pushover)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Pushover yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **2 write** operations across applimitjsons, message jsons, receipts, receiptcanceljsons, soundjsons, uservalidatejsons on Pushover. 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=pushover)

    #### Ready to build your first Pushover 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.

    <Accordion title="Browse the operations you can build with">
      | Resource           | Read operations | Write operations |
      | ------------------ | --------------- | ---------------- |
      | applimitjsons      | 1               | 0                |
      | message jsons      | 0               | 1                |
      | receipts           | 1               | 0                |
      | receiptcanceljsons | 0               | 1                |
      | soundjsons         | 1               | 0                |
      | uservalidatejsons  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# QuickBooks (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/quickbooks-api

Monitor QuickBooks (API) payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor QuickBooks (API) payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=quickbooks-api)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (7 signals)">
        | Signal                                        | Alert behaviour    | What it tracks                                                                                                                                         |
        | --------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AP Aging - 60+ Days**                       | Alert band 10 / 30 | Share of total AP in the 60+ buckets of the Aged Payables report.                                                                                      |
        | **AR Balance (live)**                         | Watch only         | Total outstanding customer balances from the Aged Receivables report.                                                                                  |
        | **Cash & Bank Balance**                       | Watch only         | Sum of CurrentBalance across Bank-classified accounts (AccountType = Bank).                                                                            |
        | **Invoices Past Due (open AR > terms)**       | Merchant rule      | Open invoices (Balance > 0) past their DueDate, ordered by days overdue x balance.                                                                     |
        | **Period Close Overdue**                      | Alert band 0 / 5   | Preferences.AccountingInfoPrefs.BookCloseDate vs the oldest calendar month it hasn't yet covered - days the books have gone unclosed past that month's |
        | **QuickBooks Health Score**                   | Merchant rule      | Composite: AR-aging-low x order-invoice-reconciled x cash-positive x close-on-track.                                                                   |
        | **Unreconciled Ecom Orders (no QBO invoice)** | Merchant rule      | Alerts for Unreconciled Ecom Orders (no QBO invoice).                                                                                                  |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                               | Alert behaviour         | What it tracks                                                                                                                   |
        | ---------------------------------------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
        | **AR 60+ Days on Customers with Active Ecom Orders** | Alert band 1000 / 10000 | Customers tipping past 60 days on AR while still ordering - credit risk compounding. Hold or pre-pay before next fulfilment.     |
        | **AR Aging - 60+ Days**                              | Alert band 5 / 15       | Share of total AR sitting in the 61-90 + 91+ buckets of the Aged Receivables report. Collections risk.                           |
        | **Ecom Customers Absent from QBO Customer Master**   | Alert band 0 / 10       | Sync-app gap - repeat ecom buyers invisible to the QBO customer master breaks invoicing, sales-tax and customer-level reporting. |
        | **Ecom Orders Missing Matching QBO Invoice**         | Merchant rule           | Sync-app gap (A2X / Webgility / native connector) - revenue invisible to the books + sales-tax/VAT base understated.             |
        | **SKUs with QBO-vs-Ecom Inventory Drift >5%**        | Alert band 1 / 5        | QBO Plus inventory tracking required - card hides on Simple Start / Essentials plans that don't track quantity on hand.          |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                  |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------- |
        | **Days Sales Outstanding (DSO)** | Alert band 30 / 60 | AR balance / (P\&L revenue / period days). Collections velocity.                |
        | **Net Income (month to date)**   | Watch only         | Net income row from the Profit and Loss report for the current period vs prior. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across companycompanyinfos, companypreferences, companyquerys, companyreportagedpayables, companyreportagedreceivables, companyreportprofitandloss on QuickBooks (API). 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=quickbooks-api)

    #### Ready to build your first QuickBooks (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | companycompanyinfos          | 1               | 0                |
      | companypreferences           | 1               | 0                |
      | companyquerys                | 1               | 0                |
      | companyreportagedpayables    | 1               | 0                |
      | companyreportagedreceivables | 1               | 0                |
      | companyreportprofitandloss   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Quora Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/quora-ads

Monitor Quora Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Quora Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/quora-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=quora-ads)

<CardGroup>
  <Card title="75">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (75)">
    ### Monitor performance

    75 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (40 signals)">
        | Signal                                          | Alert behaviour      | What it tracks                                                                                       |
        | ----------------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------- |
        | **All Conversions**                             | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **CPC by Campaign**                             | Watch only           | CPC by Campaign.                                                                                     |
        | **CTR by Campaign**                             | Watch only           | CTR by Campaign.                                                                                     |
        | **Campaign Comparison**                         | Watch only           | Campaign Comparison, broken down by row.                                                             |
        | **Clicks vs Conversions**                       | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Conversion Actions Breakdown**                | Watch only           | Conversion Actions Breakdown.                                                                        |
        | **Conversion Drop Alert**                       | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Conversion Funnel**                           | Watch only           | Conversion Funnel, stage by stage.                                                                   |
        | **Conversion Lag**                              | Watch only           | Conversion Lag, compared across items.                                                               |
        | **Conversion Rate Trend**                       | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Conversion Rate by Campaign**                 | Watch only           | Conversion Rate by Campaign.                                                                         |
        | **Conversion Rate by Device**                   | Watch only           | Conversion Rate by Device.                                                                           |
        | **Conversions Trend**                           | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Conversions by Campaign**                     | Watch only           | Conversions by Campaign.                                                                             |
        | **Conversions by Country**                      | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Conversions by Day of Week**                  | Watch only           | Conversions by Day of Week.                                                                          |
        | **Conversions by Device**                       | Watch only           | Conversions by Device.                                                                               |
        | **Conversions by Hour**                         | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Cost per Acquisition**                        | Alert band 15 / 40   | Description pending editorial review; the signal is live.                                            |
        | **Cost-per-MQL Spiked Above Threshold**         | Alert band 100 / 300 | B2B equivalent of ROAS-drop , Quora's long cycle means use 30D rolling baseline not 7D same-DOW.     |
        | **Landing Page Revenue**                        | Watch only           | Landing Page Revenue, broken down by row.                                                            |
        | **Overspending Campaigns**                      | Watch only           | Overspending Campaigns, broken down by row.                                                          |
        | **Quora Pixel + Lead Gen Form Tracking Broken** | Merchant rule        | Long-cycle attribution requires solid Pixel + CRM sync. Either fails = MQL pipeline silently broken. |
        | **ROAS**                                        | Alert band 3 / 1.5   | Description pending editorial review; the signal is live.                                            |
        | **ROAS Trend**                                  | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **ROAS by Campaign**                            | Watch only           | ROAS by Campaign.                                                                                    |
        | **ROAS by Day of Week**                         | Watch only           | ROAS by Day of Week.                                                                                 |
        | **ROAS by Device**                              | Watch only           | ROAS by Device.                                                                                      |
        | **ROAS by Region**                              | Watch only           | ROAS by Region.                                                                                      |
        | **Revenue by Campaign**                         | Watch only           | Revenue by Campaign.                                                                                 |
        | **Search Terms Report**                         | Watch only           | Search Terms Report, broken down by row.                                                             |
        | **Spend by Campaign**                           | Watch only           | Spend by Campaign.                                                                                   |
        | **Top Cities by Conversions**                   | Watch only           | Top Cities by Conversions.                                                                           |
        | **Top Keywords by Conversions**                 | Watch only           | Top Keywords by Conversions.                                                                         |
        | **Top Performing Campaigns**                    | Watch only           | Top Performing Campaigns, broken down by row.                                                        |
        | **Total Conversions**                           | Merchant rule        | Description pending editorial review; the signal is live.                                            |
        | **Total Revenue**                               | Watch only           | Description pending editorial review; the signal is live.                                            |
        | **Underspending Campaigns**                     | Watch only           | Underspending Campaigns, broken down by row.                                                         |
        | **Worst Performing Campaigns**                  | Watch only           | Worst Performing Campaigns, broken down by row.                                                      |
        | **Zero-Conversion Spend**                       | Watch only           | Description pending editorial review; the signal is live.                                            |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Clicks**               | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                               | Alert behaviour   | What it tracks                                                                                                                          |
        | ---------------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Campaigns on Out-of-Stock SKUs (B2B rare)** | Alert band 5 / 50 | Rare on Quora (mostly B2B SaaS), but B2B-commerce hybrid campaigns can still hit OOS SKUs. only\_when hides when no commerce sibling.   |
        | **Branded Paid Clicks Cannibalising Organic Search** | Merchant rule     | B2B searchers active on Quora often also search the brand on Google , branded-topic targeting cannibalises free organic.                |
        | **CTR Decline Alert**                                | Watch only        | Description pending editorial review; the signal is live.                                                                               |
        | **Landing Pages with Poor Web Vitals**               | Merchant rule     | Quora's long consideration cycle means leads return to landing pages weeks later , LCP regressions kill the dormant-buyer reactivation. |
        | **Spend on Campaigns with Active Feed Rejections**   | Merchant rule     | £ on campaign whose linked product feed has Feedonomics rejections.                                                                     |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                                              | Alert behaviour   | What it tracks                                                                                                                          |
        | --------------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **Wasted-Spend Burst (algo topic-expansion drift)** | Alert band 5 / 50 | Quora's algo can expand question-topic targeting to broader categories silently , catches the drift before it eats the B2B-tier budget. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Zero-conversion spend detected (B2B pipeline leak)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Keywords that spend without ever converting are the purest form of wasted budget, and the list is exact: these terms, this spend, zero return.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `QRA-WASTE-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Cost-per-lead above B2B threshold">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Cost-per-lead above the sector threshold means the funnel is paying too much for pipeline; targeting, creative or landing alignment needs work.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `QRA-MQL-001`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **0 write** operations across adaccounts, adaccountreportperformances, adcampaigns, admes on Quora Ads. 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=quora-ads)

    #### Ready to build your first Quora Ads 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | adaccounts                  | 1               | 0                |
      | adaccountreportperformances | 1               | 0                |
      | adcampaigns                 | 1               | 0                |
      | admes                       | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Razorpay on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/razorpay

Monitor Razorpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Razorpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=razorpay)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (8 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                        |
        | ----------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                  | Alert band 15 / 30   | Customers who saw the 3DS / OTP challenge and bailed. High abandon = checkout friction.                               |
        | **Chargeback Rate**                       | Alert band 0.5 / 0.9 | Disputes that reached chargeback / total payments. Above \~0.9% risks network monitoring programmes.                  |
        | **Decline Rate**                          | Alert band 5 / 8     | Description pending editorial review; the signal is live.                                                             |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When Razorpay declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss. |
        | **Dispute Rate**                          | Alert band 0.5 / 1   | Description pending editorial review; the signal is live.                                                             |
        | **Refund Rate**                           | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                             |
        | **Refund Volume**                         | Merchant rule        | Description pending editorial review; the signal is live.                                                             |
        | **Top Decline Reasons**                   | Watch only           | Razorpay error\_reason coded (insufficient\_funds, payment\_failed, gateway\_error) - each has a different fix.       |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                      |
        | -------------------------------- | ------------------ | ----------------------------------------------------------------------------------- |
        | **Average Transaction**          | Watch only         | Description pending editorial review; the signal is live.                           |
        | **Avg Settlement Time (days)**   | Alert band 2 / 5   | Capture-to-payout lag in days. Razorpay default is T+2 / T+3.                       |
        | **Oldest Pending Payout (days)** | Alert band 2 / 5   | Description pending editorial review; the signal is live.                           |
        | **Pending Payouts**              | Merchant rule      | Captured value not yet settled to the merchant bank.                                |
        | **Success Rate**                 | Alert band 95 / 90 | Captured / total attempts. The headline payments-health number.                     |
        | **Top Payment Methods**          | Watch only         | UPI vs card vs net-banking vs wallet vs EMI mix - watch for rail-specific breakage. |
        | **Total Transactions**           | Watch only         | Description pending editorial review; the signal is live.                           |
        | **Total Volume**                 | Merchant rule      | Gross payment value captured over the window.                                       |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                     |
        | -------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Captured vs Commerce Revenue** | Merchant rule      | Reconciliation gap between what Razorpay captured and what the commerce sibling booked as revenue. |
        | **Volume Trend**                 | Alert band 0 / -15 | Captured volume over time - spot weekly cadence and dips.                                          |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **2 write** operations across payments, refunds, disputes, disputecontests, payment refunds, settlements on Razorpay. 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=razorpay)

    #### Ready to build your first Razorpay 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | payments                 | 2               | 0                |
      | refunds                  | 2               | 0                |
      | disputes                 | 1               | 0                |
      | disputecontests          | 0               | 1                |
      | payment refunds          | 0               | 1                |
      | settlements              | 1               | 0                |
      | settlementreconcombineds | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Reddit on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/reddit

Monitor Reddit publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Reddit publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=reddit)

<CardGroup>
  <Card title="16">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (16)">
    ### Monitor performance

    16 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (14 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                                                                            |
        | --------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Session Duration**    | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **Engagement Rate**         | Alert band 3 / 1   | Avg per-post (score + comments) / subreddit subscribers x 100, across posts submitted in the last 30d.                                    |
        | **Goal Completions**        | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **New Users**               | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **Pageviews per Session**   | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **Posting Cadence**         | Alert band 0 / -40 | Count of posts submitted in the last 30d vs the prior 30d.                                                                                |
        | **Real-Time Users**         | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **Returning Users**         | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **Session Conversion Rate** | Alert band 2 / 1   | Description pending editorial review; the signal is live.                                                                                 |
        | **Sessions**                | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
        | **Social Health Score**     | Alert band 90 / 70 | Composite 0-100: engagement rate (50%) x posting cadence (30%) x days-since-last-post (20%), from the account's last 100 submitted posts. |
        | **Top Pages**               | Alert band 0 / -20 | Top Pages, compared across items.                                                                                                         |
        | **Top Traffic Sources**     | Alert band 0 / -20 | Top Traffic Sources, compared across items.                                                                                               |
        | **Users**                   | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                                                                 |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                            |
        | ------------------------- | ------------------ | --------------------------------------------------------- |
        | **Bounce Rate**           | Alert band 40 / 60 | Description pending editorial review; the signal is live. |
        | **Cart Abandonment Rate** | Alert band 60 / 75 | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Engagement rate below 1%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Engagement below 1 percent means content is reaching feeds and being scrolled past; format and hook need work before spend goes behind it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-ENGAGEMENT-001`
      </Accordion>

      <Accordion title="Reach dropped > 20% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Reach dropping over 20 percent usually means the algorithm has deprioritised the account or a format change landed badly; catching it early keeps the slide shallow.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-REACH-001`
      </Accordion>

      <Accordion title="Posting cadence collapsed (no post in 14 days)">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Posting cadence collapsing to zero lets the audience's attention lapse; reach compounds only while the account stays present.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-CADENCE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **0 write** operations across analyticsreddittraffics, mes, userabouts, usersubmitteds on Reddit. 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=reddit)

    #### Ready to build your first Reddit 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                | Read operations | Write operations |
      | ----------------------- | --------------- | ---------------- |
      | analyticsreddittraffics | 1               | 0                |
      | mes                     | 1               | 0                |
      | userabouts              | 1               | 0                |
      | usersubmitteds          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Redis on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/redis

Monitor Redis health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Redis health, cost and reliability signals, and catch incidents and runaway spend early.

[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=redis)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (21 signals)">
        | Signal                                                 | Alert behaviour          | What it tracks                                                                                               |
        | ------------------------------------------------------ | ------------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Blocked Clients (BLPOP / BRPOP / WAIT)**             | Alert band 20 / 100      | Clients waiting on blocking commands , queue-consumer + pub/sub stacks live here.                            |
        | **Clients vs maxclients %**                            | Alert band 70 / 90       | connected\_clients / maxclients. Hitting cap rejects new connections , drops downstream services.            |
        | **Cluster Slot Coverage Gap (\<16384 slots assigned)** | Merchant rule            | Redis-distinctive , slot coverage gap = some keys unreachable, commands on those slots fail.                 |
        | **Cluster Slots Assigned (of 16384)**                  | Alert band 16384 / 16383 | cluster\_slots\_ok from CLUSTER INFO. \<16384 = some keys unreachable (operations on those slots fail).      |
        | **Connected Clients**                                  | Watch only               | Description pending editorial review; the signal is live.                                                    |
        | **Connected Replicas**                                 | Alert band 1 / 0         | connected\_slaves from INFO replication.                                                                     |
        | **Connections Rejected Due to maxclients**             | Alert band 70 / 90       | Alerts for Connections Rejected Due to maxclients.                                                           |
        | **Evicted Keys / minute**                              | Merchant rule            | evicted\_keys delta , Redis at maxmemory dropping keys per maxmemory-policy. Indicates memory pressure.      |
        | **Eviction Storm (>1k evicted\_keys/min sustained)**   | Merchant rule            | Alerts for Eviction Storm (>1k evicted\_keys/min sustained).                                                 |
        | **Expired Keys / minute**                              | Watch only               | Expired Keys / minute over time.                                                                             |
        | **Instance Uptime**                                    | Watch only               | Description pending editorial review; the signal is live.                                                    |
        | **Keyspace Hit Rate %**                                | Alert band 95 / 80       | keyspace\_hits / (keyspace\_hits + keyspace\_misses) from INFO stats. The Redis-defining metric.             |
        | **Last AOF Rewrite Status**                            | Alert band 1 / 0         | aof\_last\_bgrewrite\_status from INFO persistence (ok \| err).                                              |
        | **Last RDB Save (minutes ago)**                        | Alert band 30 / 60       | rdb\_last\_save\_time from INFO persistence.                                                                 |
        | **Last Successful Backup (hours ago)**                 | Alert band 24 / 72       | Last successful RDB / AOF backup shipped offsite. For ElastiCache: CloudWatch backup events.                 |
        | **Memory Fragmentation Ratio**                         | Merchant rule            | mem\_fragmentation\_ratio = used\_memory\_rss / used\_memory. >1.5 = OS waste; \<1 = swap in progress (BAD). |
        | **Memory Used vs Maxmemory %**                         | Alert band 70 / 90       | used\_memory / maxmemory , Redis treats memory as 'disk'. Approaching maxmemory triggers eviction.           |
        | **Operations per Second (live)**                       | Watch only               | instantaneous\_ops\_per\_sec from INFO stats. Redis-distinctive , proxy for command throughput.              |
        | **Redis Health Score**                                 | Alert band 80 / 70       | Description pending editorial review; the signal is live.                                                    |
        | **Replica Lag (seconds)**                              | Alert band 1 / 10        | master\_last\_io\_seconds\_ago from INFO replication on each replica.                                        |
        | **Total Keys (db0)**                                   | Watch only               | From INFO keyspace db0:keys=.                                                                                |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                       | Alert behaviour      | What it tracks                                                                                                                                            |
        | ---------------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Command Latency p50 (us)** | Watch only           | From LATENCY HISTORY (Redis 7+) or sampling client-side.                                                                                                  |
        | **Command Latency p95 (ms)** | Alert band 50 / 200  | Redis commands typically sub-ms; p95 >10ms = something pathological (large key, slow Lua script, swap).                                                   |
        | **Command Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                                 |
        | **SLOWLOG Entries (15m)**    | Alert band 2 / 10    | Commands exceeding slowlog-log-slower-than threshold (default 10ms).                                                                                      |
        | **Slow-Query Rate %**        | Alert band 1 / 5     | SLOWLOG entry count in the trailing 15m divided by an estimated command count for that same window (INFO stats instantaneous\_ops\_per\_sec x 900s - Redi |
        | **Top 10 SLOWLOG Commands**  | Watch only           | Top 10 SLOWLOG Commands, broken down by row.                                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                  |
        | ------------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------- |
        | **Connected Clients Saturation vs Traffic Burst** | Alert band 70 / 90 | Connected Clients Saturation vs Traffic Burst, broken down by row.                              |
        | **Redis OPS Spike vs Ecom Order Rate**            | Merchant rule      | Description pending editorial review; the signal is live.                                       |
        | **Redis Session Keys vs Active Ecom Users**       | Merchant rule      | Redis-distinctive: when Redis holds sessions, session-key count should track active ecom users. |
        | **Slow Commands During Checkout Window (5m)**     | Merchant rule      | Slow Commands During Checkout Window (5m), broken down by row.                                  |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                 |
        | ------------------------------ | ------------------ | ------------------------------------------------------------------------------ |
        | **Rejected Connections (24h)** | Alert band 0.1 / 1 | rejected\_connections from INFO stats , clients refused due to maxclients hit. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **0 write** operations across cluster infos, cluster nodes, info clients, info memorys, info persistences, info replications on Redis. 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=redis)

    #### Ready to build your first Redis 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | cluster infos     | 1               | 0                |
      | cluster nodes     | 1               | 0                |
      | info clients      | 1               | 0                |
      | info memorys      | 1               | 0                |
      | info persistences | 1               | 0                |
      | info replications | 1               | 0                |
      | info servers      | 1               | 0                |
      | info stats        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Amazon Redshift on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/redshift

Monitor Amazon Redshift health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Amazon Redshift health, cost and reliability signals, and catch incidents and runaway spend early.

[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=redshift)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="12">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (15 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                          |
        | -------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
        | **Active Connections**                 | Watch only         | CloudWatch DatabaseConnections.                                                                                         |
        | **Avg WLM Queue Wait (ms)**            | Merchant rule      | Avg WLM wait before execution from STV\_WLM\_QUERY\_STATE / query queue\_time.                                          |
        | **CPU Utilisation %**                  | Merchant rule      | CloudWatch CPUUtilization (leader + compute average).                                                                   |
        | **Connection Saturation %**            | Alert band 70 / 90 | DatabaseConnections / max\_connections. Redshift caps at 500 (default) - saturation = app login timeouts.               |
        | **Cross-Region Snapshot Lag (s)**      | Alert band 1 / 10  | Lag of cross-region automated snapshot copy (disaster-recovery replica freshness).                                      |
        | **Disk Space Used %**                  | Alert band 70 / 90 | CloudWatch PercentageDiskSpaceUsed. Full disks fail writes, vacuums and sorts - the #1 Redshift outage cause.           |
        | **Disk Space Used >90%**               | Alert band 0 / 1   | Alerts for Disk Space Used >90%.                                                                                        |
        | **Largest Table (GB)**                 | Watch only         | From SVV\_TABLE\_INFO.size - top tables drive disk pressure.                                                            |
        | **Last Snapshot Age (hours)**          | Alert band 24 / 72 | Age of the most recent automated/manual snapshot (DescribeClusterSnapshots). Redshift auto-snapshots on a schedule.     |
        | **Max Table Distribution Skew**        | Merchant rule      | Redshift-distinctive - SVV\_TABLE\_INFO.skew\_rows. High skew = one slice does all the work (bad DISTKEY).              |
        | **Queries Completed / sec**            | Watch only         | CloudWatch QueriesCompletedPerSecond - live throughput.                                                                 |
        | **Tables Needing VACUUM**              | Merchant rule      | Redshift-distinctive - SVV\_TABLE\_INFO.unsorted. High unsorted rows = full scans = slow queries + wasted disk.         |
        | **Tables with Stale Statistics**       | Merchant rule      | SVV\_TABLE\_INFO.stats\_off - stale ANALYZE leads the planner to bad join orders.                                       |
        | **WLM Queue Length**                   | Merchant rule      | Redshift-distinctive - CloudWatch WLMQueueLength. Sustained queueing = under-provisioned WLM / add concurrency scaling. |
        | **WLM Queueing Sustained (>5 queued)** | Alert band 0 / 1   | Alerts for WLM Queueing Sustained (>5 queued).                                                                          |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                             | Alert behaviour     | What it tracks                                                                                                                                             |
        | ---------------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Queries Spilling to Disk (24h)** | Merchant rule       | Redshift-distinctive - queries spilling to disk (SVL\_QUERY\_SUMMARY is\_diskbased) indicate undersized memory / bad joins.                                |
        | **Query Latency p50 (ms)**         | Watch only          | From SYS\_QUERY\_HISTORY.elapsed\_time percentiles.                                                                                                        |
        | **Query Latency p95 (ms)**         | Alert band 50 / 200 | Warehouse p95 measured over analytics queries - threshold reflects warehouse, not OLTP, use.                                                               |
        | **Result Cache Hit Rate %**        | Alert band 95 / 80  | Share of queries in the last hour served from the Redshift result cache (SYS\_QUERY\_HISTORY.result\_cache\_hit) - same query set already read for Slow-Qu |
        | **Slow-Query Rate %**              | Alert band 1 / 5    | Share of queries with elapsed\_time over the 5s slow threshold (SYS\_QUERY\_HISTORY).                                                                      |
        | **Top 10 Slowest Queries**         | Watch only          | Top 10 Slowest Queries, broken down by row.                                                                                                                |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                               |
        | ------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Query Error Rate %**                                 | Alert band 0.1 / 1 | Aborted / errored queries over total (SYS\_QUERY\_HISTORY.status = 'failed').                                |
        | **Redshift Connection Saturation vs Traffic Burst**    | Alert band 70 / 90 | Redshift Connection Saturation vs Traffic Burst, broken down by row.                                         |
        | **Redshift Query Spike vs Ecom Order Rate**            | Merchant rule      | Query load should track business volume. Divergence = runaway job / dashboard storm burning warehouse spend. |
        | **Redshift Table Row Count vs Ecom Catalog Size**      | Merchant rule      | Redshift-distinctive XC - ecom data lands in Redshift via ETL; row drift = pipeline / sync failure.          |
        | **Slow Analytics Queries During Checkout Window (5m)** | Merchant rule      | Slow Analytics Queries During Checkout Window (5m), broken down by row.                                      |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                     |
        | -------------------------------------- | ------------------ | ---------------------------------------------------------------------------------- |
        | **Queries Blocked on Locks**           | Merchant rule      | From STV\_LOCKS / SVV\_TRANSACTIONS - blocked transactions waiting on locks.       |
        | **Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 5m).                                     |
        | **Redshift Health Score**              | Merchant rule      | Composite of disk usage, WLM queueing, query error rate and connection saturation. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (12)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="WLM Queue Length >5 Sustained 5m">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Queues sustained above 5 in workload management mean the cluster is undersized or a workload is misplaced; everything behind it runs late.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `RS-CAP-003`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Queries Spilling to Disk >10 in 24h">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Queries spilling to disk run orders of magnitude slower than in memory; the offending queries are identifiable and usually tunable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `RS-PERF-004`
      </Accordion>

      <Accordion title="Tables With >10% Unsorted Rows (VACUUM Candidate)">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        Tables over 10 percent unsorted degrade every scan that touches them; VACUUM restores the performance already paid for.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `RS-MAINT-001`
      </Accordion>

      <Accordion title="Tables With Stale Statistics (ANALYZE Candidate)">
        **Severity** low · **Outcome** Customer experience · **Fix status** Report only

        Stale statistics mislead the query planner into bad plans; ANALYZE is the cheapest performance fix the cluster has.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `RS-MAINT-002`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **6 write** operations across cloudwatch:getmetricdatas, redshift:describeclusters, redshift:describeclustersnapshots, redshiftdata:describestatements, redshiftdata:executestatements, redshiftdata:getstatementresults on Amazon Redshift. 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=redshift)

    #### Ready to build your first Amazon Redshift 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                          | Read operations | Write operations |
      | --------------------------------- | --------------- | ---------------- |
      | cloudwatch:getmetricdatas         | 0               | 1                |
      | redshift:describeclusters         | 0               | 1                |
      | redshift:describeclustersnapshots | 0               | 1                |
      | redshiftdata:describestatements   | 0               | 1                |
      | redshiftdata:executestatements    | 0               | 1                |
      | redshiftdata:getstatementresults  | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Royal Mail on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/royal-mail

Monitor Royal Mail delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Royal Mail delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=royal-mail)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (17 signals)">
        | Signal                          | Alert behaviour  | What it tracks                                            |
        | ------------------------------- | ---------------- | --------------------------------------------------------- |
        | **API Error Rate**              | Watch only       | Description pending editorial review; the signal is live. |
        | **Avg Shipping Cost**           | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Claim Value (open)**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost Per Shipment Trend**     | Watch only       | Description pending editorial review; the signal is live. |
        | **Cost by Zone**                | Watch only       | Cost by Zone.                                             |
        | **Days to Token Expiry**        | Watch only       | Description pending editorial review; the signal is live. |
        | **Exception Rate**              | Alert band 2 / 5 | Description pending editorial review; the signal is live. |
        | **High-Cost Shipment Outliers** | Watch only       | High-Cost Shipment Outliers, broken down by row.          |
        | **Label Generation Success**    | Watch only       | Description pending editorial review; the signal is live. |
        | **OTD by Route**                | Watch only       | OTD by Route.                                             |
        | **Open Claims**                 | Watch only       | Description pending editorial review; the signal is live. |
        | **Returned to Sender**          | Watch only       | Description pending editorial review; the signal is live. |
        | **Route Volume Concentration**  | Merchant rule    | Route Volume Concentration, compared across items.        |
        | **Shipments**                   | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Shipments Over Time**         | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Destination**    | Watch only       | Description pending editorial review; the signal is live. |
        | **Shipments by Service**        | Watch only       | Shipments by Service.                                     |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                          |
        | --------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**            | Watch only         | Description pending editorial review; the signal is live.                                                               |
        | **First-Attempt Delivery Rate**   | Watch only         | Description pending editorial review; the signal is live.                                                               |
        | **Late Shipments**                | Watch only         | Description pending editorial review; the signal is live.                                                               |
        | **On-Time Delivery Rate**         | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                               |
        | **Tracked24 Service Day Promise** | Alert band 95 / 90 | % of Tracked24 / 1st-class consignments delivered next working day - the contracted Royal Mail premium-service promise. |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                              | Alert behaviour    | What it tracks                                                                                                                                         |
        | --------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Collection vs Post-Office Handover Failure Rate** | Merchant rule      | Royal Mail's distinguishing failure mode - collection vs Post Office vs Parcel Postbox handovers fail at very different rates. Surfaces operational fi |
        | **Failed Deliveries**                               | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **P58 Claim Age Distribution**                      | Merchant rule      | Open P58 claims by days-since-opened. RMG's standard window is 30 days; anything beyond signals abandoned cash + customer goodwill loss.               |
        | **Royal Mail OTD by Sales Channel**                 | Alert band 95 / 90 | Per-channel Royal Mail OTD - which sales surface is suffering most from carrier delays. Hero.                                                          |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **1 write** operations across tbds on Royal Mail. 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=royal-mail)

    #### Ready to build your first Royal Mail 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 1               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Sage Intacct / Business Cloud on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sage

Monitor Sage Intacct / Business Cloud performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Sage Intacct / Business Cloud performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=sage)

<CardGroup>
  <Card title="88">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (88)">
    ### Monitor performance

    88 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (59 signals)">
        | Signal                                                        | Alert behaviour      | What it tracks                                                                                                                                         |
        | ------------------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **A/R Aging Detail**                                          | Alert band 5 / 25    | A/R Aging Detail from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant is connected |
        | **AP Aging , 60+ Days**                                       | Alert band 10 / 30   | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Aging Buckets**                                          | Watch only           | AR Aging Buckets, compared across items.                                                                                                               |
        | **AR Aging , 60+ Days**                                       | Alert band 5 / 15    | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Balance (live)**                                         | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Accrual Reversals (last close)**                            | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Active Customers**                                          | Watch only           | Active Customers from Sage Intacct / Business Cloud, grouped under Customer Master. Computes when a live Sage Intacct / Business Cloud tenant is conne |
        | **Active Vendors**                                            | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Landed Cost per Unit**                              | Alert band 0 / 10    | Average Landed Cost per Unit from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud tenant is |
        | **B2B Payment Terms Mix**                                     | Watch only           | B2B Payment Terms Mix from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Cash Application Rate**                                     | Alert band 95 / 85   | Cash Application Rate from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Cash Applied Today**                                        | Watch only           | Cash Applied Today from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant is  |
        | **Credit Hold Spike**                                         | Alert band 0 / 5     | Credit Hold Spike from Sage Intacct / Business Cloud, grouped under Nerve Centre. Computes when a live Sage Intacct / Business Cloud tenant is connect |
        | **Customer Churn Signals**                                    | Alert band 0 / 5     | Customer Churn Signals from Sage Intacct / Business Cloud, grouped under Customer Master. Computes when a live Sage Intacct / Business Cloud tenant is |
        | **Customer Credit Utilisation**                               | Alert band 60 / 85   | Customer Credit Utilisation from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant i |
        | **DSO Increase Alert**                                        | Alert band 0 / 10    | DSO Increase Alert from Sage Intacct / Business Cloud, grouped under Nerve Centre. Computes when a live Sage Intacct / Business Cloud tenant is connec |
        | **Days Sales Outstanding (DSO)**                              | Alert band 30 / 60   | Description pending editorial review; the signal is live.                                                                                              |
        | **Days Since Last Bank Reconciliation**                       | Merchant rule        | UK Bacs cycle assumes weekly recon; gaps >7d compound and inflate close-cycle workload.                                                                |
        | **Dead Stock Threshold Breach**                               | Alert band 5 / 15    | Dead Stock Threshold Breach from Sage Intacct / Business Cloud, grouped under Nerve Centre. Computes when a live Sage Intacct / Business Cloud tenant  |
        | **Dead Stock Value**                                          | Watch only           | Dead Stock Value from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud tenant is connected;  |
        | **ERP-vs-Ecom Inventory Variance %**                          | Alert band 1 / 5     | Intacct Inventory module required. Sage Business Cloud Accounting doesn't ship inventory , card hides for those merchants.                             |
        | **Ecom Customers Absent from Sage**                           | Alert band 0 / 10    | Description pending editorial review; the signal is live.                                                                                              |
        | **Entity Health Roll-up**                                     | Watch only           | Entity Health Roll-up from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant  |
        | **FX Currency Exposure**                                      | Alert band 5 / 15    | FX Currency Exposure from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant i |
        | **Gross Margin Percentage**                                   | Watch only           | Gross Margin Percentage from Sage Intacct / Business Cloud, grouped under Margin & Cost. Computes when a live Sage Intacct / Business Cloud tenant is  |
        | **High-Value Overdue Invoices**                               | Alert band 0 / 50000 | High-Value Overdue Invoices from Sage Intacct / Business Cloud, grouped under Nerve Centre. Computes when a live Sage Intacct / Business Cloud tenant  |
        | **Intercompany Balance**                                      | Watch only           | Intercompany Balance from Sage Intacct / Business Cloud, grouped under Multi-Entity. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Inventory Aging**                                           | Watch only           | Inventory Aging from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud tenant is connected; r |
        | **Inventory Carrying Cost**                                   | Watch only           | Inventory Carrying Cost from Sage Intacct / Business Cloud, grouped under Margin & Cost. Computes when a live Sage Intacct / Business Cloud tenant is  |
        | **Inventory Item On-Hand Went Negative**                      | Merchant rule        | Alerts for Inventory Item On-Hand Went Negative.                                                                                                       |
        | **Inventory Turnover Ratio**                                  | Alert band 4 / 2     | Inventory Turnover Ratio from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud tenant is con |
        | **Journals by Source Module**                                 | Watch only           | Journals by Source Module.                                                                                                                             |
        | **Landed Cost Variance vs Standard**                          | Alert band 2 / 5     | Landed Cost Variance vs Standard from Sage Intacct / Business Cloud, grouped under Margin & Cost. Computes when a live Sage Intacct / Business Cloud t |
        | **Manual JEs as % of Total**                                  | Alert band 10 / 25   | Description pending editorial review; the signal is live.                                                                                              |
        | **Margin Compression**                                        | Alert band 0 / 2     | Margin Compression from Sage Intacct / Business Cloud, grouped under Nerve Centre. Computes when a live Sage Intacct / Business Cloud tenant is connec |
        | **Margin Erosion Alerts**                                     | Watch only           | Margin Erosion Alerts from Sage Intacct / Business Cloud, grouped under Margin & Cost. Computes when a live Sage Intacct / Business Cloud tenant is co |
        | **New Customers (30d)**                                       | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Hand Inventory Value**                                   | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Open (Pending) Transactions**                               | Alert band 0 / 50    | gltransaction rows in Pending / Reviewed / Submitted state. Backlog suggests approval-routing rule broken.                                             |
        | **Open Order Value**                                          | Watch only           | Open Order Value from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant is co |
        | **Open Orders**                                               | Watch only           | Open Orders from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant is connect |
        | **Order State Breakdown**                                     | Watch only           | Order State Breakdown from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant  |
        | **Order to Invoice Lead Time**                                | Alert band 3 / 7     | Order to Invoice Lead Time from Sage Intacct / Business Cloud, grouped under Sales Orders. Computes when a live Sage Intacct / Business Cloud tenant i |
        | **Orders Blocked on Inventory or Credit**                     | Alert band 0 / 5     | Orders Blocked on Inventory or Credit from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud  |
        | **Orders on Credit Hold**                                     | Alert band 0 / 5     | Orders on Credit Hold from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Overdue Invoice Value**                                     | Alert band 0 / 50000 | Overdue Invoice Value from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Period Close / VAT Return Past Deadline**                   | Alert band 0 / 5     | MTD VAT submission overdue = HMRC surcharge. Pair with period-close overdue alarm.                                                                     |
        | **Period Close On-Time Rate (12mo)**                          | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Period Close Status**                                       | Alert band 0 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Returns Count**                                             | Alert band 5 / 20    | Returns Count from Sage Intacct / Business Cloud, grouped under Sales Orders. Computes when a live Sage Intacct / Business Cloud tenant is connected;  |
        | **Sage Health Score**                                         | Merchant rule        | Composite: VAT-coded-complete x smart-coding-queue-clean x bank-recon-fresh x AR-aging-low.                                                            |
        | **Slow-Moving Inventory (>90d)**                              | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Top Findings Across Entitys**                               | Alert band 0 / 5     | Top Findings Across Entitys from Sage Intacct / Business Cloud, grouped under Multi-Entity. Computes when a live Sage Intacct / Business Cloud tenant  |
        | **Top SKUs by Inventory Value**                               | Watch only           | Top SKUs by Inventory Value from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud tenant is  |
        | **Total COGS**                                                | Watch only           | Total COGS from Sage Intacct / Business Cloud, grouped under Margin & Cost. Computes when a live Sage Intacct / Business Cloud tenant is connected; re |
        | **Transaction Imbalances**                                    | Alert band 0 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Transactions Failing Validation (imbalance / missing VAT)** | Alert band 0 / 5     | Alerts for Transactions Failing Validation (imbalance / missing VAT).                                                                                  |
        | **Unpaid Invoice Count**                                      | Watch only           | Unpaid Invoice Count from Sage Intacct / Business Cloud, grouped under AP/AR Cycle. Computes when a live Sage Intacct / Business Cloud tenant is conne |
        | **Vendor Payment On-Time Rate**                               | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (15 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Order Value**                  | Alert band 0 / -5  | Average Order Value from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is co |
        | **Cash Collected**                       | Alert band 0 / -15 | Cash Collected from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is connect |
        | **Consolidated Revenue Trend**           | Watch only         | Consolidated Revenue Trend from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenan |
        | **Credit Memo Value**                    | Watch only         | Credit Memo Value from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Invoiced Revenue**                     | Alert band 0 / -5  | Invoiced Revenue from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is conne |
        | **Revenue Booked Over Time**             | Watch only         | Revenue Booked Over Time from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant  |
        | **Revenue Booked into GL**               | Watch only         | Revenue Booked into GL from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is |
        | **Revenue Gap Spike**                    | Alert band 0 / 20  | Revenue Gap Spike from Sage Intacct / Business Cloud, grouped under Nerve Centre. Computes when a live Sage Intacct / Business Cloud tenant is connect |
        | **Revenue Gap vs Commerce**              | Alert band 0 / 5   | Revenue Gap vs Commerce from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant i |
        | **Revenue Lines Missing VAT Code (MTD)** | Merchant rule      | Revenue-line transactions without VATCODE = MTD non-compliant. HMRC requires digital records for every VAT-eligible transaction.                       |
        | **Revenue by Currency**                  | Watch only         | Revenue by Currency from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is co |
        | **Revenue by Entity**                    | Watch only         | Revenue by Entity from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is conn |
        | **Revenue by Segment**                   | Watch only         | Revenue by Segment from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant is con |
        | **Top B2B Accounts by Revenue**          | Watch only         | Top B2B Accounts by Revenue from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tena |
        | **Top Customers by Revenue**             | Watch only         | Top Customers by Revenue from Sage Intacct / Business Cloud, grouped under Revenue & Sales. Computes when a live Sage Intacct / Business Cloud tenant  |
      </Accordion>

      <Accordion title="Protect revenue (11 signals)">
        | Signal                                                    | Alert behaviour         | What it tracks                                                                                                                                         |
        | --------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AR Aging on Customers with Active Ecom Orders**         | Alert band 1000 / 10000 | AR Aging on Customers with Active Ecom Orders, broken down by row.                                                                                     |
        | **B2B Customers with VAT Number Mismatch (ecom vs Sage)** | Merchant rule           | UK B2B VAT compliance requires consistent VAT registration number across ecom and ERP. Mismatch = reverse-charge accounting error risk.                |
        | **Current VAT Return Status (MTD)**                       | Merchant rule           | HMRC Making Tax Digital VAT return cycle status. Overdue = surcharge risk + repeat-offender escalation.                                                |
        | **Dead Stock with Active Ad Spend**                       | Watch only              | Dead Stock with Active Ad Spend from Sage Intacct / Business Cloud, grouped under Cross-Channel: Revenue at Risk. Computes when a live Sage Intacct /  |
        | **Ecom Customers Absent from Sage Customer Master**       | Alert band 0 / 10       | Sage Network sync gap. B2B-flagged ecom customers missing in Sage = VAT-line classification fails on next invoice batch.                               |
        | **Ecom Orders Missing Matching Sage Transaction**         | Merchant rule           | Sage Network or 3rd-party connector integration gap , revenue invisible to GL + VAT-return base understated.                                           |
        | **Inventory Sync Drift**                                  | Watch only              | Inventory Sync Drift from Sage Intacct / Business Cloud, grouped under Cross-Channel: Revenue at Risk. Computes when a live Sage Intacct / Business Cl |
        | **Low Stock Alerts**                                      | Alert band 0 / 5        | Low Stock Alerts from Sage Intacct / Business Cloud, grouped under Inventory. Computes when a live Sage Intacct / Business Cloud tenant is connected;  |
        | **OOS with Open Order Demand**                            | Watch only              | OOS with Open Order Demand from Sage Intacct / Business Cloud, grouped under Cross-Channel: Revenue at Risk. Computes when a live Sage Intacct / Busin |
        | **Revenue Gap**                                           | Watch only              | Revenue Gap from Sage Intacct / Business Cloud, grouped under Cross-Channel: Revenue at Risk. Computes when a live Sage Intacct / Business Cloud tenan |
        | **SKUs with Intacct-vs-Ecom Inventory Drift >5%**         | Alert band 1 / 5        | SKUs with Intacct-vs-Ecom Inventory Drift >5%, broken down by row.                                                                                     |
      </Accordion>

      <Accordion title="Catalogue quality (2 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Margin by SKU**                  | Alert band 30 / 10 | Margin by SKU from Sage Intacct / Business Cloud, grouped under Margin & Cost. Computes when a live Sage Intacct / Business Cloud tenant is connected; |
        | **Smart Coding Queue Depth (24h)** | Merchant rule      | Intacct's auto-categorisation engine , backlog usually = unrecognised PSP fee descriptors needing rule training.                                       |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                 | Alert behaviour | What it tracks                                                                                                                                        |
        | ---------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Entity Performance** | Watch only      | Entity Performance from Sage Intacct / Business Cloud, grouped under Executive Overview. Computes when a live Sage Intacct / Business Cloud tenant is |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **2 write** operations across iaxmlxmlgwphtmls, tokens on Sage Intacct / Business Cloud. 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=sage)

    #### Ready to build your first Sage Intacct / Business Cloud 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.

    <Accordion title="Browse the operations you can build with">
      | Resource         | Read operations | Write operations |
      | ---------------- | --------------- | ---------------- |
      | iaxmlxmlgwphtmls | 0               | 1                |
      | tokens           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Salesforce on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/salesforce

Monitor Salesforce pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Salesforce 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=salesforce)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="14">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (13 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                        |
        | ----------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule      | Campaigns grouped by status (sent, draft, scheduled).                                                 |
        | **Checkout-to-Order Rate**    | Merchant rule      | Share of started checkouts that became paid orders.                                                   |
        | **Click-to-Open Rate**        | Alert band 10 / 3  | Clicks as a share of opens - engagement quality independent of open-rate inflation.                   |
        | **Conversion Rate**           | Merchant rule      | Orders as a share of emails sent. Ties send volume to revenue.                                        |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Share of delivered emails that earned a click. The clearest engagement signal.                        |
        | **Engagement Funnel**         | Merchant rule      | Sent to delivered to opened to clicked, showing where engagement drops off.                           |
        | **List Count**                | Merchant rule      | Number of audiences on the account.                                                                   |
        | **Lists Overview**            | Merchant rule      | Every audience with its member count.                                                                 |
        | **Revenue per Recipient**     | Merchant rule      | Revenue divided by emails sent. What each address is worth per send.                                  |
        | **Revenue per Send**          | Merchant rule      | Revenue divided by emails sent - the efficiency of each send, validated against realised ecom orders. |
        | **Top Lists by Name**         | Merchant rule      | Largest audiences by member count.                                                                    |
        | **Total Revenue**             | Merchant rule      | Placed-order revenue attributed to Salesforce/Marketing-Cloud sends. The hero revenue number.         |
        | **Total Sends**               | Merchant rule      | Total emails sent across campaigns in the window.                                                     |
      </Accordion>

      <Accordion title="Run operations (11 signals)">
        | Signal                        | Alert behaviour     | What it tracks                                                                                                                                         |
        | ----------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Subscribers (Est.)** | Merchant rule       | Estimated subscribed, reachable contacts.                                                                                                              |
        | **CRM Data Hygiene Score**    | Alert band 95 / 80  | Composite required-field-completeness score across three confirmed standard fields: share of Contacts with Email populated, share of Opportunities lin |
        | **Email Open Rate**           | Alert band 20 / 10  | Share of delivered emails opened. iOS Mail Privacy inflates this; pair with click-to-open.                                                             |
        | **Flow Count Summary**        | Merchant rule       | How many automations exist on the account.                                                                                                             |
        | **Flow Status Breakdown**     | Merchant rule       | Automations split by status (live, draft, paused).                                                                                                     |
        | **Flow Trigger Types**        | Merchant rule       | Automations grouped by what triggers them.                                                                                                             |
        | **Lead Response Time**        | Alert band 60 / 480 | Median minutes from Lead.CreatedDate to the CreatedDate of the first Task logged against that Lead (Task.WhoId references the Lead). Both are confirme |
        | **List Health Summary**       | Merchant rule       | Total reachable members across all lists.                                                                                                              |
        | **Placed Orders Total**       | Merchant rule       | Orders attributed to email in the window.                                                                                                              |
        | **Segments Overview**         | Merchant rule       | Saved segments and their sizes.                                                                                                                        |
        | **Stalled Deal %**            | Alert band 10 / 30  | Open (IsClosed=false) Opportunities with no logged activity in 14 days, as a share of all open Opportunities. LastActivityDate is a genuine Salesforce |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                  | Alert behaviour      | What it tracks                                                                |
        | ----------------------- | -------------------- | ----------------------------------------------------------------------------- |
        | **Bounce Rate**         | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation.           |
        | **Delivery Rate**       | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention.     |
        | **Email Health KPIs**   | Merchant rule        | Delivered, bounced and unsubscribed at a glance - your deliverability vitals. |
        | **Refund Rate**         | Merchant rule        | Share of attributed orders later refunded.                                    |
        | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam complaints per send. Above 0.1% puts deliverability at risk.             |
        | **Unsubscribe Rate**    | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.    |
      </Accordion>

      <Accordion title="Customer experience (2 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the platform reports it. |
        | **Flows List**        | Merchant rule   | Every automation/journey and its current status.                  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **10 read** and **4 write** operations across contactlists, interactions, interactioninteractionstops, messagingmessagedefinitionsends, messagingmessagedefinitionsendpauses, messagingmessagedefinitionsendresumes on Salesforce. 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=salesforce)

    #### Ready to build your first Salesforce 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                              | Read operations | Write operations |
      | ------------------------------------- | --------------- | ---------------- |
      | contactlists                          | 1               | 0                |
      | interactions                          | 1               | 0                |
      | interactioninteractionstops           | 0               | 1                |
      | messagingmessagedefinitionsends       | 1               | 0                |
      | messagingmessagedefinitionsendpauses  | 0               | 1                |
      | messagingmessagedefinitionsendresumes | 0               | 1                |
      | servicedataquerys                     | 1               | 0                |
      | servicedatasobjectaccounts            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Salesforce Commerce Cloud (B2C) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/salesforce-commerce-cloud

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Salesforce Commerce Cloud (B2C).

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Salesforce Commerce Cloud (B2C).

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/salesforce-commerce-cloud) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=salesforce-commerce-cloud)

<CardGroup>
  <Card title="41">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (41)">
    ### Monitor performance

    41 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                                                                 |
        | ------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Sites / Storefronts**        | Watch only         | Count of enabled SCC sites (country/locale storefronts under one realm).                                                       |
        | **Average Order Value**               | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                      |
        | **Fulfillment Rate**                  | Alert band 95 / 90 | % of orders (30d) with shipping\_status = shipped , the same field the Shipping Status Distribution chart already breaks down. |
        | **New Customers (30d)**               | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Order Processing Backlog**          | Alert band 10 / 50 | Alerts for Order Processing Backlog.                                                                                           |
        | **Order Volume**                      | Watch only         | Description pending editorial review; the signal is live.                                                                      |
        | **Orders by Currency**                | Watch only         | Orders by Currency.                                                                                                            |
        | **Payment Status Distribution**       | Watch only         | Payment Status Distribution, shown by share.                                                                                   |
        | **Pending Orders (created/new/open)** | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                      |
        | **Shipping Status Distribution**      | Watch only         | Shipping Status Distribution, shown by share.                                                                                  |
        | **Stock-Out Burst**                   | Merchant rule      | Alerts for Stock-Out Burst.                                                                                                    |
        | **Total Registered Customers**        | Watch only         | Description pending editorial review; the signal is live.                                                                      |
      </Accordion>

      <Accordion title="Protect revenue (11 signals)">
        | Signal                                      | Alert behaviour  | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cancellation Rate**                       | Alert band 1 / 3 | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Rate**                         | Alert band 3 / 1 | Conversion Rate from Salesforce Commerce Cloud (B2C), grouped under Revenue at Risk. Computes when a live Salesforce Commerce Cloud (B2C) integration  |
        | **Failed Orders (24h)**                     | Merchant rule    | Description pending editorial review; the signal is live.                                                                                              |
        | **High-Value Customers Unengaged on Email** | Merchant rule    | High-Value Customers Unengaged on Email, broken down by row.                                                                                           |
        | **Low-Stock Products**                      | Watch only       | Low-Stock Products from Salesforce Commerce Cloud (B2C), grouped under Catalogue Health. Computes when a live Salesforce Commerce Cloud (B2C) integrat |
        | **Orders → Email Attribution**              | Merchant rule    | Orders → Email Attribution, broken down by row.                                                                                                        |
        | **Out-of-Stock Products**                   | Alert band 0 / 5 | Description pending editorial review; the signal is live.                                                                                              |
        | **Refund Rate**                             | Alert band 2 / 5 | Refund Rate from Salesforce Commerce Cloud (B2C), grouped under Refunds & Cancellations. Computes when a live Salesforce Commerce Cloud (B2C) integrat |
        | **Revenue at Risk (live)**                  | Merchant rule    | Description pending editorial review; the signal is live.                                                                                              |
        | **SCC Inventory vs Marketplace Listings**   | Merchant rule    | SCC Inventory vs Marketplace Listings.                                                                                                                 |
        | **Top-Velocity SKUs vs Ad Spend**           | Merchant rule    | Top-Velocity SKUs vs Ad Spend, broken down by row.                                                                                                     |
      </Accordion>

      <Accordion title="Grow revenue (11 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Conversion by Locale**                 | Merchant rule      | Per-locale conversion rate. Single-locale dropoff = local UX issue, payment-method gap, or localisation error.                                         |
        | **Master vs Variant Product Count**      | Watch only         | SCC product model has master/variant relationships , surface ratio for catalog complexity visibility.                                                  |
        | **Orders Awaiting Downstream Sync >24h** | Merchant rule      | Orders not yet flowed to Marketing Cloud / Service Cloud / OMS , surface revenue + customer-experience gaps from sync drift.                           |
        | **Orders by Status**                     | Watch only         | Orders by Status from Salesforce Commerce Cloud (B2C), grouped under Revenue & Growth. Computes when a live Salesforce Commerce Cloud (B2C) integratio |
        | **Orders to Email Attribution**          | Watch only         | Orders to Email Attribution from Salesforce Commerce Cloud (B2C), grouped under Order Issues. Computes when a live Salesforce Commerce Cloud (B2C) int |
        | **Products Missing SEO Title**           | Alert band 10 / 30 | Products where page\_title has no value in any locale.                                                                                                 |
        | **Repeat Customer Rate**                 | Alert band 25 / 10 | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue Trend**                        | Alert band 0 / -5  | Revenue Trend from Salesforce Commerce Cloud (B2C), grouped under Revenue & Growth. Computes when a live Salesforce Commerce Cloud (B2C) integration i |
        | **Revenue by Site / Locale**             | Watch only         | Per-site / per-locale revenue mix. Enterprise SCC realms run 5-20 country sites typically , shapes localisation + market investment.                   |
        | **Top Products by Revenue**              | Watch only         | Top Products by Revenue from Salesforce Commerce Cloud (B2C), grouped under Revenue & Growth. Computes when a live Salesforce Commerce Cloud (B2C) int |
        | **Total Revenue (30d)**                  | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Control risk and change (4 signals)">
        | Signal                                                       | Alert behaviour | What it tracks                                                                                                                     |
        | ------------------------------------------------------------ | --------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
        | **API Version Status (OCAPI / SCAPI)**                       | Merchant rule   | Per-integration API version + days-until-EOL. Salesforce deprecates 2 OCAPI versions/year , surfaces replatform-readiness signals. |
        | **Integrations on EOL'd / EOL-Soon Versions**                | Merchant rule   | Description pending editorial review; the signal is live.                                                                          |
        | **OCAPI / SCAPI Failure Rate Spike OR Version EOL Imminent** | Merchant rule   | SCC integrations break hard on version EOL , surfaces replatform-grade engineering concerns.                                       |
        | **OCAPI vs SCAPI Usage Mix**                                 | Watch only      | % split between legacy OCAPI and modern SCAPI usage. Drives Salesforce-side strategic conversation (SCAPI is the future).          |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                              | Alert behaviour   | What it tracks                                               |
        | ----------------------------------- | ----------------- | ------------------------------------------------------------ |
        | **Offline Products (online=false)** | Watch only        | Description pending editorial review; the signal is live.    |
        | **Products Missing Description**    | Alert band 5 / 20 | Products where long\_description has no value in any locale. |
        | **Total Products**                  | Watch only        | Description pending editorial review; the signal is live.    |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **1 write** operations across dwdataclients, dwdatacustomerlistcustomers, dwdataorders, dwdataproducts, dwdatasites, dwssooauth2accesstokens on Salesforce Commerce Cloud (B2C). 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=salesforce-commerce-cloud)

    #### Ready to build your first Salesforce Commerce Cloud (B2C) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | dwdataclients               | 1               | 0                |
      | dwdatacustomerlistcustomers | 1               | 0                |
      | dwdataorders                | 1               | 0                |
      | dwdataproducts              | 1               | 0                |
      | dwdatasites                 | 1               | 0                |
      | dwssooauth2accesstokens     | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Sanity on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sanity

Monitor Sanity publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Sanity publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=sanity)

<CardGroup>
  <Card title="17">
    performance signals
  </Card>

  <Card title="2">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (17)">
    ### Monitor performance

    17 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (9 signals)">
        | Signal                          | Alert behaviour        | What it tracks                                                           |
        | ------------------------------- | ---------------------- | ------------------------------------------------------------------------ |
        | **Accessibility Score**         | Alert band 90 / 70     | Lighthouse Accessibility category score for the rendered page.           |
        | **CLS (Mobile)**                | Alert band 0.1 / 0.25  | Cumulative Layout Shift, 75th percentile field data (mobile).            |
        | **CWV Pass Rate (Mobile)**      | Alert band 75 / 50     | % of real-user CrUX samples passing all three Core Web Vitals on mobile. |
        | **INP (Mobile)**                | Alert band 200 / 500   | Interaction to Next Paint, 75th percentile field data (mobile).          |
        | **LCP (Mobile)**                | Alert band 2500 / 4000 | Largest Contentful Paint, 75th percentile field data (mobile).           |
        | **Performance Score (Desktop)** | Alert band 90 / 50     | Lighthouse Performance category score, desktop strategy.                 |
        | **Performance Score (Mobile)**  | Alert band 90 / 50     | Lighthouse Performance category score, mobile strategy.                  |
        | **Speed Index**                 | Alert band 3400 / 5800 | How quickly content is visually populated (Lighthouse Speed Index).      |
        | **TTFB (Mobile)**               | Alert band 800 / 1800  | Time to First Byte, 75th percentile field data (mobile).                 |
      </Accordion>

      <Accordion title="Catalogue quality (5 signals)">
        | Signal                        | Alert behaviour              | What it tracks                                                                     |
        | ----------------------------- | ---------------------------- | ---------------------------------------------------------------------------------- |
        | **Best Practices Score**      | Alert band 90 / 70           | Lighthouse Best Practices category score for the rendered page.                    |
        | **Render-Blocking Resources** | Alert band 200 / 500         | Estimated savings from eliminating render-blocking CSS/JS.                         |
        | **Stale Content**             | Alert band 10 / 40           | % of documents (sampled, up to 200 most recent) not updated in the last 12 months. |
        | **Total Blocking Time**       | Alert band 200 / 600         | Total time the main thread was blocked (Lighthouse TBT).                           |
        | **Total Page Weight**         | Alert band 1572864 / 3145728 | Total transferred byte weight of the rendered page.                                |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                 | Alert behaviour    | What it tracks                                                              |
        | ---------------------- | ------------------ | --------------------------------------------------------------------------- |
        | **Publishing Cadence** | Alert band 4 / 1   | Documents created across the dataset in the last 30 days (drafts excluded). |
        | **SEO Score**          | Alert band 90 / 70 | Lighthouse SEO category score for the rendered page.                        |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                  | Alert behaviour | What it tracks                                            |
        | --------------------------------------- | --------------- | --------------------------------------------------------- |
        | **Revenue at Risk from CWV Regression** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (2)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Over 40% of content not updated in 12 months">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When over 40 percent of content has not been touched in a year, decay outpaces creation; rankings quietly rot page by page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-STALE-001`
      </Accordion>

      <Accordion title="Publishing pipeline stalled (no post in 30 days)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A stalled publishing pipeline slowly starves organic traffic; content compounds only while it keeps shipping.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CMS-PUBLISH-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across pagespeedonlinerunpagespeeds, projects, records:queryrecords, vdatadocs, vdataquerys on Sanity. 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=sanity)

    #### Ready to build your first Sanity 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | pagespeedonlinerunpagespeeds | 1               | 0                |
      | projects                     | 1               | 0                |
      | records:queryrecords         | 0               | 1                |
      | vdatadocs                    | 1               | 0                |
      | vdataquerys                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# SAP S/4HANA Cloud on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sap

Monitor SAP S/4HANA Cloud performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor SAP S/4HANA Cloud performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=sap)

<CardGroup>
  <Card title="85">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (85)">
    ### Monitor performance

    85 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (55 signals)">
        | Signal                                                | Alert behaviour      | What it tracks                                                                                                                                         |
        | ----------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **A/R Aging Detail**                                  | Alert band 5 / 25    | A/R Aging Detail from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/inve |
        | **AP Aging , 60+ Days**                               | Alert band 10 / 30   | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Aging Buckets (0-30/31-60/61-90/90+)**           | Watch only           | AR Aging Buckets (0-30/31-60/61-90/90+), compared across items.                                                                                        |
        | **AR Aging , 60+ Days**                               | Alert band 5 / 15    | Description pending editorial review; the signal is live.                                                                                              |
        | **AR Balance (live, by CompanyCode)**                 | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Accrual Reversals (last close)**                    | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Active Customers**                                  | Watch only           | Active Customers from SAP, grouped under Customer Master. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/ |
        | **Active Vendor Business Partners**                   | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Landed Cost per Unit**                      | Alert band 0 / 10    | Average Landed Cost per Unit from SAP, grouped under Inventory. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fi |
        | **B2B Payment Terms Mix**                             | Watch only           | B2B Payment Terms Mix from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Blocked Customers (BusinessPartnerIsBlocked=true)** | Alert band 2 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Cash Application Rate**                             | Alert band 95 / 85   | Cash Application Rate from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Cash Applied Today**                                | Watch only           | Cash Applied Today from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/in |
        | **Company Code Health Roll-up**                       | Watch only           | Company Code Health Roll-up from SAP, grouped under Multi-Entity. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP  |
        | **Credit Hold Spike**                                 | Alert band 0 / 5     | Credit Hold Spike from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/in |
        | **Customer Churn Signals**                            | Alert band 0 / 5     | Customer Churn Signals from SAP, grouped under Customer Master. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fi |
        | **Customer Credit Utilisation**                       | Alert band 60 / 85   | Customer Credit Utilisation from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP f |
        | **DSO Increase Alert**                                | Alert band 0 / 10    | DSO Increase Alert from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/i |
        | **Days Sales Outstanding (DSO)**                      | Alert band 30 / 60   | Description pending editorial review; the signal is live.                                                                                              |
        | **Dead Stock Threshold Breach**                       | Alert band 0 / 1     | Dead Stock Threshold Breach from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP  |
        | **Dead Stock Value**                                  | Alert band 5 / 15    | Dead Stock Value from SAP, grouped under Inventory. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/invent |
        | **ERP-vs-Ecom Inventory Variance % (top-50 SKUs)**    | Alert band 1 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Ecom Customers Absent from SAP Business Partner**   | Alert band 0 / 10    | Ecom customers with completed orders + no SAP Business Partner = AR can't post, credit-limit logic bypassed.                                           |
        | **Gross Margin Percentage**                           | Watch only           | Gross Margin Percentage from SAP, grouped under Margin & Cost. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fin |
        | **High-Value Overdue Invoices**                       | Alert band 0 / 50000 | High-Value Overdue Invoices from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP  |
        | **Intercompany Balance**                              | Watch only           | Intercompany Balance from SAP, grouped under Multi-Entity. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Intercompany Imbalances (consolidation blocker)**   | Merchant rule        | Sub-company journals that don't balance across the CompanyCode group. Blocks SAP Group Reporting consolidation.                                        |
        | **Inventory Carrying Cost**                           | Watch only           | Inventory Carrying Cost from SAP, grouped under Inventory. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Inventory Turnover Ratio**                          | Alert band 4 / 2     | Inventory Turnover Ratio from SAP, grouped under Inventory. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP financ |
        | **Journal Imbalances (debit != credit)**              | Alert band 0 / 5     | SAP rejects imbalanced documents; persistence suggests integration logic broken on the calling side.                                                   |
        | **Landed Cost Variance vs Standard**                  | Alert band 2 / 5     | Landed Cost Variance vs Standard from SAP, grouped under Margin & Cost. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom agains |
        | **Manual Journals (FB50/FB60) as % of Total**         | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Margin Compression**                                | Alert band 0 / 2     | Margin Compression from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/i |
        | **Margin Erosion Alerts**                             | Watch only           | Margin Erosion Alerts from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP financ |
        | **Margin by SKU**                                     | Alert band 30 / 10   | Margin by SKU from SAP, grouped under Margin & Cost. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/inven |
        | **New Business Partners (30d)**                       | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Hand Inventory Value (StandardPrice)**           | Watch only           | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Sales Document Value**                         | Watch only           | Open Sales Document Value from SAP, grouped under Sales Orders. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fi |
        | **Open Sales Documents**                              | Watch only           | Open Sales Documents from SAP, grouped under Sales Orders. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Orders on Credit Hold**                             | Alert band 0 / 5     | Orders on Credit Hold from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Overdue Invoice Value**                             | Alert band 0 / 50000 | Overdue Invoice Value from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **Period Close On-Time Rate (12mo)**                  | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Period Close Status (by CompanyCode)**              | Alert band 0 / 5     | Multi-entity SAP installs close per CompanyCode; one late entity blocks consolidation.                                                                 |
        | **Returns Count**                                     | Alert band 5 / 20    | Returns Count from SAP, grouped under Sales Orders. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/invent |
        | **SAP S/4HANA Health Score**                          | Merchant rule        | Composite: idoc-queue-clean x AR-aging-low x inventory-variance-low x close-on-time.                                                                   |
        | **SKUs Below Safety Stock**                           | Alert band 0 / 5     | Description pending editorial review; the signal is live.                                                                                              |
        | **Sales Document State Breakdown**                    | Watch only           | Sales Document State Breakdown from SAP, grouped under Sales Orders. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against S |
        | **Sales Document to Invoice Lead Time**               | Alert band 3 / 7     | Sales Document to Invoice Lead Time from SAP, grouped under Sales Orders. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom agai |
        | **Sales Documents Blocked on Inventory or Credit**    | Alert band 0 / 5     | Sales Documents Blocked on Inventory or Credit from SAP, grouped under Sales Orders. Computes when a live S/4HANA Cloud tenant is connected; reconcile |
        | **Slow-Moving Inventory (>90d no movement)**          | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
        | **Top Findings Across Company Codes**                 | Alert band 0 / 5     | Top Findings Across Company Codes from SAP, grouped under Multi-Entity. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom agains |
        | **Top SKUs by Inventory Value**                       | Watch only           | Top SKUs by Inventory Value from SAP, grouped under Inventory. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fin |
        | **Total COGS**                                        | Watch only           | Total COGS from SAP, grouped under Margin & Cost. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/inventor |
        | **Unpaid Invoice Count**                              | Watch only           | Unpaid Invoice Count from SAP, grouped under AP/AR Cycle. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/ |
        | **Vendor Payment On-Time Rate**                       | Merchant rule        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (18 signals)">
        | Signal                                                 | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Sales Document Value**                       | Alert band 0 / -5  | Average Sales Document Value from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against  |
        | **Cash Collected**                                     | Alert band 0 / -15 | Cash Collected from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/in |
        | **Consolidated Revenue Trend**                         | Watch only         | Consolidated Revenue Trend from SAP, grouped under Multi-Entity. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP f |
        | **Credit Memo Value**                                  | Watch only         | Credit Memo Value from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance |
        | **FX Currency Exposure**                               | Alert band 5 / 15  | FX Currency Exposure from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fina |
        | **Idoc Error Queue Depth (last 24h)**                  | Merchant rule      | Idocs in error status 51/56/64 , typical ecom-integration failure mode (Sales Document type missing, partner profile missing, currency conversion erro |
        | **Invoiced Revenue**                                   | Alert band 0 / -5  | Invoiced Revenue from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/ |
        | **Journal Entries Failing to Post (idoc error queue)** | Alert band 0 / 5   | Idoc EXPORT/IMPORT failures block ecom-driven postings. P1 because revenue invisible to GL until resolved.                                             |
        | **Journals by Source Module**                          | Watch only         | SD/MM/FI/PP split. SD share growth = ecom integration scaling; spikes in FI manual = controls gap.                                                     |
        | **Material On-Hand Went Negative (any Plant)**         | Alert band 0 / 1   | Negative on-hand = double-posting via MM-IM movements, unit-of-measure conversion error, or stock-transfer race.                                       |
        | **Revenue Booked Over Time**                           | Watch only         | Revenue Booked Over Time from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP  |
        | **Revenue Booked into GL**                             | Watch only         | Revenue Booked into GL from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fi |
        | **Revenue Gap Spike**                                  | Alert band 0 / 20  | Revenue Gap Spike from SAP, grouped under Nerve Centre. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finance/in |
        | **Revenue by Company Code**                            | Watch only         | Revenue by Company Code from SAP, grouped under Multi-Entity. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fina |
        | **Revenue by Currency**                                | Watch only         | Revenue by Currency from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP finan |
        | **Revenue by Segment**                                 | Watch only         | Revenue by Segment from SAP, grouped under Revenue & Sales. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP financ |
        | **Top B2B Accounts by Revenue**                        | Watch only         | Top B2B Accounts by Revenue from SAP, grouped under Customer Master. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against S |
        | **Top Customers by Revenue**                           | Watch only         | Top Customers by Revenue from SAP, grouped under Customer Master. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP  |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                                   | Alert behaviour         | What it tracks                                                                                                                                         |
        | -------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AR Aging on Customers with Active Ecom Orders**        | Alert band 1000 / 10000 | Credit-control gap: customer ordering on ecom while past-due on SAP AR. Should auto-flag BusinessPartnerIsBlocked=true.                                |
        | **Commerce Orders Without S/4HANA Cloud Sales Document** | Watch only              | Commerce Orders Without S/4HANA Cloud Sales Document from SAP, grouped under Cross-Channel: Revenue at Risk. Computes when a live S/4HANA Cloud tenant |
        | **Dead Stock with Active Ad Spend**                      | Watch only              | Dead Stock with Active Ad Spend from SAP, grouped under Cross-Channel: Revenue at Risk. Computes when a live S/4HANA Cloud tenant is connected; reconc |
        | **Ecom Orders Missing Matching SAP Billing Document**    | Merchant rule           | Orders the merchant fulfilled but SAP never billed , pure missed revenue + audit-trail gap. Common cause: Sales Document type misconfigured in IDoc pa |
        | **OOS with Open Sales Document Demand**                  | Watch only              | OOS with Open Sales Document Demand from SAP, grouped under Cross-Channel: Revenue at Risk. Computes when a live S/4HANA Cloud tenant is connected; re |
        | **Revenue Gap vs Commerce**                              | Alert band 0 / 5        | Revenue Gap vs Commerce from SAP, grouped under Cross-Channel: Revenue at Risk. Computes when a live S/4HANA Cloud tenant is connected; reconciles eco |
        | **Revenue Gap, Detailed Breakdown**                      | Watch only              | Revenue Gap, Detailed Breakdown from SAP, grouped under Cross-Channel: Revenue at Risk. Computes when a live S/4HANA Cloud tenant is connected; reconc |
        | **SKUs with SAP-vs-Ecom Inventory Drift >5%**            | Alert band 1 / 5        | Plant-level on-hand vs ecom availability divergence. Resolve via MM-IM stock-transfer or sync-job restart.                                             |
        | **Top-10 Customer AR Concentration %**                   | Merchant rule           | Top-10 customers' share of total AR. >40% = concentration risk; single bankruptcy event can dent quarter.                                              |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                           | Alert behaviour   | What it tracks                                                                                                            |
        | ------------------------------------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------- |
        | **Open (Unposted) Journal Entries**              | Alert band 0 / 50 | AccountingDocuments stuck in error queue. Common cause: idoc IMPORT failure on Sales Document type from ecom integration. |
        | **Period Close Past Deadline (any CompanyCode)** | Alert band 0 / 5  | Late close on any CompanyCode blocks Group Reporting consolidation + audit-trail integrity.                               |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                       | Alert behaviour | What it tracks                                                                                                                                         |
        | ---------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Company Code Performance** | Watch only      | Company Code Performance from SAP, grouped under Multi-Entity. Computes when a live S/4HANA Cloud tenant is connected; reconciles ecom against SAP fin |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across oauthtokens, sapopuodatasapapibusinesspartners, sapopuodatasapapiglaccounthierarchys, sapopuodatasapapijournalentryitembasics, sapopuodatasapapimaterialstocksrvs on SAP S/4HANA Cloud. 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=sap)

    #### Ready to build your first SAP S/4HANA Cloud 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                | Read operations | Write operations |
      | --------------------------------------- | --------------- | ---------------- |
      | oauthtokens                             | 0               | 1                |
      | sapopuodatasapapibusinesspartners       | 1               | 0                |
      | sapopuodatasapapiglaccounthierarchys    | 1               | 0                |
      | sapopuodatasapapijournalentryitembasics | 1               | 0                |
      | sapopuodatasapapimaterialstocksrvs      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Segment on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/segment

Monitor traffic, conversion and tracking integrity from Segment, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from Segment, and catch instrumentation breaks before decisions are made on bad data.

[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=segment)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="10">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (11 signals)">
        | Signal                      | Alert behaviour  | What it tracks                                                                           |
        | --------------------------- | ---------------- | ---------------------------------------------------------------------------------------- |
        | **Avg Session Duration**    | Merchant rule    | Mean time between first and last event in a derived session.                             |
        | **Goal Completions**        | Merchant rule    | Count of Order Completed (or configured goal) events in the window.                      |
        | **New Users**               | Merchant rule    | Profiles first seen within the window.                                                   |
        | **Pageviews per Session**   | Merchant rule    | Page events per derived session - depth-of-visit signal.                                 |
        | **Real-Time Users**         | Merchant rule    | Profiles with an event in the last few minutes - live activity pulse.                    |
        | **Returning Users**         | Merchant rule    | Profiles seen in the window whose first-seen predates it.                                |
        | **Session Conversion Rate** | Alert band 3 / 1 | Converting sessions / total sessions - gauge (good >2%, warn \<1%).                      |
        | **Sessions**                | Merchant rule    | Sessions derived from page/track events grouped per identity (30-min inactivity window). |
        | **Top Pages**               | Merchant rule    | Most-viewed pages by event count (context.page.url).                                     |
        | **Top Traffic Sources**     | Merchant rule    | Top referrers / UTM sources by session (context.page.referrer).                          |
        | **Users**                   | Merchant rule    | Distinct identified + anonymous profiles seen in the window.                             |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                                             |
        | ------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
        | **Bounce Rate**                                   | Alert band 40 / 60 | Share of single-page sessions - gauge\_inverse (good \<40%, warn >60%).                                                    |
        | **Cart Abandonment Rate**                         | Alert band 65 / 85 | Sessions with Product Added but no Order Completed - gauge\_inverse (good \<60%, warn >75%).                               |
        | **Segment Session Conversion vs Ecom Conversion** | Alert band 3 / 1   | Where Segment says users convert vs where the platform records orders - surfaces broken destinations and attribution gaps. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (10)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Key events not configured (purchase event firing but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based report and any ad spend optimised against this tool's conversion signal is blind until this is fixed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-003`
      </Accordion>

      <Accordion title="Attribution divergence with ecommerce platform > 25% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ATTR-001, SEG05`
      </Accordion>

      <Accordion title="Cart Abandonment Above Ceiling">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Climbing cart abandonment concentrates revenue loss at the final step; shipping surprises, payment friction and errors are the usual culprits.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SEG04`
      </Accordion>

      <Accordion title="Cart abandonment rate above 75%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, so this is lost revenue that was nearly captured, not cold traffic that never showed interest.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-CART-001`
      </Accordion>

      <Accordion title="Core Ecommerce Event Stopped Flowing">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        A core ecommerce event that stopped firing blinds every downstream report and automation that depends on it, and the gap is invisible until someone looks for the data.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SEG01`
      </Accordion>

      <Accordion title="Session Conversion Rate Below Floor">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Session conversion below the floor while traffic holds means the store is buying visits it cannot convert; the cause is usually specific and findable.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SEG02`
      </Accordion>

      <Accordion title="Session conversion rate below 1%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, not buying more visitors who will convert at the same low rate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-002`
      </Accordion>

      <Accordion title="Average engagement time below 30 seconds">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so traffic that looks healthy in a session count is not translating into attention.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-ENGAGE-001`
      </Accordion>

      <Accordion title="Bounce Rate Spike">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A bounce-rate spike after a release or campaign change is the earliest cheap warning that something on the landing experience broke.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SEG03`
      </Accordion>

      <Accordion title="Bounce rate above 70% over 30d">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those visits was still a cost (ad spend, content effort, SEO ranking) that produced no second page view.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ANALYTICS-TRACK-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **0 write** operations across spacecollectionuserprofiles, spacecollectionuserprofileevents, spacecollectionuserprofiletraits, v1betaworkspaces on Segment. 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=segment)

    #### Ready to build your first Segment 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                         | Read operations | Write operations |
      | -------------------------------- | --------------- | ---------------- |
      | spacecollectionuserprofiles      | 1               | 0                |
      | spacecollectionuserprofileevents | 1               | 0                |
      | spacecollectionuserprofiletraits | 1               | 0                |
      | v1betaworkspaces                 | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# SendGrid on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sendgrid

Monitor email revenue and deliverability for SendGrid, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

Monitor email revenue and deliverability for SendGrid, catch broken automations early, and keep lifecycle marketing accountable to store outcomes.

[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=sendgrid)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="13">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="13">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                 |
        | ----------------------------- | ------------------ | ------------------------------------------------------------------------------ |
        | **Active Subscribers (Est.)** | Merchant rule      | Estimated subscribed, reachable contacts.                                      |
        | **Email Open Rate**           | Alert band 20 / 10 | Apple Mail Privacy inflates this - pair with click-to-open for a truer signal. |
        | **Flow Count Summary**        | Merchant rule      | How many Automations exist on the account.                                     |
        | **Flow Status Breakdown**     | Merchant rule      | Automations split by status (activated, draft, deactivated).                   |
        | **Flow Trigger Types**        | Merchant rule      | Automations grouped by what triggers them.                                     |
        | **Flows List**                | Merchant rule      | Every SendGrid Automation and its current status.                              |
        | **List Count**                | Merchant rule      | Number of contact lists on the account.                                        |
        | **List Health Summary**       | Merchant rule      | Total reachable members across all lists.                                      |
        | **Lists Overview**            | Merchant rule      | Every contact list with its member count.                                      |
        | **Placed Orders Total**       | Merchant rule      | Orders attributed to SendGrid email in the window.                             |
        | **Segments Overview**         | Merchant rule      | Saved segments and their sizes.                                                |
        | **Top Lists by Name**         | Merchant rule      | Largest contact lists by member count.                                         |
        | **Total Sends**               | Merchant rule      | Total emails requested across all sends in the window.                         |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                 | Alert behaviour      | What it tracks                                                                                        |
        | -------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------- |
        | **Abandoned-Cart Recovery Value**      | Watch only           | \$/30D recovered by the abandoned-cart automation. Goes to zero if the automation is in draft (SG02). |
        | **Bounce Rate**                        | Alert band 2 / 5     | Share of sends that bounced. Rising bounces hurt sender reputation. Audit SG04 fires here.            |
        | **Delivery Rate**                      | Alert band 98 / 95   | Share of sends accepted by the inbox provider. Below 95% needs attention. SG01 fires.                 |
        | **Email Health KPIs**                  | Merchant rule        | Delivered, bounced and unsubscribed at a glance, your deliverability vitals.                          |
        | **Email Share of Total Store Revenue** | Merchant rule        | Healthy DTC ranges 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk.      |
        | **Engagement Funnel**                  | Merchant rule        | Requested → Delivered → Opened → Clicked. Drop-offs expose deliverability vs content weakness.        |
        | **Refund Rate**                        | Merchant rule        | Share of attributed orders later refunded.                                                            |
        | **Spam Complaint Rate**                | Alert band 0.1 / 0.3 | Above 0.1% Gmail starts marking the sender domain. SG03 fires; investigate immediately.               |
        | **Unsubscribe Rate**                   | Alert band 0.5 / 2   | Unsubscribes per send. A spike signals list fatigue or off-target content.                            |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                              |
        | ----------------------------- | ------------------ | --------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule      | Single Sends grouped by status (triggered, draft, scheduled).               |
        | **Checkout-to-Order Rate**    | Merchant rule      | Share of started checkouts that became paid orders.                         |
        | **Click-to-Open Rate**        | Alert band 10 / 3  | Truer engagement signal than open rate - proxy filtering doesn't pre-click. |
        | **Conversion Rate**           | Merchant rule      | Orders as a share of emails sent. Ties send volume to revenue.              |
        | **Email Click Rate**          | Alert band 2 / 0.5 | Unique clicks as a share of delivered. The clearest engagement signal.      |
        | **Revenue per Recipient**     | Merchant rule      | Revenue divided by emails sent. What each address is worth per send.        |
        | **Revenue per Send**          | Merchant rule      | Revenue divided by emails sent, the efficiency of each send.                |
        | **Total Revenue**             | Merchant rule      | Placed-order revenue attributed to SendGrid email in the conversion window. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                    |
        | --------------------- | --------------- | ----------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts begun from email clicks, where the platform reports it. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (13)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Spam complaint rate > 0.1%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to damage sender reputation with mailbox providers; a rate this high can get future campaigns throttled or routed to spam even for recipients who never complained, which drags down deliverability for the whole list, not just the segment that complained.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-002`
      </Accordion>

      <Accordion title="Spam complaint rate above ISP threshold">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        Spam complaints are the fastest way to destroy sender reputation. Above roughly 0.1 percent, providers start routing campaigns to junk for everyone, not just complainers, cutting email revenue silently.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SG03`
      </Accordion>

      <Accordion title="Abandoned-cart / welcome automation not activated">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Automations that are switched off or erroring stop producing revenue silently; abandoned-cart, welcome and win-back flows are typically the highest-earning sends a store has.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SG02`
      </Accordion>

      <Accordion title="Abandoned-cart flow not live">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Abandoned-cart recovery is usually the single highest-ROI automation in email: high-intent shoppers who nearly bought are contacted at exactly the right moment. Without it they are never contacted at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-001`
      </Accordion>

      <Accordion title="Bounce rate > 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is bouncing. Beyond the immediate lost reach, mailbox providers watch bounce rate as a sender-reputation signal, and a rate this high risks future emails, even to good addresses, landing in spam instead of the inbox.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-001`
      </Accordion>

      <Accordion title="Delivery rate < 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 20 emails is not reaching an inbox at all, whether blocked, bounced, or filtered. Every campaign, promotion or transactional email built on this list is reaching a materially smaller audience than the send count suggests.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-DEL-003`
      </Accordion>

      <Accordion title="Delivery rate below 95%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        When more than 1 in 20 emails fails to arrive at all, every campaign, promotion and transactional message built on that list underperforms, and the gap compounds as the list grows.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SG01`
      </Accordion>

      <Accordion title="Email bounce rate above 5%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Bounced emails never reach the customer, and past roughly 5% mailbox providers treat the sender as risky, dragging down delivery of every future campaign including the ones that make money.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SG04`
      </Accordion>

      <Accordion title="Sender domain authentication (SPF/DKIM/DMARC) not verified">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Without SPF, DKIM and DMARC alignment, mailbox providers cannot verify the sender, so even good campaigns get filtered; authentication is a precondition for inbox placement.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `SG05`
      </Accordion>

      <Accordion title="Welcome flow not live">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-002`
      </Accordion>

      <Accordion title="Limited lists / segmentation">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SG06`
      </Accordion>

      <Accordion title="Limited segmentation , fewer than 3 segments">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Report only

        With fewer than 3 segments, campaigns are almost certainly going to the entire list every time, new customers and loyal repeat buyers, engaged subscribers and people who have not opened an email in a year, all treated identically. That flattens response rates and raises the same unsubscribe and spam

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-LIST-001`
      </Accordion>

      <Accordion title="Too many draft flows (> 3) , launch tech debt">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        More than 3 automation flows are built but never turned on. Each one represents planned revenue, welcome series, replenishment reminders, win-back campaigns, that is sitting unused; the work to build them already happened, so the only thing standing between the store and that revenue is publishing t

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `EM-FLOW-004`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **11 read** and **2 write** operations across marketingautomations, marketingcontactcounts, marketinglists, marketinglistcontacts, marketingsegments, marketingsinglesends on SendGrid. 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=sendgrid)

    #### Ready to build your first SendGrid 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | marketingautomations   | 1               | 1                |
      | marketingcontactcounts | 1               | 0                |
      | marketinglists         | 1               | 0                |
      | marketinglistcontacts  | 0               | 1                |
      | marketingsegments      | 1               | 0                |
      | marketingsinglesends   | 1               | 0                |
      | scopes                 | 1               | 0                |
      | stats                  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Sendle on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sendle

Monitor Sendle delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Sendle delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=sendle)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (24 signals)">
        | Signal                                         | Alert behaviour  | What it tracks                                                                                                                                         |
        | ---------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Error Rate**                             | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Shipping Cost**                          | Merchant rule    | Description pending editorial review; the signal is live.                                                                                              |
        | **Carbon Offset Total (grams CO2)**            | Watch only       | Sendle is 100% carbon-neutral; per-shipment offset reporting feeds customer-facing sustainability badge.                                               |
        | **Claim Value (open)**                         | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Cost Per Shipment Trend**                    | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Cost by Zone**                               | Watch only       | Cost by Zone.                                                                                                                                          |
        | **Cost per Parcel by Zone (3 AU / 5 US)**      | Watch only       | Sendle prices by zone (metro / regional in AU; 5-zone US tier). Mix shape drives total shipping spend.                                                 |
        | **Days to Token Expiry**                       | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Exception Rate**                             | Alert band 2 / 5 | Description pending editorial review; the signal is live.                                                                                              |
        | **Flat-Rate Savings vs AusPost/USPS Baseline** | Watch only       | How much Sendle's flat-rate-by-zone model saved vs estimated AusPost / USPS cost for the same parcels. Sendle's ROI surfaces here.                     |
        | **High-Cost Shipment Outliers**                | Watch only       | High-Cost Shipment Outliers, broken down by row.                                                                                                       |
        | **Label Generation Success**                   | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Label Print Failures Spike**                 | Alert band 0 / 5 | Alerts for Label Print Failures Spike.                                                                                                                 |
        | **OTD by Route**                               | Watch only       | OTD by Route.                                                                                                                                          |
        | **Open Claims**                                | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Pickup Booking Success Rate**                | Merchant rule    | % of pickup bookings completed first attempt. Sendle's network depends on driver coverage; postcode-level coverage gaps surface here.                  |
        | **Pickup vs Drop-off Booking Mix**             | Watch only       | Pickup is more convenient (driver collects from merchant) but slightly higher cost. Drop-off uses Sendle's partner network (newsagents, post offices). |
        | **Returned to Sender**                         | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Route Volume Concentration**                 | Merchant rule    | Route Volume Concentration, compared across items.                                                                                                     |
        | **Sendle Premium Monthly Subscription ROI**    | Merchant rule    | Sendle Premium (\$30/mo) gives volume discounts. Card shows whether monthly subscription cost is recouped by per-parcel savings.                       |
        | **Shipments**                                  | Merchant rule    | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments Over Time**                        | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments by Destination**                   | Watch only       | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments by Service**                       | Watch only       | Shipments by Service.                                                                                                                                  |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                           |
        | -------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------- |
        | **Failed Deliveries**                              | Merchant rule     | Description pending editorial review; the signal is live.                                                |
        | **Orders with Dispatch SLA Missed**                | Merchant rule     | Description pending editorial review; the signal is live.                                                |
        | **Pickup Booking Failures OR Dispatch SLA Breach** | Merchant rule     | Sendle's network depends on pickup-driver coverage , failed pickups stall the whole queue.               |
        | **Return Rate by Sendle Product Code**             | Merchant rule     | Description pending editorial review; the signal is live.                                                |
        | **Sendle vs AusPost / EasyPost by Zone**           | Merchant rule     | Sendle's flat-rate vs competitor variable rates. Surface zones where flat-rate has lost competitiveness. |
        | **Shipments with Tracking-Event Gap**              | Alert band 0 / 10 | Shipments with Tracking-Event Gap, broken down by row.                                                   |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                            |
        | ------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live. |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live. |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live. |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                                    | Alert behaviour | What it tracks                                    |
        | ----------------------------------------- | --------------- | ------------------------------------------------- |
        | **Sendle Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for Sendle Tracking API Unavailable / 5xx. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **2 write** operations across orders, returns, trackings on Sendle. 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=sendle)

    #### Ready to build your first Sendle 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.

    <Accordion title="Browse the operations you can build with">
      | Resource  | Read operations | Write operations |
      | --------- | --------------- | ---------------- |
      | orders    | 1               | 1                |
      | returns   | 0               | 1                |
      | trackings | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Sentry on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sentry

Monitor Sentry health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Sentry health, cost and reliability signals, and catch incidents and runaway spend early.

[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=sentry)

<CardGroup>
  <Card title="19">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (19)">
    ### Monitor performance

    19 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (10 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                                                 |
        | ---------------------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Watch only                   | Alerts a human has acknowledged - separates 'someone is on it' from 'firing into the void'.                    |
        | **Alerts Firing**            | Alert band 0 / 1             | Metric-alert rules currently in the firing state - the live count of things breaching their threshold.         |
        | **Incidents Resolved (24h)** | Watch only                   | Incidents closed in the last 24h - throughput of the on-call response, not just the backlog size.              |
        | **Mean Time To Acknowledge** | Merchant rule                | Average gap from incident trigger to first human acknowledgement. The page-fatigue early-warning.              |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Average incident-open duration. Creeping MTTR is the canary for accumulating tech debt or thin on-call cover.  |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Crash-free / availability attainment against the SLA target. Below 99.5% means the budget is being eaten.      |
        | **Services Degraded**        | Alert band 0 / 3             | Projects breaching a warning threshold but not down - the early-warning column before an outage.               |
        | **Services Down**            | Alert band 0 / 1             | Projects with crash-free rate below the critical floor or no events flowing. Any non-zero value is a page.     |
        | **Top Alerting Services**    | Watch only                   | Projects ranked by incident/alert volume - where on-call attention and reliability investment should go first. |
        | **Top Error Types**          | Watch only                   | Error classes ranked by occurrence count - the fix-this-first list, ordered by blast radius.                   |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                   | Alert behaviour       | What it tracks                                                                                                   |
        | ------------------------ | --------------------- | ---------------------------------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.95 / 0.7 | Sentry performance Apdex over the satisfaction threshold. Below 0.85 = users feeling the slowness.               |
        | **Avg Response Time**    | Alert band 200 / 1000 | Mean transaction duration across the org/project. Baseline for latency-regression detection.                     |
        | **Error Rate**           | Alert band 0.5 / 2    | Share of transactions/requests returning errors, from Sentry events. Rising = a release or dependency regressed. |
        | **Throughput (req/min)** | Alert band 0 / -10    | Transactions per minute. A sustained drop can mean an outage upstream or a broken instrumentation path.          |
        | **p95 Latency**          | Alert band 200 / 1000 | 95th-percentile transaction duration - the slow tail most customers never see but the worst ones do.             |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                     | Alert behaviour       | What it tracks                                                                                                                                          |
        | -------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Revenue at Risk (live)** | Merchant rule         | Sentry incident/error state × commerce-sibling baseline = \$/min at risk while the error rate is elevated. The single most-valuable card in this manife |
        | **p99 Latency**            | Alert band 200 / 1000 | 99th-percentile transaction duration - the worst-case experience and the timeout-risk signal.                                                           |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal             | Alert behaviour  | What it tracks                                                                                               |
        | ------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Incidents Open** | Alert band 0 / 1 | Open metric-alert incidents right now. Any open incident on a checkout-adjacent project is revenue-relevant. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal               | Alert behaviour | What it tracks                                                                                    |
        | -------------------- | --------------- | ------------------------------------------------------------------------------------------------- |
        | **Services Healthy** | Watch only      | Count of projects whose error rate + crash-free rate are inside healthy bounds. The green column. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **1 write** operations across organizationissues, organizations, organizationalertrules, organizationevents, organizationeventstats, organizationincidents on Sentry. 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=sentry)

    #### Ready to build your first Sentry 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | organizationissues     | 1               | 1                |
      | organizations          | 1               | 0                |
      | organizationalertrules | 1               | 0                |
      | organizationevents     | 1               | 0                |
      | organizationeventstats | 1               | 0                |
      | organizationincidents  | 1               | 0                |
      | organizationprojects   | 1               | 0                |
      | organizationsessions   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ShipTheory on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/ship-theory

Monitor ShipTheory delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor ShipTheory delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=ship-theory)

<CardGroup>
  <Card title="26">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (26)">
    ### Monitor performance

    26 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                                    |
        | --------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
        | **API Error Rate**                | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Avg Shipping Cost**             | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Claim Value (open)**            | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Cost Per Shipment Trend**       | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Cost by Zone**                  | Watch only         | Cost by Zone.                                                                                                                     |
        | **Days to Token Expiry**          | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Exception Rate**                | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                                         |
        | **High-Cost Shipment Outliers**   | Watch only         | High-Cost Shipment Outliers, broken down by row.                                                                                  |
        | **Label Generation Success**      | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Label-Generation Success Rate** | Alert band 99 / 95 | ShipTheory's core SLA - did label generation succeed? Below 98% directly blocks order despatch and is the most actionable signal. |
        | **OTD by Route**                  | Watch only         | OTD by Route.                                                                                                                     |
        | **Open Claims**                   | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Returned to Sender**            | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Route Volume Concentration**    | Merchant rule      | Route Volume Concentration, compared across items.                                                                                |
        | **Shipments**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                         |
        | **Shipments Over Time**           | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Shipments by Destination**      | Watch only         | Description pending editorial review; the signal is live.                                                                         |
        | **Shipments by Service**          | Watch only         | Shipments by Service.                                                                                                             |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                     |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------ |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                          |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                          |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                          |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                          |
        | **Sub-Carrier OTD Comparison**  | Alert band 95 / 90 | Side-by-side OTD comparison across ShipTheory's sub-carriers - feeds the carrier-renegotiation conversation. Hero. |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                           | Alert behaviour | What it tracks                                                                                                                                         |
        | -------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Labels Printed Not Collected** | Merchant rule   | Shipments that have a printed label but never made it onto a carrier manifest - lost revenue, often warehouse / collection-cutoff issues.              |
        | **Sub-Carrier Volume Mix**       | Watch only      | Volume split across ShipTheory's underlying carriers (Royal Mail / DPD / Hermes / Parcelforce) - the consolidation visibility ShipTheory exists to pro |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                            |
        | --------------------- | --------------- | --------------------------------------------------------- |
        | **Failed Deliveries** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **2 write** operations across shipments, accounts, tokens, trackings on ShipTheory. 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=ship-theory)

    #### Ready to build your first ShipTheory 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.

    <Accordion title="Browse the operations you can build with">
      | Resource  | Read operations | Write operations |
      | --------- | --------------- | ---------------- |
      | shipments | 1               | 1                |
      | accounts  | 1               | 0                |
      | tokens    | 0               | 1                |
      | trackings | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ShipBob on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/shipbob

Monitor ShipBob delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor ShipBob delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=shipbob)

<CardGroup>
  <Card title="79">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (79)">
    ### Monitor performance

    79 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (46 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                            |
        | ------------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Avg Delivery Time by Region**       | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Avg Fulfilment Time (hrs)**         | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Avg Shipping Time (days)**          | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Cost by Shipping Method**           | Watch only         | Cost by Shipping Method.                                  |
        | **Cost by Warehouse**                 | Watch only         | Cost by Warehouse.                                        |
        | **Days of Cover (avg)**               | Watch only         | Description pending editorial review; the signal is live. |
        | **Delivery Failure Alerts**           | Merchant rule      | Alerts for Delivery Failure Alerts.                       |
        | **Delivery Time Distribution**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Fulfilment Cost per Order**         | Merchant rule      | Fulfilment Cost per Order, compared across items.         |
        | **Fulfilment Delay Watchlist**        | Merchant rule      | Alerts for Fulfilment Delay Watchlist.                    |
        | **Fulfilment Rate**                   | Merchant rule      | Description pending editorial review; the signal is live. |
        | **High Return Rate Alerts**           | Merchant rule      | Alerts for High Return Rate Alerts.                       |
        | **High-Cost Shipment Outliers**       | Merchant rule      | High-Cost Shipment Outliers, broken down by row.          |
        | **International vs Domestic**         | Merchant rule      | International vs Domestic, shown by share.                |
        | **Inventory Ageing (days on hand)**   | Merchant rule      | Inventory Ageing (days on hand), compared across items.   |
        | **Inventory Distribution Heatmap**    | Watch only         | Description pending editorial review; the signal is live. |
        | **Inventory Levels by SKU (Top 20)**  | Watch only         | Inventory Levels by SKU (Top 20).                         |
        | **Inventory Turnover Proxy**          | Merchant rule      | Inventory Turnover Proxy, compared across items.          |
        | **Inventory by Warehouse**            | Watch only         | Description pending editorial review; the signal is live. |
        | **On-Time Delivery Rate**             | Merchant rule      | Description pending editorial review; the signal is live. |
        | **On-Time Delivery Trend**            | Alert band 95 / 90 | Description pending editorial review; the signal is live. |
        | **Orders Breaching SLA**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Orders Exceeding SLA**              | Alert band 0 / 5   | Description pending editorial review; the signal is live. |
        | **Orders Fulfilled**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **Orders Shipped Today vs Yesterday** | Merchant rule      | Orders Shipped Today vs Yesterday, compared across items. |
        | **Orders by Merchant**                | Watch only         | Orders by Merchant.                                       |
        | **Orders by Region (Geo)**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Pending Fulfilment Backlog**        | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Return Processing Time**            | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Return Rate**                       | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Return Reasons**                    | Merchant rule      | Return Reasons, compared across items.                    |
        | **Returns Volume Trend**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Returns by Region**                 | Watch only         | Description pending editorial review; the signal is live. |
        | **SLA Compliance**                    | Watch only         | Description pending editorial review; the signal is live. |
        | **SLA Compliance by Merchant**        | Alert band 95 / 85 | SLA Compliance by Merchant.                               |
        | **SLA by Warehouse**                  | Watch only         | SLA by Warehouse.                                         |
        | **Shipments per Day**                 | Watch only         | Shipments per Day over time.                              |
        | **Shipping Cost / Order**             | Watch only         | Description pending editorial review; the signal is live. |
        | **Shipping Cost Trend**               | Watch only         | Description pending editorial review; the signal is live. |
        | **Shipping Cost by Region**           | Watch only         | Description pending editorial review; the signal is live. |
        | **Shipping Cost per Order**           | Alert band 5 / 15  | Shipping Cost per Order over time.                        |
        | **Shipping Delay Alerts**             | Merchant rule      | Alerts for Shipping Delay Alerts.                         |
        | **Shipping Delays by Warehouse**      | Merchant rule      | Shipping Delays by Warehouse.                             |
        | **Stock vs Demand Forecast**          | Merchant rule      | Stock vs Demand Forecast over time.                       |
        | **Tracking Status Breakdown**         | Merchant rule      | Tracking Status Breakdown, stage by stage.                |
        | **Warehouse Backlog Alerts**          | Merchant rule      | Alerts for Warehouse Backlog Alerts.                      |
      </Accordion>

      <Accordion title="Customer experience (22 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                            |
        | -------------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Avg Fulfilment Time by Warehouse**   | Alert band 24 / 72 | Avg Fulfilment Time by Warehouse.                         |
        | **Carrier Performance Comparison**     | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Delayed Orders**                     | Alert band 0 / 5   | Delayed Orders, compared across items.                    |
        | **Delivery Performance by Merchant**   | Alert band 95 / 90 | Delivery Performance by Merchant.                         |
        | **Fulfilment Performance by Merchant** | Alert band 95 / 85 | Fulfilment Performance by Merchant.                       |
        | **Fulfilment Time Trend**              | Alert band 24 / 72 | Description pending editorial review; the signal is live. |
        | **Last-Mile Performance**              | Merchant rule      | Last-Mile Performance, compared across items.             |
        | **Orders Fulfilled by Warehouse**      | Watch only         | Orders Fulfilled by Warehouse.                            |
        | **Orders Fulfilled per Day**           | Merchant rule      | Orders Fulfilled per Day over time.                       |
        | **Orders by Fulfilment Status**        | Merchant rule      | Orders by Fulfilment Status.                              |
        | **Orders by Region**                   | Watch only         | Description pending editorial review; the signal is live. |
        | **Orders by Shipping Method**          | Watch only         | Orders by Shipping Method.                                |
        | **Orders by Warehouse**                | Watch only         | Orders by Warehouse.                                      |
        | **Pending vs Fulfilled by Day**        | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Pick/Pack Time by Warehouse**        | Merchant rule      | Pick/Pack Time by Warehouse.                              |
        | **SLA Compliance by Warehouse**        | Alert band 95 / 85 | SLA Compliance by Warehouse.                              |
        | **Shipping Method Performance**        | Watch only         | Description pending editorial review; the signal is live. |
        | **Warehouse Backlog (Current)**        | Merchant rule      | Warehouse Backlog (Current), compared across items.       |
        | **Warehouse Capacity Utilisation**     | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Warehouse Error Rate**               | Merchant rule      | Warehouse Error Rate, compared across items.              |
        | **Warehouse Proximity Performance**    | Watch only         | Description pending editorial review; the signal is live. |
        | **Warehouse Throughput Trend**         | Merchant rule      | Warehouse Throughput Trend.                               |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                             |
        | -------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------- |
        | **Inventory Risk by Merchant**   | Alert band 0 / 5  | Description pending editorial review; the signal is live.                                                  |
        | **Low-Stock Alerts**             | Alert band 5 / 50 | Low-Stock Alerts, broken down by row.                                                                      |
        | **Low-Stock SKUs**               | Watch only        | Description pending editorial review; the signal is live.                                                  |
        | **Operational Health Score**     | Merchant rule     | Composite , fulfil rate × OTD × SLA × inverse stockout × inverse return rate. The single number for a CXO. |
        | **Out-of-Stock Products**        | Alert band 0 / 5  | Description pending editorial review; the signal is live.                                                  |
        | **Out-of-Stock SKUs**            | Watch only        | Description pending editorial review; the signal is live.                                                  |
        | **Overstock Risk**               | Merchant rule     | Overstock Risk, broken down by row.                                                                        |
        | **Stockout Alerts**              | Alert band 0 / 5  | Alerts for Stockout Alerts.                                                                                |
        | **Stockouts With Active Demand** | Watch only        | OOS where committed > 0 , actively losing sales.                                                           |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                 | Alert behaviour | What it tracks      |
        | ---------------------- | --------------- | ------------------- |
        | **Returns by Product** | Merchant rule   | Returns by Product. |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                    | Alert behaviour | What it tracks                                            |
        | ------------------------- | --------------- | --------------------------------------------------------- |
        | **Cost vs Revenue Proxy** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        With invalid credentials the tool has stopped collecting entirely; every metric that depends on it is silently stale.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FUL-AUTH-001`
      </Accordion>

      <Accordion title="Stockout with active demand (OOS where committed > 0)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stockouts on items with committed demand are immediate lost sales plus cancellation work; the highest-velocity SKUs deserve the earliest warning.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `FUL-OOS-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        On-time delivery below 90 percent erodes repeat purchase intent, the cheapest revenue a store has.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FUL-OTD-001`
      </Accordion>

      <Accordion title="Orders breaching SLA in flight (any > 0)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Orders breaching SLA while still in flight can often be rescued if flagged now; after delivery they become refunds and complaints instead.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `FUL-SLA-001`
      </Accordion>

      <Accordion title="SLA compliance below 90%">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        SLA compliance below 90 percent means late delivery is systemic, not incidental; contractual penalties and churn both follow.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FUL-SLA-002`
      </Accordion>

      <Accordion title="Carrier OTD below 85%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A carrier delivering on time less than 85 percent of the time is damaging the store's promise; reroute volume or renegotiate.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FUL-CARRIER-001`
      </Accordion>

      <Accordion title="Return rate above 8%">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        Returns above 8 percent usually concentrate in specific products or size ranges; finding the cluster turns a cost centre into a fixable defect.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `FUL-RETURN-001`
      </Accordion>

      <Accordion title="Shipping cost per order up >10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Shipping cost per order rising faster than basket value quietly eats margin on every single shipment.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `FUL-COST-001`
      </Accordion>

      <Accordion title="Warehouse capacity utilisation > 85%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Warehouse utilisation above 85 percent leaves no surge headroom; peak days start breaching SLA the moment volume spikes.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `FUL-FC-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **1 write** operations across orders, channels, inventorys, locations, products, receivings on ShipBob. 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=shipbob)

    #### Ready to build your first ShipBob 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.

    <Accordion title="Browse the operations you can build with">
      | Resource   | Read operations | Write operations |
      | ---------- | --------------- | ---------------- |
      | orders     | 1               | 1                |
      | channels   | 1               | 0                |
      | inventorys | 1               | 0                |
      | locations  | 1               | 0                |
      | products   | 1               | 0                |
      | receivings | 1               | 0                |
      | returns    | 1               | 0                |
      | shipments  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Shippo on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/shippo

Monitor Shippo delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor Shippo delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=shippo)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (23 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                       |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Error Rate**                          | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Avg Shipping Cost**                       | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Claim Value (open)**                      | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Cost Per Shipment Trend**                 | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Cost by Zone**                            | Watch only         | Cost by Zone.                                                                                                                        |
        | **Days to Token Expiry**                    | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Dispatch SLA Breached on N Orders Today** | Merchant rule      | Alerts for Dispatch SLA Breached on N Orders Today.                                                                                  |
        | **Exception Rate**                          | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                                            |
        | **High-Cost Shipment Outliers**             | Watch only         | High-Cost Shipment Outliers, broken down by row.                                                                                     |
        | **Inactive Carrier Accounts**               | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Label Failure Rate by Carrier**           | Alert band 1 / 2   | Per-underlying-carrier label-creation failure rate via Shippo. Surface which credential needs refresh.                               |
        | **Label Generation Success**                | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Label Print Failures Spike**              | Alert band 99 / 95 | Alerts for Label Print Failures Spike.                                                                                               |
        | **OTD by Route**                            | Watch only         | OTD by Route.                                                                                                                        |
        | **Open Claims**                             | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Returned to Sender**                      | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Returns Label Generation Failure Rate**   | Alert band 1 / 2   | % of /shipments/?metadata=return requests failing. Spike = carrier API down OR returns rate-shopping logic broken , RMA flow stalls. |
        | **Route Volume Concentration**              | Watch only         | Route Volume Concentration, compared across items.                                                                                   |
        | **Shipments**                               | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Shipments Over Time**                     | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Shipments by Destination**                | Watch only         | Description pending editorial review; the signal is live.                                                                            |
        | **Shipments by Service**                    | Watch only         | Shipments by Service.                                                                                                                |
        | **Shipments by Underlying Carrier**         | Watch only         | Shipments by Underlying Carrier.                                                                                                     |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                                        |
        | ------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                                                             |
        | **Orca Predicted-ETA Accuracy** | Merchant rule      | % of shipments where actual delivery matched Orca's checkout-promised ETA within +/- 1 day. Below 85% = systematic over-promising at checkout, drives |
        | **Rates Cache Staleness**       | Merchant rule      | Shippo caches rates per-route for performance. Stale cache = wrong shipping cost shown at checkout. Bust threshold.                                   |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                        | Alert behaviour   | What it tracks                                              |
        | --------------------------------------------- | ----------------- | ----------------------------------------------------------- |
        | **Cost per Parcel by Zone vs Direct-Carrier** | Merchant rule     | Cost per Parcel by Zone vs Direct-Carrier.                  |
        | **Failed Deliveries**                         | Merchant rule     | Description pending editorial review; the signal is live.   |
        | **Orders with Carrier Dispatch SLA Missed**   | Merchant rule     | Description pending editorial review; the signal is live.   |
        | **Return Rate by Underlying Carrier**         | Merchant rule     | Description pending editorial review; the signal is live.   |
        | **Shipments with Tracking-Event Gap >24h**    | Alert band 0 / 10 | Shipments with Tracking-Event Gap >24h, broken down by row. |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                             | Alert behaviour | What it tracks                                                                                          |
        | ---------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------- |
        | **Returns Label Volume**           | Watch only      | Daily returns labels generated via Shippo Returns API. Trend shapes reverse-logistics cost forecasting. |
        | **Tracking API Unavailable / 5xx** | Merchant rule   | Alerts for Tracking API Unavailable / 5xx.                                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across shipments, accounts, carrieraccounts, tracks on Shippo. 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=shippo)

    #### Ready to build your first Shippo 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | shipments       | 1               | 1                |
      | accounts        | 1               | 0                |
      | carrieraccounts | 1               | 0                |
      | tracks          | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# ShippyPro on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/shippy-pro

Monitor ShippyPro delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor ShippyPro delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=shippy-pro)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (18 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                              |
        | --------------------------------- | ------------------ | --------------------------------------------------------------------------- |
        | **API Error Rate**                | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Avg Shipping Cost**             | Merchant rule      | Description pending editorial review; the signal is live.                   |
        | **Claim Value (open)**            | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Cost Per Shipment Trend**       | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Cost by Zone**                  | Watch only         | Cost by Zone.                                                               |
        | **Days to Token Expiry**          | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Exception Rate**                | Alert band 2 / 5   | Description pending editorial review; the signal is live.                   |
        | **High-Cost Shipment Outliers**   | Watch only         | High-Cost Shipment Outliers, broken down by row.                            |
        | **Label Generation Success**      | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Label-Generation Success Rate** | Alert band 99 / 95 | ShippyPro's core SLA - did label generation succeed across the carrier mix? |
        | **OTD by Route**                  | Watch only         | OTD by Route.                                                               |
        | **Open Claims**                   | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Returned to Sender**            | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Route Volume Concentration**    | Merchant rule      | Route Volume Concentration, compared across items.                          |
        | **Shipments**                     | Merchant rule      | Description pending editorial review; the signal is live.                   |
        | **Shipments Over Time**           | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Shipments by Destination**      | Watch only         | Description pending editorial review; the signal is live.                   |
        | **Shipments by Service**          | Watch only         | Shipments by Service.                                                       |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                            |
        | ------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live. |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live. |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live. |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                             | Alert behaviour    | What it tracks                                            |
        | ---------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Failed Deliveries**              | Merchant rule      | Description pending editorial review; the signal is live. |
        | **ShippyPro OTD by Sales Channel** | Alert band 95 / 90 | Per-channel ShippyPro OTD.                                |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                            | Alert behaviour | What it tracks                                                                                                                |
        | --------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------- |
        | **Rate-Shop Winner Distribution** | Watch only      | Which sub-carrier ShippyPro picked most often in the rate-shop. Visibility into which underlying carrier is delivering value. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across shipments, accounts, rates, trackings on ShippyPro. 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=shippy-pro)

    #### Ready to build your first ShippyPro 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.

    <Accordion title="Browse the operations you can build with">
      | Resource  | Read operations | Write operations |
      | --------- | --------------- | ---------------- |
      | shipments | 1               | 1                |
      | accounts  | 1               | 0                |
      | rates     | 1               | 0                |
      | trackings | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Shopify on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/shopify

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Shopify.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Shopify.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/shopify) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=shopify)

<CardGroup>
  <Card title="75">
    performance signals
  </Card>

  <Card title="47">
    automated checks
  </Card>

  <Card title="35">
    prepared fixes
  </Card>

  <Card title="58">
    proven workflows
  </Card>

  <Card title="701">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (75)">
    ### Monitor performance

    75 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (29 signals)">
        | Signal                             | Alert behaviour     | What it tracks                                            |
        | ---------------------------------- | ------------------- | --------------------------------------------------------- |
        | **AOV (ex-VAT)**                   | Watch only          | Description pending editorial review; the signal is live. |
        | **AOV with/without Discount**      | Watch only          | AOV with/without Discount, compared across items.         |
        | **Average Order Value**            | Merchant rule       | Average amount customers spend per order.                 |
        | **B2B Revenue**                    | Watch only          | Description pending editorial review; the signal is live. |
        | **B2C Revenue Only**               | Watch only          | Description pending editorial review; the signal is live. |
        | **Customer Acquisition Trend**     | Watch only          | New customer acquisition trend over time.                 |
        | **Discount % of Revenue**          | Merchant rule       | Discount value as a percentage of total revenue.          |
        | **Discounts Given Over Time**      | Watch only          | Description pending editorial review; the signal is live. |
        | **Marketplace Revenue**            | Watch only          | Description pending editorial review; the signal is live. |
        | **Missing SEO Title Count**        | Alert band 10 / 30  | Products missing SEO title metadata.                      |
        | **Peak Order Hours**               | Watch only          | Peak Order Hours, compared across items.                  |
        | **Repeat Customer Rate**           | Alert band 25 / 10  | Percentage of customers who ordered more than once.       |
        | **Revenue Breakdown**              | Watch only          | Revenue Breakdown.                                        |
        | **Revenue Over Time**              | Watch only          | Revenue trend over the selected period.                   |
        | **Revenue by Channel**             | Watch only          | Revenue by Channel.                                       |
        | **Revenue by Day of Week**         | Watch only          | Revenue by Day of Week.                                   |
        | **Revenue by Hour**                | Watch only          | Revenue by Hour.                                          |
        | **Revenue by Payment Gateway**     | Watch only          | Revenue by Payment Gateway.                               |
        | **Revenue by Sales Channel (Tag)** | Watch only          | Revenue by Sales Channel (Tag).                           |
        | **Shipping Cost as % of Revenue**  | Alert band 5 / 15   | Description pending editorial review; the signal is live. |
        | **Top Discount Codes**             | Watch only          | Top Discount Codes, compared across items.                |
        | **Top Products by Revenue**        | Watch only          | Best-selling products ranked by revenue.                  |
        | **Total Discount Used**            | Watch only          | Total discount amount applied across all orders.          |
        | **Total Orders**                   | Merchant rule       | Number of orders placed in the selected period.           |
        | **Total Revenue**                  | Alert band 10 / -10 | Description pending editorial review; the signal is live. |
        | **Total Revenue (ex-VAT)**         | Watch only          | Description pending editorial review; the signal is live. |
        | **Total Shipping Revenue**         | Watch only          | Total shipping charges collected.                         |
        | **Total Tax Collected**            | Watch only          | Total tax collected across all orders.                    |
        | **Weekend vs Weekday**             | Watch only          | Weekend vs Weekday, shown by share.                       |
      </Accordion>

      <Accordion title="Run operations (26 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **AOV by Country**             | Watch only         | AOV by Country.                                           |
        | **Customer Order Frequency**   | Watch only         | Customer Order Frequency, compared across items.          |
        | **Customers with Zero Spend**  | Alert band 30 / 60 | Description pending editorial review; the signal is live. |
        | **Email Health**               | Alert band 95 / 80 | Description pending editorial review; the signal is live. |
        | **File Library by Type**       | Watch only         | File Library by Type.                                     |
        | **Financial Status Breakdown** | Watch only         | Orders grouped by payment/financial status.               |
        | **Free vs Paid Shipping**      | Watch only         | Free vs Paid Shipping, shown by share.                    |
        | **Fulfillment Rate**           | Alert band 95 / 90 | Percentage of orders successfully fulfilled.              |
        | **Fulfillment Rate Over Time** | Watch only         | Description pending editorial review; the signal is live. |
        | **Fulfillment Status**         | Watch only         | Distribution of orders by fulfillment status.             |
        | **Inventory Distribution**     | Watch only         | Inventory Distribution, compared across items.            |
        | **New Customers**              | Watch only         | New customer signups in the selected period.              |
        | **Order Fulfillment Status**   | Watch only         | Order Fulfillment Status, shown by share.                 |
        | **Order Value Segments**       | Watch only         | Order Value Segments, shown by share.                     |
        | **Orders Over Time**           | Watch only         | Order volume trend over the selected period.              |
        | **Orders by Country**          | Watch only         | Orders by Country.                                        |
        | **Payment Methods**            | Watch only         | Distribution of orders by payment method.                 |
        | **Return Status**              | Watch only         | Return Status, shown by share.                            |
        | **Shipping Methods**           | Watch only         | Shipping Methods, shown by share.                         |
        | **Store Health Score**         | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Tax Collected Over Time**    | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Cities by Orders**       | Watch only         | Cities generating the most orders.                        |
        | **Top Customers**              | Watch only         | Top Customers, compared across items.                     |
        | **Unfulfilled Orders**         | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Unique Customers**           | Watch only         | Number of unique customers who placed orders.             |
        | **Unverified Email Customers** | Merchant rule      | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (11 signals)">
        | Signal                                              | Alert behaviour  | What it tracks                                            |
        | --------------------------------------------------- | ---------------- | --------------------------------------------------------- |
        | **Cancellation Rate**                               | Alert band 1 / 3 | Percentage of orders cancelled before shipping.           |
        | **Cancelled Orders Over Time**                      | Watch only       | Description pending editorial review; the signal is live. |
        | **Customer Churn Risk**                             | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Failed Orders Count**                             | Watch only       | Description pending editorial review; the signal is live. |
        | **Failed Orders Value**                             | Watch only       | Description pending editorial review; the signal is live. |
        | **Products Fully Out of Stock (Oversell Excluded)** | Merchant rule    | Description pending editorial review; the signal is live. |
        | **Refund Rate**                                     | Alert band 2 / 5 | Percentage of orders that were refunded.                  |
        | **Refund Value**                                    | Watch only       | Total monetary value of refunds issued.                   |
        | **Refunded Orders**                                 | Watch only       | Number of orders with full refunds.                       |
        | **Refunds Over Time**                               | Watch only       | Description pending editorial review; the signal is live. |
        | **Top Refunding Customers**                         | Watch only       | Top Refunding Customers, compared across items.           |
      </Accordion>

      <Accordion title="Catalogue quality (8 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                            |
        | -------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Collection/Category Count**    | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Product Status**               | Watch only         | Products grouped by active/draft status.                  |
        | **Products Missing Description** | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Products by Type**             | Watch only         | Product catalog breakdown by type.                        |
        | **Products by Vendor**           | Watch only         | Product catalog breakdown by vendor.                      |
        | **SKU Coverage**                 | Alert band 80 / 50 | Description pending editorial review; the signal is live. |
        | **Top Product Tags**             | Watch only         | Top Product Tags, compared across items.                  |
        | **Top SKUs**                     | Watch only         | Top SKUs, compared across items.                          |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                   | Alert behaviour | What it tracks                              |
        | ------------------------ | --------------- | ------------------------------------------- |
        | **Slow-Moving Products** | Watch only      | Products with the lowest sales performance. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (47)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="HTTPS Not Reachable">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        If the storefront is not cleanly reachable over HTTPS, browsers warn customers away and search engines demote the site; trust and traffic drop together.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SC01`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Sitemap Missing or Thin">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without a healthy sitemap, new and updated pages are discovered late or not at all, so products can launch invisible to search.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB03`
      </Accordion>

      <Accordion title="Storefront blocked by Cloudflare - audit cannot reach the store">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Cloudflare is challenging the auditor, so storefront checks cannot run at all; every dependent finding is suppressed rather than invented.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CF01`
      </Accordion>

      <Accordion title="Theme audit blocked by Cloudflare">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        The theme audit could not reach the storefront because Cloudflare is challenging automated access; theme findings are unavailable rather than guessed until access is allowed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `TH00`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Excessive CSS files loaded">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Prepared fix

        Excess CSS files block rendering while they download; consolidating them speeds first paint on every page.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH03`
      </Accordion>

      <Accordion title="Homepage SEO Elements Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        The homepage is the most-linked page on the store; missing titles or descriptions there squander the site's strongest ranking signals.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB05`
      </Accordion>

      <Accordion title="Images missing alt text">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Prepared fix

        Images without alt text are invisible to screen readers and to image search; accessibility risk and free traffic left unclaimed at the same time.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH07`
      </Accordion>

      <Accordion title="Limited or Missing Schema Markup">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Schema markup earns rich results (stars, prices, availability) that lift click-through; without it, listings look plainer than competitors on the same results page.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB04`
      </Accordion>

      <Accordion title="Missing Meta Descriptions">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Search engines improvise snippets for pages without meta descriptions; a written one lifts click-through on impressions the page already earns.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE01`
      </Accordion>

      <Accordion title="Missing Page Titles">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Page titles are the strongest single on-page ranking and click-through signal; missing ones waste impressions the store already gets.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE02`
      </Accordion>

      <Accordion title="Missing Product Images">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Prepared fix

        Products without images barely convert; shoppers skip listings they cannot see.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ01`
      </Accordion>

      <Accordion title="Mobile Viewport Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without a mobile viewport tag the store renders desktop-sized on phones; mobile shoppers pinch, zoom and leave.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB12`
      </Accordion>

      <Accordion title="Mobile responsiveness issues">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Prepared fix

        Layouts that break on mobile lose the majority of ecommerce traffic; most stores see well over half their sessions on phones.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH11`
      </Accordion>

      <Accordion title="No Reviews Platform Detected">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Visible reviews are one of the strongest conversion levers in ecommerce; a store with no social proof converts measurably worse on identical traffic.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB10`
      </Accordion>

      <Accordion title="No analytics tracking detected on storefront">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without analytics on the storefront, marketing and UX decisions run blind and no conversion diagnosis is possible downstream.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SC03`
      </Accordion>

      <Accordion title="Order cancellation/refund rate exceeds 5%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Cancellation plus refund above 5 percent of orders means a meaningful slice of won revenue is being handed back; the causes (stock, delivery promises, payment friction) are usually fixable once identified.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `OH01`
      </Accordion>

      <Accordion title="Product Page SEO Issues">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        Product pages are where buying-intent searches land; SEO gaps here cost clicks with direct revenue attached.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB06`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Store Logo: No store logo configured">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        A missing store logo makes transactional emails, invoices and search results look unfinished; small trust losses compound at checkout.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SC02`
      </Accordion>

      <Accordion title="Zero-Price Products">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Prepared fix

        A visible product priced at zero can be added to carts for free and makes the catalogue look broken; each one is either direct revenue leakage or an embarrassment in front of customers.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ02`
      </Accordion>

      <Accordion title="llms.txt Missing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Prepared fix

        AI assistants increasingly answer shopping questions; llms.txt tells them what the store is and which pages matter, the emerging AI-search equivalent of robots.txt.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB02`
      </Accordion>

      <Accordion title="Accessibility issues found">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Accessibility failures exclude customers and carry regulatory risk in a growing list of markets; the common fixes are cheap.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH12`
      </Accordion>

      <Accordion title="Excessive JavaScript files loaded">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Each extra JavaScript file adds a request and parse cost on every page view; script bloat is one of the most common causes of slow storefronts.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH01`
      </Accordion>

      <Accordion title="Font loading not optimized">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Fonts loading without font-display cause invisible text while they download; visitors stare at blank headings on slow connections.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH10`
      </Accordion>

      <Accordion title="High refund rate">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refund concentration is a direct margin leak and often clusters around specific products, suppliers or delivery windows, which makes it diagnosable and fixable.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `OH02`
      </Accordion>

      <Accordion title="Images missing lazy loading">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Images loading eagerly below the fold compete with the content the shopper actually sees first, inflating LCP and hurting Core Web Vitals rankings.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH02, TH08`
      </Accordion>

      <Accordion title="Long inline styles">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Very long inline styles bloat every page they appear on and defeat caching that external stylesheets would get for free.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH06`
      </Accordion>

      <Accordion title="Missing Product Weight">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Weight-based shipping cannot quote correctly for products without weights, causing checkout errors or mispriced delivery. Irrelevant for flat-rate stores, which is worth recording as a business rule so this never nags.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ04`
      </Accordion>

      <Accordion title="Missing SKUs">
        **Severity** low · **Outcome** Run operations · **Fix status** Prepared fix

        Missing SKUs break inventory reconciliation, courier manifests and marketplace feeds; the problems surface downstream where they are hardest to trace back.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ03`
      </Accordion>

      <Accordion title="Missing Security Headers">
        **Severity** low · **Outcome** Control risk and change · **Fix status** Prepared fix

        Missing security headers leave the storefront easier to attack through clickjacking and script injection, and are flagged by the scanners customers and partners run.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB07`
      </Accordion>

      <Accordion title="Missing Social Meta Tags">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without Open Graph and Twitter tags, shared links render as bare URLs; rich previews carry substantially higher click-through from social and chat.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB09`
      </Accordion>

      <Accordion title="Missing/Short Product Descriptions">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Thin or missing product descriptions hurt conversion on the page and long-tail search rankings off it.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `SE03`
      </Accordion>

      <Accordion title="No Inventory Tracking">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Without inventory tracking the store cannot warn about stockouts or overselling; every availability signal downstream of this is guesswork.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `IQ01`
      </Accordion>

      <Accordion title="No Remarketing Tags Detected">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Without remarketing tags, the roughly 97 percent of visitors who leave cannot be re-engaged, making every paid acquisition channel more expensive.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB11`
      </Accordion>

      <Accordion title="Out of Stock Still Visible">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        Shoppers landing on unavailable products bounce, and any paid or organic traffic pointed at them is wasted, unless visibility is deliberate (back-in-stock capture or SEO retention), which is worth recording as a business rule.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `IQ02`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>

      <Accordion title="Render-blocking scripts in <head>">
        **Severity** low · **Outcome** Customer experience · **Fix status** Prepared fix

        Scripts loaded in the head without defer block the page from rendering until they finish; moving or deferring them is one of the cheapest speed wins available.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH05`
      </Accordion>

      <Accordion title="Uncategorized Products">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Uncategorised products are unreachable through navigation and category landing pages; they only sell if a customer happens to search for them.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `CQ05`
      </Accordion>

      <Accordion title="console.log statements found in inline scripts">
        **Severity** low · **Outcome** Protect revenue · **Fix status** Prepared fix

        console.log calls in production scripts leak implementation detail and add noise; they usually indicate debug code that shipped by accident.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `TH04`
      </Accordion>

      <Accordion title="robots.txt Missing or Misconfigured">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        A missing or broken robots.txt can accidentally block crawlers from the whole store, or fail to steer them away from junk URLs that waste crawl budget.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB01`
      </Accordion>

      <Accordion title="Tech Stack Detected">
        **Severity** info · **Outcome** Run operations · **Fix status** Prepared fix

        Informational: the technologies detected on the storefront, used to tailor the other checks to the actual stack.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `PB08, TH09`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **249 read** and **452 write** operations across abandonedcheckouts, abandonedcheckoutscounts, abandonments, abandonmentbyabandonedcheckoutids, abandonmentupdateactivitiesdeliverystatuses, apps on Shopify. 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=shopify)

    #### Proven workflow templates (58)

    <AccordionGroup>
      <Accordion title="Discount Leakage Detector">
        **For** Finance / commercial manager · **Ready to deploy**

        finds stacking, unexpected depth and customer/product misuse.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Price Change Approval Queue">
        **For** Finance / commercial manager · **Ready to deploy**

        supplies cost, margin, competitor/context and customer-group impact for each proposed change.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion Profitability Gate">
        **For** Finance / commercial manager · **Ready to deploy**

        forecasts margin impact and requires commercial approval before activation.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Best-seller Availability Guard">
        **For** E-commerce manager · **Ready to deploy**

        watches hero SKUs and recommends substitutions, replenishment escalation or merchandising changes.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Budget Pacing Guard">
        **For** Performance marketing manager · **Ready to deploy**

        forecasts over/underspend against plan and stages bounded reallocations for approval.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Readiness Gate">
        **For** E-commerce manager · **Ready to deploy**

        checks landing pages, products, inventory, tracking and links before launch; blocks “ready” if critical checks fail.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Checkout Journey Sentinel">
        **For** E-commerce manager · **Ready to deploy**

        scheduled storefront journey checks with screenshot/evidence and urgent escalation.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Creative Fatigue Watch">
        **For** Performance marketing manager · **Ready to deploy**

        detects declining response by creative/audience and opens a replacement brief.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Daily Store Pulse">
        **For** E-commerce manager · **Ready to deploy**

        morning revenue, conversion, AOV, stock and incident briefing with only material changes.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Multi-store Divergence Watch">
        **For** E-commerce manager · **Ready to deploy**

        compares stores/regions and flags unexplained differences in price, availability, content or performance.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New Product Launch Checklist">
        **For** E-commerce manager · **Ready to deploy**

        verifies content, media, inventory, category, SEO and analytics before publish approval.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion Activation QA">
        **For** Performance marketing manager · **Ready to deploy**

        verifies ads, dates, URLs, tracking, inventory and storefront offer before spend begins.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Promotion QA and Rollback Pack">
        **For** E-commerce manager · **Ready to deploy**

        validates price, dates, eligibility and merchandising, then prepares reversible fixes.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Search Query Waste Miner">
        **For** Performance marketing manager · **Ready to deploy**

        clusters irrelevant or expensive queries and drafts negative-keyword actions.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Wasted Spend Watch">
        **For** Performance marketing manager · **Ready to deploy**

        alerts on spend with no meaningful outcomes and recommends pause, budget or targeting review.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Amazon Ads, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Back-in-stock Opportunity Queue">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies high-intent customers and prepares consent-safe notifications.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brand Voice Compliance Review">
        **For** Product content manager · **Ready to deploy**

        flags off-brand, unsupported or inconsistent product claims and proposes corrections.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Preflight Gate">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        validates segment, exclusions, consent, links, stock, offer dates and tracking before send approval.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Completeness Guard">
        **For** Product content manager · **Ready to deploy**

        scores required fields by category and routes the highest-revenue gaps first.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Catalogue Integrity Night Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        checks SKU identity, variants, price, availability and orphan records across systems.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Deliverability and List Health Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        monitors bounce, complaint, suppression and engagement shifts with safe remediation advice.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Duplicate Copy Resolver">
        **For** Product content manager · **Ready to deploy**

        detects reused descriptions and produces differentiated drafts from verified attributes.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Flow Performance Decay Watch">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        detects lifecycle automations whose engagement or revenue has materially deteriorated.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Frequency Pressure Guard">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        identifies over-contacted customers across campaigns and flows.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Fulfilment SLA Breach Watch">
        **For** E-commerce operations manager · **Ready to deploy**

        predicts and escalates orders likely to miss dispatch or delivery promises.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Metadata Optimisation Queue">
        **For** SEO manager · **Ready to deploy**

        generates evidence-based title and description improvements for approval and staged publishing.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="New SKU Content Factory">
        **For** Product content manager · **Ready to deploy**

        turns approved source data into complete draft PDPs with a human review queue.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Operations Morning Handover">
        **For** E-commerce operations manager · **Ready to deploy**

        summarises overnight exceptions, actions taken, unresolved risk and accountable owners.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Exception Command Centre">
        **For** E-commerce operations manager · **Ready to deploy**

        detects stuck, failed or unusual orders and routes them with age and value-based urgency.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Order Issue Triage">
        **For** Customer service manager · **Ready to deploy**

        enriches tickets with order, payment and fulfilment context and assigns the right queue.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Out-of-stock SEO Protector">
        **For** SEO manager · **Ready to deploy**

        detects valuable unavailable pages and prepares safe redirect, substitute or retention actions.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="PDP Enrichment Queue">
        **For** Product content manager · **Ready to deploy**

        finds thin product pages, generates on-brand copy, and batches changes for approval.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Peak Freeze Controller">
        **For** E-commerce operations manager · **Ready to deploy**

        pauses writes during trading freezes while continuing all monitoring and alerts.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Proactive Delay List">
        **For** Customer service manager · **Ready to deploy**

        prepares, but does not send, customer communications for affected orders.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Product Claim Evidence Check">
        **For** Product content manager · **Ready to deploy**

        identifies unsubstantiated claims and requires evidence or removal before publish.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Returns Anomaly Monitor">
        **For** E-commerce operations manager · **Ready to deploy**

        surfaces spikes by SKU, supplier, reason or cohort and assigns investigation.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Jira Cloud, Microsoft Teams

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Schema Coverage and Validity Sweep">
        **For** SEO manager · **Ready to deploy**

        validates structured data across page types and stages theme/template fixes.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Seasonal Content Refresh">
        **For** Product content manager · **Ready to deploy**

        identifies stale seasonal language and prepares date-safe updates with expiry/rollback.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Segment Drift Monitor">
        **For** CRM / lifecycle marketing manager · **Ready to deploy**

        flags unexpected audience growth/shrinkage or overlap before it damages sends.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Mailchimp, HubSpot, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Supplier Copy Normaliser">
        **For** Product content manager · **Ready to deploy**

        converts inconsistent feeds into house style while preserving factual specifications.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Technical SEO Regression Monitor">
        **For** SEO manager · **Ready to deploy**

        watches broken links, redirect chains, canonicals, robots, schema and indexability after changes.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: Cloudflare, StagingPro, OpenAI

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Variant Consistency Sweep">
        **For** Product content manager · **Ready to deploy**

        reconciles names, options, specifications and copy across product families.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Accessibility Regression Sweep">
        **For** Web / digital product manager · **Ready to deploy**

        monitors high-value templates for newly introduced violations.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Broken Experience Prioritiser">
        **For** Web / digital product manager · **Ready to deploy**

        combines errors, traffic and revenue impact into a ranked product backlog.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Conversion Journey Sentinel">
        **For** Web / digital product manager · **Ready to deploy**

        repeatedly tests priority journeys and captures actionable failure evidence.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Core Web Performance Guard">
        **For** Web / digital product manager · **Ready to deploy**

        detects page/template regressions and routes them to the owning team.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Post-release Regression Watch">
        **For** Web / digital product manager · **Ready to deploy**

        compares critical KPIs and technical signals before/after deploy.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Release Readiness Gate">
        **For** Web / digital product manager · **Ready to deploy**

        checks staging journeys, accessibility, analytics, SEO, performance and rollback readiness.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Rollback Recommendation Pack">
        **For** Web / digital product manager · **Ready to deploy**

        assembles evidence and prepares a reversible action when guardrails fail.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Third-party Script Risk Watch">
        **For** Web / digital product manager · **Ready to deploy**

        flags new, slow, failing or unapproved scripts and tags.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: StagingPro, Cloudflare, GitHub, Jira Cloud

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief Approval Router">
        **For** Content manager · **Ready to deploy**

        sends briefs to the correct legal, SEO, product and brand approvers based on content type.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Brief-to-Draft Pipeline">
        **For** Content manager · **Ready to deploy**

        produces evidence-backed article drafts with sources, brand rules and approval status.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Campaign Asset Repurposer">
        **For** Content manager · **Ready to deploy**

        turns an approved core message into channel-specific drafts without auto-publishing.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Calendar Builder">
        **For** Content manager · **Ready to deploy**

        creates a channel-ready editorial calendar from launches, seasonality and search demand.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Content Freshness Watch">
        **For** Content manager · **Ready to deploy**

        finds decaying or outdated pages, explains why they matter and opens refresh tasks.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Editorial QA Gate">
        **For** Content manager · **Ready to deploy**

        checks links, claims, tone, formatting, metadata and calls to action before approval.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Evergreen Refresh Queue">
        **For** Content manager · **Ready to deploy**

        schedules evidence and date checks for high-value guides.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>

      <Accordion title="Launch Story Pack">
        **For** Content manager · **Ready to deploy**

        creates coordinated blog, email and social drafts from verified product information.

        Also available on: BigCommerce, WooCommerce, Shopline, PrestaShop, Swell, Square Online, Adobe Commerce, Salesforce Commerce Cloud (B2C)

        Tested alongside: HubSpot, Mailchimp, OpenAI, Anthropic, Gemini

        Runs on a schedule or trigger. Any step that changes data pauses for approval, and results deliver to the configured destination with a run receipt.
      </Accordion>
    </AccordionGroup>

    <Accordion title="Browse the operations you can build with">
      | Resource                                    | Read operations | Write operations |
      | ------------------------------------------- | --------------- | ---------------- |
      | abandonedcheckouts                          | 1               | 0                |
      | abandonedcheckoutscounts                    | 1               | 0                |
      | abandonments                                | 1               | 0                |
      | abandonmentbyabandonedcheckoutids           | 1               | 0                |
      | abandonmentupdateactivitiesdeliverystatuses | 0               | 1                |
      | apps                                        | 1               | 0                |
      | appbyhandles                                | 1               | 0                |
      | appbykeys                                   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>

    62 further designed workflows are in validation and become activatable only once proven against a live account. Prototypes are never presented as ready.
  </Tab>
</Tabs>


# Shopline on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/shopline

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Shopline.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Shopline.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/shopline) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=shopline)

<CardGroup>
  <Card title="54">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (54)">
    ### Monitor performance

    54 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                                                                                |
        | ------------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AOV by Country**             | Watch only         | AOV by Country.                                                                                                                               |
        | **Auth Token Health**          | Merchant rule      | Shopline JWTs are long-lived (Phillipstoys' is good until 2027-07) but silent expiry breaks order downloads. Surface before merchants notice. |
        | **Average Order Value**        | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                     |
        | **Avg Time to Fulfil (hrs)**   | Merchant rule      | From paid timestamp to fulfilled , surfaces 3PL/warehouse drag before SLAs break.                                                             |
        | **Fulfillment Rate**           | Alert band 95 / 90 | Orders fully fulfilled / total orders. \<90% means the merchant is breaking shipping promises.                                                |
        | **Fulfillment Rate Over Time** | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **Fulfillment Status Mix**     | Watch only         | Fulfillment Status Mix, shown by share.                                                                                                       |
        | **Inventory Distribution**     | Watch only         | Inventory Distribution, compared across items.                                                                                                |
        | **New Customers**              | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
        | **OOS Spike Alert**            | Alert band 0 / 5   | Anomalous OOS spike , usually a misconfigured sync, hold, or sudden demand event. Pair with the cross-channel ad-spend card.                  |
        | **Orders by Country**          | Watch only         | Orders by Country.                                                                                                                            |
        | **Top Cities by Orders**       | Watch only         | Top Cities by Orders.                                                                                                                         |
        | **Top Customers by Spend**     | Watch only         | Top Customers by Spend.                                                                                                                       |
        | **Total Orders**               | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                                                                     |
        | **Unfulfilled Orders**         | Alert band 10 / 50 | Paid orders with fulfillment\_status != fulfilled. The number ops should clear by EOD.                                                        |
        | **Unique Customers**           | Watch only         | Description pending editorial review; the signal is live.                                                                                     |
      </Accordion>

      <Accordion title="Grow revenue (16 signals)">
        | Signal                            | Alert behaviour    | What it tracks                                                                                                                                            |
        | --------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Coupon Usage Rate**             | Alert band 20 / 40 | Share of orders where the customer entered a coupon code, from order.promotion\_items\[].coupon\_code - distinct from Discount % of Revenue's dollar-weig |
        | **Customer Spend Segments**       | Watch only         | Customers grouped by lifetime spend bucket. Underpins lookalike + VIP campaigns.                                                                          |
        | **Orders Over Time**              | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                                                                                 |
        | **Products Missing Description**  | Alert band 5 / 20  | Products with empty body\_html. Free conversion lift on the table.                                                                                        |
        | **Repeat Customer Rate**          | Alert band 25 / 10 | Customers with >1 order in 90D. A retention barometer , DTC dies when this drops.                                                                         |
        | **Revenue Drop Alert**            | Alert band 0 / -5  | Trips when last-24h revenue lags the prior-7-day baseline by >25%. The canary for a broken checkout / app / pixel.                                        |
        | **Revenue Over Time**             | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                                 |
        | **Revenue by Channel**            | Watch only         | Storefront vs social-commerce vs POS. Single-channel today; gains depth when multi-channel Pattern A lands.                                               |
        | **Shipping Cost as % of Revenue** | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                                 |
        | **Slow-Moving Products**          | Watch only         | Bottom decile by revenue. Candidates for sunset / clearance / repositioning.                                                                              |
        | **Top Products by Revenue**       | Watch only         | Top Products by Revenue.                                                                                                                                  |
        | **Total Discount Used**           | Watch only         | Description pending editorial review; the signal is live.                                                                                                 |
        | **Total Revenue**                 | Alert band 0 / -5  | Headline gross revenue. The single number the founder checks at 9am Monday.                                                                               |
        | **Total Shipping Revenue**        | Watch only         | Description pending editorial review; the signal is live.                                                                                                 |
        | **Total Tax Collected**           | Watch only         | Description pending editorial review; the signal is live.                                                                                                 |
        | **Zero/Negative Stock Variants**  | Alert band 0 / 5   | OOS variants. Pair with the cross-channel ad-spend card to find the real revenue blockers.                                                                |
      </Accordion>

      <Accordion title="Protect revenue (15 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                        |
        | -------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------- |
        | **Active Ads on Out-of-Stock SKUs**    | Merchant rule      | Spend burning on SKUs that can't convert. The single highest-ROI 'pause' recommendation in the AIOS.                  |
        | **Cancellation Rate**                  | Alert band 1 / 3   | Description pending editorial review; the signal is live.                                                             |
        | **Catalogue Drift vs Amazon**          | Merchant rule      | SKUs that diverge between Shopline and Amazon. Brand-trust killer + de-listing risk under MAP policies.               |
        | **Days-of-Cover by SKU**               | Merchant rule      | On-hand / 30D velocity per SKU. Surfaces stockout risk before it bites.                                               |
        | **Discount % of Revenue**              | Alert band 20 / 40 | Discount leakage as a share of revenue. Persistent >25% means the business depends on promos.                         |
        | **Email-Attributed Revenue Share**     | Alert band 15 / 8  | Share of Shopline revenue driven by lifecycle email. \<15% in mature brands = retention spend underperforming.        |
        | **Low-Stock SKUs (\<10 units)**        | Alert band 0 / 5   | Description pending editorial review; the signal is live.                                                             |
        | **Marketplace Revenue Share (Amazon)** | Merchant rule      | DTC vs marketplace revenue split. >70% Amazon = platform-dependency risk; \<10% = under-utilising marketplace reach.  |
        | **Products Missing SEO Meta**          | Alert band 10 / 30 | Products with an empty SEO title or SEO description. Organic-traffic leak distinct from Products Missing Description. |
        | **Refund Rate**                        | Alert band 2 / 5   | Refunded orders / total orders. Persistent >5% signals product quality or expectation mismatch.                       |
        | **Refund Value**                       | Watch only         | Description pending editorial review; the signal is live.                                                             |
        | **Refund-Rate Spike Alert**            | Alert band 2 / 5   | Refund-rate anomaly. Catches batch-quality issues, broken sizing, or coupon misuse before the support inbox does.     |
        | **Refunds Over Time**                  | Watch only         | Description pending editorial review; the signal is live.                                                             |
        | **Revenue at Risk (live incident)**    | Merchant rule      | Live \$/min loss while a monitoring incident is open , the COO's hot-button number during outages.                    |
        | **Shopline Health Score**              | Alert band 95 / 80 | Composite of refund rate × fulfillment rate × OOS count × 30D revenue trend × auth-token health.                      |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                        |
        | -------------------------- | --------------- | --------------------------------------------------------------------- |
        | **Avg Time-to-Paid (hrs)** | Merchant rule   | Created → paid latency , flags broken authorise-only flows + COD lag. |
        | **Financial Status Mix**   | Watch only      | Financial Status Mix, compared across items.                          |
        | **Partially-Paid Orders**  | Merchant rule   | Description pending editorial review; the signal is live.             |
        | **Payment Methods**        | Watch only      | Payment Methods, shown by share.                                      |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                 | Alert behaviour    | What it tracks                                                                  |
        | ---------------------- | ------------------ | ------------------------------------------------------------------------------- |
        | **Product Status Mix** | Watch only         | Product Status Mix, shown by share.                                             |
        | **Products by Vendor** | Watch only         | Products by Vendor.                                                             |
        | **SKU Coverage**       | Alert band 80 / 50 | Variants with a populated SKU. Below 95% breaks marketplace + 3PL integrations. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **0 write** operations across openapicustomerjsons, openapiinventoryleveljsons, openapiorders, openapiorderjsons, openapiproducts, openapiproductjsons on Shopline. 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=shopline)

    #### Ready to build your first Shopline 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                   | Read operations | Write operations |
      | -------------------------- | --------------- | ---------------- |
      | openapicustomerjsons       | 1               | 0                |
      | openapiinventoryleveljsons | 1               | 0                |
      | openapiorders              | 1               | 0                |
      | openapiorderjsons          | 1               | 0                |
      | openapiproducts            | 1               | 0                |
      | openapiproductjsons        | 1               | 0                |
      | openapirefundjsons         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Slack on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/slack

Monitor Slack performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Slack performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=slack)

<CardGroup>
  <Card title="5">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="174">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (5)">
    ### Monitor performance

    5 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (4 signals)">
        | Signal                       | Alert behaviour | What it tracks                                                                                                                                                                      |
        | ---------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Delivery Channel Type**    | Watch only      | Constant 'Incoming Webhook' - the delivery mechanism for this connector. States plainly how messages reach this channel.                                                            |
        | **Messages Sent (30d)**      | Watch only      | Count of messages delivered in the last 30d. Degrades to no\_data (reason not\_tracked): an incoming webhook exposes no history/read method, so sent vol                            |
        | **Slack Channel Configured** | Watch only      | Renders 'Connected' when webhook\_url is present and matches ^[https://hooks.slack.com/](https://hooks.slack.com/), else 'Not connected'. Pure credential-shape check, no API call. |
        | **Webhook Host**             | Watch only      | Host parsed from webhook\_url (expected hooks.slack.com). Confirms the pasted URL targets Slack, not some other host.                                                               |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                   | Alert behaviour | What it tracks                                                                                                                                            |
        | ------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Last Delivery Status** | Watch only      | Result of the most recent send. Degrades to no\_data (reason delivery\_log\_unavailable): no send log is persisted yet, and an incoming webhook has no re |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Slack yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **80 read** and **94 write** operations across admin.apps.approves, admin.apps.approved.lists, admin.apps.requests.lists, admin.apps.restricts, admin.apps.restricted.lists, admin.conversations.archives on Slack. 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=slack)

    #### Ready to build your first Slack 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                              | Read operations | Write operations |
      | ------------------------------------- | --------------- | ---------------- |
      | admin.apps.approves                   | 0               | 1                |
      | admin.apps.approved.lists             | 1               | 0                |
      | admin.apps.requests.lists             | 1               | 0                |
      | admin.apps.restricts                  | 0               | 1                |
      | admin.apps.restricted.lists           | 1               | 0                |
      | admin.conversations.archives          | 0               | 1                |
      | admin.conversations.converttoprivates | 0               | 1                |
      | admin.conversations.creates           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Smartsheet (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/smartsheet-api

Monitor Smartsheet (API) performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Smartsheet (API) performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=smartsheet-api)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                        |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                             |
        | **Avg Lead Time (days)**            | Merchant rule      | Description pending editorial review; the signal is live.                                                                             |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                             |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                                  |
        | **Backlog by Status**               | Watch only         | Backlog by Status.                                                                                                                    |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Rows with Status = Blocked / Investigating - the operational queue's stuck list.                                                      |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                               |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings actually got resolved via the Smartsheet pipeline. \<50% means we're filing faster than the team drains. |
        | **In Progress**                     | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Oldest Open (days)**              | Merchant rule      | Description pending editorial review; the signal is live.                                                                             |
        | **Open Tickets**                    | Merchant rule      | Rows in the mapped Findings sheet whose Status is not in the closed set - top-of-funnel backlog volume.                               |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | People with >10 open rows in the Assigned To column - capacity bottleneck candidates.                                                 |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                             |
        | **Sprint Progress**                 | Alert band 80 / 50 | Description pending editorial review; the signal is live.                                                                             |
        | **Sprint Velocity (avg)**           | Merchant rule      | Sprint Velocity (avg) over time.                                                                                                      |
        | **Throughput Trend**                | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **Tickets Resolved (7d)**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                             |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                                  |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                             |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                             |
        | **VortexIQ Findings Open**          | Merchant rule      | Findings-sheet rows we filed from audit findings that aren't marked closed yet - the live backlog of things VortexIQ surfaced.        |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                             |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                              |
        | ----------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the Findings sheet with no Modified (Auto) change for two weeks - these are the ones losing money silently. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **3 write** operations across sheetrows, sheets, sheetcolumns, sheetrowdiscussions, users, usermes on Smartsheet (API). 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=smartsheet-api)

    #### Ready to build your first Smartsheet (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | sheetrows           | 1               | 2                |
      | sheets              | 2               | 0                |
      | sheetcolumns        | 1               | 0                |
      | sheetrowdiscussions | 0               | 1                |
      | users               | 1               | 0                |
      | usermes             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Snapchat Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/snapchat-ads

Monitor Snapchat Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Snapchat Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/snapchat-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=snapchat-ads)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                         |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------ |
        | **All Conversions**                 | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **CPC by Campaign**                 | Watch only         | CPC by Campaign.                                                                                       |
        | **CTR by Campaign**                 | Watch only         | CTR by Campaign.                                                                                       |
        | **Campaign Comparison**             | Watch only         | Campaign Comparison, broken down by row.                                                               |
        | **Clicks vs Conversions**           | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Conversion Actions Breakdown**    | Watch only         | Conversion Actions Breakdown.                                                                          |
        | **Conversion Drop Alert**           | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Conversion Funnel**               | Watch only         | Conversion Funnel, stage by stage.                                                                     |
        | **Conversion Lag**                  | Watch only         | Conversion Lag, compared across items.                                                                 |
        | **Conversion Rate Trend**           | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Conversion Rate by Campaign**     | Watch only         | Conversion Rate by Campaign.                                                                           |
        | **Conversion Rate by Device**       | Watch only         | Conversion Rate by Device.                                                                             |
        | **Conversions Trend**               | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Conversions by Campaign**         | Watch only         | Conversions by Campaign.                                                                               |
        | **Conversions by Country**          | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Conversions by Day of Week**      | Watch only         | Conversions by Day of Week.                                                                            |
        | **Conversions by Device**           | Watch only         | Conversions by Device.                                                                                 |
        | **Conversions by Hour**             | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Landing Page Revenue**            | Watch only         | Landing Page Revenue, broken down by row.                                                              |
        | **Overspending Campaigns**          | Watch only         | Overspending Campaigns, broken down by row.                                                            |
        | **ROAS**                            | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                              |
        | **ROAS Dropped Below Threshold**    | Alert band 3 / 1.5 | First number to ping when Snap's volatile Gen Z auction shifts overnight.                              |
        | **ROAS Trend**                      | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **ROAS by Campaign**                | Watch only         | ROAS by Campaign.                                                                                      |
        | **ROAS by Day of Week**             | Watch only         | ROAS by Day of Week.                                                                                   |
        | **ROAS by Device**                  | Watch only         | ROAS by Device.                                                                                        |
        | **ROAS by Region**                  | Watch only         | ROAS by Region.                                                                                        |
        | **Revenue by Campaign**             | Watch only         | Revenue by Campaign.                                                                                   |
        | **Search Terms Report**             | Watch only         | Search Terms Report, broken down by row.                                                               |
        | **Snap Pixel/CAPI Tracking Broken** | Merchant rule      | Snap's iOS-14.5 attribution drift bites harder than any other platform , catch in the same ATT window. |
        | **Spend by Campaign**               | Watch only         | Spend by Campaign.                                                                                     |
        | **Top Cities by Conversions**       | Watch only         | Top Cities by Conversions.                                                                             |
        | **Top Keywords by Conversions**     | Watch only         | Top Keywords by Conversions.                                                                           |
        | **Top Performing Campaigns**        | Watch only         | Top Performing Campaigns, broken down by row.                                                          |
        | **Total Revenue**                   | Watch only         | Description pending editorial review; the signal is live.                                              |
        | **Underspending Campaigns**         | Watch only         | Underspending Campaigns, broken down by row.                                                           |
        | **Worst Performing Campaigns**      | Watch only         | Worst Performing Campaigns, broken down by row.                                                        |
        | **Zero-Conversion Spend**           | Watch only         | Description pending editorial review; the signal is live.                                              |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                    |
        | ------------------------------------ | ------------------ | --------------------------------------------------------------------------------- |
        | **Budget Utilisation**               | Alert band 70 / 30 | Description pending editorial review; the signal is live.                         |
        | **CPA Trend**                        | Watch only         | Description pending editorial review; the signal is live.                         |
        | **CPA by Keyword**                   | Watch only         | CPA by Keyword.                                                                   |
        | **CPC Anomaly**                      | Watch only         | Description pending editorial review; the signal is live.                         |
        | **CPC Spike Detection**              | Watch only         | Description pending editorial review; the signal is live.                         |
        | **CPC Trend**                        | Alert band 0 / 25  | Description pending editorial review; the signal is live.                         |
        | **CTR Trend**                        | Watch only         | Description pending editorial review; the signal is live.                         |
        | **CTR by Keyword**                   | Watch only         | CTR by Keyword.                                                                   |
        | **Impression Share**                 | Alert band 70 / 40 | Description pending editorial review; the signal is live.                         |
        | **Impressions Trend**                | Watch only         | Description pending editorial review; the signal is live.                         |
        | **Quality Score Distribution**       | Alert band 7 / 4   | Quality Score Distribution, compared across items.                                |
        | **Spend Anomaly**                    | Watch only         | Description pending editorial review; the signal is live.                         |
        | **Spend Over Time**                  | Alert band 0 / -10 | Description pending editorial review; the signal is live.                         |
        | **Spend vs Budget**                  | Watch only         | Description pending editorial review; the signal is live.                         |
        | **Top Keywords by Spend**            | Watch only         | Top Keywords by Spend.                                                            |
        | **Total Spend**                      | Watch only         | Description pending editorial review; the signal is live.                         |
        | **Wasted Spend**                     | Watch only         | Description pending editorial review; the signal is live.                         |
        | **Wasted-Spend Burst (3-day spike)** | Alert band 5 / 50  | Snap auction can chew a runaway budget faster than Meta on mobile-only inventory. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                               | Alert behaviour   | What it tracks                                                                                                                     |
        | ---------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Catalog Ads on Out-of-Stock SKUs**          | Alert band 5 / 50 | Spend on Snap catalog ads pointing at SKUs that can't convert. Pause the product set, hold the budget.                             |
        | **Branded Paid Clicks Cannibalising Organic Search** | Merchant rule     | Brand-aware Snap audiences also search the brand on Google. Snap branded campaigns cannibalising free organic , pause or restrict. |
        | **CTR Decline Alert**                                | Watch only        | Description pending editorial review; the signal is live.                                                                          |
        | **Mobile Landing Pages with Poor Web Vitals**        | Merchant rule     | Snap traffic is 100% mobile , landing LCP regressions kill conversion before the page paints.                                      |
        | **Spend on Campaigns with Active Feed Rejections**   | Merchant rule     | £ on a Snap catalog campaign whose Feedonomics export has rejections. Bid signal degrades until cleared.                           |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **1 write** operations across adaccountcampaigns, adaccountcreatives, adaccountstats, loginoauth2accesstokens, meorganizations, organizationadaccounts on Snapchat Ads. 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=snapchat-ads)

    #### Ready to build your first Snapchat Ads 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                | Read operations | Write operations |
      | ----------------------- | --------------- | ---------------- |
      | adaccountcampaigns      | 1               | 0                |
      | adaccountcreatives      | 1               | 0                |
      | adaccountstats          | 1               | 0                |
      | loginoauth2accesstokens | 0               | 1                |
      | meorganizations         | 1               | 0                |
      | organizationadaccounts  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Snowflake on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/snowflake

Monitor Snowflake health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Snowflake health, cost and reliability signals, and catch incidents and runaway spend early.

[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=snowflake)

<CardGroup>
  <Card title="29">
    performance signals
  </Card>

  <Card title="15">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (29)">
    ### Monitor performance

    29 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (14 signals)">
        | Signal                                               | Alert behaviour    | What it tracks                                                                                                             |
        | ---------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
        | **Active Sessions**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Active Warehouses**                                | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Avg Cost per Query (\$)**                          | Merchant rule      | (credits \* \$/credit) / query\_count. Rising = inefficient queries OR more results returned per query.                    |
        | **Credit Burn +50% Week-over-Week**                  | Merchant rule      | Snowflake-distinctive , runaway query / scheduled job overrun is the #1 cost surprise.                                     |
        | **Credits Burned (24h)**                             | Merchant rule      | From METERING\_HISTORY. Snowflake-defining , credits = dollars burned in compute time.                                     |
        | **Credits by Warehouse (7d)**                        | Watch only         | Per-warehouse credit consumption. Drives sizing + scheduling decisions.                                                    |
        | **Cross-Account Replication Lag (s)**                | Alert band 1 / 10  | Description pending editorial review; the signal is live.                                                                  |
        | **Idle Warehouse Credits Wasted (24h)**              | Merchant rule      | Credits spent while warehouse was on but processing no queries , auto-suspend tuning candidate.                            |
        | **Largest Table (GB)**                               | Watch only         | From TABLE\_STORAGE\_METRICS. Top tables drive storage cost.                                                               |
        | **Last Snapshot Age (hours)**                        | Alert band 24 / 72 | Snowflake auto-snapshots via Time Travel (default 1d, up to 90d on Enterprise). This reflects Time Travel retention floor. |
        | **Queries per Hour (live)**                          | Watch only         | Description pending editorial review; the signal is live.                                                                  |
        | **Snowflake Health Score**                           | Merchant rule      | Description pending editorial review; the signal is live.                                                                  |
        | **Warehouse Queueing Sustained (>5 queries queued)** | Alert band 70 / 90 | Alerts for Warehouse Queueing Sustained (>5 queries queued).                                                               |
        | **Warehouse Saturation %**                           | Alert band 70 / 90 | running\_queries / max\_concurrency\_level per warehouse , sustained 100% indicates need to upsize or multi-cluster.       |
      </Accordion>

      <Accordion title="Customer experience (7 signals)">
        | Signal                                  | Alert behaviour      | What it tracks                                                                                                                                              |
        | --------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Query Queue Depth per Warehouse** | Merchant rule        | From QUEUED\_PROVISIONING\_TIME + QUEUED\_OVERLOAD\_TIME in QUERY\_HISTORY. Snowflake-distinctive , sustained queue = warehouse undersized.                 |
        | **Query Latency p50 (ms)**              | Watch only           | Description pending editorial review; the signal is live.                                                                                                   |
        | **Query Latency p95 (ms)**              | Alert band 50 / 200  | Snowflake p95 measured in seconds, not ms , threshold reflects analytics use case.                                                                          |
        | **Query Latency p99 (ms)**              | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                                                                                   |
        | **Slow-Query Rate %**                   | Alert band 1 / 5     | Description pending editorial review; the signal is live.                                                                                                   |
        | **Top 10 Slowest Queries**              | Watch only           | Top 10 Slowest Queries, broken down by row.                                                                                                                 |
        | **Warehouse Cache Hit Rate %**          | Alert band 95 / 80   | Avg of ACCOUNT\_USAGE.QUERY\_HISTORY.PERCENTAGE\_SCANNED\_FROM\_CACHE (0-1, scaled to %) over the trailing hour - Snowflake-distinctive: local warehouse SS |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                            | Alert behaviour | What it tracks                                                                                                                         |
        | ------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
        | **Credit Burn vs Ecom Order Volume**              | Merchant rule   | Snowflake-distinctive XC , credit burn should track ecom volume (more data to analyse = more credits). Divergence = cost inefficiency. |
        | **Failed Logins (24h)**                           | Merchant rule   | From LOGIN\_HISTORY , bursts indicate brute force or stale credentials.                                                                |
        | **Slow Analytics Queries During Checkout Window** | Merchant rule   | Slow Analytics Queries During Checkout Window, broken down by row.                                                                     |
        | **Snowflake Event Ingest vs Ecom Orders**         | Merchant rule   | Description pending editorial review; the signal is live.                                                                              |
        | **Snowflake QPS Spike vs Ecom Order Rate**        | Merchant rule   | Description pending editorial review; the signal is live.                                                                              |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                            |
        | -------------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Query Error Rate %**                 | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. |
        | **Query Error Rate Spike (>1% in 1h)** | Alert band 0.1 / 1 | Alerts for Query Error Rate Spike (>1% in 1h).            |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal                | Alert behaviour    | What it tracks                                                                              |
        | --------------------- | ------------------ | ------------------------------------------------------------------------------------------- |
        | **Storage Used (TB)** | Alert band 70 / 90 | From STORAGE\_USAGE table (1.5hr latency). Storage is cost-anchored , growth = bill growth. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (15)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Credit Burn +50% Week-over-Week">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Credit burn jumping 50 percent week over week compounds into a painful invoice; the cause is usually one new workload that nobody costed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SN-COST-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Query Error Rate Spike >1% in 1h">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Job errors spiking past 1 percent breaks the pipelines that dashboards and models silently depend on.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SN-PERF-004`
      </Accordion>

      <Accordion title="Query Queue Depth >5 Sustained 10m per Warehouse">
        **Severity** high · **Outcome** Customer experience · **Fix status** Candidate remediation

        Queries queuing behind a saturated warehouse delay every dashboard and job downstream; users experience it as everything being slow.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `SN-PERF-005`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Active Sessions Climbing (Connection Pool Pressure)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Climbing active sessions exhaust connection pools; when they run out, applications fail loudly and all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SN-CAP-003`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Cost per Query Rising >25% Week-over-Week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Cost per query rising 25 percent week over week means efficiency is degrading even if the bill has not caught up yet.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SN-COST-003`
      </Accordion>

      <Accordion title="Failed Login Attempts >10 in 24h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed logins clustering above 10 a day is either an attack or a broken integration credential; both deserve a look the same day.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SN-SEC-001`
      </Accordion>

      <Accordion title="Idle Warehouse Credits >10% of Total">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Warehouses idling while credits accrue is pure waste; auto-suspend settings usually recover it in an afternoon.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `SN-COST-002`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **0 write** operations across informationschemaqueryhistorys, snowflakeaccountusagedatabasereplicationusagehistorys, snowflakeaccountusageloginhistorys, snowflakeaccountusagemeteringhistorys, snowflakeaccountusagequeryhistorys, snowflakeaccountusagestorageusages on Snowflake. 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=snowflake)

    #### Ready to build your first Snowflake 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                              | Read operations | Write operations |
      | ----------------------------------------------------- | --------------- | ---------------- |
      | informationschemaqueryhistorys                        | 1               | 0                |
      | snowflakeaccountusagedatabasereplicationusagehistorys | 1               | 0                |
      | snowflakeaccountusageloginhistorys                    | 1               | 0                |
      | snowflakeaccountusagemeteringhistorys                 | 1               | 0                |
      | snowflakeaccountusagequeryhistorys                    | 1               | 0                |
      | snowflakeaccountusagestorageusages                    | 1               | 0                |
      | snowflakeaccountusagetablestoragemetrics              | 1               | 0                |
      | snowflakeaccountusagewarehousemeteringhistorys        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Splunk on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/splunk

Monitor Splunk health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Splunk health, cost and reliability signals, and catch incidents and runaway spend early.

[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=splunk)

<CardGroup>
  <Card title="19">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (19)">
    ### Monitor performance

    19 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                           |
        | ---------------------------- | ---------------------------- | ---------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Watch only                   | Alerts a responder has acknowledged - distinguishes 'seen' from 'firing-but-ignored'.    |
        | **Alerts Firing**            | Alert band 0 / 1             | Detectors currently in a firing state.                                                   |
        | **Incidents Open**           | Alert band 0 / 3             | Open On-Call incidents not yet resolved.                                                 |
        | **Incidents Resolved (24h)** | Watch only                   | Incidents closed in the trailing 24 hours - throughput of the on-call rotation.          |
        | **Mean Time To Acknowledge** | Alert band 300000 / 1800000  | Average time from incident trigger to first human acknowledgement.                       |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Average time from incident trigger to resolution - the headline reliability number.      |
        | **SLA Compliance**           | Merchant rule                | Percentage of SLO targets met across the window.                                         |
        | **Services Degraded**        | Merchant rule                | Services in a degraded (warning) state - early-warning surface before full outage.       |
        | **Services Down**            | Merchant rule                | Services reporting fully down - any non-zero value is an active outage.                  |
        | **Services Healthy**         | Watch only                   | Count of APM services reporting a healthy state.                                         |
        | **Top Alerting Services**    | Merchant rule                | Services ranked by alert volume - concentration on one service is the regression signal. |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour       | What it tracks                                                                                  |
        | ------------------------ | --------------------- | ----------------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.95 / 0.7 | Application performance index - satisfied/tolerating/frustrated request ratio.                  |
        | **Avg Response Time**    | Alert band 200 / 1000 | Mean APM service response time over the window.                                                 |
        | **Error Rate**           | Alert band 0.5 / 2    | Share of requests returning errors across APM services, from SignalFlow over the chosen window. |
        | **Throughput (req/min)** | Alert band 0 / -10    | Requests per minute across APM services - sustained drops flag capacity or outage.              |
        | **p95 Latency**          | Alert band 200 / 1000 | 95th-percentile service latency - the tail that customers feel.                                 |
        | **p99 Latency**          | Alert band 200 / 1000 | 99th-percentile latency - worst-case experience for the slowest 1%.                             |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                              | Alert behaviour | What it tracks                                                                                           |
        | ----------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- |
        | **Revenue at Risk (services down)** | Merchant rule   | Live \$/min on fire while a commerce-path service is down or degraded - the COO's number, not the SRE's. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                  |
        | ------------------- | --------------- | ------------------------------------------------------------------------------- |
        | **Top Error Types** | Watch only      | Most frequent error classes across services - where to point remediation first. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **2 write** operations across alertmutings, apipublicincidents, apipublicincidentacks, apipublicreportingmetrics, apmservices, detectors on Splunk. 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=splunk)

    #### Ready to build your first Splunk 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                  | Read operations | Write operations |
      | ------------------------- | --------------- | ---------------- |
      | alertmutings              | 1               | 0                |
      | apipublicincidents        | 1               | 0                |
      | apipublicincidentacks     | 0               | 1                |
      | apipublicreportingmetrics | 1               | 0                |
      | apmservices               | 1               | 0                |
      | detectors                 | 1               | 0                |
      | incidents                 | 1               | 0                |
      | organizations             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# SQLite on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sqlite

Monitor SQLite health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor SQLite health, cost and reliability signals, and catch incidents and runaway spend early.

[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=sqlite)

<CardGroup>
  <Card title="14">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="17">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (14)">
    ### Monitor performance

    14 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (7 signals)">
        | Signal                                     | Alert behaviour    | What it tracks                                                                                                                                 |
        | ------------------------------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Database File Size (MB)**                | Watch only         | PRAGMA page\_count × PRAGMA page\_size, in MB.                                                                                                 |
        | **Foreign-Key Violations**                 | Merchant rule      | Rows returned by PRAGMA foreign\_key\_check - orphaned child rows when foreign keys are enforced.                                              |
        | **Fragmentation (Free-Page %)**            | Alert band 70 / 90 | PRAGMA freelist\_count / PRAGMA page\_count. SQLite-distinctive - high freelist means the file should be VACUUMed to reclaim space.            |
        | **Hot Queries Doing Full Table SCAN**      | Alert band 2 / 10  | Sampled hot queries whose EXPLAIN QUERY PLAN reports SCAN TABLE - a missing index. SQLite-distinctive.                                         |
        | **Large Tables With No Usable Index**      | Merchant rule      | Tables >10k rows from sqlite\_schema with no index on common WHERE / JOIN columns.                                                             |
        | **WAL File Ballooning Without Checkpoint** | Merchant rule      | Alerts for WAL File Ballooning Without Checkpoint.                                                                                             |
        | **WAL File Size (MB)**                     | Merchant rule      | WAL frame count × page\_size from PRAGMA wal\_checkpoint. SQLite-distinctive - a ballooning WAL means a reader is holding back the checkpoint. |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                                 | Alert behaviour | What it tracks                                                                                                            |
        | ------------------------------------------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------- |
        | **Integrity Check Failed (corruption detected)**       | Merchant rule   | Alerts for Integrity Check Failed (corruption detected).                                                                  |
        | **SQLite Table Rows vs Ecom Catalog Count**            | Merchant rule   | SQLite-distinctive XC - many apps cache the product / inventory catalog in a local SQLite file; row drift = sync failure. |
        | **Writer-Lock Contention During Checkout Window (5m)** | Merchant rule   | Writer-Lock Contention During Checkout Window (5m), broken down by row.                                                   |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                                        | Alert behaviour    | What it tracks                                                                                      |
        | --------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------- |
        | **Integrity Check Status**                    | Merchant rule      | PRAGMA integrity\_check - anything other than a single 'ok' row indicates B-tree / page corruption. |
        | **Last Backup / VACUUM Snapshot (hours ago)** | Alert band 24 / 72 | Most recent Online-Backup-API copy, VACUUM INTO snapshot, or filesystem snapshot timestamp.         |
        | **SQLite File Health Score**                  | Merchant rule      | Composite of integrity, fragmentation, WAL state, and index coverage.                               |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                                  | Alert behaviour | What it tracks                                                                                                |
        | --------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------- |
        | **SQLITE\_BUSY / Lock Contention (5m)** | Merchant rule   | Count of SQLITE\_BUSY / SQLITE\_LOCKED returns on the single writer lock - a long write txn starving readers. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **17 read** and **0 write** operations across dbstats, explain query plans, pragma autovacuums, pragma compileoptions, pragma foreignkeychecks, pragma freelistcounts on SQLite. 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=sqlite)

    #### Ready to build your first SQLite 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                | Read operations | Write operations |
      | ----------------------- | --------------- | ---------------- |
      | dbstats                 | 1               | 0                |
      | explain query plans     | 1               | 0                |
      | pragma autovacuums      | 1               | 0                |
      | pragma compileoptions   | 1               | 0                |
      | pragma foreignkeychecks | 1               | 0                |
      | pragma freelistcounts   | 1               | 0                |
      | pragma integritychecks  | 1               | 0                |
      | pragma journalmodes     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Square on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/square

Monitor Square payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Square payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=square)

<CardGroup>
  <Card title="17">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (17)">
    ### Monitor performance

    17 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (10 signals)">
        | Signal                                           | Alert behaviour      | What it tracks                                                                                                                                                |
        | ------------------------------------------------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                         | Watch only           | Square Online checkouts that hit a 3DS-2 challenge and the customer abandoned (CANCELED with 3DS error). Online-only; POS uses chip + PIN, no 3DS. Dif        |
        | **Chargeback Rate**                              | Merchant rule        | Disputes in state = LOST / payments succeeded \* 100. A trailing metric (disputes resolve 30-60d after opening). Above 0.9% Square may impose a rolling       |
        | **Decline Rate**                                 | Alert band 3 / 8     | FAILED / (COMPLETED + FAILED + CANCELED) \* 100. CANCELED (3DS abandon) excluded and tracked separately. POS \<1%; Online 4-8%.                               |
        | **Dispute Rate**                                 | Alert band 0.5 / 0.9 | Disputes opened / payments succeeded \* 100, on /v2/disputes. POS card-present \<0.05% (chip + PIN liability shift); CNP 0.3-1.5%. The leading indica         |
        | **Online Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When Square Online declines spike, does commerce checkout completion drop in the same window? If yes, declines are causing real revenue loss - and the        |
        | **Refund Rate**                                  | Alert band 2 / 5     | SUM(refunds.amount) / SUM(payments.amount) \* 100. Spikes signal product/fulfilment issues; gentle creep signals subscription churn. Bookshops 1-3%, ap       |
        | **Refund Volume**                                | Merchant rule        | SUM(amount) over /v2/refunds where status = COMPLETED, per currency. Partial refunds counted at the partial amount. Retail 2-5%; ecom 5-12%.                  |
        | **Success Rate**                                 | Alert band 97 / 92   | COMPLETED / (COMPLETED + FAILED + CANCELED) \* 100. APPROVED (auth-only) excluded. POS card-present \~99%; Square Online \~92-96%.                            |
        | **Top Decline Reasons**                          | Merchant rule        | COUNT GROUP BY failure\_code over FAILED /v2/payments. CARD\_DECLINED, INSUFFICIENT\_FUNDS, CVV\_FAILURE, EXPIRED\_CARD, CHIP\_INSERTION\_REQUIRED - each has |
        | **Total Volume**                                 | Alert band 0 / -15   | Every /v2/payments row where status = COMPLETED, summed by amount\_money.amount, across POS, Square Online, Invoices, Virtual Terminal, Tap to Pay and        |
      </Accordion>

      <Accordion title="Run operations (7 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                                                            |
        | -------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Transaction**          | Merchant rule      | SUM(amount) / COUNT(\*) over COMPLETED payments, per currency. Channel mix-shift moves this more than any single-channel pricing change.                  |
        | **Avg Settlement Time (days)**   | Alert band 2 / 5   | AVG(payout.created\_at - payment.created\_at) in days, amount-weighted. Square default is T+1 (\~1.0-1.5 days); Instant Deposit usage drags it down; rese |
        | **Oldest Pending Payout (days)** | Alert band 2 / 5   | Calendar days since the last successful payout to the linked bank. Healthy 1-2d (T+1); >3d suggests weekend/holiday closure or schedule change; \&gt      |
        | **Pending Payouts**              | Merchant rule      | Captured COMPLETED payments not yet rolled into a settled payout. Snapshot, not trended. Reserves count as pending; Instant Deposit reduces it.           |
        | **Top Payment Methods**          | Merchant rule      | COUNT GROUP BY entry\_method + source\_type over COMPLETED payments: chip, contactless, magstripe, manual, cash, Cash App Pay, Apple/Google Pay, gift ca  |
        | **Total Transactions**           | Alert band 0 / -15 | COUNT of COMPLETED /v2/payments rows - one per payment, all source\_type values. The denominator behind average transaction.                              |
        | **Volume Trend**                 | Watch only         | Daily COMPLETED payment volume plotted over the period. The cleanest card for spotting weekday/weekend seasonality and sudden cliff-drops (terminal ou    |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **1 write** operations across payments, disputes, disputeaccepts, merchants, orders, payouts on Square. 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=square)

    #### Ready to build your first Square 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.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | payments       | 2               | 0                |
      | disputes       | 1               | 0                |
      | disputeaccepts | 0               | 1                |
      | merchants      | 1               | 0                |
      | orders         | 1               | 0                |
      | payouts        | 1               | 0                |
      | refunds        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Square Online on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/square-online

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Square Online.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Square Online.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/square-online) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=square-online)

<CardGroup>
  <Card title="44">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (44)">
    ### Monitor performance

    44 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (14 signals)">
        | Signal                                           | Alert behaviour    | What it tracks                                                                                                                                           |
        | ------------------------------------------------ | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **% Revenue From POS-Only Items**                | Watch only         | Description pending editorial review; the signal is live.                                                                                                |
        | **Channel Mix Shift (vs prior)**                 | Merchant rule      | Detects sudden channel-mix shifts (e.g. POS-revenue dropped 25pp into online , likely tied to staffing / store-closure / promotion). Distinctive to mu   |
        | **Customer Capture Source (POS vs Online)**      | Watch only         | creation\_source breakdown , TERMINAL=POS vs ONLINE\_STORE vs INVOICES. Surfaces channel-of-first-touch for cross-channel attribution.                   |
        | **Items POS-Sellable but Not Online-Visible**    | Merchant rule      | Items with ecom\_visibility in (HIDDEN, UNINDEXED, UNAVAILABLE) , surfaces underused online channel for unified-catalog Square merchants.                |
        | **Online-Only SKUs**                             | Watch only         | Items with present\_at\_all\_locations=false AND ecom\_visibility=VISIBLE , online-only catalog complement.                                              |
        | **Orders by Status**                             | Watch only         | Orders by Status from Square Online, grouped under Revenue & Growth. Computes when a live Square Online integration is connected; reconciles ecommerce   |
        | **Products Missing SEO Title**                   | Alert band 10 / 30 | Catalog items whose Square Online ecom\_seo\_data.page\_title is empty. No data if this store has no active Square Online site (POS-only).               |
        | **Repeat Customer Rate**                         | Alert band 25 / 10 | Description pending editorial review; the signal is live.                                                                                                |
        | **Revenue Trend**                                | Alert band 0 / -5  | Revenue Trend from Square Online, grouped under Revenue & Growth. Computes when a live Square Online integration is connected; reconciles ecommerce ag   |
        | **Revenue by Channel (POS / Online / Invoices)** | Watch only         | Source-name breakdown: SQUARE\_POS, SQUARE\_ONLINE, INVOICES, etc. Surfaces unified-commerce channel mix that's distinctive to Square's POS+online story |
        | **Revenue by Location (in-store)**               | Watch only         | Per-location revenue rollup , multi-location Square merchants need per-store visibility.                                                                 |
        | **Square Orders to Email Attribution**           | Watch only         | Square Orders to Email Attribution from Square Online, grouped under Order Issues. Computes when a live Square Online integration is connected; reconc   |
        | **Top Products by Revenue**                      | Watch only         | Top Products by Revenue from Square Online, grouped under Revenue & Growth. Computes when a live Square Online integration is connected; reconciles ec   |
        | **Total Revenue (30d, all channels)**            | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                                |
      </Accordion>

      <Accordion title="Protect revenue (13 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Canceled Orders (24h)**                          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Rate**                                | Alert band 3 / 1   | Conversion Rate from Square Online, grouped under Revenue at Risk. Computes when a live Square Online integration is connected; reconciles ecommerce a |
        | **Fulfillment Rate**                               | Alert band 95 / 90 | % of orders (30d) where every Fulfillment reached Square's COMPLETED state , distinct from the order-level completion/cancellation status above.       |
        | **High-Value Square Customers Unengaged on Email** | Merchant rule      | High-Value Square Customers Unengaged on Email, broken down by row.                                                                                    |
        | **Low-Stock Products**                             | Watch only         | Low-Stock Products from Square Online, grouped under Catalogue Health. Computes when a live Square Online integration is connected; reconciles ecommer |
        | **Out-of-Stock Items**                             | Alert band 0 / 5   | Description pending editorial review; the signal is live.                                                                                              |
        | **Oversell Risk (negative on-hand projected)**     | Merchant rule      | Alerts for Oversell Risk (negative on-hand projected).                                                                                                 |
        | **POS vs Online Inventory Parity**                 | Merchant rule      | POS vs Online Inventory Parity, broken down by row.                                                                                                    |
        | **POS ↔ Online Inventory Drift**                   | Merchant rule      | Variations showing different on-hand quantity between POS view and Square Online view , root oversell risk for unified-commerce merchants.             |
        | **Refund Rate**                                    | Alert band 2 / 5   | Refund Rate from Square Online, grouped under Refunds & Cancellations. Computes when a live Square Online integration is connected; reconciles ecommer |
        | **Revenue at Risk (live)**                         | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Square Inventory vs Marketplace Listings**       | Merchant rule      | Square Inventory vs Marketplace Listings.                                                                                                              |
        | **Square Orders → Email Attribution**              | Merchant rule      | Square Orders → Email Attribution, broken down by row.                                                                                                 |
      </Accordion>

      <Accordion title="Run operations (13 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Locations**                     | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Order Value**                  | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Email-Opted-In Customers (Directory)** | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Items Missing SKU**                    | Merchant rule      | SKU-less items break inventory + reporting + cross-channel parity. Hot-button for POS+online merchants.                                                |
        | **New Customers (30d)**                  | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Orders**                          | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Order Completion Rate**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Order Volume (all channels)**          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Orders by Channel**                    | Watch only         | Orders by Channel.                                                                                                                                     |
        | **POS to Online Inventory Drift**        | Watch only         | POS to Online Inventory Drift from Square Online, grouped under Catalogue Health. Computes when a live Square Online integration is connected; reconci |
        | **POS to Online Inventory Drift Alert**  | Watch only         | POS to Online Inventory Drift Alert from Square Online, grouped under Catalogue Health. Computes when a live Square Online integration is connected; r |
        | **POS ↔ Online Inventory Drift Alert**   | Merchant rule      | Square-distinctive , unified-commerce inventory parity is the killer audit signal.                                                                     |
        | **Total Customers (Directory)**          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                                        |
        | -------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **Products Missing Description** | Alert band 5 / 20 | Catalog items whose description\_plaintext is empty , a shopper page with nothing to read beyond a photo and a price. |
        | **Total Catalog Items**          | Watch only        | Description pending editorial review; the signal is live.                                                             |
        | **Total Item Variations**        | Watch only        | Description pending editorial review; the signal is live.                                                             |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                          | Alert behaviour | What it tracks                                                                              |
        | ------------------------------- | --------------- | ------------------------------------------------------------------------------------------- |
        | **OAuth Token Refresh Failure** | Merchant rule   | Square access tokens are 30-day lived , refresh failures silently break ingest; must alert. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **3 write** operations across catalog lists, customers, inventory countbatchretrieves, locations, oauth2tokens, order searchs on Square Online. 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=square-online)

    #### Ready to build your first Square Online 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                      | Read operations | Write operations |
      | ----------------------------- | --------------- | ---------------- |
      | catalog lists                 | 1               | 0                |
      | customers                     | 1               | 0                |
      | inventory countbatchretrieves | 0               | 1                |
      | locations                     | 1               | 0                |
      | oauth2tokens                  | 0               | 1                |
      | order searchs                 | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# StackAdapt on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/stackadapt

Monitor StackAdapt campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor StackAdapt campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/stackadapt) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=stackadapt)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (38 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                       |
        | ----------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------- |
        | **All Conversions**                 | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **CPC by Campaign**                 | Watch only         | CPC by Campaign.                                                                                                     |
        | **CTR by Campaign**                 | Watch only         | CTR by Campaign.                                                                                                     |
        | **Campaign Comparison**             | Watch only         | Campaign Comparison, broken down by row.                                                                             |
        | **Clicks vs Conversions**           | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Conversion Actions Breakdown**    | Watch only         | Conversion Actions Breakdown.                                                                                        |
        | **Conversion Drop Alert**           | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Conversion Funnel**               | Watch only         | Conversion Funnel, stage by stage.                                                                                   |
        | **Conversion Lag**                  | Watch only         | Conversion Lag, compared across items.                                                                               |
        | **Conversion Rate Trend**           | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Conversion Rate by Campaign**     | Watch only         | Conversion Rate by Campaign.                                                                                         |
        | **Conversion Rate by Device**       | Watch only         | Conversion Rate by Device.                                                                                           |
        | **Conversions Trend**               | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Conversions by Campaign**         | Watch only         | Conversions by Campaign.                                                                                             |
        | **Conversions by Country**          | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Conversions by Day of Week**      | Watch only         | Conversions by Day of Week.                                                                                          |
        | **Conversions by Device**           | Watch only         | Conversions by Device.                                                                                               |
        | **Conversions by Hour**             | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Landing Page Revenue**            | Watch only         | Landing Page Revenue, broken down by row.                                                                            |
        | **Overspending Campaigns**          | Watch only         | Overspending Campaigns, broken down by row.                                                                          |
        | **ROAS**                            | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                            |
        | **ROAS Dropped Below Threshold**    | Alert band 3 / 1.5 | First signal that StackAdapt's contextual + native targeting just lost its edge.                                     |
        | **ROAS Trend**                      | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **ROAS by Campaign**                | Watch only         | ROAS by Campaign.                                                                                                    |
        | **ROAS by Day of Week**             | Watch only         | ROAS by Day of Week.                                                                                                 |
        | **ROAS by Device**                  | Watch only         | ROAS by Device.                                                                                                      |
        | **ROAS by Region**                  | Watch only         | ROAS by Region.                                                                                                      |
        | **Revenue by Campaign**             | Watch only         | Revenue by Campaign.                                                                                                 |
        | **Search Terms Report**             | Watch only         | Search Terms Report, broken down by row.                                                                             |
        | **Spend by Campaign**               | Watch only         | Spend by Campaign.                                                                                                   |
        | **Top Cities by Conversions**       | Watch only         | Top Cities by Conversions.                                                                                           |
        | **Top Keywords by Conversions**     | Watch only         | Top Keywords by Conversions.                                                                                         |
        | **Top Performing Campaigns**        | Watch only         | Top Performing Campaigns, broken down by row.                                                                        |
        | **Total Revenue**                   | Watch only         | Description pending editorial review; the signal is live.                                                            |
        | **Underspending Campaigns**         | Watch only         | Underspending Campaigns, broken down by row.                                                                         |
        | **Universal Pixel Tracking Broken** | Merchant rule      | StackAdapt's first-party audience layer relies on the Universal Pixel , decay = audience-graph collapse within days. |
        | **Worst Performing Campaigns**      | Watch only         | Worst Performing Campaigns, broken down by row.                                                                      |
        | **Zero-Conversion Spend**           | Watch only         | Description pending editorial review; the signal is live.                                                            |
      </Accordion>

      <Accordion title="Run operations (18 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                            |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------------------- |
        | **Budget Utilisation**               | Alert band 70 / 30 | Description pending editorial review; the signal is live.                 |
        | **CPA Trend**                        | Watch only         | Description pending editorial review; the signal is live.                 |
        | **CPA by Keyword**                   | Watch only         | CPA by Keyword.                                                           |
        | **CPC Anomaly**                      | Watch only         | Description pending editorial review; the signal is live.                 |
        | **CPC Spike Detection**              | Watch only         | Description pending editorial review; the signal is live.                 |
        | **CPC Trend**                        | Alert band 0 / 25  | Description pending editorial review; the signal is live.                 |
        | **CTR Trend**                        | Watch only         | Description pending editorial review; the signal is live.                 |
        | **CTR by Keyword**                   | Watch only         | CTR by Keyword.                                                           |
        | **Impression Share**                 | Alert band 70 / 40 | Description pending editorial review; the signal is live.                 |
        | **Impressions Trend**                | Watch only         | Description pending editorial review; the signal is live.                 |
        | **Quality Score Distribution**       | Alert band 7 / 4   | Quality Score Distribution, compared across items.                        |
        | **Spend Anomaly**                    | Watch only         | Description pending editorial review; the signal is live.                 |
        | **Spend Over Time**                  | Alert band 0 / -10 | Description pending editorial review; the signal is live.                 |
        | **Spend vs Budget**                  | Watch only         | Description pending editorial review; the signal is live.                 |
        | **Top Keywords by Spend**            | Watch only         | Top Keywords by Spend.                                                    |
        | **Total Spend**                      | Watch only         | Description pending editorial review; the signal is live.                 |
        | **Wasted Spend**                     | Watch only         | Description pending editorial review; the signal is live.                 |
        | **Wasted-Spend Burst (3-day spike)** | Alert band 5 / 50  | Catches a runaway native-test budget before it eats the mid-market spend. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                      |
        | -------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **Active PMP Catalog Deals on Out-of-Stock SKUs**  | Alert band 5 / 50 | StackAdapt's native + display catalog deals running on OOS SKUs. Pause the creative pool, hold the budget.          |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | Brand-aware audiences also reached via Google organic. Cannibalisation = pure margin reclaim.                       |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                           |
        | **Landing Pages with Poor Web Vitals**             | Merchant rule     | Native and CTV click-throughs land on the same merchant pages , LCP regression breaks the click-to-conversion path. |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on StackAdapt catalog campaigns whose Feedonomics feed has live rejections.                                       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across accounts, campaigns, creatives, oauthtokens, report performances on StackAdapt. 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=stackadapt)

    #### Ready to build your first StackAdapt 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | accounts            | 1               | 0                |
      | campaigns           | 1               | 0                |
      | creatives           | 1               | 0                |
      | oauthtokens         | 0               | 1                |
      | report performances | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Atlassian Statuspage on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/statuspage

Monitor Atlassian Statuspage performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Atlassian Statuspage performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=statuspage)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="14">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (10 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                                                  |
        | ---------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Merchant rule                | Incidents moved to identified - cause is known and a fix is in flight.                                          |
        | **Alerts Firing**            | Alert band 0 / 3             | Published incidents still in the investigating state - the page is openly telling customers something is wrong. |
        | **Incidents Open**           | Alert band 0 / 3             | Unresolved incidents published on the status page right now.                                                    |
        | **Incidents Resolved (24h)** | Merchant rule                | Incidents closed in the last 24 hours - recovery throughput.                                                    |
        | **Mean Time To Acknowledge** | Alert band 300000 / 900000   | Average gap from incident creation to the identified/monitoring update - how fast the team confirms a cause.    |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Average gap from incident creation to resolution - how fast published incidents actually get closed.            |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Rolling component-group availability vs the SLA target. 99.9% is two-nines-plus; below 99.5% is a breach.       |
        | **Services Down**            | Alert band 0 / 1             | Components in major\_outage - customer-facing outage surface published to the status page.                      |
        | **Services Healthy**         | Alert band 0 / -10           | Components reporting operational across the status page.                                                        |
        | **Top Alerting Services**    | Merchant rule                | Components / groups generating the most incidents - where to spend reliability effort first.                    |
      </Accordion>

      <Accordion title="Customer experience (7 signals)">
        | Signal                   | Alert behaviour        | What it tracks                                                                                                        |
        | ------------------------ | ---------------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.95 / 0.7  | Satisfied/tolerating/frustrated ratio derived from the system metrics published to the status page. 0.94+ is healthy. |
        | **Avg Response Time**    | Alert band 200 / 1000  | Description pending editorial review; the signal is live.                                                             |
        | **Error Rate**           | Alert band 0.5 / 2     | Description pending editorial review; the signal is live.                                                             |
        | **Services Degraded**    | Alert band 0 / 2       | Components in degraded\_performance or partial\_outage - the early-warning band before a full outage.                 |
        | **Throughput (req/min)** | Alert band 0 / -10     | Throughput (req/min) over time.                                                                                       |
        | **p95 Latency**          | Alert band 800 / 1500  | Description pending editorial review; the signal is live.                                                             |
        | **p99 Latency**          | Alert band 1500 / 3000 | Description pending editorial review; the signal is live.                                                             |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                                | Alert behaviour | What it tracks                                                                                                      |
        | ------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **Checkout Component Health × Sales** | Merchant rule   | Checkout-component status overlaid with order volume - when the component degrades, sales follow.                   |
        | **Revenue at Risk (live)**            | Merchant rule   | Live \$/min loss while any component is in major\_outage and a commerce sibling reports velocity. The COO's number. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                 |
        | ------------------- | --------------- | ------------------------------------------------------------------------------ |
        | **Top Error Types** | Merchant rule   | Most common incident impact bands / failure causes across published incidents. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **11 read** and **3 write** operations across pageincidents, pagecomponents, pages, pagecomponentgroups, pageincidentunresolveds, pagemetrics on Atlassian Statuspage. 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=statuspage)

    #### Ready to build your first Atlassian Statuspage 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                | Read operations | Write operations |
      | ----------------------- | --------------- | ---------------- |
      | pageincidents           | 2               | 2                |
      | pagecomponents          | 2               | 1                |
      | pages                   | 2               | 0                |
      | pagecomponentgroups     | 1               | 0                |
      | pageincidentunresolveds | 1               | 0                |
      | pagemetrics             | 1               | 0                |
      | pagemetricsdatas        | 1               | 0                |
      | pagesubscribers         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Strapi on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/strapi

Monitor Strapi publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Strapi publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=strapi)

<CardGroup>
  <Card title="18">
    performance signals
  </Card>

  <Card title="2">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (10 signals)">
        | Signal                          | Alert behaviour        | What it tracks                                                                                                |
        | ------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------- |
        | **Accessibility Score**         | Alert band 90 / 70     | Lighthouse accessibility category (0-100).                                                                    |
        | **CLS (Mobile)**                | Alert band 0.1 / 0.25  | Cumulative Layout Shift p75 (mobile). Good \<0.1, poor >0.25.                                                 |
        | **CWV Pass Rate (Mobile)**      | Alert band 75 / 50     | Share of real-user sessions passing all three Core Web Vitals (mobile). Good >75%.                            |
        | **INP (Mobile)**                | Alert band 200 / 500   | Interaction to Next Paint p75 (mobile). Good \<200ms, poor >500ms.                                            |
        | **LCP (Mobile)**                | Alert band 2500 / 4000 | Largest Contentful Paint p75 from the Strapi site's CrUX field data (mobile). Good \<2.5s, poor >4s.          |
        | **Performance Score (Desktop)** | Alert band 90 / 50     | Lighthouse performance category (0-100), desktop strategy.                                                    |
        | **Performance Score (Mobile)**  | Alert band 90 / 50     | Lighthouse performance category (0-100), mobile strategy. Good >=90, poor \<50.                               |
        | **Render-Blocking Resources**   | Alert band 200 / 500   | Lighthouse render-blocking-resources audit - wasted ms from blocking CSS/JS the Strapi theme ships.           |
        | **Speed Index**                 | Alert band 3400 / 5800 | Lighthouse speed-index audit (ms) - how quickly content is visually populated.                                |
        | **TTFB (Mobile)**               | Alert band 800 / 1800  | Time To First Byte p75 (mobile) - the headless API-call cascade shows up here first. Good \<0.8s, poor >1.8s. |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                   | Alert behaviour              | What it tracks                                                                        |
        | ------------------------ | ---------------------------- | ------------------------------------------------------------------------------------- |
        | **Best Practices Score** | Alert band 90 / 70           | Lighthouse best-practices category (0-100).                                           |
        | **Stale Content**        | Alert band 10 / 40           | % of entries (sampled, up to 100) not updated in the last 12 months.                  |
        | **Total Blocking Time**  | Alert band 200 / 600         | Lighthouse total-blocking-time audit (ms) - main-thread blocking between FCP and TTI. |
        | **Total Page Weight**    | Alert band 1572864 / 3145728 | Lighthouse total-byte-weight audit (bytes transferred). Good \<1.5MB, poor >3MB.      |
      </Accordion>

      <Accordion title="Grow revenue (3 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                             |
        | --------------------------- | ------------------ | ------------------------------------------------------------------------------------------ |
        | **Publishing Cadence**      | Alert band 4 / 1   | Entries published under the configured content type in the last 30 days.                   |
        | **SEO Score**               | Alert band 90 / 70 | Lighthouse SEO category (0-100). Crawlability/markup hygiene of the Strapi-rendered pages. |
        | **Slow High-Traffic Pages** | Merchant rule      | Slow High-Traffic Pages, broken down by row.                                               |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                        | Alert behaviour | What it tracks                                            |
        | ----------------------------- | --------------- | --------------------------------------------------------- |
        | **Bounce Lift on Slow Pages** | Watch only      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (2)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Over 40% of content not updated in 12 months">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When over 40 percent of content has not been touched in a year, decay outpaces creation; rankings quietly rot page by page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-STALE-001`
      </Accordion>

      <Accordion title="Publishing pipeline stalled (no post in 30 days)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A stalled publishing pipeline slowly starves organic traffic; content compounds only while it keeps shipping.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CMS-PUBLISH-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across contenttypes, contenttypebuildercontenttypes, runpagespeeds, usermes on Strapi. 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=strapi)

    #### Ready to build your first Strapi 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                       | Read operations | Write operations |
      | ------------------------------ | --------------- | ---------------- |
      | contenttypes                   | 1               | 1                |
      | contenttypebuildercontenttypes | 1               | 0                |
      | runpagespeeds                  | 1               | 0                |
      | usermes                        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Stripe on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/stripe

Monitor Stripe payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Stripe payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/stripe) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=stripe)

<CardGroup>
  <Card title="7">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="589">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (7)">
    ### Monitor performance

    7 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (3 signals)">
        | Signal                    | Alert behaviour | What it tracks                            |
        | ------------------------- | --------------- | ----------------------------------------- |
        | **Average Charge Amount** | Watch only      | Average amount per successful charge.     |
        | **Gross Revenue**         | Watch only      | Total gross revenue processed via Stripe. |
        | **Revenue Over Time**     | Watch only      | Stripe revenue trend over time.           |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal            | Alert behaviour  | What it tracks                            |
        | ----------------- | ---------------- | ----------------------------------------- |
        | **Net Revenue**   | Watch only       | Revenue after refunds and fees.           |
        | **Refund Rate**   | Alert band 2 / 5 | Percentage of charges that were refunded. |
        | **Total Refunds** | Watch only       | Total refund amount issued.               |
      </Accordion>

      <Accordion title="Run operations (1 signals)">
        | Signal            | Alert behaviour | What it tracks                |
        | ----------------- | --------------- | ----------------------------- |
        | **Total Charges** | Watch only      | Number of successful charges. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **263 read** and **326 write** operations across accounts, account externalaccounts, account peoples, account persons, applicationfeerefunds, chargerefunds on Stripe. 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=stripe)

    #### Ready to build your first Stripe 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | accounts                 | 3               | 3                |
      | account externalaccounts | 2               | 3                |
      | account peoples          | 2               | 3                |
      | account persons          | 2               | 3                |
      | applicationfeerefunds    | 2               | 3                |
      | chargerefunds            | 2               | 3                |
      | coupons                  | 2               | 3                |
      | customers                | 2               | 3                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# SugarCRM on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/sugarcrm

Monitor SugarCRM pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor SugarCRM 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=sugarcrm)

<CardGroup>
  <Card title="31">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (31)">
    ### Monitor performance

    31 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                     | Alert behaviour    | What it tracks                                                                                                                                          |
        | -------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of two confirmed real SugarCRM Contact fields: share with a populated email array (Sidecar's confirmed field for email-address-bearing modul  |
        | **Click-to-Open Rate**     | Alert band 10 / 3  | Clicks / opens - message relevance. Gauge bands: good ≥10%, warn ≤3%.                                                                                   |
        | **Email Click Rate**       | Alert band 2 / 0.5 | Clicks / delivered. Gauge bands: good ≥2%, warn ≤0.5%.                                                                                                  |
        | **Email Open Rate**        | Alert band 20 / 10 | Opens / delivered. Gauge bands: good ≥20%, warn ≤10%.                                                                                                   |
        | **Flow Count Summary**     | Merchant rule      | Total flows (process definitions) and how many are active.                                                                                              |
        | **Flow Trigger Types**     | Merchant rule      | Flows grouped by trigger type (manual/record-create/record-update/scheduled/related-module).                                                            |
        | **Flows List**             | Merchant rule      | Tabular list of flows with status, trigger and 30d enrollment.                                                                                          |
        | **Lists Overview**         | Merchant rule      | Per-list table: name, type, entry count, active members.                                                                                                |
        | **Segments Overview**      | Merchant rule      | Dynamic segments (target lists) with member counts and last refresh.                                                                                    |
        | **Stalled Deal Rate**      | Alert band 10 / 30 | Share of open Opportunities (sales\_stage outside Closed Won/Closed Lost) with no linked Call or Task activity in the last 14 days, joined via the stan |
        | **Top Lists by Name**      | Merchant rule      | Largest lists ranked by entry count.                                                                                                                    |
      </Accordion>

      <Accordion title="Grow revenue (11 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                                                |
        | ----------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule   | Count of marketing campaigns by status (planning/active/inactive/complete/in-queue/sending/draft).                            |
        | **Checkout-to-Order Rate**    | Merchant rule   | Of campaign-driven checkouts started, the share that became orders; reconciled with the ecom sibling's order events.          |
        | **Checkouts Started**         | Merchant rule   | Checkouts started attributed to campaign activity in the window.                                                              |
        | **Conversion Rate**           | Merchant rule   | Orders / delivered emails - overall campaign conversion.                                                                      |
        | **Engagement Funnel**         | Merchant rule   | Sent → delivered → opened → clicked → converted funnel for outbound campaign email.                                           |
        | **List Health Summary**       | Merchant rule   | Active-member share across lists - low = stale/decaying audience.                                                             |
        | **Placed Orders Total**       | Merchant rule   | Orders attributed to campaign sends in the window.                                                                            |
        | **Revenue per Recipient**     | Merchant rule   | Attributed revenue divided by unique recipients.                                                                              |
        | **Revenue per Send**          | Merchant rule   | Attributed revenue divided by total sends.                                                                                    |
        | **Total Revenue**             | Merchant rule   | Campaign-attributed revenue from SugarCRM marketing campaigns; cross-checked against the ecom sibling's actual order revenue. |
        | **Total Sends**               | Merchant rule   | Total emails sent across marketing campaigns in the window.                                                                   |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                        | Alert behaviour      | What it tracks                                                                                                       |
        | ----------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule        | Estimated subscribed/deliverable contacts (email\_opt\_out = false, invalid\_email = false).                         |
        | **Bounce Rate**               | Alert band 2 / 5     | Bounces / sent (inverse gauge). Bands: good ≤2%, warn ≥5%. Sustained high = list-hygiene or auth (SPF/DKIM) problem. |
        | **Delivery Rate**             | Alert band 98 / 95   | Delivered / sent. Gauge bands: good ≥98%, warn ≤95%.                                                                 |
        | **Email Health KPIs**         | Merchant rule        | Composite email-health roll-up (delivery, open, click, bounce) in one card.                                          |
        | **Flow Status Breakdown**     | Merchant rule        | Flows grouped by status (active/paused/draft/inactive) - paused-heavy = abandoned automation.                        |
        | **Refund Rate**               | Alert band 1 / 5     | Refunded share of campaign-attributed revenue - high = post-purchase dissatisfaction or returns leakage.             |
        | **Spam Complaint Rate**       | Alert band 0.1 / 0.3 | Spam reports / delivered (inverse gauge). Bands: good ≤0.1%, warn ≥0.3%. Above 0.3% risks sender-reputation damage.  |
        | **Unsubscribe Rate**          | Alert band 0.5 / 2   | Unsubscribes / delivered (inverse gauge). Bands: good ≤0.5%, warn ≥2%.                                               |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal         | Alert behaviour | What it tracks                                |
        | -------------- | --------------- | --------------------------------------------- |
        | **List Count** | Merchant rule   | Total target lists configured in the account. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **2 write** operations across pmsebpmflows, calls, campaigns, contacts, mes, oauth2tokens on SugarCRM. 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=sugarcrm)

    #### Ready to build your first SugarCRM 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | pmsebpmflows  | 1               | 1                |
      | calls         | 1               | 0                |
      | campaigns     | 1               | 0                |
      | contacts      | 1               | 0                |
      | mes           | 1               | 0                |
      | oauth2tokens  | 0               | 1                |
      | opportunitys  | 1               | 0                |
      | prospectlists | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Supabase on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/supabase

Monitor Supabase health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Supabase health, cost and reliability signals, and catch incidents and runaway spend early.

[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=supabase)

<CardGroup>
  <Card title="33">
    performance signals
  </Card>

  <Card title="9">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (33)">
    ### Monitor performance

    33 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Control risk and change (13 signals)">
        | Signal                                          | Alert behaviour      | What it tracks                                                                                  |
        | ----------------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------- |
        | **Active Realtime Channels**                    | Watch only           | Description pending editorial review; the signal is live.                                       |
        | **Auth Active Users (24h)**                     | Watch only           | Supabase Auth , users with a session in the last 24h.                                           |
        | **Auth Sign-In Error Rate %**                   | Merchant rule        | Supabase-distinctive , Auth flow failures lock users out of the storefront.                     |
        | **Database Query Error Rate %**                 | Alert band 0.1 / 1   | Description pending editorial review; the signal is live.                                       |
        | **Database Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1   | Alerts for Database Query Error Rate Spike (>1% in 5m).                                         |
        | **Edge Function Error Rate %**                  | Merchant rule        | Supabase Edge Functions (Deno) invocation failures.                                             |
        | **PostgREST 5xx Error Rate %**                  | Alert band 0.1 / 1   | Description pending editorial review; the signal is live.                                       |
        | **PostgREST 5xx Error Spike (>1% in 5m)**       | Alert band 0.1 / 1   | Supabase-distinctive , PostgREST is the merchant app's actual API. 5xx = app down.              |
        | **PostgREST API Latency p95 (ms)**              | Alert band 50 / 200  | Supabase-distinctive , the auto-generated REST layer is what the merchant's app actually calls. |
        | **PostgREST API Latency p99 (ms)**              | Alert band 100 / 500 | Description pending editorial review; the signal is live.                                       |
        | **PostgREST Request Rate (req/sec)**            | Watch only           | PostgREST Request Rate (req/sec) over time.                                                     |
        | **Realtime Connected Clients**                  | Watch only           | Supabase-distinctive , WebSocket subscribers on Realtime channels.                              |
        | **Realtime Disconnect Rate (per min)**          | Merchant rule        | Disconnect storms = Realtime instability; clients lose live updates.                            |
      </Accordion>

      <Accordion title="Run operations (12 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                   |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------ |
        | **Buffer Cache Hit Rate %**            | Alert band 95 / 80 | Description pending editorial review; the signal is live.                                        |
        | **Connections In Use**                 | Watch only         | Description pending editorial review; the signal is live.                                        |
        | **Database Disk Usage %**              | Alert band 70 / 90 | Supabase tiers cap disk , hitting the cap puts the project in read-only / restricted mode.       |
        | **Database Queries per Second (live)** | Watch only         | Description pending editorial review; the signal is live.                                        |
        | **Last Backup Age (hours)**            | Alert band 24 / 72 | Supabase daily backups (Pro+); Point-in-Time Recovery on higher tiers. Free tier has no backup.  |
        | **Memory Usage %**                     | Merchant rule      | Description pending editorial review; the signal is live.                                        |
        | **Project Uptime**                     | Watch only         | Description pending editorial review; the signal is live.                                        |
        | **Read Replica Lag (seconds)**         | Alert band 1 / 10  | Supabase read replicas are a paid feature , regional. Lag affects read-routed queries.           |
        | **Read Replicas**                      | Watch only         | Description pending editorial review; the signal is live.                                        |
        | **Supabase Health Score**              | Merchant rule      | Description pending editorial review; the signal is live.                                        |
        | **Supavisor Pool Saturation %**        | Alert band 70 / 90 | Supavisor (Supabase's connection pooler) saturation. Free / Pro tiers have hard connection caps. |
        | **Supavisor Pool at >90% Saturation**  | Alert band 70 / 90 | Alerts for Supavisor Pool at >90% Saturation.                                                    |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                            | Alert behaviour    | What it tracks                                                                                     |
        | ------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Slow PostgREST Queries During Checkout Window** | Merchant rule      | Slow PostgREST Queries During Checkout Window, broken down by row.                                 |
        | **Supabase Products Table vs Ecom Catalog**       | Merchant rule      | Description pending editorial review; the signal is live.                                          |
        | **Supabase QPS Spike vs Ecom Order Rate**         | Merchant rule      | Description pending editorial review; the signal is live.                                          |
        | **Supavisor Pool Saturation vs Traffic Burst**    | Alert band 70 / 90 | Supabase-distinctive , Supavisor pool caps are tier-bound; burst on free / pro tier exhausts fast. |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                              | Alert behaviour  | What it tracks                                            |
        | ----------------------------------- | ---------------- | --------------------------------------------------------- |
        | **Deadlocks (last 5m)**             | Alert band 0 / 5 | Description pending editorial review; the signal is live. |
        | **Postgres Query Latency p95 (ms)** | Watch only       | Description pending editorial review; the signal is live. |
        | **Slow-Query Rate %**               | Alert band 1 / 5 | Description pending editorial review; the signal is live. |
        | **Top 10 Slowest Queries**          | Watch only       | Top 10 Slowest Queries, broken down by row.               |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (9)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Connection pool saturation above 90%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-001`
      </Accordion>

      <Accordion title="Disk usage above 90%">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CAP-002`
      </Accordion>

      <Accordion title="Query error rate above 1% in last 5 minutes">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-ERR-001`
      </Accordion>

      <Accordion title="Last successful backup older than 72 hours">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-BAK-001`
      </Accordion>

      <Accordion title="Replication lag above 10 seconds">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-REP-001`
      </Accordion>

      <Accordion title="Slow-query rate above 5% of total">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-002`
      </Accordion>

      <Accordion title="p95 query latency above 200ms sustained 15m">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-001`
      </Accordion>

      <Accordion title="Buffer / cache hit rate below 80%">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-CACHE-001`
      </Accordion>

      <Accordion title="Deadlocks detected (>0 in last 5 minutes)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `DB-PERF-003`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across pgstatactivitys, pgstatreplications, projects, projectanalyticsendpointlogalls, realtimetenanthealths, rpcpgstatstatements on Supabase. 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=supabase)

    #### Ready to build your first Supabase 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                        | Read operations | Write operations |
      | ------------------------------- | --------------- | ---------------- |
      | pgstatactivitys                 | 1               | 0                |
      | pgstatreplications              | 1               | 0                |
      | projects                        | 1               | 0                |
      | projectanalyticsendpointlogalls | 1               | 0                |
      | realtimetenanthealths           | 1               | 0                |
      | rpcpgstatstatements             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Swell on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/swell

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Swell.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Swell.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/swell) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=swell)

<CardGroup>
  <Card title="46">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (46)">
    ### Monitor performance

    46 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (22 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Ad Spend on Out-of-Stock SKUs**           | Merchant rule      | Spend on SKUs that can't convert because they're OOS. Pause immediately - pure waste.                                                                  |
        | **Billing Failure Rate**                           | Merchant rule      | Declined / errored recurring payments as % of attempts. Expired cards + gateway errors silently bleed MRR before churn even shows. Dunning trigger.    |
        | **Billing Failure Spike**                          | Merchant rule      | Sudden rise in declined recurring charges = gateway outage or a card-network event. MRR bleeding now - dunning + alert.                                |
        | **Bundle SKU Stock Check**                         | Merchant rule      | Bundle products still sellable when a component SKU is out of stock = oversell risk. Swell-distinctive: bundle stock derives from components.          |
        | **Cancellation Rate**                              | Alert band 1 / 3   | Description pending editorial review; the signal is live.                                                                                              |
        | **Cancelled Subscriptions (30d)**                  | Merchant rule      | Subscriptions with date\_canceled in window. When cancelled outpaces new, MRR is shrinking - the leading churn signal.                                 |
        | **Churn-Risk Customers**                           | Merchant rule      | High-value accounts whose gap since date\_last\_order exceeds 2x their median reorder cycle = lapsing. Win-back targets.                               |
        | **High-MRR Subscribers Unengaged on Email**        | Merchant rule      | The subscribers most expensive to lose, going dark on email. Trigger a retention flow before they cancel.                                              |
        | **Low-Stock Products**                             | Merchant rule      | Products in stock\_status=low\_stock. Pair with velocity to flag stockout-imminent SKUs before they hit zero.                                          |
        | **Orders → Email Campaign Attribution**            | Merchant rule      | Email share of revenue. Low attribution despite an active ESP = under-utilised lifecycle channel - the cheapest growth lever for subscription brands.  |
        | **Out-of-Stock Products**                          | Alert band 0 / 5   | Description pending editorial review; the signal is live.                                                                                              |
        | **Overdue B2B Invoices**                           | Merchant rule      | Sum of grand\_total on invoices where paid=false and date\_due \< now. Working-capital leak - chase before it ages further. Only meaningful when Swell |
        | **Past-Due Subscriptions**                         | Merchant rule      | Subscriptions in status=past\_due\|unpaid. Each is MRR at imminent risk - recoverable with dunning if caught early.                                    |
        | **Payment Decline Rate**                           | Merchant rule      | Declined payments / payment attempts. High decline rate on checkout = gateway config or fraud-filter over-tuning; recoverable revenue.                 |
        | **Refund Rate**                                    | Alert band 2 / 5   | Refunded orders / total orders. Above 5% signals product-quality or expectation mismatch - and on subscriptions, predicts churn.                       |
        | **Refund Value (30d)**                             | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue at Risk (live)**                         | Merchant rule      | Sum of failed payments + past-due subscription MRR + OOS-attributed demand. Live \$ exposure across the store.                                         |
        | **Revenue at Risk / Min (active incidents)**       | Merchant rule      | Live \$/min loss while a connected monitoring incident is open. Headless storefronts fail silently - this is the dollar cost of the outage.            |
        | **Subscription Cancellation Burst**                | Merchant rule      | A cancellation burst usually signals a billing bug, a price-change backlash, or a delivery failure. Investigate root cause fast.                       |
        | **Subscription Churn Rate**                        | Alert band 20 / 50 | Cancelled subscriptions / active at period start. Above \~8% monthly is unsustainable for most subscription economics.                                 |
        | **Swell Inventory vs Active Marketplace Listings** | Merchant rule      | Marketplace orders for SKUs OOS on Swell = cancellations + dissatisfaction. Highest-priority cross-channel diagnostic.                                 |
        | **Top Accounts by Revenue**                        | Watch only         | Ranked by order\_value. Concentration view - reveals if revenue leans on a handful of accounts (dependency risk).                                      |
      </Accordion>

      <Accordion title="Grow revenue (12 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                          |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active B2B Accounts**             | Watch only         | Business-type accounts with an order in the last 90d. The B2B revenue base for Swell merchants running configurable pricing.                            |
        | **Active Subscriptions**            | Merchant rule      | Count of subscriptions in status=active\|trial. The base of recurring revenue - the single most-watched number for a subscription brand.                |
        | **Catalogue Completeness**          | Alert band 90 / 80 | % of active products with image, description, SKU and price all populated. Gaps suppress conversion on a headless storefront where the API is the only  |
        | **Discount Dependency**             | Alert band 20 / 40 | Share of orders (30d) carrying a code-based coupon (Order.coupon\_code). Distinct from the dollar-discount-vs-revenue metric other platforms carry unde |
        | **Monthly Recurring Revenue (MRR)** | Alert band 0 / -5  | Sum of recurring\_total normalised to a monthly cadence across active subscriptions. The north-star metric for recurring economics.                     |
        | **Products Missing SEO Meta**       | Alert band 10 / 30 | Active products with no meta\_title or meta\_description set - the dedicated SEO fields, distinct from the storefront description.                      |
        | **Repeat Purchase Rate**            | Alert band 25 / 10 | Description pending editorial review; the signal is live.                                                                                               |
        | **Revenue Trend**                   | Watch only         | Daily revenue over 90 days. Shows seasonality and the long arc of subscription compounding.                                                             |
        | **Revenue by Currency / Region**    | Watch only         | Revenue grouped by order currency. Swell merchants frequently sell multi-currency from one store via the storefront framework.                          |
        | **Revenue by Store**                | Watch only         | Per-store revenue split for merchants running multiple Swell stores under one team. Reveals which storefront is pulling weight.                         |
        | **Top Customers by Lifetime Spend** | Watch only         | Top Customers by Lifetime Spend.                                                                                                                        |
        | **Total Revenue (30d)**             | Alert band 0 / -5  | Sum of grand\_total on paid orders across 7/30/90d windows. Top-line pulse for one-off + subscription revenue combined.                                 |
      </Accordion>

      <Accordion title="Run operations (9 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Account Spend**        | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Average Order Value**          | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Fulfillment Rate**             | Alert band 95 / 90 | Share of orders (30d) with Order.delivered = true - Swell's own field for a completely-fulfilled order (see the Order entity's delivered help text for |
        | **New Subscriptions (30d)**      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **New vs Returning Customers**   | Watch only         | New vs Returning Customers, shown by share.                                                                                                            |
        | **Order Processing Backlog**     | Alert band 10 / 50 | Alerts for Order Processing Backlog.                                                                                                                   |
        | **Order Volume (30d)**           | Alert band 0 / -10 | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending / Unfulfilled Orders** | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Customers**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Catalogue quality (2 signals)">
        | Signal                           | Alert behaviour   | What it tracks                                                                                                                                          |
        | -------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Products Missing Description** | Alert band 5 / 20 | Active products with an empty description. The same field sw\_catalogue\_completeness folds into its composite %, broken out standalone so it can carry |
        | **Total Active Products**        | Watch only        | Description pending editorial review; the signal is live.                                                                                               |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                           | Alert behaviour | What it tracks                                                                                                                               |
        | -------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Swell API Failure Rate Spike** | Merchant rule   | Headless storefronts read live from the Swell Backend API - a failure spike means the storefront itself is degraded, not just the dashboard. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **0 write** operations across accounts, invoices, orders, payments, products, refunds on Swell. 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=swell)

    #### Ready to build your first Swell 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | accounts      | 1               | 0                |
      | invoices      | 1               | 0                |
      | orders        | 1               | 0                |
      | payments      | 1               | 0                |
      | products      | 1               | 0                |
      | refunds       | 1               | 0                |
      | subscriptions | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Taboola on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/taboola

Monitor Taboola campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor Taboola campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/taboola) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=taboola)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (39 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                               |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **All Conversions**                                | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **CPC by Campaign**                                | Watch only         | CPC by Campaign.                                                                                             |
        | **CTR by Campaign**                                | Watch only         | CTR by Campaign.                                                                                             |
        | **Campaign Comparison**                            | Watch only         | Campaign Comparison, broken down by row.                                                                     |
        | **Clicks vs Conversions**                          | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Conversion Actions Breakdown**                   | Watch only         | Conversion Actions Breakdown.                                                                                |
        | **Conversion Drop Alert**                          | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Conversion Funnel**                              | Watch only         | Conversion Funnel, stage by stage.                                                                           |
        | **Conversion Lag**                                 | Watch only         | Conversion Lag, compared across items.                                                                       |
        | **Conversion Rate Trend**                          | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Conversion Rate by Campaign**                    | Watch only         | Conversion Rate by Campaign.                                                                                 |
        | **Conversion Rate by Device**                      | Watch only         | Conversion Rate by Device.                                                                                   |
        | **Conversions Trend**                              | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Conversions by Campaign**                        | Watch only         | Conversions by Campaign.                                                                                     |
        | **Conversions by Country**                         | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Conversions by Day of Week**                     | Watch only         | Conversions by Day of Week.                                                                                  |
        | **Conversions by Device**                          | Watch only         | Conversions by Device.                                                                                       |
        | **Conversions by Hour**                            | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Landing Page Revenue**                           | Watch only         | Landing Page Revenue, broken down by row.                                                                    |
        | **Overspending Campaigns**                         | Watch only         | Overspending Campaigns, broken down by row.                                                                  |
        | **ROAS**                                           | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                    |
        | **ROAS Dropped Below Threshold**                   | Alert band 3 / 1.5 | Native ROAS shifts mean publisher whitelist drift OR creative-context mismatch , investigate within the day. |
        | **ROAS Trend**                                     | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **ROAS by Campaign**                               | Watch only         | ROAS by Campaign.                                                                                            |
        | **ROAS by Day of Week**                            | Watch only         | ROAS by Day of Week.                                                                                         |
        | **ROAS by Device**                                 | Watch only         | ROAS by Device.                                                                                              |
        | **ROAS by Region**                                 | Watch only         | ROAS by Region.                                                                                              |
        | **Revenue by Campaign**                            | Watch only         | Revenue by Campaign.                                                                                         |
        | **Search Terms Report**                            | Watch only         | Search Terms Report, broken down by row.                                                                     |
        | **Spend by Campaign**                              | Watch only         | Spend by Campaign.                                                                                           |
        | **Taboola Conversion Pixel Tracking Broken**       | Merchant rule      | Multi-step native-to-purchase funnel , pixel decay breaks the only attribution chain Taboola can see.        |
        | **Top Cities by Conversions**                      | Watch only         | Top Cities by Conversions.                                                                                   |
        | **Top Keywords by Conversions**                    | Watch only         | Top Keywords by Conversions.                                                                                 |
        | **Top Performing Campaigns**                       | Watch only         | Top Performing Campaigns, broken down by row.                                                                |
        | **Total Revenue**                                  | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Underspending Campaigns**                        | Watch only         | Underspending Campaigns, broken down by row.                                                                 |
        | **Wasted-Spend Burst (publisher placement drift)** | Alert band 5 / 50  | Catches a creative-publisher mismatch burning through budget on premium placements with no engagement.       |
        | **Worst Performing Campaigns**                     | Watch only         | Worst Performing Campaigns, broken down by row.                                                              |
        | **Zero-Conversion Spend**                          | Watch only         | Description pending editorial review; the signal is live.                                                    |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                  | Alert behaviour   | What it tracks                                                                                                        |
        | ------------------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------- |
        | **Active Product-Feed Native Ads on Out-of-Stock SKUs** | Alert band 5 / 50 | Taboola product-feed native ads on OOS SKUs , pause the feed entry, hold the spend.                                   |
        | **Branded Paid Clicks Cannibalising Organic**           | Merchant rule     | Native sponsored-content campaigns whose target audience already finds the brand via Google , pure margin reclaim.    |
        | **CTR Decline Alert**                                   | Watch only        | Description pending editorial review; the signal is live.                                                             |
        | **Landing Pages with Poor Web Vitals**                  | Merchant rule     | Native click-throughs are already a cold lead , slow landing pages compound the abandonment risk.                     |
        | **Spend on Campaigns with Active Feed Rejections**      | Merchant rule     | £ on Taboola product-feed campaigns whose Feedonomics feed has rejections. Native creative falls back, CTR collapses. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **2 write** operations across backstagecampaigns, backstagecampaignitems, backstageoauthtokens, backstagereportcampaignsummarydimensiondays, backstageusercurrentaccounts on Taboola. 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=taboola)

    #### Ready to build your first Taboola 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                    | Read operations | Write operations |
      | ------------------------------------------- | --------------- | ---------------- |
      | backstagecampaigns                          | 1               | 0                |
      | backstagecampaignitems                      | 1               | 0                |
      | backstageoauthtokens                        | 0               | 1                |
      | backstagereportcampaignsummarydimensiondays | 0               | 1                |
      | backstageusercurrentaccounts                | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Target Plus on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/target-plus

Monitor Target Plus listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Target Plus listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=target-plus)

<CardGroup>
  <Card title="36">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (36)">
    ### Monitor performance

    36 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (12 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by State**                               | Watch only         | AOV by State.                                                                                                                                          |
        | **Buyer Messages Unread**                      | Watch only         | Buyer Messages Unread as exposed by the Target Plus integration. The metric is computed from the latest available data and refreshed on the standard d |
        | **Days Since Last Payout**                     | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Fees Paid**                      | Watch only         | Marketplace Fees Paid as exposed by the Target Plus integration. The metric is computed from the latest available data and refreshed on the standard d |
        | **On-Time Dispatch Rate (Partner SLA)**        | Merchant rule      | Target Plus partners are held to enterprise-grade 99% on-time SLA. Sustained \<97% triggers partner-status review.                                     |
        | **Orders / Day**                               | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by State**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Partner Health Composite Crossed Threshold** | Alert band 95 / 85 | Target's composite partner-review trigger , any one crossing kicks the partner-status review process.                                                  |
        | **Pending Dispatch**                           | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                            | Watch only         | Pending Payouts as exposed by the Target Plus integration. The metric is computed from the latest available data and refreshed on the standard data re |
        | **Return Rate**                                | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                              |
        | **Target Plus Partner Health Score**           | Merchant rule      | Composite: SLA x feed-import-success x brand-compliance. Target reviews partner-status using a similar composite.                                      |
      </Accordion>

      <Accordion title="Protect revenue (9 signals)">
        | Signal                                                      | Alert behaviour   | What it tracks                                                                                                                    |
        | ----------------------------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Target Plus Listings for OOS SKUs on BC**          | Alert band 0 / 5  | Target Plus takes orders you can't fulfil → cancellations → partner-status review. Highest-priority sync gap.                     |
        | **Cancellation Rate**                                       | Merchant rule     | Description pending editorial review; the signal is live.                                                                         |
        | **Late Dispatch Rate (Partner Penalty)**                    | Merchant rule     | Sustained late dispatch crosses Target's partner-review threshold , partner-status loss = offboarding risk.                       |
        | **Late Dispatches Risking Partner Status**                  | Merchant rule     | Target's 99% on-time SLA is enterprise-grade; sustained breach risks partner-status loss / offboarding.                           |
        | **Listings Drifting from BC Source-of-Truth**               | Alert band 5 / 50 | SKUs where Target Plus catalog differs from BC , Target's manual curation flags these as brand-presentation drift.                |
        | **Listings Failing Feedonomics → Target Mirakl Validation** | Alert band 2 / 5  | % of Feedonomics-distributed listings rejected at Target's Mirakl import.                                                         |
        | **Net Revenue (after Target fees + refunds)**               | Alert band 0 / -5 | Description pending editorial review; the signal is live.                                                                         |
        | **Revenue at Risk (live)**                                  | Merchant rule     | (rejected-listings x velocity x ASP) + (SLA-breach partner-review impact) + (brand-compliance-flagged SKU visibility loss).       |
        | **SKUs Priced Differently vs Walmart / Amazon**             | Merchant rule     | Target Plus traditionally allows higher pricing than Walmart/Amazon (curated brand value), but extreme spreads erode buyer trust. |
      </Accordion>

      <Accordion title="Catalogue quality (9 signals)">
        | Signal                                       | Alert behaviour    | What it tracks                                                                                                                                        |
        | -------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Listings**                          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Brand-Presentation Compliance Flags**      | Alert band 5 / 50  | Target's manual curation flags brand-guide violations (image dims, restricted content, missing primary category). Compounds toward partner-review.    |
        | **Inactive / Suspended Listings**            | Alert band 5 / 50  | Description pending editorial review; the signal is live.                                                                                             |
        | **Listings Expiring Soon**                   | Watch only         | Listings Expiring Soon as exposed by the Target Plus integration. The metric is computed from the latest available data and refreshed on the standard |
        | **Mirakl Feed Import Success Rate**          | Alert band 90 / 70 | % of Mirakl product-feed import lines accepted by Target. Below 95% = attribute-schema regression to investigate.                                     |
        | **Mirakl Feed Rejections (24h)**             | Alert band 5 / 50  | Mirakl import errors , schema drift, attribute violations, image-dim violations.                                                                      |
        | **Rejected Listings (Mirakl import errors)** | Alert band 5 / 50  | Lines Target's Mirakl import rejected , common causes: missing required attribute, GTIN check digit, image-dimension violation.                       |
        | **Stale Listings (>180d no update)**         | Merchant rule      | Description pending editorial review; the signal is live.                                                                                             |
        | **Total Listings**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                             |
      </Accordion>

      <Accordion title="Grow revenue (6 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                           |
        | -------------------------------- | ------------------ | ---------------------------------------------------------------------------------------- |
        | **Average Order Value**          | Alert band 0 / -5  | Target Plus traditionally has higher AOV than Amazon/Walmart due to curated brand mix.   |
        | **Orders**                       | Watch only         | Description pending editorial review; the signal is live.                                |
        | **Revenue Over Time**            | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                |
        | **Target Plus Fee % of Revenue** | Alert band 12 / 18 | Total fees / gross revenue. Target Plus commission varies by category (typically 5-15%). |
        | **Top Listings by Revenue**      | Watch only         | Top Listings by Revenue.                                                                 |
        | **Total Revenue**                | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **2 write** operations across accounts, offers, orders, order accepts, order trackings, product imports on Target Plus. 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=target-plus)

    #### Ready to build your first Target Plus 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | accounts        | 1               | 0                |
      | offers          | 1               | 0                |
      | orders          | 1               | 0                |
      | order accepts   | 0               | 1                |
      | order trackings | 0               | 1                |
      | product imports | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Teams on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/teams

Monitor Teams performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Teams performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=teams)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Teams yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **3 write** operations across teamchannelmessages, teamchannels, mes, mejoinedteams, teamchannelmessagereplys on Teams. 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=teams)

    #### Ready to build your first Teams 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | teamchannelmessages      | 1               | 2                |
      | teamchannels             | 2               | 0                |
      | mes                      | 1               | 0                |
      | mejoinedteams            | 1               | 0                |
      | teamchannelmessagereplys | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Teamwork on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/teamwork

Monitor Teamwork performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Teamwork performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=teamwork)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Lead Time (days)**            | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                                                   |
        | **Backlog by Status**               | Watch only         | Backlog by Status.                                                                                                                                     |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Tasks in a Blocked / impeded task-list - the operational queue's stuck list.                                                                           |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                                                |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings actually got completed via the Teamwork pipeline. \<50% means we're filing faster than the agency drains - a retainer-m   |
        | **In Progress**                     | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Oldest Open (days)**              | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Tickets**                    | Merchant rule      | Total open Teamwork tasks across the default project - top-of-funnel backlog volume.                                                                   |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | People with >10 open tasks across the client portfolio - capacity bottleneck candidates.                                                               |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Sprint Progress**                 | Alert band 80 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Sprint Velocity (avg)**           | Merchant rule      | Sprint Velocity (avg) over time.                                                                                                                       |
        | **Throughput Trend**                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets Resolved (7d)**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                                                   |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings Open**          | Merchant rule      | Teamwork tasks we filed from audit findings that haven't been completed yet - the live backlog of things VortexIQ surfaced, read next to billable hour |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no last-changed-on movement for two weeks - on an agency these are the silent margin leaks while logged time accrues. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **4 write** operations across projecttaskjsons, mejsons, projectpeoplejsons, projectprojectjsons, projectprojecttasklistjsons, projecttasks on Teamwork. 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=teamwork)

    #### Ready to build your first Teamwork 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                    | Read operations | Write operations |
      | --------------------------- | --------------- | ---------------- |
      | projecttaskjsons            | 1               | 1                |
      | mejsons                     | 1               | 0                |
      | projectpeoplejsons          | 1               | 0                |
      | projectprojectjsons         | 1               | 0                |
      | projectprojecttasklistjsons | 1               | 0                |
      | projecttasks                | 1               | 0                |
      | projecttaskcommentjsons     | 0               | 1                |
      | projecttaskcompletejsons    | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Telegram on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/telegram

Monitor Telegram performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Telegram performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=telegram)

<CardGroup>
  <Card title="7">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (7)">
    ### Monitor performance

    7 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (3 signals)">
        | Signal                       | Alert behaviour | What it tracks                                                                                  |
        | ---------------------------- | --------------- | ----------------------------------------------------------------------------------------------- |
        | **Bot Username**             | Watch only      | getMe.result.username as @username (fallback first\_name when a bot has no username).           |
        | **Can Join Groups**          | Watch only      | getMe.result.can\_join\_groups rendered as Yes/No; whether the bot may be added to group chats. |
        | **Reads All Group Messages** | Watch only      | getMe.result.can\_read\_all\_group\_messages rendered as Yes/No (privacy mode off = Yes).       |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                 | Alert behaviour | What it tracks                                                                                                                                                |
        | ---------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Channel Configured** | Watch only      | Whether the optional chat\_id credential is set, rendered as Configured / Not configured. Derived from credential presence, no API call.                      |
        | **Chat Member Count**  | Watch only      | getChatMemberCount.result for the configured chat\_id. Degrades to no\_data reason chat\_id\_required when no chat\_id is set, or bot\_not\_in\_chat when the |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal             | Alert behaviour | What it tracks                                                                                                                                           |
        | ------------------ | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Bot Connection** | Watch only      | getMe.username (fallback first\_name) rendered as 'Connected as @username'. When the token is revoked getMe fails and the card degrades to no\_data (aut |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal         | Alert behaviour | What it tracks                                                                                                                                                |
        | -------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Chat Title** | Watch only      | getChat.result.title (fallback first\_name/id) for the configured chat\_id. Same gating as the member count: chat\_id\_required with no chat\_id, bot\_not\_i |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Telegram yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **1 write** operations across getchats, getchatmembercounts, getmes, sendmessages on Telegram. 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=telegram)

    #### Ready to build your first Telegram 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | getchats            | 1               | 0                |
      | getchatmembercounts | 1               | 0                |
      | getmes              | 1               | 0                |
      | sendmessages        | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# The Trade Desk on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/the-trade-desk

Monitor The Trade Desk campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor The Trade Desk campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/the-trade-desk) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=the-trade-desk)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (39 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                           |
        | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
        | **All Conversions**                                | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **CPC by Campaign**                                | Watch only         | CPC by Campaign.                                                                                                         |
        | **CTR by Campaign**                                | Watch only         | CTR by Campaign.                                                                                                         |
        | **Campaign Comparison**                            | Watch only         | Campaign Comparison, broken down by row.                                                                                 |
        | **Clicks vs Conversions**                          | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Conversion Actions Breakdown**                   | Watch only         | Conversion Actions Breakdown.                                                                                            |
        | **Conversion Drop Alert**                          | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Conversion Funnel**                              | Watch only         | Conversion Funnel, stage by stage.                                                                                       |
        | **Conversion Lag**                                 | Watch only         | Conversion Lag, compared across items.                                                                                   |
        | **Conversion Rate Trend**                          | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Conversion Rate by Campaign**                    | Watch only         | Conversion Rate by Campaign.                                                                                             |
        | **Conversion Rate by Device**                      | Watch only         | Conversion Rate by Device.                                                                                               |
        | **Conversions Trend**                              | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Conversions by Campaign**                        | Watch only         | Conversions by Campaign.                                                                                                 |
        | **Conversions by Country**                         | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Conversions by Day of Week**                     | Watch only         | Conversions by Day of Week.                                                                                              |
        | **Conversions by Device**                          | Watch only         | Conversions by Device.                                                                                                   |
        | **Conversions by Hour**                            | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Landing Page Revenue**                           | Watch only         | Landing Page Revenue, broken down by row.                                                                                |
        | **Overspending Campaigns**                         | Watch only         | Overspending Campaigns, broken down by row.                                                                              |
        | **Programmatic ROAS Dropped Below Threshold**      | Alert band 3 / 1.5 | TTD programmatic ROAS shifts mean inventory-quality drop or Koa AI bid-strategy regression , investigate within the day. |
        | **ROAS**                                           | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                                |
        | **ROAS Trend**                                     | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **ROAS by Campaign**                               | Watch only         | ROAS by Campaign.                                                                                                        |
        | **ROAS by Day of Week**                            | Watch only         | ROAS by Day of Week.                                                                                                     |
        | **ROAS by Device**                                 | Watch only         | ROAS by Device.                                                                                                          |
        | **ROAS by Region**                                 | Watch only         | ROAS by Region.                                                                                                          |
        | **Revenue by Campaign**                            | Watch only         | Revenue by Campaign.                                                                                                     |
        | **Search Terms Report**                            | Watch only         | Search Terms Report, broken down by row.                                                                                 |
        | **Spend by Campaign**                              | Watch only         | Spend by Campaign.                                                                                                       |
        | **Top Cities by Conversions**                      | Watch only         | Top Cities by Conversions.                                                                                               |
        | **Top Keywords by Conversions**                    | Watch only         | Top Keywords by Conversions.                                                                                             |
        | **Top Performing Campaigns**                       | Watch only         | Top Performing Campaigns, broken down by row.                                                                            |
        | **Total Revenue**                                  | Watch only         | Description pending editorial review; the signal is live.                                                                |
        | **Underspending Campaigns**                        | Watch only         | Underspending Campaigns, broken down by row.                                                                             |
        | **Universal Pixel / UID 2.0 Resolution Broken**    | Merchant rule      | TTD's whole open-internet pitch depends on cookieless ID resolution. Pixel decay = audience-graph collapse within days.  |
        | **Wasted-Spend Burst (PMP deal under-delivering)** | Alert band 5 / 50  | PMP deals at agreed floor prices can burn fast if creative/audience match is off , catch early to renegotiate.           |
        | **Worst Performing Campaigns**                     | Watch only         | Worst Performing Campaigns, broken down by row.                                                                          |
        | **Zero-Conversion Spend**                          | Watch only         | Description pending editorial review; the signal is live.                                                                |
      </Accordion>

      <Accordion title="Run operations (17 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                            |
        | ------------------------------ | ------------------ | --------------------------------------------------------- |
        | **Budget Utilisation**         | Alert band 70 / 30 | Description pending editorial review; the signal is live. |
        | **CPA Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CPA by Keyword**             | Watch only         | CPA by Keyword.                                           |
        | **CPC Anomaly**                | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Spike Detection**        | Watch only         | Description pending editorial review; the signal is live. |
        | **CPC Trend**                  | Alert band 0 / 25  | Description pending editorial review; the signal is live. |
        | **CTR Trend**                  | Watch only         | Description pending editorial review; the signal is live. |
        | **CTR by Keyword**             | Watch only         | CTR by Keyword.                                           |
        | **Impression Share**           | Alert band 70 / 40 | Description pending editorial review; the signal is live. |
        | **Impressions Trend**          | Watch only         | Description pending editorial review; the signal is live. |
        | **Quality Score Distribution** | Alert band 7 / 4   | Quality Score Distribution, compared across items.        |
        | **Spend Anomaly**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Spend Over Time**            | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
        | **Spend vs Budget**            | Watch only         | Description pending editorial review; the signal is live. |
        | **Top Keywords by Spend**      | Watch only         | Top Keywords by Spend.                                    |
        | **Total Spend**                | Watch only         | Description pending editorial review; the signal is live. |
        | **Wasted Spend**               | Watch only         | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                             | Alert behaviour   | What it tracks                                                                                                                                   |
        | -------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active PMP Catalog Deals on Out-of-Stock SKUs**  | Alert band 5 / 50 | Premium PMP deals are expensive , running them on OOS SKUs burns through the agreed deal floor with no conversion.                               |
        | **Branded Paid Clicks Cannibalising Organic**      | Merchant rule     | TTD search/display branded targeting cannibalising free organic , common in enterprise programmatic agencies running 'defensive' brand programs. |
        | **CTR Decline Alert**                              | Watch only        | Description pending editorial review; the signal is live.                                                                                        |
        | **Landing Pages with Poor Web Vitals**             | Merchant rule     | TTD CTV / premium display click-throughs land on the same merchant pages , LCP regression breaks the whole funnel.                               |
        | **Spend on Campaigns with Active Feed Rejections** | Merchant rule     | £ on a TTD catalog/PMP campaign whose Feedonomics feed has live rejections. Creative falls back, CR drops.                                       |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **3 write** operations across advertisers, authenticationvalidates, campaign queryadvertisers, creativequeryadvertisers, myreportreportexecutionqueryadvertisers on The Trade Desk. 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=the-trade-desk)

    #### Ready to build your first The Trade Desk 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                | Read operations | Write operations |
      | --------------------------------------- | --------------- | ---------------- |
      | advertisers                             | 1               | 0                |
      | authenticationvalidates                 | 1               | 0                |
      | campaign queryadvertisers               | 0               | 1                |
      | creativequeryadvertisers                | 0               | 1                |
      | myreportreportexecutionqueryadvertisers | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Tidio on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/tidio

Monitor Tidio pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Tidio 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=tidio)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="1">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour     | What it tracks                                                                                                                                            |
        | ----------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Cycle Time (days)**           | Alert band 0 / 25   | Mean days from first work (in-progress) to solved.                                                                                                        |
        | **Avg Lead Time (days)**            | Alert band 7 / 14   | Mean days from ticket creation to solved (full lead time).                                                                                                |
        | **Avg Time-to-Fix (days)**          | Alert band 3 / 14   | Mean days from filing to solved for vortex\_iq-tagged tickets resolved in the window.                                                                     |
        | **Backlog by Priority**             | Alert band 20 / 100 | Open backlog split by priority; a high share of Highest+High signals firefighting.                                                                        |
        | **Backlog by Status**               | Merchant rule       | Distribution of tickets across open / pending / solved / closed states.                                                                                   |
        | **Blocked Tickets**                 | Alert band 3 / 8    | Tickets tagged/marked blocked (waiting on an external dependency). Warn >3, critical >8.                                                                  |
        | **Cycle Time by Priority**          | Alert band 2 / 5    | Mean cycle time split by ticket priority; Highest-priority should be fastest.                                                                             |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50  | Share of vortex\_iq-tagged tickets filed in the last 90d now solved. GET /v1/tickets?tags=vortex\_iq\&status=solved\&created\_after=\<now-90d>. Good ≥    |
        | **In Progress**                     | Merchant rule       | Tickets actively being worked (assigned + recent agent activity).                                                                                         |
        | **Oldest Open (days)**              | Alert band 60 / 90  | Age in days of the oldest still-open ticket - backlog-rot signal.                                                                                         |
        | **Open Tickets**                    | Alert band 0 / 20   | All open Tidio Helpdesk tickets (whole backlog, not just findings).                                                                                       |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1    | Count of agents carrying more than 10 open tickets - capacity bottleneck candidates.                                                                      |
        | **Scope Added Mid-Sprint**          | Alert band 15 / 30  | Percentage of sprint scope added after the triage window started.                                                                                         |
        | **Sprint Progress**                 | Alert band 90 / 70  | Share of the current triage sprint's scope completed.                                                                                                     |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20   | Average tickets completed per sprint over the trailing 5 sprints.                                                                                         |
        | **Throughput Trend**                | Merchant rule       | Daily resolved-ticket count over the trailing 30 days.                                                                                                    |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25   | Tickets moved to solved in the last 7 days vs the prior week.                                                                                             |
        | **Tickets by Assignee**             | Alert band 5 / 10   | Open ticket count per agent - distribution check for rebalancing.                                                                                         |
        | **Unassigned Tickets**              | Alert band 5 / 20   | Open tickets with no assignee - work nobody owns. Warn >5, critical >20.                                                                                  |
        | **VortexIQ Findings In Progress**   | Merchant rule       | vortex\_iq-tagged tickets being actively worked (assigned + agent activity, not yet solved).                                                              |
        | **VortexIQ Findings Open**          | Alert band 5 / 20   | Tidio Helpdesk tickets VortexIQ filed from audit findings (tagged vortex\_iq) still in open state. GET /helpdesk/tickets?tags=vortex\_iq\&status=open. Pe |
        | **VortexIQ Findings Resolved**      | Merchant rule       | Count of vortex\_iq-tagged tickets moved to solved in the trailing 90 days.                                                                               |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                          |
        | ----------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 0 / 15 | Open vortex\_iq tickets with no team-side activity (agent reply, status/assignee/tag change, automation) in 14+ days; customer + Lyro replies excluded. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (1)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **1 write** operations across tickets, accounts, contacts, helpdesktickets, operators, ticketcounts on Tidio. 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=tidio)

    #### Ready to build your first Tidio 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | tickets         | 1               | 1                |
      | accounts        | 1               | 0                |
      | contacts        | 1               | 0                |
      | helpdesktickets | 1               | 0                |
      | operators       | 1               | 0                |
      | ticketcounts    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# TikTok Ads on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/tiktok-ads

Monitor TikTok Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

Monitor TikTok Ads campaign performance and spend efficiency, and catch tracking or pacing problems before budget is wasted.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/tiktok-ads) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=tiktok-ads)

<CardGroup>
  <Card title="72">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (72)">
    ### Monitor performance

    72 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (43 signals)">
        | Signal                                              | Alert behaviour    | What it tracks                                                                                                                                         |
        | --------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **All Conversions**                                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **CPA by Creative**                                 | Watch only         | CPA by Creative.                                                                                                                                       |
        | **CPC by Campaign**                                 | Watch only         | CPC by Campaign.                                                                                                                                       |
        | **CTR Distribution by Creative (Fatigue Proxy)**    | Watch only         | TikTok creatives burn out 2-3× faster than Meta , falling CTR per-creative is the earliest available fatigue signal without needing frequency data.    |
        | **CTR by Campaign**                                 | Watch only         | CTR by Campaign.                                                                                                                                       |
        | **CTR by Creative**                                 | Watch only         | CTR by Creative.                                                                                                                                       |
        | **Campaign Comparison**                             | Watch only         | Campaign Comparison, broken down by row.                                                                                                               |
        | **Clicks vs Conversions**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Actions Breakdown**                    | Watch only         | Conversion Actions Breakdown.                                                                                                                          |
        | **Conversion Drop Alert**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Funnel**                               | Watch only         | Conversion Funnel, stage by stage.                                                                                                                     |
        | **Conversion Lag**                                  | Watch only         | Conversion Lag, compared across items.                                                                                                                 |
        | **Conversion Rate Trend**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Rate by Campaign**                     | Watch only         | Conversion Rate by Campaign.                                                                                                                           |
        | **Conversion Rate by Device**                       | Watch only         | Conversion Rate by Device.                                                                                                                             |
        | **Conversions Trend**                               | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversions by Campaign**                         | Watch only         | Conversions by Campaign.                                                                                                                               |
        | **Conversions by Country**                          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversions by Day of Week**                      | Watch only         | Conversions by Day of Week.                                                                                                                            |
        | **Conversions by Device**                           | Watch only         | Conversions by Device.                                                                                                                                 |
        | **Conversions by Hour**                             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Landing Page Revenue**                            | Watch only         | Landing Page Revenue, broken down by row.                                                                                                              |
        | **Overspending Campaigns**                          | Watch only         | Overspending Campaigns, broken down by row.                                                                                                            |
        | **Pixel/Events-API Tracking Broken**                | Merchant rule      | TikTok's iOS attribution is even more brittle than Meta , catch within the same iOS-attribution window.                                                |
        | **ROAS**                                            | Alert band 3 / 1.5 | Description pending editorial review; the signal is live.                                                                                              |
        | **ROAS Dropped Below Threshold**                    | Alert band 3 / 1.5 | First number to ping when the ad team's morning is going to be bad.                                                                                    |
        | **ROAS Trend**                                      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **ROAS by Campaign**                                | Watch only         | ROAS by Campaign.                                                                                                                                      |
        | **ROAS by Day of Week**                             | Watch only         | ROAS by Day of Week.                                                                                                                                   |
        | **ROAS by Device**                                  | Watch only         | ROAS by Device.                                                                                                                                        |
        | **ROAS by Region**                                  | Watch only         | ROAS by Region.                                                                                                                                        |
        | **Revenue by Campaign**                             | Watch only         | Revenue by Campaign.                                                                                                                                   |
        | **Spend by Campaign**                               | Watch only         | Spend by Campaign.                                                                                                                                     |
        | **Spend by Placement (TopView / In-Feed / Pangle)** | Watch only         | TikTok targets by placement and audience, not keyword , the awareness (TopView) vs conversion (In-Feed) mix question every TikTok merchant asks on Mon |
        | **Top Cities by Conversions**                       | Watch only         | Top Cities by Conversions.                                                                                                                             |
        | **Top Creatives by Conversions**                    | Watch only         | Which ads (Spark Ads / In-Feed / TopView creatives) are actually driving conversions this month.                                                       |
        | **Top Creatives by Spend**                          | Watch only         | Spend concentration across the active creative set.                                                                                                    |
        | **Top Performing Campaigns**                        | Watch only         | Top Performing Campaigns, broken down by row.                                                                                                          |
        | **Total Revenue**                                   | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Underspending Campaigns**                         | Watch only         | Underspending Campaigns, broken down by row.                                                                                                           |
        | **Wasted Spend (Zero-Conversion Creatives)**        | Alert band 5 / 50  | Roll-up of spend on creatives with zero conversions over 30D , the TikTok-native equivalent of the archetype's keyword-level Wasted Spend hero card.   |
        | **Worst Performing Campaigns**                      | Watch only         | Worst Performing Campaigns, broken down by row.                                                                                                        |
        | **Zero-Conversion Spend**                           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Run operations (13 signals)">
        | Signal                               | Alert behaviour    | What it tracks                                                                 |
        | ------------------------------------ | ------------------ | ------------------------------------------------------------------------------ |
        | **Budget Utilisation**               | Alert band 70 / 30 | Description pending editorial review; the signal is live.                      |
        | **CPA Trend**                        | Watch only         | Description pending editorial review; the signal is live.                      |
        | **CPC Anomaly**                      | Watch only         | Description pending editorial review; the signal is live.                      |
        | **CPC Spike Detection**              | Watch only         | Description pending editorial review; the signal is live.                      |
        | **CPC Trend**                        | Alert band 0 / 25  | Description pending editorial review; the signal is live.                      |
        | **CTR Trend**                        | Watch only         | Description pending editorial review; the signal is live.                      |
        | **Impression Share**                 | Alert band 70 / 40 | Description pending editorial review; the signal is live.                      |
        | **Impressions Trend**                | Watch only         | Description pending editorial review; the signal is live.                      |
        | **Spend Anomaly**                    | Watch only         | Description pending editorial review; the signal is live.                      |
        | **Spend Over Time**                  | Alert band 0 / -10 | Description pending editorial review; the signal is live.                      |
        | **Spend vs Budget**                  | Watch only         | Description pending editorial review; the signal is live.                      |
        | **Total Spend**                      | Watch only         | Description pending editorial review; the signal is live.                      |
        | **Wasted-Spend Burst (3-day spike)** | Alert band 5 / 50  | TikTok's auction can chew through a runaway budget faster than most platforms. |
      </Accordion>

      <Accordion title="Customer experience (11 signals)">
        | Signal                       | Alert behaviour | What it tracks                                            |
        | ---------------------------- | --------------- | --------------------------------------------------------- |
        | **CPA by Region**            | Watch only      | CPA by Region.                                            |
        | **CPC by Device**            | Watch only      | CPC by Device.                                            |
        | **CPC by Hour**              | Watch only      | CPC by Hour over time.                                    |
        | **CTR by Device**            | Watch only      | CTR by Device.                                            |
        | **CTR by Region**            | Watch only      | CTR by Region.                                            |
        | **Landing Page CPC**         | Watch only      | Landing Page CPC, broken down by row.                     |
        | **Landing Page Conv. Rate**  | Watch only      | Landing Page Conv. Rate, broken down by row.              |
        | **Landing Page Performance** | Watch only      | Landing Page Performance, broken down by row.             |
        | **Spend by Country**         | Watch only      | Description pending editorial review; the signal is live. |
        | **Spend by Device**          | Watch only      | Spend by Device.                                          |
        | **Spend by Hour**            | Watch only      | Spend by Hour.                                            |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                               | Alert behaviour   | What it tracks                                                                                          |
        | ---------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------- |
        | **Active TikTok Shop Ads on Out-of-Stock SKUs**      | Alert band 5 / 50 | Spend on TikTok Shop catalog ads pointing at SKUs that can't convert. Pause the ad, recover the budget. |
        | **Branded Paid Clicks Cannibalising Organic Search** | Merchant rule     | Branded keywords running on TikTok that already perform organically on Google. Pure margin reclaim.     |
        | **CTR Decline Alert**                                | Watch only        | Description pending editorial review; the signal is live.                                               |
        | **Mobile Landing Pages with Poor Web Vitals**        | Merchant rule     | TikTok traffic is \~95% mobile , slow mobile landings convert worse than any other channel.             |
        | **Spend on Campaigns with Active Feed Rejections**   | Merchant rule     | £ on a Shop campaign whose Feedonomics feed has live rejections , bid signal degrades until cleared.    |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Conversion tracking broken (clicks > 0 but conversions = 0)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Over 100 clicks with zero recorded conversions almost never means genuinely zero sales; it means the ad platform cannot see the sales that are happening. Every bid strategy that optimises toward conversions is currently optimising against no signal at all, which makes the campaign's spend effectivel

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-002`
      </Accordion>

      <Accordion title="Wasted spend , campaigns with ROAS < 1 over 30d">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A campaign returning less than $1 of revenue for every $1 spent is losing money on every dollar put into it, before accounting for product cost or fulfilment. Over 30 days that is not a bad day, it is a sustained drain on ad budget that could be funding a campaign that actually returns a profit.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-001`
      </Accordion>

      <Accordion title="Missing UTM tags in ad destination URLs">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Ads landing without UTM tags cannot be attributed, so the spend disappears from every report and the channel looks worse than it is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `AD-TRACK-001`
      </Accordion>

      <Accordion title="Budget > 80% used before mid-month">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        More than 80% of this month's budget is gone before the month is half over. At this pace the campaign runs out of budget and stops serving for the back half of the month, losing whatever sales it would have driven during that gap.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-SPEND-002`
      </Accordion>

      <Accordion title="Disapproved ads in active campaigns">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A disapproved ad stops serving immediately, so any budget allocated to it is not reaching anyone. If it sits in an active campaign unnoticed, the campaign quietly loses reach and volume with no error visible outside the ad platform itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `AD-CREATIVE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **1 write** operations across openapiadgets, openapiadvertiserinfos, openapicampaigngets, openapicreativeportfoliogets, openapioauth2accesstokens, openapireportintegratedgets on TikTok Ads. 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=tiktok-ads)

    #### Ready to build your first TikTok Ads 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                     | Read operations | Write operations |
      | ---------------------------- | --------------- | ---------------- |
      | openapiadgets                | 1               | 0                |
      | openapiadvertiserinfos       | 1               | 0                |
      | openapicampaigngets          | 1               | 0                |
      | openapicreativeportfoliogets | 1               | 0                |
      | openapioauth2accesstokens    | 0               | 1                |
      | openapireportintegratedgets  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# TikTok on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/tiktok-organic

Monitor TikTok publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor TikTok publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=tiktok-organic)

<CardGroup>
  <Card title="15">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (15)">
    ### Monitor performance

    15 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (12 signals)">
        | Signal                        | Alert behaviour  | What it tracks                                                       |
        | ----------------------------- | ---------------- | -------------------------------------------------------------------- |
        | **Avg Session Duration**      | Merchant rule    | Average time on site for TikTok visitors.                            |
        | **Goal Completions**          | Merchant rule    | Goal completions attributed to TikTok traffic.                       |
        | **New Users**                 | Merchant rule    | First-time visitors attributed to TikTok.                            |
        | **Pageviews per Session**     | Merchant rule    | Average pages viewed per TikTok-referred session.                    |
        | **Real-Time Users**           | Merchant rule    | Visitors on-site right now from TikTok - spikes flag a viral moment. |
        | **Returning Users**           | Merchant rule    | Repeat visitors arriving from TikTok.                                |
        | **Session Conversion Rate**   | Alert band 2 / 1 | Share of TikTok sessions that complete a purchase goal.              |
        | **Sessions**                  | Merchant rule    | TikTok-attributed storefront sessions over the window.               |
        | **TikTok-Attributed Revenue** | Watch only       | Closes the loop: did the viral video actually sell anything?         |
        | **Top Pages**                 | Merchant rule    | Landing pages receiving the most TikTok traffic.                     |
        | **Top Traffic Sources**       | Merchant rule    | Source/medium breakdown of inbound TikTok-linked traffic.            |
        | **Users**                     | Merchant rule    | Distinct users arriving from organic TikTok.                         |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                           |
        | ------------------------- | ------------------ | -------------------------------------------------------- |
        | **Bounce Rate**           | Alert band 40 / 60 | Share of TikTok sessions that leave after one page.      |
        | **Cart Abandonment Rate** | Alert band 60 / 75 | Share of TikTok-sourced carts abandoned before checkout. |
      </Accordion>

      <Accordion title="Run operations (1 signals)">
        | Signal        | Alert behaviour | What it tracks                                           |
        | ------------- | --------------- | -------------------------------------------------------- |
        | **Followers** | Watch only      | Current TikTok follower count for the connected account. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Engagement rate below 1%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Engagement below 1 percent means content is reaching feeds and being scrolled past; format and hook need work before spend goes behind it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-ENGAGEMENT-001`
      </Accordion>

      <Accordion title="Reach dropped > 20% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Reach dropping over 20 percent usually means the algorithm has deprioritised the account or a format change landed badly; catching it early keeps the slide shallow.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-REACH-001`
      </Accordion>

      <Accordion title="Posting cadence collapsed (no post in 14 days)">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Posting cadence collapsing to zero lets the audience's attention lapse; reach compounds only while the account stays present.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `SOCIAL-CADENCE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across analyticspages, analyticssessions, analyticssources, analyticsusers, userinfos on TikTok. 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=tiktok-organic)

    #### Ready to build your first TikTok 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | analyticspages    | 1               | 0                |
      | analyticssessions | 1               | 0                |
      | analyticssources  | 1               | 0                |
      | analyticsusers    | 1               | 0                |
      | userinfos         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Trello (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/trello-api

Monitor Trello (API) performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Trello (API) performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=trello-api)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (20 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                 |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Mean days from first In-Progress move to Done - derived from card action history.                                              |
        | **Avg Lead Time (days)**            | Merchant rule      | Mean days from card creation to Done - total queue + work time.                                                                |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Mean days from finding creation to the card reaching Done / archive.                                                           |
        | **Backlog by Priority**             | Merchant rule      | Open cards grouped by priority label - skew toward Highest+High signals firefighting.                                          |
        | **Backlog by Status**               | Watch only         | Open cards grouped by list - Trello's only status primitive.                                                                   |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Cards carrying a Blocked / Impeded label - the board's stuck list.                                                             |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle time split by priority label - surfaces where the heavy items stall.                                                     |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings actually got fixed via the Trello board. \<50% means we're filing faster than the team drains.    |
        | **Oldest Open (days)**              | Merchant rule      | Age of the oldest open card by dateLastActivity - backlog-rot signal.                                                          |
        | **Open Tickets**                    | Merchant rule      | Open cards (closed = false, not on a Done list) across all connected boards - top-of-board backlog volume.                     |
        | **Overloaded Assignees (>10 open)** | Alert band 0 / 1   | Members with >10 open cards - capacity bottleneck candidates.                                                                  |
        | **Scope Added Mid-Sprint**          | Merchant rule      | Cards added to a cycle list after the cycle started - Trello scope-creep proxy.                                                |
        | **Sprint Velocity (avg)**           | Merchant rule      | Cards completed per weekly cycle, averaged over the last 5 cycles.                                                             |
        | **Throughput Trend**                | Watch only         | Resolution pace over 30 days - direction of team capacity.                                                                     |
        | **Tickets Resolved (7d)**           | Merchant rule      | Cards moved to a Done list or archived in the last 7 days - short-window throughput.                                           |
        | **Tickets by Assignee**             | Merchant rule      | Open cards grouped by idMembers - concentration / bottleneck view.                                                             |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Open cards with an empty idMembers array - work nobody owns.                                                                   |
        | **VortexIQ Findings In Progress**   | Watch only         | Finding cards on a Doing / In-Progress list - actively being worked.                                                           |
        | **VortexIQ Findings Open**          | Merchant rule      | Cards we filed from audit findings that haven't been moved to Done or archived - the live backlog of things VortexIQ surfaced. |
        | **VortexIQ Findings Resolved**      | Watch only         | Finding cards moved to Done or archived in the last 90 days.                                                                   |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal              | Alert behaviour    | What it tracks                                                                                                                          |
        | ------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
        | **In Progress**     | Watch only         | Cards on a configured In-Progress / Doing list - what the team is actively working.                                                     |
        | **Sprint Progress** | Alert band 80 / 50 | Share of the current weekly-cycle cards already on a Done list - Trello has no native sprint, so this reads the configured cycle lists. |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                       |
        | ----------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Finding cards with no dateLastActivity change in 14 days - these are the ones losing money silently. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **3 write** operations across cards, boardactions, boardcards, boardlists, boardmembers, cardactioncomments on Trello (API). 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=trello-api)

    #### Ready to build your first Trello (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | cards                | 0               | 2                |
      | boardactions         | 1               | 0                |
      | boardcards           | 1               | 0                |
      | boardlists           | 1               | 0                |
      | boardmembers         | 1               | 0                |
      | cardactioncomments   | 0               | 1                |
      | cardcustomfielditems | 1               | 0                |
      | membermes            | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Twilio on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/twilio

Monitor Twilio performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Twilio performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=twilio)

<CardGroup>
  <Card title="None yet">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup />

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (0)">
    ### Monitor performance

    0 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Twilio yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **3 write** operations across account messagejsons, accounts, account calls, account calljsons, account messages, account usagerecordjsons on Twilio. 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=twilio)

    #### Ready to build your first Twilio 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                 | Read operations | Write operations |
      | ------------------------ | --------------- | ---------------- |
      | account messagejsons     | 1               | 1                |
      | accounts                 | 1               | 0                |
      | account calls            | 1               | 0                |
      | account calljsons        | 0               | 1                |
      | account messages         | 1               | 0                |
      | account usagerecordjsons | 1               | 0                |
      | services                 | 1               | 0                |
      | servicephonenumbers      | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# X (Twitter) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/twitter

Monitor X (Twitter) publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor X (Twitter) publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=twitter)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="178">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (16 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                                                                   |
        | ------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Account Age (days)**                | Watch only         | Days since users/me created\_at.                                                                                                 |
        | **Bookmarks (30d)**                   | Watch only         | Sum of public\_metrics.bookmark\_count; save-for-later intent.                                                                   |
        | **Days Since Last Post**              | Watch only         | Days since the most recent post. Silent cadence collapse is the top organic-social decay signal.                                 |
        | **Engagement Drop Alert**             | Alert band 3 / 1   | Current 30d engagement rate; sentiment fires when it crosses the engagement\_rate band.                                          |
        | **Engagement Rate**                   | Alert band 3 / 1   | Avg per-post (likes + replies + reposts + quotes) / followers x 100 across posts in the last 30d.                                |
        | **Engagement per 1k Followers (30d)** | Watch only         | Total 30d engagement / followers x 1000; size-normalised engagement.                                                             |
        | **Follower : Following Ratio**        | Watch only         | followers\_count / following\_count; a rough authority signal.                                                                   |
        | **Following**                         | Watch only         | users/me public\_metrics.following\_count.                                                                                       |
        | **Likes (30d)**                       | Watch only         | Sum of public\_metrics.like\_count.                                                                                              |
        | **Listed Count**                      | Watch only         | users/me public\_metrics.listed\_count; how many curated lists include the account.                                              |
        | **Replies (30d)**                     | Watch only         | Sum of public\_metrics.reply\_count; conversation signal.                                                                        |
        | **Reposts + Quotes (30d)**            | Watch only         | Sum of retweet\_count + quote\_count; amplification signal.                                                                      |
        | **Social Health Score**               | Alert band 90 / 70 | Composite 0-100: engagement rate (50%) x posting cadence (30%) x days-since-last-post (20%), from users/me + the last 200 posts. |
        | **Top Posts by Engagement**           | Watch only         | Top 10 posts by likes + replies + reposts + quotes.                                                                              |
        | **Total Engagement (30d)**            | Watch only         | Sum of likes + replies + reposts + quotes over posts in the last 30d.                                                            |
        | **Total Posts (lifetime)**            | Watch only         | users/me public\_metrics.tweet\_count.                                                                                           |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                             | Alert behaviour | What it tracks                                                               |
        | ---------------------------------- | --------------- | ---------------------------------------------------------------------------- |
        | **Avg Impressions per Post (30d)** | Watch only      | Mean impression\_count over posts in the last 30d (user-context token only). |
        | **Avg Likes per Post (30d)**       | Watch only      | Mean public\_metrics.like\_count over posts in the last 30d.                 |
        | **Avg Replies per Post (30d)**     | Watch only      | Mean public\_metrics.reply\_count over posts in the last 30d.                |
        | **Posts Published Trend**          | Watch only      | Posts per month across the fetched window (up to 200 posts).                 |
      </Accordion>

      <Accordion title="Run operations (2 signals)">
        | Signal          | Alert behaviour    | What it tracks                             |
        | --------------- | ------------------ | ------------------------------------------ |
        | **Followers**   | Alert band 0 / -2  | users/me public\_metrics.followers\_count. |
        | **Posts (30d)** | Alert band 0 / -40 | Count of posts created in the last 30d.    |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                                                                                             |
        | --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Impressions (30d)** | Watch only      | Sum of public\_metrics.impression\_count over posts in the last 30d. Owner user-context token only; app-only bearer tokens render no data. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Engagement rate below 1%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Engagement below 1 percent means content is reaching feeds and being scrolled past; format and hook need work before spend goes behind it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-ENGAGEMENT-001`
      </Accordion>

      <Accordion title="Reach dropped > 20% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Reach dropping over 20 percent usually means the algorithm has deprioritised the account or a format change landed badly; catching it early keeps the slide shallow.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-REACH-001`
      </Accordion>

      <Accordion title="Posting cadence collapsed (no post in 14 days)">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Posting cadence collapsing to zero lets the audience's attention lapse; reach compounds only while the account stays present.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `SOCIAL-CADENCE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **100 read** and **78 write** operations across activitysubscriptions, broadcastscheduleds, lists, tweets, webhooks, account activitywebhooksubscriptionalls on X (Twitter). 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=twitter)

    #### Ready to build your first X (Twitter) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                | Read operations | Write operations |
      | --------------------------------------- | --------------- | ---------------- |
      | activitysubscriptions                   | 1               | 4                |
      | broadcastscheduleds                     | 2               | 3                |
      | lists                                   | 1               | 3                |
      | tweets                                  | 2               | 2                |
      | webhooks                                | 1               | 3                |
      | account activitywebhooksubscriptionalls | 1               | 2                |
      | broadcastchats                          | 1               | 2                |
      | compliancejobs                          | 2               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Uptime Robot on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/uptime-robot

Monitor Uptime Robot health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Uptime Robot health, cost and reliability signals, and catch incidents and runaway spend early.

[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=uptime-robot)

<CardGroup>
  <Card title="20">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                             |
        | ---------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------ |
        | **Alerts Acknowledged**      | Merchant rule                | Alerts a responder has acknowledged in the window - the leading edge of MTTA.              |
        | **Alerts Firing**            | Merchant rule                | Alert events raised by Uptime Robot monitors in the window.                                |
        | **Incidents Open**           | Alert band 0 / 3             | Outage windows currently open (down or degraded) across all monitors.                      |
        | **Incidents Resolved (24h)** | Merchant rule                | Outage windows closed in the last 24 hours - recovery throughput.                          |
        | **Mean Time To Acknowledge** | Alert band 300000 / 900000   | Median gap between a monitor going down and a responder acknowledging it.                  |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Median gap between a monitor going down and recovering to up.                              |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Uptime ratio measured against the SLA target across the window.                            |
        | **Services Degraded**        | Alert band 0 / 2             | Monitors responding slowly or intermittently (seems\_down) but not fully down.             |
        | **Services Down**            | Alert band 0 / 1             | Monitors fully unreachable (down). The single most-watched number for an SMB operator.     |
        | **Services Healthy**         | Alert band 1 / 0             | Monitors currently reporting an up / healthy state.                                        |
        | **Top Alerting Services**    | Merchant rule                | Monitors that raised the most alerts in the window - the noisiest / least-stable services. |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour        | What it tracks                                                                         |
        | ------------------------ | ---------------------- | -------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.94 / 0.85 | Satisfied vs tolerating vs frustrated response-time buckets rolled into one 0-1 score. |
        | **Avg Response Time**    | Alert band 200 / 1500  | Average monitor response time across all checks.                                       |
        | **Error Rate**           | Alert band 0.5 / 2     | Share of checks returning an error / down state.                                       |
        | **Throughput (req/min)** | Alert band 0 / -10     | Checks executed per minute across all monitors.                                        |
        | **p95 Latency**          | Alert band 800 / 1500  | 95th-percentile monitor response time - the slow-tail experience.                      |
        | **p99 Latency**          | Alert band 1500 / 3000 | 99th-percentile monitor response time - worst-case slow checks.                        |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                              | Alert behaviour | What it tracks                                                                                                                                         |
        | ----------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Revenue at Risk (live)**          | Merchant rule   | When a storefront monitor is down, price the outage in \$/min using the commerce sibling's revenue baseline. The COO's number.                         |
        | **Storefront Down During Campaign** | Merchant rule   | Paid traffic landing on a down storefront. Overlay outage windows with active ad-campaign spend to surface money burned on traffic that cannot convert |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                                                       |
        | ------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Top Error Types** | Merchant rule   | Most common down reasons (timeout, connection refused, status code, keyword-not-found, DNS) across failing monitors. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **Severity** critical · **Outcome** Customer experience · **Fix status** Report only

        More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping work, and a rate this high is an active problem, not background noise.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-ERROR-001`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when performance complaints are about to start, even before anyone files one.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-APDEX-001`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is a revenue issue wearing a performance-metric label.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-PERF-001`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve requests it would otherwise handle, two very different problems that look identical in this one number.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MONITORING-THROUGHPUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **6 write** operations across editmonitors, getaccountdetails, getalertcontacts, getmonitors, getmwindows, getpsps on Uptime Robot. 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=uptime-robot)

    #### Ready to build your first Uptime Robot 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.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | editmonitors      | 0               | 1                |
      | getaccountdetails | 0               | 1                |
      | getalertcontacts  | 0               | 1                |
      | getmonitors       | 0               | 1                |
      | getmwindows       | 0               | 1                |
      | getpsps           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# USPS on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/usps

Monitor USPS delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

Monitor USPS delivery performance, SLA risk and cost per order, and catch carrier problems before customers feel them.

[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=usps)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="2">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (19 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Error Rate**                     | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Shipping Cost**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Claim Value (open)**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Cost Per Shipment Trend**            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Cost by Zone**                       | Watch only         | Cost by Zone.                                                                                                                                          |
        | **Days to Token Expiry**               | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Exception Rate**                     | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                                                              |
        | **High-Cost Shipment Outliers**        | Watch only         | High-Cost Shipment Outliers, broken down by row.                                                                                                       |
        | **Label Generation Success**           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **OTD by Origin-Destination ZIP Zone** | Alert band 95 / 90 | USPS zone-based delivery OTD. Identifies regional weakness (rural Alaska, Hawaii, US territories) for service-level adjustment.                        |
        | **OTD by Route**                       | Watch only         | OTD by Route.                                                                                                                                          |
        | **Open Claims**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Returned to Sender**                 | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Route Volume Concentration**         | Merchant rule      | Route Volume Concentration, compared across items.                                                                                                     |
        | **SCAN-Form Acceptance Gap**           | Merchant rule      | % of shipments with a printed label but no SCAN-form acceptance event - untracked-handover blackhole, each one a customer-trust hit when 'no tracking' |
        | **Shipments**                          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments Over Time**                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments by Destination**           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Shipments by Service**               | Watch only         | Shipments by Service.                                                                                                                                  |
      </Accordion>

      <Accordion title="Customer experience (5 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------- |
        | **Avg Transit (days)**          | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **First-Attempt Delivery Rate** | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **Late Shipments**              | Watch only         | Description pending editorial review; the signal is live.                                                     |
        | **On-Time Delivery Rate**       | Alert band 95 / 90 | Description pending editorial review; the signal is live.                                                     |
        | **Priority Mail OTD**           | Alert band 95 / 90 | USPS Priority Mail OTD - the contractual baseline (\~92%). Below this and customers paid premium for nothing. |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                            |
        | --------------------- | --------------- | --------------------------------------------------------- |
        | **Failed Deliveries** | Merchant rule   | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token expired or about to expire (<14 days)">
        **Severity** critical · **Outcome** Run operations · **Fix status** Report only

        Once this token expires, VortexIQ stops receiving tracking and delivery data from this carrier entirely, and every finding in this report that depends on courier data goes stale from that moment, silently, until someone notices shipments look wrong.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-AUTH-001`
      </Accordion>

      <Accordion title="Exception rate above 3%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 3% of shipments with this carrier are hitting an exception, a failed delivery attempt, damage, an address problem, a lost parcel, each of which usually turns into a support ticket and, often, a refund or reshipment cost the store absorbs.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-EXCEPTION-001`
      </Accordion>

      <Accordion title="On-time delivery rate below 90%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 shipments with this carrier is arriving late. Late delivery is one of the most common drivers of customer support contacts, refund requests and negative reviews, and it lands on the store's reputation even though the carrier caused it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-001`
      </Accordion>

      <Accordion title="Open claims unresolved > 7 days">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Courier claims open beyond 7 days are money owed sitting unclaimed; carriers rely on claimants giving up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-CLAIM-001`
      </Accordion>

      <Accordion title="Avg cost per shipment up > 10% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Average cost per shipment with this carrier rose more than 10% compared to the prior period. Shipping is rarely re-priced into the product on the same timeline it changes, so a jump this size quietly erodes margin on every order this carrier touches until pricing or carrier choice is revisited.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-COST-001`
      </Accordion>

      <Accordion title="Failed-delivery rate above 2%">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Failed deliveries above 2 percent create support contacts, redelivery costs and refunds; address validation and carrier choice are the usual levers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-FAIL-001`
      </Accordion>

      <Accordion title="OTD trending down >5pp WoW">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        On-time delivery dropped more than 5 percentage points in a single week. A move this fast usually has a specific, recent cause (a service disruption, a capacity issue at the carrier, a seasonal volume spike), which is worth catching now, before it settles into a new, worse normal that customers star

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-OTD-002`
      </Accordion>

      <Accordion title="Single-carrier dependency on a route (>80% volume)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Over 80% of shipping volume on one route runs through a single carrier. If that carrier has an outage, a rate hike, or a capacity problem on that route, there is no fallback already in place, and the store finds out at the worst possible time, mid-disruption, rather than in advance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `COURIER-DEPENDENCY-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **0 write** operations across tbds on USPS. 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=usps)

    #### Ready to build your first USPS 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.

    <Accordion title="Browse the operations you can build with">
      | Resource | Read operations | Write operations |
      | -------- | --------------- | ---------------- |
      | tbds     | 2               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Vinted on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/vinted

Monitor Vinted listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Vinted listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=vinted)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by Country (EU)**                         | Watch only         | AOV by Country (EU).                                                                                                                                   |
        | **Buyer Messages Unread**                       | Watch only         | Buyer Messages Unread as exposed by the Vinted integration. The metric is computed from the latest available data and refreshed on the standard data r |
        | **Buyer-Protection / Rating Threshold Crossed** | Alert band 95 / 85 | Alerts for Buyer-Protection / Rating Threshold Crossed.                                                                                                |
        | **Days Since Last Payout**                      | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Late Shipments**                              | Merchant rule      | Alerts for Late Shipments.                                                                                                                             |
        | **Marketplace Fees Paid**                       | Watch only         | Marketplace Fees Paid as exposed by the Vinted integration. The metric is computed from the latest available data and refreshed on the standard data r |
        | **Orders / Day**                                | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by Country (EU)**                      | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**                             | Watch only         | Pending Payouts as exposed by the Vinted integration. The metric is computed from the latest available data and refreshed on the standard data refresh |
        | **Pending Shipment**                            | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Ships-Within-5-Days Rate**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Vinted Effective Cost % (vs gross)**          | Alert band 12 / 18 | Vinted = 0% seller fee. Cost mostly Wardrobe Spotlight ads + payment-processing diff.                                                                  |
        | **Vinted Shop Health Score**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                             | Alert behaviour    | What it tracks                                                                                                                                           |
        | -------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Average Sale Price**                             | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                                |
        | **Brand + Size + Condition Completeness**          | Alert band 90 / 70 | Vinted search is brand+size+condition driven. Missing these = invisible to filter-driven buyers.                                                         |
        | **Favourites → Views Conversion**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                                |
        | **Net Revenue (Buyer Protection paid by buyer)**   | Alert band 0 / -5  | Vinted's distinctive model: 0% selling fees for sellers. Buyer pays Buyer Protection (\~3-8% + \~€0.70). Net revenue = sale price minus optional Wardrob |
        | **Orders**                                         | Watch only         | Description pending editorial review; the signal is live.                                                                                                |
        | **Revenue Mix by EU Country**                      | Watch only         | EU multi-country split. Vinted operates per-country marketplaces; mix shapes shipping economics + tax compliance.                                        |
        | **Revenue Over Time**                              | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                                |
        | **Stale Listings (>14d, freshness boost decayed)** | Merchant rule      | Vinted's 'wardrobe' discovery boost decays around the 2-week mark. Aging listings need bump or refresh.                                                  |
        | **Top Listings by Revenue**                        | Watch only         | Top Listings by Revenue.                                                                                                                                 |
        | **Total Revenue**                                  | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                                |
      </Accordion>

      <Accordion title="Protect revenue (6 signals)">
        | Signal                                              | Alert behaviour   | What it tracks                                                                                                                   |
        | --------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Vinted Listings for Sold-Elsewhere Items** | Alert band 0 / 5  | Description pending editorial review; the signal is live.                                                                        |
        | **Buyer Protection Complaint Rate**                 | Alert band 5 / 15 | EU consumer-law-driven complaint flow. Vinted refunds at discretion when complaints stick. Spike = description-vs-reality drift. |
        | **Listings Drifting from BC**                       | Alert band 5 / 50 | Listings Drifting from BC, broken down by row.                                                                                   |
        | **Listings Failing Feedonomics Validation**         | Alert band 2 / 5  | Description pending editorial review; the signal is live.                                                                        |
        | **Revenue at Risk**                                 | Merchant rule     | Description pending editorial review; the signal is live.                                                                        |
        | **Same Item Priced Differently vs Mercari / Depop** | Merchant rule     | Same Item Priced Differently vs Mercari / Depop, broken down by row.                                                             |
      </Accordion>

      <Accordion title="Catalogue quality (6 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                    |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------- |
        | **Active Listings**                       | Merchant rule      | Description pending editorial review; the signal is live.                                         |
        | **Feedback Rating**                       | Alert band 95 / 85 | Description pending editorial review; the signal is live.                                         |
        | **Listings Priced Above Country Average** | Merchant rule      | Vinted shows category-country average prices. Listings priced significantly above get few clicks. |
        | **Listings with \<2 Photos**              | Alert band 10 / 25 | Description pending editorial review; the signal is live.                                         |
        | **Total Listings**                        | Watch only         | Description pending editorial review; the signal is live.                                         |
        | **Vinted Removed Listings (24h)**         | Alert band 5 / 50  | Alerts for Vinted Removed Listings (24h).                                                         |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across disputes, oauthtokens, users, useritems, userorders on Vinted. 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=vinted)

    #### Ready to build your first Vinted 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.

    <Accordion title="Browse the operations you can build with">
      | Resource    | Read operations | Write operations |
      | ----------- | --------------- | ---------------- |
      | disputes    | 1               | 0                |
      | oauthtokens | 0               | 1                |
      | users       | 1               | 0                |
      | useritems   | 1               | 0                |
      | userorders  | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Viva Payments on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/viva-payments

Monitor Viva Payments payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Viva Payments payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=viva-payments)

<CardGroup>
  <Card title="25">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (10 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **3DS Abandonment Rate**        | Alert band 15 / 30 | 3DS Abandonment Rate from Viva Payments, grouped under Payments & Checkout Health. Computes when a live Viva Payments integration is connected; reconc |
        | **Chargeback Rate**             | Alert band 0.5 / 1 | Chargeback Rate from Viva Payments, grouped under Disputes & Chargebacks. Computes when a live Viva Payments integration is connected; reconciles ecom |
        | **Decline Rate**                | Alert band 3 / 8   | Description pending editorial review; the signal is live.                                                                                              |
        | **Dispute Rate**                | Alert band 1 / 2   | Dispute Rate from Viva Payments, grouped under Disputes & Chargebacks. Computes when a live Viva Payments integration is connected; reconciles ecommer |
        | **Net Revenue (after refunds)** | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Refund Rate**                 | Alert band 2 / 5   | Description pending editorial review; the signal is live.                                                                                              |
        | **Refund Value**                | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Refund Volume**               | Watch only         | Refund Volume from Viva Payments, grouped under Disputes & Chargebacks. Computes when a live Viva Payments integration is connected; reconciles ecomme |
        | **Refunds Over Time**           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Top Decline Reasons**         | Watch only         | Top Decline Reasons from Viva Payments, grouped under Payments & Checkout Health. Computes when a live Viva Payments integration is connected; reconci |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                  | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Average Transaction** | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue Over Time**   | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Revenue by Country**  | Watch only         | Revenue by Country.                                                                                                                                    |
        | **Top Payment Methods** | Watch only         | Top Payment Methods from Viva Payments, grouped under Revenue & Sales. Computes when a live Viva Payments integration is connected; reconciles ecommer |
        | **Total Revenue**       | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Transactions**  | Watch only         | Total Transactions from Viva Payments, grouped under Revenue & Sales. Computes when a live Viva Payments integration is connected; reconciles ecommerc |
        | **Total Volume**        | Watch only         | Total Volume from Viva Payments, grouped under Revenue & Sales. Computes when a live Viva Payments integration is connected; reconciles ecommerce agai |
        | **Volume Trend**        | Alert band 0 / -15 | Volume Trend from Viva Payments, grouped under Revenue & Sales. Computes when a live Viva Payments integration is connected; reconciles ecommerce agai |
      </Accordion>

      <Accordion title="Run operations (6 signals)">
        | Signal                                  | Alert behaviour   | What it tracks                                                                                                                                         |
        | --------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Settlement Time (days)**          | Alert band 2 / 5  | Avg Settlement Time (days) from Viva Payments, grouped under Settlement & Payouts. Computes when a live Viva Payments integration is connected; reconc |
        | **Card vs Customer Country Mismatches** | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Oldest Pending Payout (days)**        | Alert band 7 / 21 | Description pending editorial review; the signal is live.                                                                                              |
        | **Payment Methods**                     | Watch only        | Payment Methods, shown by share.                                                                                                                       |
        | **Pending Payouts**                     | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
        | **Successful Transactions**             | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal           | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Success Rate** | Alert band 97 / 92 | Success Rate from Viva Payments, grouped under Payments & Checkout Health. Computes when a live Viva Payments integration is connected; reconciles eco |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across checkouttransactions, acquiringorders, messagemes, payouts, transactionrefunds on Viva Payments. 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=viva-payments)

    #### Ready to build your first Viva Payments 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | checkouttransactions | 2               | 0                |
      | acquiringorders      | 1               | 0                |
      | messagemes           | 1               | 0                |
      | payouts              | 1               | 0                |
      | transactionrefunds   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Volusion on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/volusion

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Volusion.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Volusion.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/volusion) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=volusion)

<CardGroup>
  <Card title="35">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (35)">
    ### Monitor performance

    35 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (15 signals)">
        | Signal                                | Alert behaviour    | What it tracks                                                                                     |
        | ------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Active Ads on Out-of-Stock SKUs**   | Merchant rule      | Active Ads on Out-of-Stock SKUs, broken down by row.                                               |
        | **Cancellation Rate**                 | Alert band 1 / 3   | Description pending editorial review; the signal is live.                                          |
        | **Catalogue Drift vs Marketplace**    | Merchant rule      | Catalogue Drift vs Marketplace, broken down by row.                                                |
        | **Churn-Risk Customers**              | Alert band 20 / 50 | Previously-active customers with no order in 90+ days - win-back targets.                          |
        | **Email Share of Revenue**            | Merchant rule      | Email Share of Revenue, broken down by row.                                                        |
        | **Low-Stock Products**                | Merchant rule      | Products at or below their Volusion low-stock reorder level.                                       |
        | **Order Status Mix**                  | Watch only         | Distribution of orders across New / Processing / Shipped / Returned / Cancelled.                   |
        | **Order Status Spike**                | Merchant rule      | Fires when any order-status bucket (e.g. Cancelled, Returned) spikes vs its 30D baseline.          |
        | **Out-of-Stock Products**             | Alert band 0 / 5   | Products with stock \<=0 still visible on the storefront.                                          |
        | **Pagespeed-Driven Cart Loss**        | Merchant rule      | Description pending editorial review; the signal is live.                                          |
        | **Refund / Return Rate**              | Alert band 2 / 5   | Returned/refunded orders as a share of orders - product-quality and trust signal.                  |
        | **Refund Rate Spike**                 | Alert band 0 / 1   | Alerts for Refund Rate Spike.                                                                      |
        | **Refund Value**                      | Merchant rule      | Total refunded value - margin destroyer when it climbs past \~8% of revenue.                       |
        | **Refunded Order Count**              | Watch only         | Description pending editorial review; the signal is live.                                          |
        | **Volusion API/Export Failure Spike** | Merchant rule      | Spikes in failed API or CSV-export pulls - early signal of credential expiry or store-host issues. |
      </Accordion>

      <Accordion title="Grow revenue (8 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                                                  |
        | ------------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------- |
        | **Average Order Value**        | Alert band 0 / -5  | Revenue divided by order count - basket size health.                                                            |
        | **Orders Using a Coupon**      | Alert band 20 / 40 | Share of orders (30d) that redeemed a coupon code, via Volusion's dedicated CouponCode export field.            |
        | **Products Missing SEO Meta**  | Alert band 10 / 30 | Products missing SEO title or meta description - suppressed organic and paid conversion.                        |
        | **Repeat Purchase Rate**       | Alert band 25 / 10 | Share of customers with more than one order - retention health for an established catalogue.                    |
        | **Revenue Trend**              | Watch only         | Daily revenue trend over the trailing 90 days.                                                                  |
        | **Revenue by Payment Method**  | Watch only         | Revenue by Payment Method.                                                                                      |
        | **Revenue by Shipping Method** | Watch only         | Revenue by Shipping Method.                                                                                     |
        | **Total Revenue**              | Alert band 0 / -5  | Gross order revenue across 7, 30 and 90 day windows - the top-line executive pulse for a legacy Volusion store. |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                  |
        | ----------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------- |
        | **Fulfillment Rate**                | Alert band 95 / 90 | Share of orders (30d) confirmed shipped via Volusion's dedicated Shipped export field.                          |
        | **New vs Returning Customers**      | Watch only         | New vs Returning Customers, shown by share.                                                                     |
        | **Order Count**                     | Alert band 0 / -10 | Order volume across 7, 30 and 90 day windows with previous-period comparison.                                   |
        | **Pending / Processing Orders**     | Alert band 10 / 50 | Orders still in New / Processing - the fulfilment backlog.                                                      |
        | **Products With No Stock Tracking** | Merchant rule      | Share of catalogue with inventory tracking disabled - intentional for digital goods, sloppy otherwise.          |
        | **Stock-Out Burst**                 | Alert band 0 / 5   | Alerts for Stock-Out Burst.                                                                                     |
        | **Tax Collected by State**          | Watch only         | Sales tax collected per US state - Volusion's merchant base is US-heavy with state-level sales-tax obligations. |
        | **Top Customers by Spend**          | Watch only         | Top Customers by Spend.                                                                                         |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                            | Alert behaviour   | What it tracks                                            |
        | --------------------------------- | ----------------- | --------------------------------------------------------- |
        | **Products Missing Description**  | Alert band 5 / 20 | Description pending editorial review; the signal is live. |
        | **Products Missing Image**        | Merchant rule     | Description pending editorial review; the signal is live. |
        | **Products Missing Manufacturer** | Watch only        | Description pending editorial review; the signal is live. |
        | **Total Products**                | Watch only        | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **0 write** operations across customers, netwebserviceaspx?ediname=generic\customers, netwebserviceaspx?ediname=generic\orders, netwebserviceaspx?ediname=generic\products, netwebserviceaspx?ediname=generic\productsinventorys, netwebserviceaspx?ediname=generic\returns on Volusion. 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=volusion)

    #### Ready to build your first Volusion 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                             | Read operations | Write operations |
      | ---------------------------------------------------- | --------------- | ---------------- |
      | customers                                            | 1               | 0                |
      | netwebserviceaspx?ediname=generic\customers          | 1               | 0                |
      | netwebserviceaspx?ediname=generic\orders             | 1               | 0                |
      | netwebserviceaspx?ediname=generic\products           | 1               | 0                |
      | netwebserviceaspx?ediname=generic\productsinventorys | 1               | 0                |
      | netwebserviceaspx?ediname=generic\returns            | 1               | 0                |
      | orders                                               | 1               | 0                |
      | products                                             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Walmart Marketplace on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/walmart-marketplace

Monitor Walmart Marketplace listings, account health and orders, and catch suppressions and sync problems before they cost sales.

Monitor Walmart Marketplace listings, account health and orders, and catch suppressions and sync problems before they cost sales.

[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=walmart-marketplace)

<CardGroup>
  <Card title="40">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (40)">
    ### Monitor performance

    40 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (12 signals)">
        | Signal                                                            | Alert behaviour    | What it tracks                                                                                                                       |
        | ----------------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Walmart Listings for OOS SKUs on BC**                    | Alert band 0 / 5   | Walmart takes orders you can't fulfil , drives cancellations, late-dispatch hits, and Pro Seller demotion.                           |
        | **Cancellation Rate**                                             | Merchant rule      | Description pending editorial review; the signal is live.                                                                            |
        | **Late Dispatch Rate**                                            | Merchant rule      | Walmart penalises late dispatches with bid visibility cuts at >1% and account suspension risk at >2% sustained.                      |
        | **Late Dispatches Risking Pro Seller Status**                     | Merchant rule      | Walmart's 99% on-time SLA is unforgiving , each late shipment compounds toward bid-visibility cuts and account suspension.           |
        | **Listings Drifting from BC Source-of-Truth**                     | Alert band 5 / 50  | SKUs where Walmart title/price/image differs from BC source-of-truth , buyer confusion AND Walmart parity-enforcement risk.          |
        | **Listings Failing Feedonomics Feed Validation**                  | Alert band 2 / 5   | % of Feedonomics-distributed listings rejected at Walmart ingestion , listings hidden until clean.                                   |
        | **Net Revenue (after Walmart fees + refunds)**                    | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                            |
        | **On-Time Dispatch Rate**                                         | Merchant rule      | Walmart's 99% on-time SLA , below 98% triggers algorithmic visibility cuts; below 97% sustained risks suspension.                    |
        | **Pro Seller Status**                                             | Merchant rule      | Pro Seller badge = higher search ranking + reduced fees. Requires 99% on-time dispatch + \<2% cancel + price parity vs Amazon.       |
        | **Revenue at Risk (live)**                                        | Merchant rule      | (suspended\_listings x velocity x ASP) + (late-dispatch penalty bid loss) + (parity-flagged SKU buy-box loss).                       |
        | **SKUs Priced Differently vs Amazon**                             | Merchant rule      | Walmart Pro Seller programme requires equal-or-lower pricing vs Amazon , violations lose buy-box, ranking, and Pro Seller status.    |
        | **Walmart Account Health (LQS / SLA / Cancel) Crossed Threshold** | Alert band 95 / 85 | Composite of Walmart's three account-health KPIs , any one crossing kicks the seller out of Pro Seller and triggers visibility cuts. |
      </Accordion>

      <Accordion title="Grow revenue (10 signals)">
        | Signal                                   | Alert behaviour    | What it tracks                                                                                               |
        | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------ |
        | **Average Listing Quality Score**        | Alert band 90 / 70 | Walmart's catalog quality KPI , below 60% suppresses listings from search results.                           |
        | **Average Order Value**                  | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                    |
        | **Listings with LQS \<60% (suppressed)** | Alert band 5 / 50  | Walmart hides these from search until LQS rises , direct revenue blocker.                                    |
        | **Orders**                               | Watch only         | Description pending editorial review; the signal is live.                                                    |
        | **Revenue Over Time**                    | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                    |
        | **Top Listings by Revenue**              | Watch only         | Top Listings by Revenue.                                                                                     |
        | **Total Revenue**                        | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                    |
        | **WFS vs Seller-Fulfilled Revenue Mix**  | Watch only         | Walmart Fulfillment Services vs seller-fulfilled split , WFS scales easier but takes more margin.            |
        | **Walmart Fee % of Revenue**             | Alert band 12 / 18 | Total fees / gross revenue , Walmart referral fees range 6-15% by category; +WFS fees if fulfilled.          |
        | **Walmart Marketplace Health Score**     | Merchant rule      | Composite: LQS x SLA x active-listing-pct x inverse-suspended-count. Drives Walmart's auto-visibility logic. |
      </Accordion>

      <Accordion title="Run operations (10 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **AOV by State**                 | Watch only         | AOV by State.                                                                                                                                          |
        | **Buyer Messages Unread**        | Watch only         | Buyer Messages Unread as exposed by the Walmart Marketplace integration. The metric is computed from the latest available data and refreshed on the st |
        | **Days Since Last Payout**       | Alert band 7 / 21  | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Fees Paid**        | Watch only         | Marketplace Fees Paid as exposed by the Walmart Marketplace integration. The metric is computed from the latest available data and refreshed on the st |
        | **Oldest Pending Payout (days)** | Watch only         | Oldest Pending Payout (days) as exposed by the Walmart Marketplace integration. The metric is computed from the latest available data and refreshed on |
        | **Orders / Day**                 | Watch only         | Orders / Day over time.                                                                                                                                |
        | **Orders by State**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Dispatch**             | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending Payouts**              | Watch only         | Pending Payouts as exposed by the Walmart Marketplace integration. The metric is computed from the latest available data and refreshed on the standard |
        | **Return Rate**                  | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Catalogue quality (8 signals)">
        | Signal                                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Listings (Published)**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Buy-Box Win Rate**                      | Alert band 90 / 70 | Walmart often awards buy box to lowest-price seller (incl. WFS). Drops here = price-undercut by competitors or Walmart 1P.                             |
        | **Listings Expiring Soon**                | Watch only         | Listings Expiring Soon as exposed by the Walmart Marketplace integration. The metric is computed from the latest available data and refreshed on the s |
        | **Required-Attribute Completeness**       | Alert band 90 / 70 | % of listings with all Walmart category-mandated attributes filled , drives LQS.                                                                       |
        | **Stale Listings (>180d no update)**      | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Suspended / Item Setup Error Listings** | Alert band 5 / 50  | Description pending editorial review; the signal is live.                                                                                              |
        | **Total Listings**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Walmart Rejected New Listings (24h)**   | Alert band 5 / 50  | Catches feed regressions, schema drift, or Walmart category-rule updates that broke the listing pipeline.                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Listing buy-box win rate below 30% (Amazon-specific; non-applicable elsewhere)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Losing the Buy Box means losing the sale even when the listing wins the search; price, delivery promise and account health drive the algorithm.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-002`
      </Accordion>

      <Accordion title="Listings missing required attributes (varies per marketplace)">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A listing missing a required attribute is commonly suppressed, down-ranked in marketplace search, or blocked from certain placements entirely, so it can be losing sales without showing any error the seller would notice on the listing itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `MARKETPLACE-LISTING-001`
      </Accordion>

      <Accordion title="Seller feedback score dropped > 3pp in 30 days">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Seller feedback score is one of the strongest signals marketplace search ranking and buy-box eligibility use, so a drop this size can cost visibility on every listing, not just the ones that triggered the negative feedback.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEEDBACK-001`
      </Accordion>

      <Accordion title="Marketplace fee % drifted > 2pp vs last quarter">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        The share of revenue this marketplace takes as fees has shifted by more than 2 percentage points from last quarter. On thin-margin products, a shift this size can move a listing from profitable to break-even without anything on the store side changing at all.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-FEE-001`
      </Accordion>

      <Accordion title="Payout overdue > 7 days vs marketplace's typical schedule">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        A payout is running more than 7 days behind this marketplace's usual schedule. That is cash the store has already earned sitting outside its bank account, which matters directly to cash flow regardless of how the underlying sales are performing.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-PAYOUT-001`
      </Accordion>

      <Accordion title="Return rate spiked > 50% vs 90-day average">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Returns on this marketplace jumped more than 50% above the recent average. Beyond the direct cost of the returned goods and return shipping, a spike this size often also damages the seller-performance metrics the marketplace uses for search ranking and account health.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `MARKETPLACE-RETURN-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **2 write** operations across feeds, insightlistingqualitys, items, orders, sellerinfos, tokens on Walmart Marketplace. 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=walmart-marketplace)

    #### Ready to build your first Walmart Marketplace 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.

    <Accordion title="Browse the operations you can build with">
      | Resource               | Read operations | Write operations |
      | ---------------------- | --------------- | ---------------- |
      | feeds                  | 0               | 1                |
      | insightlistingqualitys | 1               | 0                |
      | items                  | 1               | 0                |
      | orders                 | 1               | 0                |
      | sellerinfos            | 1               | 0                |
      | tokens                 | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Wave on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/wave

Monitor Wave payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Wave payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=wave)

<CardGroup>
  <Card title="10">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (10)">
    ### Monitor performance

    10 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (7 signals)">
        | Signal                                 | Alert behaviour    | What it tracks                                                                                             |
        | -------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------- |
        | **AR Aging - 60+ Days**                | Alert band 5 / 15  | Share of AR balance in invoices >60 days past due - the bucket least likely to ever be collected.          |
        | **Accounts Receivable Balance (live)** | Watch only         | Sum of amountDue across all non-PAID, non-DRAFT invoices.                                                  |
        | **Days Sales Outstanding (DSO)**       | Alert band 30 / 60 | Average days from invoice issued to paid - how long cash sits in receivables.                              |
        | **Net Income (month to date)**         | Watch only         | INCOME-type minus EXPENSE-type money transactions for the current period vs the previous.                  |
        | **Overdue Invoices**                   | Alert band 5 / 15  | Invoices in OVERDUE status. Each is cash stuck past its due date.                                          |
        | **Unreviewed Money Transactions**      | Merchant rule      | moneyTransactions in UNREVIEWED status. Backlog = books drift from reality + sales-tax filing understated. |
        | **Wave Health Score**                  | Merchant rule      | Composite: AR-aging-low x invoices-not-overdue x transactions-reviewed x order→invoice-reconciled.         |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                              | Alert behaviour         | What it tracks                                                                                                         |
        | --------------------------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------- |
        | **Ecom Customers Absent from Wave**                 | Alert band 0 / 10       | Sync gap - ecom customers invisible to Wave means invoicing/AR runs against an incomplete customer list.               |
        | **Ecom Orders Missing Matching Wave Invoice**       | Merchant rule           | Storefront revenue that never became a Wave invoice/income transaction - invisible to the books and to sales-tax base. |
        | **Overdue AR on Customers with Active Ecom Orders** | Alert band 1000 / 10000 | Customers who owe overdue money but keep ordering - extend credit knowingly or pause.                                  |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **0 read** and **6 write** operations across graphqlpublic#accounts, graphqlpublic#business, graphqlpublic#customers, graphqlpublic#invoices, graphqlpublic#moneytransactions, graphqlpublics on Wave. 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=wave)

    #### Ready to build your first Wave 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                        | Read operations | Write operations |
      | ------------------------------- | --------------- | ---------------- |
      | graphqlpublic#accounts          | 0               | 1                |
      | graphqlpublic#business          | 0               | 1                |
      | graphqlpublic#customers         | 0               | 1                |
      | graphqlpublic#invoices          | 0               | 1                |
      | graphqlpublic#moneytransactions | 0               | 1                |
      | graphqlpublics                  | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# PageSpeed + CrUX on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/website-performance

Monitor traffic, conversion and tracking integrity from PageSpeed + CrUX, and catch instrumentation breaks before decisions are made on bad data.

Monitor traffic, conversion and tracking integrity from PageSpeed + CrUX, and catch instrumentation breaks before decisions are made on bad data.

[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=website-performance)

<CardGroup>
  <Card title="64">
    performance signals
  </Card>

  <Card title="7">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="1">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (64)">
    ### Monitor performance

    64 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (33 signals)">
        | Signal                                  | Alert behaviour | What it tracks                                            |
        | --------------------------------------- | --------------- | --------------------------------------------------------- |
        | **All CWV Pass**                        | Watch only      | All CWV Pass, broken down by row.                         |
        | **Best Practices Score**                | Watch only      | Description pending editorial review; the signal is live. |
        | **Biggest Regression**                  | Watch only      | Biggest Regression, broken down by row.                   |
        | **CWV Pass by Template**                | Watch only      | CWV Pass by Template.                                     |
        | **Caching Opportunities**               | Watch only      | Caching Opportunities, broken down by row.                |
        | **Field vs Lab**                        | Watch only      | Description pending editorial review; the signal is live. |
        | **Health Score Trend**                  | Watch only      | Description pending editorial review; the signal is live. |
        | **JS Execution Time**                   | Watch only      | JS Execution Time, compared across items.                 |
        | **LCP by Template**                     | Watch only      | LCP by Template.                                          |
        | **Lab Layout Stability**                | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Layout Stability Over Time**          | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Layout Stability: Mobile vs Desktop** | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Mobile vs Desktop Score**             | Watch only      | Description pending editorial review; the signal is live. |
        | **Opportunities by Template**           | Watch only      | Description pending editorial review; the signal is live. |
        | **Overall Score: Mobile vs Desktop**    | Watch only      | Description pending editorial review; the signal is live. |
        | **Page Freeze Time**                    | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Pages by Status**                     | Watch only      | Pages by Status.                                          |
        | **Render-Blocking Resources**           | Watch only      | Render-Blocking Resources, broken down by row.            |
        | **Request Count**                       | Watch only      | Description pending editorial review; the signal is live. |
        | **Responsiveness Over Time**            | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Responsiveness: Mobile vs Desktop**   | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Score by Template**                   | Watch only      | Score by Template.                                        |
        | **Slowest LCP URLs**                    | Watch only      | Slowest LCP URLs, broken down by row.                     |
        | **Slowest Template**                    | Watch only      | Slowest Template, broken down by row.                     |
        | **Template Trend**                      | Watch only      | Description pending editorial review; the signal is live. |
        | **Third-Party Cost**                    | Watch only      | Third-Party Cost, compared across items.                  |
        | **Top Opportunities (bytes)**           | Watch only      | Top Opportunities (bytes), compared across items.         |
        | **Top Opportunities (ms)**              | Watch only      | Top Opportunities (ms), compared across items.            |
        | **Unused CSS**                          | Watch only      | Unused CSS, compared across items.                        |
        | **Unused JavaScript**                   | Watch only      | Unused JavaScript, compared across items.                 |
        | **Urgent Pages**                        | Watch only      | Urgent Pages, broken down by row.                         |
        | **Worst CLS URLs**                      | Watch only      | Worst CLS URLs, broken down by row.                       |
        | **Worst INP URLs**                      | Watch only      | Worst INP URLs, broken down by row.                       |
      </Accordion>

      <Accordion title="Customer experience (26 signals)">
        | Signal                              | Alert behaviour        | What it tracks                                            |
        | ----------------------------------- | ---------------------- | --------------------------------------------------------- |
        | **Accessibility Score**             | Watch only             | Description pending editorial review; the signal is live. |
        | **Click Responsiveness**            | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Desktop Speed Pass Rate**         | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Device Performance Gap**          | Watch only             | Device Performance Gap, broken down by row.               |
        | **First Content Visible**           | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Lab Load Speed**                  | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Layout Shift Distribution**       | Watch only             | Description pending editorial review; the signal is live. |
        | **Layout Stability**                | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Load Speed Distribution**         | Watch only             | Description pending editorial review; the signal is live. |
        | **Load Speed Over Time**            | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Load Speed: Mobile vs Desktop**   | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Mobile Speed Pass Rate**          | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Page Load Speed**                 | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Performance Score**               | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Performance Score Over Time**     | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Performance Score Summary**       | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Responsiveness Distribution**     | Watch only             | Description pending editorial review; the signal is live. |
        | **Server Response Time**            | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Server Speed Over Time**          | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Server Speed: Mobile vs Desktop** | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Site-wide vs Page Performance**   | Watch only             | Description pending editorial review; the signal is live. |
        | **Speed Improvement Opportunities** | Watch only             | Description pending editorial review; the signal is live. |
        | **Speed Index**                     | Alert band 3400 / 5800 | Description pending editorial review; the signal is live. |
        | **Speed Test Pass Rate**            | Merchant rule          | Description pending editorial review; the signal is live. |
        | **Speed Test Pass Rate Over Time**  | Watch only             | Description pending editorial review; the signal is live. |
        | **When Did Speed Get Worse?**       | Watch only             | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                      | Alert behaviour | What it tracks                                            |
        | --------------------------- | --------------- | --------------------------------------------------------- |
        | **First Content Over Time** | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Image Optimisation**      | Watch only      | Image Optimisation, compared across items.                |
        | **Total Page Weight**       | Merchant rule   | Description pending editorial review; the signal is live. |
        | **Weight by Resource Type** | Watch only      | Weight by Resource Type.                                  |
      </Accordion>

      <Accordion title="Grow revenue (1 signals)">
        | Signal        | Alert behaviour | What it tracks                                            |
        | ------------- | --------------- | --------------------------------------------------------- |
        | **SEO Score** | Watch only      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (7)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Core Web Vitals failing on mobile (LCP > 2.5s OR CLS > 0.1 OR INP > 200ms)">
        **Severity** critical · **Outcome** Grow revenue · **Fix status** Report only

        Failing Core Web Vitals on mobile suppresses rankings sitewide and correlates directly with conversion loss; this is the field data Google actually uses.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-CWV-001`
      </Accordion>

      <Accordion title="CWV pass rate below 75% on mobile">
        **Severity** high · **Outcome** Customer experience · **Fix status** Report only

        When fewer than three quarters of sampled pages pass Core Web Vitals, slow experiences are the norm rather than the exception for real visitors.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-CWV-002`
      </Accordion>

      <Accordion title="Lighthouse performance score below 50 on mobile">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        A mobile performance score below 50 means most shoppers meet a visibly slow store; speed is a ranking factor and a conversion factor at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-PERF-001`
      </Accordion>

      <Accordion title="Lighthouse SEO score below 90">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Lighthouse SEO failures are basic crawlability and metadata problems that suppress pages regardless of how good the content is.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-SEO-001`
      </Accordion>

      <Accordion title="Lighthouse accessibility score below 90">
        **Severity** medium · **Outcome** Customer experience · **Fix status** Report only

        An accessibility score below 90 means common assistive-technology journeys are breaking; lost customers and legal exposure in several markets.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-A11Y-001`
      </Accordion>

      <Accordion title="Render-blocking resources blocking > 500ms">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Render-blocking resources delay the first paint beyond half a second; the store feels slower than it needs to be on every single visit.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `WEBPERF-RENDER-001`
      </Accordion>

      <Accordion title="Total page weight above 3 MiB">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Candidate remediation

        Pages heavier than 3 MiB punish mobile and slow-connection shoppers hardest, exactly the visitors with the least patience for it.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `WEBPERF-WEIGHT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **1 read** and **0 write** operations across runpagespeeds on PageSpeed + CrUX. 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=website-performance)

    #### Ready to build your first PageSpeed + CrUX 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.

    <Accordion title="Browse the operations you can build with">
      | Resource      | Read operations | Write operations |
      | ------------- | --------------- | ---------------- |
      | runpagespeeds | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# WooCommerce on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/woocommerce

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to WooCommerce.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to WooCommerce.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/woocommerce) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=woocommerce)

<CardGroup>
  <Card title="66">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="6">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (66)">
    ### Monitor performance

    66 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (21 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Active Coupons**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Active Plugin Count**                         | Watch only         | Active Plugin Count from WooCommerce, grouped under Order Issues. Computes when a live WooCommerce integration is connected; reconciles ecommerce agai |
        | **Average Order Value**                         | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Orders per Customer**                     | Watch only         | Avg Orders per Customer from WooCommerce, grouped under Customer Health. Computes when a live WooCommerce integration is connected; reconciles ecommer |
        | **Avg Processing → Completed Time**             | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Customer Churn (No Purchase 90D)**            | Alert band 20 / 50 | Customer Churn (No Purchase 90D) from WooCommerce, grouped under Customer Health. Computes when a live WooCommerce integration is connected; reconcile |
        | **Fulfillment Rate**                            | Alert band 95 / 90 | Orders with status=completed ÷ total orders (30d). WooCommerce core has no dedicated shipment field; Completed is the closest real signal, and WooComm |
        | **Low-Star Reviews (1-2 stars, 30d)**           | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **New Customers (30d)**                         | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **On-Backorder Products**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Order Processing Backlog**                    | Alert band 10 / 50 | Alerts for Order Processing Backlog.                                                                                                                   |
        | **Order Volume (30d)**                          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Pending / On-Hold Orders**                    | Alert band 10 / 50 | Description pending editorial review; the signal is live.                                                                                              |
        | **Plugin Security-Patch Breach**                | Watch only         | Plugin Security-Patch Breach from WooCommerce, grouped under Order Issues. Computes when a live WooCommerce integration is connected; reconciles ecomm |
        | **Plugins Out-of-Date**                         | Watch only         | Plugins Out-of-Date from WooCommerce, grouped under Order Issues. Computes when a live WooCommerce integration is connected; reconciles ecommerce agai |
        | **Stock Value Snapshot**                        | Watch only         | Stock Value Snapshot from WooCommerce, grouped under Catalogue Health. Computes when a live WooCommerce integration is connected; reconciles ecommerce |
        | **Stock-Out Burst (multiple SKUs OOS in \<1h)** | Merchant rule      | Alerts for Stock-Out Burst (multiple SKUs OOS in \<1h).                                                                                                |
        | **Top Coupons by Usage (30d)**                  | Watch only         | Top Coupons by Usage (30d).                                                                                                                            |
        | **Top Customers by LTV**                        | Watch only         | Top Customers by LTV from WooCommerce, grouped under Customer Health. Computes when a live WooCommerce integration is connected; reconciles ecommerce  |
        | **Total Customers**                             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **WooCommerce Version Status**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (20 signals)">
        | Signal                                          | Alert behaviour    | What it tracks                                                                                                                                         |
        | ----------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cancellation Rate**                           | Alert band 1 / 3   | Description pending editorial review; the signal is live.                                                                                              |
        | **Conversion Rate**                             | Alert band 3 / 1   | Conversion Rate from WooCommerce, grouped under Revenue at Risk. Computes when a live WooCommerce integration is connected; reconciles ecommerce again |
        | **Failed Order Rate**                           | Watch only         | Failed Order Rate from WooCommerce, grouped under Order Issues. Computes when a live WooCommerce integration is connected; reconciles ecommerce agains |
        | **Failed Orders (24h)**                         | Merchant rule      | Status=failed signals checkout/payment-gateway issues. Spike often correlates with plugin update or theme change.                                      |
        | **Failed-Order Spike Alert**                    | Watch only         | Failed-Order Spike Alert from WooCommerce, grouped under Order Issues. Computes when a live WooCommerce integration is connected; reconciles ecommerce |
        | **High-Value Customers Unengaged on Email**     | Merchant rule      | High-Value Customers Unengaged on Email, broken down by row.                                                                                           |
        | **Low-Stock Products**                          | Watch only         | Low-Stock Products from WooCommerce, grouped under Catalogue Health. Computes when a live WooCommerce integration is connected; reconciles ecommerce a |
        | **Orders → Email Campaign Attribution**         | Merchant rule      | Orders → Email Campaign Attribution, broken down by row.                                                                                               |
        | **Out-of-Stock Products**                       | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Pagespeed-Caused Cart-Abandonment Loss**      | Watch only         | Pagespeed-Caused Cart-Abandonment Loss from WooCommerce, grouped under Revenue at Risk. Computes when a live WooCommerce integration is connected; rec |
        | **Plugin Updates (Last 24h)**                   | Merchant rule      | Count of plugin / theme updates in last 24h. When this >0 AND order error rate spikes, almost always indicates plugin-side regression. Pair with wc    |
        | **Refund Rate**                                 | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Refund Rate Spike Alert**                     | Alert band 2 / 5   | Refund Rate Spike Alert from WooCommerce, grouped under Nerve Centre. Computes when a live WooCommerce integration is connected; reconciles ecommerce  |
        | **Refund Value Trend**                          | Watch only         | Refund Value Trend from WooCommerce, grouped under Refunds & Cancellations. Computes when a live WooCommerce integration is connected; reconciles ecom |
        | **Refund-Driven Customer Churn**                | Alert band 20 / 50 | Refund-Driven Customer Churn from WooCommerce, grouped under Refunds & Cancellations. Computes when a live WooCommerce integration is connected; recon |
        | **Revenue at Risk (live)**                      | Merchant rule      | Sum of failed orders + suspended-listing potential + abandoned-checkout estimated value.                                                               |
        | **Top Refunded Products**                       | Watch only         | Top Refunded Products from WooCommerce, grouped under Refunds & Cancellations. Computes when a live WooCommerce integration is connected; reconciles e |
        | **Top-Velocity SKUs vs Ad Spend**               | Merchant rule      | Top-selling SKUs deserve proportional ad spend. Misalignment = under-amplified winners.                                                                |
        | **WC Inventory vs Active Marketplace Listings** | Merchant rule      | Marketplace orders for SKUs OOS on WC = cancellations + customer dissatisfaction. Highest-priority cross-channel diagnostic.                           |
        | **WordPress Core Version Status**               | Merchant rule      | Current WP core version vs latest. Out-of-date core = security risk + WooCommerce compatibility risk.                                                  |
      </Accordion>

      <Accordion title="Grow revenue (13 signals)">
        | Signal                                         | Alert behaviour    | What it tracks                                                                                                                                          |
        | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Coupon Stacking Abuse (>2 coupons / order)** | Merchant rule      | Orders with >2 stacked coupons indicate WC > Marketing > Coupons restrictions misconfigured. Each stacked coupon usually = unintended margin            |
        | **Coupon Usage Rate**                          | Alert band 20 / 40 | Share of orders (30d) with at least one coupon\_lines entry: genuine order-count coupon usage, distinct from Discount as % of Revenue above (which is d |
        | **Discount as % of Revenue**                   | Alert band 20 / 40 | Description pending editorial review; the signal is live.                                                                                               |
        | **Email Share of Total Store Revenue**         | Watch only         | Email Share of Total Store Revenue from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconc  |
        | **Gross Margin**                               | Watch only         | Gross Margin from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconciles ecommerce against  |
        | **Orders by Status**                           | Watch only         | Orders by Status from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconciles ecommerce aga  |
        | **Repeat Customer Rate**                       | Alert band 25 / 10 | Description pending editorial review; the signal is live.                                                                                               |
        | **Revenue Trend**                              | Watch only         | Description pending editorial review; the signal is live.                                                                                               |
        | **Revenue by Payment Method**                  | Watch only         | Revenue by Payment Method from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconciles ecom  |
        | **SSL / HTTPS Status**                         | Watch only         | SSL / HTTPS Status from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconciles ecommerce a  |
        | **Top Categories by Revenue**                  | Watch only         | Top Categories by Revenue from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconciles ecom  |
        | **Top Products by Revenue**                    | Watch only         | Top Products by Revenue from WooCommerce, grouped under Revenue & Growth. Computes when a live WooCommerce integration is connected; reconciles ecomme  |
        | **Total Revenue (30d)**                        | Alert band 0 / -5  | Description pending editorial review; the signal is live.                                                                                               |
      </Accordion>

      <Accordion title="Catalogue quality (8 signals)">
        | Signal                                   | Alert behaviour   | What it tracks                                                                                                                                         |
        | ---------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Ad Spend on OOS Products**             | Alert band 0 / 5  | Ad Spend on OOS Products from WooCommerce, grouped under Catalogue Health. Computes when a live WooCommerce integration is connected; reconciles ecomm |
        | **Average Product Review Rating**        | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Draft Products >30d Old**              | Merchant rule     | Description pending editorial review; the signal is live.                                                                                              |
        | **Marketplace Listing Drift vs Catalog** | Watch only        | Marketplace Listing Drift vs Catalog from WooCommerce, grouped under Catalogue Health. Computes when a live WooCommerce integration is connected; reco |
        | **Products Missing Description**         | Alert band 5 / 20 | Share of fetched products with an empty description field, distinct from short\_description and from Products Missing Image/SKU below.                 |
        | **Products Missing Image**               | Watch only        | Products Missing Image from WooCommerce, grouped under Catalogue Health. Computes when a live WooCommerce integration is connected; reconciles ecommer |
        | **Products Missing SKU**                 | Watch only        | Products Missing SKU from WooCommerce, grouped under Catalogue Health. Computes when a live WooCommerce integration is connected; reconciles ecommerce |
        | **Total Products**                       | Watch only        | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Customer experience (4 signals)">
        | Signal                                      | Alert behaviour | What it tracks                                                                                                                                         |
        | ------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Checkout Error Rate (24h)**               | Merchant rule   | Description pending editorial review; the signal is live.                                                                                              |
        | **Plugin Compatibility Audit**              | Merchant rule   | Cross-references active WP plugins against WooCommerce + WP core version compatibility matrix. Surfaces conflict-likely plugins before they break chec |
        | **Variable Product Attribute Completeness** | Merchant rule   | % of variable products (type=variable) with all required attributes filled across variations. Missing attrs break checkout selection.                  |
        | **WC REST API / Checkout Error Rate Spike** | Merchant rule   | Most common WC failure mode , plugin update breaks checkout. Pair with wc\_recent\_plugin\_updates\_24h for root-cause.                                |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **6 read** and **0 write** operations across coupons, customers, orders, products, product reviews, report sales on WooCommerce. 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=woocommerce)

    #### Ready to build your first WooCommerce 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | coupons         | 1               | 0                |
      | customers       | 1               | 0                |
      | orders          | 1               | 0                |
      | products        | 1               | 0                |
      | product reviews | 1               | 0                |
      | report sales    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# WordPress on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/wordpress

Monitor WordPress publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor WordPress publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=wordpress)

<CardGroup>
  <Card title="37">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="7">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (37)">
    ### Monitor performance

    37 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Catalogue quality (15 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                |
        | -------------------------------- | ------------------ | ----------------------------------------------------------------------------- |
        | **Avg Words per Post**           | Watch only         | Average word count across a sample of recent published posts.                 |
        | **Blog-Attributed Sessions**     | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Categories**                   | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Content Freshness**            | Watch only         | Median age (days) since last update across published posts. Lower is fresher. |
        | **Content by Category**          | Watch only         | Content by Category.                                                          |
        | **Drafts Pending**               | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Media Library Size**           | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Oldest Stale Posts**           | Merchant rule      | Oldest Stale Posts, broken down by row.                                       |
        | **Posts Missing Featured Image** | Merchant rule      | Featured image drives social/open-graph cards + listing thumbnails.           |
        | **Posts Published Trend**        | Watch only         | Description pending editorial review; the signal is live.                     |
        | **Posts by Author**              | Watch only         | Posts by Author.                                                              |
        | **Stale Content**                | Alert band 10 / 40 | % of published posts not modified in the last 12 months.                      |
        | **Stale High-Traffic Posts**     | Merchant rule      | Stale High-Traffic Posts, broken down by row.                                 |
        | **Top Converting Content**       | Watch only         | Top Converting Content, broken down by row.                                   |
        | **Uncategorised Posts**          | Merchant rule      | Description pending editorial review; the signal is live.                     |
      </Accordion>

      <Accordion title="Grow revenue (11 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                                       |
        | --------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------- |
        | **Avg Views per Post**      | Watch only         | Description pending editorial review; the signal is live.                                            |
        | **Blog-Attributed Revenue** | Watch only         | Description pending editorial review; the signal is live.                                            |
        | **Comments per Post**       | Watch only         | Description pending editorial review; the signal is live.                                            |
        | **Content Health Score**    | Alert band 90 / 70 | Composite: publish cadence x (inverse) stale-content x (inverse) moderation backlog x traffic trend. |
        | **Most Commented Posts**    | Watch only         | Most Commented Posts, broken down by row.                                                            |
        | **Publishing Cadence**      | Alert band 4 / 1   | Posts published in the window vs the previous window.                                                |
        | **Top Posts by Views**      | Watch only         | Top Posts by Views.                                                                                  |
        | **Top Referrers**           | Watch only         | Top Referrers, compared across items.                                                                |
        | **Top Search Terms**        | Watch only         | Top Search Terms, broken down by row.                                                                |
        | **Unique Visitors (30d)**   | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                            |
        | **Views Trend**             | Alert band 0 / -20 | Description pending editorial review; the signal is live.                                            |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                            |
        | -------------------------------- | ------------------ | --------------------------------------------------------- |
        | **Comments Awaiting Moderation** | Alert band 0 / 20  | Description pending editorial review; the signal is live. |
        | **Days Since Last Post**         | Watch only         | Description pending editorial review; the signal is live. |
        | **Moderation Backlog Alert**     | Alert band 0 / 20  | Description pending editorial review; the signal is live. |
        | **Posts Missing Excerpt**        | Merchant rule      | Description pending editorial review; the signal is live. |
        | **Published Posts**              | Watch only         | Description pending editorial review; the signal is live. |
        | **Tags**                         | Watch only         | Description pending editorial review; the signal is live. |
        | **Traffic Drop Alert**           | Alert band 0 / -20 | Description pending editorial review; the signal is live. |
        | **Views (30d)**                  | Alert band 0 / -20 | Description pending editorial review; the signal is live. |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Approved Comments**     | Watch only         | Total approved comments across the site (X-WP-Total, all time). Held and spam are auth-gated and excluded from this count.                             |
        | **Comment Approval Rate** | Alert band 80 / 40 | Approved / (approved + held). Needs auth to read held comments; shows no data without it rather than a false 100%. Low = spam flood or over-aggressive |
        | **Spam Caught (Akismet)** | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Site views dropped > 20% vs prior period">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Site views dropping over 20 percent needs a cause before it needs a reaction: seasonality, tracking, or a real ranking loss all look identical at the top line.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-TRAFFIC-001`
      </Accordion>

      <Accordion title="Comment moderation backlog above 20">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        A moderation backlog above 20 leaves genuine questions unanswered in public and spam visible on the store's own pages.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-MODERATION-001`
      </Accordion>

      <Accordion title="Over 40% of content not updated in 12 months">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When over 40 percent of content has not been touched in a year, decay outpaces creation; rankings quietly rot page by page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-STALE-001`
      </Accordion>

      <Accordion title="Publishing pipeline stalled (no post in 30 days)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A stalled publishing pipeline slowly starves organic traffic; content compounds only while it keeps shipping.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CMS-PUBLISH-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **7 read** and **0 write** operations across jetpackstatapps, wpcategorys, wpcomments, wpmedias, wpposts, wptags on WordPress. 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=wordpress)

    #### Ready to build your first WordPress 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | jetpackstatapps | 1               | 0                |
      | wpcategorys     | 1               | 0                |
      | wpcomments      | 1               | 0                |
      | wpmedias        | 1               | 0                |
      | wpposts         | 1               | 0                |
      | wptags          | 1               | 0                |
      | wpusers         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Worldpay on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/worldpay

Monitor Worldpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Worldpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=worldpay)

<CardGroup>
  <Card title="19">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (19)">
    ### Monitor performance

    19 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (11 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                             |
        | ----------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                  | Alert band 15 / 30   | Customers who hit the 3DS challenge and bail. High abandon = checkout friction.                                            |
        | **Chargeback Rate**                       | Alert band 0.5 / 0.9 | Chargebacks as a share of transactions. Crossing 1% risks scheme monitoring programmes.                                    |
        | **Decline Rate**                          | Alert band 5 / 8     | Share of attempts refused. Inverse of success rate; drives recoverable-revenue analysis.                                   |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When Worldpay declines spike, do we see commerce checkout completion drop? If yes, declines are causing real revenue loss. |
        | **Dispute Rate**                          | Alert band 0.5 / 1   | All raised disputes (retrievals + chargebacks) as a share of transactions.                                                 |
        | **Oldest Pending Payout (days)**          | Alert band 2 / 5     | Age of the oldest payout still pending. Cash-flow risk indicator.                                                          |
        | **Recoverable Revenue (decline-driven)**  | Merchant rule        | Total value leaked through soft declines that retry / dunning could recover next month.                                    |
        | **Refund Rate**                           | Alert band 3 / 8     | Refund value as a share of processed volume. Sustained rise signals product or fulfilment issues.                          |
        | **Refund Volume**                         | Watch only           | Description pending editorial review; the signal is live.                                                                  |
        | **Refunds vs Commerce Returns**           | Merchant rule        | Do Worldpay refunds track commerce returns? Divergence flags reconciliation gaps or off-platform refunds.                  |
        | **Top Decline Reasons**                   | Merchant rule        | Reason-coded declines (insufficient funds, do-not-honour, expired card) - each has a different fix.                        |
      </Accordion>

      <Accordion title="Run operations (4 signals)">
        | Signal                  | Alert behaviour | What it tracks                                                                  |
        | ----------------------- | --------------- | ------------------------------------------------------------------------------- |
        | **Average Transaction** | Merchant rule   | Description pending editorial review; the signal is live.                       |
        | **Pending Payouts**     | Merchant rule   | Total value of settled funds not yet paid out to the merchant bank.             |
        | **Top Payment Methods** | Merchant rule   | Mix of card brands and wallets (Visa / Mastercard / Amex / Apple Pay / PayPal). |
        | **Total Transactions**  | Merchant rule   | Description pending editorial review; the signal is live.                       |
      </Accordion>

      <Accordion title="Grow revenue (3 signals)">
        | Signal                         | Alert behaviour    | What it tracks                                                                          |
        | ------------------------------ | ------------------ | --------------------------------------------------------------------------------------- |
        | **Avg Settlement Time (days)** | Alert band 2 / 5   | Average days from transaction to funds paid out. Higher = slower cash conversion.       |
        | **Total Volume**               | Alert band 0 / -15 | Total processed value across all outcomes. The headline revenue-through-gateway number. |
        | **Volume Trend**               | Alert band 0 / -15 | Processed-value trend over the window - spot growth, seasonality, and dips.             |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal           | Alert behaviour    | What it tracks                                                                               |
        | ---------------- | ------------------ | -------------------------------------------------------------------------------------------- |
        | **Success Rate** | Alert band 95 / 90 | Share of authorisation attempts that succeed. The single number for checkout payment health. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Dispute rate above 1% (Visa/Mastercard threshold)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-DISPUTE-001`
      </Accordion>

      <Accordion title="Decline rate above 8%">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PAYMENT-DECLINE-001`
      </Accordion>

      <Accordion title="Refund rate spiked > 50% vs 7-day average">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-REFUND-001`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-3DS-001`
      </Accordion>

      <Accordion title="Payout overdue > 5 days vs typical schedule">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `PAYMENT-PAYOUT-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **3 write** operations across payment querys, disputes, disputedefends, payment refunds, payment reports, payouts on Worldpay. 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=worldpay)

    #### Ready to build your first Worldpay 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.

    <Accordion title="Browse the operations you can build with">
      | Resource        | Read operations | Write operations |
      | --------------- | --------------- | ---------------- |
      | payment querys  | 1               | 1                |
      | disputes        | 1               | 0                |
      | disputedefends  | 0               | 1                |
      | payment refunds | 0               | 1                |
      | payment reports | 1               | 0                |
      | payouts         | 1               | 0                |
      | refunds         | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Wrike on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/wrike-api

Monitor Wrike performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Wrike performance signals, run automated checks, and prepare approved work through Vortex IQ.

[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=wrike-api)

<CardGroup>
  <Card title="42">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="23">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (42)">
    ### Monitor performance

    42 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (37 signals)">
        | Signal                                     | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Rate-Limit Headroom**                | Merchant rule      | Wrike throttles per-account; if we approach the limit, finding-creation slows or fails - surfaces here before it bites.                                |
        | **Avg Cycle Time (days)**                  | Alert band 3 / 7   | completedDate − createdDate, averaged over tasks closed in window.                                                                                     |
        | **Avg Lead Time (days)**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Time-to-Fix (days)**                 | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Backlog by Importance**                  | Merchant rule      | Open task split by Wrike importance (High/Normal/Low) - too many High = no real prioritisation.                                                        |
        | **Backlog by Priority**                    | Merchant rule      | Active tasks grouped by Wrike importance (High / Normal / Low).                                                                                        |
        | **Backlog by Status**                      | Watch only         | Backlog by Status.                                                                                                                                     |
        | **Blocked Tickets**                        | Alert band 3 / 8   | Tasks in a blocked / on-hold custom status - the operational queue's stuck list.                                                                       |
        | **Critical Findings Without a Wrike Task** | Merchant rule      | Critical / high audit findings older than 7 days with no Wrike task - coverage gap. Auto-dispatch missed these or the merchant disabled it; either way |
        | **Cycle Time by Importance**               | Merchant rule      | Cycle Time by Importance.                                                                                                                              |
        | **Cycle Time by Priority**                 | Merchant rule      | Avg cycle time bucketed by Wrike importance.                                                                                                           |
        | **Deferred Tasks**                         | Alert band 3 / 8   | Tasks parked in Deferred - Wrike's stuck/on-hold queue (maps to the archetype blocked-tickets sentiment).                                              |
        | **Finding Resolution Rate (90d)**          | Alert band 75 / 50 | What share of audit findings actually got fixed via the Wrike pipeline. \<50% means we're filing faster than the team drains.                          |
        | **Finding-to-Task Dispatch Lag**           | Merchant rule      | How fast we get findings into Wrike after detection. Slow dispatch = cold leads by the time the team sees them.                                        |
        | **Hours Logged (7d)**                      | Watch only         | Total tracked hours from the timelog endpoint - capacity-utilisation signal for billable teams.                                                        |
        | **In Progress**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Oldest Open (days)**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Tasks**                             | Merchant rule      | Total Active tasks across the account - top-of-funnel backlog volume.                                                                                  |
        | **Open Tickets**                           | Merchant rule      | Total active tasks across the default space - top-of-funnel backlog volume from GET /tasks.                                                            |
        | **Overdue Projects**                       | Merchant rule      | Projects past endDate that are not yet Completed.                                                                                                      |
        | **Overloaded Assignees (>10 open)**        | Alert band 0 / 1   | People with >10 open tasks - capacity bottleneck candidates.                                                                                           |
        | **Projects Newly Gone Red**                | Merchant rule      | Projects that flipped to Red status in the last day - escalate before the next status meeting.                                                         |
        | **Projects by Status**                     | Watch only         | Green / Yellow / Red / On-Hold split across all active projects.                                                                                       |
        | **Rate-Limit Exhausted**                   | Merchant rule      | Wrike is throttling us - finding dispatch will stall. Back off bulk-create and warn the merchant.                                                      |
        | **Scope Added Mid-Sprint**                 | Merchant rule      | Tasks added to the active project folder after its start date.                                                                                         |
        | **Sprint Progress**                        | Alert band 80 / 50 | % of the active project folder's tasks completed vs schedule. Wrike Projects stand in for sprints.                                                     |
        | **Sprint Velocity (avg)**                  | Merchant rule      | Completed tasks per project cycle, last 5 projects.                                                                                                    |
        | **Tasks Completed (7d)**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Tasks by Assignee**                      | Merchant rule      | Tasks by Assignee.                                                                                                                                     |
        | **Throughput Trend**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets Resolved (7d)**                  | Merchant rule      | Tasks completed in the last 7 days vs the prior 7 (completedDate filter).                                                                              |
        | **Tickets by Assignee**                    | Merchant rule      | Active tasks per responsible contact - capacity distribution.                                                                                          |
        | **Unassigned Tasks**                       | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                              |
        | **Unassigned Tickets**                     | Alert band 5 / 20  | Active tasks with an empty responsibleIds list - work nobody owns.                                                                                     |
        | **VortexIQ Findings In Progress**          | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings Open**                 | Merchant rule      | Tasks we filed from audit findings that haven't been completed yet - the live backlog of things VortexIQ surfaced.                                     |
        | **VortexIQ Findings Resolved**             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                              |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently. |
        | **Abandoned-Findings Burst**              | Alert band 5 / 15 | Sudden spike in findings hitting the 14d abandonment threshold - capacity issue or process breakdown.       |
        | **Projects At Risk (Red)**                | Merchant rule     | Projects flagged Red - actively behind or blocked. The headline answer to 'what's at risk this morning?'.   |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                          | Alert behaviour | What it tracks                                                                                                             |
        | ------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------- |
        | **Wrike Token Expiry Imminent** | Merchant rule   | If the OAuth token expires we silently stop creating tasks - every audit finding goes into the void. Surface 7 days early. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal            | Alert behaviour | What it tracks                                                      |
        | ----------------- | --------------- | ------------------------------------------------------------------- |
        | **Overdue Tasks** | Merchant rule   | Active tasks past dueDate - slippage signal feeding project health. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time 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: `PM-AUTH-001, PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001, PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001, PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001, PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001, PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001, PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **16 read** and **7 write** operations across tasks, foldertasks, contacts, folders, taskcomments, workflows on Wrike. 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=wrike-api)

    #### Ready to build your first Wrike 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.

    <Accordion title="Browse the operations you can build with">
      | Resource     | Read operations | Write operations |
      | ------------ | --------------- | ---------------- |
      | tasks        | 4               | 3                |
      | foldertasks  | 1               | 2                |
      | contacts     | 2               | 0                |
      | folders      | 2               | 0                |
      | taskcomments | 0               | 2                |
      | workflows    | 2               | 0                |
      | accounts     | 1               | 0                |
      | comments     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Xero (API) on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/xero-api

Monitor Xero (API) payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Xero (API) payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=xero-api)

<CardGroup>
  <Card title="23">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (23)">
    ### Monitor performance

    23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                               | Alert behaviour         | What it tracks                                                                                                                            |
        | ------------------------------------ | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
        | **AR Aging - 60+ Days**              | Alert band 5 / 15       | Share of AR balance aged 60+ days, from Reports/AgedReceivablesByContact.                                                                 |
        | **AR Aging Buckets**                 | Watch only              | Outstanding balance bucketed 0-30 / 31-60 / 61-90 / 90+ days from Reports/AgedReceivablesByContact.                                       |
        | **Bank Reconciliation Going Stale**  | Merchant rule           | Unreconciled bank lines piling up - the books drift from cash and the VAT/GST return base is unreliable.                                  |
        | **Days Sales Outstanding (DSO)**     | Alert band 30 / 60      | AR balance / average daily sales-invoice value.                                                                                           |
        | **ERP-vs-Ecom Inventory Variance %** | Alert band 1 / 5        | Xero QuantityOnHand vs storefront available qty on tracked items with active orders.                                                      |
        | **New Overdue AR Crossed Threshold** | Alert band 1000 / 10000 | Receivables aging past collectable - escalate to the collections queue.                                                                   |
        | **Period Close Overdue**             | Alert band 0 / 5        | Organisation.PeriodLockDate vs the oldest calendar month it hasn't yet covered - days the books have gone unclosed past that month's end. |
        | **Tracked Inventory Value**          | Watch only              | Σ TotalCostPool on items with IsTrackedAsInventory=true. Most Xero orgs use untracked items - card hides for them.                        |
        | **Unbalanced Draft Manual Journals** | Alert band 0 / 5        | Status==DRAFT ManualJournals whose JournalLines LineAmount total isn't zero - Xero only blocks the imbalance at Post, not at Save Draft.  |
        | **Unreconciled Bank Transactions**   | Merchant rule           | BankTransaction rows with IsReconciled=false. Backlog = books drifting from cash + unreliable VAT/GST base.                               |
        | **Xero Health Score**                | Merchant rule           | Composite: order-to-books-sync-clean x bank-rec-current x AR-aging-low x VAT/GST-on-track.                                                |
      </Accordion>

      <Accordion title="Protect revenue (5 signals)">
        | Signal                                                   | Alert behaviour         | What it tracks                                                                                                                                |
        | -------------------------------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AR Aging on Customers with Active Ecom Orders**        | Alert band 1000 / 10000 | Credit risk compounding - overdue AR on customers you're still shipping to.                                                                   |
        | **Current VAT/GST Return Status**                        | Merchant rule           | Period-end VAT (UK MTD) / GST (AU/NZ) cycle status, derived from TaxType lines + organisation tax period. Overdue = surcharge / penalty risk. |
        | **Ecom Customers Absent from Xero Contacts**             | Alert band 0 / 10       | Sync gap - B2B-flagged ecom customers missing in Xero break AR invoicing + tax classification on the next batch.                              |
        | **Ecom Orders Missing a Matching Xero Invoice**          | Merchant rule           | Storefront orders never posted to Xero = revenue invisible to the books + understated VAT/GST base.                                           |
        | **PSP Payouts Missing a Matching Xero Bank Transaction** | Merchant rule           | Stripe/PayPal settlements not matched in Xero = cash position wrong + reconciliation backlog.                                                 |
      </Accordion>

      <Accordion title="Control risk and change (3 signals)">
        | Signal                         | Alert behaviour   | What it tracks                                                                                                                                        |
        | ------------------------------ | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AR Balance (live)**          | Watch only        | Sum of AmountDue across AUTHORISED ACCREC (sales) invoices.                                                                                           |
        | **Open Draft Manual Journals** | Alert band 0 / 50 | Status==DRAFT ManualJournals awaiting posting - Xero's only draft-journal surface is manual journals specifically; AUTHORISED sales/purchase invoices |
        | **Overdue Invoice Value**      | Merchant rule     | Σ AmountDue on AUTHORISED ACCREC invoices past DueDate.                                                                                               |
      </Accordion>

      <Accordion title="Grow revenue (3 signals)">
        | Signal                                         | Alert behaviour | What it tracks                                                                                                      |
        | ---------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **Revenue (sales invoices, 30d)**              | Watch only      | Σ Total on AUTHORISED/PAID ACCREC invoices in the window.                                                           |
        | **Sales Invoices by Status**                   | Watch only      | ACCREC invoice counts by DRAFT / SUBMITTED / AUTHORISED / PAID - draft backlog = invoicing stuck.                   |
        | **VAT/GST Return Approaching / Past Deadline** | Merchant rule   | UK MTD VAT / AU-NZ GST submission overdue = surcharge + repeat-offender escalation. Pair with bank-rec-stale alarm. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                            | Alert behaviour | What it tracks                                                 |
        | --------------------------------- | --------------- | -------------------------------------------------------------- |
        | **Cash Position (bank accounts)** | Watch only      | Sum of bank-account balances (Type=BANK). Bank-feed dependent. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Journal entries failed to post (debit != credit)">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only

        An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-002`
      </Accordion>

      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **9 read** and **0 write** operations across apixroaccounts, apixrobanktransactions, apixrocontacts, apixroinvoices, apixroitems, apixroorganisations on Xero (API). 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=xero-api)

    #### Ready to build your first Xero (API) 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                              | Read operations | Write operations |
      | ------------------------------------- | --------------- | ---------------- |
      | apixroaccounts                        | 1               | 0                |
      | apixrobanktransactions                | 1               | 0                |
      | apixrocontacts                        | 1               | 0                |
      | apixroinvoices                        | 1               | 0                |
      | apixroitems                           | 1               | 0                |
      | apixroorganisations                   | 1               | 0                |
      | apixroreportagedreceivablesbycontacts | 1               | 0                |
      | apixroreportbalancesheets             | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# YouTube on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/youtube

Monitor YouTube publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor YouTube publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=youtube)

<CardGroup>
  <Card title="17">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (17)">
    ### Monitor performance

    17 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Grow revenue (14 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                                     |
        | --------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
        | **Avg Session Duration**    | Merchant rule      | Average dwell time of YouTube-referred sessions.                                                   |
        | **Engagement Rate**         | Alert band 3 / 1   | (likes + comments) on videos uploaded in the last 30 days / views, averaged per video.             |
        | **Goal Completions**        | Merchant rule      | Key-event / goal completions from YouTube-referred sessions.                                       |
        | **New Users**               | Merchant rule      | First-time storefront visitors referred by YouTube.                                                |
        | **Pageviews per Session**   | Merchant rule      | Average screen/page views per YouTube-referred session.                                            |
        | **Posting Cadence**         | Alert band 0 / -40 | Videos uploaded in the last 30 days vs the prior 30 days.                                          |
        | **Real-Time Users**         | Merchant rule      | Live storefront users currently from YouTube referral (realtime report).                           |
        | **Returning Users**         | Merchant rule      | Returning storefront visitors referred by YouTube.                                                 |
        | **Session Conversion Rate** | Alert band 2 / 1   | Conversion rate of YouTube-referred sessions vs the site baseline.                                 |
        | **Sessions**                | Alert band 0 / -20 | Storefront sessions attributed to YouTube referral source/medium.                                  |
        | **Social Health Score**     | Alert band 90 / 70 | Composite: per-video engagement rate (50%) x posting cadence (30%) x days-since-last-upload (20%). |
        | **Top Pages**               | Merchant rule      | Storefront landing pages most visited by YouTube referral traffic.                                 |
        | **Top Traffic Sources**     | Merchant rule      | YouTube source/medium breakdown (youtube / referral, youtube / social, m.youtube.com).             |
        | **Users**                   | Merchant rule      | Active users arriving on the storefront from YouTube.                                              |
      </Accordion>

      <Accordion title="Protect revenue (2 signals)">
        | Signal                    | Alert behaviour    | What it tracks                                                  |
        | ------------------------- | ------------------ | --------------------------------------------------------------- |
        | **Bounce Rate**           | Alert band 40 / 60 | Share of YouTube-referred sessions that leave without engaging. |
        | **Cart Abandonment Rate** | Alert band 60 / 75 | Share of YouTube-referred carts that never complete checkout.   |
      </Accordion>

      <Accordion title="Run operations (1 signals)">
        | Signal          | Alert behaviour   | What it tracks                                                                                                                                         |
        | --------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Subscribers** | Alert band 0 / -2 | channels.list statistics.subscriberCount, trended against the total 30 days ago (reconstructed from the real subscribersGained/subscribersLost delta - |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Engagement rate below 1%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Engagement below 1 percent means content is reaching feeds and being scrolled past; format and hook need work before spend goes behind it.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-ENGAGEMENT-001`
      </Accordion>

      <Accordion title="Reach dropped > 20% vs prior period">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Reach dropping over 20 percent usually means the algorithm has deprioritised the account or a format change landed badly; catching it early keeps the slide shallow.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-REACH-001`
      </Accordion>

      <Accordion title="Posting cadence collapsed (no post in 14 days)">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Report only

        Posting cadence collapsing to zero lets the audience's attention lapse; reach compounds only while the account stays present.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SOCIAL-CADENCE-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **3 write** operations across v1betapropertys, https:oauth2googleapicomtokens, https:wwwgoogleapicomyoutubechannels, https:wwwgoogleapicomyoutubeplaylistitems, https:wwwgoogleapicomyoutubevideos, https:youtubeanalyticgoogleapicomreports on YouTube. 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=youtube)

    #### Ready to build your first YouTube 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                                  | Read operations | Write operations |
      | ----------------------------------------- | --------------- | ---------------- |
      | v1betapropertys                           | 0               | 2                |
      | https:oauth2googleapicomtokens            | 0               | 1                |
      | https:wwwgoogleapicomyoutubechannels      | 1               | 0                |
      | https:wwwgoogleapicomyoutubeplaylistitems | 1               | 0                |
      | https:wwwgoogleapicomyoutubevideos        | 1               | 0                |
      | https:youtubeanalyticgoogleapicomreports  | 1               | 0                |
      | v1betapropertymetadatas                   | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Zendesk on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/zendesk

Monitor Zendesk pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Zendesk 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=zendesk)

<CardGroup>
  <Card title="24">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (24)">
    ### Monitor performance

    24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (22 signals)">
        | Signal                              | Alert behaviour    | What it tracks                                                                                                                                   |
        | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**           | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                        |
        | **Avg Lead Time (days)**            | Alert band 7 / 14  | Description pending editorial review; the signal is live.                                                                                        |
        | **Avg Time-to-Fix (days)**          | Merchant rule      | Description pending editorial review; the signal is live.                                                                                        |
        | **Backlog by Priority**             | Merchant rule      | Backlog by Priority.                                                                                                                             |
        | **Backlog by Status**               | Merchant rule      | Backlog by Status.                                                                                                                               |
        | **Blocked Tickets**                 | Alert band 3 / 8   | Tickets in On-hold / blocked state - the operational queue's stuck list.                                                                         |
        | **Cycle Time by Priority**          | Merchant rule      | Cycle Time by Priority.                                                                                                                          |
        | **Finding Resolution Rate (90d)**   | Alert band 75 / 50 | What share of audit findings filed in the last 90d actually got fixed via the Zendesk pipeline. \<50% means we file faster than the team drains. |
        | **In Progress**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                        |
        | **Oldest Open (days)**              | Alert band 30 / 90 | Description pending editorial review; the signal is live.                                                                                        |
        | **Open Tickets**                    | Alert band 0 / 100 | Total open tickets across the connected brands - top-of-funnel backlog volume.                                                                   |
        | **Overloaded Assignees (>10 open)** | Merchant rule      | People with >10 open tickets - capacity bottleneck candidates.                                                                                   |
        | **Scope Added Mid-Sprint**          | Alert band 5 / 15  | Description pending editorial review; the signal is live.                                                                                        |
        | **Sprint Progress**                 | Alert band 90 / 70 | Description pending editorial review; the signal is live.                                                                                        |
        | **Sprint Velocity (avg)**           | Alert band 0 / 20  | Sprint Velocity (avg) over time.                                                                                                                 |
        | **Throughput Trend**                | Merchant rule      | Description pending editorial review; the signal is live.                                                                                        |
        | **Tickets Resolved (7d)**           | Alert band 0 / 25  | Description pending editorial review; the signal is live.                                                                                        |
        | **Tickets by Assignee**             | Merchant rule      | Tickets by Assignee.                                                                                                                             |
        | **Unassigned Tickets**              | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                        |
        | **VortexIQ Findings In Progress**   | Watch only         | Description pending editorial review; the signal is live.                                                                                        |
        | **VortexIQ Findings Open**          | Merchant rule      | Tickets we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced.                              |
        | **VortexIQ Findings Resolved**      | Watch only         | Description pending editorial review; the signal is live.                                                                                        |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                              |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently. |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal   | Alert behaviour    | What it tracks                                                                                                                                            |
        | -------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **CSAT** | Alert band 90 / 70 | GET /api/v2/satisfaction\_ratings.json - good / (good + bad) \* 100 over rated tickets in the window. Bare support\_helpdesk sentiment\_key so this picks |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CSAT below 70%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-CSAT-001`
      </Accordion>

      <Accordion title="First-response SLA breached on open conversations">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Breached first-response SLAs compound: late answers create chase messages, which create more queue, which creates later answers.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-SLA-001`
      </Accordion>

      <Accordion title="Median first-response time above 4h">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-FRT-001`
      </Accordion>

      <Accordion title="Open-conversation backlog rising > 20% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `SUPPORT-BACKLOG-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **2 write** operations across ticketjsons, brandjsons, groupjsons, satisfactionratingjsons, searchcountjsons, searchjsons on Zendesk. 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=zendesk)

    #### Ready to build your first Zendesk 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.

    <Accordion title="Browse the operations you can build with">
      | Resource                | Read operations | Write operations |
      | ----------------------- | --------------- | ---------------- |
      | ticketjsons             | 1               | 1                |
      | brandjsons              | 1               | 0                |
      | groupjsons              | 1               | 0                |
      | satisfactionratingjsons | 1               | 0                |
      | searchcountjsons        | 1               | 0                |
      | searchjsons             | 1               | 0                |
      | tickets                 | 0               | 1                |
      | userjsons               | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Zoho Books on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/zoho-books

Monitor Zoho Books payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Zoho Books payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

[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=zoho-books)

<CardGroup>
  <Card title="13">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="8">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (13)">
    ### Monitor performance

    13 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (7 signals)">
        | Signal                               | Alert behaviour   | What it tracks                                                                                                                                           |
        | ------------------------------------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **AR Aging - 60+ Days**              | Alert band 5 / 15 | Share of outstanding receivable aged 60+ days from invoice due\_date. Reports/AgingSummary if enabled, else derived from invoice balances + due\_date.   |
        | **AR Outstanding (live)**            | Watch only        | Sum of Invoice.balance across unpaid / overdue / partially\_paid invoices.                                                                               |
        | **ERP-vs-Ecom Inventory Variance %** | Alert band 1 / 5  | Zoho Books available\_stock vs storefront available qty on stock-tracked SKUs with active orders. Inventory-tracking items only - card hides for servic  |
        | **Overdue Invoice Value**            | Merchant rule     | Sum of Invoice.balance where status = overdue (date past due\_date). Collections priority.                                                               |
        | **Period Close Overdue**             | Alert band 0 / 5  | transaction\_lock\_date vs the oldest calendar month it hasn't yet covered - days the books have gone unclosed past that month's end. Disabled/never-set |
        | **Unposted (Draft) Journal Entries** | Alert band 0 / 50 | Count of Zoho Books manual journals in draft status - Zoho enforces debit==credit even on a draft save, so these are balanced but not yet finalised to   |
        | **Zoho Books Health Score**          | Merchant rule     | Composite: order-to-cash-sync-clean x AR-aging-low x bank-recon-fresh x overdue-bills-low.                                                               |
      </Accordion>

      <Accordion title="Protect revenue (4 signals)">
        | Signal                                                | Alert behaviour         | What it tracks                                                                                                    |
        | ----------------------------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------- |
        | **Ecom Customers Absent from Zoho Books Contacts**    | Alert band 0 / 10       | Sync gap - repeat ecom buyers invisible to Zoho Books breaks invoicing, GST/VAT reporting and B2B tax-reg checks. |
        | **Ecom Orders Missing a Matching Zoho Books Invoice** | Merchant rule           | Storefront orders never posted to Zoho Books = revenue invisible to the books + understated tax base.             |
        | **Overdue AR on Customers with Active Ecom Orders**   | Alert band 1000 / 10000 | Credit risk compounding - overdue AR on customers you are still shipping to.                                      |
        | **Overdue Bills (AP)**                                | Alert band 1000 / 10000 | Sum of Bill.balance where status = overdue. Late-payment / supplier-relationship risk.                            |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                  |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------- |
        | **Days Sales Outstanding (DSO)** | Alert band 30 / 60 | Outstanding receivable / average daily invoiced revenue. Derived from invoices. |
        | **Revenue Invoiced**             | Watch only         | Sum of Invoice.total by day for sent/paid invoices in the window.               |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="AR aging on 60+ day buckets above threshold">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-FIN-001`
      </Accordion>

      <Accordion title="ERP-vs-ecom inventory variance > 5% on SKUs with active orders">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-INV-001`
      </Accordion>

      <Accordion title="Period close past deadline">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-CLOSE-001`
      </Accordion>

      <Accordion title="Unposted journal entries >50 (GL hygiene)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ERP-GL-001`
      </Accordion>

      <Accordion title="Ecom customers absent from ERP customer master after 7d">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ERP-CUST-001`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **0 write** operations across bookbanktransactions, bookbills, bookcontacts, bookinvoices, bookitems, bookjournals on Zoho Books. 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=zoho-books)

    #### Ready to build your first Zoho Books 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.

    <Accordion title="Browse the operations you can build with">
      | Resource             | Read operations | Write operations |
      | -------------------- | --------------- | ---------------- |
      | bookbanktransactions | 1               | 0                |
      | bookbills            | 1               | 0                |
      | bookcontacts         | 1               | 0                |
      | bookinvoices         | 1               | 0                |
      | bookitems            | 1               | 0                |
      | bookjournals         | 1               | 0                |
      | bookorganizations    | 1               | 0                |
      | booktransactionlocks | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Zoho CRM on Vortex IQ
Source: https://docs.vortexiq.ai/connectors/zoho-crm

Monitor Zoho CRM pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn.

Monitor Zoho CRM 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=zoho-crm)

<CardGroup>
  <Card title="32">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="9">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (32)">
    ### Monitor performance

    32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (13 signals)">
        | Signal                     | Alert behaviour     | What it tracks                                                                                                                                            |
        | -------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **CRM Data Hygiene Score** | Alert band 95 / 80  | Composite of two confirmed real Contact fields: share with Email populated and share with Phone populated. A genuine multi-field composite, not a sing    |
        | **Click-to-Open Rate**     | Alert band 10 / 3   | Clicks / opens - message relevance. Gauge bands: good ≥10%, warn ≤3%.                                                                                     |
        | **Email Click Rate**       | Alert band 2 / 0.5  | Clicks / delivered. Gauge bands: good ≥2%, warn ≤0.5%.                                                                                                    |
        | **Email Open Rate**        | Alert band 20 / 10  | Opens / delivered. Gauge bands: good ≥20%, warn ≤10%.                                                                                                     |
        | **Flow Count Summary**     | Merchant rule       | Total workflow rules (flows) and how many are active.                                                                                                     |
        | **Flow Trigger Types**     | Merchant rule       | Workflow rules grouped by trigger (create/edit/field-update/date-time).                                                                                   |
        | **Flows List**             | Merchant rule       | Tabular list of workflow rules with status, trigger and 30d execution count.                                                                              |
        | **Lead Response Time**     | Alert band 60 / 480 | Median minutes from Lead.Created\_Time to the Created\_Time of the first Task logged against that lead (Tasks.Who\_Id references the Lead - Zoho's confir |
        | **Lists Overview**         | Merchant rule       | Per-list table: name, type, member count, active members.                                                                                                 |
        | **Placed Orders Total**    | Merchant rule       | Orders attributed to email sends in the window (Placed Order metric).                                                                                     |
        | **Segments Overview**      | Merchant rule       | Dynamic segments (custom views) with member counts and last refresh.                                                                                      |
        | **Stalled Deal %**         | Alert band 10 / 30  | Open Deals with no logged activity in 14 days, as a share of all open Deals. Tasks.What\_Id is Zoho's confirmed standard activity-to-record reference f   |
        | **Top Lists by Name**      | Merchant rule       | Largest lists ranked by member count.                                                                                                                     |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                                    |
        | ----------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------- |
        | **Campaign Status Breakdown** | Merchant rule   | Count of campaigns by status (Planning/Active/Scheduled/Sent/Complete/Aborted).                                   |
        | **Checkout-to-Order Rate**    | Merchant rule   | Of email-driven checkouts started, the share that became orders; reconciled with the ecom sibling's order events. |
        | **Conversion Rate**           | Merchant rule   | Orders / delivered emails - overall email conversion.                                                             |
        | **Engagement Funnel**         | Merchant rule   | Sent → delivered → opened → clicked → converted funnel for outbound email.                                        |
        | **List Health Summary**       | Merchant rule   | Active-member share across lists - low = stale/decaying audience.                                                 |
        | **Revenue per Recipient**     | Merchant rule   | Attributed revenue divided by unique recipients.                                                                  |
        | **Revenue per Send**          | Merchant rule   | Attributed revenue divided by total sends.                                                                        |
        | **Total Revenue**             | Merchant rule   | Email-attributed revenue from Zoho CRM campaigns; cross-checked against the ecom sibling's actual order revenue.  |
        | **Total Sends**               | Merchant rule   | Total emails sent across campaigns in the window.                                                                 |
      </Accordion>

      <Accordion title="Protect revenue (8 signals)">
        | Signal                        | Alert behaviour      | What it tracks                                                                                                       |
        | ----------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Active Subscribers (Est.)** | Merchant rule        | Estimated subscribed/deliverable contacts (Email\_Opt\_Out = false, not hard-bounced).                               |
        | **Bounce Rate**               | Alert band 2 / 5     | Bounces / sent (inverse gauge). Bands: good ≤2%, warn ≥5%. Sustained high = list-hygiene or auth (SPF/DKIM) problem. |
        | **Delivery Rate**             | Alert band 98 / 95   | Delivered / sent. Gauge bands: good ≥98%, warn ≤95%.                                                                 |
        | **Email Health KPIs**         | Merchant rule        | Composite email-health roll-up (delivery, open, click, bounce) in one card.                                          |
        | **Flow Status Breakdown**     | Merchant rule        | Workflow rules grouped by status (active/paused/draft/archived) - paused-heavy = abandoned automation.               |
        | **Refund Rate**               | Alert band 1 / 5     | Refunded share of email-attributed revenue - high = post-purchase dissatisfaction or returns leakage.                |
        | **Spam Complaint Rate**       | Alert band 0.1 / 0.3 | Spam reports / delivered (inverse gauge). Bands: good ≤0.1%, warn ≥0.3%. Above 0.3% risks sender-reputation damage.  |
        | **Unsubscribe Rate**          | Alert band 0.5 / 2   | Unsubscribes / delivered (inverse gauge). Bands: good ≤0.5%, warn ≥2%.                                               |
      </Accordion>

      <Accordion title="Customer experience (1 signals)">
        | Signal                | Alert behaviour | What it tracks                                                |
        | --------------------- | --------------- | ------------------------------------------------------------- |
        | **Checkouts Started** | Merchant rule   | Checkouts started attributed to email activity in the window. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal         | Alert behaviour | What it tracks                                                |
        | -------------- | --------------- | ------------------------------------------------------------- |
        | **List Count** | Merchant rule   | Total contact lists / custom views configured in the account. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="CRM API token invalid or scope insufficient">
        **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`
      </Accordion>

      <Accordion title="Median lead response time above 8h">
        **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`
      </Accordion>

      <Accordion title="Stalled open deals above threshold (no activity in 14 days)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CRM-PIPE-001`
      </Accordion>

      <Accordion title="CRM data hygiene below 80% (missing required fields)">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **1 write** operations across deals, actionworkflowrules, campaigns, contacts, leads, orgs on Zoho CRM. 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=zoho-crm)

    #### Ready to build your first Zoho CRM 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.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | deals               | 1               | 1                |
      | actionworkflowrules | 1               | 0                |
      | campaigns           | 1               | 0                |
      | contacts            | 1               | 0                |
      | leads               | 1               | 0                |
      | orgs                | 1               | 0                |
      | settingscustomviews | 1               | 0                |
      | tasks               | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>


# Vortex IQ glossary: key terms explained
Source: https://docs.vortexiq.ai/get-started/glossary

Definitions for every Vortex IQ AI OS product term - modules, card types, findings, connectors, profiles, and the agentic concepts that tie them together.

Every product term you encounter in the Vortex IQ documentation, defined in plain English. If you read a word in the docs and are not sure what it means, this is the page. Terms are in alphabetical order.

<AccordionGroup>
  <Accordion title="Action (item)">
    A piece of work surfaced in the Actions module. Each Action has a title, a source (which finding produced it), a severity level, an assignee (or "auto"), and a status on the Kanban board (Backlog, In progress, In review, Shipped).

    Actions are the unit of execution in Vortex IQ. They start as findings, get ranked by severity, and ship through Vortex Apps when you approve them.
  </Accordion>

  <Accordion title="Actions (module)">
    The work surface of the AI OS - the fourth of the six modules. The Actions hub contains the Audit Dashboard, the Kanban board, the SEO + GEO Domination Engine, the Bulk Content Edit grid, and the Briefings cards.

    This is where findings become tasks become shipped fixes.
  </Accordion>

  <Accordion title="Agentic loop">
    The end-to-end flow that Vortex IQ runs on your behalf: **signal → diagnosis → action proposal → human approval → execution**.

    The Nerve Centre detects a signal, Vortex Mind diagnoses its cause, an Action is proposed, you approve it, and Vortex Apps executes the fix. You are in the loop at the approval step for any high-impact action; the OS handles the rest automatically.
  </Accordion>

  <Accordion title="AI OS">
    Short for AI Operating System. Vortex IQ's self-description and category positioning. The "OS" framing means the platform acts as a connective layer beneath every ecommerce tool you run - reading signals from all of them, reasoning across those signals with AI, and shipping fixes back into the relevant platforms.

    The distinction from a dashboard, a chatbot, or a SaaS suite is that the connections between data sources are pre-wired, run continuously, and are shared by all six modules through a single connector graph.
  </Accordion>

  <Accordion title="Ask Viq">
    The conversational AI module - the third of the six modules. You type plain-English questions and receive charted answers scoped to a saved Profile of connectors.

    Ask Viq queries the live connector graph - the same data that the Nerve Centre and Vortex Mind use - rather than running on generic LLM knowledge. The brand is always written as two words ("Ask Viq"); the second word is never used by itself as a standalone product name.
  </Accordion>

  <Accordion title="Connector">
    The named integration to a specific platform - for example, the Shopify connector, the Stripe connector, or the Klaviyo connector. Vortex IQ supports over 200 connectors spanning commerce platforms, payment gateways, ad platforms, analytics tools, email and CRM, fulfilment providers, monitoring stacks, marketplaces, and more.

    Each connected instance of a connector is a **Connected Source** on the Settings, Connected Sources tab.

    Connectors come in two classes, and the class decides what you see:

    * **Data sources** hold auditable state: stores, ad accounts, payment gateways, analytics, marketplaces, email platforms. They carry KPI cards on the Nerve Centre and an audit profile.
    * **Channels** are where Vortex IQ sends and receives messages: Slack, Microsoft Teams, Telegram, Discord, Twilio, Pushover, email. Channels are health-checked but never audited, and they carry no business KPI cards. A channel may show connection-health cards, for example whether its webhook is configured and which host it points at, but never business metrics.

    Email marketing platforms such as Klaviyo, Mailchimp, Brevo and SendGrid are **data sources**, not channels. They measure campaign performance and revenue, so they carry full KPI cards. The channel class covers only the alert-delivery surfaces above.
  </Accordion>

  <Accordion title="Cross-platform card">
    A KPI card on the Nerve Centre that fuses signal from two or more connectors. Examples:

    * *Ad spend on out-of-stock SKUs* - Google Ads + Shopify inventory
    * *Stripe declines on email-recovery customers* - Stripe + Klaviyo
    * *Cart-page LCP vs paid traffic conversion* - CrUX + Google Ads + Shopify

    Cross-platform cards are the AI OS positioning anchor: a standard dashboard tool shows you one source at a time; the connector graph fuses them.
  </Accordion>

  <Accordion title="Finding">
    One diagnostic insight produced by Vortex Mind or the Audit module. Each finding has a title, a severity (Critical, High, Medium, Low), a source (which connector or audit category produced it), an explanation of why it matters, and a recommended fix.

    Findings turn into Actions automatically and appear as cards on the Kanban board.
  </Accordion>

  <Accordion title="Key Metrics card">
    The highest-priority KPI cards on a Nerve Centre connector tab. Each tab has 3 to 5 Key Metrics cards highlighted at the top. For the Shopify tab, Key Metrics cards include Total revenue, Conversion rate, Average order value, and Cart abandonment.

    Key Metrics cards are the primary metrics for each connected platform - the numbers you check first every morning.
  </Accordion>

  <Accordion title="KPI card">
    One metric tile on the Nerve Centre. Each card shows the metric name (for example, *Add-to-cart rate*, *Largest Contentful Paint*, *Decline rate*), the current value, a trend line, and a sentiment colour (green, amber, or red) that reflects whether the metric is healthy, worth watching, or critical.

    There are over 7,000 cards across the full Nerve Centre catalogue.
  </Accordion>

  <Accordion title="Nerve Centre">
    The KPI watch tower module - the first of the six modules. The Nerve Centre shows real-time numbers, trend lines, anomaly detection, and alerts across every connected platform. It is organised as a tab bar of connectors (Website, Analytics, Ads, Shopify, BigCommerce, Stripe, and so on), with a grid of KPI cards on each tab.

    The Nerve Centre is read-only by design. When something needs attention, you click through to Vortex Mind for the diagnosis or to Actions for the fix.
  </Accordion>

  <Accordion title="Profile">
    A saved set of connectors that Ask Viq queries against. You create Profiles in Settings, Profiles. The Ask Viq Profile dropdown selects which profile is active for the current chat session, scoping every question to the connectors in that profile.

    Profiles are the multi-tenant question-isolation primitive of the AI OS - they let a marketer ask about ad spend efficiency and a finance lead ask about gross margin in the same workspace without the questions mixing.
  </Accordion>

  <Accordion title="Vortex Apps">
    The action-engines module - the fifth of the six modules. Vortex Apps is the launcher tile grid containing the seven shipped apps that do work directly on your store in a controlled, auditable way:

    | App            | Platform                 | What it does                                                              |
    | -------------- | ------------------------ | ------------------------------------------------------------------------- |
    | StagingPro     | BigCommerce              | Multi-environment sync and controlled releases with one-click rollback    |
    | RollbackPro    | BigCommerce              | Continuous automated backups with instant rollback and version tracking   |
    | Vortex Staging | Shopify                  | Safe theme versioning, preview, and migration with auditable environments |
    | Vortex Backup  | Shopify                  | Automated backups with version history and one-click restore              |
    | DryRunPro      | Adobe Commerce + Magento | Data and theme sync with approvals, Docker and cloud support              |
    | CloudHub       | Multichannel OMS         | Inventory sync, order routing, and listing management across marketplaces |
    | App Builder    | All                      | The AI-agent-powered custom app builder                                   |
  </Accordion>

  <Accordion title="Vortex Memory">
    The knowledge-base module - the sixth of the six modules. Vortex Memory has two halves:

    * **Knowledge files** - manual uploads: brand guidelines, supplier catalogues, returns policies, contracts, image style references. Supported formats include PDF, docx, xlsx, csv, images, and audio transcripts.
    * **Report archive** - auto-ingested: every Vortex Mind report run lands here automatically.

    Ask Viq cites Vortex Memory when answering questions. Vortex Mind reasons against it when producing reports. The platform gets smarter the more your team uses it because findings from previous sessions remain queryable.
  </Accordion>

  <Accordion title="Vortex Mind">
    The AI diagnostician module - the second of the six modules. When the Nerve Centre surfaces an anomaly, Vortex Mind walks the connector graph, pulls related signals from every connector that touches the metric, identifies the most likely root causes ranked by impact, and produces a named report with findings. It also generates Actions for each finding so the work is queued before you read the report.

    Vortex Mind produces seven canonical report types and four scheduled briefing cadences (Daily Morning, Weekly, Monthly, Quarterly Business Review).
  </Accordion>

  <Accordion title="Workspace">
    One tenant inside Vortex IQ. Merchants have one workspace. Agencies have one parent workspace plus one child workspace per client.

    All connectors, KPI data, audit findings, Profiles, and Ask Viq conversations live inside one workspace; data does not cross between workspaces. The workspace name is set during signup (the Company field) and is editable from Settings, Account.
  </Accordion>
</AccordionGroup>


# Vortex IQ: AI Operating System for ecommerce
Source: https://docs.vortexiq.ai/get-started/introduction

Vortex IQ is an AI OS for ecommerce - it reads signals across your entire tech stack, diagnoses issues, and ships fixes into your existing platforms.

Vortex IQ is an AI Operating System for ecommerce. The phrase "operating system" is deliberate - it is not a dashboard you log into to read numbers, not a chatbot bolted onto your store, and not a suite of point tools sharing a logo. It is a connective layer that reads every signal across your stack, reasons across that signal with AI, and ships fixes back into the platforms you already run on. The value is in the **connector graph**: the thing that knows that this Stripe payment relates to this Shopify order, which relates to this Google Ads click, which relates to this customer's lifetime value, which relates to this Klaviyo email send.

## The six modules

Vortex IQ is one product made of six modules, all sitting on a shared platform layer. They share one identity layer, one connector graph, one billing surface, one settings page, one alert system, and one audit log.

<CardGroup>
  <Card title="Nerve Centre" icon="https://mintcdn.com/vortexiq/Rr6z2ok5QdLjE3bQ/icons/nerve.svg?fit=max&auto=format&n=Rr6z2ok5QdLjE3bQ&q=85&s=39f474e11136e369992e3d4d14c66dbf" href="/nerve-centre">
    The live KPI watch tower. Real-time numbers, trend lines, anomaly detection, and alerts across every connected platform. The dashboard you check first thing in the morning.
  </Card>

  <Card title="Vortex Mind" icon="https://mintcdn.com/vortexiq/Rr6z2ok5QdLjE3bQ/icons/mind.svg?fit=max&auto=format&n=Rr6z2ok5QdLjE3bQ&q=85&s=9fcdf9cdb1941f2c299734ded0aaecbc" href="/vortex-mind">
    The AI diagnostician. Reads anomalies from the Nerve Centre, walks the connector graph, identifies root causes, and produces named reports with ranked findings.
  </Card>

  <Card title="Ask Viq" icon="https://mintcdn.com/vortexiq/Rr6z2ok5QdLjE3bQ/icons/ask-viq.svg?fit=max&auto=format&n=Rr6z2ok5QdLjE3bQ&q=85&s=85ae9d4b40ab55b75820b0e486d36249" href="/ask-viq">
    The conversational layer. Ask plain-English questions and get charted answers back, scoped to a saved Profile of connectors relevant to your role.
  </Card>

  <Card title="Vortex AgentVortex Agents" icon="https://mintcdn.com/vortexiq/Rr6z2ok5QdLjE3bQ/icons/agent-hub.svg?fit=max&auto=format&n=Rr6z2ok5QdLjE3bQ&q=85&s=705ed685defaec4519c71aca5a206c04" href="/actions">
    The execution layer. Agents surface findings, rank them by revenue, and resolve them with staging-first, approval-gated fixes that are reversible by default with one-click rollbackexecution layer. Agents surface findings, rank them by revenue, and resolve them with staging-first, approval-gated fixes that are reversible by default with one-click rollback.
  </Card>

  <Card title="Vortex Apps" icon="https://mintcdn.com/vortexiq/Rr6z2ok5QdLjE3bQ/icons/apps.svg?fit=max&auto=format&n=Rr6z2ok5QdLjE3bQ&q=85&s=aeb8a81eb854d2d1de5c34374e855722" href="/vortex-apps">
    The action engines. Seven apps (StagingPro, RollbackPro, Vortex Staging, Vortex Backup, DryRunPro, CloudHub, App Builder) that do work directly on your store in a controlled, auditable way.
  </Card>

  <Card title="Vortex Memory" icon="https://mintcdn.com/vortexiq/Rr6z2ok5QdLjE3bQ/icons/vortex-memory.svg?fit=max&auto=format&n=Rr6z2ok5QdLjE3bQ&q=85&s=2b6c8a85abbef8c1363b93d73647d94a" href="/vortex-memory">
    The knowledge layer. Manual uploads (brand guidelines, supplier catalogues, policies) plus the auto-archived Vortex Mind report runs, all queryable through Ask Viq.
  </Card>
</CardGroup>

## Connectors

The connector graph is what makes the six modules more than the sum of their parts. Vortex IQ connects 240+ data sources across commerce, marketplaces, ads, payments, analytics, logistics, support and more.

<CardGroup>
  <Card title="Browse all connectors" icon="plug" href="/integrations/connector-catalogue">
    The full catalogue, grouped into the same categories you see in Settings → Connected Sources. Each connector links to its live KPI cards.
  </Card>
</CardGroup>

## Connectors

The connector graph is what makes the six modules more than the sum of their parts. Vortex IQ connects 240+ data sources across commerce, marketplaces, ads, payments, analytics, logistics, support and more.

<CardGroup>
  <Card title="Browse all connectors" icon="plug" href="/integrations/connector-catalogue">
    The full catalogue, grouped into the same categories you see in Settings → Connected Sources. Each connector links to its live KPI cards.
  </Card>
</CardGroup>

## How it works: the connector graph

The connector graph is the architectural reason Vortex IQ is an OS rather than a stack of tools. Every feature - KPI cards, root-cause diagnostics, conversational queries, audits, fixes - is a query against the same graph.

Here is how a typical signal flows through the system:

1. **The Nerve Centre** detects an anomaly: cart abandonment is up 22% in the last four hours.
2. **Vortex Mind** runs the Checkout Conversion Failure report automatically, identifies that a recent theme push slowed Largest Contentful Paint on the cart page from 1.8s to 4.6s.
3. **Vortex Mind** generates an Action: *Roll back the cart-page theme change*.
4. **Actions** surfaces the new card on the Kanban board.
5. **Vortex Apps** executes the rollback when you approve it.
6. **Ask Viq** can answer "what just happened to my cart?" from any of these surfaces, citing the report from **Vortex Memory**.

That is one signal becoming a diagnosis becoming a fix in three clicks across four modules, without a developer, without a CSV export, and without a Slack thread.

<Info>
  Vortex IQ connects to **over 200 integrations** across the ecommerce stack - commerce platforms, payment gateways, ad platforms, analytics tools, fulfilment providers, monitoring stacks, and more. The full catalogue is searchable from Settings, Connected Sources.
</Info>

## Two account types

At signup you choose one of two account types. Both use the same six modules; the differences are scoped to identity, billing, and workspace structure.

<CardGroup>
  <Card title="Merchant account" icon="store">
    Built for brand owners and in-house ecommerce teams running one storefront. One workspace, one tenant, one billing relationship.
  </Card>

  <Card title="Agency account" icon="building-2">
    Built for agencies and partners managing multiple client storefronts. One parent agency workspace plus one child workspace per client, with shared identity and shared billing. Includes a workspace switcher to jump between clients without re-signing in.
  </Card>
</CardGroup>

## What Vortex IQ is not

The clearest way to understand what Vortex IQ is, is to be precise about what it is not.

<AccordionGroup>
  <Accordion title="It is not a dashboard">
    Dashboards are passive. They display numbers you have to interpret. They do not run diagnostics, generate work, or act on your store.

    Vortex IQ has a dashboard layer (the Nerve Centre), but the dashboard is the entry point, not the product. The product runs work behind the dashboard: anomaly detection, root-cause diagnosis, action generation, and execution through Vortex Apps.
  </Accordion>

  <Accordion title="It is not a chatbot">
    Chatbots are language-only. They sit on top of an LLM and answer general-purpose questions. They do not know your store data, they do not have a connector graph behind them, and they do not produce structured findings or generate Actions.

    Ask Viq is the conversational surface inside Vortex IQ, but it queries the live connector graph - the same Nerve Centre signals, Vortex Mind diagnoses, and Vortex Memory archive that every other module uses. The chat is a UI choice, not the value.
  </Accordion>

  <Accordion title="It is not a SaaS suite">
    A SaaS suite is a marketing label for several tools sharing a parent brand. The data does not flow between them at runtime; you copy-paste between tabs. Each tool has its own admin, its own user model, its own pricing.

    Vortex IQ has six modules, but they are not six tools. A finding generated in Vortex Mind appears as a card on the Actions Kanban board because they read the same backing store, not because there is an integration between two products. The connections are pre-wired and run continuously.
  </Accordion>
</AccordionGroup>

## The agentic loop

Vortex IQ is an AI agentic OS. The agentic part means three things:

* **Reasoning over signal.** When the Nerve Centre fires an anomaly, Vortex Mind reasons across the full connector graph - not just one source - to identify likely causes, weighted by impact.
* **Action proposal.** Findings turn into Actions automatically. You do not have to translate a diagnostic insight into a Jira ticket; the Action card is created and surfaces with the recommended fix.
* **Execution.** Approved Actions execute through Vortex Apps - a theme rollback, a bulk content rewrite, a backup restore, a marketplace listing update - in a controlled, auditable way through the relevant app.

The agentic loop is: **signal → diagnosis → action proposal → human approval → execution**. You are in the loop at the approval step for any high-impact action; the OS does the rest.

## Next steps

<CardGroup>
  <Card title="Quick Start" icon="rocket" href="/get-started/quickstart">
    Sign up, connect your first source, and review your first findings in five minutes.
  </Card>

  <Card title="Glossary" icon="book-open" href="/get-started/glossary">
    Definitions for every Vortex IQ product term in one place.
  </Card>
</CardGroup>


# Get started with Vortex IQ in five minutes
Source: https://docs.vortexiq.ai/get-started/quickstart

Sign up, connect your first source, run your first query on Ask Viq, and review live findings on the Nerve Centre - no developer, no credit card required.

The promise on the signup page is "looking at audit findings on your own store inside a few minutes." This page is the end-to-end walkthrough for that promise. You will sign up, connect your commerce platform, watch the first audit run, and review your first findings on the Kanban board - all without writing a line of code or configuring a rule.

## Before you begin

Vortex IQ runs entirely in your browser. You do not need to install anything. Check that you have:

* A modern browser (Chrome, Edge, Firefox, Safari 16+, Brave, or Arc)
* Your store admin credentials for your commerce platform (Shopify, BigCommerce, or Adobe Commerce)
* A work email address

<Note>
  Pop-up blockers can interrupt the OAuth connector flow. Allow pop-ups for `app.vortexiq.ai` before you start to avoid a silent failure mid-step.
</Note>

## Step 1: Sign up

Choose the account type that matches how you work. Both types use the same six modules; the difference is workspace structure and billing.

<Tabs>
  <Tab title="Merchant signup">
    A merchant account is for brand owners and in-house ecommerce teams running one storefront.

    <Steps>
      <Step title="Go to the signup page">
        Navigate to `app.vortexiq.ai` and click **Get started**.
      </Step>

      <Step title="Choose your account type">
        Select **Merchant** when prompted. This creates one workspace scoped to a single storefront.
      </Step>

      <Step title="Sign in with Google or a magic link">
        You have two options:

        * **Continue with Google**, one click, your email is verified immediately by Google.
        * **Magic link**, enter your work email, receive a single-use link, click it to verify and enter your workspace.

        If the magic link does not arrive, check spam and promotional folders. The sender domain is `vortexiq.ai`.
      </Step>

      <Step title="Sign in with Google or a magic link">
        You have two options:

        * **Continue with Google** - one click, your email is verified immediately by Google.
        * **Magic link** - enter your work email, receive a single-use link, click it to verify and enter your workspace.

        If the magic link does not arrive, check spam and promotional folders. The sender domain is `vortexiq.ai`.
      </Step>

      <Step title="Enter your company name">
        This becomes your workspace name. It is editable later from Settings, Account.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Agency signup">
    An agency account is for agencies and partners managing multiple client storefronts from one place.

    <Steps>
      <Step title="Go to the signup page">
        Navigate to `app.vortexiq.ai` and click **Get started**.
      </Step>

      <Step title="Choose your account type">
        Select **Agency** when prompted. This creates a parent agency workspace plus the ability to add client child workspaces.
      </Step>

      <Step title="Sign in with Google or a magic link">
        You have two options:

        * **Continue with Google**, one click, your email is verified immediately by Google.
        * **Magic link**, enter your work email, receive a single-use link, click it to verify and enter your workspace.
      </Step>

      <Step title="Sign in with Google or a magic link">
        You have two options:

        * **Continue with Google** - one click, your email is verified immediately by Google.
        * **Magic link** - enter your work email, receive a single-use link, click it to verify and enter your workspace.
      </Step>

      <Step title="Enter your agency name">
        This becomes your parent workspace name. Client workspaces are added separately after signup from the workspace switcher.
      </Step>
    </Steps>

    <Info>
      Once inside, use the workspace switcher in the top-right of the dashboard to jump between client workspaces without re-signing in. The switcher only appears for agency accounts with active client partnerships.
    </Info>
  </Tab>
</Tabs>

## Step 2: Tell Vortex IQ what you care about

The first onboarding screen is **Tell us your interests**. Tick the areas that match your role:

| Area               | What it surfaces                               |
| ------------------ | ---------------------------------------------- |
| Sales              | Revenue, order volume, AOV, conversion         |
| Marketing          | Ad spend, email performance, traffic sources   |
| Inventory          | Stockouts, overstocks, SKU health              |
| Customer behaviour | Cart abandonment, retention, LTV               |
| Operations         | Fulfilment, helpdesk, refund rates             |
| Analytics          | Core Web Vitals, GA4 metrics, site performance |

Select as many as you like, or click **Select all** to tick every box at once. This seeds which agents and reports get surfaced first on your Nerve Centre. You can change it later from Settings.

## Step 3: Connect your first source

This is the highest-value step - the moment you wire your store, Vortex IQ begins building the connector graph.

<Tabs>
  <Tab title="Shopify">
    <Steps>
      <Step title="Click the Shopify tile">
        On the onboarding connector screen, click **Shopify**.
      </Step>

      <Step title="Enter your store URL">
        Type your `.myshopify.com` store URL, for example, `acmeoutdoors.myshopify.com`.
      </Step>

      <Step title="Enter your store URL">
        Type your `.myshopify.com` store URL - for example, `acmeoutdoors.myshopify.com`.
      </Step>

      <Step title="Click Connect">
        A pop-up opens at your Shopify admin. Sign in with your Shopify credentials, or your existing Shopify session takes you straight to the consent screen.
      </Step>

      <Step title="Review and approve the read scopes">
        Vortex IQ requests read access to: products, orders, customers, inventory, and analytics. No write scopes are requested at the connector step, write scopes are only requested when you deploy an Action that needs them.
      </Step>

      <Step title="Review and approve the read scopes">
        Vortex IQ requests read access to: products, orders, customers, inventory, and analytics. No write scopes are requested at the connector step - write scopes are only requested when you deploy an Action that needs them.
      </Step>

      <Step title="Click Install app">
        Shopify uses "install app" language for OAuth grants. Click it. The pop-up closes and you land back in Vortex IQ with a green **Connected** badge on the Shopify tile.
      </Step>
    </Steps>
  </Tab>

  <Tab title="BigCommerce">
    <Steps>
      <Step title="Click the BigCommerce tile">
        On the onboarding connector screen, click **BigCommerce**.
      </Step>

      <Step title="Enter your store hash">
        Enter the alphanumeric string from your BigCommerce admin URL, for example, `stores/abc123def`.
      </Step>

      <Step title="Enter your store hash">
        Enter the alphanumeric string from your BigCommerce admin URL - for example, `stores/abc123def`.
      </Step>

      <Step title="Click Connect">
        The BigCommerce OAuth flow runs. If you are already signed into your BigCommerce admin, it takes you straight to the consent screen.
      </Step>

      <Step title="Approve the read scopes">
        Approve read access to: products, orders, customers, and inventory. Then land back in Vortex IQ with the green Connected badge.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Adobe Commerce">
    Adobe Commerce uses a credentials form rather than an OAuth pop-up.

    <Steps>
      <Step title="Click the Adobe Commerce tile">
        On the onboarding connector screen, click **Adobe Commerce**.
      </Step>

      <Step title="Enter your API base URL">
        Enter the REST API base URL for your store, for example, `https://shop.acmeoutdoors.com/rest/V1/`.
      </Step>

      <Step title="Enter your API base URL">
        Enter the REST API base URL for your store - for example, `https://shop.acmeoutdoors.com/rest/V1/`.
      </Step>

      <Step title="Enter your admin token">
        Generate a token in your Magento admin under System, Integrations, then paste it into the form.
      </Step>

      <Step title="Click Connect">
        Vortex IQ verifies the credentials and saves them encrypted. You land back on the connector screen with the Connected badge.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Other platforms">
    Shopify, BigCommerce, and Adobe Commerce cover roughly 80% of merchant signups, but Vortex IQ connects to over 200 integrations in total.

    <Steps>
      <Step title="Click More or use the search field">
        On the onboarding connector screen, click the **More** tile or use the **Find a connector** search field.
      </Step>

      <Step title="Find your platform">
        Search for your platform, NetSuite, Salesforce Commerce Cloud, WooCommerce, and many more are available, and select it.
      </Step>

      <Step title="Find your platform">
        Search for your platform - NetSuite, Salesforce Commerce Cloud, WooCommerce, and many more are available - and select it.
      </Step>

      <Step title="Follow the connector-specific flow">
        Each connector has its own OAuth or credentials form. Follow the prompts shown on screen.
      </Step>
    </Steps>
  </Tab>
</Tabs>

<Warning>
  If the OAuth pop-up does not open, your browser's pop-up blocker is likely blocking it. Allow pop-ups for `app.vortexiq.ai`, then click **Connect** again.
</Warning>

## Step 4: Watch the first data pull

The moment your connector lands in the connected state, Vortex IQ starts pulling data. You can see the pull progress on the Settings, Connected Sources page: products imported, orders imported, customers imported, inventory snapshotted.

For Shopify and BigCommerce, the initial pull typically takes 5 to 15 minutes for a mid-size store. You do not need to wait - the Nerve Centre tab for your connected platform appears immediately and starts populating cards as data arrives, and the Store Audit kicks off automatically in parallel.

## Step 5: Review your first findings

Open **Actions** in the sidebar, then go to **Store Audit**, then **Latest Findings**. The Store Audit runs a 50+ check sweep across SEO, AI search readiness, Core Web Vitals performance, checkout conversion, inventory, and catalogue health. Findings begin landing on the Kanban board in real time while the audit is still running.

A typical first-run findings list looks like this:

| Severity | Example finding                                   | Source                           |
| -------- | ------------------------------------------------- | -------------------------------- |
| Critical | 14 product pages missing meta descriptions        | Audit, SEO                       |
| Critical | Largest Contentful Paint 4.6s on cart page        | Audit, Performance               |
| High     | 23 SKUs out of stock with active Google Ads spend | Cross-platform                   |
| High     | Cart abandonment up 18% week-on-week              | Vortex Mind, Checkout Conversion |
| Medium   | 42 underused 301 redirects                        | Audit, SEO                       |
| Medium   | 8 product images larger than 500KB                | Audit, Performance               |

Click any finding to open the detail panel: what it is, why it matters, the recommended fix, and the **Run Action** button to ship the fix.

## Step 6: Run your first query on Ask Viq

Ask Viq is the conversational layer of Vortex IQ. Open **Ask Viq** in the sidebar.

<Steps>
  <Step title="Select a Profile">
    Use the **Profile** dropdown at the top of the Ask Viq panel. A Profile is a saved set of connectors (for example, *Marketing profile* = GA4 + Google Ads + Klaviyo + Shopify). If you have just connected your first source, a default profile is available. Select it.
  </Step>

  <Step title="Type your first question">
    Ask something grounded in your connected data, for example:

    * *"How did revenue compare last week versus the week before?"*
    * *"Which products had the biggest drop in conversion this month?"*
    * *"What is the top reason customers are abandoning checkout right now?"*

    Ask Viq reads the live connector graph, the same data the Nerve Centre and Vortex Mind use, so answers are specific to your store, not generic LLM responses.
  </Step>

  <Step title="Type your first question">
    Ask something grounded in your connected data - for example:

    * *"How did revenue compare last week versus the week before?"*
    * *"Which products had the biggest drop in conversion this month?"*
    * *"What is the top reason customers are abandoning checkout right now?"*

    Ask Viq reads the live connector graph - the same data the Nerve Centre and Vortex Mind use - so answers are specific to your store, not generic LLM responses.
  </Step>

  <Step title="Review the charted answer">
    Ask Viq returns a charted answer with the data source cited. If the answer references a Vortex Mind finding or a Vortex Memory document, those citations appear inline.
  </Step>
</Steps>

## Step 7: Ship your first fix

Go back to **Actions**, Kanban. Pick the easiest Critical finding - typically a missing meta description or a redirect cleanup - and click **Run Action**.

Depending on the finding type, the Action either:

* Generates the fix automatically and queues it for your approval (for example, AI-generated meta descriptions).
* Fires through Vortex Apps to apply the fix on your store (for example, a redirect cleanup).
* Opens a Bulk Content Edit grid where you review and confirm dozens of changes at once.

Approve the fix. Within seconds it ships to your store. You have closed the agentic loop: **signal → diagnosis → action → shipped**.

## Before your second session

<Tip>
  A few minutes of setup now makes every future session faster.
</Tip>

* **Invite a teammate.** Go to Settings, Account, Team Members, then **Invite**. They receive a magic link by email.
* **Set up an alert channel.** Go to Settings, Alerts, Notification Channels. Add Slack or Microsoft Teams if your team lives there; the default is your work email.
* **Create a Profile in Ask Viq.** Go to Settings, Profiles, Create Profile. Group the connectors that match your role so every Ask Viq session is pre-scoped.
* **Bookmark the workspace.** Most merchants check the Nerve Centre daily. Bookmark `app.vortexiq.ai` for fast access.

## Common questions

<AccordionGroup>
  <Accordion title="The audit returned no findings. What happened?">
    Either the data pull is still in progress (wait a few minutes and refresh the Latest Findings view) or your store is genuinely in good shape, which is rare - most stores have at least 5 to 10 SEO findings. Check Settings, Connected Sources for the data pull status.
  </Accordion>

  <Accordion title="My connector did not connect. What now?">
    Check that the OAuth pop-up was not blocked by your browser. Re-run the connect flow. If it fails a second time, see the connector-specific troubleshooting on the connector's documentation page or contact support.
  </Accordion>

  <Accordion title="Can I run the audit before the data pull finishes?">
    Yes. The audit runs against whatever data is currently loaded. If the pull is still in progress, the audit re-runs automatically against the full dataset once the pull completes.
  </Accordion>

  <Accordion title="What happens after the first session?">
    You move into the day-to-day operating rhythm: check the Nerve Centre in the morning, read the daily briefing in your inbox, and ship Actions through the day. The first session is the only one that feels like setup; from session two onward you are operating, not configuring.
  </Accordion>
</AccordionGroup>


# Connect Adobe Commerce to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/adobe-commerce

Connect Adobe Commerce (Magento) to Vortex IQ for B2B revenue share, AOV delta, and order KPI cards plus cross-platform alerts across your commerce stack.

Connecting Adobe Commerce (formerly Magento) to Vortex IQ gives the AI OS access to your order stream, product catalogue, customer records, and fulfilment data. Adobe Commerce is the platform of choice for mid-market and enterprise merchants with complex B2B, multi-website, or custom checkout requirements - and Vortex IQ surfaces the KPI cards that matter for that operating context, including B2B-specific metrics that simpler analytics tools miss entirely.

## What data Vortex IQ reads from Adobe Commerce

Vortex IQ connects to the Adobe Commerce REST API and ingests the following data:

<AccordionGroup>
  <Accordion title="Orders and revenue">
    * Order totals across all websites and store views configured in Adobe Commerce
    * Order state and status (new, processing, complete, closed, cancelled, holded)
    * Payment method and gateway per order
    * Shipping amounts, methods, and carrier assignments
    * Discount codes and discount amounts
    * Refunds (credit memos) and return status
    * Tax amounts and tax class per line item
    * Guest vs customer account orders
  </Accordion>

  <Accordion title="Products and inventory">
    * Product variants and configurable product options with current stock quantities
    * Product status (enabled, disabled)
    * Product type (simple, configurable, bundle, downloadable)
    * SKU, category, and attribute sets
    * Out-of-stock state per variant
  </Accordion>

  <Accordion title="B2B data (Adobe Commerce B2B edition)">
    * Company accounts and account status
    * B2B revenue share vs B2C revenue
    * B2B average order value delta vs B2C AOV
    * Account-level silence signals (companies that have stopped ordering)
  </Accordion>

  <Accordion title="Customers">
    * Customer records with email state
    * Order frequency and geography
    * Guest vs account-registered breakdown
    * Repeat purchase rate and churn signals
  </Accordion>
</AccordionGroup>

<Note>
  Adobe Commerce uses credential-based authentication. You will need an Admin API integration token generated in the Adobe Commerce Admin panel. Vortex IQ shows step-by-step instructions for generating the token inline in the connector drawer.
</Note>

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Adobe Commerce card">
    Locate the Adobe Commerce connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Generate an integration token in Adobe Commerce">
    In your Adobe Commerce Admin, go to **System → Extensions → Integrations → Add New Integration**. Set the integration name, then under **API** grant read access to: Orders, Products, Inventory, Customers, and Store. Save the integration and copy the **Access Token**.
  </Step>

  <Step title="Enter your store URL and access token">
    Enter your Adobe Commerce **Base URL** (for example, `https://store.yoursite.com`) and the **Access Token** in the Vortex IQ connector form.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the token and base URL. On success, the card flips to Connected.
  </Step>

  <Step title="Wait for the first data pull">
    Adobe Commerce KPI cards appear in Nerve Centre within 5 to 15 minutes. Full historical order backfill takes 1 to 4 hours.
  </Step>
</Steps>

<Note>
  Grant the integration **read-only** access to all required resources. Vortex IQ does not require write access to any Adobe Commerce resource. For multi-website setups, the access token covers all websites within the same Adobe Commerce installation.
</Note>

## Available KPI cards

Vortex IQ populates Nerve Centre with Adobe Commerce KPI cards across the following categories.

<CardGroup>
  <Card title="Revenue and growth" icon="chart-line">
    **Total Revenue** - Gross revenue across all websites and store views for the period, compared to the prior period. Alerts on a drop greater than 15% vs prior 30 days.

    **Revenue Over Time** - Daily revenue trend sparkline.

    **Average Order Value** - Revenue ÷ Order Count, with trend.

    **Revenue by Day of Week** - Identifies highest-revenue days for scheduling.

    **Discount % of Revenue** - Discount value as a share of gross revenue.

    **Daily Order Trends** - Daily order volume with period comparison.
  </Card>

  <Card title="B2B-specific cards" icon="building">
    **B2B Revenue Share** - B2B company-account revenue as a percentage of total Adobe Commerce revenue.

    **B2B AOV Delta** - Difference between B2B average order value and B2C AOV. Indicates customer mix changes.

    **B2B Account Silence** - Company accounts that have not placed an order within a configurable look-back window. An early churn signal for wholesale accounts.
  </Card>

  <Card title="Orders and fulfilment" icon="truck">
    **Order Count** - Total orders placed in the period.

    **Orders Over Time** - Daily order volume sparkline.

    **Order State Breakdown** - Distribution of orders across Adobe Commerce order states.

    **Unfulfilled Orders** - Orders awaiting processing or shipment.

    **Fulfilment Rate** - Share of orders fulfilled within the expected window.

    **Fulfilment Over Time** - Fulfilment rate trend.

    **Cancellation Rate** - Cancelled orders as a share of total.
  </Card>

  <Card title="Customers" icon="users">
    **Customer Count** - Total active customers.

    **New Customers** - First-time buyers in the period.

    **Repeat Rate** - Share of customers who bought more than once.

    **Guest vs Account** - Breakdown of guest checkout vs registered account orders.

    **Churn Risk** - Customers showing lapse signals.

    **Customer Segments** - Breakdown by RFM-style segment.
  </Card>

  <Card title="Refunds and returns" icon="arrow-left">
    **Refund Rate** - Credit memos as a share of orders in the period.

    **Refund Value** - Total value of credit memos issued.

    **Refunds Over Time** - Daily refund trend.

    **Return Status** - Breakdown of return requests by state.

    **Refund Spike Alert** - Fires when refund rate rises sharply.
  </Card>

  <Card title="Alerts and anomalies" icon="bell">
    **Revenue Drop Alert** - Revenue falls more than 15% vs prior period.

    **OOS Spike Alert** - Out-of-stock count rises sharply.

    **Fulfilment Delay Alert** - Fulfilment rate drops below threshold.

    **Cart Abandon Spike Alert** - Cart abandonment rate rises sharply.

    **Refund Spike Alert** - Refund rate rises above threshold.
  </Card>
</CardGroup>

### Cross-platform cards

When you connect ad platforms or other data sources alongside Adobe Commerce, Vortex IQ unlocks additional cross-platform cards:

| Card                                  | What it shows                                                  |
| ------------------------------------- | -------------------------------------------------------------- |
| Active Ads on Out-of-Stock SKUs       | Ad spend on OOS variants - pause candidates                    |
| Revenue at Risk from active incidents | Live revenue impact when a monitoring incident is open         |
| Catalogue Drift vs Amazon             | Adobe Commerce SKUs active on Amazon but OOS on the main store |
| Email Revenue Share                   | Email-attributed revenue as a share of Adobe Commerce total    |

## Troubleshooting

<AccordionGroup>
  <Accordion title="API token authentication fails">
    Check that the integration token was generated with the correct resource permissions (Orders, Products, Inventory, Customers, Store - all read-only). Also verify that the Base URL does not have a trailing slash and matches the admin-panel domain exactly. If authentication still fails after re-checking both, regenerate the integration token in Adobe Commerce Admin and try again.
  </Accordion>

  <Accordion title="B2B cards show no data">
    B2B-specific cards (B2B Revenue Share, B2B AOV Delta, B2B Account Silence) require Adobe Commerce B2B edition and at least one active company account. If your installation is the standard Adobe Commerce edition without the B2B module, these cards will remain empty.
  </Accordion>

  <Accordion title="Revenue in Vortex IQ differs from Adobe Commerce reports">
    Adobe Commerce reports typically use the order created date in the configured locale timezone. Vortex IQ uses UTC. Boundary-day differences are expected, particularly for stores in UTC-offset timezones. For 30-day windows these differences average out. Also check whether your Adobe Commerce report is showing net revenue (post-credit memo) rather than gross - Vortex IQ Total Revenue is gross of credit memos.
  </Accordion>

  <Accordion title="Multi-website setup - only one website's data is showing">
    The Vortex IQ Adobe Commerce connector reads all websites within a single Adobe Commerce installation using the Admin API. Ensure the integration token has access to Global scope (not restricted to a specific website). For separate Adobe Commerce installations, each requires its own connector connection.
  </Accordion>
</AccordionGroup>


# Connect AdRoll to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/adroll

Connect AdRoll to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting AdRoll to Vortex IQ gives the AI OS a live read on your AdRoll data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from AdRoll

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the AdRoll card">
    Locate the AdRoll connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with AdRoll">
    You are redirected to AdRoll's own authorisation page (`https://services.adroll.com/auth/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `read`, `write`.
  </Step>

  <Step title="Return to Vortex IQ">
    AdRoll redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the AdRoll API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your AdRoll data. See the [AdRoll KPI card reference](/nerve-centre/kpi-cards/adroll) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the AdRoll developer console for typos or trailing whitespace. If a scope or permission is missing, AdRoll will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Amazon Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/amazon-ads

Connect Amazon Ads to Vortex IQ for 96 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Amazon Ads to Vortex IQ gives the AI OS a live read on your Amazon Ads data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Amazon Ads

* **Campaign**
* **AdGroup**
* **ProductAd**
* **Keyword**
* **SearchTerm**
* **ReportRow**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Amazon Ads card">
    Locate the Amazon Ads connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Amazon Ads">
    You are redirected to Amazon Ads's own authorisation page (`https://www.amazon.com/ap/oa`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `advertising::campaign_management`, `advertising::reporting`.
  </Step>

  <Step title="Return to Vortex IQ">
    Amazon Ads redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Amazon Ads API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **96** Nerve Centre cards from your Amazon Ads data. See the [Amazon Ads KPI card reference](/nerve-centre/kpi-cards/amazon-ads) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Amazon Ads developer console for typos or trailing whitespace. If a scope or permission is missing, Amazon Ads will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Big Cartel to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/bigcartel

Connect Big Cartel to Vortex IQ for 32 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Big Cartel to Vortex IQ gives the AI OS a live read on your Big Cartel data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Big Cartel

* **Product**
* **Order**
* **Customer**
* **Account**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Big Cartel card">
    Locate the Big Cartel connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Big Cartel">
    You are redirected to Big Cartel's own authorisation page (`https://api.bigcartel.com/oauth/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `read`.
  </Step>

  <Step title="Return to Vortex IQ">
    Big Cartel redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Big Cartel API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **32** Nerve Centre cards from your Big Cartel data. See the [Big Cartel KPI card reference](/nerve-centre/kpi-cards/bigcartel) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Big Cartel developer console for typos or trailing whitespace. If a scope or permission is missing, Big Cartel will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect BigCommerce to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/bigcommerce

Connect BigCommerce to Vortex IQ for 115 KPI cards - channel revenue, orders, inventory, and customer data - plus cross-platform Vortex Mind diagnostics.

Connecting BigCommerce to Vortex IQ gives the AI OS a live read on your orders, products, customers, and revenue across every sales channel your store operates. BigCommerce's multi-channel architecture means Vortex IQ can segment KPI cards by channel ID, giving you per-channel revenue, conversion rate, fulfilment, and refund breakdowns that most analytics tools flatten into a single number.

## What data Vortex IQ reads from BigCommerce

Vortex IQ connects to the BigCommerce API v2 and v3 and ingests the following data:

<AccordionGroup>
  <Accordion title="Orders and revenue">
    * Order totals across all channels (Online Store, POS, marketplace channels, headless storefronts)
    * Order status, payment status, and fulfilment status per order
    * Discount codes and coupon amounts
    * Refunds and returns
    * Shipping methods and shipping revenue
    * Tax amounts and gateway per order
    * Failed and incomplete orders (declined payments)
  </Accordion>

  <Accordion title="Products and inventory">
    * Product variants with current stock levels
    * Product margin and COGS (where configured in BigCommerce)
    * Product type, brand, and category
    * SKU and barcode per variant
    * Channel-specific product listings and inventory splits
  </Accordion>

  <Accordion title="Customers">
    * Customer records with email state
    * Guest vs registered customer breakdown
    * Order frequency and geography per customer
    * Repeat purchase signals and churn risk indicators
  </Accordion>
</AccordionGroup>

<Note>
  BigCommerce uses credential-based authentication (API key + Store Hash) rather than OAuth. Vortex IQ shows step-by-step instructions for generating your API key inline in the connector drawer.
</Note>

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the BigCommerce card">
    Locate the BigCommerce connector card and click **+ Connect**. The connector drawer opens with a credential form rather than an OAuth button.
  </Step>

  <Step title="Generate your API credentials in BigCommerce">
    Follow the inline instructions in the drawer to generate an API account in BigCommerce: go to **Advanced Settings → API Accounts → Create API Account (V2/V3 API Token)**. Set the OAuth Scopes to at least: Orders (read-only), Products (read-only), Customers (read-only), Store Information (read-only).
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Copy the **Client ID**, **Client Secret**, and **Access Token** from BigCommerce and paste them into the corresponding fields in Vortex IQ. Also enter your **Store Hash** (found in your BigCommerce store URL: `store-{hash}.mybigcommerce.com`).
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials. On success, the card flips to Connected. On failure, an inline error identifies the issue (typically a missing scope or typo in the store hash).
  </Step>

  <Step title="Wait for the first data pull">
    BigCommerce KPI cards appear in Nerve Centre within 5 to 15 minutes. Full historical order backfill takes 1 to 4 hours.
  </Step>
</Steps>

<Note>
  Set all API scopes to **read-only**. Vortex IQ does not require write access to any BigCommerce resource.
</Note>

## Available KPI cards

Vortex IQ populates 115 Nerve Centre cards from your BigCommerce data, including a set of channel-specific cards that are unique to BigCommerce's multi-channel architecture.

<CardGroup>
  <Card title="Revenue and growth" icon="chart-line">
    **Total Revenue** - Gross revenue across all channels for the period, compared to prior period. Alerts on a drop greater than 15% vs prior 30 days.

    **Revenue Over Time** - Daily revenue trend sparkline.

    **Average Order Value** - Revenue ÷ Order Count.

    **Revenue by Channel** - Per-channel revenue breakdown by channel ID.

    **Revenue by Currency** - Multi-currency revenue breakdown.

    **Revenue by Device** - Desktop vs mobile revenue split.

    **Revenue by Hour** - Intra-day revenue pattern.
  </Card>

  <Card title="Channel performance" icon="layers">
    **Channel Revenue Mix** - Share of total revenue by channel.

    **Channel Revenue Trend** - Per-channel daily revenue trend.

    **Channel AOV** - Average order value broken out by channel.

    **Channel Conversion Rate** - Conversion rate per channel.

    **Channel Fulfilment Rate** - Fulfilment performance per channel.

    **Channel Refund Rate** - Refund rate per channel.

    **Channel OOS per Channel** - Out-of-stock variants by channel.

    **Channel Repeat Rate** - Repeat purchase rate by channel.
  </Card>

  <Card title="Orders and payments" icon="credit-card">
    **Order Count** - Total orders placed.

    **Orders by Channel ID** - Volume per BigCommerce channel.

    **Failed Orders Count** - Orders that failed due to payment decline.

    **Failed Orders Value** - Revenue value of failed orders.

    **Decline Rate by Payment Method** - Which payment methods are declining most.

    **Incomplete Rate** - Orders started but not completed.

    **Unrecovered Value** - Value of failed orders not recovered.
  </Card>

  <Card title="Inventory and products" icon="warehouse">
    **Products with Zero/Negative Stock** - Live count of OOS variants. Alerts when any active variant hits zero.

    **Stock vs Sales** - Variants approaching stockout.

    **Inventory Distribution** - Stock level distribution across variants.

    **Revenue by Brand** - Revenue broken out by product brand.

    **Revenue by Category** - Revenue broken out by product category.

    **Product Margin** - Margin per product where COGS is configured.

    **Top SKUs by Revenue** - Highest-revenue variants in the period.
  </Card>

  <Card title="Customers" icon="users">
    **Customer Count** - Total active customers.

    **New Customers** - First-time buyers in the period.

    **Repeat Rate** - Share of customers who bought more than once.

    **Guest vs Registered** - Breakdown of guest checkout vs account orders.

    **Churn Risk** - Customers showing lapse signals.

    **Top Customers** - Highest-value customers by lifetime spend.
  </Card>

  <Card title="Alerts and health" icon="bell">
    **Revenue Drop Alert** - Revenue falls more than 15% vs prior period.

    **OOS Spike Alert** - Out-of-stock count rises sharply.

    **Refund Rate Spike Alert** - Refund rate rises sharply.

    **Fulfilment Delay Alert** - Fulfilment rate drops below threshold.

    **Abandoned Cart Spike Alert** - Cart abandonment rate rises sharply.

    **Channel Revenue Drop Alert** - Revenue drops sharply on a specific channel.

    **Store Health Score** - Composite 0-100 score blending revenue trend, fulfilment rate, refund rate, and OOS count.
  </Card>
</CardGroup>

### Cross-platform cards

When you also connect ad platforms or other data sources alongside BigCommerce, Vortex IQ unlocks additional cross-platform cards:

| Card                                  | What it shows                                                    |
| ------------------------------------- | ---------------------------------------------------------------- |
| Active Ads on Out-of-Stock SKUs       | Ad spend on OOS variants - pause candidates                      |
| Revenue at Risk from active incidents | Live revenue impact when a monitoring incident is open           |
| Catalogue Drift vs Amazon             | BigCommerce SKUs active on Amazon but OOS on the main store      |
| Checkout Funnel Drop                  | Step-by-step checkout funnel drop-off correlated with ad traffic |
| Paid Traffic Waste                    | Ad spend landing on low-converting or OOS pages                  |
| Klaviyo Email Revenue Share           | Email-attributed revenue as a share of BigCommerce total         |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Check the following in order: (1) trailing whitespace on any pasted credential - re-copy and paste again; (2) the Store Hash matches the hash in your BigCommerce admin URL exactly; (3) the API account has the required read-only scopes for Orders, Products, Customers, and Store Information. If all three are correct and verification still fails, regenerate the Access Token in BigCommerce and retry.
  </Accordion>

  <Accordion title="Channel-specific cards are empty">
    BigCommerce channel cards require that your store has multiple channels configured. If you operate a single storefront, channel-breakdown cards will show data only for channel ID 1 (the default storefront). Cards that show "no data" for additional channels indicate those channels are not yet active in your BigCommerce account.
  </Accordion>

  <Accordion title="Revenue in Vortex IQ differs from BigCommerce analytics">
    BigCommerce Analytics uses the order creation date in your store's local timezone. Vortex IQ uses UTC. On boundary days, orders near midnight may fall on different dates in each system. The difference is typically less than one day's revenue at the boundary and averages out over a 30-day window.
  </Accordion>

  <Accordion title="Declined and failed orders are missing">
    Failed orders are captured via the BigCommerce Orders API with `status_id` values for incomplete and failed states. If declined orders are not appearing in the relevant Nerve Centre cards, check that the API account was granted access to the Orders scope and that the connection was established after the orders were created.
  </Accordion>
</AccordionGroup>


# Connect Vortex IQ to Claude
Source: https://docs.vortexiq.ai/integrations/claude-mcp/connect-claude

Step-by-step guide to adding the Vortex IQ MCP connector in Claude web, Claude desktop and Claude Code, with verification prompts and troubleshooting.

Adding the Vortex IQ connector to Claude takes under two minutes. You need a [Vortex IQ account](https://app.vortexiq.ai), the connector signs in with your existing Vortex IQ (Google) login and only ever returns data your account can already see.

## Claude web and desktop

<Steps>
  <Step title="Open Connectors">
    In Claude, go to **Settings → Connectors** and click **Add custom connector**.
  </Step>

  <Step title="Enter the server URL">
    Paste `https://app.vortexiq.ai/mcp` and confirm.
  </Step>

  <Step title="Sign in and allow">
    A Vortex IQ consent screen opens. Sign in with your existing Vortex IQ (Google) login and click **Allow**.
  </Step>

  <Step title="Start asking">
    The Vortex IQ tools appear in Claude. Try *"List my recent store audits."*
  </Step>
</Steps>

<Tip>
  If Vortex IQ is listed in the Claude connector directory, you can add it from there with one click instead of entering the URL manually, the sign-in flow is the same.
</Tip>

## Claude Code

Add the connector as a remote MCP server from your terminal:

```bash theme={null}
claude mcp add --transport http vortexiq https://app.vortexiq.ai/mcp
```

Then run `/mcp` inside a Claude Code session to complete the OAuth sign-in in your browser.

## Other MCP clients

Any MCP client that supports Streamable HTTP and OAuth 2.1 with PKCE can connect. Endpoints are machine-discoverable:

```
GET https://app.vortexiq.ai/.well-known/oauth-authorization-server
GET https://app.vortexiq.ai/.well-known/oauth-protected-resource
```

The full flow, dynamic client registration, authorize, token exchange and refresh, is documented in the [OAuth developer guide](/integrations/claude-mcp/oauth).

## Verify it works

Each of these prompts exercises a different part of the connector:

1. **"List my recent store audits."**, returns audit runs with id, guid, integration, health score and completion time. Follow up with *"Show the findings report for integration `<id>`."*
2. **"What KPIs are available, and show the 30-day KPIs for `<integration>`."**, returns the KPI library plus KPI cards and trends for that integration.
3. **"List my active Nerve Centre alerts and give me the 24h incident summary."**, returns active alerts plus summary counts.
4. **"Show my Brand DNA voice and tone guidelines."**, returns your Brand DNA profile.
5. **"Show my Kanban health-fix backlog."**, returns the board state per column.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Claude says authentication failed or the tools disappeared">
    Access tokens expire after one hour and refresh automatically; if refresh fails (for example after a long idle period), remove and re-add the connector, or re-run the sign-in from **Settings → Connectors**. In Claude Code, run `/mcp` and re-authenticate.
  </Accordion>

  <Accordion title="A tool returns no data">
    The connector only returns data your Vortex IQ account can access. Check that your role has access to the relevant module (Store Audit, Nerve Centre, Brand DNA and so on) in the Vortex IQ dashboard, and that the organisation actually has data there, for example, at least one completed audit run.
  </Accordion>

  <Accordion title="A list looks truncated">
    Some list results are capped at the first 50 items (roughly 40k characters) to stay model-friendly. Ask a narrower question or request a specific id to drill into full detail.
  </Accordion>
</AccordionGroup>

## Support

Questions or issues? Email [support@vortexiq.ai](mailto:support@vortexiq.ai).


# Vortex IQ MCP OAuth: connect any client with OAuth 2.1 + PKCE
Source: https://docs.vortexiq.ai/integrations/claude-mcp/oauth

The full OAuth 2.1 Authorization Code + PKCE flow for authenticating any MCP client or agent against Vortex IQ, registration, authorize, token exchange, refresh and gotchas.

This guide is for developers connecting a custom MCP client or agent to Vortex IQ, the same flow Claude connectors use under the hood. If you just want to use the connector in Claude, follow the [connection guide](/integrations/claude-mcp/connect-claude) instead.

The flow is standard **OAuth 2.1 Authorization Code + PKCE (S256)** with a **public client**, no client secret. Access tokens are audience-bound (RFC 8707) to `https://app.vortexiq.ai`.

|                          |                                             |
| ------------------------ | ------------------------------------------- |
| **Base URL**             | `https://app.vortexiq.ai`                   |
| **MCP endpoint**         | `POST /mcp` (Streamable HTTP, JSON-RPC 2.0) |
| **Register client**      | `POST /oauth/mcp/register`                  |
| **Authorize**            | `GET /oauth/mcp/authorize` (browser)        |
| **Token / refresh**      | `POST /oauth/mcp/token`                     |
| **Whoami / token check** | `GET /oauth/mcp/userinfo`                   |

## Discovery

Everything below is machine-discoverable, MCP clients that support discovery need nothing more than the server URL:

```
GET https://app.vortexiq.ai/.well-known/oauth-authorization-server
GET https://app.vortexiq.ai/.well-known/oauth-protected-resource
```

## The flow

<Steps>
  <Step title="Register a client (one time)">
    Dynamic Client Registration (RFC 7591) is public and self-service. Store the returned `client_id`, there is no secret.

    ```bash theme={null}
    curl -X POST https://app.vortexiq.ai/oauth/mcp/register \
      -H "Content-Type: application/json" \
      -d '{
            "redirect_uris": ["https://YOUR-APP/callback"],
            "client_name": "My Agent",
            "token_endpoint_auth_method": "none"
          }'
    ```

    Returns `{"client_id":"mcp_xxx", ...}`. `redirect_uris` must be **https** (`localhost` allowed for development). Only public clients (`"token_endpoint_auth_method": "none"`) are accepted.
  </Step>

  <Step title="Generate a PKCE verifier and challenge (per authorization)">
    ```
    code_verifier  = random 43-128 char string
    code_challenge = BASE64URL( SHA256(code_verifier) )   // no padding
    ```

    Keep `code_verifier` in memory tied to the `state`. **S256 is mandatory**, `plain` is rejected.
  </Step>

  <Step title="Send the user to authorize">
    Open in a browser:

    ```
    GET https://app.vortexiq.ai/oauth/mcp/authorize
          ?response_type=code
          &client_id=<CLIENT_ID>
          &redirect_uri=<REGISTERED_URI>
          &state=<RANDOM>
          &code_challenge=<CHALLENGE>
          &code_challenge_method=S256
          &resource=https://app.vortexiq.ai
    ```

    The user signs in with their existing Vortex IQ (Google) login and clicks **Allow**. Vortex IQ redirects back to `<REDIRECT_URI>?code=<AUTH_CODE>&state=<RANDOM>`. Verify `state` matches, the `code` is single-use and expires in about 5 minutes.
  </Step>

  <Step title="Exchange the code for tokens">
    ```bash theme={null}
    curl -X POST https://app.vortexiq.ai/oauth/mcp/token \
      -H "Content-Type: application/x-www-form-urlencoded" \
      --data-urlencode "grant_type=authorization_code" \
      --data-urlencode "code=<AUTH_CODE>" \
      --data-urlencode "client_id=<CLIENT_ID>" \
      --data-urlencode "redirect_uri=<REGISTERED_URI>" \
      --data-urlencode "code_verifier=<VERIFIER>"
    ```

    Returns:

    ```json theme={null}
    {
      "access_token": "<JWT>",
      "token_type": "Bearer",
      "expires_in": 3600,
      "refresh_token": "<opaque>",
      "scope": ""
    }
    ```
  </Step>

  <Step title="Call the MCP endpoint">
    Send `Authorization: Bearer <access_token>` on every request to `POST https://app.vortexiq.ai/mcp`. The endpoint speaks `initialize`, `tools/list`, `tools/call` and `ping`, and exposes the [30 read-only tools](/integrations/claude-mcp/tools) scoped to the signed-in user. `GET` and `DELETE` return 405, there is no server-initiated stream.

    `GET /oauth/mcp/userinfo` works as a lightweight token health check: 200 means the token is valid, 401 means re-authenticate.
  </Step>

  <Step title="Refresh (access token expires in 1 hour)">
    Refresh tokens **rotate**, each refresh returns a new refresh token and invalidates the old one. Always store the newest.

    ```bash theme={null}
    curl -X POST https://app.vortexiq.ai/oauth/mcp/token \
      -H "Content-Type: application/x-www-form-urlencoded" \
      --data-urlencode "grant_type=refresh_token" \
      --data-urlencode "refresh_token=<REFRESH_TOKEN>" \
      --data-urlencode "client_id=<CLIENT_ID>"
    ```
  </Step>
</Steps>

## Rules and gotchas

* **HTTPS only.** `redirect_uris` must be https; `localhost` is allowed only in development.
* **PKCE S256 required.** No client secret is used or accepted.
* **Audience binding.** Always send `resource=https://app.vortexiq.ai` (RFC 8707). Tokens minted for a different audience are rejected.
* **On 401** the response carries `WWW-Authenticate: Bearer resource_metadata="https://app.vortexiq.ai/.well-known/oauth-protected-resource"`, follow it to re-discover endpoints and re-authenticate.
* **Token lifetimes:** access token about 1 hour, refresh token about 30 days, authorization code about 5 minutes.
* **Permissions.** The token acts as the signed-in user, with the same organisation and role permissions that user already has in Vortex IQ.


# Vortex IQ MCP connector: query your workspace from Claude
Source: https://docs.vortexiq.ai/integrations/claude-mcp/overview

Connect Claude (or any MCP client) to Vortex IQ and ask about store audits, KPIs, Nerve Centre alerts, Brand DNA, Kanban fixes and more, 30 read-only tools, scoped to your own workspace.

The Vortex IQ MCP connector gives Claude, and any other [Model Context Protocol](https://modelcontextprotocol.io) client, read-only access to your Vortex IQ workspace. Once connected, you can ask about your store's health scores, KPI trends, active alerts, brand voice guidelines, health-fix backlog and more, in plain English, without opening the dashboard.

Every tool is **read-only**: the connector cannot create, edit, delete, publish or send anything. Each call runs as the signed-in user, so the data returned is always scoped to your own organisation and your role's permissions.

## At a glance

|                    |                                                                                                      |
| ------------------ | ---------------------------------------------------------------------------------------------------- |
| **Server URL**     | `https://app.vortexiq.ai/mcp`                                                                        |
| **Transport**      | Streamable HTTP (remote MCP server)                                                                  |
| **Authentication** | Per-user OAuth 2.1 (Authorization Code + PKCE, S256)                                                 |
| **Access**         | Read-only, scoped to the signed-in user's organisation                                               |
| **Tools**          | 30, across Store Audit, Nerve Centre, Brand DNA, Ask Viq, Kanban, Reports, Inventory and Deployments |
| **Requirements**   | A [Vortex IQ account](https://app.vortexiq.ai)                                                       |

<CardGroup>
  <Card title="Connect to Claude" icon="plug" href="/integrations/claude-mcp/connect-claude">
    Add the connector in Claude web, desktop or Claude Code in under two minutes.
  </Card>

  <Card title="Tool reference" icon="wrench" href="/integrations/claude-mcp/tools">
    All 30 read-only tools with parameters and example prompts, grouped by area.
  </Card>

  <Card title="OAuth for developers" icon="key" href="/integrations/claude-mcp/oauth">
    The full OAuth 2.1 + PKCE flow for connecting any custom MCP client or agent.
  </Card>
</CardGroup>

## What you can ask

Once connected, Claude picks the right tools automatically. Some starting points:

| Prompt                                                                        | What happens                                                                     |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| "List my recent store audits, then show the findings for integration `<id>`." | Lists audit runs, then pulls the full findings report with health score.         |
| "What KPIs are available, and show the 30-day KPIs for `<integration>`."      | Browses the KPI library, then fetches KPI cards and trends for that integration. |
| "List my active Nerve Centre alerts and give me the 24h incident summary."    | Returns active alerts plus the last-24-hours incident counts.                    |
| "Show my Brand DNA voice and tone guidelines."                                | Fetches your Brand DNA profile for use while drafting content.                   |
| "Show my Kanban health-fix backlog."                                          | Returns the board state, and can drill into a fix run's before/after changes.    |
| "List my connected integrations and their status."                            | Summarises the organisation's connector graph and connection counts.             |

## How it works

The connector is a native MCP server co-located with the Vortex IQ OAuth authorization server at `app.vortexiq.ai`, there is no separate proxy. When you add it, Claude walks you through a standard OAuth sign-in with your existing Vortex IQ (Google) login. Your access token is forwarded on every tool call, so every result reflects exactly what your account can already see in the dashboard.

<Note>
  All 30 tools carry the MCP `readOnlyHint`. The connector has no write, delete, publish or send capability of any kind, it cannot modify your workspace, your stores or your data.
</Note>

## Known limitations

* **Read-only.** The connector cannot create, edit, delete, publish or send anything.
* **Per-user scope.** Each call runs as the connecting user against their own organisation's data, there is no shared or service account.
* **Response caps.** Some list results are capped (first 50 items / roughly 40k characters) to stay model-friendly. Ask for a specific id to drill into full detail.

## Support

* Documentation: [docs.vortexiq.ai](https://docs.vortexiq.ai/)
* Privacy policy: [vortexiq.ai/privacy-policy](https://www.vortexiq.ai/privacy-policy)
* Email: [support@vortexiq.ai](mailto:support@vortexiq.ai)


# Vortex IQ MCP tool reference: all 30 read-only tools
Source: https://docs.vortexiq.ai/integrations/claude-mcp/tools

Every tool exposed by the Vortex IQ MCP connector, parameters, example prompts and what each returns, grouped by area: Store Audit, Nerve Centre, Brand DNA, Ask Viq, Kanban, Reports, Inventory and Deployments.

The Vortex IQ MCP connector exposes 30 tools, all read-only. Every tool runs as the signed-in user and only returns data your account can access; none of them can change anything in your workspace. Large list results are capped (first 50 items / roughly 40k characters), request a specific id to drill into full detail.

You don't call these tools directly: describe what you want in plain English and Claude picks the right tools, chaining them where one tool's output (an id or guid) feeds another.

| Area                                          | Tools |
| --------------------------------------------- | ----- |
| [Store Audit](#store-audit)                   | 3     |
| [Nerve Centre & KPIs](#nerve-centre-and-kpis) | 12    |
| [Brand DNA](#brand-dna)                       | 3     |
| [Ask Viq](#ask-viq)                           | 2     |
| [Kanban health-fix](#kanban-health-fix)       | 3     |
| [Reports & Insights](#reports-and-insights)   | 3     |
| [Inventory & Memory](#inventory-and-memory)   | 3     |
| [Deployments](#deployments)                   | 1     |

## Store Audit

Tools for the [Store Audit](/actions/store-audit) module: audit runs, findings reports and run progress.

### list\_store\_audit\_runs

Lists recent Store Audit runs with id, guid, integration, health score and completion time. Takes no parameters. Usually the first call, its ids and guids feed the two tools below.

> *"List my store audit runs."*

### get\_store\_audit\_report

Gets the latest Store Audit findings report for one integration, including the health score and detailed findings.

| Parameter       | Type    | Required | Description                                                                        |
| --------------- | ------- | -------- | ---------------------------------------------------------------------------------- |
| `integrationId` | integer | Yes      | The integration to fetch the audit report for, find it via `list_store_audit_runs` |

> *"Show the audit findings report for integration 42."*

### get\_store\_audit\_status

Gets the status and progress of one Store Audit run, useful while an audit is still running.

| Parameter | Type   | Required | Description                                     |
| --------- | ------ | -------- | ----------------------------------------------- |
| `guid`    | string | Yes      | The audit run guid from `list_store_audit_runs` |

> *"What's the status of my latest store audit?"*

## Nerve Centre and KPIs

Tools for [Nerve Centre](/nerve-centre/overview): KPI cards and trends, alerts, monitors, dashboard activity and the connector graph.

### list\_nerve\_centre\_alerts

Lists active Nerve Centre KPI alerts, optionally filtered by severity or status.

| Parameter  | Type                                       | Required | Description              |
| ---------- | ------------------------------------------ | -------- | ------------------------ |
| `severity` | `critical` \| `high` \| `medium`           | No       | Filter by alert severity |
| `status`   | `active` \| `investigating` \| `dismissed` | No       | Filter by alert status   |

> *"List my critical Nerve Centre alerts."*

### get\_alert\_summary

Gets a 24-hour alert and incident summary count for the organisation. Takes no parameters.

> *"Give me the 24h incident summary."*

### list\_alert\_activity

Lists paginated alert activity across the organisation, including agency partner organisations. Takes no parameters.

> *"Show my recent alert activity."*

### get\_integration\_kpis

Gets KPI cards plus trend data (today / 7 days / 30 days / 90 days) for one specific integration.

| Parameter       | Type    | Required | Description                                                                                       |
| --------------- | ------- | -------- | ------------------------------------------------------------------------------------------------- |
| `integrationId` | integer | Yes      | The integration to fetch KPIs for, find it via `list_dashboard_stores` or `list_store_audit_runs` |

> *"Show the 30-day KPIs for my Shopify integration."*

### list\_kpi\_library

Lists the full catalogue of KPI definitions Vortex IQ tracks across all platforms. Takes no parameters.

> *"What KPIs does Vortex IQ track?"*

### get\_nerve\_integration\_counts

Gets connected-integration counts for the organisation. Takes no parameters.

> *"How many integrations do I have connected?"*

### list\_nerve\_centre\_profiles

Lists saved Nerve Centre dashboard KPI profiles, both templates and the organisation's custom profiles. Takes no parameters.

> *"List my Nerve Centre dashboard profiles."*

### list\_nerve\_configurations

Lists the metric and KPI definitions Vortex IQ can track per platform. Takes no parameters.

> *"What metrics can Vortex IQ track for Stripe?"*

### list\_connector\_catalog

Lists the full catalogue of connector types Vortex IQ supports, the same catalogue as the [connector catalogue](/integrations/connector-catalogue) page. Takes no parameters.

> *"What connectors does Vortex IQ support?"*

### list\_monitors\_by\_type

Lists the organisation's monitors of a given platform type, with alert-configuration counts.

| Parameter | Type   | Required | Description                                        |
| --------- | ------ | -------- | -------------------------------------------------- |
| `type`    | string | Yes      | Platform type, e.g. `shopify`, `website`, `stripe` |

> *"List my website monitors."*

### get\_dashboard\_activity\_feed

Gets a recent cross-source activity feed, audit findings, Kanban activity and other workspace events. Takes no parameters.

> *"What's happened in my workspace recently?"*

### list\_dashboard\_stores

Lists the stores available on the organisation's dashboard. Takes no parameters.

> *"List my connected stores."*

## Brand DNA

Tools for Brand DNA: voice and tone profiles and the stores they link to.

### list\_brand\_profiles

Lists the organisation's Brand DNA profiles. Takes no parameters. Its ids feed `get_brand_profile`.

> *"List my brand profiles."*

### get\_brand\_profile

Gets one Brand DNA profile by id, voice, tone and brand guidelines, handy while drafting content elsewhere.

| Parameter   | Type    | Required | Description                                 |
| ----------- | ------- | -------- | ------------------------------------------- |
| `profileId` | integer | Yes      | Brand profile id from `list_brand_profiles` |

> *"Show my Brand DNA voice and tone guidelines."*

### list\_brand\_ecommerce\_stores

Lists connected ecommerce stores eligible for Brand DNA profile linking. Takes no parameters.

> *"Which stores can I link a brand profile to?"*

## Ask Viq

Tools for [Ask Viq](/ask-viq/overview) chat history.

### list\_ask\_viq\_conversations

Lists your recent Ask Viq chat conversations, most recent first.

| Parameter | Type    | Required | Description                     |
| --------- | ------- | -------- | ------------------------------- |
| `limit`   | integer | No       | Maximum conversations to return |

> *"List my recent Ask Viq conversations."*

### get\_ask\_viq\_conversation

Gets the full message thread for one Ask Viq conversation.

| Parameter        | Type   | Required | Description                                       |
| ---------------- | ------ | -------- | ------------------------------------------------- |
| `conversationId` | string | Yes      | Conversation ID from `list_ask_viq_conversations` |

> *"Show me my last Ask Viq conversation about revenue."*

## Kanban health-fix

Tools for the health-fix Kanban board and its automated fix runs.

### get\_kanban\_board

Gets the organisation's Kanban board state, health-fix backlog cards per column. Takes no parameters.

> *"Show my Kanban health-fix backlog."*

### get\_kanban\_fix\_status

Gets the plan, rollback and approval status of one automated fix run.

| Parameter | Type    | Required | Description                      |
| --------- | ------- | -------- | -------------------------------- |
| `fixId`   | integer | Yes      | Fix run id from the Kanban board |

> *"What's the status of fix run 17?"*

### get\_kanban\_fix\_items

Gets the paginated before/after change records for one automated fix run.

| Parameter | Type    | Required | Description                      |
| --------- | ------- | -------- | -------------------------------- |
| `fixId`   | integer | Yes      | Fix run id from the Kanban board |

> *"Show the before/after changes for fix run 17."*

## Reports and Insights

Tools for generated insight reports, report configuration and schedules.

### list\_insights\_reports

Lists generated insight reports (status, platform, title) for a given user. The API requires an explicit user id, if Claude doesn't know it, it reads the `user_id` field from `list_ask_viq_conversations` first.

| Parameter | Type    | Required | Description                           |
| --------- | ------- | -------- | ------------------------------------- |
| `userId`  | integer | Yes      | Vortex IQ user id to list reports for |

> *"List my insights reports."*

### list\_report\_profiles

Lists saved report configuration profiles. Takes no parameters.

> *"List my report profiles."*

### list\_report\_schedules

Lists recurring report schedules with their status. Takes no parameters.

> *"Which reports are scheduled to run?"*

## Inventory and Memory

Tools for CloudHub multichannel inventory and the [Vortex Memory](/vortex-memory/overview) archive.

### list\_cloudhub\_inventory\_tabs

Lists CloudHub multichannel inventory tabs, marketplace channels like FBA, inventory images and so on. Takes no parameters.

> *"List my CloudHub inventory tabs."*

### list\_vortex\_memory\_files

Lists files in Vortex Memory's Knowledge Base, uploaded documents plus auto-saved reports. Takes no parameters.

> *"What's in my Vortex Memory knowledge base?"*

### list\_vortex\_memory\_reports

Lists archived Vortex Mind reports, daily briefings, audits and revenue intelligence reports. Takes no parameters.

> *"List my archived Vortex Mind reports."*

## Deployments

### get\_deployment\_history

Gets a deployment's revision and rollback history.

| Parameter      | Type    | Required | Description   |
| -------------- | ------- | -------- | ------------- |
| `deploymentId` | integer | Yes      | Deployment id |

> *"Show the rollback history for deployment 8."*


# Connect CloudHub Insights to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/cloudhub-insights

Connect CloudHub Insights to Vortex IQ for 39 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting CloudHub Insights to Vortex IQ gives the AI OS a live read on your CloudHub Insights data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from CloudHub Insights

* **Company**
* **SalesLine**
* **Order**
* **Invoice**
* **OrderStage**
* **OrderStageChange**
* **InventoryItem**
* **StockLevel**
* **Listing**
* **ProductStatus**
* **RepricerDaily**
* **Supplier**

## How to connect

<Note>
  CloudHub Insights uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the CloudHub Insights card">
    Locate the CloudHub Insights connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from CloudHub Insights">
    You will need:

    * **Customer Database**: The 247Cxxxx database for this customer (e.g. 247C1005).
    * **Company Name**: Friendly label, from CompanyDetails.CompanyName.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where CloudHub Insights offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **39** Nerve Centre cards from your CloudHub Insights data. See the [CloudHub Insights KPI card reference](/nerve-centre/kpi-cards/cloudhub-insights) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the CloudHub Insights developer console for typos or trailing whitespace. If a scope or permission is missing, CloudHub Insights will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Vortex IQ connector catalogue: every connector by category
Source: https://docs.vortexiq.ai/integrations/connector-catalogue

Browse every Vortex IQ connector, grouped into the same categories as Settings -> Connected Sources: commerce, marketplaces, databases, ads, payments, shipping, analytics, CRM, email, monitoring, support, CMS and more.

Vortex IQ's connector graph spans over 200 connectors, using the same grouping you see in **Settings -> Connected Sources**. Every connector you add populates Nerve Centre with KPI cards, feeds Vortex Mind diagnostics, and becomes queryable through Ask Viq. The value of the platform grows with each connector you add, since cross-platform findings are only possible when the graph has data from multiple sources.

To connect any source, go to **Settings -> Connected Sources -> Add Source**, search or browse by type, and follow the OAuth or credential flow for that connector. Connectors without a linked card page are live in the app with documentation on the way.

<Card title="New: Vortex IQ MCP Connector for Claude" icon="bot" href="/integrations/claude-mcp/overview">
  Connect Claude (or any MCP client) to your Vortex IQ workspace and ask about store audits, KPIs, alerts, Brand DNA and more, 30 read-only tools, scoped to your own account.
</Card>

<AccordionGroup>
  <Accordion title="E-commerce Platforms (18)">
    [Acumatica](/nerve-centre/kpi-cards/acumatica), [Adobe Commerce](/nerve-centre/kpi-cards/adobe-commerce), [Big Cartel](/nerve-centre/kpi-cards/bigcartel), [BigCommerce](/nerve-centre/kpi-cards/bigcommerce), [Medusa](/nerve-centre/kpi-cards/medusa), [Microsoft Dynamics 365](/nerve-centre/kpi-cards/microsoft-dynamics), [NetSuite](/nerve-centre/kpi-cards/netsuite), [Odoo](/nerve-centre/kpi-cards/odoo), [OpenCart](/nerve-centre/kpi-cards/opencart), [Oracle ERP Cloud](/nerve-centre/kpi-cards/oracle-erp), [PrestaShop](/nerve-centre/kpi-cards/prestashop), [Sage](/nerve-centre/kpi-cards/sage), [SAP](/nerve-centre/kpi-cards/sap), [Shopify](/nerve-centre/kpi-cards/shopify), [Shopline](/nerve-centre/kpi-cards/shopline), [Swell](/nerve-centre/kpi-cards/swell), [Volusion](/nerve-centre/kpi-cards/volusion), [WooCommerce](/nerve-centre/kpi-cards/woocommerce)

    Commerce and ERP platforms that power the core revenue and product KPIs in Nerve Centre and feed Vortex Mind revenue and checkout diagnostics.
  </Accordion>

  <Accordion title="Marketplace (18)">
    [AbeBooks](/nerve-centre/kpi-cards/abebooks), [Alibaba.com (B2B)](/nerve-centre/kpi-cards/alibaba), [Alibris](/nerve-centre/kpi-cards/alibris), [AliExpress](/nerve-centre/kpi-cards/aliexpress), [Amazon Seller Central](/nerve-centre/kpi-cards/amazon-seller), [Bonanza](/nerve-centre/kpi-cards/bonanza), [Costco SIP](/nerve-centre/kpi-cards/costco-sip), [Depop](/nerve-centre/kpi-cards/depop), [eBay](/nerve-centre/kpi-cards/ebay), [Etsy](/nerve-centre/kpi-cards/etsy), [Fruugo](/nerve-centre/kpi-cards/fruugo), [JD.com](/nerve-centre/kpi-cards/jd-com), [Mercari](/nerve-centre/kpi-cards/mercari), [Newegg](/nerve-centre/kpi-cards/newegg), [OnBuy](/nerve-centre/kpi-cards/onbuy), [Target Plus](/nerve-centre/kpi-cards/target-plus), [Vinted](/nerve-centre/kpi-cards/vinted), [Walmart Marketplace](/nerve-centre/kpi-cards/walmart-marketplace)

    Marketplaces, resale and wholesale channels. Track GMV, listing health, Buy Box win rate, fees and returns alongside your direct store.
  </Accordion>

  <Accordion title="Databases (22)">
    Amazon DynamoDB, Amazon Redshift, Apache Cassandra, [ClickHouse](/nerve-centre/kpi-cards/clickhouse), [CockroachDB](/nerve-centre/kpi-cards/cockroachdb), Custom Connector, [Databricks](/nerve-centre/kpi-cards/databricks), [Elasticsearch](/nerve-centre/kpi-cards/elasticsearch), Google BigQuery, Google Firestore, [MariaDB](/nerve-centre/kpi-cards/mariadb), Microsoft SQL Server, [MongoDB](/nerve-centre/kpi-cards/mongodb), [MySQL](/nerve-centre/kpi-cards/mysql), Neo4j, Oracle Database, PlanetScale, [PostgreSQL](/nerve-centre/kpi-cards/postgresql), [Redis](/nerve-centre/kpi-cards/redis), [Snowflake](/nerve-centre/kpi-cards/snowflake), SQLite, [Supabase](/nerve-centre/kpi-cards/supabase)

    Operational and analytical data stores. Track table volume, query health, replication lag and freshness, and join custom data back to commerce KPIs.
  </Accordion>

  <Accordion title="Analytics (12)">
    [Amplitude](/nerve-centre/kpi-cards/amplitude), [Chartbeat](/nerve-centre/kpi-cards/chartbeat), [FullStory](/nerve-centre/kpi-cards/fullstory), [Google Analytics](/nerve-centre/kpi-cards/google-analytics), [Google Search Console](/nerve-centre/kpi-cards/google-search-console), [Hotjar](/nerve-centre/kpi-cards/hotjar), [Matomo](/nerve-centre/kpi-cards/matomo), [Microsoft Clarity](/nerve-centre/kpi-cards/clarity), [Mixpanel](/nerve-centre/kpi-cards/mixpanel), [Plausible Analytics](/nerve-centre/kpi-cards/plausible), [PostHog](/nerve-centre/kpi-cards/posthog), [Segment](/nerve-centre/kpi-cards/segment)

    Web and product analytics. Surface traffic, funnel behaviour and conversion KPIs. GA4 feeds Cross-Platform Metrics cards in Nerve Centre.
  </Accordion>

  <Accordion title="Advertising (16)">
    [AdRoll](/nerve-centre/kpi-cards/adroll), [Amazon Ads](/nerve-centre/kpi-cards/amazon-ads), [Criteo](/nerve-centre/kpi-cards/criteo), [Google Ads](/nerve-centre/kpi-cards/google-ads), [LinkedIn Ads](/nerve-centre/kpi-cards/linkedin-ads), [MediaMath (T1)](/nerve-centre/kpi-cards/mediamath), [Meta Ads (Facebook)](/nerve-centre/kpi-cards/facebook-ads), [Microsoft Ads (Bing)](/nerve-centre/kpi-cards/microsoft-ads), [Outbrain](/nerve-centre/kpi-cards/outbrain), [Pinterest Ads](/nerve-centre/kpi-cards/pinterest-ads), [Quora Ads](/nerve-centre/kpi-cards/quora-ads), [Snapchat Ads](/nerve-centre/kpi-cards/snapchat-ads), [StackAdapt](/nerve-centre/kpi-cards/stackadapt), [Taboola](/nerve-centre/kpi-cards/taboola), [The Trade Desk](/nerve-centre/kpi-cards/the-trade-desk), [TikTok Ads](/nerve-centre/kpi-cards/tiktok-ads)

    Ad platforms carry deep KPI card sets covering spend, ROAS, CPA, CTR, conversion funnels, budget and anomaly alerts.
  </Accordion>

  <Accordion title="Payments (18)">
    [Adyen](/nerve-centre/kpi-cards/adyen), [Afterpay](/nerve-centre/kpi-cards/afterpay), [Authorize.net](/nerve-centre/kpi-cards/authorize-net), [Braintree](/nerve-centre/kpi-cards/braintree), [CyberSource](/nerve-centre/kpi-cards/cybersource), FreshBooks, [Klarna (API)](/nerve-centre/kpi-cards/klarna-api), [Mollie](/nerve-centre/kpi-cards/mollie), [PayPal](/nerve-centre/kpi-cards/paypal), QuickBooks (API), [Razorpay](/nerve-centre/kpi-cards/razorpay), [Square](/nerve-centre/kpi-cards/square), [Stripe](/nerve-centre/kpi-cards/stripe), [Viva Payments](/nerve-centre/kpi-cards/viva-payments), Wave, [Worldpay](/nerve-centre/kpi-cards/worldpay), Xero (API), Zoho Books

    Payment gateways and finance tools feeding Payment Performance and Decline Recovery diagnostics: auth rates, decline reason codes, BIN-level patterns and recoverable revenue.
  </Accordion>

  <Accordion title="Shipping & Delivery (23)">
    [Amazon Prime Shipping (SFP)](/nerve-centre/kpi-cards/amazon-prime-shipping), [APC Overnight](/nerve-centre/kpi-cards/apc), [Australia Post](/nerve-centre/kpi-cards/australia-post), [Bring (Posten Norge)](/nerve-centre/kpi-cards/bring), [Deutsche Post / DHL Parcel](/nerve-centre/kpi-cards/deutsche-post), [DHL InExpress](/nerve-centre/kpi-cards/dhl-inexpress), [DPD](/nerve-centre/kpi-cards/dpd), [DPDLocal](/nerve-centre/kpi-cards/dpdlocal), [EasyPost](/nerve-centre/kpi-cards/easypost), [Evri (formerly Hermes UK)](/nerve-centre/kpi-cards/hermes-evri), [FedEx](/nerve-centre/kpi-cards/fedex), [Interlink Express](/nerve-centre/kpi-cards/interlink-express), [Japan Post (EMS / Yu-Pack)](/nerve-centre/kpi-cards/japan-post), [NetDispatch](/nerve-centre/kpi-cards/net-dispatch), [Parcelforce Worldwide](/nerve-centre/kpi-cards/parcelforce), [PostNord](/nerve-centre/kpi-cards/postnord), [Royal Mail](/nerve-centre/kpi-cards/royal-mail), [Sendle](/nerve-centre/kpi-cards/sendle), [ShipBob](/nerve-centre/kpi-cards/shipbob), [Shippo](/nerve-centre/kpi-cards/shippo), [ShippyPro](/nerve-centre/kpi-cards/shippy-pro), [ShipTheory](/nerve-centre/kpi-cards/ship-theory), [USPS](/nerve-centre/kpi-cards/usps)

    Carriers and 3PLs. On-time delivery rate, cost per shipment, carrier comparison and exception alerts for delayed or lost parcels.
  </Accordion>

  <Accordion title="Project Management (16)">
    ADP, [Asana](/nerve-centre/kpi-cards/asana), BambooHR, [Basecamp](/nerve-centre/kpi-cards/basecamp), [ClickUp](/nerve-centre/kpi-cards/clickup), Gusto, [Height](/nerve-centre/kpi-cards/height), [Jira](/nerve-centre/kpi-cards/jira), [Linear](/nerve-centre/kpi-cards/linear), [Monday.com](/nerve-centre/kpi-cards/monday), Personio, [Smartsheet (API)](/nerve-centre/kpi-cards/smartsheet-api), [Teamwork](/nerve-centre/kpi-cards/teamwork), [Trello (API)](/nerve-centre/kpi-cards/trello-api), Wrike, [Wrike (API)](/nerve-centre/kpi-cards/wrike-api)

    Push Vortex Agents findings and Kanban cards into the planning tools your team already uses for task tracking.
  </Accordion>

  <Accordion title="Cloud Platforms (14)">
    Amazon Web Services, Anthropic (Claude), [Cloudflare](/nerve-centre/kpi-cards/cloudflare), Cohere, DigitalOcean, Fly.io, Google Cloud Platform, Hetzner, Hugging Face, Linode (Akamai), Microsoft Azure, OpenAI, Replicate, Vultr

    Infrastructure and AI/ML providers. Track usage, spend and service health, and correlate cost or outages against revenue.
  </Accordion>

  <Accordion title="CRM (10)">
    [Agile CRM](/nerve-centre/kpi-cards/agile-crm), [Freshsales](/nerve-centre/kpi-cards/freshsales), [HubSpot](/nerve-centre/kpi-cards/hubspot), [Insightly](/nerve-centre/kpi-cards/insightly), [Keap (Infusionsoft)](/nerve-centre/kpi-cards/keap), [Nimble](/nerve-centre/kpi-cards/nimble), [Pipedrive](/nerve-centre/kpi-cards/pipedrive), [Salesforce](/nerve-centre/kpi-cards/salesforce), [SugarCRM](/nerve-centre/kpi-cards/sugarcrm), [Zoho CRM](/nerve-centre/kpi-cards/zoho-crm)

    Customer lifetime value, churn-risk signals and the Customer Recovery Opportunity report in Vortex Mind.
  </Accordion>

  <Accordion title="Email & Marketing (13)">
    [ActiveCampaign](/nerve-centre/kpi-cards/activecampaign), [AWeber](/nerve-centre/kpi-cards/aweber), [Brevo (Sendinblue)](/nerve-centre/kpi-cards/brevo-sendinblue), [Campaign Monitor](/nerve-centre/kpi-cards/campaign-monitor), [Constant Contact](/nerve-centre/kpi-cards/constant-contact), [ConvertKit (API)](/nerve-centre/kpi-cards/convertkit-api), [Customer.io (API)](/nerve-centre/kpi-cards/customerio-api), [Dotdigital](/nerve-centre/kpi-cards/dotdigital), [Drip (API)](/nerve-centre/kpi-cards/drip-api), [Iterable](/nerve-centre/kpi-cards/iterable), [Klaviyo](/nerve-centre/kpi-cards/klaviyo), [Mailchimp](/nerve-centre/kpi-cards/mailchimp), [SendGrid](/nerve-centre/kpi-cards/sendgrid)

    Deliverability, open and click rate, revenue attribution and list-health KPIs. Klaviyo feeds Cross-Platform Metrics audience-overlap cards.
  </Accordion>

  <Accordion title="Notifications (10)">
    [Atlassian Statuspage](/nerve-centre/kpi-cards/statuspage), [Discord](/nerve-centre/kpi-cards/discord), Email, [Microsoft Teams](/nerve-centre/kpi-cards/teams), [Opsgenie](/nerve-centre/kpi-cards/opsgenie), [PagerDuty](/nerve-centre/kpi-cards/pagerduty), [Pushover](/nerve-centre/kpi-cards/pushover), [Slack](/nerve-centre/kpi-cards/slack), [Telegram](/nerve-centre/kpi-cards/telegram), [Twilio](/nerve-centre/kpi-cards/twilio)

    Alert and messaging channels for routing Nerve Centre alerts and Vortex Agents updates into the tools your team lives in.
  </Accordion>

  <Accordion title="Monitoring & Performance (15)">
    [Better Uptime](/nerve-centre/kpi-cards/better-uptime), CrowdStrike, [Datadog](/nerve-centre/kpi-cards/datadog), Duo Security, Google Tag Manager, [Grafana](/nerve-centre/kpi-cards/grafana), [New Relic](/nerve-centre/kpi-cards/newrelic), OneLogin, [Pingdom](/nerve-centre/kpi-cards/pingdom), [Prometheus](/nerve-centre/kpi-cards/prometheus), SentinelOne, [Sentry](/nerve-centre/kpi-cards/sentry), [Splunk](/nerve-centre/kpi-cards/splunk), [Uptime Robot](/nerve-centre/kpi-cards/uptime-robot), Website

    Infrastructure, application and site-performance signals. Vortex Mind correlates these against revenue anomalies to build root-cause evidence.
  </Accordion>

  <Accordion title="Version Control (4)">
    Azure DevOps, Bitbucket, GitHub, GitLab

    Source-control and DevOps platforms. Track deployment cadence, change volume and incident correlation against store health.
  </Accordion>

  <Accordion title="Support (9)">
    [Crisp](/nerve-centre/kpi-cards/crisp), [Freshdesk](/nerve-centre/kpi-cards/freshdesk), [Gorgias](/nerve-centre/kpi-cards/gorgias), [Help Scout](/nerve-centre/kpi-cards/helpscout), [Intercom](/nerve-centre/kpi-cards/intercom), [LiveAgent](/nerve-centre/kpi-cards/liveagent), [LiveChat](/nerve-centre/kpi-cards/livechat), [Tidio](/nerve-centre/kpi-cards/tidio), [Zendesk](/nerve-centre/kpi-cards/zendesk)

    Helpdesk and contact-centre tools surfacing ticket volume, response time, CSAT and deflection signals.
  </Accordion>

  <Accordion title="Content & Docs (6)">
    Airtable, Baserow, Coda, [Confluence](/nerve-centre/kpi-cards/confluence), Google Sheets, [Notion](/nerve-centre/kpi-cards/notion)

    Knowledge, docs and tabular data sources that Ask Viq can query and Vortex Memory can archive.
  </Accordion>

  <Accordion title="CMS (5)">
    [Ghost](/nerve-centre/kpi-cards/ghost), [Prismic](/nerve-centre/kpi-cards/prismic), [Sanity](/nerve-centre/kpi-cards/sanity), [Strapi](/nerve-centre/kpi-cards/strapi), [WordPress](/nerve-centre/kpi-cards/wordpress)

    Content platforms that expose content-performance metrics and let Bulk Content Edit map directly to your content model for AI-powered rewrites.
  </Accordion>

  <Accordion title="Social Media (5)">
    [Instagram](/nerve-centre/kpi-cards/instagram), [Reddit](/nerve-centre/kpi-cards/reddit), [TikTok](/nerve-centre/kpi-cards/tiktok-organic), [X (Twitter)](/nerve-centre/kpi-cards/twitter), [YouTube](/nerve-centre/kpi-cards/youtube)

    Organic social channels for audience, engagement and content KPIs.
  </Accordion>

  <Accordion title="VortexIQ Apps (5)">
    RollbackPro, Shopify Backup, Shopify Staging, StagingPro, Viva Payments App

    First-party VortexIQ apps for safe staging, rollback and store protection.
  </Accordion>
</AccordionGroup>

## Connect a source

<Steps>
  <Step title="Open Connected Sources">
    Go to **Settings -> Connected Sources** and click **Add Source**.
  </Step>

  <Step title="Find your connector">
    Use the search bar or browse by type.
  </Step>

  <Step title="Authenticate">
    Follow the OAuth pop-up or enter API credentials depending on the connector type.
  </Step>

  <Step title="Save">
    Click **Save**. Nerve Centre cards for that connector appear after the initial data pull (typically 2-10 minutes for OAuth sources, up to 30 minutes for high-volume credential-based sources).
  </Step>
</Steps>

<Tip>
  Start by connecting your primary commerce platform, at least one ad platform, and your payment gateway. These three together unlock the most powerful Vortex Mind cross-platform diagnostics.
</Tip>


# Connect Criteo to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/criteo

Connect Criteo to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Criteo to Vortex IQ gives the AI OS a live read on your Criteo data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Criteo

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Criteo card">
    Locate the Criteo connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Criteo">
    You are redirected to Criteo's own authorisation page. Sign in and approve the requested permissions.
  </Step>

  <Step title="Return to Vortex IQ">
    Criteo redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Criteo API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your Criteo data. See the [Criteo KPI card reference](/nerve-centre/kpi-cards/criteo) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Criteo developer console for typos or trailing whitespace. If a scope or permission is missing, Criteo will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Ecwid by Lightspeed to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/ecwid

Connect Ecwid by Lightspeed to Vortex IQ for 37 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Ecwid by Lightspeed to Vortex IQ gives the AI OS a live read on your Ecwid by Lightspeed data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Ecwid by Lightspeed

* **Product**
* **Order**
* **Customer**
* **Storefront**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Ecwid by Lightspeed card">
    Locate the Ecwid by Lightspeed connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Ecwid by Lightspeed">
    You are redirected to Ecwid by Lightspeed's own authorisation page (`https://my.ecwid.com/api/oauth/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `read_catalog`, `read_orders`, `read_customers`, `read_store_profile`.
  </Step>

  <Step title="Return to Vortex IQ">
    Ecwid by Lightspeed redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Ecwid by Lightspeed API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **37** Nerve Centre cards from your Ecwid by Lightspeed data. See the [Ecwid by Lightspeed KPI card reference](/nerve-centre/kpi-cards/ecwid) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Ecwid by Lightspeed developer console for typos or trailing whitespace. If a scope or permission is missing, Ecwid by Lightspeed will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Google Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/google-ads

Connect Google Ads to Vortex IQ for 75 KPI cards including Cross-Platform Metrics cards for revenue at risk, ads on out-of-stock SKUs, and Google Ads revenue share.

Connecting Google Ads to Vortex IQ gives the AI OS a live read on every campaign, ad group, and keyword in your account. Nerve Centre populates with 75 KPI cards covering campaign performance, budget monitoring, keyword intelligence, geographic performance, alert detection, and Cross-Platform Metrics signals that only become visible when Google Ads data is paired with your commerce platform and other connectors.

## What data Vortex IQ reads from Google Ads

Vortex IQ connects to the Google Ads API (GAQL) and ingests the following data:

<AccordionGroup>
  <Accordion title="Campaign performance">
    * Spend, impressions, clicks, and conversions at account, campaign, ad group, and keyword level
    * Conversion value (`conversions_value`) for revenue attribution
    * Cost per click (CPC), cost per acquisition (CPA), and ROAS
    * Click-through rate (CTR) and conversion rate
    * Campaign type, status, and bidding strategy
    * Budget utilisation per campaign
  </Accordion>

  <Accordion title="Keywords and search terms">
    * Keyword performance including Quality Score
    * Search terms report (actual queries that triggered ads)
    * Wasted spend on zero-conversion search terms
    * Top keywords by spend and by conversions
  </Accordion>

  <Accordion title="Geography and device">
    * Conversions, spend, and ROAS by country and city
    * Performance breakdown by device (desktop, mobile, tablet)
    * Impression share by geography
  </Accordion>

  <Accordion title="Day and time performance">
    * Spend, ROAS, and conversion rate by hour of day
    * Spend and conversions by day of week
    * Conversion lag (time from click to conversion)
  </Accordion>

  <Accordion title="Landing page performance">
    * CPC, conversion rate, and revenue attributed per landing page URL
  </Accordion>
</AccordionGroup>

<Note>
  Vortex IQ uses the Google Ads API with GAQL (Google Ads Query Language). The connector requires a Google Ads account with at least one active campaign. For MCC (Manager Account) setups, you connect at the MCC level and Vortex IQ surfaces per-child-account alerts individually.
</Note>

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Google Ads card">
    Locate the Google Ads connector card and click **+ Connect**. The connector drawer opens showing the scopes Vortex IQ will request.
  </Step>

  <Step title="Authenticate with Google">
    Click **Connect with Google**. A new tab opens at Google's authorisation screen. Sign in with the Google account that has access to your Google Ads account. Review the requested scope and click **Allow**.
  </Step>

  <Step title="Select your account or MCC">
    After authentication, Vortex IQ shows a list of Google Ads accounts accessible under your login. Select the account or MCC you want to connect.
  </Step>

  <Step title="Wait for the first data pull">
    Google Ads KPI cards appear in Nerve Centre within 5 to 15 minutes for active campaigns. Historical data backfills progressively.
  </Step>
</Steps>

<Note>
  The scope Vortex IQ requests is `https://www.googleapis.com/auth/adwords` (read-only access to Google Ads data). No campaign changes, bid adjustments, or budget modifications are made by Vortex IQ.
</Note>

## Available KPI cards

Google Ads is the most instrumented ad platform in Vortex IQ with 75 Nerve Centre cards, including a unique set of Cross-Platform Metrics cards.

<CardGroup>
  <Card title="Executive overview" icon="gauge">
    **ROAS** - Return on ad spend (`conversions_value ÷ cost`). Key Metrics gauge card. The account-level efficiency number. Alerts at configurable thresholds.

    **Total Spend** - Account-level spend in the period.

    **ROAS by Campaign** - Per-campaign ROAS breakdown. Key Metrics bar chart for identifying which campaigns are carrying vs dragging the account.

    **Wasted Spend** - Spend on zero-conversion keywords and search terms.

    **Zero-Conversion Spend** - Spend where no conversion occurred in the period. Key Metrics alert card.
  </Card>

  <Card title="Alert cards" icon="bell">
    **ROAS Drop Alert** - Fires when ROAS drops more than 25% vs the prior 7-day same-day-of-week baseline. The first alert when the ad team's day is going to be difficult. Suppressed before 14:00 local to avoid incomplete-data false positives.

    **Conversion-Tracking-Broken Alert** - Fires when the click-to-conversion ratio collapses in a way that indicates a pixel or tag break rather than real performance. Key Metrics alert card.

    **CPC Spike Alert** - Fires when CPC rises sharply above the same-DOW baseline.

    **Disapproved-Ad Burst Alert** - Fires when a cluster of ads receive disapprovals in a short window.

    **Wasted-Spend Burst Alert** - Fires when spend on zero-conversion terms rises sharply.

    **Conversion Drop Alert** - Fires when conversion volume drops sharply. Key Metrics alert card.
  </Card>

  <Card title="Campaign performance" icon="megaphone">
    **Campaign Comparison** - Side-by-side table of spend, ROAS, CPC, CTR, and conversion rate per campaign.

    **Top Performing Campaigns** - Highest-ROAS campaigns in the period.

    **Worst Performing Campaigns** - Lowest-ROAS campaigns - pause or restructure candidates.

    **Overspending Campaigns** - Campaigns pacing above daily budget.

    **Underspending Campaigns** - Campaigns restricted by budget before end of day.

    **Budget Utilisation** - Spend vs budget gauge per campaign.
  </Card>

  <Card title="Keyword intelligence" icon="search">
    **Wasted Spend** - Spend on keywords that generated zero conversions.

    **Quality Score Distribution** - Distribution of keyword Quality Scores across the account.

    **Top Keywords by Conversions** - Highest-converting keywords.

    **Top Keywords by Spend** - Highest-spend keywords.

    **Search Terms Report** - Actual queries triggering your ads, with spend and conversion data.

    **CPA by Keyword** - Cost per acquisition broken out per keyword.
  </Card>

  <Card title="Geography and device" icon="globe">
    **Conversions by Country** - Choropleth map of conversion volume by country.

    **Spend by Country** - Choropleth map of spend by country.

    **Top Cities by Conversions** - Highest-converting cities.

    **CTR by Region** - Click-through rate by geographic region.

    **ROAS by Region** - ROAS breakdown by region.

    **Conversions by Device** - Desktop vs mobile vs tablet conversion split (donut chart).

    **ROAS by Device** - ROAS per device type.
  </Card>

  <Card title="Day and time" icon="clock">
    **ROAS by Day of Week** - Best and worst days for return on ad spend.

    **Spend by Hour** - Intra-day spend distribution.

    **Conversions by Hour** - Heatmap of conversion volume by hour of day.

    **CPC by Hour** - CPC variation across hours for dayparting optimisation.

    **Conversion Lag** - Distribution of time from click to conversion.
  </Card>
</CardGroup>

### Cross-Platform Metrics cards

Google Ads unlocks a set of Cross-Platform Metrics cards when paired with a commerce platform connector (Shopify, BigCommerce, or Adobe Commerce) and monitoring tools:

| Card                                  | Metrics type           | What it shows                                                                                                                                |
| ------------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Active Ads on Out-of-Stock SKUs       | Cross-Platform Metrics | Google Ads spend on product URLs where inventory is at zero - the exact keywords and campaigns wasting budget on unsellable products         |
| Revenue at Risk from active incidents | Cross-Platform Metrics | Live revenue-per-minute estimate while a monitoring incident (Datadog, New Relic) is open, attributed to the Google Ads traffic stream       |
| Google Ads Revenue Share              | Cross-Platform Metrics | Google Ads-attributed revenue as a share of total commerce-platform revenue - the paid-search contribution to the business                   |
| Audience Overlap with Email Programme | Cross-Platform Metrics | Overlap between Google Ads audiences and your email list - identifies where paid and owned media are duplicating                             |
| Landing-Page LCP vs Conversion        | Cross-Platform Metrics | Correlation between landing page Largest Contentful Paint score and conversion rate - surface pages where performance is costing conversions |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Google authentication succeeds but no accounts are listed">
    The Google account you authenticated with does not have access to any Google Ads accounts. Sign in to Google Ads directly to confirm which accounts are accessible under that login. If you use an MCC (Manager Account), ensure you signed in with the MCC owner login or a user with account access granted at the MCC level.
  </Accordion>

  <Accordion title="ROAS Drop Alert fires every Monday morning">
    Monday-after-a-promotion is a known false-positive pattern. The alert compares Monday-to-Monday, but if the prior Monday had a sale running and this Monday does not, the baseline is inflated. Document your promotional calendar and treat Monday alerts following a weekend sale as expected. You can raise the alert threshold from 25% to 35% in your workspace alert settings for high-volatility accounts.
  </Accordion>

  <Accordion title="Conversion-Tracking-Broken Alert fired - what do I do first?">
    Open the **Clicks vs Conversions** card. If clicks held normal volume but conversions dropped sharply, the cause is almost always a pixel or tag break. Run a test order on your store and use Google Tag Assistant to check whether the conversion tag fires on the order confirmation page. If the tag does not fire, your conversion tracking has been broken - likely by a recent change to the checkout page. Fix the tag and do not pause campaigns based on this alert alone.
  </Accordion>

  <Accordion title="Google Ads spend differs from what is in the Google Ads UI">
    Vortex IQ reads spend via the Google Ads API, which may have a 1 to 4 hour ingest lag relative to the Google Ads UI. For today's figures, expect a small lag. For prior days (yesterday and earlier), figures should match the UI to within sub-percent rounding differences from currency handling.
  </Accordion>

  <Accordion title="Cross-Platform Metrics cards are empty even with Shopify connected">
    Cross-Platform Metrics cards require both Google Ads and your commerce platform to be connected and synced. If either connector is still in its first-pull window (up to 4 hours for Shopify), the cross-platform join cannot run. Wait for both connectors to show a Connected and synced state, then refresh the Nerve Centre dashboard.
  </Accordion>
</AccordionGroup>


# Connect LinkedIn Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/linkedin-ads

Connect LinkedIn Ads to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting LinkedIn Ads to Vortex IQ gives the AI OS a live read on your LinkedIn Ads data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from LinkedIn Ads

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the LinkedIn Ads card">
    Locate the LinkedIn Ads connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with LinkedIn Ads">
    You are redirected to LinkedIn Ads's own authorisation page (`https://www.linkedin.com/oauth/v2/authorization`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `r_ads`, `r_ads_reporting`, `rw_ads`, `r_organization_social`.
  </Step>

  <Step title="Return to Vortex IQ">
    LinkedIn Ads redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the LinkedIn Ads API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your LinkedIn Ads data. See the [LinkedIn Ads KPI card reference](/nerve-centre/kpi-cards/linkedin-ads) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the LinkedIn Ads developer console for typos or trailing whitespace. If a scope or permission is missing, LinkedIn Ads will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect MediaMath (T1) to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/mediamath

Connect MediaMath (T1) to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting MediaMath (T1) to Vortex IQ gives the AI OS a live read on your MediaMath (T1) data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from MediaMath (T1)

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Note>
  MediaMath (T1) uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the MediaMath (T1) card">
    Locate the MediaMath (T1) connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from MediaMath (T1)">
    You will need:

    * **T1 Username**: T1 user account with API access. Engineering must verify post-2023 support.
    * **T1 Password**: T1 user password. Historical session-cookie login, engineering must verify current flow.
    * **Organization ID**: T1 organization ID, find under Admin → Organization Settings (when accessible).
    * **Agency ID**: T1 agency ID under the organization.
    * **Advertiser ID**: T1 advertiser ID under the agency. One per brand/client.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where MediaMath (T1) offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your MediaMath (T1) data. See the [MediaMath (T1) KPI card reference](/nerve-centre/kpi-cards/mediamath) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the MediaMath (T1) developer console for typos or trailing whitespace. If a scope or permission is missing, MediaMath (T1) will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Medusa to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/medusa

Connect Medusa to Vortex IQ for 29 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Medusa to Vortex IQ gives the AI OS a live read on your Medusa data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Medusa

* **Product**
* **ProductVariant**
* **Order**
* **Customer**
* **Region**

## How to connect

<Note>
  Medusa uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Medusa card">
    Locate the Medusa connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from Medusa">
    You will need:

    * **Medusa Backend URL**: Per-merchant Medusa backend base URL where the Admin API lives, e.g. [https://commerce.yourbrand.com](https://commerce.yourbrand.com). Admin API path /admin is appended automatically.
    * **Admin API Token**: Admin API token from the Medusa admin dashboard (Settings → API key management → Secret keys), or a JWT from /auth/user/emailpass. Sent as Authorization: Bearer.
    * **Publishable API Key**: Optional pk\_... key scoping which sales channels are visible. Only needed when the merchant restricts admin reads by sales channel.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where Medusa offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **29** Nerve Centre cards from your Medusa data. See the [Medusa KPI card reference](/nerve-centre/kpi-cards/medusa) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Medusa developer console for typos or trailing whitespace. If a scope or permission is missing, Medusa will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Meta Ads (Facebook) to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/meta-ads

Connect Meta Ads to Vortex IQ to monitor 65 KPI cards covering spend, ROAS, conversions, and performance across your Facebook and Instagram campaigns.

Connecting Meta Ads gives Vortex IQ access to your Facebook and Instagram campaign data. Once connected, 65 KPI cards become available in Nerve Centre-covering campaign performance, budget monitoring, funnel conversion, keyword intelligence, and real-time anomaly alerts. Vortex Mind can cross-reference Meta Ads spend with Shopify or BigCommerce revenue to diagnose paid traffic waste.

## What Vortex IQ reads from Meta Ads

| Category             | Example cards                                                                               |
| -------------------- | ------------------------------------------------------------------------------------------- |
| Executive Overview   | Total Spend, Total Revenue, ROAS, CPA Trend, Impressions Trend                              |
| Budget Monitoring    | Spend vs Budget, Budget Utilisation, Overspending Campaigns, Underspending Campaigns        |
| Campaign Performance | ROAS by Campaign, Revenue by Campaign, Conversion Rate by Campaign, Campaign Comparison     |
| Funnel & Conversion  | Conversion Funnel, Conversion Lag, Clicks vs Conversions, Conversion Rate Trend             |
| Alerts & Anomalies   | Conversion Drop Alert, CPC Anomaly, CTR Decline Alert, Spend Anomaly, Zero-Conversion Spend |
| Geography            | Conversions by Country, Spend by Country, CPA by Region                                     |
| Device               | Conversion Rate by Device, Spend by Device, ROAS by Device                                  |
| Day & Time           | Conversions by Hour, Spend by Hour, Conversions by Day of Week                              |

Key Metrics cards (the most prominent KPIs shown at the top of your Nerve Centre dashboard) include: **ROAS**, **Spend vs Budget**, **Total Spend**, **Total Revenue**, **Wasted Spend**, and **Zero-Conversion Spend**.

## How to connect

<Steps>
  <Step title="Go to Connected Sources">
    In Vortex IQ, navigate to **Settings → Connected Sources** and click **Add Source**.
  </Step>

  <Step title="Select Meta Ads">
    Search for "Meta Ads" or "Facebook Ads" and select it from the catalogue.
  </Step>

  <Step title="Authorise via OAuth">
    Click **Connect**. A Meta login pop-up opens. Log in with the Facebook account that has admin access to your ad account, then grant the requested permissions.
  </Step>

  <Step title="Select ad accounts">
    Choose which Meta ad accounts to import. You can add more accounts later without re-authenticating.
  </Step>

  <Step title="Save">
    Click **Save**. An initial data pull begins. Your Meta Ads KPI cards appear in Nerve Centre within a few minutes.
  </Step>
</Steps>

<Note>
  The Meta account you use to connect must have **Admin** or **Advertiser** access to the ad accounts you want to import. Analyst-level access does not grant the API permissions Vortex IQ requires.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="OAuth pop-up blocked">
    Disable your browser's pop-up blocker for `app.vortexiq.ai` and try again.
  </Accordion>

  <Accordion title="Ad accounts not appearing after connect">
    Only ad accounts where your Facebook user has Admin or Advertiser access are listed. Ask your Meta Business Manager admin to grant access, then reconnect.
  </Accordion>

  <Accordion title="Data stops refreshing">
    Meta OAuth tokens expire after 60 days. Go to **Settings → Connected Sources → Meta Ads → Reconnect** to re-authorise.
  </Accordion>

  <Accordion title="ROAS looks wrong">
    Vortex IQ reads ROAS as reported by Meta (click-attributed). If your attribution window differs from Meta's default, the ROAS card reflects Meta's attribution-not your internal model.
  </Accordion>
</AccordionGroup>


# Connect Microsoft Ads (Bing) to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/microsoft-ads

Connect Microsoft Ads (Bing) to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Microsoft Ads (Bing) to Vortex IQ gives the AI OS a live read on your Microsoft Ads (Bing) data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Microsoft Ads (Bing)

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Microsoft Ads (Bing) card">
    Locate the Microsoft Ads (Bing) connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Microsoft Ads (Bing)">
    You are redirected to Microsoft Ads (Bing)'s own authorisation page (`https://login.microsoftonline.com/common/oauth2/v2.0/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `https://ads.microsoft.com/msads.manage`, `offline_access`.
  </Step>

  <Step title="Return to Vortex IQ">
    Microsoft Ads (Bing) redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Microsoft Ads (Bing) API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your Microsoft Ads (Bing) data. See the [Microsoft Ads (Bing) KPI card reference](/nerve-centre/kpi-cards/microsoft-ads) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Microsoft Ads (Bing) developer console for typos or trailing whitespace. If a scope or permission is missing, Microsoft Ads (Bing) will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect NetSuite to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/netsuite

Connect NetSuite to Vortex IQ so Vortex Mind can reconcile ecommerce revenue against your GL, surface revenue leakage, and answer finance questions via Ask Viq.

Connecting NetSuite brings your ERP and general ledger data into Vortex IQ. Vortex Mind uses NetSuite to run the Daily Revenue Leakage report-reconciling gross ecommerce revenue (from Shopify, BigCommerce, or another commerce platform) against your NetSuite GL booking to identify where revenue is lost to fees, refunds, disputes, or timing gaps. Finance teams can then query this data directly through Ask Viq using a Finance Profile.

## What Vortex IQ reads from NetSuite

| Data type                      | Used by                                                               |
| ------------------------------ | --------------------------------------------------------------------- |
| General ledger entries         | Vortex Mind - Daily Revenue Leakage                                   |
| Sales orders and invoices      | Vortex Mind - Payment Performance Intelligence, Daily Revenue Leakage |
| Customer records               | Vortex Mind - Customer Recovery Opportunity                           |
| Refund and credit memo records | Vortex Mind - Daily Revenue Leakage, Decline Recovery Intelligence    |

## How to connect

NetSuite uses token-based authentication (TBA). You will need to create an integration record and generate access tokens inside NetSuite before connecting.

<Steps>
  <Step title="Create a NetSuite Integration Record">
    In NetSuite, go to **Setup → Integrations → Manage Integrations → New**. Name it "Vortex IQ", enable **Token-Based Authentication**, and save. Note the **Consumer Key** and **Consumer Secret**.
  </Step>

  <Step title="Create an Access Token">
    Go to **Setup → Users/Roles → Access Tokens → New**. Select the Integration you just created, select a user with the appropriate role, and save. Note the **Token ID** and **Token Secret**.
  </Step>

  <Step title="Open Connected Sources in Vortex IQ">
    Navigate to **Settings → Connected Sources**, click **Add Source**, and select **NetSuite**.
  </Step>

  <Step title="Enter credentials">
    Enter your NetSuite **Account ID**, **Consumer Key**, **Consumer Secret**, **Token ID**, and **Token Secret**, then click **Save**.
  </Step>

  <Step title="Verify">
    Vortex IQ runs a connection test. A successful test confirms credentials are valid and pulls begin.
  </Step>
</Steps>

<Warning>
  The NetSuite user associated with the access token must have read access to Transactions, Customers, and General Ledger records. Missing role permissions cause partial or failed data pulls.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authentication error on save">
    Double-check that TBA is enabled on the integration record in NetSuite, and that the Token ID/Secret match the token created for that integration (not a different one).
  </Accordion>

  <Accordion title="Revenue Leakage report shows no GL data">
    The NetSuite user's role must include read access to the **Transaction** and **Accounting Period** record types. Ask your NetSuite admin to verify role permissions.
  </Accordion>

  <Accordion title="Data refresh failing">
    NetSuite imposes concurrent API connection limits. If other integrations are polling heavily at the same time, Vortex IQ may hit rate limits. Use **Settings → Data Refresh** to stagger the NetSuite refresh cadence to off-peak hours.
  </Accordion>
</AccordionGroup>


# Connect OpenCart to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/opencart

Connect OpenCart to Vortex IQ for 31 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting OpenCart to Vortex IQ gives the AI OS a live read on your OpenCart data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from OpenCart

* **Product**
* **Order**
* **Customer**
* **Category**

## How to connect

<Note>
  OpenCart uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the OpenCart card">
    Locate the OpenCart connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from OpenCart">
    You will need:

    * **Store URL**: Base URL of the OpenCart store, e.g. [https://shop.example.com](https://shop.example.com)
    * **API Username**: API user created in Admin -> Users -> API.
    * **API Key**: Key paired with the API user; exchanged for a session token.
    * **OpenCart Version**: e.g. 4.0.2.0, needed for version-drift KPIs on this self-hosted platform.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where OpenCart offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **31** Nerve Centre cards from your OpenCart data. See the [OpenCart KPI card reference](/nerve-centre/kpi-cards/opencart) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the OpenCart developer console for typos or trailing whitespace. If a scope or permission is missing, OpenCart will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Outbrain to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/outbrain

Connect Outbrain to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Outbrain to Vortex IQ gives the AI OS a live read on your Outbrain data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Outbrain

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Outbrain card">
    Locate the Outbrain connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Outbrain">
    You are redirected to Outbrain's own authorisation page (`https://my.outbrain.com/amplify/api/oauth/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `read_marketer`, `read_campaigns`, `read_reports`.
  </Step>

  <Step title="Return to Vortex IQ">
    Outbrain redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Outbrain API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your Outbrain data. See the [Outbrain KPI card reference](/nerve-centre/kpi-cards/outbrain) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Outbrain developer console for typos or trailing whitespace. If a scope or permission is missing, Outbrain will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect PayPal to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/paypal

Connect PayPal to Vortex IQ to include transaction data in payment performance reports, revenue leakage analysis, and Vortex Mind cross-platform diagnostics.

Connecting PayPal allows Vortex IQ to include PayPal transaction data alongside your other payment gateways. Vortex Mind can then compare auth rates, refund rates, and dispute patterns across Stripe, PayPal, and any other connected payment processor-giving you a unified view of payment health rather than a per-gateway silo.

## What Vortex IQ reads from PayPal

| Data type                                      | Used by                                                               |
| ---------------------------------------------- | --------------------------------------------------------------------- |
| Transaction records (sales, refunds, disputes) | Vortex Mind - Payment Performance Intelligence, Daily Revenue Leakage |
| Decline and void records                       | Vortex Mind - Decline Recovery Intelligence                           |
| Checkout abandonment signals                   | Vortex Mind - Checkout Conversion Failure                             |
| Payout and fee data                            | Vortex Mind - Daily Revenue Leakage                                   |

## How to connect

<Steps>
  <Step title="Go to Connected Sources">
    Navigate to **Settings → Connected Sources** and click **Add Source**.
  </Step>

  <Step title="Select PayPal">
    Search for "PayPal" and select it from the catalogue.
  </Step>

  <Step title="Authorise via OAuth">
    Click **Connect**. You will be redirected to PayPal to log in and grant Vortex IQ read access to your transaction history. No write permissions are requested.
  </Step>

  <Step title="Select accounts">
    If you manage multiple PayPal accounts, select which ones to import.
  </Step>

  <Step title="Save">
    Click **Save**. The initial data pull begins. Vortex Mind reports that include PayPal data will reflect it on the next scheduled report run.
  </Step>
</Steps>

<Note>
  Vortex IQ requests **read-only** access to PayPal transaction data. It cannot initiate refunds, moves funds, or change your PayPal account settings.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="OAuth redirect fails">
    Ensure you are logged into the PayPal account with admin/owner access before clicking Connect. Sub-user accounts may not have sufficient permissions.
  </Accordion>

  <Accordion title="Historical data not appearing">
    PayPal's API returns up to 3 years of transaction history. The initial pull may take up to 30 minutes for accounts with high transaction volume.
  </Accordion>

  <Accordion title="Token expired">
    PayPal OAuth tokens expire periodically. Reconnect via **Settings → Connected Sources → PayPal → Reconnect**.
  </Accordion>
</AccordionGroup>


# Connect Pinterest Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/pinterest-ads

Connect Pinterest Ads to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Pinterest Ads to Vortex IQ gives the AI OS a live read on your Pinterest Ads data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Pinterest Ads

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Pinterest Ads card">
    Locate the Pinterest Ads connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Pinterest Ads">
    You are redirected to Pinterest Ads's own authorisation page (`https://www.pinterest.com/oauth/`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `ads:read`, `ads:write`, `catalogs:read`, `user_accounts:read`.
  </Step>

  <Step title="Return to Vortex IQ">
    Pinterest Ads redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Pinterest Ads API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your Pinterest Ads data. See the [Pinterest Ads KPI card reference](/nerve-centre/kpi-cards/pinterest-ads) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Pinterest Ads developer console for typos or trailing whitespace. If a scope or permission is missing, Pinterest Ads will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect PrestaShop to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/prestashop

Connect PrestaShop to Vortex IQ for 46 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting PrestaShop to Vortex IQ gives the AI OS a live read on your PrestaShop data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from PrestaShop

* **Order**
* **OrderDetail**
* **Product**
* **StockAvailable**
* **Customer**

## How to connect

<Note>
  PrestaShop uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the PrestaShop card">
    Locate the PrestaShop connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from PrestaShop">
    You will need:

    * **Store URL**: Storefront base URL, e.g. [https://shop.example.com](https://shop.example.com) - the Webservice lives at /api.
    * **Webservice API Key**: Advanced Parameters → Webservice → Add new key. Grant GET on orders, order\_details, products, stock\_availables, customers, addresses, currencies, order\_states. Sent as HTTP Basic username, empty password.
    * **PrestaShop Version**: 1.6 supported on request; 1.7 and 8.x are the build focus.
    * **Hosting Mode**: self\_hosted = merchant infrastructure; hosted\_cloud = PrestaShop Cloud (Hosted).
    * **Read-only DB DSN (optional)**: Optional read-only MySQL DSN for fields the Webservice does not expose (stock movements, derived OSS/VAT views). PrestaShop stays system of record.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where PrestaShop offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **46** Nerve Centre cards from your PrestaShop data. See the [PrestaShop KPI card reference](/nerve-centre/kpi-cards/prestashop) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the PrestaShop developer console for typos or trailing whitespace. If a scope or permission is missing, PrestaShop will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Quora Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/quora-ads

Connect Quora Ads to Vortex IQ for 75 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Quora Ads to Vortex IQ gives the AI OS a live read on your Quora Ads data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Quora Ads

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Note>
  Quora Ads uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Quora Ads card">
    Locate the Quora Ads connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from Quora Ads">
    You will need:

    * **OAuth Access Token**: Bearer token from Quora OAuth (scope: ads\_read). Register OAuth client via [ads-api-help@quora.com](mailto:ads-api-help@quora.com); exchange code at [https://www.quora.com/\_/oauth/token](https://www.quora.com/_/oauth/token).
    * **Account ID**: Quora Ads account ID, visible in Ads Manager URL (/ad\_account/) or account settings.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where Quora Ads offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **75** Nerve Centre cards from your Quora Ads data. See the [Quora Ads KPI card reference](/nerve-centre/kpi-cards/quora-ads) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Quora Ads developer console for typos or trailing whitespace. If a scope or permission is missing, Quora Ads will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Salesforce Commerce Cloud (B2C) to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/salesforce-commerce-cloud

Connect Salesforce Commerce Cloud (B2C) to Vortex IQ for 38 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Salesforce Commerce Cloud (B2C) to Vortex IQ gives the AI OS a live read on your Salesforce Commerce Cloud (B2C) data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Salesforce Commerce Cloud (B2C)

* **Product**
* **Order**
* **Customer**
* **Site**
* **ApiIntegration**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Salesforce Commerce Cloud (B2C) card">
    Locate the Salesforce Commerce Cloud (B2C) connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Salesforce Commerce Cloud (B2C)">
    You are redirected to Salesforce Commerce Cloud (B2C)'s own authorisation page. Sign in and approve the requested permissions. Vortex IQ requests these scopes: `SALESFORCE_COMMERCE_API:{tenant_id}.sandbox sfcc.shopper-orders.read sfcc.shopper-baskets.read`.
  </Step>

  <Step title="Return to Vortex IQ">
    Salesforce Commerce Cloud (B2C) redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Salesforce Commerce Cloud (B2C) API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **38** Nerve Centre cards from your Salesforce Commerce Cloud (B2C) data. See the [Salesforce Commerce Cloud (B2C) KPI card reference](/nerve-centre/kpi-cards/salesforce-commerce-cloud) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Salesforce Commerce Cloud (B2C) developer console for typos or trailing whitespace. If a scope or permission is missing, Salesforce Commerce Cloud (B2C) will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Shopify to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/shopify

Connect Shopify to Vortex IQ for 78 KPI cards, cross-platform alerts, Vortex Staging for safe deploys, and Vortex Backup for instant rollback.

Connecting your Shopify store to Vortex IQ gives the AI OS a live read on every order, variant, customer, and revenue movement in your store. The moment the connector goes active, Nerve Centre populates with Shopify-specific KPI cards, Vortex Mind gains a diagnostic surface for root-cause analysis, and Ask Viq can answer revenue and inventory questions in plain English.

## What data Vortex IQ reads from Shopify

Vortex IQ connects to the Shopify Admin GraphQL API and ingests the following data:

<AccordionGroup>
  <Accordion title="Orders and revenue">
    * Order totals (`totalPrice`) across all sales channels: Online Store, Shop POS, Buy Button, TikTok Shop, B2B, and any marketplace app channel
    * Financial status, fulfilment status, and cancellation state per order
    * Discount codes and discount amounts applied
    * Refunds and refund line items
    * Shipping amounts and methods
    * Tax amounts and tax inclusion flag
    * Payment gateway per order
  </Accordion>

  <Accordion title="Products and inventory">
    * All active product variants with `totalInventory` and per-location `InventoryLevel.available`
    * Product status (active, draft, archived)
    * Product type, vendor, and tags
    * SKU and barcode per variant
    * Collection membership
  </Accordion>

  <Accordion title="Customers">
    * Customer records with email verification state
    * Order frequency and lifetime value per customer
    * Customer geography (country, city)
    * New vs returning customer segmentation
  </Accordion>
</AccordionGroup>

<Note>
  Vortex IQ reads Shopify data using scheduled, rate-limited API calls. No customer-facing store performance is affected. All access is read-only; Vortex IQ never writes to your store.
</Note>

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Shopify card">
    Locate the Shopify connector card and click **+ Connect**. The connector drawer slides in showing the scopes Vortex IQ will request.
  </Step>

  <Step title="Authenticate with Shopify">
    Click **Connect with Shopify**. A new tab opens at Shopify's authorisation screen. Sign in with the account that has admin access to your store, then review the requested scopes and click **Install app**.
  </Step>

  <Step title="Select sandbox or production">
    If you want to test against a development store, toggle **Sandbox** before connecting. For a live store, leave it on **Production** (the default).
  </Step>

  <Step title="Wait for the first data pull">
    Shopify KPI cards appear in Nerve Centre within 5 to 15 minutes. A full historical order backfill takes 1 to 4 hours. You can navigate away while the pull runs in the background.
  </Step>
</Steps>

<Note>
  The scopes Vortex IQ requests are read-only: `read_orders`, `read_products`, `read_inventory`, `read_customers`, `read_analytics`. Vortex IQ does not request write scopes.
</Note>

## Available KPI cards

Vortex IQ populates 78 Nerve Centre cards from your Shopify data across the following categories.

<CardGroup>
  <Card title="Revenue and growth" icon="chart-line">
    **Total Revenue** - Gross revenue (`SUM(totalPrice)`) across all channels for the period, compared to the prior period. Alerts when revenue drops more than 15% vs prior 30 days.

    **Revenue Over Time** - Daily revenue trend with period-over-period sparkline.

    **Average Order Value (AOV)** - Revenue ÷ Order Count. Tells you whether a revenue move was driven by volume or basket size.

    **Revenue by Channel** - Breaks revenue by source (Online Store, POS, TikTok Shop, B2B, etc.).

    **Revenue by Day of Week** - Identifies your highest-revenue days for campaign timing.

    **Revenue by Hour** - Intra-day revenue pattern for staffing and ad scheduling.
  </Card>

  <Card title="Orders and operations" icon="box">
    **Order Count** - Total orders placed in the period.

    **Orders Over Time** - Daily order volume sparkline.

    **Unfulfilled Orders** - Count of orders awaiting fulfilment.

    **Fulfilment Rate** - Share of orders fulfilled within the expected window.

    **Cancellation Rate** - Cancelled orders as a share of total, with trend.

    **Financial Status** - Breakdown of orders by payment state (paid, pending, refunded, voided).
  </Card>

  <Card title="Inventory" icon="warehouse">
    **Products with Zero/Negative Stock** - Live count of active variants at zero or negative inventory. Alerts the moment any active variant hits zero. Negative inventory (oversold) is flagged as the most urgent subset.

    **Stock vs Sales** - Shows non-OOS variants heading toward stockout before they hit zero.

    **Inventory Distribution** - Fat-tail view of stock levels across your catalogue.

    **OOS Spike Alert** - Fires when the out-of-stock variant count rises sharply in a short window.
  </Card>

  <Card title="Customers" icon="users">
    **Customer Count** - Total active customers.

    **New Customers** - First-time buyers in the period.

    **Repeat Rate** - Share of customers who bought more than once.

    **Churn Risk** - Customers showing lapse signals.

    **Customer Segments** - Breakdown by RFM-style segment.

    **Top Customers** - Highest-value customers by lifetime spend.
  </Card>

  <Card title="Refunds and returns" icon="arrow-left">
    **Refund Rate** - Refunds as a share of orders in the period.

    **Refund Value** - Total value of refunds issued.

    **Refund Spike Alert** - Fires when the refund rate rises sharply.

    **Top Refunded Products** - Products with the highest refund frequency.

    **Refunds Over Time** - Daily refund trend.
  </Card>

  <Card title="Store health and alerts" icon="heart-pulse">
    **Store Health Score** - Composite 0-100 score blending revenue trend (30%), fulfilment rate (25%), refund rate (25%), and OOS count (20%). Alerts when the score falls below 70.

    **Revenue Drop Alert** - Fires when revenue drops more than 15% vs prior 30 days.

    **Fulfilment Delay Alert** - Fires when fulfilment rate drops below threshold.

    **Negative Review Burst Alert** - Fires on a sudden spike in low-rating signals.
  </Card>
</CardGroup>

### Cross-platform cards

When you connect ad platforms (Google Ads, Meta Ads, TikTok Ads) alongside Shopify, Vortex IQ unlocks additional cross-platform cards:

| Card                                  | What it shows                                                                           |
| ------------------------------------- | --------------------------------------------------------------------------------------- |
| Active Ads on Out-of-Stock SKUs       | Ad spend burning on variants with zero inventory - the highest-ROI cross-platform pause |
| Revenue at Risk from active incidents | Live revenue impact estimate when a Datadog or New Relic incident is open               |
| Catalogue Drift vs Amazon             | SKUs active on Amazon but OOS on Shopify - an inventory mis-sync and brand-trust risk   |
| Klaviyo Email Revenue Share           | Share of Shopify revenue attributable to Klaviyo email flows                            |
| Amazon Revenue Share                  | Comparison of Amazon marketplace revenue against Shopify direct                         |

## Vortex Staging and Vortex Backup apps

Shopify merchants get access to two dedicated Vortex IQ apps available in the Shopify App Store.

<Tabs>
  <Tab title="Vortex Staging">
    **Vortex Staging** gives your Shopify store a real staging environment - something Shopify itself does not provide natively.

    Key capabilities:

    * **Multi-environment linking** - Link Production, Staging, UAT, and Integration stores under one Vortex IQ tenant
    * **Bulk migration** - Clone the live storefront into a staging store in one operation; 20+ entity types covered including Products, Collections, Customers, Orders, Themes, Discount Codes, Gift Cards, Navigation Menus, URL Redirects, Metaobjects, and more
    * **Selective migration** - Pick specific products, themes, or collections when you need only a subset
    * **Customer data anonymisation** - Scramble PII when migrating to non-production environments so your team works against production-shaped volumes without touching real personal data
    * **Git-driven theme deployment** - Connect a GitHub repository and deploy theme changes through an approval workflow, with rollback to any previous version on demand
    * **Migration history and rollback** - Every migration is logged with per-entity progress and downloadable error logs
    * **Notifications** - Email, Slack, and Microsoft Teams alerts when migrations complete or fail

    Available in the Shopify App Store for standard, Shopify Advanced, and Shopify Plus plans.
  </Tab>

  <Tab title="Vortex Backup">
    **Vortex Backup** gives your Shopify store an undo button - something Shopify itself does not provide natively.

    Key capabilities:

    * **19 entity types covered** - Products, Collections, Customers, Orders, Discount Codes, Blogs, Pages, Files, Themes, Gift Cards, Navigation Menus, URL Redirects, Markets, Delivery Profiles, Locations, Price Lists, Catalogs, Metaobject Definitions, and Metaobjects
    * **Real-time webhook backup** for Products, Collections, Customers, and Orders - every change captured as Shopify fires the webhook
    * **Manual full backup** for the remaining entity types Shopify does not expose via webhook
    * **Per-record restore** - Roll back a single product, page, or delivery profile to any stored version without touching anything else in the store
    * **Side-by-side version comparison** - Compare any two stored versions in Summary or JSON view before deciding to restore
    * **Theme backup with full ZIP archive** - Restore creates a new theme; your live theme is never overwritten
    * **File and media backup to Azure Blob Storage** - Images, videos, 3D models, documents

    Available in the Shopify App Store.
  </Tab>
</Tabs>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The OAuth pop-up was blocked">
    Allow pop-ups for `app.vortexiq.ai` in your browser settings. Brave and Firefox with strict mode block pop-ups by default. After allowing, click **+ Connect** again.
  </Accordion>

  <Accordion title="Shopify says 'this app does not have access to your account'">
    You are signed into Shopify with an account that does not have admin access to the store you want to connect. Sign out of Shopify, sign in with the store owner or admin account, then retry the connection from Vortex IQ.
  </Accordion>

  <Accordion title="KPI cards are empty after connecting">
    The first data pull typically completes within 5 to 15 minutes for KPI cards and up to 4 hours for full historical orders. If cards are still empty after 4 hours, open **Settings → Connected Sources**, find your Shopify connection, and use the manual refresh control to trigger a new pull.
  </Accordion>

  <Accordion title="Revenue in Vortex IQ differs from Shopify Admin">
    Several legitimate reasons cause small differences: time-zone boundaries (Shopify reports run on shop timezone; Vortex IQ runs on UTC by default), test orders (Vortex IQ does not yet filter `Order.test = true`), and multi-currency stores (Vortex IQ sums `totalPrice` in each order's own currency without FX conversion). For multi-currency stores, use the currency-filtered view in Nerve Centre.
  </Accordion>

  <Accordion title="OOS card count does not match Shopify Admin">
    Vortex IQ aggregates inventory across all active fulfilment locations. A variant with zero stock in one location but stock available in another will not appear on the OOS card. Shopify Admin shows per-location inventory by default. To match the card, filter Shopify Admin → Products → Inventory to Active status and view the aggregate Available total.
  </Accordion>
</AccordionGroup>


# Connect Shopline to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/shopline

Connect Shopline to Vortex IQ for 52 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Shopline to Vortex IQ gives the AI OS a live read on your Shopline data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Shopline

* **Order**
* **Product**
* **Customer**
* **InventoryLevel**
* **Channel**

## How to connect

<Note>
  Shopline uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Shopline card">
    Locate the Shopline connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from Shopline">
    You will need:

    * **API Token (JWT Bearer)**: Long-lived HS512 JWT issued by the Shopline seller portal. Sent as 'Authorization: Bearer '. Decode the payload to read sellerId, storeId, and exp; store those alongside the raw token. Phillipstoys' token expires 2027-07-24.
    * **API Region**: Shopline runs region-pinned hosts. Maps to base\_url: us → sl-open-us.myshopline.com, apac → sl-open-apac.myshopline.com, asean → sl-open-asean.myshopline.com. Cross-check the JWT payload's `domain` claim, it's the source of truth.
    * **Storefront Handle**: myshopline.com subdomain (e.g. phillipstoys3.myshopline.com, the merchant-facing storefront, NOT the open-api host). Used for deep-links into the Shopline admin from finding rows.
    * **App Key**: Shopline developer app identifier (decoded from the JWT `appKey` claim). Captured at credential-import; not required on every request.
    * **Seller ID**: Decoded from the JWT `sellerId` claim. Useful for support tickets + cross-store dedup if the same merchant runs more than one Shopline store.
    * **Store ID**: Decoded from the JWT `storeId` claim. The unique store identifier within Shopline's seller graph.
    * **Token Expiry**: Decoded from the JWT `exp` claim at credential-import. Powers the auth\_token\_expiry alert card.
    * **API Version**: Shopline API revision pinned in the URL (e.g. /admin/openapi/v20241201/orders.json). Phillipstoys is on v20241201; new merchants should use the latest documented.
    * **Webhook Secret**: Optional HMAC secret if the merchant has wired Shopline webhooks for order/refund events. Used to verify X-SL-Hmac-Sha256 on inbound POSTs.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where Shopline offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **52** Nerve Centre cards from your Shopline data. See the [Shopline KPI card reference](/nerve-centre/kpi-cards/shopline) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Shopline developer console for typos or trailing whitespace. If a scope or permission is missing, Shopline will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Snapchat Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/snapchat-ads

Connect Snapchat Ads to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Snapchat Ads to Vortex IQ gives the AI OS a live read on your Snapchat Ads data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Snapchat Ads

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Snapchat Ads card">
    Locate the Snapchat Ads connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Snapchat Ads">
    You are redirected to Snapchat Ads's own authorisation page (`https://accounts.snapchat.com/login/oauth2/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `snapchat-marketing-api`.
  </Step>

  <Step title="Return to Vortex IQ">
    Snapchat Ads redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Snapchat Ads API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your Snapchat Ads data. See the [Snapchat Ads KPI card reference](/nerve-centre/kpi-cards/snapchat-ads) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Snapchat Ads developer console for typos or trailing whitespace. If a scope or permission is missing, Snapchat Ads will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Square Online to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/square-online

Connect Square Online to Vortex IQ for 41 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Square Online to Vortex IQ gives the AI OS a live read on your Square Online data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Square Online

* **CatalogItem**
* **Order**
* **Customer**
* **Location**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Square Online card">
    Locate the Square Online connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Square Online">
    You are redirected to Square Online's own authorisation page (`https://connect.squareup.com/oauth2/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `MERCHANT_PROFILE_READ`, `ITEMS_READ`, `ORDERS_READ`, `CUSTOMERS_READ`, `INVENTORY_READ`.
  </Step>

  <Step title="Return to Vortex IQ">
    Square Online redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Square Online API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **41** Nerve Centre cards from your Square Online data. See the [Square Online KPI card reference](/nerve-centre/kpi-cards/square-online) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Square Online developer console for typos or trailing whitespace. If a scope or permission is missing, Square Online will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect StackAdapt to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/stackadapt

Connect StackAdapt to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting StackAdapt to Vortex IQ gives the AI OS a live read on your StackAdapt data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from StackAdapt

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the StackAdapt card">
    Locate the StackAdapt connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with StackAdapt">
    You are redirected to StackAdapt's own authorisation page (`https://api.stackadapt.com/oauth/authorize`). Sign in and approve the requested permissions. Vortex IQ requests these scopes: `read`.
  </Step>

  <Step title="Return to Vortex IQ">
    StackAdapt redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the StackAdapt API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your StackAdapt data. See the [StackAdapt KPI card reference](/nerve-centre/kpi-cards/stackadapt) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the StackAdapt developer console for typos or trailing whitespace. If a scope or permission is missing, StackAdapt will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Stripe to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/stripe

Connect Stripe to Vortex IQ so Vortex Mind can analyse payment performance, decline patterns, and revenue leakage using real transaction-level data.

Connecting Stripe gives Vortex IQ access to your payment transaction data. Vortex Mind uses this to power Payment Performance Intelligence and Decline Recovery Intelligence reports-diagnosing auth rate drops, BIN-level decline patterns, gateway error codes, and recoverable revenue from failed transactions. Nerve Centre surfaces the resulting KPI cards, and Ask Viq can answer payment-specific questions in plain English.

## What Vortex IQ reads from Stripe

Stripe feeds the following Vortex Mind report types directly:

| Report                           | What Stripe data it uses                                                 |
| -------------------------------- | ------------------------------------------------------------------------ |
| Payment Performance Intelligence | Auth rates, decline reason codes, payment method mix, BIN-level patterns |
| Decline Recovery Intelligence    | Failed charge amounts, retry eligibility, recoverable revenue estimate   |
| Checkout Conversion Failure      | Checkout abandonment correlated with payment errors                      |
| Daily Revenue Leakage            | Gross vs net revenue, refunds, disputes, fee deductions                  |

KPI cards populated in Nerve Centre include payment success rate, decline rate by payment method, dispute rate, refund rate, and revenue after fees.

## How to connect

<Steps>
  <Step title="Go to Connected Sources">
    Navigate to **Settings → Connected Sources** and click **Add Source**.
  </Step>

  <Step title="Select Stripe">
    Search for "Stripe" and select it from the catalogue.
  </Step>

  <Step title="Enter your Stripe Restricted Key">
    Vortex IQ uses a Stripe **Restricted API Key** (not your secret key). In your Stripe Dashboard, go to **Developers → API Keys → Create Restricted Key** with read permissions on: Charges, Customers, PaymentIntents, Refunds, Disputes, and Balance Transactions.
  </Step>

  <Step title="Paste the key into Vortex IQ">
    Enter the restricted key in the connection form and click **Save**.
  </Step>

  <Step title="Verify">
    Vortex IQ runs a connection test. A green status indicator confirms the key is valid and data pull has started.
  </Step>
</Steps>

<Warning>
  Never paste your Stripe **Secret Key** into Vortex IQ. Use a Restricted Key scoped to read-only access on the resources listed above.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection test fails">
    Verify the restricted key has read access on Charges and PaymentIntents. Missing permissions on either resource cause the connection test to fail.
  </Accordion>

  <Accordion title="No data appearing in reports">
    Stripe data is pulled on a daily refresh by default. If you just connected, wait until the following day's refresh cycle or click **Refresh Now** in **Settings → Data Refresh**.
  </Accordion>

  <Accordion title="Decline reason codes not showing">
    Decline reason codes require the **Charges** read permission. Confirm the restricted key includes this scope.
  </Accordion>
</AccordionGroup>


# Connect Swell to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/swell

Connect Swell to Vortex IQ for 42 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Swell to Vortex IQ gives the AI OS a live read on your Swell data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Swell

* **Order**
* **Subscription**
* **Product**
* **Account**
* **Invoice**
* **Payment**
* **Refund**

## How to connect

<Note>
  Swell uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Swell card">
    Locate the Swell connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from Swell">
    You will need:

    * **Store ID**: Your Swell store identifier (the subdomain of .swell.store). Used as the Basic auth username and the host prefix.
    * **Secret API Key**: Generate in Swell dashboard → Developer → API keys → Secret key. Full backend access - shown once on creation.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where Swell offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **42** Nerve Centre cards from your Swell data. See the [Swell KPI card reference](/nerve-centre/kpi-cards/swell) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Swell developer console for typos or trailing whitespace. If a scope or permission is missing, Swell will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect Taboola to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/taboola

Connect Taboola to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Taboola to Vortex IQ gives the AI OS a live read on your Taboola data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Taboola

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Taboola card">
    Locate the Taboola connector card and click **+ Connect**.
  </Step>

  <Step title="Authorise with Taboola">
    You are redirected to Taboola's own authorisation page. Sign in and approve the requested permissions.
  </Step>

  <Step title="Return to Vortex IQ">
    Taboola redirects you back to Vortex IQ once authorisation completes. The connector card flips to Connected automatically; no credentials are copied by hand.
  </Step>

  <Step title="Wait for the first data pull">
    KPI cards begin populating once the first sync completes. Timing depends on the Taboola API response size and rate limits.
  </Step>
</Steps>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your Taboola data. See the [Taboola KPI card reference](/nerve-centre/kpi-cards/taboola) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Taboola developer console for typos or trailing whitespace. If a scope or permission is missing, Taboola will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect The Trade Desk to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/the-trade-desk

Connect The Trade Desk to Vortex IQ for 72 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting The Trade Desk to Vortex IQ gives the AI OS a live read on your The Trade Desk data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from The Trade Desk

* **AdAccount**
* **Campaign**
* **AdCreative**

## How to connect

<Note>
  The Trade Desk uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the The Trade Desk card">
    Locate the The Trade Desk connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from The Trade Desk">
    You will need:

    * **TTD API Token**: Long-lived API token issued from TTD UI → Settings → API Tokens. Sent as TTD-Auth header. Rotate manually before expiry.
    * **Partner ID**: TTD Partner ID, find under Partner Settings. Required for cross-advertiser reporting.
    * **Advertiser ID**: TTD Advertiser ID, find under Advertiser → Settings. One per brand/agency client.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where The Trade Desk offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **72** Nerve Centre cards from your The Trade Desk data. See the [The Trade Desk KPI card reference](/nerve-centre/kpi-cards/the-trade-desk) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the The Trade Desk developer console for typos or trailing whitespace. If a scope or permission is missing, The Trade Desk will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect TikTok Ads to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/tiktok-ads

Link TikTok Ads to Vortex IQ to track spend, ROAS, conversions, and creative performance across your TikTok campaigns alongside all your other ad platforms.

Connecting TikTok Ads brings your TikTok campaign metrics into Nerve Centre alongside every other ad platform in your stack. Vortex Mind can then cross-reference TikTok spend against your commerce platform revenue to identify paid traffic waste and conversion drop patterns-without you switching between dashboards.

## What Vortex IQ reads from TikTok Ads

| Category             | Example cards                                                                                |
| -------------------- | -------------------------------------------------------------------------------------------- |
| Executive Overview   | Total Spend, Total Revenue, ROAS, CPA Trend, Impressions Trend, Clicks vs Conversions        |
| Budget Monitoring    | Spend vs Budget, Budget Utilisation, Overspending Campaigns, Underspending Campaigns         |
| Campaign Performance | ROAS by Campaign, Revenue by Campaign, Conversion Rate by Campaign, Top Performing Campaigns |
| Funnel & Conversion  | Conversion Funnel, Conversion Lag, Conversion Rate Trend, Conversion Actions Breakdown       |
| Alerts & Anomalies   | Conversion Drop Alert, CPC Anomaly, CTR Decline Alert, Spend Anomaly, Zero-Conversion Spend  |
| Geography            | Conversions by Country, Spend by Country, Top Cities by Conversions                          |
| Device               | Conversion Rate by Device, ROAS by Device, Spend by Device                                   |
| Day & Time           | Conversions by Hour, Spend by Hour, Conversions by Day of Week                               |

## How to connect

<Steps>
  <Step title="Go to Connected Sources">
    Navigate to **Settings → Connected Sources** and click **Add Source**.
  </Step>

  <Step title="Select TikTok Ads">
    Search for "TikTok Ads" and select it from the catalogue.
  </Step>

  <Step title="Authorise via OAuth">
    Click **Connect**. A TikTok login pop-up opens. Log in with the account that has admin access to your TikTok Ads account, then grant the required permissions.
  </Step>

  <Step title="Select ad accounts">
    Choose which TikTok ad accounts to import. Multiple accounts can be added in one connection.
  </Step>

  <Step title="Save">
    Click **Save**. Nerve Centre populates your TikTok Ads KPI cards once the initial data pull completes.
  </Step>
</Steps>

<Note>
  You need **Admin** access on the TikTok Ads account. Operator-level access may not expose all required API scopes.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="No data after connecting">
    TikTok Ads requires at least one active or recently active campaign to return data. If your account has no spend in the last 90 days, some cards may show empty states.
  </Accordion>

  <Accordion title="OAuth pop-up blocked">
    Allow pop-ups from `app.vortexiq.ai` in your browser settings and retry the connection.
  </Accordion>

  <Accordion title="Token expired">
    TikTok OAuth tokens require periodic re-authorisation. Go to **Settings → Connected Sources → TikTok Ads → Reconnect**.
  </Accordion>
</AccordionGroup>


# Connect Volusion to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/volusion

Connect Volusion to Vortex IQ for 33 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting Volusion to Vortex IQ gives the AI OS a live read on your Volusion data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from Volusion

* **Order**
* **Product**
* **Customer**
* **Refund**
* **InventoryLevel**

## How to connect

<Note>
  Volusion uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the Volusion card">
    Locate the Volusion connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from Volusion">
    You will need:

    * **Store URL**: Your Volusion store host, e.g. [https://www.yourstore.com](https://www.yourstore.com) - every API and CSV-export call is relative to it.
    * **API Token / Encrypted Password**: Volusion API token (modern API) or the EncryptedPassword for the generic CSV export. Generate under Account → API.
    * **API Login**: API Login user for the classic generic export endpoint (paired with the Encrypted Password).
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where Volusion offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **33** Nerve Centre cards from your Volusion data. See the [Volusion KPI card reference](/nerve-centre/kpi-cards/volusion) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the Volusion developer console for typos or trailing whitespace. If a scope or permission is missing, Volusion will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Connect WooCommerce to Vortex IQ
Source: https://docs.vortexiq.ai/integrations/woocommerce

Connect WooCommerce to Vortex IQ for 63 KPI cards, plus cross-platform Vortex Mind diagnostics.

Connecting WooCommerce to Vortex IQ gives the AI OS a live read on your WooCommerce data, feeding the Nerve Centre dashboard, Vortex Mind diagnostics, and Ask Viq.

## What data Vortex IQ reads from WooCommerce

* **Product**
* **Order**
* **Customer**
* **Coupon**
* **ProductReview**

## How to connect

<Note>
  WooCommerce uses credential-based authentication rather than OAuth. You provide these values directly rather than approving a redirect.
</Note>

<Steps>
  <Step title="Open Connected Sources">
    In your Vortex IQ workspace, go to **Settings → Connected Sources**. You need Admin role in the workspace to connect sources.
  </Step>

  <Step title="Find the WooCommerce card">
    Locate the WooCommerce connector card and click **+ Connect**. The connector drawer opens with a credential form.
  </Step>

  <Step title="Gather your credentials from WooCommerce">
    You will need:

    * **Store URL**: Per-merchant WordPress site URL where WooCommerce is installed (e.g. [https://merchant.com](https://merchant.com)). Substituted into base\_url; /wp-json/wc/v3 appended automatically.
    * **Consumer Key (ck\_)**: From WooCommerce > Settings > Advanced > REST API. Prefix 'ck\_'.
    * **Consumer Secret (cs\_)**: Paired with Consumer Key, shown once on creation. Prefix 'cs\_'.
  </Step>

  <Step title="Enter credentials in Vortex IQ">
    Paste each value into its matching field in the connector drawer.
  </Step>

  <Step title="Verify and connect">
    Click **Verify and Connect**. Vortex IQ makes a test API call to validate the credentials before saving them.
  </Step>
</Steps>

<Note>
  Vortex IQ only ever requests read-only access. Where WooCommerce offers scoped or read-only API keys, use one.
</Note>

## Available KPI cards

Vortex IQ populates **63** Nerve Centre cards from your WooCommerce data. See the [WooCommerce KPI card reference](/nerve-centre/kpi-cards/woocommerce) for the full list with definitions, calculations, and sentiment bands.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Credential verification fails">
    Re-check each value against the WooCommerce developer console for typos or trailing whitespace. If a scope or permission is missing, WooCommerce will typically return a 401 or 403 on the verification call rather than a generic failure.
  </Accordion>

  <Accordion title="Cards show no data after connecting">
    Allow time for the first sync to complete; large accounts can take longer. If cards are still empty after an hour, disconnect and reconnect to confirm the credentials were saved correctly.
  </Accordion>
</AccordionGroup>


# Set up and manage real-time alerts in Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/alerts

Nerve Centre alert cards fire when a metric breaks its expected pattern. Each alert routes to your Kanban Board with severity, owner, and full context attached.

A dashboard that only renders numbers is a passive surface - you have to remember to look. The Nerve Centre is built around the opposite principle: every card can fire an alert when its metric crosses a defined threshold or breaks an expected pattern, and alerts route into a triage queue with severity, owner, and supporting context already attached. You do not need to set up alert rules from scratch. Every card ships with a recipe-driven default threshold tuned to the metric's behaviour.

## What an alert is

An alert is a structured event emitted by the Nerve Centre runtime when a card's underlying metric meets a fire condition. Every alert carries:

* **Card reference** - the card ID, connector key, and current metric value
* **Trigger reason** - which fire condition matched (threshold breach, anomaly score, or missing data)
* **Severity** - Critical, High, Medium, Low, or Info
* **Period** - the time window the metric was evaluated against
* **Baseline** - the reference value the metric was compared to
* **Delta** - absolute and percentage change from the baseline
* **Trace ID** - a stable identifier for the alert run, used downstream to deduplicate

Alerts are first-class objects. They have an ID, a state, an audit trail, and you can query them after the fact from the alert history at **Nerve Centre header → alert count badge → History**.

## How alerts fire

A card fires an alert when at least one of three conditions is met.

### Threshold breach

The most common case. The card carries an `alert_trigger` field describing a numeric threshold:

| Example trigger                          | Metric                                               | Connector  |
| ---------------------------------------- | ---------------------------------------------------- | ---------- |
| `drop >25% vs prior 7D same-DOW`         | ROAS Drop Alert (`gads_alert_roas_drop`)             | Google Ads |
| `any keyword CPC >2× 30D baseline`       | CPC Spike Alert (`gads_alert_cpc_spike`)             | Google Ads |
| `>$0 (any campaign with spend, no conv)` | Zero-Conversion Spend (`gads_zero_conversion_spend`) | Google Ads |
| `drop >15% vsP`                          | Total Revenue                                        | Shopify    |
| `auth_rate < 0.85`                       | Authorisation Rate                                   | Stripe     |
| `refund_rate > 0.04`                     | Refund Rate                                          | Shopify    |
| `latency_p95 > 2500ms`                   | Checkout Latency p95                                 | Datadog    |

Threshold conditions are evaluated on every card refresh. The runtime keeps a fire-state per card so a flapping metric (one that crosses and uncrosses repeatedly) does not spam the Kanban: it fires once on the first crossing, then sends a resolved event when the metric returns to its band.

### Anomaly score

Some metrics do not have a fixed threshold but should still alert when they break their pattern. A merchant whose typical Sunday traffic is 60 percent of weekday traffic does not want a static "below 70 percent" rule - they want "this Sunday is unusually quiet versus what Sundays usually look like for me."

The Nerve Centre runs a statistical anomaly detector on every card with `has_threshold: true`. It computes a rolling baseline (typically 28 to 90 days), the variance, and a z-score for the latest reading. A z-score outside the configured band (default: ±2.5 sigma) fires an alert with `trigger_reason: anomaly`.

Anomaly alerts carry a confidence component: a 3-sigma move with 90 days of baseline is more credible than a 3-sigma move on 14 days of history. Low-confidence anomaly alerts are automatically downgraded to a lower severity tier.

### Missing data

A connector can stop publishing data because of an OAuth expiry, a vendor API outage, or a refresh rate-limit. The Nerve Centre treats prolonged data absence as a fire condition. If a card has not received fresh data for more than its expected refresh window plus a tolerance (typically 1.5×), an alert fires with `trigger_reason: data_gap` and the card shows a "stale" badge.

## Alert severity tiers

Every alert carries one of five severity tiers. Severity is set by the card's recipe at fire time and reflects the business impact of the metric movement.

| Severity   | Default treatment                                                                             | Example                                                            |
| ---------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| `critical` | Pages the on-call contact. Kanban auto-routes to top of queue. Badge turns red.               | Stripe authorisation rate drops below 50 percent (payment outage). |
| `high`     | Kanban card created with priority flag. Surfaces in the next briefing.                        | Total Revenue drops 18 percent versus prior period.                |
| `medium`   | Kanban card created without priority flag. Surfaces in the next weekly report.                | Refund rate climbs from 3.2 percent to 4.4 percent.                |
| `low`      | Surfaces inline on the card with a sentiment colour change. No Kanban card unless subscribed. | AOV drifts down 4 percent.                                         |
| `info`     | Pure context, no Kanban routing.                                                              | "Total Revenue is back inside its band" - a resolved event.        |

<Warning>
  Severity is recipe-driven, not metric-size-driven. A 5 percent revenue drop is critical for one merchant and routine noise for another. The workspace admin can override the default severity bands under **Settings → Alerts → Alert Rules**.
</Warning>

## Real alert card examples

### ROAS Drop Alert - `gads_alert_roas_drop` (Key Metrics)

A real-time (`RT`) Key Metrics alert on Google Ads. Fires when today's ROAS drops more than 25 percent versus the average ROAS on the same day of week over the prior seven days. The card is suppressed before 14:00 local time to avoid false positives from incomplete morning data (Google Ads conversion data has a 1-4 hour ingestion lag).

When this alert fires, the first diagnostic step is to open the Clicks vs Conversions card (`gads_clicks_vs_conversions`). If clicks held but conversions dropped sharply, the most common cause is a broken conversion pixel on the checkout confirmation page - not a performance regression. The card documentation includes a full worked example with a UK fashion brand showing a 60 percent ROAS drop traced to a developer change that removed the Google Ads conversion tag.

### CPC Spike Alert - `gads_alert_cpc_spike`

A real-time Supporting Metrics alert on Google Ads. Fires when any keyword's cost-per-click exceeds twice its 30-day baseline. Causes include auction-side competition (a competitor entered the auction), Quality Score drop, or a bid-strategy misconfiguration. The alert appears in the Alerts & Anomalies category on the Google Ads connector tab.

### Wasted-Spend Burst Alert - `gads_alert_wasted_spend_burst`

Fires when wasted spend (spend on search terms that produced zero conversions) increases sharply within a defined window. Signals that keyword targeting or match types have widened to attract irrelevant traffic.

### Disapproved-Ad Burst Alert - `gads_alert_disapproved_burst`

Fires when the number of disapproved ads in a Google Ads account increases above a threshold. Disapproval bursts often follow automated creative uploads or policy changes.

### Conversion-Tracking-Broken Alert - `gads_alert_conversion_tracking_broken` (Key Metrics)

A Key Metrics alert that watches the click-to-conversion ratio across the account. When the ratio falls far below its baseline while clicks remain stable, the most likely cause is a conversion pixel outage rather than genuine performance decline. This is the most actionable alert in the ad-platform archetype because the fix (restoring the tag) is quick and the cost of not fixing it (wasted spend on unmeasured campaigns) compounds every hour.

### Shopify Alerts

Shopify carries its own dedicated alert cards in the same Alerts & Anomalies category:

* `shp_alert_revenue_drop` - fires when revenue falls beyond the threshold versus the prior comparable period.
* `shp_alert_refund_spike` - fires when refund rate climbs above the configured threshold.
* `shp_alert_oos_spike` - fires when out-of-stock SKUs increase sharply, indicating an inventory event.
* `shp_alert_fulfilment_delay` - fires when unfulfilled orders age past the SLA threshold.
* `shp_alert_negative_review_burst` - fires when negative review volume spikes.

## How to respond to an alert

<Steps>
  <Step title="See the alert in the Nerve Centre">
    The alert count badge (top-right of the Nerve Centre header) updates in real time. Connector tabs with active alerts show a coloured dot on the tab label. Card tiles with active alerts show a coloured border and render their primary value in the alert's sentiment colour.
  </Step>

  <Step title="Open the alert details">
    Click the alert badge or click directly on the card tile to open the alert detail panel. The panel shows the current value, the baseline the metric was compared to, the delta, the trigger reason, and a link to the card's full documentation page.
  </Step>

  <Step title="Check sibling cards">
    Every alert card has a set of sibling cards that help you triage. For a ROAS Drop Alert, open Clicks vs Conversions first (30-second triage: did clicks drop too, or only conversions?). For a Spend Anomaly, open Spend by Campaign to identify which campaign moved. The card documentation page lists the recommended siblings.
  </Step>

  <Step title="Invoke Vortex Mind">
    For High and Critical alerts, Vortex Mind automatically starts a diagnostic run with the alert as the trigger anchor. For Medium and Low alerts, you can invoke the diagnostic manually by clicking **Investigate** on the alert detail panel. Vortex Mind walks the connector graph, gathers cross-connector evidence, and produces a structured finding.
  </Step>

  <Step title="Act on the Kanban">
    High and Critical alerts that pass the severity threshold create a card on the Actions Kanban. Move the card through Pending Review → In Progress → Done as you triage. The original alert and any Vortex Mind finding remain backlinked to the Action card for audit purposes.
  </Step>
</Steps>

## How alerts connect to Vortex Mind findings

Alerts and Vortex Mind findings share the same severity vocabulary. When a high or critical alert fires:

1. The alert event is emitted by the card runtime.
2. Vortex Mind picks it up and starts a diagnostic run, using the card's metric ID as the anchor.
3. Vortex Mind walks the connector graph, gathering evidence from related connectors (for example, a Google Ads ROAS Drop Alert triggers Vortex Mind to check Shopify order volume, GA4 Paid Search revenue, and the Clicks vs Conversions card before concluding whether it is a measurement break or a real performance decline).
4. The diagnostic produces a structured finding with severity and confidence attached.
5. If the finding qualifies, it promotes to an Action on the Kanban.

When the alert resolves (the metric returns to its band), a resolved event fires with `severity: info`, the Action card moves to Done, and Vortex Memory archives the alert with its evidence for future pattern matching.

## Configure alert channels and routing

You can customise where alerts surface under **Settings → Alerts**.

| Channel         | Default behaviour                                                                     |
| --------------- | ------------------------------------------------------------------------------------- |
| In-app banner   | Always on. Alert count badge updates in real time.                                    |
| Email           | Daily digest by default. Critical alerts send immediately.                            |
| Slack           | Webhook-based. Default floor: High and above. Configure per channel and per severity. |
| Microsoft Teams | Same model as Slack.                                                                  |
| PagerDuty       | Critical alerts only, via a PagerDuty integration key.                                |
| Webhook         | Generic JSON POST for partner integrations.                                           |

<Tip>
  A common Slack setup: route `critical` alerts to `#vortex-iq-critical` and all alerts to `#vortex-iq-all`. Set quiet hours per channel (for example, no pings between 22:00 and 07:00 local) so high-severity alerts still reach on-call but low-severity alerts wait for morning.
</Tip>

## Adjust alert thresholds

The **Dashboard Settings** page (gear icon on any connector tab, or navigate to `/v2/dashboard-settings`) includes an **Alert Rules** tab. For each alerting card you see:

* The current green target value
* The current red threshold value
* An alert-threshold slider (Very high / High / Medium / Low)
* A **Reset to defaults** button per category

Customisations are versioned and audit-trailed. You can see who changed a threshold and when, and revert to the recipe default at any time.

<Note>
  Tightening a sentiment threshold also tightens the alert threshold unless you decouple the two under the advanced settings for that card. Widening the threshold during a known event (a Black Friday promotional period, for example) prevents false-positive alerts without disabling the card's monitoring.
</Note>


# Connect data sources to Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/connectors

Nerve Centre connectors are organised into the same categories you see in Settings → Connected Sources. Connect a source once and every KPI card for that connector appears in your dashboard automatically.

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.

Vortex IQ connects **over 200 data sources**, grouped into the same **[categories](#connectors-by-category)** you see in **Settings → Connected Sources**. For the full A-Z list, see the [connector catalogue](/integrations/connector-catalogue).

## How connectors work

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-Platform Metrics 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.

## Data sources and channels

Every connector belongs to one of two classes, and the class determines whether it appears on the Nerve Centre with KPI cards.

<CardGroup>
  <Card title="Data sources" icon="database">
    Systems that hold auditable state: commerce platforms, marketplaces, ad platforms, payment gateways, analytics, CRM, email marketing, shipping, monitoring and databases.

    They carry the full KPI card set, an audit profile, and alert thresholds.
  </Card>

  <Card title="Channels" icon="paper-plane">
    Where Vortex IQ sends alerts and receives messages: Slack, Microsoft Teams, Telegram, Discord, Twilio, Pushover and email.

    Channels are health-checked, never audited, and carry no business KPI cards.
  </Card>
</CardGroup>

A channel may show a small number of **connection-health cards**, for example whether its webhook is configured and which host it points at, so you can confirm alerts are reaching the right place. These are diagnostics, not business metrics. If a revenue-critical alert is routed to a channel the Vortex IQ app has been removed from, that is what these cards are there to catch.

<Note>
  Email marketing platforms such as Klaviyo, Mailchimp, Brevo and SendGrid are **data sources**, not channels. They measure campaign performance, deliverability and revenue per send, so they carry full KPI cards. The channel class covers only the alert-delivery surfaces listed above.
</Note>

## Connect a new source

<Steps>
  <Step title="Open Connected Sources">
    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 connector-type filter for the full catalogue.
  </Step>

  <Step title="Find the connector">
    Search by connector name (for example, "Shopify" or "Google Ads") or browse by type. Each connector card shows the connector type, the number of cards it unlocks, and its connection method (OAuth, API key, or webhook).
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Review your new connector tab">
    Open the Nerve Centre. A new tab appears for the connected source. Key Metrics cards are already rendering. Browse by category or use the Key Metrics only filter to see the key metrics immediately.
  </Step>
</Steps>

<Note>
  Cross-Platform Metrics 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-Platform Metrics card shows a "Connect \[connector] to unlock" placeholder on the tab.
</Note>

## Connectors by category

Every connector below maps to a category in **Settings → Connected Sources**. Each connector links to its full card catalogue; its Key Metrics cards link straight to their pages.

### E-commerce Platforms

<AccordionGroup>
  <Accordion title="Acumatica">
    [Open the Acumatica connector page →](/nerve-centre/kpi-cards/acumatica)
  </Accordion>

  <Accordion title="Adobe Commerce · 59 cards">
    **Key Metrics cards:** [B2B Accounts Gone Quiet](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet), [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert), [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders), [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue), [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)

    [View all 59 cards →](/nerve-centre/kpi-cards/adobe-commerce)
  </Accordion>

  <Accordion title="Bigcartel">
    [Open the Bigcartel connector page →](/nerve-centre/kpi-cards/bigcartel)
  </Accordion>

  <Accordion title="BigCommerce · 105 cards">
    **Key Metrics cards:** [Channel Revenue Drop Alert](/nerve-centre/kpi-cards/bigcommerce/channel-revenue-drop-alert), [Declined Transaction Rate](/nerve-centre/kpi-cards/bigcommerce/declined-transaction-rate), [Fulfillment Rate](/nerve-centre/kpi-cards/bigcommerce/fulfillment-rate), [OOS Listings per Channel](/nerve-centre/kpi-cards/bigcommerce/oos-listings-per-channel), [Products with Zero/Negative Stock](/nerve-centre/kpi-cards/bigcommerce/products-with-zero-negative-stock)

    [View all 105 cards →](/nerve-centre/kpi-cards/bigcommerce)
  </Accordion>

  <Accordion title="Ecwid · 12 cards">
    **Key Metrics cards:** [Average Order Value](/nerve-centre/kpi-cards/ecwid/average-order-value), [Conversion Rate](/nerve-centre/kpi-cards/ecwid/conversion-rate), [Out-of-Stock Products](/nerve-centre/kpi-cards/ecwid/out-of-stock-products), [Refund Rate](/nerve-centre/kpi-cards/ecwid/refund-rate), [Total Orders](/nerve-centre/kpi-cards/ecwid/total-orders)

    [View all 12 cards →](/nerve-centre/kpi-cards/ecwid)
  </Accordion>

  <Accordion title="Medusa">
    [Open the Medusa connector page →](/nerve-centre/kpi-cards/medusa)
  </Accordion>

  <Accordion title="Microsoft Dynamics 365 · 60 cards">
    **Key Metrics cards:** [Days Sales Outstanding (DSO)](/nerve-centre/kpi-cards/microsoft-dynamics/days-sales-outstanding), [Dead Stock Value](/nerve-centre/kpi-cards/microsoft-dynamics/dead-stock-value), [Gross Margin Percentage](/nerve-centre/kpi-cards/microsoft-dynamics/gross-margin-percentage), [Inventory Aging](/nerve-centre/kpi-cards/microsoft-dynamics/inventory-aging), [Margin Erosion Alerts](/nerve-centre/kpi-cards/microsoft-dynamics/margin-erosion-alerts)

    [View all 60 cards →](/nerve-centre/kpi-cards/microsoft-dynamics)
  </Accordion>

  <Accordion title="NetSuite · 60 cards">
    **Key Metrics cards:** [Days Sales Outstanding (DSO)](/nerve-centre/kpi-cards/netsuite/days-sales-outstanding), [Dead Stock Value](/nerve-centre/kpi-cards/netsuite/dead-stock-value), [Gross Margin Percentage](/nerve-centre/kpi-cards/netsuite/gross-margin-percentage), [Inventory Aging](/nerve-centre/kpi-cards/netsuite/inventory-aging), [Margin Erosion Alerts](/nerve-centre/kpi-cards/netsuite/margin-erosion-alerts)

    [View all 60 cards →](/nerve-centre/kpi-cards/netsuite)
  </Accordion>

  <Accordion title="Odoo">
    [Open the Odoo connector page →](/nerve-centre/kpi-cards/odoo)
  </Accordion>

  <Accordion title="Opencart">
    [Open the Opencart connector page →](/nerve-centre/kpi-cards/opencart)
  </Accordion>

  <Accordion title="Oracle ERP Cloud · 60 cards">
    **Key Metrics cards:** [Days Sales Outstanding (DSO)](/nerve-centre/kpi-cards/oracle-erp/days-sales-outstanding), [Dead Stock Value](/nerve-centre/kpi-cards/oracle-erp/dead-stock-value), [Gross Margin Percentage](/nerve-centre/kpi-cards/oracle-erp/gross-margin-percentage), [Inventory Aging](/nerve-centre/kpi-cards/oracle-erp/inventory-aging), [Margin Erosion Alerts](/nerve-centre/kpi-cards/oracle-erp/margin-erosion-alerts)

    [View all 60 cards →](/nerve-centre/kpi-cards/oracle-erp)
  </Accordion>

  <Accordion title="Prestashop">
    [Open the Prestashop connector page →](/nerve-centre/kpi-cards/prestashop)
  </Accordion>

  <Accordion title="Sage · 60 cards">
    **Key Metrics cards:** [Days Sales Outstanding (DSO)](/nerve-centre/kpi-cards/sage/days-sales-outstanding), [Dead Stock Value](/nerve-centre/kpi-cards/sage/dead-stock-value), [Gross Margin Percentage](/nerve-centre/kpi-cards/sage/gross-margin-percentage), [Inventory Aging](/nerve-centre/kpi-cards/sage/inventory-aging), [Margin Erosion Alerts](/nerve-centre/kpi-cards/sage/margin-erosion-alerts)

    [View all 60 cards →](/nerve-centre/kpi-cards/sage)
  </Accordion>

  <Accordion title="Salesforce Commerce Cloud · 12 cards">
    **Key Metrics cards:** [Average Order Value](/nerve-centre/kpi-cards/salesforce-commerce-cloud/average-order-value), [Conversion Rate](/nerve-centre/kpi-cards/salesforce-commerce-cloud/conversion-rate), [Out-of-Stock Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/out-of-stock-products), [Refund Rate](/nerve-centre/kpi-cards/salesforce-commerce-cloud/refund-rate), [Total Orders](/nerve-centre/kpi-cards/salesforce-commerce-cloud/total-orders)

    [View all 12 cards →](/nerve-centre/kpi-cards/salesforce-commerce-cloud)
  </Accordion>

  <Accordion title="SAP · 60 cards">
    **Key Metrics cards:** [Days Sales Outstanding (DSO)](/nerve-centre/kpi-cards/sap/days-sales-outstanding), [Dead Stock Value](/nerve-centre/kpi-cards/sap/dead-stock-value), [Gross Margin Percentage](/nerve-centre/kpi-cards/sap/gross-margin-percentage), [Inventory Aging](/nerve-centre/kpi-cards/sap/inventory-aging), [Margin Erosion Alerts](/nerve-centre/kpi-cards/sap/margin-erosion-alerts)

    [View all 60 cards →](/nerve-centre/kpi-cards/sap)
  </Accordion>

  <Accordion title="Shopify · 78 cards">
    **Key Metrics cards:** [Fulfillment Rate](/nerve-centre/kpi-cards/shopify/fulfillment-rate), [Products with Zero/Negative Stock](/nerve-centre/kpi-cards/shopify/products-with-zero-negative-stock), [Refund Rate](/nerve-centre/kpi-cards/shopify/refund-rate), [Revenue Drop Alert](/nerve-centre/kpi-cards/shopify/revenue-drop-alert), [Total Revenue](/nerve-centre/kpi-cards/shopify/total-revenue)

    [View all 78 cards →](/nerve-centre/kpi-cards/shopify)
  </Accordion>

  <Accordion title="Shopline · 52 cards">
    **Key Metrics cards:** [Auth Token Health](/nerve-centre/kpi-cards/shopline/auth-token-health), [Fulfillment Rate](/nerve-centre/kpi-cards/shopline/fulfillment-rate), [Refund Rate](/nerve-centre/kpi-cards/shopline/refund-rate), [Total Revenue](/nerve-centre/kpi-cards/shopline/total-revenue), [Unfulfilled Orders](/nerve-centre/kpi-cards/shopline/unfulfilled-orders)

    [View all 52 cards →](/nerve-centre/kpi-cards/shopline)
  </Accordion>

  <Accordion title="Square Online · 12 cards">
    **Key Metrics cards:** [Average Order Value](/nerve-centre/kpi-cards/square-online/average-order-value), [Conversion Rate](/nerve-centre/kpi-cards/square-online/conversion-rate), [Out-of-Stock Products](/nerve-centre/kpi-cards/square-online/out-of-stock-products), [Refund Rate](/nerve-centre/kpi-cards/square-online/refund-rate), [Total Orders](/nerve-centre/kpi-cards/square-online/total-orders)

    [View all 12 cards →](/nerve-centre/kpi-cards/square-online)
  </Accordion>

  <Accordion title="Swell">
    [Open the Swell connector page →](/nerve-centre/kpi-cards/swell)
  </Accordion>

  <Accordion title="Volusion">
    [Open the Volusion connector page →](/nerve-centre/kpi-cards/volusion)
  </Accordion>

  <Accordion title="WooCommerce · 39 cards">
    **Key Metrics cards:** [Average Order Value](/nerve-centre/kpi-cards/woocommerce/average-order-value), [Conversion Rate](/nerve-centre/kpi-cards/woocommerce/conversion-rate), [Failed Order Rate](/nerve-centre/kpi-cards/woocommerce/failed-order-rate), [Failed-Order Spike Alert](/nerve-centre/kpi-cards/woocommerce/failed-order-spike-alert), [OOS Spike Alert](/nerve-centre/kpi-cards/woocommerce/oos-spike-alert)

    [View all 39 cards →](/nerve-centre/kpi-cards/woocommerce)
  </Accordion>
</AccordionGroup>

### Marketplace

<AccordionGroup>
  <Accordion title="AbeBooks · 52 cards">
    **Key Metrics cards:** [Dispatch SLA Compliance](/nerve-centre/kpi-cards/abebooks/dispatch-sla-compliance), [Feed Cycle Failure](/nerve-centre/kpi-cards/abebooks/feed-cycle-failure), [Last Successful Upload](/nerve-centre/kpi-cards/abebooks/last-successful-upload), [Late Order Processing Queue](/nerve-centre/kpi-cards/abebooks/late-order-processing-queue), [Listings Processed With Errors](/nerve-centre/kpi-cards/abebooks/listings-processed-with-errors)

    [View all 52 cards →](/nerve-centre/kpi-cards/abebooks)
  </Accordion>

  <Accordion title="Alibaba · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/alibaba/active-listings), [Average Order Value](/nerve-centre/kpi-cards/alibaba/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/alibaba/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/alibaba/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/alibaba/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/alibaba)
  </Accordion>

  <Accordion title="Alibris · 52 cards">
    **Key Metrics cards:** [Dispatch SLA Compliance](/nerve-centre/kpi-cards/alibris/dispatch-sla-compliance), [Feed Cycle Failure](/nerve-centre/kpi-cards/alibris/feed-cycle-failure), [Last Successful Upload](/nerve-centre/kpi-cards/alibris/last-successful-upload), [Late Order Processing Queue](/nerve-centre/kpi-cards/alibris/late-order-processing-queue), [Listings Processed With Errors](/nerve-centre/kpi-cards/alibris/listings-processed-with-errors)

    [View all 52 cards →](/nerve-centre/kpi-cards/alibris)
  </Accordion>

  <Accordion title="AliExpress · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/aliexpress/active-listings), [Average Order Value](/nerve-centre/kpi-cards/aliexpress/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/aliexpress/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/aliexpress/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/aliexpress/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/aliexpress)
  </Accordion>

  <Accordion title="Amazon (Selling Partner) · 77 cards">
    **Key Metrics cards:** [Account Health Status](/nerve-centre/kpi-cards/amazon/account-health-status), [Buy-Box Loss Burst](/nerve-centre/kpi-cards/amazon/buy-box-loss-burst), [Catalogue Drift vs DTC](/nerve-centre/kpi-cards/amazon/catalogue-drift-vs-dtc), [Estimated Revenue Lost to Buy-Box Loss](/nerve-centre/kpi-cards/amazon/estimated-revenue-lost-to-buy-box-loss), [New Suppressions (24h)](/nerve-centre/kpi-cards/amazon/new-suppressions)

    [View all 77 cards →](/nerve-centre/kpi-cards/amazon)
  </Accordion>

  <Accordion title="Bonanza · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/bonanza/active-listings), [Average Order Value](/nerve-centre/kpi-cards/bonanza/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/bonanza/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/bonanza/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/bonanza/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/bonanza)
  </Accordion>

  <Accordion title="Costco SIP · 48 cards">
    **Key Metrics cards:** [Item Delisting Burst (24h)](/nerve-centre/kpi-cards/costco-sip/item-delisting-burst), [Items Delisted This Week](/nerve-centre/kpi-cards/costco-sip/items-delisted-this-week), [Last Successful Inbound](/nerve-centre/kpi-cards/costco-sip/last-successful-inbound), [POs Missing ASN](/nerve-centre/kpi-cards/costco-sip/pos-missing-asn), [Costco vs DTC Pricing Parity](/nerve-centre/kpi-cards/costco-sip/costco-vs-dtc-pricing-parity)

    [View all 48 cards →](/nerve-centre/kpi-cards/costco-sip)
  </Accordion>

  <Accordion title="Depop · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/depop/active-listings), [Average Order Value](/nerve-centre/kpi-cards/depop/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/depop/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/depop/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/depop/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/depop)
  </Accordion>

  <Accordion title="eBay · 50 cards">
    **Key Metrics cards:** [Defect Rate](/nerve-centre/kpi-cards/ebay/defect-rate), [eBay Health Score](/nerve-centre/kpi-cards/ebay/ebay-health-score), [INR Cases Burst (24h)](/nerve-centre/kpi-cards/ebay/inr-cases-burst), [Listings Missing Attributes](/nerve-centre/kpi-cards/ebay/listings-missing-attributes), [Open INR Cases](/nerve-centre/kpi-cards/ebay/open-inr-cases)

    [View all 50 cards →](/nerve-centre/kpi-cards/ebay)
  </Accordion>

  <Accordion title="Etsy · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/etsy/active-listings), [Average Order Value](/nerve-centre/kpi-cards/etsy/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/etsy/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/etsy/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/etsy/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/etsy)
  </Accordion>

  <Accordion title="Fruugo · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/fruugo/active-listings), [Average Order Value](/nerve-centre/kpi-cards/fruugo/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/fruugo/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/fruugo/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/fruugo/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/fruugo)
  </Accordion>

  <Accordion title="JD.com · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/jd-com/active-listings), [Average Order Value](/nerve-centre/kpi-cards/jd-com/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/jd-com/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/jd-com/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/jd-com/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/jd-com)
  </Accordion>

  <Accordion title="Mercari · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/mercari/active-listings), [Average Order Value](/nerve-centre/kpi-cards/mercari/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/mercari/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/mercari/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/mercari/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/mercari)
  </Accordion>

  <Accordion title="Newegg Marketplace · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/newegg/active-listings), [Average Order Value](/nerve-centre/kpi-cards/newegg/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/newegg/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/newegg/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/newegg/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/newegg)
  </Accordion>

  <Accordion title="OnBuy · 62 cards">
    **Key Metrics cards:** [Dispatch SLA Compliance](/nerve-centre/kpi-cards/onbuy/dispatch-sla-compliance), [Late Dispatch Queue](/nerve-centre/kpi-cards/onbuy/late-dispatch-queue), [Listings Suspension Burst (24h)](/nerve-centre/kpi-cards/onbuy/listings-suspension-burst), [Revenue at Risk (live)](/nerve-centre/kpi-cards/onbuy/revenue-at-risk), [Suspended Listings](/nerve-centre/kpi-cards/onbuy/suspended-listings)

    [View all 62 cards →](/nerve-centre/kpi-cards/onbuy)
  </Accordion>

  <Accordion title="Target Plus · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/target-plus/active-listings), [Average Order Value](/nerve-centre/kpi-cards/target-plus/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/target-plus/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/target-plus/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/target-plus/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/target-plus)
  </Accordion>

  <Accordion title="Vinted · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/vinted/active-listings), [Average Order Value](/nerve-centre/kpi-cards/vinted/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/vinted/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/vinted/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/vinted/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/vinted)
  </Accordion>

  <Accordion title="Walmart Marketplace · 17 cards">
    **Key cards:** [Active Listings](/nerve-centre/kpi-cards/walmart-marketplace/active-listings), [Average Order Value](/nerve-centre/kpi-cards/walmart-marketplace/average-order-value), [Avg Review Rating](/nerve-centre/kpi-cards/walmart-marketplace/avg-review-rating), [Buyer Messages Unread](/nerve-centre/kpi-cards/walmart-marketplace/buyer-messages-unread), [Dispute Rate](/nerve-centre/kpi-cards/walmart-marketplace/dispute-rate)

    [View all 17 cards →](/nerve-centre/kpi-cards/walmart-marketplace)
  </Accordion>
</AccordionGroup>

### Databases

Amazon DynamoDB, Amazon Redshift, Apache Cassandra, [ClickHouse](/nerve-centre/kpi-cards/clickhouse), [CockroachDB](/nerve-centre/kpi-cards/cockroachdb), Custom Connector, [Databricks](/nerve-centre/kpi-cards/databricks), [Elasticsearch](/nerve-centre/kpi-cards/elasticsearch), Google BigQuery, Google Firestore, [MariaDB](/nerve-centre/kpi-cards/mariadb), Microsoft SQL Server, [MongoDB](/nerve-centre/kpi-cards/mongodb), [MySQL](/nerve-centre/kpi-cards/mysql), Neo4j, Oracle Database, PlanetScale, [PostgreSQL](/nerve-centre/kpi-cards/postgresql), [Redis](/nerve-centre/kpi-cards/redis), [Snowflake](/nerve-centre/kpi-cards/snowflake), SQLite, [Supabase](/nerve-centre/kpi-cards/supabase)

Operational and analytical data stores. Track table volume, query health, replication lag and freshness, and join custom data back to commerce KPIs. Connectors without a linked card page are live in the app with documentation on the way.

### Analytics

<AccordionGroup>
  <Accordion title="Amplitude · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/amplitude/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/amplitude/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/amplitude/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/amplitude/goal-completions), [New Users](/nerve-centre/kpi-cards/amplitude/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/amplitude)
  </Accordion>

  <Accordion title="Chartbeat · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/chartbeat/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/chartbeat/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/chartbeat/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/chartbeat/goal-completions), [New Users](/nerve-centre/kpi-cards/chartbeat/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/chartbeat)
  </Accordion>

  <Accordion title="FullStory · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/fullstory/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/fullstory/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/fullstory/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/fullstory/goal-completions), [New Users](/nerve-centre/kpi-cards/fullstory/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/fullstory)
  </Accordion>

  <Accordion title="Google Analytics 4 · 100 cards">
    **Key Metrics cards:** [Conversion-Rate Drop Alert](/nerve-centre/kpi-cards/google-analytics/conversion-rate-drop-alert), [Ecommerce Conversion Rate](/nerve-centre/kpi-cards/google-analytics/ecommerce-conversion-rate), [GA4 Property Health](/nerve-centre/kpi-cards/google-analytics/ga4-property-health), [Revenue Trend](/nerve-centre/kpi-cards/google-analytics/revenue-trend), [Traffic Drop Alert](/nerve-centre/kpi-cards/google-analytics/traffic-drop-alert)

    [View all 100 cards →](/nerve-centre/kpi-cards/google-analytics)
  </Accordion>

  <Accordion title="Google Search Console · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/google-search-console/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/google-search-console/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/google-search-console/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/google-search-console/goal-completions), [New Users](/nerve-centre/kpi-cards/google-search-console/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/google-search-console)
  </Accordion>

  <Accordion title="Heap · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/heap/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/heap/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/heap/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/heap/goal-completions), [New Users](/nerve-centre/kpi-cards/heap/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/heap)
  </Accordion>

  <Accordion title="Hotjar · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/hotjar/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/hotjar/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/hotjar/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/hotjar/goal-completions), [New Users](/nerve-centre/kpi-cards/hotjar/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/hotjar)
  </Accordion>

  <Accordion title="Kissmetrics · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/kissmetrics/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/kissmetrics/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/kissmetrics/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/kissmetrics/goal-completions), [New Users](/nerve-centre/kpi-cards/kissmetrics/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/kissmetrics)
  </Accordion>

  <Accordion title="Looker · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/looker/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/looker/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/looker/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/looker/goal-completions), [New Users](/nerve-centre/kpi-cards/looker/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/looker)
  </Accordion>

  <Accordion title="Matomo · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/matomo/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/matomo/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/matomo/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/matomo/goal-completions), [New Users](/nerve-centre/kpi-cards/matomo/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/matomo)
  </Accordion>

  <Accordion title="Microsoft Clarity · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/clarity/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/clarity/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/clarity/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/clarity/goal-completions), [New Users](/nerve-centre/kpi-cards/clarity/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/clarity)
  </Accordion>

  <Accordion title="Mixpanel · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/mixpanel/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/mixpanel/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/mixpanel/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/mixpanel/goal-completions), [New Users](/nerve-centre/kpi-cards/mixpanel/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/mixpanel)
  </Accordion>

  <Accordion title="Mixpanel (B) · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/mixpanel-b/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/mixpanel-b/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/mixpanel-b/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/mixpanel-b/goal-completions), [New Users](/nerve-centre/kpi-cards/mixpanel-b/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/mixpanel-b)
  </Accordion>

  <Accordion title="Mode Analytics · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/mode-analytics/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/mode-analytics/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/mode-analytics/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/mode-analytics/goal-completions), [New Users](/nerve-centre/kpi-cards/mode-analytics/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/mode-analytics)
  </Accordion>

  <Accordion title="Plausible Analytics · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/plausible/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/plausible/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/plausible/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/plausible/goal-completions), [New Users](/nerve-centre/kpi-cards/plausible/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/plausible)
  </Accordion>

  <Accordion title="PostHog · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/posthog/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/posthog/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/posthog/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/posthog/goal-completions), [New Users](/nerve-centre/kpi-cards/posthog/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/posthog)
  </Accordion>

  <Accordion title="Segment · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/segment/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/segment/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/segment/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/segment/goal-completions), [New Users](/nerve-centre/kpi-cards/segment/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/segment)
  </Accordion>

  <Accordion title="Tableau · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/tableau/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/tableau/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/tableau/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/tableau/goal-completions), [New Users](/nerve-centre/kpi-cards/tableau/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/tableau)
  </Accordion>
</AccordionGroup>

### Advertising

<AccordionGroup>
  <Accordion title="AdRoll · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/adroll/roas), [Spend vs Budget](/nerve-centre/kpi-cards/adroll/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/adroll/total-revenue), [Total Spend](/nerve-centre/kpi-cards/adroll/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/adroll/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/adroll)
  </Accordion>

  <Accordion title="Amazon Ads · 102 cards">
    **Key Metrics cards:** [ACOS](/nerve-centre/kpi-cards/amazon-ads/acos), [Active Ads on No-Buy-Box ASINs](/nerve-centre/kpi-cards/amazon-ads/active-ads-on-no-buy-box-asins), [Active Ads on Out-of-Stock SKUs](/nerve-centre/kpi-cards/amazon-ads/active-ads-on-out-of-stock-skus), [Dayparting Waste (low-CR hours)](/nerve-centre/kpi-cards/amazon-ads/dayparting-waste), [DSP vs Sponsored Spend Mix](/nerve-centre/kpi-cards/amazon-ads/dsp-vs-sponsored-spend-mix)

    [View all 102 cards →](/nerve-centre/kpi-cards/amazon-ads)
  </Accordion>

  <Accordion title="Criteo · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/criteo/roas), [Spend vs Budget](/nerve-centre/kpi-cards/criteo/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/criteo/total-revenue), [Total Spend](/nerve-centre/kpi-cards/criteo/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/criteo/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/criteo)
  </Accordion>

  <Accordion title="Google Ads · 75 cards">
    **Key Metrics cards:** [Conversion Drop Alert](/nerve-centre/kpi-cards/google-ads/gads-conversion-drop-alert), [Conversion-Tracking-Broken Alert](/nerve-centre/kpi-cards/google-ads/conversion-tracking-broken-alert), [ROAS](/nerve-centre/kpi-cards/google-ads/roas), [ROAS by Campaign](/nerve-centre/kpi-cards/google-ads/roas-by-campaign), [ROAS Drop Alert](/nerve-centre/kpi-cards/google-ads/roas-drop-alert)

    [View all 75 cards →](/nerve-centre/kpi-cards/google-ads)
  </Accordion>

  <Accordion title="LinkedIn Ads · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/linkedin-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/linkedin-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/linkedin-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/linkedin-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/linkedin-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/linkedin-ads)
  </Accordion>

  <Accordion title="MediaMath · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/mediamath/roas), [Spend vs Budget](/nerve-centre/kpi-cards/mediamath/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/mediamath/total-revenue), [Total Spend](/nerve-centre/kpi-cards/mediamath/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/mediamath/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/mediamath)
  </Accordion>

  <Accordion title="Meta Ads (Facebook) · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/facebook-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/facebook-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/facebook-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/facebook-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/facebook-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/facebook-ads)
  </Accordion>

  <Accordion title="Microsoft Ads (Bing) · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/microsoft-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/microsoft-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/microsoft-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/microsoft-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/microsoft-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/microsoft-ads)
  </Accordion>

  <Accordion title="Outbrain · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/outbrain/roas), [Spend vs Budget](/nerve-centre/kpi-cards/outbrain/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/outbrain/total-revenue), [Total Spend](/nerve-centre/kpi-cards/outbrain/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/outbrain/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/outbrain)
  </Accordion>

  <Accordion title="Pinterest Ads · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/pinterest-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/pinterest-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/pinterest-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/pinterest-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/pinterest-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/pinterest-ads)
  </Accordion>

  <Accordion title="Quora Ads · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/quora-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/quora-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/quora-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/quora-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/quora-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/quora-ads)
  </Accordion>

  <Accordion title="Snapchat Ads · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/snapchat-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/snapchat-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/snapchat-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/snapchat-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/snapchat-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/snapchat-ads)
  </Accordion>

  <Accordion title="StackAdapt · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/stackadapt/roas), [Spend vs Budget](/nerve-centre/kpi-cards/stackadapt/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/stackadapt/total-revenue), [Total Spend](/nerve-centre/kpi-cards/stackadapt/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/stackadapt/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/stackadapt)
  </Accordion>

  <Accordion title="Taboola · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/taboola/roas), [Spend vs Budget](/nerve-centre/kpi-cards/taboola/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/taboola/total-revenue), [Total Spend](/nerve-centre/kpi-cards/taboola/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/taboola/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/taboola)
  </Accordion>

  <Accordion title="The Trade Desk · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/the-trade-desk/roas), [Spend vs Budget](/nerve-centre/kpi-cards/the-trade-desk/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/the-trade-desk/total-revenue), [Total Spend](/nerve-centre/kpi-cards/the-trade-desk/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/the-trade-desk/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/the-trade-desk)
  </Accordion>

  <Accordion title="TikTok Ads · 65 cards">
    **Key Metrics cards:** [ROAS](/nerve-centre/kpi-cards/tiktok-ads/roas), [Spend vs Budget](/nerve-centre/kpi-cards/tiktok-ads/spend-vs-budget), [Total Revenue](/nerve-centre/kpi-cards/tiktok-ads/total-revenue), [Total Spend](/nerve-centre/kpi-cards/tiktok-ads/total-spend), [Wasted Spend](/nerve-centre/kpi-cards/tiktok-ads/wasted-spend)

    [View all 65 cards →](/nerve-centre/kpi-cards/tiktok-ads)
  </Accordion>
</AccordionGroup>

### Payments

<AccordionGroup>
  <Accordion title="Adyen · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/adyen/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/adyen/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/adyen/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/adyen/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/adyen/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/adyen)
  </Accordion>

  <Accordion title="Afterpay · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/afterpay/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/afterpay/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/afterpay/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/afterpay/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/afterpay/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/afterpay)
  </Accordion>

  <Accordion title="Authorize.net · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/authorize-net/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/authorize-net/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/authorize-net/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/authorize-net/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/authorize-net/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/authorize-net)
  </Accordion>

  <Accordion title="BlueSnap · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/bluesnap/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/bluesnap/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/bluesnap/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/bluesnap/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/bluesnap/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/bluesnap)
  </Accordion>

  <Accordion title="Braintree · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/braintree/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/braintree/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/braintree/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/braintree/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/braintree/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/braintree)
  </Accordion>

  <Accordion title="Chargebee · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/chargebee/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/chargebee/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/chargebee/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/chargebee/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/chargebee/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/chargebee)
  </Accordion>

  <Accordion title="Checkout.com · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/checkout-com/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/checkout-com/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/checkout-com/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/checkout-com/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/checkout-com/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/checkout-com)
  </Accordion>

  <Accordion title="CyberSource · 76 cards">
    **Key Metrics cards:** [3DS Challenge Abandon Rate](/nerve-centre/kpi-cards/cybersource/3ds-challenge-abandon-rate), [Authorisation Success Rate](/nerve-centre/kpi-cards/cybersource/authorisation-success-rate), [Chargeback Rate](/nerve-centre/kpi-cards/cybersource/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/cybersource/decline-rate), [Decline Rate Spike Alert](/nerve-centre/kpi-cards/cybersource/decline-rate-spike-alert)

    [View all 76 cards →](/nerve-centre/kpi-cards/cybersource)
  </Accordion>

  <Accordion title="eWAY · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/eway/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/eway/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/eway/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/eway/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/eway/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/eway)
  </Accordion>

  <Accordion title="GoCardless · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/gocardless/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/gocardless/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/gocardless/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/gocardless/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/gocardless/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/gocardless)
  </Accordion>

  <Accordion title="Helcim · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/helcim/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/helcim/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/helcim/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/helcim/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/helcim/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/helcim)
  </Accordion>

  <Accordion title="Klarna · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/klarna-api/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/klarna-api/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/klarna-api/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/klarna-api/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/klarna-api/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/klarna-api)
  </Accordion>

  <Accordion title="Mollie · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/mollie/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/mollie/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/mollie/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/mollie/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/mollie/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/mollie)
  </Accordion>

  <Accordion title="Nuvei · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/nuvei/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/nuvei/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/nuvei/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/nuvei/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/nuvei/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/nuvei)
  </Accordion>

  <Accordion title="PayPal · 77 cards">
    **Key Metrics cards:** [Decline / Failure Rate](/nerve-centre/kpi-cards/paypal/decline-failure-rate), [Decline Rate Spike Alert](/nerve-centre/kpi-cards/paypal/decline-rate-spike-alert), [Dispute Threshold Watch](/nerve-centre/kpi-cards/paypal/dispute-threshold-watch), [Open Disputes](/nerve-centre/kpi-cards/paypal/open-disputes), [Payment Health Score](/nerve-centre/kpi-cards/paypal/payment-health-score)

    [View all 77 cards →](/nerve-centre/kpi-cards/paypal)
  </Accordion>

  <Accordion title="Razorpay · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/razorpay/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/razorpay/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/razorpay/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/razorpay/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/razorpay/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/razorpay)
  </Accordion>

  <Accordion title="Recharge · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/recharge/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/recharge/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/recharge/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/recharge/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/recharge/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/recharge)
  </Accordion>

  <Accordion title="Recurly · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/recurly/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/recurly/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/recurly/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/recurly/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/recurly/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/recurly)
  </Accordion>

  <Accordion title="Square · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/square/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/square/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/square/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/square/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/square/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/square)
  </Accordion>

  <Accordion title="Stax Payments · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/stax-payments/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/stax-payments/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/stax-payments/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/stax-payments/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/stax-payments/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/stax-payments)
  </Accordion>

  <Accordion title="Stripe · 80 cards">
    **Key Metrics cards:** [Authorisation Success Rate](/nerve-centre/kpi-cards/stripe/authorisation-success-rate), [Decline Rate](/nerve-centre/kpi-cards/stripe/decline-rate), [Decline Rate Spike Alert](/nerve-centre/kpi-cards/stripe/decline-rate-spike-alert), [Dispute Threshold Watch](/nerve-centre/kpi-cards/stripe/dispute-threshold-watch), [Open Disputes](/nerve-centre/kpi-cards/stripe/open-disputes)

    [View all 80 cards →](/nerve-centre/kpi-cards/stripe)
  </Accordion>

  <Accordion title="Viva Payments · 30 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/viva-payments/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/viva-payments/average-transaction), [Average Transaction](/nerve-centre/kpi-cards/viva-payments/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/viva-payments/avg-settlement-time), [Card vs Customer Country Mismatches](/nerve-centre/kpi-cards/viva-payments/card-vs-customer-country-mismatches)

    [View all 30 cards →](/nerve-centre/kpi-cards/viva-payments)
  </Accordion>

  <Accordion title="Worldpay · 16 cards">
    **Key cards:** [3DS Abandonment Rate](/nerve-centre/kpi-cards/worldpay/3ds-abandonment-rate), [Average Transaction](/nerve-centre/kpi-cards/worldpay/average-transaction), [Avg Settlement Time (days)](/nerve-centre/kpi-cards/worldpay/avg-settlement-time), [Chargeback Rate](/nerve-centre/kpi-cards/worldpay/chargeback-rate), [Decline Rate](/nerve-centre/kpi-cards/worldpay/decline-rate)

    [View all 16 cards →](/nerve-centre/kpi-cards/worldpay)
  </Accordion>
</AccordionGroup>

### Shipping & Delivery

<AccordionGroup>
  <Accordion title="Amazon Prime Shipping (SFP) · 25 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/amazon-prime-shipping/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/amazon-prime-shipping/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/amazon-prime-shipping/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/amazon-prime-shipping/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/amazon-prime-shipping/on-time-delivery-rate)

    [View all 25 cards →](/nerve-centre/kpi-cards/amazon-prime-shipping)
  </Accordion>

  <Accordion title="APC Overnight · 25 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/apc/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/apc/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/apc/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/apc/late-shipments), [NextDay 9am Service Promise](/nerve-centre/kpi-cards/apc/nextday-9am-service-promise)

    [View all 25 cards →](/nerve-centre/kpi-cards/apc)
  </Accordion>

  <Accordion title="Australia Post · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/australia-post/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/australia-post/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/australia-post/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/australia-post/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/australia-post/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/australia-post)
  </Accordion>

  <Accordion title="Bring · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/bring/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/bring/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/bring/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/bring/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/bring/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/bring)
  </Accordion>

  <Accordion title="Deutsche Post · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/deutsche-post/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/deutsche-post/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/deutsche-post/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/deutsche-post/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/deutsche-post/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/deutsche-post)
  </Accordion>

  <Accordion title="DHL InExpress · 24 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/dhl-inexpress/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/dhl-inexpress/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/dhl-inexpress/exception-rate), [International Express OTD](/nerve-centre/kpi-cards/dhl-inexpress/international-express-otd), [Late Shipments](/nerve-centre/kpi-cards/dhl-inexpress/late-shipments)

    [View all 24 cards →](/nerve-centre/kpi-cards/dhl-inexpress)
  </Accordion>

  <Accordion title="DPD · 24 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/dpd/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/dpd/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/dpd/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/dpd/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/dpd/on-time-delivery-rate)

    [View all 24 cards →](/nerve-centre/kpi-cards/dpd)
  </Accordion>

  <Accordion title="DPDLocal · 51 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/dpdlocal/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/dpdlocal/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/dpdlocal/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/dpdlocal/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/dpdlocal/on-time-delivery-rate)

    [View all 51 cards →](/nerve-centre/kpi-cards/dpdlocal)
  </Accordion>

  <Accordion title="EasyPost · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/easypost/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/easypost/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/easypost/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/easypost/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/easypost/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/easypost)
  </Accordion>

  <Accordion title="Evri (formerly Hermes UK) · 25 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/hermes-evri/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/hermes-evri/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/hermes-evri/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/hermes-evri/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/hermes-evri/on-time-delivery-rate)

    [View all 25 cards →](/nerve-centre/kpi-cards/hermes-evri)
  </Accordion>

  <Accordion title="FedEx · 25 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/fedex/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/fedex/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/fedex/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/fedex/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/fedex/on-time-delivery-rate)

    [View all 25 cards →](/nerve-centre/kpi-cards/fedex)
  </Accordion>

  <Accordion title="Interlink Express · 24 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/interlink-express/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/interlink-express/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/interlink-express/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/interlink-express/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/interlink-express/on-time-delivery-rate)

    [View all 24 cards →](/nerve-centre/kpi-cards/interlink-express)
  </Accordion>

  <Accordion title="Japan Post · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/japan-post/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/japan-post/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/japan-post/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/japan-post/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/japan-post/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/japan-post)
  </Accordion>

  <Accordion title="NetDispatch · 23 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/net-dispatch/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/net-dispatch/days-to-token-expiry), [Dispatch-to-Collection Lag](/nerve-centre/kpi-cards/net-dispatch/dispatch-to-collection-lag), [Exception Rate](/nerve-centre/kpi-cards/net-dispatch/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/net-dispatch/late-shipments)

    [View all 23 cards →](/nerve-centre/kpi-cards/net-dispatch)
  </Accordion>

  <Accordion title="Parcelforce Worldwide · 24 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/parcelforce/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/parcelforce/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/parcelforce/exception-rate), [Express24 Service Day Promise](/nerve-centre/kpi-cards/parcelforce/express24-service-day-promise), [Late Shipments](/nerve-centre/kpi-cards/parcelforce/late-shipments)

    [View all 24 cards →](/nerve-centre/kpi-cards/parcelforce)
  </Accordion>

  <Accordion title="PostNord · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/postnord/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/postnord/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/postnord/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/postnord/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/postnord/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/postnord)
  </Accordion>

  <Accordion title="Royal Mail · 25 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/royal-mail/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/royal-mail/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/royal-mail/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/royal-mail/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/royal-mail/on-time-delivery-rate)

    [View all 25 cards →](/nerve-centre/kpi-cards/royal-mail)
  </Accordion>

  <Accordion title="Sendle · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/sendle/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/sendle/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/sendle/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/sendle/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/sendle/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/sendle)
  </Accordion>

  <Accordion title="ShipBob · 87 cards">
    **Key Metrics cards:** [Fulfilment Rate](/nerve-centre/kpi-cards/shipbob/fulfilment-rate), [On-Time Delivery Rate](/nerve-centre/kpi-cards/shipbob/on-time-delivery-rate), [On-Time Delivery Trend](/nerve-centre/kpi-cards/shipbob/on-time-delivery-trend), [Operational Health Score](/nerve-centre/kpi-cards/shipbob/operational-health-score), [Orders by Region](/nerve-centre/kpi-cards/shipbob/orders-by-region)

    [View all 87 cards →](/nerve-centre/kpi-cards/shipbob)
  </Accordion>

  <Accordion title="Shippo · 21 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/shippo/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/shippo/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/shippo/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/shippo/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/shippo/on-time-delivery-rate)

    [View all 21 cards →](/nerve-centre/kpi-cards/shippo)
  </Accordion>

  <Accordion title="ShippyPro · 24 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/shippy-pro/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/shippy-pro/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/shippy-pro/exception-rate), [Label-Generation Success Rate](/nerve-centre/kpi-cards/shippy-pro/label-generation-success-rate), [Late Shipments](/nerve-centre/kpi-cards/shippy-pro/late-shipments)

    [View all 24 cards →](/nerve-centre/kpi-cards/shippy-pro)
  </Accordion>

  <Accordion title="ShipTheory · 25 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/ship-theory/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/ship-theory/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/ship-theory/exception-rate), [Label-Generation Success Rate](/nerve-centre/kpi-cards/ship-theory/label-generation-success-rate), [Labels Printed Not Collected](/nerve-centre/kpi-cards/ship-theory/labels-printed-not-collected)

    [View all 25 cards →](/nerve-centre/kpi-cards/ship-theory)
  </Accordion>

  <Accordion title="USPS · 24 cards">
    **Key Metrics cards:** [Avg Shipping Cost](/nerve-centre/kpi-cards/usps/avg-shipping-cost), [Days to Token Expiry](/nerve-centre/kpi-cards/usps/days-to-token-expiry), [Exception Rate](/nerve-centre/kpi-cards/usps/exception-rate), [Late Shipments](/nerve-centre/kpi-cards/usps/late-shipments), [On-Time Delivery Rate](/nerve-centre/kpi-cards/usps/on-time-delivery-rate)

    [View all 24 cards →](/nerve-centre/kpi-cards/usps)
  </Accordion>
</AccordionGroup>

### Project Management

<AccordionGroup>
  <Accordion title="Asana · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/asana/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/asana/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/asana/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/asana)
  </Accordion>

  <Accordion title="Basecamp · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/basecamp/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/basecamp/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/basecamp/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/basecamp)
  </Accordion>

  <Accordion title="ClickUp · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/clickup/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/clickup/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/clickup/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/clickup)
  </Accordion>

  <Accordion title="Height · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/height/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/height/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/height/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/height)
  </Accordion>

  <Accordion title="Jira · 32 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/jira/abandoned-findings), [Atlassian Token Expiry Imminent](/nerve-centre/kpi-cards/jira/atlassian-token-expiry-imminent), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/jira/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/jira/vortexiq-findings-open), [Critical Findings Without a Jira Ticket](/nerve-centre/kpi-cards/jira/critical-findings-without-a-jira-ticket)

    [View all 32 cards →](/nerve-centre/kpi-cards/jira)
  </Accordion>

  <Accordion title="Linear · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/linear/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/linear/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/linear/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/linear)
  </Accordion>

  <Accordion title="Lucidchart · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/lucidchart/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/lucidchart/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/lucidchart/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/lucidchart)
  </Accordion>

  <Accordion title="Miro · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/miro/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/miro/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/miro/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/miro)
  </Accordion>

  <Accordion title="Monday.com · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/monday/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/monday/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/monday/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/monday)
  </Accordion>

  <Accordion title="Mural · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/mural/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/mural/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/mural/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/mural)
  </Accordion>

  <Accordion title="Smartsheet (API) · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/smartsheet-api/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/smartsheet-api/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/smartsheet-api/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/smartsheet-api)
  </Accordion>

  <Accordion title="Teamwork · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/teamwork/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/teamwork/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/teamwork/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/teamwork)
  </Accordion>

  <Accordion title="Trello (API) · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/trello-api/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/trello-api/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/trello-api/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/trello-api)
  </Accordion>

  <Accordion title="Wrike (API) · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/wrike-api/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/wrike-api/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/wrike-api/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/wrike-api)
  </Accordion>
</AccordionGroup>

### Cloud Platforms

Amazon Web Services, Anthropic (Claude), [Cloudflare](/nerve-centre/kpi-cards/cloudflare), Cohere, DigitalOcean, Fly.io, Google Cloud Platform, Hetzner, Hugging Face, Linode (Akamai), Microsoft Azure, OpenAI, Replicate, Vultr

Infrastructure and AI/ML providers. Track usage, spend and service health, and correlate cost or outages against revenue. Connectors without a linked card page are live in the app with documentation on the way.

### CRM

<AccordionGroup>
  <Accordion title="Agile CRM · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/agile-crm/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/agile-crm/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/agile-crm/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/agile-crm/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/agile-crm/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/agile-crm)
  </Accordion>

  <Accordion title="Freshsales · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/freshsales/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/freshsales/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/freshsales/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/freshsales/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/freshsales/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/freshsales)
  </Accordion>

  <Accordion title="HubSpot · 68 cards">
    **Key Metrics cards:** [Deals Closing This Month](/nerve-centre/kpi-cards/hubspot/deals-closing-this-month), [Lifecycle Stage Distribution](/nerve-centre/kpi-cards/hubspot/lifecycle-stage-distribution), [Marketing Emails Sent](/nerve-centre/kpi-cards/hubspot/marketing-emails-sent), [Pipeline Drop Alert](/nerve-centre/kpi-cards/hubspot/pipeline-drop-alert), [Pipeline Value by Stage](/nerve-centre/kpi-cards/hubspot/pipeline-value-by-stage)

    [View all 68 cards →](/nerve-centre/kpi-cards/hubspot)
  </Accordion>

  <Accordion title="Insightly · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/insightly/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/insightly/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/insightly/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/insightly/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/insightly/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/insightly)
  </Accordion>

  <Accordion title="Keap (Infusionsoft) · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/keap/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/keap/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/keap/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/keap/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/keap/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/keap)
  </Accordion>

  <Accordion title="Nimble · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/nimble/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/nimble/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/nimble/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/nimble/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/nimble/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/nimble)
  </Accordion>

  <Accordion title="Pipedrive · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/pipedrive/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/pipedrive/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/pipedrive/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/pipedrive/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/pipedrive/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/pipedrive)
  </Accordion>

  <Accordion title="Salesforce · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/salesforce/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/salesforce/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/salesforce/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/salesforce/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/salesforce/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/salesforce)
  </Accordion>

  <Accordion title="SugarCRM · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/sugarcrm/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/sugarcrm/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/sugarcrm/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/sugarcrm/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/sugarcrm/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/sugarcrm)
  </Accordion>

  <Accordion title="Zoho CRM · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/zoho-crm/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/zoho-crm/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/zoho-crm/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/zoho-crm/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/zoho-crm/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/zoho-crm)
  </Accordion>
</AccordionGroup>

### Email & Marketing

<AccordionGroup>
  <Accordion title="ActiveCampaign · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/activecampaign/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/activecampaign/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/activecampaign/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/activecampaign/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/activecampaign/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/activecampaign)
  </Accordion>

  <Accordion title="AWeber · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/aweber/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/aweber/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/aweber/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/aweber/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/aweber/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/aweber)
  </Accordion>

  <Accordion title="Brevo (Sendinblue) · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/brevo-sendinblue/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/brevo-sendinblue/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/brevo-sendinblue/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/brevo-sendinblue/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/brevo-sendinblue/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/brevo-sendinblue)
  </Accordion>

  <Accordion title="Campaign Monitor · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/campaign-monitor/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/campaign-monitor/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/campaign-monitor/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/campaign-monitor/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/campaign-monitor/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/campaign-monitor)
  </Accordion>

  <Accordion title="Constant Contact · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/constant-contact/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/constant-contact/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/constant-contact/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/constant-contact/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/constant-contact/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/constant-contact)
  </Accordion>

  <Accordion title="ConvertKit (API) · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/convertkit-api/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/convertkit-api/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/convertkit-api/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/convertkit-api/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/convertkit-api/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/convertkit-api)
  </Accordion>

  <Accordion title="Customer.io (API) · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/customerio-api/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/customerio-api/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/customerio-api/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/customerio-api/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/customerio-api/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/customerio-api)
  </Accordion>

  <Accordion title="Dotdigital · 62 cards">
    **Key Metrics cards:** [Abandoned-Cart Programme Status](/nerve-centre/kpi-cards/dotdigital/abandoned-cart-programme-status), [Bounce Rate](/nerve-centre/kpi-cards/dotdigital/bounce-rate), [Bounce Spike](/nerve-centre/kpi-cards/dotdigital/bounce-spike), [Email-Attributed Revenue](/nerve-centre/kpi-cards/dotdigital/email-attributed-revenue), [Programme vs Campaign Revenue Mix](/nerve-centre/kpi-cards/dotdigital/programme-vs-campaign-revenue-mix)

    [View all 62 cards →](/nerve-centre/kpi-cards/dotdigital)
  </Accordion>

  <Accordion title="Drip (API) · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/drip-api/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/drip-api/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/drip-api/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/drip-api/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/drip-api/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/drip-api)
  </Accordion>

  <Accordion title="Iterable · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/iterable/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/iterable/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/iterable/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/iterable/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/iterable/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/iterable)
  </Accordion>

  <Accordion title="Klaviyo · 53 cards">
    **Key Metrics cards:** [Abandoned-Cart Flow Status](/nerve-centre/kpi-cards/klaviyo/abandoned-cart-flow-status), [Bounce Rate](/nerve-centre/kpi-cards/klaviyo/bounce-rate), [Bounce Spike](/nerve-centre/kpi-cards/klaviyo/bounce-spike), [Email-Attributed Revenue](/nerve-centre/kpi-cards/klaviyo/email-attributed-revenue), [Flow vs Campaign Revenue Mix](/nerve-centre/kpi-cards/klaviyo/flow-vs-campaign-revenue-mix)

    [View all 53 cards →](/nerve-centre/kpi-cards/klaviyo)
  </Accordion>

  <Accordion title="Mailchimp · 69 cards">
    **Key Metrics cards:** [Abandoned-Cart Automation Status](/nerve-centre/kpi-cards/mailchimp/abandoned-cart-automation-status), [Audience Size](/nerve-centre/kpi-cards/mailchimp/audience-size), [Automation vs Campaign Revenue Mix](/nerve-centre/kpi-cards/mailchimp/automation-vs-campaign-revenue-mix), [Bounce Rate](/nerve-centre/kpi-cards/mailchimp/bounce-rate), [Bounce Spike](/nerve-centre/kpi-cards/mailchimp/bounce-spike)

    [View all 69 cards →](/nerve-centre/kpi-cards/mailchimp)
  </Accordion>

  <Accordion title="Mailgun · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/mailgun/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/mailgun/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/mailgun/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/mailgun/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/mailgun/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/mailgun)
  </Accordion>

  <Accordion title="Moosend · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/moosend/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/moosend/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/moosend/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/moosend/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/moosend/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/moosend)
  </Accordion>

  <Accordion title="Omnisend · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/omnisend/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/omnisend/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/omnisend/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/omnisend/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/omnisend/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/omnisend)
  </Accordion>

  <Accordion title="Postmark · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/postmark/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/postmark/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/postmark/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/postmark/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/postmark/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/postmark)
  </Accordion>

  <Accordion title="SendGrid · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/sendgrid/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/sendgrid/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/sendgrid/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/sendgrid/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/sendgrid/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/sendgrid)
  </Accordion>

  <Accordion title="SparkPost · 29 cards">
    **Key cards:** [Active Subscribers (Est.)](/nerve-centre/kpi-cards/sparkpost/active-subscribers), [Bounce Rate](/nerve-centre/kpi-cards/sparkpost/bounce-rate), [Campaign Status Breakdown](/nerve-centre/kpi-cards/sparkpost/campaign-status-breakdown), [Checkout-to-Order Rate](/nerve-centre/kpi-cards/sparkpost/checkout-to-order-rate), [Checkouts Started](/nerve-centre/kpi-cards/sparkpost/checkouts-started)

    [View all 29 cards →](/nerve-centre/kpi-cards/sparkpost)
  </Accordion>
</AccordionGroup>

### Notifications

<AccordionGroup>
  <Accordion title="Aircall">
    [Open the Aircall connector page →](/nerve-centre/kpi-cards/aircall)
  </Accordion>

  <Accordion title="Dialpad">
    [Open the Dialpad connector page →](/nerve-centre/kpi-cards/dialpad)
  </Accordion>

  <Accordion title="Discord">
    [Open the Discord connector page →](/nerve-centre/kpi-cards/discord)
  </Accordion>

  <Accordion title="Pagerduty">
    [Open the Pagerduty connector page →](/nerve-centre/kpi-cards/pagerduty)
  </Accordion>

  <Accordion title="Pushover">
    [Open the Pushover connector page →](/nerve-centre/kpi-cards/pushover)
  </Accordion>

  <Accordion title="Ringcentral">
    [Open the Ringcentral connector page →](/nerve-centre/kpi-cards/ringcentral)
  </Accordion>

  <Accordion title="Slack">
    [Open the Slack connector page →](/nerve-centre/kpi-cards/slack)
  </Accordion>

  <Accordion title="Teams">
    [Open the Teams connector page →](/nerve-centre/kpi-cards/teams)
  </Accordion>

  <Accordion title="Telegram">
    [Open the Telegram connector page →](/nerve-centre/kpi-cards/telegram)
  </Accordion>

  <Accordion title="Twilio">
    [Open the Twilio connector page →](/nerve-centre/kpi-cards/twilio)
  </Accordion>

  <Accordion title="Vonage">
    [Open the Vonage connector page →](/nerve-centre/kpi-cards/vonage)
  </Accordion>
</AccordionGroup>

### Monitoring & Performance

<AccordionGroup>
  <Accordion title="AppDynamics · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/app-dynamics/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/app-dynamics/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/app-dynamics/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/app-dynamics/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/app-dynamics/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/app-dynamics)
  </Accordion>

  <Accordion title="Atlassian Statuspage · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/statuspage/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/statuspage/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/statuspage/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/statuspage/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/statuspage/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/statuspage)
  </Accordion>

  <Accordion title="Better Uptime · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/better-uptime/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/better-uptime/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/better-uptime/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/better-uptime/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/better-uptime/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/better-uptime)
  </Accordion>

  <Accordion title="Bugsnag · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/bugsnag/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/bugsnag/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/bugsnag/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/bugsnag/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/bugsnag/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/bugsnag)
  </Accordion>

  <Accordion title="Cloudflare · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/cloudflare/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/cloudflare/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/cloudflare/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/cloudflare/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/cloudflare/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/cloudflare)
  </Accordion>

  <Accordion title="Datadog · 80 cards">
    **Key Metrics cards:** [5xx Response Rate](/nerve-centre/kpi-cards/datadog/5xx-response-rate), [Active Incidents](/nerve-centre/kpi-cards/datadog/active-incidents), [Alerts Summary](/nerve-centre/kpi-cards/datadog/alerts-summary), [Critical-Path Tests Status](/nerve-centre/kpi-cards/datadog/critical-path-tests-status), [Currently Triggered Monitors](/nerve-centre/kpi-cards/datadog/currently-triggered-monitors)

    [View all 80 cards →](/nerve-centre/kpi-cards/datadog)
  </Accordion>

  <Accordion title="Dynatrace · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/dynatrace/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/dynatrace/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/dynatrace/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/dynatrace/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/dynatrace/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/dynatrace)
  </Accordion>

  <Accordion title="Fastly · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/fastly/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/fastly/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/fastly/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/fastly/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/fastly/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/fastly)
  </Accordion>

  <Accordion title="Grafana · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/grafana/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/grafana/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/grafana/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/grafana/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/grafana/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/grafana)
  </Accordion>

  <Accordion title="LogRocket · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/logrocket/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/logrocket/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/logrocket/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/logrocket/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/logrocket/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/logrocket)
  </Accordion>

  <Accordion title="New Relic · 75 cards">
    **Key Metrics cards:** [Active Incidents](/nerve-centre/kpi-cards/newrelic/active-incidents), [Critical-Path Tests Status](/nerve-centre/kpi-cards/newrelic/critical-path-tests-status), [Error Rate](/nerve-centre/kpi-cards/newrelic/error-rate), [Operational Health Score](/nerve-centre/kpi-cards/newrelic/operational-health-score), [p95 Response Time](/nerve-centre/kpi-cards/newrelic/p95-response-time)

    [View all 75 cards →](/nerve-centre/kpi-cards/newrelic)
  </Accordion>

  <Accordion title="Opsgenie · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/opsgenie/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/opsgenie/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/opsgenie/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/opsgenie/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/opsgenie/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/opsgenie)
  </Accordion>

  <Accordion title="Pingdom · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/pingdom/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/pingdom/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/pingdom/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/pingdom/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/pingdom/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/pingdom)
  </Accordion>

  <Accordion title="Prometheus · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/prometheus/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/prometheus/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/prometheus/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/prometheus/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/prometheus/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/prometheus)
  </Accordion>

  <Accordion title="Raygun · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/raygun/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/raygun/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/raygun/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/raygun/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/raygun/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/raygun)
  </Accordion>

  <Accordion title="Rollbar · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/rollbar/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/rollbar/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/rollbar/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/rollbar/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/rollbar/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/rollbar)
  </Accordion>

  <Accordion title="Sentry · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/sentry/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/sentry/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/sentry/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/sentry/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/sentry/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/sentry)
  </Accordion>

  <Accordion title="Splunk · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/splunk/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/splunk/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/splunk/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/splunk/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/splunk/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/splunk)
  </Accordion>

  <Accordion title="Uptime Robot · 18 cards">
    **Key cards:** [Alerts Acknowledged](/nerve-centre/kpi-cards/uptime-robot/alerts-acknowledged), [Alerts Firing](/nerve-centre/kpi-cards/uptime-robot/alerts-firing), [Apdex Score](/nerve-centre/kpi-cards/uptime-robot/apdex-score), [Avg Response Time](/nerve-centre/kpi-cards/uptime-robot/avg-response-time), [Error Rate](/nerve-centre/kpi-cards/uptime-robot/error-rate)

    [View all 18 cards →](/nerve-centre/kpi-cards/uptime-robot)
  </Accordion>

  <Accordion title="Website Performance (PageSpeed + CrUX) · 79 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/website-performance/accessibility-score), [Accessibility Score](/nerve-centre/kpi-cards/website-performance/accessibility-score), [All CWV Pass](/nerve-centre/kpi-cards/website-performance/all-cwv-pass), [Best Practices Score](/nerve-centre/kpi-cards/website-performance/best-practices-score), [Best Practices Score](/nerve-centre/kpi-cards/website-performance/best-practices-score)

    [View all 79 cards →](/nerve-centre/kpi-cards/website-performance)
  </Accordion>
</AccordionGroup>

### Version Control

Azure DevOps, Bitbucket, GitHub, GitLab

Source-control and DevOps platforms. Track deployment cadence, change volume and incident correlation against store health. Connectors without a linked card page are live in the app with documentation on the way.

### Support

<AccordionGroup>
  <Accordion title="Crisp · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/crisp/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/crisp/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/crisp/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/crisp)
  </Accordion>

  <Accordion title="Freshdesk · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/freshdesk/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/freshdesk/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/freshdesk/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/freshdesk)
  </Accordion>

  <Accordion title="Gorgias · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/gorgias/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/gorgias/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/gorgias/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/gorgias)
  </Accordion>

  <Accordion title="Help Scout · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/helpscout/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/helpscout/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/helpscout/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/helpscout)
  </Accordion>

  <Accordion title="Intercom · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/intercom/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/intercom/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/intercom/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/intercom)
  </Accordion>

  <Accordion title="LiveAgent · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/liveagent/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/liveagent/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/liveagent/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/liveagent)
  </Accordion>

  <Accordion title="LiveChat · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/livechat/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/livechat/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/livechat/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/livechat)
  </Accordion>

  <Accordion title="Tidio · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/tidio/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/tidio/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/tidio/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/tidio)
  </Accordion>

  <Accordion title="Zendesk · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/zendesk/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/zendesk/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/zendesk/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/zendesk)
  </Accordion>
</AccordionGroup>

### Content & Docs

<AccordionGroup>
  <Accordion title="Confluence · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/confluence/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/confluence/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/confluence/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/confluence)
  </Accordion>

  <Accordion title="Notion · 23 cards">
    **Key Metrics cards:** [Abandoned Findings (>14d no movement)](/nerve-centre/kpi-cards/notion/abandoned-findings), [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/notion/finding-resolution-rate), [VortexIQ Findings Open](/nerve-centre/kpi-cards/notion/vortexiq-findings-open)

    [View all 23 cards →](/nerve-centre/kpi-cards/notion)
  </Accordion>
</AccordionGroup>

### CMS

<AccordionGroup>
  <Accordion title="Ghost · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/ghost/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/ghost/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/ghost/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/ghost/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/ghost/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/ghost)
  </Accordion>

  <Accordion title="Prismic · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/prismic/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/prismic/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/prismic/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/prismic/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/prismic/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/prismic)
  </Accordion>

  <Accordion title="Sanity · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/sanity/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/sanity/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/sanity/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/sanity/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/sanity/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/sanity)
  </Accordion>

  <Accordion title="Strapi · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/strapi/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/strapi/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/strapi/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/strapi/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/strapi/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/strapi)
  </Accordion>

  <Accordion title="WordPress · 14 cards">
    **Key cards:** [Accessibility Score](/nerve-centre/kpi-cards/wordpress/accessibility-score), [Best Practices Score](/nerve-centre/kpi-cards/wordpress/best-practices-score), [CLS (Mobile)](/nerve-centre/kpi-cards/wordpress/cls), [CWV Pass Rate (Mobile)](/nerve-centre/kpi-cards/wordpress/cwv-pass-rate), [INP (Mobile)](/nerve-centre/kpi-cards/wordpress/inp)

    [View all 14 cards →](/nerve-centre/kpi-cards/wordpress)
  </Accordion>
</AccordionGroup>

### Social Media

<AccordionGroup>
  <Accordion title="Instagram · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/instagram/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/instagram/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/instagram/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/instagram/goal-completions), [New Users](/nerve-centre/kpi-cards/instagram/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/instagram)
  </Accordion>

  <Accordion title="Reddit · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/reddit/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/reddit/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/reddit/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/reddit/goal-completions), [New Users](/nerve-centre/kpi-cards/reddit/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/reddit)
  </Accordion>

  <Accordion title="TikTok · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/tiktok-organic/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/tiktok-organic/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/tiktok-organic/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/tiktok-organic/goal-completions), [New Users](/nerve-centre/kpi-cards/tiktok-organic/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/tiktok-organic)
  </Accordion>

  <Accordion title="X (Twitter) · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/twitter/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/twitter/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/twitter/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/twitter/goal-completions), [New Users](/nerve-centre/kpi-cards/twitter/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/twitter)
  </Accordion>

  <Accordion title="YouTube · 13 cards">
    **Key cards:** [Avg Session Duration](/nerve-centre/kpi-cards/youtube/avg-session-duration), [Bounce Rate](/nerve-centre/kpi-cards/youtube/bounce-rate), [Cart Abandonment Rate](/nerve-centre/kpi-cards/youtube/cart-abandonment-rate), [Goal Completions](/nerve-centre/kpi-cards/youtube/goal-completions), [New Users](/nerve-centre/kpi-cards/youtube/new-users)

    [View all 13 cards →](/nerve-centre/kpi-cards/youtube)
  </Accordion>
</AccordionGroup>

## Reconnect or re-authorise a connector

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:

<Steps>
  <Step title="Open Connected Sources">
    Navigate to **Settings → Connected Sources**.
  </Step>

  <Step title="Find the affected connector">
    Connectors with expired authorisation show a red status badge. Click the connector to open its settings panel.
  </Step>

  <Step title="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.
  </Step>
</Steps>


# Understanding Nerve Centre KPI cards and card types
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards

Each Nerve Centre KPI card is a named metric with a chart type and alert trigger. Learn how Key Metrics, Supporting Metrics, and Cross-Platform Metrics types work.

A card is the unit of work inside the Nerve Centre. Each card represents one question asked of one data source over one defined time window - for example, "Shopify Total Revenue, last 30 days versus the prior 30 days" or "Google Ads Zero-Conversion Spend, last 30 days". The card is the smallest object that has a stable identity, a stable query, and a stable visual treatment. The merchant trusts a card the same way they trust a row in a financial report: same definition every day, same window logic every day, same colour rules every day.

A card is not a chart. A chart is one of the things a card can render. A card is the wrapper: identity, metadata, query binding, render rules, alert binding, and sentiment binding.

## Metrics types

The cards in the Nerve Centre catalogue are classified into three metrics types.

### Key Metrics cards

Key Metrics cards answer the questions you ask of a connector on a typical day - not weekly, not quarterly, but daily. They are editorially curated by the Vortex IQ product team in collaboration with the merchant base, capped at roughly 15 percent of each connector's card set.

A metric becomes a Key Metric after two checks:

1. **Universality** - does every merchant on this connector ask this question regularly?
2. **Decision impact** - does the answer change what the merchant does today?

Key Metrics cards render in a larger tile at the top of each category group. They carry a coloured accent border that picks up the card's sentiment colour. They surface in the Executive view (the cross-connector morning scan) and lead every scheduled briefing.

**Example Key Metrics cards per connector:**

* **Shopify** - Total Revenue, Order Count, Refund Rate, AOV, Conversion Rate
* **Stripe** - Authorisation Rate, Successful Charges, Decline Rate by Reason
* **Google Ads** - ROAS, Spend, Cost per Acquisition, Zero-Conversion Spend, Wasted Spend
* **Klaviyo** - Active Subscribers, Open Rate, Click Rate, Revenue Per Recipient
* **Datadog** - Checkout Latency p95, Error Rate, Open Incidents

### Supporting Metrics cards

Supporting Metrics cards are the long-tail breakdowns that fill out each connector's card set: ROAS by Campaign, Spend by Device, Conversions by Hour, CPC by Region, and hundreds more. Supporting does not mean unimportant - a merchant investigating a performance drop needs the breakdowns. What changes is the visual treatment: smaller tiles in the secondary grid, excluded from the Executive view by default, snapshotted weekly rather than daily in Vortex Memory.

### Cross-Platform Metrics cards

Cross-Platform Metrics cards join data from two or more connectors to compute a value that no single connector could produce alone. The card's `cross_channel` flag is `true` and the `derive_from` field lists the source connectors. Examples:

* **Active Ads on Out-of-Stock SKUs** (`derive_from: [google_ads, shopify]`) - for each SKU advertised in Google Ads in the last 24 hours, what is the current Shopify inventory level? When spend > 0 and inventory == 0, you are paying for clicks on out-of-stock product.
* **Revenue at Risk from active incidents** (`derive_from: [stripe, shopify]`) - joins Stripe decline spikes with Shopify refund spikes inside the same window to surface payment-vendor incidents before they appear in your support queue.
* **LCP-to-Conversion Correlation** (`derive_from: [website_performance, google_analytics]`) - maps Largest Contentful Paint scores to session conversion rates by landing page.

Cross-Platform Metrics cards are roughly 4 to 7 percent of the catalogue and render in a larger tile with a distinctive connecting-lines icon. Clicking a Cross-Platform Metrics card routes you into the corresponding Vortex Mind diagnostic report.

## Card categories

Within each connector's tab, cards are grouped by **category**. The categories mirror the way the vendor's own admin presents its data, so the metric you know from Google Ads or Shopify's own dashboard sits in the same logical place inside the Nerve Centre.

Common categories across connectors:

| Category                 | What you find there                                                                                           |
| ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Executive Overview       | Headline KPIs: total revenue, total spend, ROAS, CPA trend                                                    |
| Alerts & Anomalies       | Cards that fire when something breaks: Conversion Drop Alert, CPC Spike, Spend Anomaly, Zero-Conversion Spend |
| Campaign Performance     | Revenue, ROAS, CTR, and CPC broken down by individual campaign                                                |
| Budget Monitoring        | Spend vs Budget, Budget Utilisation gauge, Overspending and Underspending Campaigns                           |
| Funnel & Conversion      | Conversion funnel, conversion lag, conversion rate by campaign and device                                     |
| Keyword Intelligence     | Wasted Spend, Top Keywords by Spend and Conversions, Quality Score Distribution                               |
| Device Performance       | ROAS, CPC, CTR, and conversion rate broken down by device type                                                |
| Geography Performance    | Conversions, spend, and revenue by country, region, and city                                                  |
| Day & Time Performance   | Conversions by hour (heatmap), spend by day of week, CPC by hour                                              |
| Landing Page Performance | CPC, conversion rate, and revenue broken out by landing page URL                                              |

## Chart types

Each card renders one of the following chart types, chosen to match the shape of the data:

| Chart type               | Used for                                                                                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `kpi`                    | Single scalar value with trend arrow and sentiment colour. Used for Key Metrics headline metrics (Total Revenue, Total Spend, Zero-Conversion Spend). |
| `gauge`                  | Percentage or rate within a defined range. Used for Budget Utilisation, ROAS (as a level indicator), Authorisation Rate.                              |
| `sparkline`              | Compact trend line showing direction over the time window. Used for ROAS Trend, CPC Trend, Conversions Trend.                                         |
| `area`                   | Filled time-series showing volume over time. Used for Spend Over Time, Revenue Over Time.                                                             |
| `bar`                    | Vertical bar chart for categorical comparisons over time. Used for Conversions by Day of Week, Spend by Hour.                                         |
| `bar_horizontal`         | Horizontal bar chart for ranked categorical breakdowns. Used for ROAS by Campaign, Revenue by Campaign, CPC by Region.                                |
| `line`                   | Time-series line. Used for CPC by Hour.                                                                                                               |
| `donut`                  | Part-to-whole distribution. Used for Conversions by Device, Spend by Device, Conversion Actions Breakdown.                                            |
| `funnel`                 | Step-by-step drop-off visualisation. Used for Conversion Funnel.                                                                                      |
| `table`                  | Ranked row data. Used for Campaign Comparison, Top Keywords by Spend, Landing Page Performance.                                                       |
| `heatmap`                | Two-dimensional intensity grid. Used for Conversions by Hour (day-of-week × hour-of-day).                                                             |
| `geo_map` / `choropleth` | Geography heat map. Used for Conversions by Country, Spend by Country.                                                                                |
| `progress`               | Linear progress bar showing spend relative to budget cap. Used for Spend vs Budget.                                                                   |
| `dual_axis`              | Two series on a shared time axis with separate Y scales. Used for Clicks vs Conversions.                                                              |
| `alert_list`             | Structured alert feed. Used for real-time alert cards (ROAS Drop Alert, CPC Spike Alert).                                                             |
| `scatter`                | Two-axis correlation plot. Used for LCP-to-Conversion cross-platform cards.                                                                           |

## Real card examples

### ROAS (Google Ads) - Key Metrics

The ROAS card (`gads_roas`) is a `gauge` chart in the Executive Overview category. It displays Return on Ad Spend - revenue divided by ad spend - for the selected time window compared to the prior comparable period. Across most ad-platform connectors (AdRoll, Amazon Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Microsoft Ads, and others), ROAS is consistently a Key Metrics card because it is the primary signal of whether paid acquisition is profitable.

<Note>
  ROAS of 4.0× means £4 of revenue per £1 of ad spend. Below 2.0× is unprofitable for most direct-to-consumer brands after accounting for cost of goods, fulfilment, and overheads.
</Note>

### Zero-Conversion Spend (Google Ads) - Key Metrics, `gads_zero_conversion_spend`

This `kpi` card surfaces the total spend on enabled campaigns that produced **zero primary conversions** over the last 30 days. The formula sums `cost_micros ÷ 1,000,000` for every campaign where `metrics.conversions = 0` and `campaign.status = ENABLED`. The alert fires at any non-zero value; an action prompt fires at spend above the threshold (default: \$500 per 30-day window).

A worked example from the source data: a UK fashion brand with £27,400 total Google Ads spend had £680 of zero-conversion spend across two campaigns - a Display Remarketing campaign with too-small an audience (£420) and a mismatched "vintage 90s" search campaign (£260). Pausing both was a five-minute action recovering 2.5 percent of total spend.

### ROAS Drop Alert (Google Ads) - Key Metrics, `gads_alert_roas_drop`

An `alert_list` card with `data_type: Real-time`. The alert fires when today's ROAS drops more than 25 percent versus the average of the same day-of-week over the prior seven days. The card is suppressed before 14:00 local time to avoid false positives from incomplete morning data. It sits alongside Conversion Drop Alert and CPC Spike Alert as the first-responder cards for a Google Ads account going wrong.

## Card metadata

Every card carries a fixed metadata shape used by the Nerve Centre renderer, the alert engine, Vortex Mind, Ask Viq, and the documentation generator. Key fields:

| Field           | Example                                    | Purpose                                                                                                             |
| --------------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| `id`            | `gads_zero_conversion_spend`               | Stable identifier. Persists across label renames.                                                                   |
| `label`         | "Zero-Conversion Spend"                    | Human-readable name shown on the tile.                                                                              |
| `category`      | "Alerts & Anomalies"                       | The group the card sits under in the connector tab.                                                                 |
| `chart_type`    | `kpi`                                      | How the card renders.                                                                                               |
| `time_window`   | `30D`, `7D`, `RT`                          | Default lookback for the card.                                                                                      |
| `alert_trigger` | `">$0 (any campaign with spend, no conv)"` | The condition that fires an alert.                                                                                  |
| `sentiment_key` | `zero_conversion_spend`                    | The colour rule used to mark the value green, amber, or red.                                                        |
| `tier`          | `hero` or `standard`                       | Metrics type for dashboard prominence: `hero` shows as **Key Metrics**, `standard` shows as **Supporting Metrics**. |
| `roles`         | `[owner, marketing, finance]`              | Who the card is for; drives alert routing.                                                                          |
| `data_type`     | `API-derived`, `Real-time`, `Native`       | Where the data comes from and how it refreshes.                                                                     |

## Navigating to a connector's cards

<Steps>
  <Step title="Open the Nerve Centre">
    Click **Nerve Centre** in the left navigation. The connector tab row appears at the top of the dashboard.
  </Step>

  <Step title="Select a connector tab">
    Click the tab for the connector you want - for example, Google Ads, Shopify, or Klaviyo. If the connector is not yet connected, the tab shows a "Connect to unlock" placeholder.
  </Step>

  <Step title="Browse by category">
    Cards are grouped by category. Expand any category group to see all cards in it. Use the **Key Metrics only** filter (top-right) to collapse the view to Key Metrics cards only.
  </Step>

  <Step title="Open a card's full documentation">
    Click the info icon on any card tile to open its documentation page. The doc page covers the metric definition, calculation formula, source field trace, worked example, sibling cards, and FAQs.
  </Step>
</Steps>

<Tip>
  Use the **Executive view** toggle (dashboard header) to see Key Metrics and Cross-Platform Metrics cards across every connected connector at once. This is the fastest way to spot which connectors have active alerts or amber metrics.
</Tip>


# AbeBooks audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/abebooks/audit

What the Vortex IQ AbeBooks health audit checks: AbeBooks: FTPS Feed Health, Listing Visibility & Cross-Platform ISBN Leak

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/abebooks) · [Audit Profile](/nerve-centre/kpi-cards/abebooks/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/abebooks/sentiment)**

AbeBooks is a used / rare-book reseller marketplace served entirely over FTPS (no real-time API). Audits cover FTPS connectivity + feed-cycle health, listing visibility (suspended, pending, stale, missing-ISBN), order fulfilment SLA (the seller-rating signal that drives AbeBooks account standing), pricing / margin watch on rare titles, and cross-platform ISBN comparisons against Alibris + Amazon book listings to surface drift, missing-on-AbeBooks ISBNs, and channel-mix imbalance for book-trade merchants.

## What this audit checks

### Authentication & connectivity

* FTPS login on ftp.abebooks.com:21 succeeds (220 -> AUTH TLS -> 230)
* Explicit AUTH TLS upgrade negotiated correctly (no plain-FTP fallback)
* TLS server certificate verifies (verify\_peer is on)
* Passive-mode data channel opens on the merchant's egress
* Drop folders /inbox + /outbox readable / writable for the merchant's username
* Time skew between merchant clock and AbeBooks server \<5 min (TLS sanity)

### Listing-feed health

* Last successful /outbox/listings upload \<48h (any older = feed blind)
* Failed batches in /inbox/acks (any > 0 = rows AbeBooks rejected)
* Top error patterns clustered from inbound ack files (drives 'fix once' bug list)
* ISBN coverage \<90% (untracked listings can't cross-reference Alibris / Amazon)
* Stale listings >180d no update >10% of catalogue
* Suspended / pending listings >0 (direct revenue blocker)

### Order-feed health

* Inbound /inbox/orders file lag >12h (probable upstream incident)
* Pending dispatch >2x 30D average (back-office backlog)
* Avg time to process >24h
* Late dispatches past dispatch\_due\_by >5% of 30D orders (account-standing risk)
* Cancellation rate >3%
* Return rate >5% (book-trade tolerates some, watch for grading drift on used stock)

### Cost & efficiency

* Commission paid % of revenue drift vs prior 90D
* Avg dispatch hours rising trend (fulfilment cost creep)
* Per-condition margin: like\_new / very\_good vs acceptable mix shift
* AOV drop with no volume drop (mix shift to lower-condition stock)

### Cross-platform: leak vs Alibris + Amazon (the killer area)

* ISBN drift - same ISBN, AbeBooks vs Alibris vs Amazon price delta >15%
* Top-50 Alibris / Amazon book-revenue ISBNs not listed on AbeBooks (cheapest revenue lift)
* AbeBooks price >15% below merchant's own DTC list on like\_new / very\_good first editions (margin erosion)
* Channel mix anomaly: AbeBooks share of book-trade revenue dropping >25% WoW vs sibling book marketplaces
* Outbound feed cycle desync: same SKU updated on Alibris but no AbeBooks /outbox/listings upload in 7d

## Severity thresholds

| Signal                               | Warn | Critical |
| ------------------------------------ | ---- | -------- |
| `hours_since_last_successful_upload` | 24   | 48       |
| `failed_batch_count_7d`              | 1    | 5        |
| `isbn_coverage_pct`                  | 90   | 80       |
| `suspended_listings_count`           | 1    | 5        |
| `stale_listings_pct`                 | 5    | 10       |
| `inbound_orders_file_lag_hours`      | 6    | 12       |
| `pending_dispatch_multiplier`        | 1.5  | 2        |
| `avg_time_to_process_hours`          | 18   | 24       |
| `late_dispatch_pct`                  | 3    | 5        |
| `cancellation_rate_pct`              | 2    | 3        |
| `return_rate_pct`                    | 4    | 5        |
| `isbn_drift_count`                   | 5    | 10       |
| `missing_on_abebooks_count`          | 3    | 5        |
| `rare_book_floor_violation_count`    | 1    | 5        |

## Data sources

* `GET ftps://ftp.abebooks.com:21/inbox/orders/` - Download daily order files for SLA + revenue audits.
* `GET ftps://ftp.abebooks.com:21/inbox/acks/` - Read upload acks + processed-with-errors reports for feed-health audit.
* `GET ftps://ftp.abebooks.com:21/inbox/returns/` - Return + refund notifications for return-rate audit.
* `PUT ftps://ftp.abebooks.com:21/outbox/listings/` - Upload-cycle telemetry source - confirmed-vs-rejected counts drive feed health.
* `PUT ftps://ftp.abebooks.com:21/outbox/price/` - Price delta uploads - per-batch ack timing.
* `PUT ftps://ftp.abebooks.com:21/outbox/quantity/` - Quantity-only uploads - fast availability updates.


# AbeBooks KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/abebooks/index

Every AbeBooks KPI pulse Vortex IQ Nerve Centre tracks: 52 metrics covering revenue, orders, customers, refunds, and more.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/abebooks) · [Audit Profile](/nerve-centre/kpi-cards/abebooks/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/abebooks/sentiment)**

Vortex IQ Nerve Centre tracks **52** KPI pulses for AbeBooks stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves.

The AbeBooks connector covers the Amazon-owned global marketplace for books - used and rare books, antiquarian sellers, university booksellers. The **Nerve Centre** tracks 52 KPI pulses for AbeBooks accounts in the Vortex IQ **AI OS** catalogue - including hero alerts (*Feed Cycle Failure*, *Last Successful Upload*, *Late Order Processing Queue*, *Listings Processed With Errors*, *Pending Dispatch*, *Suspended/Pending Listings*, *Dispatch SLA Compliance*) plus cross-platform cards that fuse AbeBooks with the broader book trade (*ISBN Drift vs Alibris + Amazon*, *AbeBooks Share of Book-Trade Revenue*, *Rare-Book Price Floor Watch*). **Vortex Mind** investigates when feed cycles fail or rare-book pricing drifts; **Ask Viq™** lets you ask in plain English with citations back to the source card.

| Card                                                                                                              | Metrics type           | Category                 | Chart           |
| ----------------------------------------------------------------------------------------------------------------- | ---------------------- | ------------------------ | --------------- |
| [Dispatch SLA Compliance](/nerve-centre/kpi-cards/abebooks/dispatch-sla-compliance)                               | Key Metrics            | Executive Command Centre | gauge           |
| [Feed Cycle Failure](/nerve-centre/kpi-cards/abebooks/feed-cycle-failure)                                         | Key Metrics            | Nerve Centre             | alert\_list     |
| [Last Successful Upload](/nerve-centre/kpi-cards/abebooks/last-successful-upload)                                 | Key Metrics            | Feed Operations          | kpi             |
| [Late Order Processing Queue](/nerve-centre/kpi-cards/abebooks/late-order-processing-queue)                       | Key Metrics            | Nerve Centre             | alert\_table    |
| [Listings Processed With Errors](/nerve-centre/kpi-cards/abebooks/listings-processed-with-errors)                 | Key Metrics            | Listing Health           | kpi             |
| [Pending Dispatch](/nerve-centre/kpi-cards/abebooks/pending-dispatch)                                             | Key Metrics            | Fulfilment               | kpi             |
| [Revenue at Risk (live)](/nerve-centre/kpi-cards/abebooks/revenue-at-risk)                                        | Key Metrics            | Executive Command Centre | kpi             |
| [Suspended / Pending Listings](/nerve-centre/kpi-cards/abebooks/suspended-pending-listings)                       | Key Metrics            | Listing Health           | kpi             |
| [Total Revenue](/nerve-centre/kpi-cards/abebooks/total-revenue)                                                   | Key Metrics            | Executive Command Centre | kpi             |
| [AbeBooks Share of Book-Trade Revenue](/nerve-centre/kpi-cards/abebooks/abebooks-share-of-book-trade-revenue)     | Cross-Platform Metrics | Revenue at Risk          | donut           |
| [ISBN Drift vs Alibris + Amazon](/nerve-centre/kpi-cards/abebooks/isbn-drift-vs-alibris-amazon)                   | Cross-Platform Metrics | Revenue at Risk          | table           |
| [Rare-Book Price Floor Watch](/nerve-centre/kpi-cards/abebooks/rare-book-price-floor-watch)                       | Cross-Platform Metrics | Revenue at Risk          | alert\_table    |
| [Top-Velocity ISBNs Missing on AbeBooks](/nerve-centre/kpi-cards/abebooks/top-velocity-isbns-missing-on-abebooks) | Cross-Platform Metrics | Revenue at Risk          | kpi             |
| [AbeBooks Health Score](/nerve-centre/kpi-cards/abebooks/abebooks-health-score)                                   | Supporting Metrics     | Executive Command Centre | gauge           |
| [Active Listings](/nerve-centre/kpi-cards/abebooks/active-listings)                                               | Supporting Metrics     | Listings                 | kpi             |
| [Active Listings](/nerve-centre/kpi-cards/abebooks/active-listings)                                               | Supporting Metrics     | Executive Command Centre | kpi             |
| [AOV by Country](/nerve-centre/kpi-cards/abebooks/aov-by-country)                                                 | Supporting Metrics     | Geography                | bar             |
| [Average Order Value](/nerve-centre/kpi-cards/abebooks/average-order-value)                                       | Supporting Metrics     | Sales                    | kpi             |
| [Average Order Value](/nerve-centre/kpi-cards/abebooks/average-order-value)                                       | Supporting Metrics     | Revenue & Sales          | kpi             |
| [Avg Review Rating](/nerve-centre/kpi-cards/abebooks/avg-review-rating)                                           | Supporting Metrics     | Reputation               | gauge           |
| [Avg Time to Process (hrs)](/nerve-centre/kpi-cards/abebooks/avg-time-to-process)                                 | Supporting Metrics     | Fulfilment               | kpi             |
| [Buyer Messages Unread](/nerve-centre/kpi-cards/abebooks/buyer-messages-unread)                                   | Supporting Metrics     | Reputation               | kpi             |
| [Cancellation Rate](/nerve-centre/kpi-cards/abebooks/cancellation-rate)                                           | Supporting Metrics     | Fulfilment               | gauge           |
| [Dispute Rate](/nerve-centre/kpi-cards/abebooks/dispute-rate)                                                     | Supporting Metrics     | Returns                  | gauge           |
| [Failed Batches (7d)](/nerve-centre/kpi-cards/abebooks/failed-batches)                                            | Supporting Metrics     | Feed Operations          | kpi             |
| [Fees as % of Revenue](/nerve-centre/kpi-cards/abebooks/fees-as-of-revenue)                                       | Supporting Metrics     | Economics                | gauge           |
| [FTPS Connection / Auth Health](/nerve-centre/kpi-cards/abebooks/ftps-connection-auth-health)                     | Supporting Metrics     | Nerve Centre             | kpi             |
| [Inbound Orders File Lag](/nerve-centre/kpi-cards/abebooks/inbound-orders-file-lag)                               | Supporting Metrics     | Feed Operations          | kpi             |
| [ISBN Coverage](/nerve-centre/kpi-cards/abebooks/isbn-coverage)                                                   | Supporting Metrics     | Listing Health           | gauge           |
| [Listing Error Spike (24h)](/nerve-centre/kpi-cards/abebooks/listing-error-spike)                                 | Supporting Metrics     | Nerve Centre             | alert\_list     |
| [Listing Quality Score](/nerve-centre/kpi-cards/abebooks/listing-quality-score)                                   | Supporting Metrics     | Listings                 | gauge           |
| [Listings Expiring Soon](/nerve-centre/kpi-cards/abebooks/listings-expiring-soon)                                 | Supporting Metrics     | Listings                 | kpi             |
| [Listings Uploaded (24h)](/nerve-centre/kpi-cards/abebooks/listings-uploaded)                                     | Supporting Metrics     | Listing Health           | kpi             |
| [Marketplace Fees Paid](/nerve-centre/kpi-cards/abebooks/marketplace-fees-paid)                                   | Supporting Metrics     | Economics                | kpi             |
| [Net Revenue (after commission + refunds)](/nerve-centre/kpi-cards/abebooks/net-revenue)                          | Supporting Metrics     | Revenue & Sales          | kpi             |
| [Oldest Pending Payout (days)](/nerve-centre/kpi-cards/abebooks/oldest-pending-payout)                            | Supporting Metrics     | Economics                | kpi             |
| [Orders](/nerve-centre/kpi-cards/abebooks/orders)                                                                 | Supporting Metrics     | Revenue & Sales          | kpi             |
| [Orders / Day](/nerve-centre/kpi-cards/abebooks/orders-day)                                                       | Supporting Metrics     | Fulfilment               | line            |
| [Orders by Country](/nerve-centre/kpi-cards/abebooks/orders-by-country)                                           | Supporting Metrics     | Geography                | choropleth      |
| [Out-of-Stock Listings](/nerve-centre/kpi-cards/abebooks/out-of-stock-listings)                                   | Supporting Metrics     | Listings                 | kpi             |
| [Pending Payouts](/nerve-centre/kpi-cards/abebooks/pending-payouts)                                               | Supporting Metrics     | Economics                | kpi             |
| [Return Rate](/nerve-centre/kpi-cards/abebooks/return-rate)                                                       | Supporting Metrics     | Returns                  | gauge           |
| [Return Rate](/nerve-centre/kpi-cards/abebooks/return-rate)                                                       | Supporting Metrics     | Fulfilment               | gauge           |
| [Revenue Over Time](/nerve-centre/kpi-cards/abebooks/revenue-over-time)                                           | Supporting Metrics     | Revenue & Sales          | area            |
| [Seller Feedback Score](/nerve-centre/kpi-cards/abebooks/seller-feedback-score)                                   | Supporting Metrics     | Reputation               | gauge           |
| [Stale Listings (>180d no update)](/nerve-centre/kpi-cards/abebooks/stale-listings)                               | Supporting Metrics     | Listing Health           | kpi             |
| [Top Listings by Revenue](/nerve-centre/kpi-cards/abebooks/top-listings-by-revenue)                               | Supporting Metrics     | Sales                    | bar\_horizontal |
| [Top Titles by Revenue](/nerve-centre/kpi-cards/abebooks/top-titles-by-revenue)                                   | Supporting Metrics     | Revenue & Sales          | bar\_horizontal |
| [Top Upload Error Types](/nerve-centre/kpi-cards/abebooks/top-upload-error-types)                                 | Supporting Metrics     | Feed Operations          | bar\_horizontal |
| [Total Listings](/nerve-centre/kpi-cards/abebooks/total-listings)                                                 | Supporting Metrics     | Listing Health           | kpi             |
| [Total Revenue](/nerve-centre/kpi-cards/abebooks/total-revenue)                                                   | Supporting Metrics     | Sales                    | kpi             |
| [Total Transactions](/nerve-centre/kpi-cards/abebooks/total-transactions)                                         | Supporting Metrics     | Sales                    | kpi             |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector. Replace this block when authored.*


# AbeBooks sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/abebooks/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag AbeBooks KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/abebooks) · [Audit Profile](/nerve-centre/kpi-cards/abebooks/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/abebooks/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each AbeBooks KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **6** of the 35 AbeBooks cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                                                                                              | Direction       | Good | Bad | Unit  |
| ------------------------------------------------------------------------------------------------- | --------------- | ---- | --- | ----- |
| [Failed Batches (7d)](/nerve-centre/kpi-cards/abebooks/failed-batches-7d)                         | Lower is better | 5    | 50  | Count |
| [ISBN Coverage](/nerve-centre/kpi-cards/abebooks/isbn-coverage)                                   | Lower is better | 5    | 50  | %     |
| [ISBN Drift vs Alibris + Amazon](/nerve-centre/kpi-cards/abebooks/isbn-drift-vs-alibris-amazon)   | Lower is better | 5    | 50  | Count |
| [Listing Error Spike (24h)](/nerve-centre/kpi-cards/abebooks/listing-error-spike-24h)             | Lower is better | 5    | 50  | Count |
| [Listings Processed With Errors](/nerve-centre/kpi-cards/abebooks/listings-processed-with-errors) | Lower is better | 5    | 50  | Count |
| [Suspended / Pending Listings](/nerve-centre/kpi-cards/abebooks/suspended-pending-listings)       | Lower is better | 5    | 50  | Count |


# ActiveCampaign audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/activecampaign/audit

What the Vortex IQ ActiveCampaign health audit checks: ActiveCampaign Email + Automation Programme Health

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/activecampaign) · [Audit Profile](/nerve-centre/kpi-cards/activecampaign/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/activecampaign/sentiment)**

Audits automations, list and segmentation health, deliverability, and revenue attribution for merchants on ActiveCampaign. Answers four daily questions: are sends landing in the inbox, are the welcome / abandoned-cart automations live, is the audience growing, and is email pulling its weight in store revenue. Cross-platform value lands when a commerce sibling (Shopify / BigCommerce / Adobe Commerce) is connected - email-attributed revenue and abandoned-cart recovery value become computable in £/\$.

## What this audit checks

### Authentication & access

* API token valid against /api/3/users/me
* Token user has Campaigns, Automations, Lists, Segments, Contacts permissions
* Account API URL reachable (per-account host resolves)

### Automations

* Inactive automations (draft / inactive status)
* Welcome automation present and active
* Abandoned-cart automation present and active
* Automations with zero contacts entered

### Lists & segmentation

* List count and growth rate
* Segment count (under-segmentation below 3)
* Bounced / unsubscribed contact share per list

### Deliverability

* Bounce rate (hard + soft) across recent campaigns
* Spam complaint rate vs ISP threshold
* Delivery rate below 95%

### Revenue attribution

* Email-attributed revenue trend
* Top-performing automations by revenue

### Cross-platform: email revenue at risk

* Email share of total store revenue (sibling = shopify|bigcommerce|adobe\_commerce on customer\_email)
* Abandoned-cart recovery value in £/\$ (sibling commerce AOV × recovered carts)
* Campaigns advertising out-of-stock SKUs (sibling = ecommerce\_platform inventory)

## Data sources

* `GET https://{account}.api-us1.com/api/3/users/me` - Auth probe + user permissions
* `GET https://{account}.api-us1.com/api/3/campaigns` - Campaign metadata + send/open/click/bounce stats
* `GET https://{account}.api-us1.com/api/3/automations` - Automation inventory + status + entered counts
* `GET https://{account}.api-us1.com/api/3/lists` - List metadata + subscriber counts
* `GET https://{account}.api-us1.com/api/3/segments` - Segment definitions
* `GET https://{account}.api-us1.com/api/3/contacts` - Contact status counts for active-subscriber estimate


# ActiveCampaign KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/activecampaign/index

Every ActiveCampaign KPI pulse Vortex IQ Nerve Centre tracks: 29 metrics covering revenue, orders, customers, refunds, and more.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/activecampaign) · [Audit Profile](/nerve-centre/kpi-cards/activecampaign/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/activecampaign/sentiment)**

Vortex IQ Nerve Centre tracks **29** KPI pulses for ActiveCampaign stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves.

The ActiveCampaign connector brings the Vortex IQ **AI OS** to merchants on ActiveCampaign's email + automation + CRM platform - strong on multi-step automation flows and behavioural segmentation for SMB to mid-market brands. The **Nerve Centre** tracks 29 KPI pulses including subscriber, deliverability, engagement, and revenue-attribution metrics. **Vortex Mind** investigates when a number moves; **Ask Viq™** lets you ask in plain English with citations back to the source card.

| Card                                                                                          | Metrics type       | Category            | Chart           |
| --------------------------------------------------------------------------------------------- | ------------------ | ------------------- | --------------- |
| [Active Subscribers (Est.)](/nerve-centre/kpi-cards/activecampaign/active-subscribers)        | Supporting Metrics | Customer Lifecycle  | kpi             |
| [Bounce Rate](/nerve-centre/kpi-cards/activecampaign/bounce-rate)                             | Supporting Metrics | Deliverability      | gauge           |
| [Campaign Status Breakdown](/nerve-centre/kpi-cards/activecampaign/campaign-status-breakdown) | Supporting Metrics | Email Campaigns     | donut           |
| [Checkout-to-Order Rate](/nerve-centre/kpi-cards/activecampaign/checkout-to-order-rate)       | Supporting Metrics | Revenue Attribution | gauge           |
| [Checkouts Started](/nerve-centre/kpi-cards/activecampaign/checkouts-started)                 | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Click-to-Open Rate](/nerve-centre/kpi-cards/activecampaign/click-to-open-rate)               | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Conversion Rate](/nerve-centre/kpi-cards/activecampaign/conversion-rate)                     | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Delivery Rate](/nerve-centre/kpi-cards/activecampaign/delivery-rate)                         | Supporting Metrics | Deliverability      | gauge           |
| [Email Click Rate](/nerve-centre/kpi-cards/activecampaign/email-click-rate)                   | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Email Health KPIs](/nerve-centre/kpi-cards/activecampaign/email-health-kpis)                 | Supporting Metrics | Email Engagement    | kpi             |
| [Email Open Rate](/nerve-centre/kpi-cards/activecampaign/email-open-rate)                     | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Engagement Funnel](/nerve-centre/kpi-cards/activecampaign/engagement-funnel)                 | Supporting Metrics | Email Engagement    | funnel          |
| [Flow Count Summary](/nerve-centre/kpi-cards/activecampaign/flow-count-summary)               | Supporting Metrics | Email Automation    | kpi             |
| [Flow Status Breakdown](/nerve-centre/kpi-cards/activecampaign/flow-status-breakdown)         | Supporting Metrics | Email Automation    | donut           |
| [Flow Trigger Types](/nerve-centre/kpi-cards/activecampaign/flow-trigger-types)               | Supporting Metrics | Email Automation    | donut           |
| [Flows List](/nerve-centre/kpi-cards/activecampaign/flows-list)                               | Supporting Metrics | Email Automation    | table           |
| [List Count](/nerve-centre/kpi-cards/activecampaign/list-count)                               | Supporting Metrics | Customer Lifecycle  | kpi             |
| [List Health Summary](/nerve-centre/kpi-cards/activecampaign/list-health-summary)             | Supporting Metrics | List Health         | kpi             |
| [Lists Overview](/nerve-centre/kpi-cards/activecampaign/lists-overview)                       | Supporting Metrics | Customer Lifecycle  | table           |
| [Placed Orders Total](/nerve-centre/kpi-cards/activecampaign/placed-orders-total)             | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Refund Rate](/nerve-centre/kpi-cards/activecampaign/refund-rate)                             | Supporting Metrics | Revenue Attribution | gauge           |
| [Revenue per Recipient](/nerve-centre/kpi-cards/activecampaign/revenue-per-recipient)         | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Revenue per Send](/nerve-centre/kpi-cards/activecampaign/revenue-per-send)                   | Supporting Metrics | Revenue Attribution | kpi             |
| [Segments Overview](/nerve-centre/kpi-cards/activecampaign/segments-overview)                 | Supporting Metrics | Customer Lifecycle  | table           |
| [Spam Complaint Rate](/nerve-centre/kpi-cards/activecampaign/spam-complaint-rate)             | Supporting Metrics | Deliverability      | gauge           |
| [Top Lists by Name](/nerve-centre/kpi-cards/activecampaign/top-lists-by-name)                 | Supporting Metrics | List Health         | bar\_horizontal |
| [Total Revenue](/nerve-centre/kpi-cards/activecampaign/total-revenue)                         | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Total Sends](/nerve-centre/kpi-cards/activecampaign/total-sends)                             | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Unsubscribe Rate](/nerve-centre/kpi-cards/activecampaign/unsubscribe-rate)                   | Supporting Metrics | Deliverability      | gauge           |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector. Replace this block when authored.*


# ActiveCampaign sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/activecampaign/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag ActiveCampaign KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/activecampaign) · [Audit Profile](/nerve-centre/kpi-cards/activecampaign/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/activecampaign/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each ActiveCampaign KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **7** of the 29 ActiveCampaign cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                                                                              | Direction        | Good | Bad | Unit |
| --------------------------------------------------------------------------------- | ---------------- | ---- | --- | ---- |
| [Bounce Rate](/nerve-centre/kpi-cards/activecampaign/bounce-rate)                 | Lower is better  | 2    | 5   | %    |
| [Click-to-Open Rate](/nerve-centre/kpi-cards/activecampaign/click-to-open-rate)   | Higher is better | 10   | 3   | %    |
| [Delivery Rate](/nerve-centre/kpi-cards/activecampaign/delivery-rate)             | Higher is better | 98   | 95  | %    |
| [Email Click Rate](/nerve-centre/kpi-cards/activecampaign/email-click-rate)       | Higher is better | 3    | 1   | %    |
| [Email Open Rate](/nerve-centre/kpi-cards/activecampaign/email-open-rate)         | Higher is better | 25   | 15  | %    |
| [Spam Complaint Rate](/nerve-centre/kpi-cards/activecampaign/spam-complaint-rate) | Lower is better  | 0.1  | 0.3 | %    |
| [Unsubscribe Rate](/nerve-centre/kpi-cards/activecampaign/unsubscribe-rate)       | Lower is better  | 0.5  | 2   | %    |


# Acumatica audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/acumatica/audit

What the Vortex IQ Acumatica health audit checks: Acumatica: Order-to-Cash Sync, Inventory Parity, AR Aging & GL Health

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/acumatica) · [Audit Profile](/nerve-centre/kpi-cards/acumatica/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/acumatica/sentiment)**

The questions an SMB-to-mid-market finance + operations lead asks at 9am on Monday: did yesterday's storefront orders all land in Acumatica as sales orders + invoices, is multi-warehouse stock-on-hand drifting from the storefront, is AR aging concentrating on customers still placing new ecom orders, and are GL batches posting cleanly so the period can close. Cross-references the ecommerce platforms (BigCommerce / Adobe Commerce / Shopify) - an order with no matching Acumatica invoice, inventory variance on active-order SKUs, or overdue AR on a still-shipping customer are the killer reconciliation findings no single tool can see.

## What this audit checks

### Authentication & access

* OAuth2 token refresh against /identity/connect/token succeeds (client\_id + client\_secret + refresh\_token, scope `api offline_access`)
* Connected Application has the `api` scope and the integration user's role grants read access to SalesOrder / Invoice / Customer / StockItem / JournalTransaction entities
* Contract API version resolves - GET /entity/Default//Company returns the tenant without a 404 (wrong version) or 401 (bad token)
* License-tier concurrent-request limit headroom - sustained 429 / 'License limit exceeded' indicates the API seat is saturated by other integrations

### Order-to-cash health

* Sales orders stuck in Hold / PendingApproval >48h (approval-routing rule broken - blocks fulfilment + invoicing)
* Order-to-cash velocity (storefront order → invoice paid) regressing >20% vs trailing 30d
* Invoices in Hold / PendingApproval blocking AR recognition
* Sales orders Completed but with no corresponding AR invoice after the sync window (revenue not recognised)

### Inventory & distribution health

* Any warehouse QtyOnHand negative (receipt / shipment posting error or oversell)
* Stock days-on-hand >120d on >10% of SKUs (slow movers tying up working capital)
* Warehouse-level stockout (QtyAvailable = 0) on a SKU with open sales orders
* Inventory turns annualised \<4 (distribution-edition efficiency floor)

### AR & GL economics

* AR aged 60+ days above 15% of total AR balance
* Days Sales Outstanding (DSO) above 60 days
* GL journal batches Unposted / OnHold above 50 (close-cycle backlog)
* GL batch with DebitTotal != CreditTotal (imbalanced - blocks period close)
* Financial period open past its scheduled close date by >5 days

### Cross-platform: Acumatica vs ecommerce reconciliation

* Storefront order has no matching Acumatica sales order/invoice after the sync window (sibling = bigcommerce.order / shopify.order / adobe\_commerce.order, by external\_ref)
* Acumatica aggregate QtyAvailable drifts >5% from storefront available qty on SKUs with active orders (sibling = bigcommerce.product / shopify.product / adobe\_commerce.product, by InventoryID=sku)
* Ecom customer with completed orders absent from Acumatica customer master after 7d (sibling = bigcommerce.customer / shopify.customer, by email)
* Customer with AR aged 60+ days still placing new ecom orders (credit risk compounding, sibling = ecommerce customer by email)

## Severity thresholds

| Signal                          | Warn | Critical |
| ------------------------------- | ---- | -------- |
| `erp_open_journal_count`        | 25   | 50       |
| `erp_journal_imbalance_count`   | 1    | 5        |
| `erp_inventory_variance_pct`    | 1    | 5        |
| `erp_ar_aging_60d_pct`          | 5    | 15       |
| `erp_customer_master_drift`     | 5    | 10       |
| `erp_period_close_overdue_days` | 1    | 5        |
| `erp_dso_days`                  | 45   | 60       |
| `stock_days_on_hand`            | 90   | 120      |
| `orders_on_hold_count`          | 5    | 10       |

## Data sources

* `POST /identity/connect/token` - OAuth2 token refresh on the per-tenant Identity Server
* `GET /entity/Default/{version}/Company` - Auth / tenant validation probe
* `GET /entity/Default/{version}/SalesOrder` - Sales orders - order-to-cash, backlog, hold status
* `GET /entity/Default/{version}/Invoice` - AR invoices - balance, aging buckets, DSO
* `GET /entity/Default/{version}/Customer` - Customer master - credit hold, B2B tax reg, master drift
* `GET /entity/Default/{version}/StockItem` - Stock items - cost, status, inventory value
* `PUT /entity/Default/{version}/InventorySummaryInquiry` - Per-warehouse QtyOnHand / QtyAvailable allocation inquiry
* `GET /entity/Default/{version}/Project` - Projects - margin, milestone billing (Project Accounting module)
* `GET /entity/Default/{version}/JournalTransaction` - GL batches - unposted count, debit/credit balance


# Acumatica Connector, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/acumatica/index

Vortex IQ Nerve Centre is adding Acumatica Cloud ERP KPI cards: order-to-cash velocity, multi-entity consolidation, project and distribution signals.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/acumatica) · [Audit Profile](/nerve-centre/kpi-cards/acumatica/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/acumatica/sentiment)**

> Acumatica is the modern cloud ERP gaining ground across SMB and mid-market commerce, and Vortex IQ is building it into the Nerve Centre as a first-class signal source.

## What is Acumatica?

Acumatica is a cloud-native ERP built for small and mid-sized businesses, with industry-specific editions covering construction, distribution, manufacturing, retail and ecommerce, and professional services. Unlike most legacy ERPs, Acumatica uses a resource-based pricing model rather than per-user licensing, which makes it unusually well-suited for businesses with many occasional users (warehouse workers, project managers, partners) who all need read or write access without buying full seats each.

The platform is API-first and built on a modern application stack, with a strong VAR and partner ecosystem in the United States, Canada, Australia, and increasingly the UK and EU. That partner ecosystem is part of why Acumatica has become the most credible mid-market alternative to NetSuite for commerce, distribution, and project-driven businesses.

For commerce operators, Acumatica's Retail-Commerce edition pairs natively with BigCommerce and Magento (Adobe Commerce), and is commonly used by multi-channel merchants who need real-time inventory, order, and financial sync between storefront and ERP. The Distribution edition handles wholesale, B2B, and complex supplier networks. The Manufacturing edition handles BOMs, production orders, and shop floor. The Construction edition is widely used by trades, builders, and project-based businesses.

Acumatica's general ledger, multi-entity, multi-currency, and project accounting capabilities are robust for the size band, which means it can serve as a credible financial source of truth for merchants in the $5M to $250M annual revenue range.

## Why Vortex IQ tracks Acumatica

Acumatica is a high-leverage connector for Vortex IQ because it sits exactly where the SMB-to-mid-market ICP lives. These are merchants who have outgrown QuickBooks or Xero, are not yet ready for NetSuite or SAP, and need real KPI visibility across storefront, ERP, and supply chain without building a data team.

The strategic positioning is clear. Acumatica customers tend to run lean, multi-channel operations: BigCommerce or Adobe Commerce on the storefront, Acumatica on the back office, a focused paid-media stack, and a customer-service tool. Their reconciliation problems are real but smaller in surface area than enterprise SAP or Oracle estates, which means Vortex IQ can deliver high-impact cards quickly without years of integration work.

Acumatica's API-first design and clear data model make it an unusually clean ERP to read from, which matters for KPI accuracy. Combined with the platform's strong fit for distribution, project, and retail edition customers, the Nerve Centre can surface signals that other tools simply do not have access to: project-accounting milestones, multi-warehouse stock turn, and order-to-cash velocity that ties storefront and ERP timestamps together.

For Ask Viq, the Acumatica connector also expands the assistant's ability to answer mid-market operator questions with the right vocabulary: branches, inventory transactions, BOMs, project tasks, and edition-specific concepts. That linguistic and contextual fluency is part of why the connector earns its place alongside NetSuite, Sage, and the larger ERP set.

## What you can monitor (when KPI cards launch)

When the Acumatica cards ship, the planned coverage spans:

* Order-to-cash velocity across storefront, EDI, and direct sales channels
* Multi-entity and multi-branch revenue consolidation
* Project-accounting signals: milestone billing, project margin, and revenue recognition
* Distribution-edition inventory turns, stock days-on-hand, and warehouse-level stockouts
* Manufacturing-edition production lead time, work-in-progress, and BOM cost drift
* AR aging, collections risk, and B2B customer-level revenue exposure
* Storefront vs Acumatica order and revenue reconciliation
* Gross margin after landed cost, fees, and refunds, by SKU and by channel
* Multi-currency settlement variance for cross-border merchants

## Detailed KPI cards in active development

Acumatica's KPI cards are in active development. The initial set focuses on Retail-Commerce and Distribution editions, given the natural fit with the existing BigCommerce and Adobe Commerce connectors, with Manufacturing, Construction, and Project editions following.

If you run an Acumatica-backed business and want early access, tell us, and we will route you into the design partner cohort.

[Book a demo](https://www.vortexiq.ai/contact-us) or [start a free trial](https://www.vortexiq.ai/signup) to be notified the day Acumatica cards go live.


# Acumatica sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/acumatica/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag Acumatica KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/acumatica) · [Audit Profile](/nerve-centre/kpi-cards/acumatica/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/acumatica/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each Acumatica KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **11** of the 34 Acumatica cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                                                                                                                                           | Direction       | Good | Bad | Unit     |
| ---------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ---- | --- | -------- |
| [AR Aging - 60+ Days](/nerve-centre/kpi-cards/acumatica/ar-aging-60-days)                                                                      | Lower is better | 5    | 15  | %        |
| [AR Aging on Customers with Active Ecom Orders](/nerve-centre/kpi-cards/acumatica/ar-aging-on-customers-with-active-ecom-orders)               | Lower is better | 5    | 15  | Currency |
| [Days Sales Outstanding (DSO)](/nerve-centre/kpi-cards/acumatica/days-sales-outstanding-dso)                                                   | Lower is better | 30   | 60  | Count    |
| [ERP-vs-Ecom Inventory Variance %](/nerve-centre/kpi-cards/acumatica/erp-vs-ecom-inventory-variance)                                           | Lower is better | 1    | 5   | %        |
| [Ecom Customers Absent from Acumatica Customer Master](/nerve-centre/kpi-cards/acumatica/ecom-customers-absent-from-acumatica-customer-master) | Lower is better | 0    | 10  | Count    |
| [Financial Period Close Past Deadline](/nerve-centre/kpi-cards/acumatica/financial-period-close-past-deadline)                                 | Lower is better | 0    | 5   | Count    |
| [Financial Period Close Status](/nerve-centre/kpi-cards/acumatica/financial-period-close-status)                                               | Lower is better | 0    | 5   | Count    |
| [GL Batches Failing to Balance (debit ≠ credit)](/nerve-centre/kpi-cards/acumatica/gl-batches-failing-to-balance-debit-credit)                 | Lower is better | 0    | 5   | Count    |
| [Order-to-Cash Velocity (days)](/nerve-centre/kpi-cards/acumatica/order-to-cash-velocity-days)                                                 | Lower is better | 30   | 60  | Count    |
| [SKUs with Acumatica-vs-Ecom Inventory Drift >5%](/nerve-centre/kpi-cards/acumatica/skus-with-acumatica-vs-ecom-inventory-drift-5)             | Lower is better | 1    | 5   | Count    |
| [Unposted GL Batches](/nerve-centre/kpi-cards/acumatica/unposted-gl-batches)                                                                   | Lower is better | 0    | 50  | Count    |


# Amazon Revenue Share vs Adobe DTC, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/amazon-revenue-share-vs-adobe-dtc

How dependent is the brand on Amazon vs its own Adobe storefront? Concentration risk + early signal of marketplace policy hit. How to read it, why it matte...

**Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> How dependent is the brand on Amazon vs its own Adobe storefront? Concentration risk + early signal of marketplace policy hit.

## At a glance

> Amazon Seller Central revenue divided by Amazon + Adobe DTC combined revenue, expressed as a percentage. Tells you how much of your top-line depends on the marketplace versus your owned storefront. Above 50% is concentration risk, a single Amazon policy change, suspension, or Buy Box loss can wipe out half the business overnight.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | Numerator: Amazon Seller Central revenue (sum of `OrderTotal.Amount` from the Amazon SP-API `Orders` resource) over the 30-day window. Denominator: Amazon revenue + Adobe Commerce `SUM(grand_total)` across all Store Views over the same window. Returned as a percentage of total combined revenue.                                                                                                                                                                                            |
| **API field**                                          | Amazon side: `OrderTotal.Amount` from `GET /orders/v0/orders` (Amazon SP-API). Adobe side: `grand_total` from `GET /rest/V1/orders`.                                                                                                                                                                                                                                                                                                                                                               |
| **VAT / tax treatment**                                | **Mixed.** Amazon `OrderTotal` is the customer-paid total inclusive of any tax Amazon collected on the merchant's behalf (Marketplace Facilitator regions, e.g. UK, EU, US-most states). Adobe `grand_total` is also inclusive of tax. Apples-to-apples in tax-inclusive markets. In tax-exclusive markets (some US states without Marketplace Facilitator, B2B Adobe stores), there's a small bias.                                                                                               |
| **Shipping inclusion**                                 | **Included on both sides.** Amazon `OrderTotal` includes `ShippingPrice`; Adobe `grand_total` includes `shipping_amount`.                                                                                                                                                                                                                                                                                                                                                                          |
| **Discounts**                                          | Already deducted, both sides. Amazon's discounts (Lightning Deals, coupons, Subscribe & Save savings) are already netted in `OrderTotal`.                                                                                                                                                                                                                                                                                                                                                          |
| **Credit Memo refund treatment**                       | **NOT subtracted on either side.** Adobe Commerce `grand_total` is unchanged after a Credit Memo (refund lives separately). Amazon's `OrderTotal` is unchanged after an A-to-Z claim or return refund. Both sides are gross of refunds. To see net-of-refund concentration, divide *Net Amazon Revenue* by *Net Combined Revenue*.                                                                                                                                                                 |
| **`state` machine inclusion**                          | **All Adobe states included** (matches [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)): `new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, `payment_review`. Amazon side counts orders in any non-`Canceled` Amazon order status (Pending, Unshipped, PartiallyShipped, Shipped). The Adobe `pending_payment` quirk means a high-fail Adobe gateway can artificially inflate the Adobe denominator and depress the Amazon share, see FAQs. |
| **`pending_payment` quirk**                            | Adobe Commerce includes `pending_payment` orders in the denominator even though they never collected cash. A store with high gateway-callback failures will have a denominator that's 2-5% bigger than realised cash flow, which understates the Amazon share. For a "realised cash" version, filter Adobe to `state IN (processing, complete, closed)`.                                                                                                                                           |
| **Multi-currency `grand_total` vs `base_grand_total`** | Both sides use display currency without FX. Amazon's per-marketplace orders (Amazon US in USD, Amazon UK in GBP) sum without conversion; Adobe's per-Store-View orders likewise. The combined ratio is approximately FX-neutral if Amazon and Adobe share similar currency mixes. International merchants with very different geo footprints between the two channels should use `base_grand_total` views.                                                                                         |
| **Store View scope (`store_id`)**                      | **All Adobe Store Views summed**, including B2B portals. If your Amazon presence is consumer-only but Adobe includes a large B2B portal, the denominator is consumer + B2B and the Amazon share is artificially low. Filter the Adobe denominator to consumer-only Store Views for a fair retail-vs-marketplace comparison.                                                                                                                                                                        |
| **Time window**                                        | `30D vsP` (rolling 30-day vs the prior 30-day)                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Alert trigger**                                      | `Amazon share >50% (channel-concentration risk)`. The threshold is a strategy signal rather than an outage signal; no `has_threshold` enforcement (alert is informational).                                                                                                                                                                                                                                                                                                                        |
| **Roles**                                              | owner, finance, marketing                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |

## Calculation

```
SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A consumer-electronics brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views, also selling on Amazon US, Amazon UK, and Amazon DE via Seller Central. The 30-day window covers 14 Mar 26 to 12 Apr 26.

| Channel                                      | Revenue (display currency) | Indicative USD  |
| -------------------------------------------- | -------------------------- | --------------- |
| Amazon US                                    | \$312,400                  | \$312,400       |
| Amazon UK                                    | £74,200                    | \~\$92,800      |
| Amazon DE                                    | €58,600                    | \~\$63,200      |
| **Amazon total (numerator)**                 |                            | **\~\$468,400** |
| Adobe `grand_total` US Store View            | \$272,320                  | \$272,320       |
| Adobe `grand_total` UK Store View            | £80,784                    | \~\$101,000     |
| Adobe `grand_total` B2B portal               | \$58,220                   | \$58,220        |
| Adobe `pending_payment` value (across views) | \$12,168                   | \$12,168        |
| **Adobe total (rest of denominator)**        |                            | **\~\$443,708** |
| **Combined denominator (Amazon + Adobe)**    |                            | **\~\$912,100** |
| **This card (Amazon share)**                 |                            | **\~51.4%**     |

The card just crossed the 50% concentration threshold. What this is telling the merchant:

1. **Amazon now drives more revenue than your owned channel.** Above 50% is the strategic warning zone, a single Amazon policy hit (suspension, Buy Box loss, takedown of a hero ASIN, ToS violation) can wipe out a quarter of the business in 24 hours. The card is a strategic-risk indicator, not an outage indicator.
2. **The B2B portal (\$58,220) inflates the Adobe denominator and artificially lowers Amazon share.** Most Amazon-vs-DTC analyses are about consumer business; B2B is a separate motion. **With B2B excluded, Amazon share rises to 54.7%**, the real concentration is worse than the headline.
3. **vs prior 30 days the share moved from 47.2% to 51.4%.** Investigate which side moved: did Adobe DTC drop (a campaign ended, paid-ads softened) or did Amazon grow (a Lightning Deal landed, an ASIN went viral)? Pair with [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) trend and [`amazon_sp.amazon_sp_total_revenue`](/nerve-centre/amazon_sp/amazon_sp_total_revenue).
4. **`pending_payment` orders (\$12,168) inflate the Adobe denominator slightly, understating Amazon share by \~0.7 percentage points.** The "realised cash" Amazon share (excluding `pending_payment`) is \~52.1%.
5. **The European mix is heavier on Amazon than the US mix.** Amazon UK + DE = $156k vs Adobe UK = $101k (ratio 60.7%). Amazon US = $312k vs Adobe US = $272k (ratio 53.4%). The brand is more dependent on Amazon in Europe than in the US, drives a different rebalancing strategy per region.

## Sibling cards merchants should reference together

This is a strategy card, pair with these to drive decisions:

| Card                                                                                                    | Why pair it with Amazon Revenue Share                                                                                                                                  |
| ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                                   | The Adobe denominator. Movement on the share card without movement on this card means Amazon grew; movement on both means both are moving (often opposite directions). |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)                | A `pending_payment` spike inflates the Adobe denominator, suppressing Amazon share. Cross-check before declaring "Amazon is shrinking".                                |
| [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id)                               | Filter to consumer-only Store Views to exclude B2B from the denominator for a fair retail-only comparison.                                                             |
| [Credit Memo Total](/nerve-centre/adobe_commerce/credit_memo_total)                                     | Both sides are gross of refunds. A returns-heavy month doesn't show in the share but does show here.                                                                   |
| [Email Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/email-attributed-revenue-share)            | Sister cross-platform card. Together they tell you "what % is Amazon, what % is owned email, what % is everything else".                                               |
| [`amazon_sp.amazon_sp_total_revenue`](/nerve-centre/amazon_sp/amazon_sp_total_revenue)                  | The Amazon numerator on its own. Movement here without movement on the share card means Adobe DTC is keeping pace.                                                     |
| [`amazon_sp.amazon_sp_buy_box_pct`](/nerve-centre/amazon_sp/amazon_sp_buy_box_pct)                      | The leading indicator of Amazon revenue health. Buy Box loss precedes revenue loss by days.                                                                            |
| [`google_analytics.ga_revenue_by_channel`](/nerve-centre/kpi-cards/google-analytics/revenue-by-channel) | GA4 doesn't see Amazon (it's its own walled garden). Use GA4 only for the Adobe DTC channel mix; this card spans both.                                                 |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

Adobe Commerce doesn't natively know about Amazon, so reconciliation is per-side.

For the Adobe denominator:

> **Reports > Sales > Orders** (or **Reports > Sales** in 2.4.6+). Set the same 30-day window, scope to *All Store Views*, Status filter "All Orders". The Total Revenue column is the Adobe denominator. Cross-check with [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue).

For the Amazon numerator (in Amazon Seller Central, not Adobe Admin):

> **Reports > Business Reports > Sales and Orders by Date** in Seller Central. Set the same 30-day window. The "Ordered Product Sales" column should match the Amazon numerator within \~1% (Amazon's Business Reports include Pending orders; SP-API does too).

Other Adobe Commerce Admin views that *look* relevant but aren't:

* **Marketing > Communications**: email/transactional, not channel-revenue.
* **Catalog > Products** with marketplace flags: shows which SKUs sync to which channel, not channel revenue.
* **Reports > Sales > Coupons**: coupon-revenue, not channel-revenue.
* **Stores > Configuration > Sales**: configuration, not data.
* **Customers > Now Online**: irrelevant.

Adobe Commerce *can* host Amazon-routed orders (via the Amazon Sales Channel module, M2EPro, or Channel Advisor) which would put Amazon orders in the Adobe denominator with a marketplace tag. **If that's your setup, this card double-counts**, the Amazon orders appear in both the numerator (via SP-API) and the denominator (via Adobe). Configure the manifest to exclude marketplace-tagged Adobe orders from the denominator. The default assumes Amazon and Adobe are independent channels.

**Why our number may legitimately differ from a manual Seller Central + Adobe Admin calculation:**

| Reason                                                                                                                                                                                                                             | Direction of divergence                              |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| **Time-zone**. Amazon SP-API uses `PurchaseDate` in UTC. Adobe Commerce Admin uses Store View timezone. The 30-day window endpoints sit at different real-world cutoffs.                                                           | ±1 day's data at the boundary                        |
| **Currency**. Both sides use display currency without FX. The combined ratio is approximately FX-neutral if both channels share similar geo mix; biased otherwise. Material for international merchants.                           | Material for FX-mix-asymmetric merchants             |
| **Store View scope**. Adobe denominator sums all Store Views including B2B. If your Amazon presence is consumer-only, the denominator-includes-B2B inflates and Amazon share is artificially low.                                  | Vortex IQ ratio lower than consumer-only manual calc |
| **`pending_payment` asymmetry**. Adobe denominator includes `pending_payment`; Amazon SP-API's Pending status is included in the numerator (matching). The asymmetry depends on relative `pending_payment` rates between channels. | Usually 0-2% bias                                    |
| **Marketplace-tagged Adobe orders**. If Adobe hosts Amazon-routed orders via a Sales Channel module, they appear in both numerator and denominator. Configure the manifest to exclude.                                             | Material if double-count not configured out          |
| **SP-API rate limits**. Amazon SP-API has strict rate-limits; if the Vortex IQ sync throttled during the most recent run, the latest few hours of Amazon orders may be missing.                                                    | Self-resolves at next sync, typically within 1 hour  |
| **Refund timing**. Both sides are gross of refunds. Amazon's A-to-Z claim refunds are processed up to 90 days after the order; this doesn't affect either side's revenue figure (both are unchanged).                              | No divergence                                        |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

This card is itself a cross-connector view. The honest reads:

| Pair                                                                                                                                                      | Expected relationship                    | What divergence tells you                                                                                                                                                                                         |
| --------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Amazon SP-API revenue + [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) (this card's combined view) vs the merchant's bank deposits | Combined ≥ deposits                      | Combined includes refunded orders, `pending_payment`, and Amazon Pending. Bank deposits are net of all of those. The gap should be stable; growing gap means refunds are growing or `pending_payment` is growing. |
| [`amazon_sp.amazon_sp_total_revenue`](/nerve-centre/amazon_sp/amazon_sp_total_revenue)                                                                    | Should equal the numerator of this card  | If they differ, one connector has a sync issue. Check the most recent sync timestamp on each.                                                                                                                     |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume)                                                                       | Stripe ≤ Adobe denominator               | Stripe sees only the Adobe DTC side, and only the Stripe-paid subset of that. Doesn't reconcile to combined revenue.                                                                                              |
| [`google_analytics.ga_revenue_trend`](/nerve-centre/kpi-cards/google-analytics/revenue-trend)                                                             | GA4 ≈ Adobe revenue × (1 − tracking gap) | GA4 doesn't see Amazon at all. Useful only for sanity-checking the Adobe side.                                                                                                                                    |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same cross-platform concept exists on other commerce connectors. This is **not a reconciliation**; your Adobe Commerce store doesn't have a parallel Shopify or BigCommerce store.

  * [`shopify.shopify_xc_amazon_revenue_share`](/nerve-centre/kpi-cards/shopify/marketplace-revenue-share)
  * [`bigcommerce.bc_xc_amazon_revenue_share`](/nerve-centre/kpi-cards/bigcommerce/amazon-revenue-share-vs-dtc)
</details>

## Known limitations / merchant FAQs

**Why does Amazon Seller Central show a different revenue figure than the numerator on this card?**
Three usual causes: (1) timezone, Seller Central renders in your account's locale, the SP-API uses UTC; (2) you're looking at a different metric in Seller Central, "Ordered Product Sales" matches but "Sales" sometimes excludes shipping/tax, and "Net Sales" subtracts refunds; (3) sync lag, SP-API rate-limits can leave the most recent few hours stale.

**My finance team says Amazon revenue is lower, why?**
Both sides on this card are gross of refunds. Amazon's A-to-Z claims and return-refunds get processed up to 90 days post-order; finance typically uses Amazon's settlement reports which net them out. This card uses SP-API order data which doesn't net them. Pair with [`amazon_sp.amazon_sp_refund_value`](/nerve-centre/amazon_sp/amazon_sp_refund_value) for the offset.

**What's the difference between `state` and `status` and how does it affect this card?**
On the Adobe side: `state` is the lifecycle (8 values); `status` is the configurable label. The denominator sums all states regardless. On the Amazon side: Amazon's `OrderStatus` is fixed (Pending, Unshipped, PartiallyShipped, Shipped, Canceled, Unfulfillable). The numerator includes everything except `Canceled`, matching the spirit of the Adobe-side inclusion of `canceled` (we want orders placed, not realised). This is intentional but worth knowing if you're cross-checking.

**Why does Adobe's `pending_payment` matter to a card about Amazon share?**
Because it inflates the Adobe denominator. A high-fail Adobe gateway can have 5%+ of `grand_total` sitting in `pending_payment` (orders the gateway didn't confirm). That bloats the denominator and depresses the Amazon share artificially. For a "realised cash" view, filter Adobe to `state IN (processing, complete, closed)`.

**What's `grand_total` vs `base_grand_total` and which does this card use?**
`grand_total` is the order's display currency; `base_grand_total` is the store's base currency, FX-converted at order time. This card uses `grand_total` (display currency, mixed without FX) on the Adobe side and `OrderTotal.Amount` (display currency per marketplace) on the Amazon side. The combined ratio is approximately FX-neutral if both channels share similar geo mix; biased otherwise. Multi-currency international merchants should consider per-region card variants.

**My multi-store Adobe Commerce, can I see per-region Amazon share?**
Not on this card directly. Filter both sides per region: connect a per-marketplace Amazon (US, UK, DE) view alongside a per-Store-View Adobe filter. A per-region card variant is on the roadmap.

**Why doesn't Adobe Commerce dashboard show Amazon share?**
Adobe Commerce doesn't natively know Amazon exists. Some merchants use the Amazon Sales Channel module or M2EPro to bring Amazon orders into Adobe with a marketplace tag, that's a configuration, not a default. If your setup does that, this card double-counts; configure the manifest to exclude marketplace-tagged Adobe orders from the denominator.

**My Stripe revenue and Amazon revenue don't match, expected?**
Yes. Stripe is the Adobe DTC payment processor only; Amazon doesn't use Stripe. There's no direct relationship. Stripe sees the Adobe-side cash flow; SP-API sees the Amazon-side. They're parallel, not overlapping.

**Why doesn't Google Analytics show Amazon revenue?**
GA4 only tracks traffic on your Adobe Commerce storefront. Amazon shoppers never touch your site, so GA4 has no view of them. This card is the only place to get the channel-vs-channel revenue mix.

**My Amazon share is below 50%, am I safe?**
The 50% threshold is informational, not a guarantee. Some healthy DTC brands run at 60-70% Amazon and are fine because their margins on Amazon and DTC are roughly equal. Some struggling brands at 30% Amazon are in trouble because their Amazon margin is razor-thin while DTC subsidises. Use this card alongside [`amazon_sp.amazon_sp_buy_box_pct`](/nerve-centre/amazon_sp/amazon_sp_buy_box_pct), per-channel margin analysis, and your category's typical concentration to make a judgement.

**Why does today's number swing so much?**
Daily resolution on a 30-day rolling window is smoothed enough to be stable; the share rarely moves more than 1-2 percentage points day-to-day. If you see >5pp swings between days, one of the connectors is having sync issues. Check the most recent sync timestamps on both Amazon SP and Adobe Commerce in your Vortex IQ workspace settings.

***

### Tracked live in Vortex IQ Nerve Centre

*Amazon Revenue Share vs Adobe DTC* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Adobe Commerce audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/audit

What the Vortex IQ Adobe Commerce health audit checks: Catalog Quality

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adobe-commerce) · [Audit Profile](/nerve-centre/kpi-cards/adobe-commerce/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adobe-commerce/sentiment)**

Audits product catalog completeness and inventory hygiene against the connector's commerce API.

## What this audit checks

### Product completeness

* Missing meta description (SEO)
* Missing product weight / shipping data
* Missing or short product titles
* Zero-priced visible products
* Missing alt text on product images

### Inventory tracking

* Inventory tracking enabled per variant
* Out-of-stock products still visible
* Negative or implausible stock levels

### Schema & structured data

* Product schema markup present
* Breadcrumb structure validity

### Order & customer data hygiene

* Orders stuck in unfulfilled or failed payment state
* Customers with unverified email addresses
* Refund and cancellation rates within expected band


# Average Order Value, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/average-order-value

Average Order Value for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Average Order Value across all orders in the period: `SUM(grand_total) / COUNT(orders)`. AOV on Adobe Commerce typically runs higher than Shopify/BigCommerce equivalents due to the B2B mix; a typical Adobe Commerce merchant sees blended AOV of $150 to $400 vs Shopify's $80 to $150. Movements in AOV reveal product-mix changes, promotional impact, and B2B/B2C segment shifts.

|                                                        |                                                                                                                                                                                                                  |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `AVG(grand_total)` over orders within the period. Each order contributes one observation regardless of line-item count.                                                                                          |
| **API field**                                          | `grand_total` from `GET /rest/V1/orders`.                                                                                                                                                                        |
| **VAT / tax treatment**                                | **Tax-inclusive on B2C; tax-exempt on most B2B** (resale certificates). For a B2B-heavy Adobe Commerce store the blended AOV understates the inclusive-equivalent figure for the B2C portion.                    |
| **Shipping inclusion**                                 | **Included.** `grand_total` adds `shipping_amount`. Stores with sharp regional shipping differences (heavy items, fragile glassware) see non-trivial AOV variance month-on-month from shipping alone.            |
| **Discounts**                                          | **Already deducted.** Post-promotion. A flash-sale period drags AOV down.                                                                                                                                        |
| **Credit Memo refund treatment**                       | **NOT subtracted.** AOV is gross. For net-of-refund AOV, divide [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) net by [Order Count](/nerve-centre/kpi-cards/adobe-commerce/total-orders). |
| **`state` machine inclusion**                          | All states except `canceled`. Includes `pending_payment` (B2B net-30 in particular).                                                                                                                             |
| **`pending_payment` quirk**                            | Included. Adobe Commerce orders sit in `pending_payment` until gateway callback or AP approval; excluding them would make AOV volatile and understate B2B contribution.                                          |
| **Multi-currency `grand_total` vs `base_grand_total`** | Uses `base_grand_total` for cross-currency roll-up. Display can be configured per-currency for merchants who want to see GBP-only and USD-only averages.                                                         |
| **Store View scope (`store_id`)**                      | All Store Views by default. Per-Store-View AOV is recommended on multi-region stores; the consumer-USD AOV typically differs materially from B2B-USD AOV.                                                        |
| **Time window**                                        | `30D vsP` (trailing 30 days vs prior 30 days).                                                                                                                                                                   |
| **Alert trigger**                                      | `drop >10% vsP`.                                                                                                                                                                                                 |
| **Sentiment key**                                      | `aov_trend`                                                                                                                                                                                                      |
| **Roles**                                              | owner, marketing                                                                                                                                                                                                 |

## Calculation

```
AVG(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A specialty kitchenware retailer on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views. Trailing 30-day window ending Monday 4 May 26.

**Blended AOV (all Store Views, all customer types):**

| Period       | Order count | `SUM(base_grand_total)` | AOV       |
| ------------ | ----------- | ----------------------- | --------- |
| Trailing 30D | 6,070       | \$1,230,340             | \$202.69  |
| Prior 30D    | 6,140       | \$1,178,800             | \$191.99  |
| **Delta**    | -1.1%       | +4.4%                   | **+5.6%** |

**Per-segment breakdown:**

| Segment         | Trailing 30D AOV | Prior 30D AOV | Delta |
| --------------- | ---------------- | ------------- | ----- |
| B2B (Companies) | \$642.82         | \$618.40      | +3.9% |
| B2C consumer    | \$68.29          | \$69.90       | -2.3% |

**Per-Store-View breakdown:**

| Store View  | Orders | AOV      |
| ----------- | ------ | -------- |
| US consumer | 2,610  | \$72.40  |
| UK consumer | 2,040  | \$63.10  |
| B2B portal  | 1,420  | \$642.82 |

What this is telling the merchant:

1. **Blended AOV grew 5.6%** but the headline obscures the segment story.
2. **B2B AOV grew 3.9%**: healthy, accounts buying slightly larger baskets.
3. **B2C AOV dropped 2.3%**: smaller consumer baskets. Could be promotional drag, smaller-basket demographic shift, or a shipping-fee change that pushed customers to single-item orders.
4. **The blended AOV is rising despite B2C contracting because B2B order count grew** (412 trailing vs 386 prior, +6.7%); more B2B mix in the average pulls it up.
5. **The composition trap**: a leadership view that watched only blended AOV would conclude "AOV is up, all is well". The segmentation reveals B2C contraction that warrants its own action plan.
6. **Cross-checking [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)**: B2B share rose from 47% to 53%. Confirms the mix shift driving blended AOV.
7. **Cross-checking [Discount %](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue)**: discount% on B2C is up 2.4 pts, pulling AOV down on that segment. A spring sale is running. Once the sale ends, B2C AOV should recover.
8. **Action**: extend the discount monitoring window, set a checkpoint to re-measure B2C AOV in the 30 days after the sale ends. If it doesn't recover, the issue is structural rather than promotional.

The point: AOV is a composite metric. On Adobe Commerce especially, the B2B/B2C and per-Store-View segmentation reveals 2 to 3 distinct stories that the blended figure masks.

## Sibling cards merchants should reference together

AOV is a composite; the value comes from the cards that decompose it.

| Card                                                                                | Why pair it with AOV                                                                                                                 |
| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)               | The numerator. AOV change can be revenue-driven (numerator change) or order-driven (denominator change); both decompositions matter. |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                 | The denominator. Watch for AOV moving inversely to order count, classic mix-shift signature.                                         |
| [B2B AOV vs B2C AOV](/nerve-centre/kpi-cards/adobe-commerce/b2b-aov-vs-b2c-aov)     | The segment split. Adobe Commerce blended AOV is 80% explained by segment mix in most stores.                                        |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)       | The shift in mix that drives blended AOV.                                                                                            |
| [Discount %](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue)            | Discounts pull AOV down. A campaign period sees AOV drop and discount% rise in lockstep.                                             |
| [Customer Segments](/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments) | Per-cohort AOV. New customers vs repeat have different AOV; mix shifts surface here.                                                 |
| [Top Refunded SKUs](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) | If a high-AOV SKU is being refunded heavily, gross AOV looks healthy but net is contracting.                                         |
| [`shopify.aov`](/nerve-centre/kpi-cards/shopify/average-order-value)                | Cross-platform peer for agency benchmark.                                                                                            |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Orders** with the date range set to "Last 30 days". The "Average" column shows AOV for the period. Adobe also displays AOV on the **Dashboard > Lifetime Average Order Value** tile, but that tile is all-time, not 30-day.

For per-Customer-Group AOV (manual computation needed):

> **Reports > Sales > Orders** with Customer Group filter applied (Adobe Commerce 2.4.4+). Sum the totals and divide by the order count.

For per-Store-View:

> Switch the scope selector at the top-left to a single Store View, then **Reports > Sales > Orders**.

**Why our number may legitimately differ from Adobe Admin:**

| Reason                                                                                                                             | Direction of divergence                             |
| ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| **Time-zone**. Admin in Store View timezone; card in UTC. 30-day window boundaries shift.                                          | ±1 day inclusion                                    |
| **Currency**. Card uses `base_grand_total`; Admin uses Store View base currency. Multi-currency stores see FX-related differences. | Material on multi-currency mixes                    |
| **`canceled` exclusion**. Card excludes; Admin Reports > Sales include unless filtered.                                            | Card AOV slightly higher (cancellations skew small) |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin live.                                                                    | Negligible at 30D                                   |

**Internal identity (within Adobe Commerce):**

`adobe_commerce.aov = total_revenue ÷ order_count`

Component cards (these should be self-consistent, if they're not, it's a sampling or rounding issue, not real divergence):

* [`adobe_commerce.total_revenue`](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)
* [`adobe_commerce.order_count`](/nerve-centre/kpi-cards/adobe-commerce/total-orders)

**Cross-connector reconciliation (when both connectors are connected for this merchant):**

These connectors view the same orders/sessions/transactions through different lenses. Numbers should agree within tracking-gap accuracy. Divergence is a data-quality signal worth investigating.

* [`google_analytics.ga_aov`](/nerve-centre/kpi-cards/google-analytics/average-order-value)

**Expected relationship:** GA4 AOV ≈ Adobe AOV × (1 - tracking gap). GA4 typically misses 10 to 25% of orders (ad blockers, consent rejection, tag-fire failure on slow pages). The orders missed by GA4 tend to be a representative sample, so the AOV figure should match within 2 to 5%. Material divergence (>10%) signals one of: (a) GA4 is missing high-AOV B2B orders (B2B portal customers often run private/incognito for security, blocking GA tags), in which case GA4 AOV is biased low; (b) GA4 is double-counting on multi-step checkout (purchase event firing twice), biasing high; (c) currency mismatch: GA4 reports in the property's reporting currency, Adobe in `base_grand_total`.

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  This metric exists with the same definition on other commerce platforms. This is **not** a reconciliation, your Adobe Commerce store doesn't have a parallel store on those platforms to compare against. These references exist purely so an agency running clients across multiple platforms can cross-link the same metric across docs.

  * [`shopify.aov`](/nerve-centre/kpi-cards/shopify/average-order-value)
  * [`bigcommerce.aov`](/nerve-centre/kpi-cards/bigcommerce/average-order-value)
</details>

## Known limitations / merchant FAQs

**Why is my Adobe Commerce AOV so much higher than industry benchmarks for ecommerce?**
Adobe Commerce skews toward complex use cases: B2B, multi-store, custom-attribute-driven catalogues, hospitality and industrial verticals. Industry "ecommerce AOV" benchmarks are dominated by Shopify-class pure DTC consumer brands ($60 to $120 typical). A typical Adobe Commerce store with any B2B mix runs $150 to $400 blended; pure B2B easily $500 to $2,500. Use category-and-edition-matched benchmarks (B2B distribution vs DTC fashion), not generic ecommerce benchmarks.

**Adobe Commerce vs Magento Open Source: any AOV difference?**
None at the calculation level; both editions use `grand_total` identically. The merchant-mix difference matters: Adobe Commerce paid edition is overwhelmingly used by larger merchants (and B2B-heavy merchants), so the average Adobe Commerce installation has higher AOV than the average Open Source installation. This is a customer-base effect, not an edition difference.

**My multi-store AOV is misleading because of currency mixing, what should I do?**
The card defaults to `base_grand_total` (FX-converted at order time) for cross-currency rollup. For per-currency views, configure per-Store-View variants. Don't rely on `grand_total` for multi-currency comparison; FX swings from order time to display time make the figure unreliable.

**My B2B AOV is much higher than B2C, will the blended AOV always trend with B2B mix?**
Yes. Blended AOV is a weighted average; the higher-AOV segment (B2B) has outsized influence. A 5pt mix shift toward B2B can move blended AOV by 30%+ even if neither segment's own AOV changed. The correct interpretation: blended AOV is a mix-mix indicator, not a quality-of-customer indicator. For quality, use per-segment AOV from [B2B AOV vs B2C AOV](/nerve-centre/kpi-cards/adobe-commerce/b2b-aov-vs-b2c-aov).

**Why include `pending_payment` orders in AOV?**
They are genuine pipeline; B2B net-30 specifically. Excluding them would understate AOV (since net-30 orders skew large) and create false volatility (when a batch of pending orders flips to processing, AOV would jump). Including them gives a stable cash-pipeline view.

**Why is AOV gross of refunds rather than net?**
Two reasons. First, refunds happen days to weeks after the order, so net-of-refund AOV is always a backward-looking moving target. Second, the act of refunding is a separate operational signal tracked in [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate); folding it into AOV obscures both signals. For a net view, divide net Total Revenue by Order Count manually.

**A flash sale ran for 3 days, AOV dropped 8%, is that a problem?**
Probably not. Promotional AOV drag is expected behaviour: discounts pull `grand_total` down by definition. The diagnostic question is whether the volume lift compensated. Cross-check [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders): if order count rose more than AOV fell, total revenue is up. Cross-check [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) directly. If revenue is up despite AOV falling, the campaign is working.

**Why does AOV rise on weekends but Total Revenue falls?**
Common pattern on B2B-heavy stores. Weekend orders are mostly consumer (smaller AOV would suggest revenue should drop) but B2B accounts who DO order on weekends tend to be operations-team-driven emergency orders (high AOV). The mix shift toward fewer, larger orders pushes the average up while the volume push down on revenue. The pattern is healthy mix variation, not a problem.

**My multi-store Adobe Commerce, AOV varies 5x across regions, normal?**
Yes. Region-level AOV differences reflect (a) tax-inclusive pricing vs exclusive (UK +20% VAT, US varies), (b) shipping fee structures, (c) regional product mix (the UK store may stock lower-priced lines), (d) currency-strength effects. A 5x variance suggests US is mostly B2B and UK is mostly consumer (or vice versa); check Store View routing and segment classification.

**Should I optimise for AOV or for Total Revenue?**
Total Revenue. AOV is a means, not an end. Pushing AOV by raising minimum-order-value thresholds reduces volume; the net revenue impact is what matters. The exception: when AOV is dropping and volume is flat (the bad mix-shift case), the AOV signal is the indicator that something needs fixing.

***

### Tracked live in Vortex IQ Nerve Centre

*Average Order Value* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# B2B AOV vs B2C AOV, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/b2b-aov-vs-b2c-aov

B2B AOV vs B2C AOV for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Compares the trailing 30-day Average Order Value of B2B accounts against B2C consumers, expressed both as the per-segment AOV and the delta. Adobe Commerce merchants typically see B2B AOV at 4 to 12x B2C; a contracting delta is an early warning that B2B accounts are shifting volume to other suppliers, downgrading product-mix, or splitting purchases into smaller POs to game line-of-credit limits.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                         |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `AVG(grand_total)` partitioned by customer segment. B2B segment: orders where `extension_attributes.company_attributes.company_id IS NOT NULL` (Adobe Commerce B2B module) OR `customer_group_id` is a B2B-tagged group. B2C segment: everyone else. The card surfaces three numbers: B2B AOV, B2C AOV, and the multiplier (B2B / B2C).                                                                                 |
| **API field**                                          | `grand_total`, `customer_group_id`, and `extension_attributes.company_attributes.company_id` from `GET /rest/V1/orders`. Customer group classification from `GET /rest/V1/customerGroups`.                                                                                                                                                                                                                              |
| **VAT / tax treatment**                                | **Tax-inclusive on consumer (B2C); typically tax-exclusive on B2B** because most B2B orders are tax-exempt at the resale-certificate level. This creates a comparison hazard: B2C `grand_total` includes 20% VAT (UK) or US sales tax, B2B does not. The card uses raw `grand_total` for both, surfacing the inclusive-vs-exclusive distinction in the FAQ. For pure mix comparison, normalise to `subtotal` (pre-tax). |
| **Shipping inclusion**                                 | Included on both. B2B ships freight (LTL/parcel), often at higher absolute cost; included `shipping_amount` somewhat narrows the AOV gap.                                                                                                                                                                                                                                                                               |
| **Discounts**                                          | Already deducted. B2B accounts often have negotiated tier pricing applied as `customer_group_price` or `special_price`; `grand_total` is post-tier.                                                                                                                                                                                                                                                                     |
| **Credit Memo refund treatment**                       | NOT subtracted. Gross AOV. B2B refund rates are typically 1 to 3% and stable, so the un-netted view is rarely misleading.                                                                                                                                                                                                                                                                                               |
| **`state` machine inclusion**                          | All states except `canceled`. `pending_payment` is included on both segments because B2B net-30 orders intentionally sit in pending\_payment until AP processes the invoice. Excluding them would distort the B2B figure heavily.                                                                                                                                                                                       |
| **`pending_payment` quirk**                            | Included for both segments (see above). For B2B specifically, an account whose orders accumulate in `pending_payment` may have a broken AP integration; check [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) filtered to B2B for stuck POs.                                                                                                                                   |
| **Multi-currency `grand_total` vs `base_grand_total`** | Uses `base_grand_total` so multi-currency stores roll up cleanly. The display alongside per-currency breakdown is also exposed for merchants who want to see USD-only and GBP-only AOV.                                                                                                                                                                                                                                 |
| **Store View scope (`store_id`)**                      | All Store Views by default. For merchants with a dedicated B2B Store View and separate consumer Store Views, the segment classification by Store View is more reliable than `customer_group_id`. Configure the manifest to use Store View routing if your B2B portal is its own Store View.                                                                                                                             |
| **Time window**                                        | `30D vsP` (trailing 30 days vs prior 30 days for delta computation).                                                                                                                                                                                                                                                                                                                                                    |
| **Alert trigger**                                      | `B2B AOV drop >15% vsP`. The threshold is asymmetric: B2B AOV rising is a feature, not a problem; we only alert on contraction.                                                                                                                                                                                                                                                                                         |
| **Sentiment key**                                      | `aov_trend`                                                                                                                                                                                                                                                                                                                                                                                                             |
| **Roles**                                              | owner, finance, marketing                                                                                                                                                                                                                                                                                                                                                                                               |

## Calculation

```
AVG(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A janitorial-supply distributor on Adobe Commerce 2.4.6 with the B2B Companies module enabled. Mixed B2B (180 active Companies) and B2C (consumer side, \~3,400 active customers in last 12 months). Snapshot taken Monday 4 May 26.

**30-day AOV by segment:**

| Segment          | Orders (last 30D) | Total `base_grand_total` | AOV      | Multiplier vs B2C |
| ---------------- | ----------------- | ------------------------ | -------- | ----------------- |
| B2B (Companies)  | 1,420             | \$912,800                | \$642.82 | 9.4x              |
| B2C (consumer)   | 4,650             | \$317,540                | \$68.29  | 1.0x (baseline)   |
| **All segments** | 6,070             | \$1,230,340              | \$202.69 | n/a               |

**Prior 30-day AOV (comparison period):**

| Segment | Orders | Total `base_grand_total` | AOV      |
| ------- | ------ | ------------------------ | -------- |
| B2B     | 1,380  | \$1,062,600              | \$770.00 |
| B2C     | 4,710  | \$322,100                | \$68.39  |

**Delta:**

| Segment | Current AOV | Prior AOV | Change     |
| ------- | ----------- | --------- | ---------- |
| B2B     | \$642.82    | \$770.00  | **-16.5%** |
| B2C     | \$68.29     | \$68.39   | -0.1%      |

**The alert fires** because B2B AOV dropped 16.5%, exceeding the 15% threshold. B2C is stable so the issue is B2B-specific.

What the investigation reveals:

1. **B2B order volume is up slightly** (1,420 vs 1,380, +2.9%). Total B2B revenue is down 14.1% ($912k vs $1,062k). Smaller orders, slightly more of them.
2. **Splitting B2B by Company size cohort** (top 20% LTV vs middle 60% vs bottom 20%):
   * Top-20% Companies: AOV $1,180 vs prior $1,210, -2.5%. Within range.
   * Middle-60% Companies: AOV $480 vs prior $560, -14.3%. Material.
   * Bottom-20% Companies: AOV $190 vs prior $310, **-38.7%**. Severe.
3. **The signal**: small and mid-tier B2B accounts are placing smaller orders. The pattern is classic credit-tightening: when an AP department starts splitting POs to stay under approval thresholds, AOV contracts even though order count is steady or higher.
4. **Cross-checking [B2B Accounts Gone Quiet](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet)**: silence count is also up, 8 mid-tier Companies are flagged this week vs typical 2 to 3. Some accounts are smaller-and-more-frequent; some are vanishing.
5. **Most likely cause**: a category-wide credit tightening (merchants in this distributor's customer base are responding to their own cash pressure by reducing purchase quantities). This is macroeconomic rather than operational; the action is on the merchant's side (reach out to mid-tier accounts, offer longer payment terms in exchange for committed volumes).
6. **Less likely but worth ruling out**: a competitor running a price campaign on the merchant's top SKUs. Cross-check [Top Refunded SKUs](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) for product-quality issues; cross-check pricing against direct competitors via manual review.
7. **Action**: Sales team contacts the bottom-20% B2B Companies to discuss. Three of the affected accounts will say "AP cut PO sizes by 30%, can you help with terms?". Two will say "we shifted some volume to a competitor, your prices on category X are no longer best". Both responses are actionable.

The point of this card: a 16% B2B AOV contraction would be invisible in [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) if B2C revenue happens to be growing concurrently. The segmentation isolates the signal.

## Sibling cards merchants should reference together

B2B AOV is most informative when paired with cohort and silence cards.

| Card                                                                                      | Why pair it with B2B AOV vs B2C AOV                                                                                                  |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)             | The denominator. AOV change matters more when B2B is a high revenue share.                                                           |
| [B2B Accounts Gone Quiet](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet) | Sister card. Smaller orders + more silenced accounts together signal a category-wide credit issue.                                   |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                         | The blended figure that this card decomposes. Stable blended AOV with diverging segments is invisible without this card.             |
| [Order Frequency](/nerve-centre/kpi-cards/adobe-commerce/customer-order-frequency)        | If B2B AOV is shrinking but order frequency is rising, accounts are splitting POs (a signal in itself).                              |
| [Customer Segments](/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments)       | Segment-level revenue distribution. AOV is one dimension; this card adds count and revenue contribution.                             |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                     | The aggregate consequence. A 16% B2B AOV drop on a B2B-heavy book bends the revenue curve within 4 to 8 weeks.                       |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)       | B2B repeat rate is normally near 100%; if it dips alongside AOV contraction, accounts are not just buying less but buying elsewhere. |
| [`shopify.shopify_b2b_aov_delta`](/nerve-centre/shopify/shopify_b2b_aov_delta)            | Cross-platform peer for agencies.                                                                                                    |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

For B2B-specific (Adobe Commerce paid edition with Companies module enabled):

> **Customers > Companies** lists all Company entities. Click any Company > Orders tab to see per-account order history. Adobe does not natively compute AOV per Company; you can export the orders to CSV and average in a spreadsheet.

For Customer Group routing (works on both Adobe Commerce and Magento Open Source):

> **Customers > Customer Groups** to define the B2B group(s). **Customers > All Customers** filtered by group, then click any customer > Orders tab. Same manual averaging required.

For aggregate sales:

> **Reports > Sales > Orders** can be filtered by Customer Group via the Filters drop-down on Adobe Commerce 2.4.4+. The "Items Ordered" and "Total" columns let you compute a rough AOV per group manually.

Other Adobe Commerce Admin views that look relevant but are not:

* **Reports > Customers > Customers by Orders Total**: lifetime totals, not 30-day AOV.
* **Reports > Customers > Customers by Number of Orders**: count, not value.
* **Sales > Orders > Filter by Group**: per-order list, not aggregated.

**Why our number may legitimately differ from a manual Admin computation:**

| Reason                                                                                                                                                                                                                | Direction of divergence                                               |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **Time-zone**. Admin in Store View timezone, card runs UTC. The 30-day window boundaries shift slightly.                                                                                                              | ±1 day inclusion/exclusion                                            |
| **Currency**. Admin sums in `base_currency` per Store View. The card uses `base_grand_total` rolled up. Multi-currency stores see slight differences.                                                                 | Material on multi-currency mixes                                      |
| **`canceled` exclusion**. Card excludes; Admin Reports > Sales includes by default unless filtered.                                                                                                                   | Card AOV slightly higher (cancellations are typically smaller orders) |
| **B2B classification**. Card uses `extension_attributes.company_attributes.company_id` OR `customer_group_id`. Manual classification by Group only would miss customers attached to a Company but not in a B2B Group. | Card shows more B2B orders                                            |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin is live.                                                                                                                                                    | Negligible at 30D window                                              |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                                                      | Expected relationship                                            | What divergence tells you                                                                                      |
| --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume) on B2B-tagged charges | Stripe should match Adobe B2B revenue for Stripe-paid B2B orders | Material gap means many B2B orders are paid via net-30 invoice (not Stripe). Normal.                           |
| ERP / accounting system per-Company AOV                                                                   | Should match within sync lag                                     | Divergence usually means manual orders entered in ERP but not Adobe (a process gap, not a card bug).           |
| [`google_analytics.ga_revenue_by_segment`](/nerve-centre/google_analytics/ga_revenue_by_segment)          | GA4 has no native B2B/B2C dimension; would need custom dimension | If a custom dimension exists, GA4 will undercount by 10-25% (tracking gap) but the segment ratio should match. |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same B2B-vs-consumer AOV concept exists on Shopify Plus B2B and BigCommerce B2B Edition.

  * [`shopify.shopify_b2b_aov_delta`](/nerve-centre/shopify/shopify_b2b_aov_delta)
  * [`bigcommerce.bc_b2b_aov_delta`](/nerve-centre/bigcommerce/bc_b2b_aov_delta)
</details>

## Known limitations / merchant FAQs

**Why is B2B AOV so much higher than B2C, is that real?**
Yes, and it varies by category. Wholesale distribution typically sees 8 to 15x; manufacturing 5 to 10x; specialty retail 3 to 6x. The drivers: B2B orders are case-pack or pallet quantities, not single units; B2B accounts often consolidate weekly into one PO rather than ordering as needed; B2B pricing tiers grant volume discounts that incentivise larger baskets. For an Adobe Commerce merchant the multiplier is a useful sanity check on B2B health; a multiplier shrinking month-on-month is a warning even if absolute B2B AOV looks acceptable.

**Adobe Commerce vs Magento Open Source: does this card work on the free edition?**
Partially. The Adobe Commerce paid edition's B2B Companies module gives explicit Company-to-Customer mapping which is the cleanest classification source. Magento Open Source merchants must rely on Customer Groups; you must define a "Wholesale" or "B2B" group and assign customers to it manually (or via API). The card supports both; configure the manifest to point at your B2B group(s) on Open Source.

**My B2C is tax-inclusive but B2B is tax-exempt, the AOV comparison is biased, what should I do?**
You're right that the raw `grand_total` comparison overstates B2C relative to B2B in the UK/EU (where consumer tax is included) and on tax-paying B2C in US states. For pure mix comparison, configure the card to use `subtotal` (pre-tax). The card defaults to `grand_total` because most merchants want to compare what's actually in the bank; for analytical purity, switch to `subtotal`. The FAQ in the [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value) card discusses the tax treatment in more detail.

**Why include `pending_payment` orders in the B2B figure?**
B2B net-30 orders typically sit in `pending_payment` until the customer's AP department processes the invoice. Excluding them would cause the B2B AOV to be wildly volatile (only "captured" orders would count, missing the bulk of B2B activity). The card includes them, which represents the genuine sales pipeline. If your installation has many `pending_payment` orders that never resolve (broken AP integration), check [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) filtered to B2B Companies.

**My multi-store Adobe Commerce, B2B is on a separate Store View, can I filter by it?**
Yes, configure the manifest to use Store View routing. If your B2B portal Store View is identifiable (typical setup: `b2b_uk`, `b2b_us` Store Views), filter `store_id` rather than relying on `customer_group_id`. Store View routing is more reliable when multiple Customer Groups are involved (e.g. tiered B2B pricing groups: Bronze, Silver, Gold) all mapped to the B2B portal.

**Why does the alert only fire on contraction, not expansion?**
B2B AOV expansion means accounts are buying more, a positive signal that doesn't need an alarm. Contraction is the warning signal. If you specifically want to monitor expansion (e.g. for cross-sell program success measurement), configure a positive-direction variant in the manifest.

**The card shows a 9.4x multiplier, what's a normal range?**
Highly category-dependent. Janitorial supply, foodservice, and packaging distributors typically see 8 to 12x. Industrial manufacturing 5 to 8x. Specialty B2B (premium fashion wholesale, luxury hospitality supply) 3 to 5x. A multiplier well outside category norms suggests either misclassification (consumer customers tagged as B2B, or vice versa) or an unusual business model. Compare to peers via VortexIQ benchmark data if uncertain.

**How does this card handle a customer whose first order was retail but who later registered as a B2B Company?**
The card uses the order-time classification: each order is bucketed by the customer's segment at the time of order placement. A customer who upgraded from B2C to B2B mid-quarter has their pre-upgrade orders in B2C and post-upgrade in B2B. This is correct; counting all-time-by-current-status would distort retroactive segment averages.

**My B2B AOV jumped 30% suddenly, is that a problem?**
Probably not but worth investigating. Likely benign causes: a single very large PO (look for one outlier order in the period), a new B2B contract win (check whether a new high-value Company entity appeared in the period), an inflation pass-through (you raised prices and B2B accepted). Rare problem causes: a misclassified consumer order (a B2C customer accidentally placed an order through a B2B portal). Cross-check with order count; if order count is steady but AOV is up, average is driving; if order count fell and AOV rose, only large orders survived (a different signal: small-account churn).

**Why doesn't B2C AOV move much in the example?**
Consumer AOV is heavily anchored by category and product mix; sudden moves typically reflect product-line changes, promotional campaigns, or seasonality. The B2B contraction in the worked example was a credit-availability shift on the buyer side, not a merchant-side change, hence B2C is unaffected. The point of the segmentation is exactly this: signals localised to one segment are invisible in the blended AOV.

***

### Tracked live in Vortex IQ Nerve Centre

*B2B AOV vs B2C AOV* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Cancellation Rate, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate

Cancellation Rate for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Percentage of orders that ended in `state = canceled` rather than progressing to fulfillment. Pre-shipment money-back. On Adobe Commerce, cancellations capture two distinct flows: customer-initiated cancels (changed mind, found cheaper elsewhere) and merchant-initiated cancels (fraud detection, OOS at picking, payment failed authorisation). Both end in the same state but tell different stories.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **What it counts**                                     | `COUNT(orders where state = canceled) / COUNT(all orders)` over the period. The numerator includes voluntary customer cancels via the storefront, ops-initiated cancels via Admin > Sales > Orders > Cancel, and gateway-driven cancels (a `pending_payment` order that timed out or was declined moves to `canceled`).                                                                                                                          |
| **API field**                                          | `state` from `GET /rest/V1/orders`; filter `state = "canceled"`.                                                                                                                                                                                                                                                                                                                                                                                 |
| **VAT / tax treatment**                                | Count-based ratio; tax doesn't bias it. Companion value-at-risk uses `grand_total` of cancelled orders (tax-inclusive on B2C, often exempt on B2B).                                                                                                                                                                                                                                                                                              |
| **Shipping inclusion**                                 | Count-based; n/a for the ratio.                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Discounts**                                          | Count-based; n/a for the ratio.                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Credit Memo refund treatment**                       | This card tracks `state = canceled` (pre-shipment), NOT Credit Memos (post-shipment refunds). Cancellations and Credit Memos are two distinct money-back surfaces; merchants who watch only one miss the other.                                                                                                                                                                                                                                  |
| **`state` machine inclusion**                          | Numerator: only `canceled`. Denominator: all states (so the ratio is "cancellations as % of all orders").                                                                                                                                                                                                                                                                                                                                        |
| **`pending_payment` quirk**                            | A `pending_payment` order that times out (Adobe Commerce default: 24h, configurable in Stores > Configuration > Sales > Sales) auto-transitions to `canceled`. Included. If your gateway is silently failing callbacks, cancellation rate spikes not because customers are cancelling but because Adobe is auto-cancelling pending orders. Cross-check [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown). |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a for the count ratio. The companion value-at-risk uses `base_grand_total`.                                                                                                                                                                                                                                                                                                                                                                    |
| **Store View scope (`store_id`)**                      | All Store Views by default. Per-Store-View variants useful because B2B cancellation is typically near zero while B2C cancellation is 1 to 3%; the blended view masks segment differences.                                                                                                                                                                                                                                                        |
| **Time window**                                        | `30D vsP`.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Alert trigger**                                      | `>3%`. Healthy DTC stores baseline at 0.5 to 2%; B2B near 0%. >3% is meaningful regardless of segment mix.                                                                                                                                                                                                                                                                                                                                       |
| **Sentiment key**                                      | `cancellation_rate`                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Roles**                                              | owner, operations                                                                                                                                                                                                                                                                                                                                                                                                                                |

## Calculation

```
COUNT(state=canceled) / COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A specialty footwear brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views. Trailing 30-day window ending Monday 4 May 26.

**Cancellation rate by Store View:**

| Store View  | Total orders | Cancelled | Rate     |
| ----------- | ------------ | --------- | -------- |
| US consumer | 2,610        | 86        | 3.3%     |
| UK consumer | 2,040        | 41        | 2.0%     |
| B2B portal  | 1,420        | 4         | 0.3%     |
| **Blended** | **6,070**    | **131**   | **2.2%** |

**Prior 30-day blended rate:** 1.4% (84 of 6,140).

**The alert fires** because blended rate is 2.2% (within 3% threshold technically, but the 30-day vs prior shows 1.4% to 2.2% which is a 57% relative increase). Worth investigating.

**Drilldown of the 86 US cancellations:**

| Cause (per Adobe order notes)                 | Count | % of cancellations |
| --------------------------------------------- | ----- | ------------------ |
| Customer-initiated (cancelled via storefront) | 12    | 14%                |
| Ops-initiated (manual cancel, fraud)          | 8     | 9%                 |
| Auto-canceled from `pending_payment` timeout  | 51    | 59%                |
| Ops-initiated (OOS at picking)                | 9     | 11%                |
| Other / unclear                               | 6     | 7%                 |

What the investigation reveals:

1. **The cancellation increase is dominated by `pending_payment` timeouts** (51 of 86, 59%). Customers reached order-create but the gateway never callback-confirmed; after 24 hours Adobe auto-canceled.
2. **Cross-checking [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) for the period**: `pending_payment` count is up 65% over the trailing 30 days. This is the smoking gun.
3. **Pulling Stripe webhook logs for the period**: 47 failed webhook deliveries to the merchant's Adobe endpoint over the last 30 days, mostly clustered in the last 14 days. The merchant migrated to a new firewall on day 16 of the period; the firewall is occasionally rate-limiting Stripe webhook IPs.
4. **The fix**: whitelist Stripe webhook source IP ranges in the firewall, replay the failed webhooks. Within hours, the `pending_payment` backlog drains, the canceled orders unfortunately stay canceled (Adobe doesn't reverse `canceled` state), but new orders flow normally.
5. **The cost**: 51 cancelled orders × \~$72 average US AOV = ~$3,670 of unrecovered revenue. Some customers will retry and place a new order; many will not.
6. **The OOS-at-picking cancellations (9)** are a separate operational issue worth tracking: the `salable_qty` was zero by the time the picker reached the bin, meaning either the [Out-of-Stock Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/out-of-stock-spike-alert) is not catching the supplier-stall pattern fast enough or the buffer between cart-reservation and picking is too small.
7. **The B2B rate of 0.3%** is normal; B2B accounts almost never cancel.

The point of this card: cancellation rate alone is ambiguous (genuine cancels vs gateway timeouts vs ops actions). Pairing with order-state distribution and gateway data distinguishes the cause within minutes.

## Sibling cards merchants should reference together

| Card                                                                                      | Why pair it with Cancellation Rate                                                                         |
| ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)  | Distinguishes gateway-timeout cancels from genuine cancels. The most useful diagnostic pair.               |
| [Cancelled Over Time](/nerve-centre/kpi-cards/adobe-commerce/cancelled-orders-over-time)  | Trend view. Spikes correlate to gateway issues, fraud campaigns, or system migrations.                     |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                         | The post-shipment money-back. Cancellations + Credit Memos = full money-back surface.                      |
| [Refund-Rate Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/refund-rate-spike-alert) | If refunds spike alongside cancellations, both are post-purchase pain; if only one moves, different cause. |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                     | Revenue is gross; cancellation rate is the proxy for unrealised revenue.                                   |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                       | The denominator.                                                                                           |
| [`stripe.stripe_payment_decline_rate`](/nerve-centre/stripe/stripe_payment_decline_rate)  | Decline rate spike causes a `pending_payment` timeout cascade.                                             |
| [`shopify.cancellation_rate`](/nerve-centre/kpi-cards/shopify/cancellation-rate)          | Cross-platform peer.                                                                                       |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Sales > Orders** filtered by Status = "Canceled" gives the cancelled-order list. Sort by Purchase Date for the time view.

> **Reports > Sales > Orders** with the date range set; Adobe Admin's report shows totals per status, you compute the ratio manually.

For per-cause segmentation:

> **Sales > Orders > \[Order ID] > Comments** shows the cancellation note (typically auto-generated for gateway-timeout cancels: "Order canceled because of payment timeout"). Manual cancels include the operator's user comment.

Other Adobe Commerce Admin views that look relevant but are not:

* **Reports > Sales > Tax**: tax aggregations.
* **Reports > Sales > Coupons**: coupon usage.
* **Sales > Invoices**: invoiced orders only; cancelled orders are not invoiced.

**Why our number may legitimately differ from the Admin status filter:**

| Reason                                                                                                                                                                                                                | Direction of divergence                   |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
| **Time-zone**. Admin in Store View timezone; card UTC. Window boundaries shift.                                                                                                                                       | ±1 day inclusion                          |
| **`status` vs `state`**. Admin's filter shows by `status`; this card uses `state`. The two usually agree (default workflow maps `state = canceled` to `status = canceled`) but custom status renames can desync them. | Material if custom status workflow exists |
| **Manual ops actions**. Operator cancels via Admin > Sales > Orders > Cancel are immediate; gateway-timeout auto-cancels can take 24+ hours. The card sees the timestamp of state transition.                         | Negligible at 30D                         |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin live.                                                                                                                                                       | Negligible                                |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                                     | Expected relationship                                                         | What divergence tells you                                                                       |
| ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| [`stripe.stripe_payment_decline_rate`](/nerve-centre/stripe/stripe_payment_decline_rate) | Stripe decline spike causes `pending_payment` timeout cancellations 24h later | Strong leading indicator.                                                                       |
| [`stripe.stripe_chargebacks`](/nerve-centre/stripe/stripe_chargebacks)                   | Cancelled orders don't generate chargebacks (no money was captured)           | Chargebacks are post-shipment; cancellations are pre-shipment. The two metrics are independent. |
| Customer service ticket volume (Zendesk / Intercom)                                      | Customer-initiated cancels usually generate a ticket                          | Cancellation rate up + ticket volume flat = automated/timeout cancels, not customer choice.     |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.cancellation_rate`](/nerve-centre/kpi-cards/shopify/cancellation-rate)
  * [`bigcommerce.cancellation_rate`](/nerve-centre/kpi-cards/bigcommerce/cancellation-rate)
</details>

## Known limitations / merchant FAQs

**My cancellation rate spiked but my customer-service inbox is quiet, what happened?**
Customers didn't cancel; Adobe auto-cancelled `pending_payment` orders that timed out. Look at order notes: "Order canceled because of payment timeout" or similar means gateway callback failed. Cross-check Stripe/PayPal webhook logs for failed deliveries. Fix: replay webhooks, address whatever broke the gateway-to-Adobe path.

**What's the difference between `state = canceled` and a Credit Memo?**
Cancellation is pre-shipment, no money captured. Credit Memo is post-shipment refund of captured payment. They are distinct events; cancellations are tracked here, Credit Memos in [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate). Together they cover the full money-back surface area.

**Adobe Commerce vs Magento Open Source: difference?**
None at the calculation layer; both editions use the same `state` machine. Adobe Commerce's B2B Companies module adds the concept of company-level approval workflows, where an order can sit in `pending` (awaiting approval) before reaching `processing`. If approval fails or expires, the order moves to `canceled`. This is an Adobe-only cancellation cause.

**Why include `pending_payment` timeouts in cancellation rate?**
Because the customer-facing experience is identical: an order that doesn't ship is a cancelled order, regardless of why. Excluding timeouts would understate the customer's perceived cancellation experience. The companion drilldown (cancellation cause breakdown) lets you separate genuine cancels from timeouts when you need to.

**My multi-store Adobe Commerce, B2B has 0% cancellation, normal?**
Yes. B2B accounts almost never cancel: orders are budgeted, approved, and contractually committed. The rare exceptions are credit-check failures or AP rejection, which are typically \<1%. If your B2B portal is showing >2% cancellation rate, investigate: usually it's gateway issues on B2B-specific payment routes (some B2B portals route to a separate payment service or use net-30 invoice issuance).

**Why is my cancellation rate higher than industry benchmarks of 0.5%?**
Adobe Commerce stores often run higher because (a) `pending_payment` timeouts are included (Shopify, BigCommerce handle gateway-failed orders differently in their data models), (b) ops-initiated cancels for OOS-at-picking are routine on multi-source MSI installations, (c) B2B installations may show 0% but blended consumer-only stores see 1-3%. Use Adobe-Commerce-matched peer benchmarks, not generic ecommerce.

**A flash sale ran and cancellation rate spiked, why?**
Flash sales drive impulse orders, some of which are reconsidered and cancelled before shipment. A 1-2 pt spike during a sale is normal; >5 pt spike suggests the sale terms were unclear (customers didn't realise the discount didn't apply, regretted, cancelled).

**A fraud-detection rule auto-cancels suspicious orders, are those counted?**
Yes. Any cancel-state order is counted, regardless of cause. If your fraud rules cancel 3% of orders, that 3% will appear here. Configure the manifest to filter on order comment or fraud-flag if you want to exclude rule-based cancels from the customer-facing rate.

**Why does the rate look different between Adobe Admin and this card?**
Most common cause: Admin's filter is by `status`, this card uses `state`. If you have custom statuses (e.g. you renamed "canceled" to "Cancelled - Customer Request"), the Admin filter shows that status; this card sees the underlying `state`. Both are correct; they answer slightly different questions.

***

### Tracked live in Vortex IQ Nerve Centre

*Cancellation Rate* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Cart-Abandonment Spike Alert, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/cart-abandonment-spike-alert

Order-count divided by quote/cart-create count, fires when a checkout regression silently kills conversion. How to read it, why it matters, and how to act...

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> Order-count divided by quote/cart-create count, fires when a checkout regression silently kills conversion.

## At a glance

> Real-time canary that compares completed-order count against quote-create count to derive a checkout abandonment rate. Fires when the rate exceeds 2 standard deviations above the 30-day baseline. Designed to catch silent checkout regressions: a broken JavaScript event, a payment-method dropdown that no longer renders, a tax-calculation service timing out, an Adobe Commerce 2.4.x patch that changed the address-validation flow.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `1 - (COUNT(orders) / COUNT(quotes_with_at_least_one_item))` over a rolling hour, compared against the 30-day mean and standard deviation of the same ratio at the same hour-of-week. Quote count comes from the `quote` table where `items_count > 0` and `created_at` falls in the window.                                                                                                                                                   |
| **API field**                                          | Quote count via `GET /rest/V1/carts/search` (or direct `quote` table read for performance); order count via `GET /rest/V1/orders`. The card joins on `quote_id` to identify converted vs abandoned quotes.                                                                                                                                                                                                                                     |
| **VAT / tax treatment**                                | n/a for the ratio itself (it is a count-based ratio, not a value). The "lost-revenue" companion estimate uses average `grand_total` per converted quote, which is tax-inclusive.                                                                                                                                                                                                                                                               |
| **Shipping inclusion**                                 | n/a for the abandonment ratio. Shipping configuration changes are a frequent root cause of abandonment spikes (a new freight rule made shipping eye-watering on a popular SKU), so the FAQs cover this.                                                                                                                                                                                                                                        |
| **Discounts**                                          | n/a for the ratio. A discount-code field that broke (returns "Invalid coupon" on every legitimate code) is a classic spike trigger.                                                                                                                                                                                                                                                                                                            |
| **Credit Memo refund treatment**                       | n/a, this card is conversion-side.                                                                                                                                                                                                                                                                                                                                                                                                             |
| **`state` machine inclusion**                          | Order numerator includes orders in any `state` except `canceled`. Reasoning: a `pending_payment` order still represents the customer reaching checkout completion intent; only `canceled` truly didn't convert. The card's intent is funnel-stage detection, not cash-in-bank.                                                                                                                                                                 |
| **`pending_payment` quirk**                            | Included in the numerator. If your gateway is dropping callbacks (orders pile in `pending_payment` and never resolve), this card looks healthy because the customer reached order-create. The contrast diagnostic: if abandonment is flat but [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) shows `pending_payment` ballooning, the regression is post-checkout (gateway/webhook), not in-checkout. |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a for the ratio. The lost-revenue companion uses `base_grand_total` so multi-currency stores roll up cleanly.                                                                                                                                                                                                                                                                                                                                |
| **Store View scope (`store_id`)**                      | **All Store Views summed by default.** A US-only checkout regression on a multi-Store-View merchant may dilute below the 2-sigma threshold if the UK store is healthy. Per-Store-View variants strongly recommended for any merchant with regional checkout differentiation (different gateways, different shipping providers, different tax services per region).                                                                             |
| **Time window**                                        | `RT` (real-time, hour-by-hour rolling).                                                                                                                                                                                                                                                                                                                                                                                                        |
| **Alert trigger**                                      | `abandonment rate >2-sigma vs 30D baseline` at same hour-of-week. The same-hour-of-week comparator handles natural patterns (Sunday-night impulse-buyers vs Tuesday-morning B2B procurement).                                                                                                                                                                                                                                                  |
| **Roles**                                              | owner, marketing, engineering                                                                                                                                                                                                                                                                                                                                                                                                                  |

## Calculation

```
COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A specialty kitchenware retailer on Adobe Commerce 2.4.6 with a US Store View, a UK Store View, and a B2B portal Store View. Tuesday 19 Apr 26, 11:00 GMT. The alert just fired on the UK Store View.

**30-day baseline (Tuesdays 11:00 GMT, UK Store View):**

|                         | Quote count | Order count | Abandonment rate |
| ----------------------- | ----------- | ----------- | ---------------- |
| Mean (4 prior Tuesdays) | 412         | 132         | 67.9%            |
| Standard deviation      | 38          | 14          | 2.4%             |
| 2-sigma upper bound     |             |             | 72.7%            |

**Current hour (this Tuesday 11:00):**

| Stream        | Quote count | Order count | Abandonment rate | vs baseline              |
| ------------- | ----------- | ----------- | ---------------- | ------------------------ |
| US (consumer) | 308         | 96          | 68.8%            | within range             |
| UK (consumer) | 446         | 89          | **80.0%**        | **+12.1 pts, \~5-sigma** |
| B2B portal    | 22          | 19          | 13.6%            | within B2B range         |

The alert fired because UK abandonment jumped from a baseline 67.9% to 80.0%. Quote volume looks healthy (446 vs 412 baseline) so traffic isn't the issue; it's that 357 of those 446 quote-creators didn't reach order-complete.

What the investigation reveals:

1. **The US store is fine.** The regression is UK-specific.
2. **B2B is fine** (small sample, Company users with saved cards rarely abandon). This rules out a backend Adobe Commerce platform issue (the UK and B2B Store Views run on the same Magento installation).
3. **Pulling the most recent 50 abandoned UK quotes**: 41 of 50 reached the shipping-method step but no order followed. That points at the shipping or payment phase.
4. **Stripe Dashboard for the same hour**: Stripe shows no payment attempts that failed, just no attempts at all. So the customers aren't reaching the payment step.
5. **Adobe Commerce admin > Stores > Configuration > Sales > Shipping Methods (UK Store View scope)**: a new free-shipping rule was deployed at 09:30 with a syntax error in the conditions, the `Royal Mail Tracked 24` method silently disappeared from the storefront for any cart under £50.
6. **The fix:** roll back the shipping rule. Within 30 minutes of the rollback, abandonment returns to \~68%.
7. **Lost revenue estimate** for the 1-hour incident window: 357 abandoned quotes × baseline conversion rate (32%) × baseline UK AOV (\~£68) = \~£7,750 of revenue at risk if the rule had stayed live for the full day.

The point of this card: a quote-to-order ratio change is a leading indicator. Total Revenue would have shown the dip 2-3 hours later (after the order-create rate collapsed enough to bend the hourly revenue curve). The alert caught it within the same hour.

## Sibling cards merchants should reference together

This alert is most useful when triangulated with funnel-stage cards and payment-side cards.

| Card                                                                                                 | Why pair it with Cart-Abandonment Spike Alert                                                                                                                                                          |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                                  | The numerator. A drop here downstream of a quote-rate that's flat is the canonical abandonment signature.                                                                                              |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)             | If `pending_payment` is ballooning while abandonment is flat, the regression is post-checkout (gateway callback failure), not in-checkout.                                                             |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                                    | If abandonment spikes coincide with AOV change, a checkout step (shipping cost, tax estimate, freight rule) is the likely culprit.                                                                     |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                                | Lagging confirmation. Abandonment leads revenue by 2 to 3 hours; a confirmed sustained abandonment spike means revenue will follow.                                                                    |
| [Guest vs Account Checkout](/nerve-centre/kpi-cards/adobe-commerce/guest-vs-account-orders)          | If abandonment spikes only on guest checkout, the regression is likely in the guest path (address validation, account-create form). If it spikes on logged-in customers too, the regression is shared. |
| [Discount %](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue)                             | If discount usage drops sharply alongside abandonment, the discount-code field broke.                                                                                                                  |
| [`stripe.stripe_payment_decline_rate`](/nerve-centre/stripe/stripe_payment_decline_rate)             | If Stripe declines spiked, the regression is at the payment-attempt stage (stale Stripe public key, 3DS configuration changed, BIN-block list update).                                                 |
| [`shopify.shopify_alert_cart_abandon_spike`](/nerve-centre/shopify/shopify_alert_cart_abandon_spike) | Cross-platform peer for agencies running multi-platform clients.                                                                                                                                       |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

Adobe Commerce has a native abandoned-cart view, though it is shaped for outreach rather than spike detection:

> **Reports > Sales > Abandoned Carts** lists quotes with at least one item that did not convert, in the Adobe Commerce sense (no associated order). Filter by date range to see the hour-by-hour count. The Adobe view shows the absolute count; this card derives a ratio against quote volume which the Admin view does not natively compute.

For Adobe Commerce B2B (paid edition), the Companies view also surfaces unfinished quotes per Company, but again does not compute the ratio.

For the order side of the ratio:

> **Sales > Orders** filtered to today, with a counter row at the top, gives the order denominator.

Other Adobe Commerce Admin views that look relevant but are not:

* **Reports > Sales > Tax**: tax aggregations, no funnel signal.
* **Reports > Sales > Coupons**: coupon usage, lagging indicator at best.
* **Customers > Now Online**: who is currently logged in, no quote signal.
* **Marketing > Cart Price Rules**: rules engine, not realtime cart state.

**Why our number may legitimately differ from the Adobe Commerce Abandoned Carts view:**

| Reason                                                                                                                                                                                                                                                                                                                                                              | Direction of divergence                                    |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| **Definition of "abandoned"**. Adobe Commerce Admin defines an abandoned cart as a quote not associated with any order, including `canceled` orders if the quote ID was reused. This card excludes `canceled` orders from the numerator (treating them as not-converted) but includes the quote in the denominator, which is the closer-to-funnel-truth definition. | Vortex IQ ratio slightly higher than Admin's implied ratio |
| **Time-zone**. Admin renders in Store View timezone, the card runs UTC. Hour-of-week boundaries shift by the timezone offset.                                                                                                                                                                                                                                       | ±N hours depending on Store View timezone                  |
| **Quote eligibility**. Admin counts every quote with at least one item; the card additionally excludes quotes where `customer_is_guest=1` AND `items_count=1` AND last\_updated within 5 minutes (a common bot-pattern). On bot-heavy stores this reduces noise materially.                                                                                         | Vortex IQ slightly lower quote count                       |
| **Multi-Store-View scope**. Admin scopes to one Store View; this card sums by default.                                                                                                                                                                                                                                                                              | Vortex IQ higher quote and order counts                    |
| **Sync lag**. The card uses the most recent OpenSearch sync (5 to 15 minutes); Admin is live.                                                                                                                                                                                                                                                                       | Vortex IQ slightly stale at the boundary                   |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

The cross-connector contrast is itself a diagnostic for this card.

| Card                                                                                       | Expected relationship                                                | What divergence tells you                                                                                                                                                                                              |
| ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`google_analytics.ga_checkout_funnel`](/nerve-centre/google_analytics/ga_checkout_funnel) | GA4 checkout-step drop-off should align with the abandonment spike   | If GA4 shows the drop at step 2 (shipping) and the alert fired, you have your stage. If GA4 shows no drop but the alert fired, the issue is between order-create and order-confirm, not in the customer-facing funnel. |
| [`stripe.stripe_payment_decline_rate`](/nerve-centre/stripe/stripe_payment_decline_rate)   | Decline rate aligned with abandonment spike means payment regression | A decline-rate spike with steady abandonment means existing customers are getting blocked but new shoppers are still completing.                                                                                       |
| [`google_search_console.gsc_clicks`](/nerve-centre/google_search_console/gsc_clicks)       | Inbound traffic should be normal during a regression                 | If GSC clicks dropped at the same time as abandonment spiked, the page-level issue is broader (template error, redirect loop).                                                                                         |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same alert exists with platform-specific definitions on other commerce connectors. This is **not a reconciliation**; your Adobe Commerce store does not have a parallel Shopify or BigCommerce store. These cross-links exist so agencies running multi-platform client books can navigate between equivalent metrics.

  * [`shopify.shopify_alert_cart_abandon_spike`](/nerve-centre/shopify/shopify_alert_cart_abandon_spike)
  * [`bigcommerce.bc_alert_cart_abandon_spike`](/nerve-centre/bigcommerce/bc_alert_cart_abandon_spike)
</details>

## Known limitations / merchant FAQs

**The alert fired but my Google Analytics checkout funnel looks fine, why?**
Two common causes. First, GA4 misses 10 to 25% of customer activity due to ad blockers and consent rejection; the card uses Adobe-side server data which is closer to ground truth. Second, the abandonment may be happening at the order-confirm stage (after the customer clicks "Place Order") which GA4 attributes as a successful purchase event but Adobe never receives the gateway callback to mark `state = processing`. Cross-check [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) for `pending_payment` accumulation.

**What's the difference between the Adobe Commerce Abandoned Cart report and this card?**
The Adobe Admin report counts abandoned carts in absolute terms over a date range, optimised for the marketing team to send recovery emails. This card computes a ratio against quote volume and detects deviation from baseline, optimised for engineering and operations to detect regressions. The Admin report is a list; this card is a smoke alarm.

**Adobe Commerce vs Magento Open Source: does this card work on the free edition?**
Yes. The quote and order tables exist in both editions. The B2B Companies filter (used in some peer cards) requires Adobe Commerce; this alert does not. The only relevant difference is that some Adobe Commerce edition features (Page Builder, customer segments) can change checkout flow and create their own regression sources, those are absent on Open Source.

**Why does the alert use 2-sigma rather than a fixed threshold like 75% abandonment?**
Baseline abandonment varies hugely between merchants. A B2B-heavy Adobe Commerce store may have 35% baseline abandonment (logged-in repeat buyers); a fashion DTC store may baseline at 78%. A fixed 75% threshold would constantly fire on the fashion store and never fire on the B2B store. The 2-sigma comparator normalises against each merchant's own baseline and against same-hour-of-week patterns.

**My multi-store Adobe Commerce, can I get a per-Store-View alert?**
Yes, configure per-Store-View variants in the manifest, filtering both quote and order counts by `store_id`. This is strongly recommended for any merchant with regional checkout differentiation: different gateways per region, different shipping providers, different tax services. A region-locked regression on the combined view often dilutes below the 2-sigma threshold.

**Why does abandonment fluctuate hour-by-hour even without a regression?**
Smaller volume buckets are noisier. A merchant doing 50 orders per hour at baseline can swing the ratio by 5 to 10 points just on Poisson variance. The 2-sigma comparator absorbs natural variance; only sustained or extreme deviations trigger. For very low-volume stores (under 100 orders/day) consider widening the bucket to 6-hour rolling.

**B2B accounts barely abandon, why include them in the count at all?**
You're right that B2B abandonment baselines are far lower (often single digits). A B2B portal Store View with 100 quotes and 95 orders is typical. By default the card aggregates all Store Views, which can wash out a consumer-side regression. Filter to consumer Store Views only, or set up per-Store-View variants. The B2B portal having its own variant catches a different problem (the supplier relationship breakdown rather than checkout regression).

**Quote-create count seems suspiciously high, are bots being counted?**
Possibly. Adobe Commerce creates a quote on first add-to-cart, including from headless storefronts and from automated price-checker bots. The card excludes the most obvious pattern (single-item, guest, last-updated within 5 minutes of create) but sophisticated bots can evade. If your quote-create count is more than 5x your active-session count from GA4, install bot management (Cloudflare Bot Management, Akamai BotManager) and treat the elevated baseline as a known data quality issue.

**Why doesn't the alert fire when revenue is down?**
Two reasons. First, this is a leading indicator on the funnel; revenue drops are often lagging effects 2 to 6 hours later. Second, a revenue drop caused by upstream traffic loss (an SEO penalty, a paid-ads budget exhausted) shows up as fewer quotes AND fewer orders proportionally, leaving the abandonment ratio steady. Use [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert) for cash-side monitoring and this card for funnel-side monitoring; they catch different failure modes.

***

### Tracked live in Vortex IQ Nerve Centre

*Cart-Abandonment Spike Alert* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Customer Acquisition Trend, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend

Customer Acquisition Trend for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Daily distinct-customer count over trailing 90 days. The trend chart for [Customer Count](/nerve-centre/kpi-cards/adobe-commerce/unique-customers), with optional new-vs-returning split. Adobe Commerce merchants often see a 7-day weekly pattern (B2B procurement-heavy weekday peaks, consumer weekend dips) plus monthly cycles (B2B end-of-month PO clustering).

|                                                        |                                                                                                                                                                                                          |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | Daily `CARDINALITY(customer_email)` over 90 days. Each day is one bucket showing distinct customers who placed at least one order that day. Optional decomposition: new (first-ever order) vs returning. |
| **API field**                                          | `customer_email`, `created_at`, optional `customer_id` from `GET /rest/V1/orders`. New-vs-returning detection via per-customer `created_at` history.                                                     |
| **VAT / tax treatment**                                | n/a, count metric.                                                                                                                                                                                       |
| **Shipping inclusion**                                 | n/a.                                                                                                                                                                                                     |
| **Discounts**                                          | n/a.                                                                                                                                                                                                     |
| **Credit Memo refund treatment**                       | A customer who later got a full refund still counts on the original-order day.                                                                                                                           |
| **`state` machine inclusion**                          | All states except `canceled`.                                                                                                                                                                            |
| **`pending_payment` quirk**                            | Included.                                                                                                                                                                                                |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a for the count.                                                                                                                                                                                       |
| **Store View scope (`store_id`)**                      | All Store Views; same email across Store Views deduped per day.                                                                                                                                          |
| **Time window**                                        | `90D` daily granularity. 7-day moving average overlay typical.                                                                                                                                           |
| **Alert trigger**                                      | None by default.                                                                                                                                                                                         |
| **Roles**                                              | owner, marketing                                                                                                                                                                                         |

## Calculation

```
DATE_HISTOGRAM CARDINALITY(customer_email)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6, US/UK/B2B Store Views. 90-day window ending Monday 4 May 26.

**90-day overview:**

| Metric                           | Value                         |
| -------------------------------- | ----------------------------- |
| Total distinct customers (90D)   | 11,420                        |
| Average daily distinct customers | 320                           |
| Standard deviation               | 65                            |
| Highest single-day count         | 542 (after Mother's Day push) |
| Lowest single-day count          | 184 (Christmas Day)           |

**Weekly pattern (median day-of-week):**

| Day | Median customers |
| --- | ---------------- |
| Mon | 380              |
| Tue | 410              |
| Wed | 405              |
| Thu | 395              |
| Fri | 350              |
| Sat | 240              |
| Sun | 220              |

**New-vs-returning split (90D total):**

| Cohort                 | Customers | % of total |
| ---------------------- | --------- | ---------- |
| New (first-ever order) | 4,640     | 40.6%      |
| Returning              | 6,780     | 59.4%      |

What this is telling marketing:

1. **Weekday-heavy customer pattern.** Tuesday and Wednesday are peak; weekend dips reflect B2B-mix dominance (B2B is overwhelmingly weekday).
2. **40.6% new customer rate over 90 days** is a healthy acquisition cadence. Consumer-side; on B2B it's typically \<5%.
3. **The Mother's Day spike** (542 on the peak day, \~70% above 7-day moving average) is a campaign-driven event. Useful to see how the cohort acquired performs over the next 90 days for ROAS attribution.
4. **The Christmas Day trough** (184) is the lowest single day. Expected: most B2B and consumer activity pauses Christmas Day. Use this baseline rather than the moving average for "is the business operating normally" detection on holidays.
5. **Cross-checking [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers) trend**: new-customer rate has been stable at \~40% for 6 of the 12 weeks; rose to \~50% in weeks 8 and 9 (Mother's Day campaign push) then receded. The campaign created a transient lift in new-customer share.
6. **Cross-checking [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)**: 59.4% returning over 90 days is in the healthy range; well-retained brands run 55-70%, struggling ones below 50%.
7. **Strategic question**: should the merchant invest in a Saturday-Sunday weekend campaign to lift weekend customer count? The 40% weekday-vs-weekend gap is a B2B effect; converting consumer weekend traffic better could close the gap. Cross-check with paid-traffic conversion rates by day-of-week.

## Sibling cards merchants should reference together

| Card                                                                                       | Why pair it with Customer Trend                             |
| ------------------------------------------------------------------------------------------ | ----------------------------------------------------------- |
| [Customer Count](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)                  | Single-period summary; this card is its trend chart.        |
| [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers)                      | The first-time-orderer subset.                              |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)        | The returning subset.                                       |
| [Daily Order Trends](/nerve-centre/kpi-cards/adobe-commerce/daily-order-trends)            | Sibling chart at the order level (not deduped to customer). |
| [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time)              | The dollar-weighted view of the same period.                |
| [Customer Segments](/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments)        | Per-cohort rollup.                                          |
| [`google_analytics.ga_users_over_time`](/nerve-centre/google_analytics/ga_users_over_time) | Top-of-funnel comparison.                                   |
| [`shopify.customer_trend`](/nerve-centre/kpi-cards/shopify/customer-acquisition-trend)     | Cross-platform peer.                                        |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Customers > Customers by Number of Orders** with a date range gives the per-customer activity, not a daily trend. Manual aggregation needed for the daily series.

> **Sales > Orders** with date filter, group by date manually via export.

> **Dashboard > Last Orders** is real-time but only shows the last 5 orders.

For B2B (Adobe Commerce paid edition):

> **Customers > Companies** with order history, manual per-Company timeline.

**Why our number may legitimately differ from a manual Admin computation:**

| Reason                                                                                                                           | Direction of divergence                           |
| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Time-zone**. Admin in Store View timezone; card UTC. Day boundaries shift.                                                     | ±1 day per bucket                                 |
| **Email vs `customer_id`**. Card uses email which captures both registered and guests; Admin's customer-grid is registered only. | Card count higher                                 |
| **Multi-Store-View dedup**. Card dedupes the same email across Store Views.                                                      | Card slightly lower than Store-View-summed manual |
| **`canceled` exclusion**. Card excludes; Admin includes unless filtered.                                                         | Card count slightly lower                         |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                                       | Expected relationship                                                       | What divergence tells you                                      |
| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | -------------------------------------------------------------- |
| [`google_analytics.ga_users_over_time`](/nerve-centre/google_analytics/ga_users_over_time) | GA4 users with `purchase` event ≈ Adobe customer trend × (1 - tracking gap) | Material divergence indicates GA4 tag-fire issues at checkout. |
| ESP active-recipient daily count                                                           | ESP "active" definition varies; usually broader                             | Trend correlation more useful than absolute alignment.         |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.customer_trend`](/nerve-centre/kpi-cards/shopify/customer-acquisition-trend)
  * [`bigcommerce.customer_trend`](/nerve-centre/kpi-cards/bigcommerce/customer-acquisition-trend)
</details>

## Known limitations / merchant FAQs

**Why does my customer count drop on weekends?**
Adobe Commerce stores typically run B2B-heavy or B2B-mixed; B2B procurement is weekday-only. The weekend dip reflects the weekday-weekend B2B/consumer split. Pure-DTC consumer brands without B2B see weekend peaks instead.

**The card shows 320/day average but my CRM shows 5,000 active customers, contradiction?**
No. 320/day average means about 320 distinct customers order on a typical day; over 90 days that aggregates to \~11,400 distinct customers (because most are repeat). Both numbers are correct; they answer different questions.

**Adobe Commerce vs Magento Open Source: any difference?**
None at the calculation. The card runs identically.

**My multi-store Adobe Commerce, can I see per-Store-View trends?**
Yes, configure per-Store-View variants. Useful for spotting region-specific patterns (US Memorial Day spike, UK Bank Holiday dip).

**A specific day shows zero customers, what happened?**
Two causes: (a) actual zero-business day (Christmas, New Year on certain configurations), (b) data sync gap (the OpenSearch index missed orders for that day, usually self-resolves at next sync). The shape of the surrounding days disambiguates.

**The new-vs-returning split shows 40% new, but my acquisition spend isn't growing, sustainable?**
40% new on 90-day window means new acquisition is keeping up with churn-and-growth. If acquisition spend is flat but new-customer share is rising, your acquisition efficiency is improving. If new share is rising AND retention is dropping, you're acquiring faster than you're retaining (a leaky bucket).

**Why doesn't this card show acquisition channel?**
Acquisition channel attribution requires marketing-platform integration (Google Ads, Meta) cross-tabbed with Adobe order data. This card is the count view; for channel attribution see GA4-side and ad-platform-side cards.

**B2B Companies cross weekday peaks but my consumer side is steady, normal?**
Yes. The aggregate trend has both signals; per-segment trends look very different. B2B mid-week spikes (Tue, Wed) and consumer Saturday peak balance out the blended view.

***

### Tracked live in Vortex IQ Nerve Centre

*Customer Acquisition Trend* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Customer Spend Segments, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments

Customer Spend Segments for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Customer base distributed into LTV cohorts (top 10%, mid 60%, bottom 30%) plus B2B-vs-consumer split. Adobe Commerce paid edition has a native "Customer Segments" feature for marketing rules; this card is the analytical complement, surfacing how the cohort mix evolves and where revenue is concentrated. The 80/20 rule is usually 70/30 on Adobe Commerce because B2B Companies dominate the top.

|                                                        |                                                                                                                                                                                                                                                                                                        |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **What it counts**                                     | For each customer (email-based identity, optionally Company-grouped on B2B), compute trailing-90-day `SUM(grand_total)` and rank. Bucket into LTV deciles, then aggregate to top-10% / mid-60% / bottom-30%. Cross-tab against B2B/B2C segment. Returns the count and revenue contribution per cohort. |
| **API field**                                          | `customer_email`, `customer_id`, `grand_total`, `customer_group_id`, `extension_attributes.company_attributes.company_id` from `GET /rest/V1/orders`.                                                                                                                                                  |
| **VAT / tax treatment**                                | Tax-inclusive on B2C; exempt on most B2B. Cohort ranking is by `grand_total`, so B2C customers in the UK appear slightly higher in the LTV ranking than equivalent-revenue US B2B customers.                                                                                                           |
| **Shipping inclusion**                                 | Included via `grand_total`.                                                                                                                                                                                                                                                                            |
| **Discounts**                                          | Deducted (post-promotion).                                                                                                                                                                                                                                                                             |
| **Credit Memo refund treatment**                       | NOT subtracted. Gross LTV. A high-refund customer may rank above their net contribution.                                                                                                                                                                                                               |
| **`state` machine inclusion**                          | All states except `canceled`.                                                                                                                                                                                                                                                                          |
| **`pending_payment` quirk**                            | Included.                                                                                                                                                                                                                                                                                              |
| **Multi-currency `grand_total` vs `base_grand_total`** | Uses `base_grand_total` for cross-currency LTV ranking.                                                                                                                                                                                                                                                |
| **Store View scope (`store_id`)**                      | All Store Views by default. Per-Store-View variants useful when consumer cohort is regionally heterogeneous.                                                                                                                                                                                           |
| **B2B Company aggregation**                            | Each Company aggregated as one customer for the B2B segment by default.                                                                                                                                                                                                                                |
| **Time window**                                        | `90D`                                                                                                                                                                                                                                                                                                  |
| **Alert trigger**                                      | None by default.                                                                                                                                                                                                                                                                                       |
| **Roles**                                              | owner, marketing                                                                                                                                                                                                                                                                                       |

## Calculation

```
RANGE(grand_total) by spend bucket
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6, B2B Companies module enabled. Snapshot Monday 4 May 26.

**Trailing 90-day customer base, 9,820 active customers (180 B2B Companies + 9,640 consumers):**

| Cohort                           | Customer count | 90D revenue | Revenue share | Avg per customer |
| -------------------------------- | -------------- | ----------- | ------------- | ---------------- |
| **Top 10%** (982 customers)      | 982            | \$1,640,000 | 65%           | \$1,670          |
| - of which B2B Companies         | 142            | \$1,210,000 | 48%           | \$8,520          |
| - of which consumer              | 840            | \$430,000   | 17%           | \$512            |
| **Mid 60%** (5,892 customers)    | 5,892          | \$720,000   | 28%           | \$122            |
| **Bottom 30%** (2,946 customers) | 2,946          | \$172,000   | 7%            | \$58             |
| **Total**                        | 9,820          | \$2,532,000 | 100%          | \$258            |

What this is telling marketing:

1. **The top 10% generates 65% of revenue.** Classic Pareto. On Adobe Commerce, the top decile is dominated by B2B (142 of 982 customers but $1.21m of $1.64m).
2. **142 B2B Companies generate 48% of total revenue.** Each is worth \~$8,500 of trailing-90-day revenue, ~$34,000 annualised. Loss of any single top-decile B2B account is a 0.3% hit to total revenue.
3. **The mid-60% consumer cohort** (mostly mid-LTV repeat consumers) generates 28% of revenue from 60% of customers. Healthy retention layer.
4. **Bottom 30% of customers contribute only 7% of revenue.** Mostly one-time gift buyers, single-purpose shoppers, and recently-acquired-not-yet-repeat. Marketing investment in this cohort is generally unprofitable; a "first repeat purchase" cadence may be worth running, but acquisition spend on lookalikes of this cohort is wasteful.
5. **Cross-checking [Churn Risk](/nerve-centre/kpi-cards/adobe-commerce/customer-churn-risk)**: top-10% has 8% churn risk, mid-60% has 32%, bottom-30% has 44%. The retention investment priority is mid-60%: high churn risk, material revenue contribution, manageable count for an email-cadence intervention.
6. **Cross-checking [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)**: 48% B2B share is consistent with this cohort decomposition (the Companies are mostly in the top decile).
7. **Strategic implications**:
   * B2B account-based marketing focus on top-10% B2B Companies (142 accounts, \~\$1.2m revenue at stake).
   * Consumer retention focus on mid-60% (5,892 customers, \~\$720k revenue at stake).
   * Acquisition focus reviews the lookalike profile of top-10% consumers (840 customers, \$430k revenue) rather than blanket lookalikes of all-customers.

The point: customer base on Adobe Commerce is heavily concentrated. Cohort decomposition reveals where to invest marketing effort.

## Sibling cards merchants should reference together

| Card                                                                                      | Why pair it with Customer Segments                           |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| [Customer Count](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)                 | The denominator.                                             |
| [Churn Risk](/nerve-centre/kpi-cards/adobe-commerce/customer-churn-risk)                  | Per-cohort churn prioritisation.                             |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)             | Top-decile dominance comes from B2B.                         |
| [B2B Accounts Gone Quiet](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet) | Top-decile B2B silence is the highest-priority Sales action. |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)       | Lifetime repeat behaviour underlies cohort stability.        |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                     | The aggregate.                                               |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                         | AOV varies materially across cohorts.                        |
| [`shopify.customer_segments`](/nerve-centre/kpi-cards/shopify/customer-spend-segments)    | Cross-platform peer.                                         |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Customers > Segments** (Adobe Commerce paid edition only) lets you define rule-based segments for marketing automation. The Admin Segments feature is rule-driven (e.g. "customers with >5 orders in last 12 months"); this card uses LTV ranking which the Admin doesn't natively compute.

> **Reports > Customers > Customers by Orders Total** ranks customers by lifetime revenue. Decile-bucketing requires CSV export and spreadsheet computation.

> **Reports > Customers > Customers by Number of Orders** ranks by order count, complementary to LTV ranking.

For B2B (Adobe Commerce paid edition):

> **Customers > Companies** with sort by 90-day revenue (manual via export-and-pivot).

**Why our number may legitimately differ from Admin:**

| Reason                                                                                                                  | Direction of divergence                    |
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
| **LTV vs Order Count ranking**. Card uses LTV (sum of grand\_total). Admin's order-count-rank shows different ordering. | Material if a few large orders skew LTV    |
| **B2B Company aggregation**. Card aggregates by Company; Admin shows by buyer-email.                                    | Material if Companies have multiple buyers |
| **`canceled` exclusion**. Card excludes; Admin includes unless filtered.                                                | Card LTV slightly higher                   |
| **Time window**. Card uses 90 days; Admin reports default to all-time.                                                  | Different cohorts entirely                 |
| **Refund-adjustment**. Card uses gross LTV (no refund subtraction).                                                     | Material for high-refund customers         |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                           | Expected relationship                                              | What divergence tells you                                                                                      |
| -------------------------------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------- |
| [`klaviyo.list_segments`](/nerve-centre/klaviyo/list_segments) | Klaviyo's RFM segments should overlap with this card's LTV cohorts | Material divergence indicates Klaviyo's segmentation criteria don't reflect dollar-weighted reality.           |
| ESP top-spender list                                           | Should match top-decile within sync lag                            | Klaviyo top-spender lists are usually current; this card uses 90-day; diff = customers outside the 90D window. |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.customer_segments`](/nerve-centre/kpi-cards/shopify/customer-spend-segments)
  * [`bigcommerce.customer_segments`](/nerve-centre/kpi-cards/bigcommerce/customer-spend-segments)
</details>

## Known limitations / merchant FAQs

**Why does the card use LTV ranking rather than the Adobe Commerce Customer Segments feature?**
Adobe Commerce's native Customer Segments is rule-driven (predicate logic for marketing automation: "customers in California with abandoned carts in last 7 days"). It's optimised for marketing rules, not analytical decomposition. This card complements rather than replaces; use the native feature for marketing-rule targeting and this card for cohort-revenue analysis.

**Adobe Commerce vs Magento Open Source: any difference?**
Open Source lacks the Customer Segments rule engine but has the same underlying customer/order tables. The card runs identically. Open Source merchants who want rule-based marketing typically install a third-party module or use ESP segmentation (Klaviyo, Mailchimp).

**Why are top-decile thresholds different across stores?**
The card computes deciles on the merchant's own customer base. A high-AOV B2B distributor's top decile threshold may be $20,000 of trailing 90-day revenue; a DTC fashion store's may be $400. Each store's thresholds reflect its own business shape.

**Are B2B Companies really worth aggregating to one customer?**
Depends on the question. For "where is revenue concentrated", yes (one Company is one decision-making unit). For "how many people log into our portal", no (each buyer-email is a user). Configure the manifest aggregation to match the question.

**Why include `pending_payment` orders in LTV?**
B2B net-30 pipelines depend on `pending_payment`-state orders. Excluding them would understate B2B LTV by a third or more on net-30-heavy stores.

**My multi-store Adobe Commerce, can I see per-region cohorts?**
Yes, configure per-Store-View variants. Useful when consumer cohort is regionally heterogeneous (UK is mostly mid-LTV, US has more long-tail bottom-decile).

**Why is the bottom decile so big (30% of customers, 7% of revenue)?**
Common pattern. New customer acquisition floods the bottom; gift buyers, one-time-purpose shoppers, and recently-acquired-not-yet-repeat customers all pile into the lowest decile. This is normal and useful as the "convert to repeat" pool, but generally not where retention investment pays back.

**A specific B2B Company isn't appearing in top-10% even though they spent a lot, why?**
Most likely cause: the 90-day window doesn't include their order. B2B accounts on quarterly cadence may have placed their last \$50k PO 100 days ago, putting them outside the window. Consider a longer window (180D, 365D) for B2B-LTV ranking specifically.

**The card and ESP segmentation disagree on top spenders, who's right?**
Both, for different definitions. Card uses 90-day Adobe order data; ESP often uses a longer window plus marketing-engagement signals. Align the windows before comparing.

***

### Tracked live in Vortex IQ Nerve Centre

*Customer Spend Segments* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Daily Order Trends, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/daily-order-trends

Daily Order Trends for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Daily order count over trailing 30 days. The most-used operational chart on Adobe Commerce dashboards: warehouse staffing, customer-service capacity planning, and ad-budget pacing all reference this curve. Adobe Commerce stores typically show a strong weekday weekend pattern with monthly cycles overlaid (B2B end-of-month PO clusters).

|                                                        |                                                                                                                                                                                                                      |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `COUNT(orders) GROUP BY date(created_at)` over 30 days. Each day is a bucket; 30 buckets per series. Optional 7-day moving average overlay.                                                                          |
| **API field**                                          | `_id`, `created_at` from `GET /rest/V1/orders`.                                                                                                                                                                      |
| **VAT / tax treatment**                                | n/a, count metric.                                                                                                                                                                                                   |
| **Shipping inclusion**                                 | n/a.                                                                                                                                                                                                                 |
| **Discounts**                                          | n/a.                                                                                                                                                                                                                 |
| **Credit Memo refund treatment**                       | An order later refunded counts on the original-order day.                                                                                                                                                            |
| **`state` machine inclusion**                          | All states except `canceled` (cancelled orders aren't operationally meaningful for warehouse and customer service planning).                                                                                         |
| **`pending_payment` quirk**                            | Included. Net-30 B2B orders count as "orders placed" even though no money has captured. For "orders that will need fulfillment" use [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders). |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a.                                                                                                                                                                                                                 |
| **Store View scope (`store_id`)**                      | All Store Views by default; per-Store-View overlays useful for spotting region-specific patterns (a UK Store View campaign that doesn't affect US).                                                                  |
| **Time window**                                        | `30D` daily granularity.                                                                                                                                                                                             |
| **Alert trigger**                                      | None by default.                                                                                                                                                                                                     |
| **Roles**                                              | owner, marketing, operations                                                                                                                                                                                         |

## Calculation

```
DATE_HISTOGRAM COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6, US/UK/B2B Store Views. 30-day window ending Monday 4 May 26.

**Daily order count summary:**

| Metric                        | Value                       |
| ----------------------------- | --------------------------- |
| Average daily orders          | 240                         |
| Standard deviation            | 48                          |
| Highest day                   | 392 (Mother's Day Saturday) |
| Lowest day                    | 142 (Easter Sunday)         |
| 7-day moving average (latest) | 252                         |

**Day-of-week median:**

| Day | Median orders |
| --- | ------------- |
| Mon | 285           |
| Tue | 308           |
| Wed | 304           |
| Thu | 285           |
| Fri | 248           |
| Sat | 168           |
| Sun | 154           |

What this is telling operations:

1. **Order volume is mid-week heavy.** B2B procurement clusters Tuesday/Wednesday; warehouse staffing should be heaviest Wednesday/Thursday for the lagged dispatch.
2. **The Mother's Day spike (392 on the campaign Saturday)** is 60% above weekly median, expected for the campaign. Worth comparing the cohort acquired that day for 90-day repeat behaviour.
3. **The Easter Sunday trough (142)** is the lowest of the period. B2B is closed; consumer demand is reduced. Plan warehouse and customer service to reflect this.
4. **The 7-day moving average of 252** is up 8% vs the same window a quarter ago. Steady growth.
5. **Cross-checking [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)**: customers per day track orders per day closely (orders-per-customer hovers around 1.05). A sudden divergence (orders rising faster than customers) indicates AOV-rising-by-larger-baskets or repeat-orders-from-same-customer-in-day patterns.
6. **Action**: warehouse staffing for the next 14 days should target 250-300 orders/day capacity; surge-staffing reserved for the next campaign push (planned for week 4).

## Sibling cards merchants should reference together

| Card                                                                                         | Why pair it with Daily Order Trends |
| -------------------------------------------------------------------------------------------- | ----------------------------------- |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                          | Single-period summary.              |
| [Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/orders-over-time)                  | Longer-window trend (90 days).      |
| [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)          | Customer-level companion.           |
| [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time)                | Dollar-weighted view.               |
| [Revenue by Day-of-Week](/nerve-centre/kpi-cards/adobe-commerce/revenue-by-day-of-week)      | The DOW pattern decomposition.      |
| [Daily Leakage](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)                   | Operational fulfillment slice.      |
| [`google_analytics.ga_orders_over_time`](/nerve-centre/google_analytics/ga_orders_over_time) | Top-of-funnel comparison.           |
| [`shopify.daily_order_trends`](/nerve-centre/shopify/daily_order_trends)                     | Cross-platform peer.                |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Orders** with the date range. Adobe's report shows daily totals natively when granularity is set to "Day".

> **Dashboard > Orders** widget shows the recent days at a glance.

> **Sales > Orders** with date filter for individual order verification.

For multi-Store-View:

> Switch scope to specific Store View; each Store View has its own daily totals.

**Why our number may legitimately differ from Admin:**

| Reason                                                                         | Direction of divergence                    |
| ------------------------------------------------------------------------------ | ------------------------------------------ |
| **Time-zone**. Admin in Store View timezone; card UTC. ±1 day per bucket.      | Boundary-day differences                   |
| **`canceled` exclusion**. Card excludes; Admin includes unless filtered.       | Card lower                                 |
| **Multi-Store-View aggregation**. Card sums; Admin defaults to one Store View. | Card higher than per-Store-View admin view |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin live.                | Negligible at daily                        |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                                         | Expected relationship            | What divergence tells you                                |
| -------------------------------------------------------------------------------------------- | -------------------------------- | -------------------------------------------------------- |
| [`google_analytics.ga_orders_over_time`](/nerve-centre/google_analytics/ga_orders_over_time) | GA4 ≈ Adobe × (1 - tracking gap) | 10-25% lower is normal.                                  |
| [`stripe.stripe_charges`](/nerve-centre/stripe/stripe_charges)                               | Stripe-paid orders only; subset  | Stripe is a subset; net-30 B2B orders skew Adobe higher. |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.daily_order_trends`](/nerve-centre/shopify/daily_order_trends)
  * [`bigcommerce.daily_order_trends`](/nerve-centre/bigcommerce/daily_order_trends)
</details>

## Known limitations / merchant FAQs

**Why does my chart drop on weekends but my GA4 sessions stay flat?**
B2B procurement is weekday-only; consumer browsing continues on weekends but at lower conversion. The order-per-session ratio drops on weekends, dragging order count down even though traffic is steady.

**Adobe Commerce vs Magento Open Source: any difference?**
None at the calculation. Both editions show the same trend.

**My multi-store Adobe Commerce, can I see per-Store-View overlays?**
Yes, configure per-Store-View series in the manifest. Useful for spotting regional campaign effects.

**The chart shows 0 orders on a recent day, what happened?**
Two causes: actual zero-order day (Christmas, holidays) or sync gap (the OpenSearch index missed orders). Cross-check Adobe Admin for ground truth.

**Why include `pending_payment` orders in the count?**
B2B net-30 orders are placed-orders even though uncaptured. Excluding them would understate the operational pipeline.

**A spike day shows up but my warehouse didn't see it, why?**
Most likely B2B net-30 orders. They're placed (the sale is real, the customer committed) but no payment has captured and no shipment is required for some hours/days. Cross-check [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders) for the warehouse-relevant view.

**Why does the chart use `created_at` rather than `updated_at`?**
Day-of-business is the order-creation day; subsequent state changes don't move the order to a different day for capacity planning purposes.

**The pattern looks different from my GA4 chart, why?**
GA4 measures purchase events (which fire on Adobe order create); they should track. Material divergence indicates GA4 tag-fire issues at checkout.

***

### Tracked live in Vortex IQ Nerve Centre

*Daily Order Trends* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Discount % of Revenue, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue

Discount % of Revenue for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Total discount value as a percentage of revenue, over the trailing 30 days. Margin-compression detector. Adobe Commerce stores often have higher discount-of-revenue % than Shopify equivalents because B2B tier pricing (`customer_group_price`) is structurally always-on. Healthy DTC ranges 3 to 8%; B2B-mixed stores 6 to 15%. Above 15% triggers margin scrutiny.

|                                                        |                                                                                                                                                                                                                                                                         |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `SUM(discount_amount) / SUM(grand_total)`. The numerator includes cart-rule discounts (BOGO, percent-off codes), customer-group price discounts (B2B tier pricing), and applied catalog price rules. Excludes shipping discounts (separate field).                      |
| **API field**                                          | `discount_amount`, `grand_total` from `GET /rest/V1/orders`.                                                                                                                                                                                                            |
| **VAT / tax treatment**                                | The ratio is a percentage so tax-bias washes out only if both numerator and denominator are tax-treated identically. Adobe stores discount typically pre-tax; `grand_total` is post-tax. This means discount % is slightly understated relative to a pure pre-tax view. |
| **Shipping inclusion**                                 | `discount_amount` excludes shipping discount; `grand_total` includes shipping. Mild understatement of discount % because the denominator is "fatter" than the numerator.                                                                                                |
| **Discounts**                                          | This card IS discount measurement.                                                                                                                                                                                                                                      |
| **Credit Memo refund treatment**                       | NOT subtracted. A discount given on an order later refunded still counts as discount spent.                                                                                                                                                                             |
| **`state` machine inclusion**                          | All states except `canceled`.                                                                                                                                                                                                                                           |
| **`pending_payment` quirk**                            | Included; B2B net-30 orders with tier discounts are pipeline.                                                                                                                                                                                                           |
| **Multi-currency `grand_total` vs `base_grand_total`** | Uses `base_discount_amount / base_grand_total` for cross-currency rollup.                                                                                                                                                                                               |
| **Store View scope (`store_id`)**                      | All Store Views; per-Store-View variants useful (B2B portal will show much higher discount %).                                                                                                                                                                          |
| **Time window**                                        | `30D vsP`                                                                                                                                                                                                                                                               |
| **Alert trigger**                                      | `>15% (margin compression)`                                                                                                                                                                                                                                             |
| **Sentiment key**                                      | `discount_dependency`                                                                                                                                                                                                                                                   |
| **Roles**                                              | owner, marketing                                                                                                                                                                                                                                                        |

## Calculation

```
SUM(discount_amount) / SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6 with US/UK/B2B Store Views. 30-day window ending Monday 4 May 26.

**Discount % by Store View:**

| Stream      | 30D revenue     | 30D discount | Discount % |
| ----------- | --------------- | ------------ | ---------- |
| US consumer | \$312,800       | \$14,800     | 4.7%       |
| UK consumer | \$246,000       | \$12,400     | 5.0%       |
| B2B portal  | \$462,000       | \$42,600     | 9.2%       |
| **Blended** | **\$1,020,800** | **\$69,800** | **6.8%**   |

**Vs prior 30D (blended):** 5.4% prior vs 6.8% current = +1.4 pts.

What this is telling leadership:

1. **B2B at 9.2% reflects tier pricing** (always-on `customer_group_price` discounts). Material but expected; B2B unit margins absorb this in negotiated contracts.
2. **Consumer (US 4.7%, UK 5.0%) is in the healthy DTC range.** A campaign month would push these to 8-10%; current levels suggest light campaign activity.
3. **Blended +1.4 pt rise vs prior** is driven by the B2B share growing (more B2B mix = higher blended discount %) plus a small consumer uptick (Mother's Day campaign extension).
4. **Cross-checking [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)**: B2B share rose 5.6 pts in the period. The discount % rise is consistent with the B2B mix shift; not an underlying margin compression issue.
5. **Cross-checking [Discount Over Time](/nerve-centre/kpi-cards/adobe-commerce/discounts-given-over-time)**: the daily chart confirms B2B baseline-discount drove the rise; consumer campaign discount was steady.
6. **Action**: no immediate margin concern, but worth setting up a per-Store-View alert at 12% (consumer Store Views) to catch a future campaign creep without dragging on the B2B alert. The current 15% blended trigger is appropriate for the current B2B-mix shape but would not catch a consumer-side issue.

The point: discount % on Adobe Commerce needs segmentation. The blended view obscures B2B tier pricing dragging the average up; per-Store-View clarity reveals whether margin compression is consumer-side (campaign) or structural (B2B mix).

## Sibling cards merchants should reference together

| Card                                                                                   | Why pair it with Discount %                                            |
| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| [Discount Over Time](/nerve-centre/kpi-cards/adobe-commerce/discounts-given-over-time) | Daily trend chart of the absolute value.                               |
| [Total Discount](/nerve-centre/kpi-cards/adobe-commerce/total-discount-used)           | Single-period absolute value.                                          |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                  | The denominator.                                                       |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                      | Discount campaigns drag AOV.                                           |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)          | B2B mix changes blended discount % independently of campaign activity. |
| [B2B AOV vs B2C AOV](/nerve-centre/kpi-cards/adobe-commerce/b2b-aov-vs-b2c-aov)        | B2B tier-pricing impact on per-segment AOV.                            |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                      | Discount-driven impulse buys can have higher refund rates.             |
| [`shopify.discount_pct`](/nerve-centre/kpi-cards/shopify/discount-of-revenue)          | Cross-platform peer.                                                   |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Coupons** lists per-rule usage; manual computation needed for the % vs revenue.

> **Reports > Sales > Orders** with date filter has a per-period discount column; the report total includes all discount types.

> **Marketing > Cart Price Rules** for the rule list and per-rule discount totals.

**Why our number may legitimately differ from Admin:**

| Reason                                                                                                                  | Direction of divergence              |
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| **Coupon vs cart-rule scope**. Admin Coupons report shows code-only rules; this card includes all discount types.       | Card higher than coupons-report-only |
| **Customer-group price**. Often invisible in Admin reports as "discounts"; the card includes them in `discount_amount`. | Card higher than admin perception    |
| **Time-zone**. Admin in Store View timezone; card UTC.                                                                  | Boundary effects                     |
| **Currency**. Card uses `base_*` fields. Admin uses Store View base.                                                    | Material on multi-currency           |
| **`canceled` exclusion**. Card excludes; Admin includes unless filtered.                                                | Marginal                             |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                       | Expected relationship                            | What divergence tells you                                                         |
| -------------------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------- |
| ESP campaign attribution                                                   | ESP-attributed discount ≤ card total             | If ESP shows higher attributed discount than card has spent, attribution overlap. |
| [`google_ads.google_ads_promo`](/nerve-centre/google_ads/google_ads_promo) | Google Ads-attributed promotional revenue ≤ card | Material divergence indicates attribution drift.                                  |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.discount_pct`](/nerve-centre/kpi-cards/shopify/discount-of-revenue)
  * [`bigcommerce.discount_pct`](/nerve-centre/kpi-cards/bigcommerce/discount-of-revenue)
</details>

## Known limitations / merchant FAQs

**Why is my Adobe Commerce discount % higher than industry benchmarks for ecommerce?**
Industry benchmarks are dominated by pure-DTC stores. Adobe Commerce skews B2B-mixed; B2B tier pricing structurally drives discount % higher. Use Adobe-Commerce-matched peer benchmarks: pure-DTC 3-6%, B2B-mixed 6-12%, B2B-heavy 10-20%.

**Adobe Commerce vs Magento Open Source: difference?**
None at the calculation. Both editions handle discount machinery identically.

**My multi-store, can I see per-Store-View discount %?**
Yes, configure per-Store-View variants. Strongly recommended because B2B-tier-pricing-driven discount % can mask consumer-side campaign creep.

**Why exclude shipping discounts from the numerator?**
Shipping discounts (`shipping_discount_amount`) are a separately-managed promotional surface (free shipping over £X is a marketing decision distinct from item-discount campaigns). The card defaults to product-discount-only; configure to include shipping if you want a unified view.

**Customer-group price counts as a discount, why?**
Adobe Commerce's data model: every customer-group-price-applied-vs-base-price difference flows into `discount_amount` as a per-line-item discount. From an accounting perspective this is correct (the difference is revenue forgone). From a campaign perspective, it's not a "campaign discount". The card surfaces the total; rule-name decomposition (in [Discount Over Time](/nerve-centre/kpi-cards/adobe-commerce/discounts-given-over-time)) lets you separate.

**My discount % spiked but I didn't run a campaign, why?**
Likely B2B mix shift. If B2B share rose, blended discount % rises mechanically because B2B has higher structural discount. Cross-check [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share).

**Why does the alert at 15% feel too lenient for my consumer-only Store View?**
The 15% default is for blended (B2B + consumer). Configure per-Store-View thresholds: 8-10% for consumer Store Views, 15-20% for B2B portal Store Views.

**My multi-currency Adobe Commerce, is the % comparable across currencies?**
Yes; the card uses `base_*` for both numerator and denominator so FX-conversion-related artefacts cancel out.

**Why isn't the % subtracting for refunded orders?**
Discount given on a refunded order is still a discount the merchant chose to extend. The customer received the discounted price; the refund returned the post-discount cash. The discount cost was incurred. For pure-net-margin analysis you'd subtract; for marketing-cost analysis the gross figure is right.

***

### Tracked live in Vortex IQ Nerve Centre

*Discount % of Revenue* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Email-Attributed Revenue Share, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/email-attributed-revenue-share

Healthy DTC email programmes drive 15-25% of revenue. Below 8% means either bad list health or broken attribution, both recoverable. How to read it, why i...

**Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> Healthy DTC email programmes drive 15-25% of revenue. Below 8% means either bad list health or broken attribution, both recoverable.

## At a glance

> Email-attributed revenue (Klaviyo / Dotdigital / Mailchimp) divided by Adobe Commerce Total Revenue, expressed as a percentage. Tells you what share of your top-line came from your owned email channel. Healthy DTC programmes sit at 15-25%; below 8% indicates either a list-health problem (low engagement, deliverability slipping) or a broken attribution pipeline (UTMs missing, click-tracking off).

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | Numerator: revenue attributed to email campaigns or flows in the connected ESP (Klaviyo, Dotdigital, etc.) over the 30-day window. Denominator: Adobe Commerce `SUM(grand_total)` over the same window. Returned as a percentage.                                                                                                                                                                                                                                                     |
| **API field**                                          | Numerator from the ESP connector (e.g. Klaviyo `attributed_revenue` on Campaign and Flow objects). Denominator from Adobe Commerce orders index `grand_total`, REST endpoint `GET /rest/V1/orders`.                                                                                                                                                                                                                                                                                   |
| **VAT / tax treatment**                                | **Tax-inclusive on both sides.** `grand_total` includes tax; Klaviyo's `attributed_revenue` reflects what the customer paid (the order total at attribution event time). Apples-to-apples by default. UK VAT-inclusive merchants should not see a tax-induced bias.                                                                                                                                                                                                                   |
| **Shipping inclusion**                                 | **Included on both sides.** `grand_total` includes shipping; ESP attribution captures the order total which already includes shipping.                                                                                                                                                                                                                                                                                                                                                |
| **Discounts**                                          | Already deducted, both sides. A heavy discount campaign attributed to an email flow shows up at the post-promo value here.                                                                                                                                                                                                                                                                                                                                                            |
| **Credit Memo refund treatment**                       | **NOT subtracted on either side.** Adobe Commerce `grand_total` doesn't change after a Credit Memo (refund lives on a separate document). Klaviyo's `attributed_revenue` similarly doesn't retroactively reduce attribution after a refund. Both sides are gross of refunds, so the *ratio* is honest. To see net-of-refund email share, divide *Net Email Revenue* by *Net Adobe Revenue* manually using [Credit Memo Total](/nerve-centre/adobe_commerce/credit_memo_total).        |
| **`state` machine inclusion**                          | **All states included on the Adobe denominator.** That covers `new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, `payment_review`. Klaviyo only attributes orders that fired a `Placed Order` event, which typically means the order reached at least `processing`. So the numerator excludes most `pending_payment` while the denominator includes them, this can suppress the ratio by 2-5% for stores with significant gateway-callback failures. |
| **`pending_payment` quirk**                            | The asymmetric treatment described above is the single biggest reason this card under-reads versus a "pure" Klaviyo > Dashboard percentage. If your store has high `pending_payment` volume, expect this card to read 2-5% lower than Klaviyo's own attribution figure.                                                                                                                                                                                                               |
| **Multi-currency `grand_total` vs `base_grand_total`** | Numerator and denominator both use display currency (`grand_total` here, Klaviyo's order\_total). For multi-region stores, the *ratio* is approximately FX-neutral as long as email-driven revenue and total revenue share the same currency mix. If your email programme is heavily UK-focused but US is your biggest market, the ratio is biased.                                                                                                                                   |
| **Store View scope (`store_id`)**                      | **All Store Views summed on the denominator.** Klaviyo numerators depend on which Klaviyo accounts are connected, most merchants run one Klaviyo per store-region, so a UK Klaviyo connected against a global Adobe denominator will under-report. Best practice: connect the same scope on both sides (per-region Klaviyo + per-Store-View Adobe filter).                                                                                                                            |
| **Time window**                                        | `30D` (rolling 30-day)                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Alert trigger**                                      | `<8% (email programme under-performing)`                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Roles**                                              | owner, marketing, finance                                                                                                                                                                                                                                                                                                                                                                                                                                                             |

## Calculation

```
SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views, connected to Klaviyo for the consumer programme. The 30-day window covers 14 Mar 26 to 12 Apr 26.

| Source                                               | Value                            |
| ---------------------------------------------------- | -------------------------------- |
| Adobe `grand_total` (US Store View, USD)             | \$272,320                        |
| Adobe `grand_total` (UK Store View, GBP)             | £80,784 (≈ \$101,000 indicative) |
| Adobe `grand_total` (B2B portal, USD)                | \$58,220                         |
| Adobe `pending_payment` value (across views)         | \$12,168                         |
| **Adobe Total Revenue (denominator)**                | **\~\$443,708 indicative**       |
| Klaviyo email-attributed revenue (US programme, USD) | \$46,200                         |
| Klaviyo email-attributed revenue (UK programme, GBP) | £14,400 (≈ \$18,000 indicative)  |
| **Total email-attributed (numerator)**               | **\~\$64,200 indicative**        |
| **This card**                                        | **\~14.5%**                      |

What this is telling the merchant:

1. **14.5% sits comfortably in the 15-25% healthy band** (just below). The email programme is working but has room to grow. The alert threshold is 8% so no fire.
2. **The B2B portal contributes \$58,220 to the denominator but zero to the numerator** because B2B accounts don't get the consumer email campaigns. This drags the ratio down by \~2 percentage points. **For a fair "DTC email share" view, exclude `store_id = 3` from the Adobe denominator.** With B2B excluded the ratio jumps to 16.7%.
3. **`pending_payment` orders (\$12,168) are in the denominator but typically not in Klaviyo's numerator** (Klaviyo fires on `Placed Order` which usually requires the gateway to have completed). This costs the ratio another \~0.4 percentage points. Real, comparable email share is closer to 17.1%.
4. **The UK programme is under-indexed.** UK email revenue ÷ UK Adobe revenue = 17.8% but US is 17.0%, the UK programme is performing slightly better despite a smaller list. Investigate why (probably better segmentation; maybe steal the playbook for US).
5. **vs prior 30 days the share dropped from 16.0% to 14.5%.** Investigate: did Adobe Total Revenue rise on a non-email channel (paid social, organic, retail)? Did Klaviyo open rates fall (deliverability issue)? Did UTM tagging change recently? See the FAQ for the diagnostic order.

## Sibling cards merchants should reference together

This is a cross-platform ratio; pair with both halves to investigate movement:

| Card                                                                                                    | Why pair it with Email Revenue Share                                                                                                                              |
| ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                                   | The denominator. If revenue rose on paid ads while email stayed flat, the share drops without the email programme actually weakening.                             |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)                | A `pending_payment` spike inflates the denominator but not the numerator, suppressing this card. Cross-check before declaring email "broken".                     |
| [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id)                               | If your B2B Store View grew this period, the ratio drops (B2B doesn't get consumer email). Filter B2B out for a fair DTC-only view.                               |
| [Credit Memo Total](/nerve-centre/adobe_commerce/credit_memo_total)                                     | Both sides are gross of refunds. A refund-heavy month leaves the headline unchanged but cash flow worse, this card doesn't capture that.                          |
| [`klaviyo.email_attributed_revenue`](/nerve-centre/klaviyo/email_attributed_revenue)                    | The numerator card on its own. Movement here without movement on the share card means the denominator (Adobe) moved equally, the email programme is keeping pace. |
| [`klaviyo.email_open_rate`](/nerve-centre/klaviyo/email_open_rate)                                      | Falling open rates precede falling email revenue by 4-6 weeks (deliverability decay). Watch this for the early signal.                                            |
| [`klaviyo.email_unsubscribe_rate`](/nerve-centre/klaviyo/email_unsubscribe_rate)                        | Sudden unsubscribe spikes shrink the addressable list.                                                                                                            |
| [`google_analytics.ga_revenue_by_channel`](/nerve-centre/kpi-cards/google-analytics/revenue-by-channel) | GA4's email channel attribution as a sanity check. Should sit within 20% of this card; bigger gaps suggest UTM/tagging mismatch.                                  |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

Adobe Commerce doesn't natively track email-attribution. The closest cross-checks for the *denominator* of this ratio:

> **Reports > Sales > Orders** (or **Reports > Sales** in 2.4.6+). Set the same 30-day window, scope to *All Store Views*, Status filter "All Orders". The Total Revenue column is the denominator. Cross-check this against [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue).

Other Adobe Commerce Admin views that *look* like email-attribution but aren't:

* **Marketing > Newsletter Subscribers**: Adobe Commerce's built-in newsletter list, doesn't track campaign-level revenue attribution.
* **Marketing > Email Reminder Rules**: cart-abandonment email rules, not the same as ESP campaign attribution.
* **Reports > Marketing > Newsletter Problem Reports**: deliverability errors, not revenue.
* **Reports > Sales > Coupons**: revenue from orders that used a coupon code; partially overlaps email but not equivalent (paid-ads emails also use codes).
* **Customers > Now Online**: irrelevant.

**Why our number may legitimately differ from Klaviyo's own dashboard email-share:**

| Reason                                                                                                                                                                                                                                     | Direction of divergence                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------- |
| **Time-zone**. Adobe Commerce stores `created_at` in server local time (configurable per Store View). Klaviyo attributes in UTC. The 30-day window endpoints will sit at different real-world cutoffs.                                     | ±1 day's data at the boundary                       |
| **Currency**. Klaviyo's dashboard typically shows attributed revenue in the connected store's reporting currency (FX-converted). This card sums `grand_total` without FX. Material for international merchants with multi-currency stores. | Material for multi-currency stores                  |
| **Store View scope**. Klaviyo connects per-store; Adobe denominator sums all Store Views. A US-Klaviyo on a multi-Store-View Adobe merchant will under-report this card by the share that non-US Store Views contribute.                   | Vortex IQ ratio lower than Klaviyo's per-store view |
| **`pending_payment` asymmetry**. Adobe denominator includes `pending_payment` orders; Klaviyo numerator typically doesn't (no `Placed Order` event for orders that never completed).                                                       | Vortex IQ ratio 2-5% lower than Klaviyo's           |
| **`canceled` asymmetry**. Adobe denominator includes `canceled`; Klaviyo's `Placed Order` fires before cancellation, so most canceled orders are in both numerator and denominator. Cancellation-heavy stores see this balance out.        | Usually no divergence                               |
| **Attribution window**. Klaviyo's default attribution window is 5 days (click) or 1 day (open). Orders within that window of an email engagement are credited. Different ESPs use different windows; Dotdigital is 30 days for clicks.     | Material if window setting differs                  |
| **List exclusions**. If Klaviyo's data feed is filtered (e.g. only campaign-attributed, not flow-attributed) the numerator under-reports. Always include both campaigns and flows for a true email-share read.                             | Vortex IQ ratio lower if flows excluded             |
| **API rate-limit gaps during sync**. Adobe REST has request quotas; if the indexer throttled during the recent run, the latest day's denominator may be incomplete.                                                                        | Self-resolves at next sync                          |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

This card *is* a cross-connector reconciliation. The honest read is:

| Pair                                                                                                         | Expected relationship                     | What divergence tells you                                                                                                                                         |
| ------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Klaviyo `attributed_revenue` ÷ Adobe `grand_total` (this card) vs Klaviyo Dashboard's "Revenue from Email" % | Should match within 2-5 percentage points | Bigger gaps mean: (1) different attribution-window settings, (2) one side is filtering Store View, (3) `pending_payment` asymmetry on a high-fail store.          |
| GA4 channel report Email % vs this card                                                                      | Should sit within 10-20% of each other    | GA4 attribution uses click-tracked sessions; Klaviyo uses email-engagement events. Different lenses on the same purchases. Use both, neither is the single truth. |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume)                          | Doesn't reconcile directly                | Stripe doesn't see channel; useful only for sanity-checking the denominator.                                                                                      |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same cross-platform concept exists on other commerce connectors. This is **not a reconciliation**; your Adobe Commerce store doesn't have a parallel Shopify or BigCommerce store. These cross-links exist so agencies running multi-platform client books can navigate equivalent metrics across the docs.

  * [`shopify.shopify_xc_email_revenue_share`](/nerve-centre/shopify/shopify_xc_email_revenue_share)
  * [`bigcommerce.bc_xc_email_revenue_share`](/nerve-centre/bigcommerce/bc_xc_email_revenue_share)
</details>

## Known limitations / merchant FAQs

**My Klaviyo dashboard says 22% but this card says 14.5%, why the gap?**
Most common cause is denominator scope mismatch. Klaviyo's "% of revenue from email" uses the orders Klaviyo *sees* as the denominator, which is whatever's flowing into Klaviyo via the Adobe Commerce > Klaviyo integration. That's typically only the consumer Store Views, not B2B portals or marketplace channels. This card uses Adobe Commerce Total Revenue across *every* Store View. To match Klaviyo's view, exclude the B2B `store_id` from the Adobe denominator. Second-most-common cause: the `pending_payment` asymmetry described in the TLDR.

**My finance team says email revenue is lower than this card shows, why?**
Both sides are gross of Credit Memos. A refund-heavy month (returns season for apparel, electronics returns after Christmas) leaves email *attributed* revenue unchanged but cash flow worse. Pair with [Credit Memo Total](/nerve-centre/adobe_commerce/credit_memo_total) for the net view. Finance is correct, accounting-wise; this card is correct, attribution-wise. Both are valid for different jobs.

**What's the difference between `state` and `status` and does it affect this card?**
`state` is the system-level lifecycle (8 fixed values: `new`, `pending_payment`, `processing`, `complete`, `closed`, `canceled`, `holded`, `payment_review`). `status` is a configurable, user-facing label. The denominator (Adobe `grand_total`) is summed across all states, so renamed statuses are irrelevant. The numerator (Klaviyo's attribution) typically only fires on `Placed Order` events, which usually means `state >= processing`. This asymmetry is the chief cause of the card under-reading vs Klaviyo's own dashboard.

**Why does the alert fire below 8% rather than below 15%?**
The 15-25% band is the "healthy DTC" target, but real merchants take time to get there. The alert at \<8% is the *broken* threshold, either email is genuinely under-performing (list health, deliverability) or attribution is broken (UTMs missing, Klaviyo connection broken, click-tracking off). 8% to 15% is a coaching range, not an alarm range; we surface the gap on the card without firing.

**My multi-store Adobe Commerce, can I see per-Store-View email share?**
Not on this card directly. The denominator sums all Store Views; the numerator depends on which Klaviyo accounts are connected. Most stable read: connect one Klaviyo per region, filter the Adobe denominator by the matching `store_id`, and read each region separately. A per-region card variant is on the roadmap.

**Why doesn't Adobe Commerce dashboard show email share?**
Adobe Commerce's native marketing reporting is limited to its own newsletter feature and coupon-code reports, neither of which is real campaign-level attribution. For email-share you need Klaviyo, Dotdigital, Mailchimp, or another ESP with click tracking. This is a category Adobe Commerce expects you to solve via integration, not native.

**My Stripe revenue and email-attributed revenue don't match, expected?**
Yes, completely expected. Stripe sees *successful charges*, not channel attribution. Stripe doesn't know whether an order came from email, paid social, or organic search. Stripe is the right source for "did the money clear?", Klaviyo is the right source for "what channel brought them?". Don't try to reconcile these directly.

**Why doesn't Google Analytics email channel match this card?**
GA4's email channel attribution depends on UTM tags on email links and last-non-direct-click attribution. Klaviyo's attribution depends on email-engagement events tracked in its own pixel. Different lenses, different rules. Both miss different things, GA4 misses ad-blocked sessions, Klaviyo misses customers who don't open emails but still buy after seeing them. Use both as triangulation, not as a single truth.

**My multi-currency Adobe Commerce, does this card work?**
Approximately. Both sides use display currency, so the *ratio* is FX-neutral as long as the email numerator and the total denominator share the same currency mix. If your email programme is heavily UK-focused but US is your biggest revenue market, the ratio will lag the actual UK email performance. Best practice: filter both sides to the same Store View for region-specific reads.

***

### Tracked live in Vortex IQ Nerve Centre

*Email-Attributed Revenue Share* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Financial Status Breakdown, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/financial-status-breakdown

Financial Status Breakdown for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Distribution of orders by financial status (`status` field). Adobe Commerce uses configurable status labels layered on top of the `state` machine; merchants commonly extend the default list with custom statuses (e.g. "Awaiting Wire Transfer", "Net-30 Pending", "Sales Approved"). The card surfaces the active distribution so finance and operations can audit the workflow.

|                                                        |                                                                                                                                                                     |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `COUNT(orders) GROUP BY status` over the trailing 30 days, with revenue (`SUM(grand_total)`) per status. Returns the status distribution as count and dollar share. |
| **API field**                                          | `status` (configurable label) and `state` (canonical lifecycle) from `GET /rest/V1/orders`.                                                                         |
| **VAT / tax treatment**                                | n/a for the count; revenue series uses `grand_total` (tax-inclusive on B2C).                                                                                        |
| **Shipping inclusion**                                 | Included via `grand_total`.                                                                                                                                         |
| **Discounts**                                          | Deducted via `grand_total`.                                                                                                                                         |
| **Credit Memo refund treatment**                       | An order can have a custom status like "Partially Refunded" if the merchant configured it; the card sees whatever label is current.                                 |
| **`state` machine inclusion**                          | All states. The card distinguishes status from state explicitly, surfacing the mapping.                                                                             |
| **`pending_payment` quirk**                            | A `pending_payment` state may have a custom status like "Awaiting Bank Wire" or "Net-30 PO Submitted"; the card preserves the custom label.                         |
| **Multi-currency `grand_total` vs `base_grand_total`** | Revenue uses `base_grand_total`.                                                                                                                                    |
| **Store View scope (`store_id`)**                      | All Store Views; per-Store-View variants useful when status workflows differ by region.                                                                             |
| **Time window**                                        | `30D`                                                                                                                                                               |
| **Alert trigger**                                      | None by default.                                                                                                                                                    |
| **Roles**                                              | owner, operations                                                                                                                                                   |

## Calculation

```
GROUP BY status
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B-heavy industrial supply distributor on Adobe Commerce 2.4.6. Custom statuses configured per the merchant's workflow. 30-day window ending Monday 4 May 26.

**Status distribution:**

| Status (custom)         | State (canonical) | Order count | Revenue         | % of revenue |
| ----------------------- | ----------------- | ----------- | --------------- | ------------ |
| Sales Approved          | processing        | 412         | \$310,000       | 31%          |
| Awaiting Wire Transfer  | pending\_payment  | 168         | \$124,000       | 12.4%        |
| Net-30 Pending          | pending\_payment  | 72          | \$186,000       | 18.6%        |
| Shipped                 | complete          | 1,820       | \$282,000       | 28.2%        |
| Closed                  | closed            | 246         | \$42,000        | 4.2%         |
| Canceled                | canceled          | 88          | \$12,000        | 1.2%         |
| Holded for Credit Check | holded            | 32          | \$44,000        | 4.4%         |
| **Total**               |                   | **2,838**   | **\$1,000,000** | **100%**     |

What this is telling operations and finance:

1. **Custom workflow visibility.** This merchant has 7 active status labels mapped onto 5 canonical states. The card surfaces both, so operations can audit which custom labels are in use.
2. **31% of revenue is in "Sales Approved" but not yet shipped.** This is the operational pipeline; warehouse should prioritise.
3. **12.4% in "Awaiting Wire Transfer" + 18.6% in "Net-30 Pending"** = 31% of revenue waiting on payment. For B2B distribution this is normal (net-30 invoicing); the merchant's cash-flow forecasts depend on aging this pipeline.
4. **4.4% "Holded for Credit Check"** (\$44k) is the credit-review queue. A back-office task; operations should ensure this doesn't accumulate.
5. **1.2% "Canceled"** is in the healthy range; cross-check [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate) for the trend.
6. **Cross-checking [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)** which shows canonical states only: the same data appears as 4 buckets there (`processing`, `pending_payment`, `complete`/`closed` combined, `canceled`, `holded`). The 7-status custom view here is more useful for operations workflow tracking; the canonical view is more useful for cross-platform comparison.

## Sibling cards merchants should reference together

| Card                                                                                     | Why pair it with Financial Status                                    |
| ---------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) | The canonical-state companion.                                       |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)            | The cancellation slice tracked over time.                            |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                    | The aggregate.                                                       |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                      | The aggregate count.                                                 |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)            | B2B-specific statuses (Net-30) drive much of the distribution.       |
| [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)          | Operational pipeline subset.                                         |
| [`shopify.financial_status`](/nerve-centre/kpi-cards/shopify/financial-status-breakdown) | Cross-platform peer (Shopify uses `paid`/`pending`/`refunded` etc.). |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Sales > Orders** with the Status filter shows per-status counts. The grid total updates as filters apply.

> **Stores > Configuration > Sales > Sales > Order Status** lists all configured statuses and their state mappings.

> **Reports > Sales > Orders** with date range and grouping by status (Adobe Commerce 2.4.4+).

For workflow audit:

> **Stores > Order Status** lists every status, custom label, and which state it maps to.

**Why our number may legitimately differ from Admin:**

| Reason                                                                                                                                                                                | Direction of divergence      |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| **Status vs State**. Card surfaces both; Admin grid filter is by status. If a custom status was renamed, the card sees the new label; saved filters or reports may reference the old. | Material if rename is recent |
| **Time-zone**. Admin in Store View timezone; card UTC.                                                                                                                                | Boundary effects             |
| **Currency**. Card uses `base_grand_total` for revenue. Admin uses Store View base.                                                                                                   | Material on multi-currency   |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin live.                                                                                                                       | Negligible                   |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                           | Expected relationship                                       | What divergence tells you                                                                           |
| -------------------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| ERP / accounting status                                        | ERP statuses often less granular than Adobe custom statuses | Map Adobe custom status to ERP at sync time; track which Adobe statuses don't have ERP equivalents. |
| [`stripe.stripe_charges`](/nerve-centre/stripe/stripe_charges) | Stripe-paid orders should be in `processing` or later state | Material gap means Stripe-captured but Adobe shows pending; webhook callback issue.                 |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.financial_status`](/nerve-centre/kpi-cards/shopify/financial-status-breakdown)
  * [`bigcommerce.financial_status`](/nerve-centre/kpi-cards/bigcommerce/financial-status-breakdown)
</details>

## Known limitations / merchant FAQs

**What's the difference between status and state in Adobe Commerce?**
`state` is the canonical 8-value lifecycle (new, pending\_payment, processing, complete, closed, canceled, holded, payment\_review). `status` is a configurable label that maps to a state. A merchant can have 20 custom statuses ("Sales Approved", "Awaiting Wire", "Pick Started", "Quality Check") all mapped to `state = processing`. The card surfaces both.

**Adobe Commerce vs Magento Open Source: difference?**
Both editions have configurable status. Open Source merchants typically have fewer custom statuses (no built-in B2B workflows); Adobe Commerce paid edition's B2B Companies module may add approval-flow statuses (Awaiting Approval, Approved, Rejected).

**My status names look weird, why?**
The card preserves whatever the merchant has configured in Stores > Configuration > Sales > Order Status. Custom names persist; abbreviations and historical labels appear here.

**Why are pending\_payment orders worth tracking?**
On B2B-heavy stores they represent net-30 PO pipeline (genuine future revenue). On consumer stores they may indicate gateway issues. The financial\_status card lets you distinguish: a B2B-tagged custom status like "Net-30 Pending" is healthy pipeline; a status like "Stripe Failed" sitting in pending\_payment is a gateway problem.

**My multi-store, can statuses differ per Store View?**
Adobe Commerce statuses are global, not per-Store-View. A status defined for the consumer Store View applies on all. For per-Store-View routing, use Customer Group filtering on rules instead.

**A custom status was renamed; do historical records update?**
Adobe Commerce status changes apply going forward. Historical orders keep the label they had at order time. The card sees current labels, so a rename creates a brief "two labels for the same state" period. Most stabilises within 7-14 days.

**Why do `complete` and `closed` look similar?**
`complete` = order shipped and invoiced; `closed` = the merchant has closed the order (typically because it's fully refunded or no further action expected). On many stores they look similar; on stores using Adobe RMA module, `closed` may dominate post-RMA.

**Why does the card include cancelled orders in the distribution but other cards exclude?**
This card is auditing the workflow distribution; cancellations are part of that. Other cards (Total Revenue, AOV) exclude cancellations because they're not real revenue.

***

### Tracked live in Vortex IQ Nerve Centre

*Financial Status Breakdown* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Fulfillment Rate, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate

Fulfillment Rate for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Percentage of orders that progressed to `state = complete` within the merchant's defined SLA. Adobe Commerce's `complete` state means "shipped and invoiced"; the rate is the operational quality KPI for fulfillment. Below 92% is the industry-baseline alert; below 88% indicates structural issues (3PL queue depth, integration failures, persistent staffing gaps).

|                                                        |                                                                                                                                                                                                                                                                                                                             |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `COUNT(orders where state = complete AND fulfilled_within_SLA) / COUNT(orders eligible for fulfillment)`. The denominator excludes `pending_payment` (SLA hasn't started) and `canceled` (no fulfillment expected). The numerator counts orders that reached `complete` within the configured SLA hours of payment capture. |
| **API field**                                          | `state`, `created_at`, `updated_at` from `GET /rest/V1/orders`.                                                                                                                                                                                                                                                             |
| **VAT / tax treatment**                                | n/a, count-and-time metric.                                                                                                                                                                                                                                                                                                 |
| **Shipping inclusion**                                 | n/a.                                                                                                                                                                                                                                                                                                                        |
| **Discounts**                                          | n/a.                                                                                                                                                                                                                                                                                                                        |
| **Credit Memo refund treatment**                       | An order shipped on time then later refunded still counts as "fulfilled within SLA".                                                                                                                                                                                                                                        |
| **`state` machine inclusion**                          | Numerator: `complete` within SLA. Denominator: orders eligible for fulfillment (paid, not cancelled, not deliberately held).                                                                                                                                                                                                |
| **`pending_payment` quirk**                            | Excluded from denominator (SLA clock hasn't started).                                                                                                                                                                                                                                                                       |
| **`holded` quirk**                                     | Excluded from denominator (operations deliberately paused; SLA pauses with it).                                                                                                                                                                                                                                             |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a.                                                                                                                                                                                                                                                                                                                        |
| **Store View scope (`store_id`)**                      | All Store Views; per-Store-View variants useful when warehouses serve different regions.                                                                                                                                                                                                                                    |
| **Time window**                                        | `30D vsP`.                                                                                                                                                                                                                                                                                                                  |
| **Alert trigger**                                      | `<92% (industry baseline)`.                                                                                                                                                                                                                                                                                                 |
| **Sentiment key**                                      | `fulfillment_rate`                                                                                                                                                                                                                                                                                                          |
| **Roles**                                              | owner, operations                                                                                                                                                                                                                                                                                                           |

## Calculation

```
COUNT(state=complete) / COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A nutritional supplements brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views. SLA: 48h consumer, 72h B2B. 30-day window ending Monday 4 May 26.

**Fulfillment rate by Store View:**

| Stream      | Eligible orders | Fulfilled within SLA | Rate      |
| ----------- | --------------- | -------------------- | --------- |
| US consumer | 2,610           | 2,486                | 95.2%     |
| UK consumer | 2,040           | 1,849                | 90.6%     |
| B2B portal  | 1,420           | 1,398                | 98.5%     |
| **Blended** | **6,070**       | **5,733**            | **94.4%** |

**Vs prior 30-day:** 94.4% current vs 95.7% prior = -1.3 pts.

What this is telling operations:

1. **Blended 94.4%** is just above the 92% baseline, mid-pack performance. Best-in-class is 96%+.
2. **UK at 90.6%** is below the alert threshold. Worth investigating: cross-check [Fulfilment Over Time](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate-over-time) for the UK series specifically. The UK staffing dip mentioned in that worked example (5 days in late April) explains the drop.
3. **B2B at 98.5%** is best-in-class because the in-house HQ team prioritises B2B and their SLA is more generous (72h vs 48h consumer).
4. **The 1.3 pt blended decline** is driven entirely by the UK Store View; US and B2B are stable. Targeted action on the UK warehouse, not blanket changes.
5. **Operational implications**: roughly 3.4% of orders breached SLA (337 of 6,070). Customer service can expect \~340 enquiries-per-month from these customers (industry typical: 70 to 100% of late-shipment customers contact support).
6. **Action**: address UK warehouse staffing-flex; weekly review with Huboo to ensure forecast-vs-actual reconciliation; set per-Store-View alerting to catch UK-specific dips before blended rate drags.

The point: a single number (94.4%) across multiple Store Views obscures region-specific issues. Per-Store-View alerting and decomposition is essential for multi-warehouse Adobe Commerce stores.

## Sibling cards merchants should reference together

| Card                                                                                      | Why pair it with Fulfilment Rate    |
| ----------------------------------------------------------------------------------------- | ----------------------------------- |
| [Fulfilment Over Time](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate-over-time) | Trend chart.                        |
| [Fulfilment Delay Alert](/nerve-centre/kpi-cards/adobe-commerce/fulfilment-delay-alert)   | Real-time breach alerting.          |
| [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)           | Current pipeline.                   |
| [Fulfillment Breakdown](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-status)        | State distribution.                 |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                       | Volume context.                     |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                         | Lagging effect of breaches.         |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)             | Customer-cancel response to delays. |
| [`shopify.fulfillment_rate`](/nerve-centre/kpi-cards/shopify/fulfillment-rate)            | Cross-platform peer.                |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Shipping** for shipment counts; manual SLA-breach computation requires per-order time-since-payment.

> **Sales > Orders** with state filter; manual export and analysis for SLA breach detection.

> **Sales > Shipments** lists every shipment created in the period.

**Why our number may legitimately differ from a manual count:**

| Reason                                                                                                             | Direction of divergence                 |
| ------------------------------------------------------------------------------------------------------------------ | --------------------------------------- |
| **SLA threshold**. Card uses configurable threshold (default 48h/72h). Different thresholds yield different rates. | Material if thresholds differ           |
| **Time-zone**. Admin in Store View timezone; card UTC.                                                             | Negligible at 30D                       |
| **`pending_payment` exclusion**. Card excludes from denominator.                                                   | Card rate higher                        |
| **`holded` exclusion**. Card excludes from denominator.                                                            | Card rate higher                        |
| **Partial shipments**. Card treats any shipment as fulfillment-started.                                            | Card rate higher than strict definition |
| **Sync lag**. Card uses OpenSearch sync; Admin live.                                                               | Negligible                              |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                         | Expected relationship                    | What divergence tells you                                                    |
| ---------------------------- | ---------------------------------------- | ---------------------------------------------------------------------------- |
| 3PL on-time-shipment reports | Should align within SLA-definition match | Material divergence indicates definition mismatch or off-platform shipments. |
| Carrier API tracking         | First scan ≈ Adobe shipment-create       | Lag indicates carrier handover delay.                                        |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.fulfillment_rate`](/nerve-centre/kpi-cards/shopify/fulfillment-rate)
  * [`bigcommerce.fulfillment_rate`](/nerve-centre/kpi-cards/bigcommerce/fulfillment-rate)
</details>

## Known limitations / merchant FAQs

**My fulfillment rate is 88%, is that bad?**
Below the 92% industry baseline, yes. Most likely cause: the SLA is too tight for current operational capacity, or there's a structural issue (3PL queue depth, integration). Cross-check with [Fulfilment Over Time](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate-over-time) for the trend (declining or stable?) and [Fulfilment Delay Alert](/nerve-centre/kpi-cards/adobe-commerce/fulfilment-delay-alert) for current breaches.

**Adobe Commerce vs Magento Open Source: difference?**
None at the calculation. Both editions have identical state machine.

**My multi-store, can I see per-Store-View rates?**
Yes, configure per-Store-View variants. Strongly recommended for multi-warehouse operations.

**B2B is on a 72h SLA but consumer on 48h, can I configure both?**
Yes, per-Store-View thresholds. Most B2B portal Store Views configure 72h or 5-day SLA; consumer Store Views 48h or 24h. The card respects whatever you configure.

**Why exclude `holded` from the denominator?**
Adobe's `holded` state is "operations paused this order" (fraud review, B2B credit check, custom-make awaiting design). The SLA should pause while held; counting them as breach would penalise legitimate ops actions.

**Why exclude `pending_payment`?**
SLA only starts when payment captures. A `pending_payment` order is still in the customer's hands (or AP's hands). Including would distort the rate.

**My 3PL says they ship 99% within 48h but the card shows 91%, why?**
Likely SLA-definition difference. The 3PL measures from "order received in 3PL queue" to "shipment despatched"; the card measures from "Adobe payment capture" to "shipment created". The Adobe-to-3PL handover (typically 1-4 hours) is included in the card but not in the 3PL metric.

**Why does the card consider partial shipments as fulfilled?**
Default behaviour: any shipment for an order moves it to fulfillment-started. The customer received goods; the SLA is functionally met. For strict "all items shipped" measurement, configure tighter. The default is operationally pragmatic.

**Why is fulfillment rate falling but customer service tickets are flat?**
Customers don't complain on day 3; they complain on day 5 to 7. Tickets lag rate by \~5 days. If rate is falling now, ticket volume rises in a week or two unless you intervene proactively.

***

### Tracked live in Vortex IQ Nerve Centre

*Fulfillment Rate* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Fulfillment Rate Over Time, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate-over-time

Fulfillment Rate Over Time for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Daily fulfillment rate over trailing 90 days, expressed as % of orders shipped within the merchant's promised SLA. The trend chart for [Fulfilment Rate](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate). Captures multi-week patterns (3PL queue depth, holiday-season backlog, seasonal staffing changes) that point-in-time fulfillment metrics miss.

|                                                        |                                                                                                                                                                                                                                                                  |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | Per day: `COUNT(orders shipped within SLA hours of payment) / COUNT(orders that should have shipped that day)`. SLA is configurable per merchant (default 48h consumer, 72h B2B). The chart is the percentage series; companion absolute count series available. |
| **API field**                                          | `state`, `created_at`, `updated_at` from `GET /rest/V1/orders`; shipment existence via shipment index.                                                                                                                                                           |
| **VAT / tax treatment**                                | n/a, time-and-count metric.                                                                                                                                                                                                                                      |
| **Shipping inclusion**                                 | n/a.                                                                                                                                                                                                                                                             |
| **Discounts**                                          | n/a.                                                                                                                                                                                                                                                             |
| **Credit Memo refund treatment**                       | An order shipped within SLA then later refunded still counts as "shipped on time".                                                                                                                                                                               |
| **`state` machine inclusion**                          | `processing` and beyond count toward the denominator; orders with at least one shipment count toward the numerator.                                                                                                                                              |
| **`pending_payment` quirk**                            | Excluded; SLA clock only starts when payment captured.                                                                                                                                                                                                           |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a.                                                                                                                                                                                                                                                             |
| **Store View scope (`store_id`)**                      | All Store Views; per-Store-View overlays useful when warehouses serve different regions independently.                                                                                                                                                           |
| **Time window**                                        | `90D` daily granularity.                                                                                                                                                                                                                                         |
| **Alert trigger**                                      | None by default; pair with [Fulfilment Rate](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate) for alerts.                                                                                                                                                |
| **Roles**                                              | owner, operations                                                                                                                                                                                                                                                |

## Calculation

```
DATE_HISTOGRAM rate(state=complete)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A nutritional supplements brand on Adobe Commerce 2.4.6, US ShipBob and UK Huboo 3PLs, B2B in-house fulfillment from HQ. SLA: 48h consumer, 72h B2B. 90-day window ending Monday 4 May 26.

**90-day fulfillment overview:**

| Metric                     | Value                               |
| -------------------------- | ----------------------------------- |
| Average daily on-time rate | 94.2%                               |
| Standard deviation         | 3.4 pts                             |
| Lowest day on-time rate    | 78% (single bad day, Friday 22 Apr) |
| Highest day on-time rate   | 99% (typical Tuesday)               |
| Days below 90% threshold   | 9 of 90                             |

**Notable dips in the 90-day series:**

| Period                 | Median rate | Cause                                            |
| ---------------------- | ----------- | ------------------------------------------------ |
| 18-22 Apr 26 (5 days)  | 84%         | UK warehouse staffing dip (packer absent)        |
| 5-7 Mar 26 (3 days)    | 82%         | US warehouse stock-recount disruption            |
| 12 Feb 26 (single day) | 73%         | UPS pickup truck delay; backlog cleared next day |

What this is telling operations:

1. **94.2% average is in the healthy range.** Best-in-class is 96%+; below 90% sustained needs intervention.
2. **The 9 below-90% days cluster around 3 incidents**, not random variance. Each had an identifiable operational cause.
3. **The 18-22 Apr UK staffing dip** is the single largest issue; 5 days at 84% means roughly 16% of orders breached SLA across that week. Cross-check with [Fulfilment Delay Alert](/nerve-centre/kpi-cards/adobe-commerce/fulfilment-delay-alert) firings for that period.
4. **The Mar 5-7 stock-recount disruption** is a known operational cost; if recounts happen quarterly, the fulfillment dip is predictable. Communicate proactively to customers in advance to manage expectations.
5. **The 12 Feb single-day dip (73%)** was a pure carrier issue (UPS pickup missed), self-resolved next day. Acceptable, no systemic action needed.
6. **The 7-day moving average shows a slight upward trend** from 93.8% (12 weeks ago) to 94.6% (latest week). Operational-maturity gain, possibly from the merchant's recent introduction of pre-pick batching at Huboo.
7. **Action**: review UK warehouse staffing-flex policy (the Apr staffing dip would have been caught earlier if the planner had access to forecast volume); consider proactive customer-comms for known disruption days.

The point: the 90-day chart shows the difference between a single bad day (carrier issue, weather) and a multi-day systemic issue (staffing, integration). The pattern shape determines the operational response.

## Sibling cards merchants should reference together

| Card                                                                                          | Why pair it with Fulfilment Over Time                                               |
| --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| [Fulfilment Rate](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate)                    | Single-period summary.                                                              |
| [Fulfilment Delay Alert](/nerve-centre/kpi-cards/adobe-commerce/fulfilment-delay-alert)       | Real-time alerting for breaches.                                                    |
| [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)               | Current-state pipeline.                                                             |
| [Fulfillment Breakdown](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-status)            | Cross-state distribution.                                                           |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                           | The volume context (a 90% rate on a busy day is more material than on a quiet one). |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                             | Lagging effect; sustained SLA breaches drive refunds.                               |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)                 | Lagging effect on customer-cancels.                                                 |
| [`shopify.fulfillment_over_time`](/nerve-centre/kpi-cards/shopify/fulfillment-rate-over-time) | Cross-platform peer.                                                                |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Shipping** for shipment counts and aggregates. Adobe doesn't natively compute on-time rates; manual computation requires per-order time-since-payment vs SLA.

> **Sales > Orders** with state filter and date range; manual export and analysis for SLA breach detection.

> **Sales > Shipments** lists every shipment created in the period.

**Why our number may legitimately differ from a manual Admin computation:**

| Reason                                                                                                                                                       | Direction of divergence                       |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- |
| **SLA threshold**. Card uses a configurable threshold (default 48h consumer, 72h B2B). Manual analysis using a different threshold gives different results.  | Material if thresholds differ                 |
| **Time-zone**. Admin in Store View timezone; card UTC. Day-bucket assignment can shift by ±1.                                                                | Negligible at 90D                             |
| **`pending_payment` exclusion**. SLA clock only starts at payment capture. Admin export may include pending-state in the count.                              | Card rate higher than naive admin computation |
| **Partial shipments**. Adobe allows partial shipments. Card treats any shipment as fulfillment-started. Stricter SLAs (all items shipped) yield lower rates. | Card rate higher than strict definition       |
| **Sync lag**. Card uses OpenSearch sync; Admin live.                                                                                                         | Negligible at 90D                             |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                         | Expected relationship                        | What divergence tells you                                                                 |
| ---------------------------- | -------------------------------------------- | ----------------------------------------------------------------------------------------- |
| 3PL on-time-shipment reports | Should align within sync lag                 | Material divergence indicates either off-platform shipments or SLA-definition difference. |
| Carrier API tracking         | First-scan timestamp ≈ Adobe shipment-create | Lag indicates carrier handover delay.                                                     |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.fulfillment_over_time`](/nerve-centre/kpi-cards/shopify/fulfillment-rate-over-time)
  * [`bigcommerce.fulfillment_over_time`](/nerve-centre/kpi-cards/bigcommerce/fulfillment-rate-over-time)
</details>

## Known limitations / merchant FAQs

**Why does the chart use 48h consumer SLA, my promise is 24h?**
Configure the manifest to your actual SLA. The 48h default is industry-norm; merchants with same-day or 24h promises should configure tighter. Per-Store-View thresholds are also supported (B2B 72h, consumer 48h, premium 24h on the same merchant).

**Adobe Commerce vs Magento Open Source: difference?**
None at the calculation. Both editions have the shipment entity and state machine.

**My multi-store, can I overlay Store Views on the chart?**
Yes, configure per-Store-View series. Useful when each warehouse serves a specific Store View; per-warehouse trend shows operational health independently.

**A single bad day (carrier issue) tanks my 7-day moving average; how to filter?**
Use the per-cause analysis. The card surfaces the dips; the operational team annotates known causes. The Vortex IQ workspace allows incident annotations against the chart so the dip explanation is preserved.

**Why include `pending_payment` orders in the denominator?**
They're not in the denominator on this card. Only orders that have entered `processing` (paid) count toward the SLA-eligible denominator. `pending_payment` is excluded because SLA hasn't started.

**Why does the on-time rate sometimes spike to 99%+?**
Quiet days (single-digit order count) can show 100% on a single shipment. The 7-day moving average smooths this; raw daily numbers can be volatile.

**Partial shipments confuse the metric, how does the card handle them?**
Default: any shipment for an order moves it to "fulfillment-started" and counts as on-time if within SLA. For stricter "all items shipped" measurement, configure the manifest. The default is operational-pragmatic; the strict view is service-promise-rigorous.

**Why does my customer service team see different SLA breach numbers?**
Customer service usually counts breaches as "customers contacted us about a delay", which understates breach count (most customers don't complain on day 3, only on day 5+). The card counts SLA breaches by definition (over the threshold), regardless of customer notification.

***

### Tracked live in Vortex IQ Nerve Centre

*Fulfillment Rate Over Time* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Fulfillment Status, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/fulfillment-status

Fulfillment Status for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Distribution of orders by fulfillment state (new, processing, complete, closed, holded, etc.). The operational dashboard for warehouse managers and ops leads. Adobe Commerce's `state` machine is the canonical lifecycle; this card decomposes it. The B2B-mixed nature of typical Adobe Commerce stores means `pending_payment` is often a large bucket (net-30 PO pipeline) rather than a problem signal.

|                                                        |                                                                                                                                                                                                                                                         |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `COUNT(orders) GROUP BY state` over the trailing 30 days, with `SUM(grand_total)` per state. Returns the state distribution.                                                                                                                            |
| **API field**                                          | `state` from `GET /rest/V1/orders`.                                                                                                                                                                                                                     |
| **VAT / tax treatment**                                | n/a for the count; revenue uses `grand_total` (tax-inclusive on B2C).                                                                                                                                                                                   |
| **Shipping inclusion**                                 | Included via `grand_total`.                                                                                                                                                                                                                             |
| **Discounts**                                          | Deducted via `grand_total`.                                                                                                                                                                                                                             |
| **Credit Memo refund treatment**                       | Refunded orders typically sit in `closed`; the card reflects the current state.                                                                                                                                                                         |
| **`state` machine inclusion**                          | All 8 canonical states.                                                                                                                                                                                                                                 |
| **`pending_payment` quirk**                            | Surfaced as its own bucket. Important to distinguish "healthy B2B net-30 pipeline" from "broken gateway callback" via cross-checks (does the count and value of `pending_payment` move in step with B2B order growth, or does it spike independently?). |
| **Multi-currency `grand_total` vs `base_grand_total`** | Revenue uses `base_grand_total`.                                                                                                                                                                                                                        |
| **Store View scope (`store_id`)**                      | All Store Views; per-Store-View overlays useful when warehouse ownership is split by region.                                                                                                                                                            |
| **Time window**                                        | `30D`                                                                                                                                                                                                                                                   |
| **Alert trigger**                                      | None by default.                                                                                                                                                                                                                                        |
| **Roles**                                              | owner, operations                                                                                                                                                                                                                                       |

## Calculation

```
GROUP BY state
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B-heavy industrial supply distributor on Adobe Commerce 2.4.6. 30-day window ending Monday 4 May 26.

**State distribution:**

| State            | Count     | Revenue         | % of revenue |
| ---------------- | --------- | --------------- | ------------ |
| new              | 142       | \$42,000        | 4.2%         |
| pending\_payment | 240       | \$310,000       | 31.0%        |
| processing       | 412       | \$186,000       | 18.6%        |
| complete         | 1,820     | \$282,000       | 28.2%        |
| closed           | 246       | \$42,000        | 4.2%         |
| canceled         | 88        | \$12,000        | 1.2%         |
| holded           | 32        | \$44,000        | 4.4%         |
| payment\_review  | 24        | \$82,000        | 8.2%         |
| **Total**        | **3,004** | **\$1,000,000** | **100%**     |

What this is telling operations:

1. **31% of revenue (\$310k) sits in `pending_payment`.** On a B2B-heavy store this is normal: net-30 POs and B2B-sales-approved orders awaiting AP processing. Cross-check the running average; if it's stable at 28-32%, healthy.
2. **18.6% in `processing`** is the warehouse pipeline (paid, not yet shipped).
3. **8.2% in `payment_review`** (\$82k of revenue value) is fraud-review queue. This is unusually high; typical baseline is 1-3%. Investigate: is the fraud-rule sensitivity tuned too tightly?
4. **4.4% in `holded`** is operations-paused orders (credit checks, custom-make awaiting approval).
5. **4.2% in `closed`** at \$42k is post-RMA fully-refunded orders or specially-handled small orders.
6. **1.2% in `canceled`** is in the healthy range.
7. **The `payment_review` flag is the most actionable surprise.** A fraud rule pause-rate of 8% means the rule is rejecting \~7% more orders than benchmark. Either the rule is over-sensitive (reduce sensitivity to recover legitimate orders) or the merchant is genuinely seeing a fraud campaign (validate via per-IP and per-card-BIN review).
8. **Cross-checking [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)**: 1.2% is fine. If the `payment_review` fraction was being auto-cancelled, cancellation rate would be 9%+. The merchant currently leaves them in review (manual ops review), which is conservative but adds operational load.

## Sibling cards merchants should reference together

| Card                                                                                      | Why pair it with Fulfillment Breakdown                            |
| ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)  | The same data, different visualisation.                           |
| [Financial Status](/nerve-centre/kpi-cards/adobe-commerce/financial-status-breakdown)     | The custom-status companion.                                      |
| [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)           | The processing-and-pending pipeline subset.                       |
| [Fulfilment Rate](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate)                | The trailing percentage view.                                     |
| [Fulfilment Over Time](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate-over-time) | The trend view.                                                   |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)             | Cancellation-state slice.                                         |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)             | B2B mix drives `pending_payment` size.                            |
| [`shopify.fulfillment_breakdown`](/nerve-centre/kpi-cards/shopify/fulfillment-status)     | Cross-platform peer (Shopify uses fulfilled/partial/unfulfilled). |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Sales > Orders** with the Status filter shows per-status counts; the State filter (Adobe Commerce 2.4.6+) shows canonical-state counts.

> **Reports > Sales > Orders** with state grouping (newer Adobe versions).

> **Stores > Order Status** to see the configured status-to-state mapping.

For specific state subsets:

> **Sales > Orders** with `state = pending_payment` filter for the AP/gateway pipeline.

> **Sales > Orders** with `state = holded` for the credit-check queue.

> **Sales > Orders** with `state = payment_review` for the fraud review queue.

**Why our number may legitimately differ from Admin:**

| Reason                                                                                                                              | Direction of divergence                            |
| ----------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| **State vs Status**. Card uses `state`; Admin grid filter is by `status`. Custom statuses mapping to the same state aggregate here. | Card buckets fewer than admin custom-status filter |
| **Time-zone**. Admin in Store View timezone; card UTC.                                                                              | Boundary effects                                   |
| **Currency**. Card uses `base_grand_total`.                                                                                         | Material on multi-currency                         |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin live.                                                                     | Negligible                                         |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                           | Expected relationship                                  | What divergence tells you                                                       |
| -------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------- |
| 3PL queue depth                                                | `processing` count ≈ 3PL fulfilment queue              | If 3PL queue is empty but `processing` is high, the integration is failing.     |
| [`stripe.stripe_charges`](/nerve-centre/stripe/stripe_charges) | Stripe-paid orders should sit in `processing` or later | If Stripe captured but Adobe shows `pending_payment`, webhook callback failure. |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.fulfillment_breakdown`](/nerve-centre/kpi-cards/shopify/fulfillment-status)
  * [`bigcommerce.fulfillment_breakdown`](/nerve-centre/kpi-cards/bigcommerce/fulfillment-status)
</details>

## Known limitations / merchant FAQs

**Why is `pending_payment` so big on my store?**
On B2B-heavy stores, net-30 POs sit in `pending_payment` until AP processes the invoice. 20-35% pending is typical. On consumer-only stores, `pending_payment` should be transient (gateway pre-authorisation lasting seconds-to-minutes); a high pending count there indicates webhook callback failures or net-30/wire-transfer routes the merchant should investigate.

**Adobe Commerce vs Magento Open Source: difference?**
None at the calculation. Both editions use the same 8-value `state` enum. Adobe Commerce paid edition's B2B Companies module adds approval-flow lifecycle on top, but the `state` field itself is identical.

**What's the difference between this and Order State Breakdown?**
Same underlying data. This card surfaces it primarily as count and revenue distribution; [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) often adds time-in-state analysis. Use the one that matches your question.

**Why is `payment_review` separate from `processing`?**
`payment_review` is Adobe's fraud-review state; orders sit there awaiting manual review or fraud-rule decision. `processing` is paid-and-greenlit. The distinction matters operationally: warehouse picks `processing` orders; fraud-team handles `payment_review`.

**My multi-store, can I see per-Store-View distribution?**
Yes, configure per-Store-View variants. Useful when one Store View has different fraud rules or B2B-routing.

**Why does `closed` show meaningful revenue?**
Closed orders include refunded orders, post-RMA orders, and orders the merchant manually closed (typically because of refund or special handling). 2-5% revenue share in `closed` is normal.

**The `holded` state has \$44k of revenue, is that money at risk?**
Possibly. `holded` means operations paused the order. If the hold is for credit-check (B2B), the revenue typically converts after AP review (low risk). If for fraud or supplier-stall, the order may eventually cancel. Audit hold reasons by clicking into individual orders.

**Why does this card include cancelled orders?**
Because it's a workflow-distribution view. Other cards (Total Revenue, AOV) exclude cancellations because they're not real revenue, but the workflow card is auditing the lifecycle and cancelled orders are part of it.

***

### Tracked live in Vortex IQ Nerve Centre

*Fulfillment Status* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Adobe Commerce KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/index

Every Adobe Commerce KPI pulse Vortex IQ Nerve Centre tracks: 59 metrics covering revenue, orders, customers, refunds, and more.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adobe-commerce) · [Audit Profile](/nerve-centre/kpi-cards/adobe-commerce/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adobe-commerce/sentiment)**

Vortex IQ Nerve Centre tracks **59** KPI pulses for Adobe Commerce stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves.

The Adobe Commerce (Magento) connector is built for the multi-store, multi-environment B2B + B2C complexity Adobe merchants live in. The **Nerve Centre** tracks 59 KPI pulses for Adobe Commerce stores - including the B2B-specific cards (*B2B Accounts Gone Quiet*, *B2B AOV vs B2C AOV*, *B2B Revenue Share*) that Adobe Analytics doesn't surface natively, plus the cross-platform *Catalogue Drift (Adobe ↔ Amazon)* alert. **Vortex Mind** explains why a B2B account went quiet or why catalogue drift opened up; **Ask Viq™** lets you ask in plain English, scoped per Profile so the B2B and DTC questions stay separate.

| Card                                                                                                          | Metrics type           | Category                        | Chart           |
| ------------------------------------------------------------------------------------------------------------- | ---------------------- | ------------------------------- | --------------- |
| [B2B Accounts Gone Quiet](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet)                     | Key Metrics            | B2B vs B2C                      | alert\_list     |
| [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert)                               | Key Metrics            | Nerve Centre                    | alert\_list     |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                                           | Key Metrics            | Revenue & Growth                | kpi             |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                                         | Key Metrics            | Revenue & Growth                | kpi             |
| [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)                               | Key Metrics            | Order Issues                    | kpi             |
| [Active Ads on Out-of-Stock SKUs](/nerve-centre/kpi-cards/adobe-commerce/active-ads-on-out-of-stock-skus)     | Cross-Platform Metrics | Cross-Platform: Revenue at Risk | alert\_table    |
| [Amazon Revenue Share vs Adobe DTC](/nerve-centre/kpi-cards/adobe-commerce/amazon-revenue-share-vs-adobe-dtc) | Cross-Platform Metrics | Cross-Platform: Revenue at Risk | donut           |
| [Catalogue Drift (Adobe ↔ Amazon)](/nerve-centre/kpi-cards/adobe-commerce/catalogue-drift)                    | Cross-Platform Metrics | Cross-Platform: Revenue at Risk | alert\_table    |
| [Email-Attributed Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/email-attributed-revenue-share)       | Cross-Platform Metrics | Cross-Platform: Revenue at Risk | gauge           |
| [Revenue at Risk (active incidents)](/nerve-centre/kpi-cards/adobe-commerce/revenue-at-risk)                  | Cross-Platform Metrics | Cross-Platform: Revenue at Risk | kpi             |
| [Average Order Value](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                             | Supporting Metrics     | Revenue & Growth                | kpi             |
| [B2B AOV vs B2C AOV](/nerve-centre/kpi-cards/adobe-commerce/b2b-aov-vs-b2c-aov)                               | Supporting Metrics     | B2B vs B2C                      | bar             |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)                                 | Supporting Metrics     | B2B vs B2C                      | donut           |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)                                 | Supporting Metrics     | Refunds & Cancellations         | gauge           |
| [Cancelled Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/cancelled-orders-over-time)               | Supporting Metrics     | Cancellations                   | area            |
| [Cart-Abandonment Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/cart-abandonment-spike-alert)           | Supporting Metrics     | Nerve Centre                    | alert\_list     |
| [Customer Acquisition Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)               | Supporting Metrics     | Trends                          | area            |
| [Customer Churn Risk](/nerve-centre/kpi-cards/adobe-commerce/customer-churn-risk)                             | Supporting Metrics     | Customer Retention              | gauge           |
| [Customer Order Frequency](/nerve-centre/kpi-cards/adobe-commerce/customer-order-frequency)                   | Supporting Metrics     | Customer Retention              | bar             |
| [Customer Spend Segments](/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments)                     | Supporting Metrics     | Customer Insights               | pie             |
| [Customers with Zero Spend](/nerve-centre/kpi-cards/adobe-commerce/customers-with-zero-spend)                 | Supporting Metrics     | Customer Health                 | kpi             |
| [Daily Order Trends](/nerve-centre/kpi-cards/adobe-commerce/daily-order-trends)                               | Supporting Metrics     | Revenue & Growth                | area            |
| [Discount % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue)                           | Supporting Metrics     | Revenue & Growth                | gauge           |
| [Discounts Given Over Time](/nerve-centre/kpi-cards/adobe-commerce/discounts-given-over-time)                 | Supporting Metrics     | Promotions                      | area            |
| [Email Health](/nerve-centre/kpi-cards/adobe-commerce/email-health)                                           | Supporting Metrics     | Customer Data                   | gauge           |
| [Financial Status Breakdown](/nerve-centre/kpi-cards/adobe-commerce/financial-status-breakdown)               | Supporting Metrics     | Operations                      | bar             |
| [Free vs Paid Shipping](/nerve-centre/kpi-cards/adobe-commerce/free-vs-paid-shipping)                         | Supporting Metrics     | Shipping                        | pie             |
| [Fulfillment Rate](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate)                                   | Supporting Metrics     | Fulfillment                     | gauge           |
| [Fulfillment Rate Over Time](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate-over-time)               | Supporting Metrics     | Operations                      | area            |
| [Fulfillment Status](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-status)                               | Supporting Metrics     | Fulfillment                     | pie             |
| [Fulfilment Delay Alert](/nerve-centre/kpi-cards/adobe-commerce/fulfilment-delay-alert)                       | Supporting Metrics     | Nerve Centre                    | alert\_list     |
| [Guest vs Account Orders](/nerve-centre/kpi-cards/adobe-commerce/guest-vs-account-orders)                     | Supporting Metrics     | Customer Insights               | pie             |
| [Line Item Fulfillment Status](/nerve-centre/kpi-cards/adobe-commerce/line-item-fulfillment-status)           | Supporting Metrics     | Operations                      | pie             |
| [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers)                                         | Supporting Metrics     | Customer Insights               | kpi             |
| [Order State Breakdown](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)                         | Supporting Metrics     | Operations                      | bar             |
| [Orders by Country](/nerve-centre/kpi-cards/adobe-commerce/orders-by-country)                                 | Supporting Metrics     | Customer Insights               | bar             |
| [Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/orders-over-time)                                   | Supporting Metrics     | Trends                          | area            |
| [Out-of-Stock Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/out-of-stock-spike-alert)                   | Supporting Metrics     | Nerve Centre                    | alert\_list     |
| [Payment Methods](/nerve-centre/kpi-cards/adobe-commerce/payment-methods)                                     | Supporting Metrics     | Operations                      | pie             |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                                             | Supporting Metrics     | Refunds & Cancellations         | gauge           |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)                                           | Supporting Metrics     | Refunds & Cancellations         | kpi             |
| [Refund-Rate Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/refund-rate-spike-alert)                     | Supporting Metrics     | Nerve Centre                    | alert\_list     |
| [Refunded Orders](/nerve-centre/kpi-cards/adobe-commerce/refunded-orders)                                     | Supporting Metrics     | Refunds & Cancellations         | kpi             |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)                                 | Supporting Metrics     | Refunds                         | area            |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)                           | Supporting Metrics     | Customer Insights               | gauge           |
| [Return Status](/nerve-centre/kpi-cards/adobe-commerce/return-status)                                         | Supporting Metrics     | Returns                         | pie             |
| [Revenue Breakdown](/nerve-centre/kpi-cards/adobe-commerce/revenue-breakdown)                                 | Supporting Metrics     | Finance                         | pie             |
| [Revenue by Day of Week](/nerve-centre/kpi-cards/adobe-commerce/revenue-by-day-of-week)                       | Supporting Metrics     | Revenue Patterns                | bar             |
| [Revenue by Payment Gateway](/nerve-centre/kpi-cards/adobe-commerce/revenue-by-payment-gateway)               | Supporting Metrics     | Finance                         | bar             |
| [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time)                                 | Supporting Metrics     | Trends                          | area            |
| [Shipping Cost as % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/shipping-cost-as-of-revenue)           | Supporting Metrics     | Shipping                        | gauge           |
| [Tax Analysis](/nerve-centre/kpi-cards/adobe-commerce/tax-analysis)                                           | Supporting Metrics     | Finance                         | bar             |
| [Tax Collected Over Time](/nerve-centre/kpi-cards/adobe-commerce/tax-collected-over-time)                     | Supporting Metrics     | Tax                             | area            |
| [Top Refunding Customers](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers)                     | Supporting Metrics     | Returns                         | bar\_horizontal |
| [Total Discount Used](/nerve-centre/kpi-cards/adobe-commerce/total-discount-used)                             | Supporting Metrics     | Revenue & Growth                | kpi             |
| [Total Shipping Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-shipping-revenue)                       | Supporting Metrics     | Revenue & Growth                | kpi             |
| [Total Tax Collected](/nerve-centre/kpi-cards/adobe-commerce/total-tax-collected)                             | Supporting Metrics     | Revenue & Growth                | kpi             |
| [Unique Customers](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)                                   | Supporting Metrics     | Customer Insights               | kpi             |
| [Unverified Email Customers](/nerve-centre/kpi-cards/adobe-commerce/unverified-email-customers)               | Supporting Metrics     | Customer Health                 | kpi             |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector. Replace this block when authored.*


# New Customers, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/new-customers

New Customers for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Number of customers whose first-ever order in the system fell within the 30-day window. The acquisition headline. Pairs with [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate) (retention) and [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend) (cumulative growth).

|                                                                        |                                                                                                                                                                                                                                                                                              |
| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                                     | `CARDINALITY(customer_email WHERE first_ever_order_date IN window)`. The "first\_ever" determination uses the customer's earliest order across all time, not just within the window. A customer who ordered for the first time 18 months ago and then again last week is NOT counted as new. |
| **API field**                                                          | `customer_id`, `customer_email`, `created_at` from `GET /rest/V1/orders`. The "first ever" timestamp is computed by aggregating all orders per customer and taking the minimum `created_at`.                                                                                                 |
| **Why this is the right definition (not "first order in the period")** | A "first order in the period" definition would count anyone who reactivated after dormancy as new, which is misleading. A proper "new customer" is someone who never ordered before, anywhere. Vortex IQ uses this stricter definition.                                                      |
| **B2B Companies**                                                      | A Company entity is "new" if any of its buyers placed the Company's first ever order in the window. So a new Company can be triggered by either a new Company entity in Adobe or by a buyer being added to an existing Company. The card respects the toggle.                                |
| **Guests**                                                             | Aggregated by `customer_email`. A guest who used a new email is counted as new even if they're the same physical person who ordered before with a different email. Source of inflation.                                                                                                      |
| **VAT / tax / shipping / discounts**                                   | n/a, this is a customer count.                                                                                                                                                                                                                                                               |
| **Refunds**                                                            | A new customer who immediately refunded is still counted (they were a customer).                                                                                                                                                                                                             |
| **Cancelled orders**                                                   | Included by default. A customer whose only order was cancelled before capture is still counted; toggle to exclude for "captured-only new customers".                                                                                                                                         |
| **Currency**                                                           | Unitless.                                                                                                                                                                                                                                                                                    |
| **Multi-store scope**                                                  | All Store Views by default. A customer whose first order was on UK and second on US is "new" once (on the UK first-order date). Same email across Store Views is the same customer.                                                                                                          |
| **Time window**                                                        | `30D vsP` (rolling 30-day, compared to prior 30-day window).                                                                                                                                                                                                                                 |
| **Alert trigger**                                                      | None on this card directly. Acquisition is a top-of-funnel target with merchant-specific goals.                                                                                                                                                                                              |
| **Roles**                                                              | owner, marketing                                                                                                                                                                                                                                                                             |

## Calculation

```
CARDINALITY(customer_email WHERE first_order in window)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC apparel merchant on Adobe Commerce 2.4.7. UK base. Period: 14 Apr 26 to 13 May 26.

**New customer aggregates:**

| Slice                                                                              | New customer count | First-order revenue (`grand_total`) |
| ---------------------------------------------------------------------------------- | ------------------ | ----------------------------------- |
| All new customers                                                                  | 1,420              | £218,000                            |
| DTC consumers                                                                      | 1,360              | £164,000                            |
| New B2B Companies (genuinely new entity)                                           | 12                 | £42,000                             |
| New buyers added to existing Companies (counted only if the Company itself is new) | 0 (excluded)       | n/a                                 |
| Welcome-coupon (WELCOME10) redeemed on first order                                 | 1,120              | £128,000                            |
| Acquired via guest checkout                                                        | 480                | £48,000                             |
| Acquired via account-creation checkout                                             | 940                | £170,000                            |

**Comparison to prior 30 days:**

| Window              | New customers | First-order revenue | New CAC implied                |
| ------------------- | ------------- | ------------------- | ------------------------------ |
| 14 Apr to 13 May 26 | 1,420         | £218,000            | (calc against marketing spend) |
| 15 Mar to 13 Apr 26 | 1,180         | £172,000            |                                |
| **Change**          | **+20.3%**    | **+26.7%**          |                                |

**Insight pattern:**

1. **1,420 new customers in 30 days, +20% vs prior.** Strong acquisition. Cross-link with [`google_analytics.ga_new_users`](/nerve-centre/kpi-cards/google-analytics/new-users) for traffic-side context; new customers / new users = checkout-conversion rate among new visitors.
2. **First-order revenue per new customer = £153.** Reasonable for apparel DTC. Compare to LTV target (90-day LTV / new customer count from prior 90 days) for retention economics.
3. **12 new B2B Companies in 30 days** is a healthy B2B acquisition rate. New Companies are typically Sales-led (not self-service); cross-link with the merchant's CRM (Salesforce, HubSpot) to verify rep-attributed accounts.
4. **WELCOME10 redemption rate among new customers = 1,120 / 1,420 = 79%.** High; confirms the welcome flow is reaching most new buyers. The 21% who didn't use WELCOME10 either shopped sale items (where coupons stack disabled) or came in via marketplace channels with their own pricing.
5. **Account-creation cohort has higher first-order revenue (£181 avg)** than guest cohort (£100 avg). Account-creation buyers self-select for higher commitment; they convert better on subsequent emails too. Use this in the acquisition CTAs ("Create account, save £X").
6. **Action queue:** (a) compute new-customer CAC against marketing spend in the period; (b) ensure WELCOME10 doesn't apply to already-discounted SPRING25 orders (margin-stacking); (c) Sales follow-up on the 12 new Companies for white-glove onboarding.

## Sibling cards merchants should reference together

| Card                                                                                        | Why pair it with New Customers                                                |
| ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| [Customer Count](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)                   | Total customers; new is a subset.                                             |
| [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)         | Cumulative customer growth.                                                   |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)         | The retention complement; together they form the acquisition-retention story. |
| [Customer Order Frequency](/nerve-centre/kpi-cards/adobe-commerce/customer-order-frequency) | New customers are mostly in the "1 order" bucket.                             |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                       | First-order revenue is a slice of total.                                      |
| [Total Discount](/nerve-centre/kpi-cards/adobe-commerce/total-discount-used)                | Welcome coupons drive new-customer discount expense.                          |
| [`google_analytics.ga_new_users`](/nerve-centre/kpi-cards/google-analytics/new-users)       | Traffic-side new users; pair to compute new-user-to-new-customer conversion.  |
| [`klaviyo.welcome_flow_signups`](/nerve-centre/klaviyo/welcome_flow_signups)                | Email signup velocity.                                                        |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Customers > All Customers** with "Created At" filter set to the period; count rows. **Note: this counts customer registrations, not first-order placement.** A user can register and never order; this card excludes those. Conversely, a guest order does not register a customer; this card includes guest first-orders.

For a true "first order" view:

> **Sales > Orders** with `Customer Group` filter set to your "first-time" segment if you have one set up in Magento. Otherwise, no native first-order filter exists.

**Why our number may legitimately differ from a manual Admin computation:**

| Reason                                                                                                                                                                                                                                                                                              | Direction of divergence            |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| **Registration vs first-order**. Admin's customer-creation date counts when the customer registered, this card counts when they first ordered. A customer might register today and not order for 6 months; in that case, this card counts them on order day, Admin counts them on registration day. | Different dates                    |
| **Guest customers**. Adobe doesn't create customer records for guests (`customer_id IS NULL`); they don't appear in Customers grid. This card includes them by email.                                                                                                                               | Card higher                        |
| **B2B Company aggregation**. Card optionally aggregates to Company; Admin doesn't.                                                                                                                                                                                                                  | Configuration-dependent            |
| **Time-zone, sync lag**. Standard.                                                                                                                                                                                                                                                                  | Minor                              |
| **Email duplication**. A customer who deleted their account and re-registered with the same email is "old" here (first ever order), but might appear "new" if Admin treats account creation as the start.                                                                                           | Card under-counts re-registrations |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                                  | Expected relationship                                                                        | What divergence tells you                                                                        |
| ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| [`google_analytics.ga_new_users`](/nerve-centre/kpi-cards/google-analytics/new-users) | GA4 new-users count is sessions-based, much higher than this card (most new users don't buy) | Don't reconcile; useful as a funnel ratio (new-users → new-customers conversion).                |
| [`klaviyo.welcome_flow_signups`](/nerve-centre/klaviyo/welcome_flow_signups)          | Klaviyo welcome-flow entrants ≈ this card if every new customer enters the flow              | If Klaviyo lower, the welcome-flow trigger is misconfigured; some new customers aren't entering. |
| [`stripe.stripe_new_customers`](/nerve-centre/stripe/stripe_new_customers)            | Stripe new-customer count for Stripe-paid orders only                                        | Should match Stripe-paid subset of this card.                                                    |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.new_customers`](/nerve-centre/kpi-cards/shopify/new-customers)
  * [`bigcommerce.new_customers`](/nerve-centre/kpi-cards/bigcommerce/new-customers)
</details>

## Known limitations / merchant FAQs

**A customer registered last year but didn't order until this month, are they new?**
Yes. The card counts first-order date, not registration date. The customer's "first ever order" landed in the window, so they're a new customer.

**A customer ordered once 18 months ago and again this month, are they new?**
No. They have prior order history (the 18-month-old order). They are reactivated, not new. To track reactivation, use a separate cohort card; reactivation has different acquisition economics from genuinely-new customers.

**Guest customers using a new email, are they new?**
Yes per the card's logic. The email has no prior order history. Even if the same physical person used a different email before, the card has no way to know. This inflates the new-customer count by 5-15% for most merchants.

**B2B Companies: when is a Company "new"?**
When the Company's first ever order in the system falls within the window. Adobe Commerce can pre-create Company entities (the Sales rep adds the Company; orders come later). The card uses first-order timestamp, not Company-creation timestamp.

**Why doesn't Reports > Customers match?**
Reports > Customers > New Accounts uses registration date. This card uses first-order date. They are different metrics; both useful but not directly comparable.

**Welcome-coupon redemption rate, why isn't it 100%?**
Three causes: (1) some customers shop sale items where coupon-stacking is disabled; (2) some come via marketplaces or B2B portals that bypass the welcome flow; (3) some new customers don't sign up for emails and never see the coupon. 70-85% is healthy.

**Multi-store, can a customer be "new" twice (once per Store View)?**
No. The card aggregates across Store Views by `customer_email`. A customer who first ordered on UK and later on US is "new" once (UK first-order date).

**B2B account ABC has 5 buyers; one new buyer placed first order this month, is the Company "new"?**
Depends on toggle. With Company aggregation: the Company isn't new (it had prior orders from other buyers). Without Company aggregation: the new buyer is new. Most merchants use Company aggregation for B2B context.

**Why is today's new-customer count low?**
Today is incomplete; the day-to-date number is necessarily lower than a full day's count. If the card's headline shows the 30-day rolling, today's contribution is small relative to the window.

**Refunded customers, are they still counted?**
Yes; first-order placement is what matters, refund is a downstream event. A new customer who immediately refunds is still counted as new (and contributes negatively to LTV; this is a fraud-watch signal).

***

### Tracked live in Vortex IQ Nerve Centre

*New Customers* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Orders by Country, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/orders-by-country

Orders by Country for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Distribution of customers and revenue by shipping-address country (ISO-2 country code). Adobe Commerce's multi-store nature makes this a strategic surface: a UK-headquartered merchant who runs separate Store Views for US, UK, EU, and AU sees the country read distinct from per-Store-View aggregations. Country detection uses `shipping_address.country_id`, not IP geolocation. A customer ordering from a UK billing address but shipping to a France hotel for delivery counts as France here.

|                                                        |                                                                                                                                                                                                                                               |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `COUNT(DISTINCT customer_email)` and `SUM(grand_total)` grouped by `shipping_country_id`, over the trailing 30 days. Returns a ranked table by customer count and by revenue contribution.                                                    |
| **API field**                                          | `extension_attributes.shipping_assignments[0].shipping.address.country_id` (ISO-2) and `customer_email` from `GET /rest/V1/orders`.                                                                                                           |
| **VAT / tax treatment**                                | Revenue series uses `grand_total` (tax-inclusive on B2C, often exempt on B2B). Cross-country tax-rate variance creates a slight bias when ranking by revenue: tax-inclusive UK revenue is overstated by \~16.7% vs tax-exempt B2B US revenue. |
| **Shipping inclusion**                                 | Included via `grand_total`. International shipping fees are typically much higher than domestic, biasing international-country revenue upward.                                                                                                |
| **Discounts**                                          | Deducted.                                                                                                                                                                                                                                     |
| **Credit Memo refund treatment**                       | Not subtracted.                                                                                                                                                                                                                               |
| **`state` machine inclusion**                          | All states except `canceled`.                                                                                                                                                                                                                 |
| **`pending_payment` quirk**                            | Included.                                                                                                                                                                                                                                     |
| **Multi-currency `grand_total` vs `base_grand_total`** | Uses `base_grand_total` for cross-country comparison.                                                                                                                                                                                         |
| **Store View scope (`store_id`)**                      | All Store Views; country dimension is independent of Store View. A customer shipping to US on the UK Store View counts as US.                                                                                                                 |
| **Time window**                                        | `30D`                                                                                                                                                                                                                                         |
| **Alert trigger**                                      | None by default.                                                                                                                                                                                                                              |
| **Roles**                                              | owner, marketing                                                                                                                                                                                                                              |

## Calculation

```
GROUP BY shipping_country_id.keyword
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6 with separate UK, US, EU, and AU Store Views plus a B2B portal. Snapshot Monday 4 May 26.

**Top countries by customer count:**

| Country              | Customers (30D) | Revenue (`base_grand_total`) | % of revenue |
| -------------------- | --------------- | ---------------------------- | ------------ |
| GB (United Kingdom)  | 1,840           | \$246,000                    | 28.0%        |
| US                   | 1,420           | \$312,800                    | 35.6%        |
| AU                   | 320             | \$87,400                     | 9.9%         |
| DE (Germany)         | 280             | \$51,200                     | 5.8%         |
| FR (France)          | 240             | \$46,800                     | 5.3%         |
| IE (Ireland)         | 180             | \$32,800                     | 3.7%         |
| NL (Netherlands)     | 130             | \$26,400                     | 3.0%         |
| ES (Spain)           | 110             | \$19,200                     | 2.2%         |
| Other (24 countries) | 286             | \$56,400                     | 6.4%         |
| **Total**            | **4,806**       | **\$879,000**                | **100%**     |

What this is telling leadership:

1. \*\*GB has the most customers (1,840) but the US has the most revenue ($312k).** US AOV is materially higher: $220 per US customer vs \$134 per UK customer. Cross-check this with [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share): the US Store View is more B2B-skewed than the UK Store View.
2. **Australia is a small but high-value market** (\$273 revenue per AU customer). Worth a strategic question: is AU traffic conversion already optimised, or is there room to grow?
3. \*\*EU long tail (DE + FR + NL + ES + IE) totals $176k revenue** from 940 customers, $187/customer average. Combined this is the second-largest market segment. Strategic question: is the EU Store View configured optimally? Is local-language support active? Are local payment methods (iDEAL for NL, Bancontact for BE, SEPA Direct Debit) configured?
4. **24 long-tail countries contribute 6.4% of revenue** combined. Most are likely incidental international shipments. The merchant might consider whether to maintain shipping configurations to all 24 (each has tax compliance overhead) or restrict to top markets.
5. **Tax-treatment bias caveat**: GB revenue includes 20% VAT; US B2B revenue is typically tax-exempt. The "true" comparison removes this: GB customer-revenue ex-VAT is \~$205k vs US at ~$313k. Even adjusted, US per-customer LTV is materially higher.
6. **Multi-currency note**: the figures above are FX-converted via `base_grand_total`. Merchants comparing to per-Store-View native-currency totals see different absolute numbers; this card's view is the right one for cross-country strategic comparison.
7. **Action**: prioritise EU localisation (the long-tail segment with proven traffic but small per-country revenue suggests checkout friction at the local level); consider a US-targeted B2B sales hire; evaluate AU paid-traffic investment.

The point: country mix on Adobe Commerce is more strategically rich than on single-region platforms because the business is genuinely multi-region. The card surfaces both the per-country opportunity and the localisation gaps.

## Sibling cards merchants should reference together

| Card                                                                                         | Why pair it with Customer Countries                                                           |
| -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| [Customer Count](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)                    | The aggregate. Country breakdown is its decomposition.                                        |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                        | The revenue denominator.                                                                      |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                            | Per-country AOV varies materially.                                                            |
| [Total Shipping](/nerve-centre/kpi-cards/adobe-commerce/total-shipping-revenue)              | International shipping fees inflate per-country revenue.                                      |
| [Tax Analysis](/nerve-centre/kpi-cards/adobe-commerce/tax-analysis)                          | Country-by-country tax-rate variance.                                                         |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)                | Country mix correlates with segment mix; US tends B2B-heavier than UK on most stores.         |
| [`google_analytics.ga_users_by_country`](/nerve-centre/google_analytics/ga_users_by_country) | Top-of-funnel comparison. Sessions per country vs orders per country reveals conversion gaps. |
| [`shopify.customer_countries`](/nerve-centre/kpi-cards/shopify/orders-by-country)            | Cross-platform peer.                                                                          |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Orders** filtered by date and ordered by country (Adobe Commerce 2.4.4+ supports country filter on the Sales Orders report).

> **Customers > All Customers** with Address country sort, but this is registered customers only (excludes guests).

> **Sales > Orders** with the Shipping Address: Country filter applied; CSV export and pivot for the country distribution.

For multi-Store-View merchants:

> Switch the Store View scope and run Reports > Sales > Orders per scope. Cross-country flow (a UK Store View order shipping to France) is visible only in the order-level filter, not in the Store View aggregate.

**Why our number may legitimately differ from Admin:**

| Reason                                                                                                                | Direction of divergence                                                |
| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Time-zone**. Admin in Store View timezone; card UTC. ±1 day inclusion.                                              | Negligible at 30D                                                      |
| **Currency**. Card uses `base_grand_total`; Admin uses Store View base currency. Multi-currency sums differ.          | Material on multi-currency mixes                                       |
| **Country definition**. Card uses shipping country. Admin can filter by billing or shipping; defaults vary by report. | Material if shipping and billing diverge frequently (gift orders, B2B) |
| **`canceled` exclusion**. Card excludes; Admin reports include unless filtered.                                       | Card revenue slightly higher per-country                               |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                                         | Expected relationship                                                               | What divergence tells you                                                                                                              |
| -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| [`google_analytics.ga_users_by_country`](/nerve-centre/google_analytics/ga_users_by_country) | GA4 sessions/users by country should correlate with order-customer count by country | Material divergence indicates conversion-rate variance by country (a country with high traffic but low orders has a localisation gap). |
| [`google_ads.google_ads_geo`](/nerve-centre/google_ads/google_ads_geo)                       | Ad spend by country should correlate with new-customer revenue by country           | If you're spending in Germany but seeing zero German customers, your ads are geo-mismatched or the German checkout is broken.          |
| Carrier shipping reports                                                                     | Country distribution should match within carrier-included territories               | Major divergence usually means a carrier-managed forwarding service changing destination after shipment.                               |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.customer_countries`](/nerve-centre/kpi-cards/shopify/orders-by-country)
  * [`bigcommerce.customer_countries`](/nerve-centre/kpi-cards/bigcommerce/orders-by-country)
</details>

## Known limitations / merchant FAQs

**Why does the card use shipping country rather than billing?**
Shipping country reflects where goods physically go, which is the most relevant strategic dimension (logistics planning, international shipping fees, carrier choice). Billing country can lag where the customer actually lives (corporate-card billing addresses, gift cards, intermediary billing services). For merchants who care about billing-country distribution specifically (tax reporting, fraud analysis), configure a sibling card variant.

**Adobe Commerce vs Magento Open Source: any difference?**
None at the calculation. Both editions store `country_id` on shipping addresses identically. Adobe Commerce paid edition's enhanced multi-region tax logic and Adobe Experience Cloud integration give richer reporting on top of the same underlying data; Open Source merchants compute the country roll-up identically.

**A customer ordering from US to a UK gift recipient, who counts where?**
The shipping address is UK; the card counts this as a UK order. Useful for logistics planning. For purchase-intent analysis (where the customer "lives"), use billing-country sibling.

**My multi-store Adobe Commerce, the country distribution looks weird, why?**
Likely cause: Store View routing is geographic (US Store View, UK Store View) but customers can technically check out on a non-matching Store View (a UK customer accidentally lands on the US Store View, completes the order with UK shipping). The card surfaces this; the merchant can use it to identify Store-View routing leakage.

**Why does the EU long tail show inflated revenue per customer compared to GB customers?**
International shipping inflation: international parcels typically cost 3 to 8x domestic shipping. Cross-check with [Total Shipping](/nerve-centre/kpi-cards/adobe-commerce/total-shipping-revenue). The "real" per-customer purchase intent is closer if you subtract shipping; gross AOV-by-country misleads.

**Why is my country count higher than my Store View count?**
Store Views are merchant-created (US, UK, EU, AU); customers can ship anywhere they have an address. A 5-Store-View merchant might serve customers in 40+ countries. The two metrics are independent.

**A few orders show country = "" (empty), why?**
Adobe Commerce can store empty country on incomplete addresses (typically virtual/digital products that don't require shipping). Filter these out via the manifest if your merchant ships physical-only goods.

**My multi-currency Adobe Commerce, are the per-country totals comparable?**
Yes; the card uses `base_grand_total`. Per-currency caveats: a US customer ordering on the UK Store View pays in GBP, and `base_grand_total` is the GBP value FX-converted to the merchant's primary currency at order time. A pure-USD comparison would require segmenting by `order_currency_code = USD` (only available via custom configuration).

***

### Tracked live in Vortex IQ Nerve Centre

*Orders by Country* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Orders Over Time, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/orders-over-time

Orders Over Time for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> The day-by-day count of orders created over the last 90 days. The simplest of the time-series cards, useful for spotting promotion peaks, weekly seasonality, post-holiday collapses, and incident-driven dips. Plotted as a line chart with a 7-day moving average overlay to smooth weekly noise.

|                                                 |                                                                                                                                                                                                                                                                                                                      |
| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                              | For each day in the 90-day window: `COUNT(orders WHERE created_at IN day)`. Order counted regardless of `state`, including `canceled`, `pending_payment`, `payment_review`. The intent is "orders the customer placed", not "orders we collected money on".                                                          |
| **API field**                                   | `entity_id`, `created_at` from the orders index. Adobe Commerce REST: `GET /rest/V1/orders` with `searchCriteria` filtering on `created_at`.                                                                                                                                                                         |
| **State filter**                                | All states included by default. Toggle filters on the chart legend to exclude `canceled`, `pending_payment`, etc. for cleaner views. The default-includes-canceled stance differs from value-side cards (which often exclude canceled to avoid double-counting refunds); for count, all-states is the right default. |
| **VAT / tax / shipping / discounts / currency** | n/a, this is a count card.                                                                                                                                                                                                                                                                                           |
| **Refunds**                                     | A refunded order still counts as an order placed. Refunds happen later; this card is about creation time.                                                                                                                                                                                                            |
| **Channels / sources**                          | All Adobe Commerce sources counted: storefront, Admin-created, B2B portal, Marketplace if installed.                                                                                                                                                                                                                 |
| **Multi-store scope**                           | All Store Views by default; per-Store-View slicing via legend filter.                                                                                                                                                                                                                                                |
| **Time window**                                 | `90D` rolling. Daily granularity. 7-day moving average overlay.                                                                                                                                                                                                                                                      |
| **Alert trigger**                               | None on this card directly. The hourly canary is on [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert).                                                                                                                                                                                 |
| **Sentiment key**                               | `order_count_trend`                                                                                                                                                                                                                                                                                                  |
| **Roles**                                       | owner, marketing, operations                                                                                                                                                                                                                                                                                         |

## Calculation

```
DATE_HISTOGRAM COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC apparel merchant on Adobe Commerce 2.4.7. Snapshot 13 May 26, 90-day rolling.

**Aggregate stats over the window:**

| Metric                               | Value  |
| ------------------------------------ | ------ |
| Days                                 | 90     |
| Total orders                         | 14,420 |
| Mean orders / day                    | 160    |
| Median orders / day                  | 153    |
| Min day (Sun 7 Apr 26)               | 67     |
| Max day (Mon 14 Apr 26, post-Easter) | 297    |
| Standard deviation                   | 38     |

**Weekly seasonality (mean orders by day of week):**

| Day | Mean orders |
| --- | ----------- |
| Mon | 184         |
| Tue | 175         |
| Wed | 166         |
| Thu | 161         |
| Fri | 148         |
| Sat | 142         |
| Sun | 134         |

Monday-to-Sunday spread is about 38%. Typical for B2B+DTC.

**Notable events on the chart:**

| Date                  | Orders    | What happened                                                                    |
| --------------------- | --------- | -------------------------------------------------------------------------------- |
| 24 Feb 26             | 247       | Flash sale 25% off; +54% vs Tue average                                          |
| 14 Mar 26             | 89        | -39% vs Sat average; investigate (turned out: storefront 502 errors for 2 hours) |
| 14 Apr 26             | 297       | post-Easter Monday catch-up + post-holiday surge; +61% vs Mon mean               |
| 28 Apr 26 to 5 May 26 | 78-95/day | sustained dip; supplier sizing issue caused PR; recovery from 6 May              |

**Insight pattern:**

1. **The 14 Mar dip (-39%) is the canary.** A single day, a Saturday so volume is naturally lower. But the absolute drop was sharp enough to suggest an incident. The merchant cross-checked [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert) for that day; it had fired at 11:00 GMT (storefront 502 burst). Confirmation that the alert worked.
2. **The 14 Apr spike (+61%) is benign.** Post-holiday catch-up; B2B accounts that didn't order during Easter weekend post fresh POs Monday morning. Cross-link with [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time), revenue should also spike but the AOV may dip (high order count, normal AOV per order).
3. **The 28 Apr to 5 May sustained dip.** This is the most concerning pattern. Eight straight days below the 7-day moving average, with the average itself trending down. Cause: a viral negative review on a B2B forum about the uniform sizing issue. Mitigation: the merchant's PR team posted corrections and offered replacements; volume recovered by 6 May.
4. **Weekly seasonality is the dominant noise.** B2B-leaning merchants always show Mon > Tue > ... > Sun pattern. Compare this card's daily values to the same DOW two weeks prior, not yesterday, for clean signal.
5. **Cross-link with [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend).** If order count is up but customer count is flat, repeat-customer concentration is rising, healthy retention. If order count is up because customer count is up, acquisition is winning.
6. **`canceled` orders included.** The 134 cancelled orders in the period contribute to the count. Toggle the legend to exclude for "captured-only" view; it's about 1% lower on most days.

## Sibling cards merchants should reference together

| Card                                                                                     | Why pair it with Orders Over Time                                      |
| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                      | Aggregate of this card.                                                |
| [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time)            | Value-side companion. Diverging shapes diagnose AOV swings.            |
| [Daily Order Trends](/nerve-centre/kpi-cards/adobe-commerce/daily-order-trends)          | Intraday view.                                                         |
| [Cancelled Over Time](/nerve-centre/kpi-cards/adobe-commerce/cancelled-orders-over-time) | Cancellations subtracted; for understanding the captured-orders shape. |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)            | Same chart shape pattern; useful for incident-correlation.             |
| [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)      | Customer count over time; pair to disentangle volume from acquisition. |
| [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert)          | Real-time canary; this card is the historical context.                 |
| [`shopify.orders_over_time`](/nerve-centre/kpi-cards/shopify/orders-over-time)           | Shopify peer.                                                          |
| [`bigcommerce.orders_over_time`](/nerve-centre/kpi-cards/bigcommerce/orders-over-time)   | BigCommerce peer.                                                      |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Orders** with "Show By" set to "Day", date range matching this card. The chart shows daily order count alongside daily revenue. The count column should match this card.

For the live grid:

> **Sales > Orders** filtered by Purchase Date range; the bottom-of-grid total row count gives the period's count.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                           | Direction of divergence                        |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| **Time-zone**. Reports use Store View locale; this card uses UTC by default. Day-edge orders shift.                                                              | Bucket-shift                                   |
| **Reports indexer lag**. Reports > Sales > Orders relies on the `sales_order_aggregated_*` tables refreshed nightly. Today's orders may not show until tomorrow. | Vortex IQ ahead by \~12-24h on most-recent day |
| **Status filter on Reports**. Reports > Sales > Orders defaults to "Status = Any". Match unless the merchant overrode the filter.                                | Usually no divergence                          |
| **`pending_payment` and `canceled` inclusion**. Reports includes them by default; so does this card.                                                             | None expected                                  |
| **Multi-store scope**. Both default to "All Store Views".                                                                                                        | None                                           |
| **Sync lag**. 5-15 min.                                                                                                                                          | Standard                                       |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                                                     | Expected relationship                                                     | What divergence tells you                                                                                                    |
| -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [`google_analytics.ga_transactions_over_time`](/nerve-centre/google_analytics/ga_transactions_over_time) | GA4 daily transactions ≈ this card × (1 − tracking gap, typically 10-25%) | Persistent \<70% means GA4 tracking is broken or consent is blocking events. >100% almost always means double-firing tags.   |
| [`stripe.stripe_charge_count_over_time`](/nerve-centre/stripe/stripe_charge_count_over_time)             | Stripe daily successful charges ≤ this card's order count                 | Gap = orders paid via PayPal, Authorize.Net, manual transfer + orders in `pending_payment`/`canceled` that never hit Stripe. |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.orders_over_time`](/nerve-centre/kpi-cards/shopify/orders-over-time)
  * [`bigcommerce.orders_over_time`](/nerve-centre/kpi-cards/bigcommerce/orders-over-time)
</details>

## Known limitations / merchant FAQs

**Why does the card include `canceled` and `pending_payment` orders?**
Because the question this card answers is "how many orders did customers place?" An order created and then cancelled is still demand the merchant captured. For "how many orders did we collect money on", filter the chart legend to exclude `canceled` and `pending_payment`; for "what's our acquisition velocity", keep them.

**Why does Saturday always look low?**
Because B2B accounts don't order on weekends. DTC orders on weekends but at lower volume than weekdays. Compound the two and Saturday is the structural low. Use the day-of-week comparison rather than yesterday-vs-today for cleaner signal.

**My 7-day moving average is smoothing too much, can I disable?**
Yes. The chart toggle "Show MA" can be turned off. Daily-only view exposes incidents more clearly but is noisier.

**Why is today's last data point lower than yesterday's?**
Because today is incomplete. The trailing data point is "orders so far today" which is structurally less than a full day's count. The chart should annotate this with "(in progress)"; if not, mentally exclude the trailing point.

**A spike on a weekend, real or admin-created?**
Adobe Commerce admins occasionally create bulk orders manually (e.g. importing wholesale POs from email). These show up as Admin-created orders with `created_at = now()` even though the actual customer order date might be 3 days prior. Cross-check with the Admin user attribution; if a single admin user created 50 orders on Sat 2pm, it's a backlog import, not real demand. Filter `admin_created` orders out for true demand signal.

**Multi-store, can I see one Store View at a time?**
Yes. Filter via the chart legend. Useful for comparing US store seasonality vs UK store seasonality (very different).

**Why doesn't Google Analytics agree?**
GA4 typically misses 10-30% of orders due to ad blockers, consent banners, tag-fire failures, browser tracking prevention. Adobe Commerce is the system of record (it has the order); GA4 is a sampled view. Don't try to reconcile them; use Adobe for absolute count and GA4 for marketing attribution.

**A B2B Company places one PO that creates 3 child orders, do I see 3 spikes?**
Adobe Commerce B2B "Quotes" can convert to multiple orders if the customer splits delivery. Each child order is a separate row in the orders index, so the count is 3. If you want to see the parent quote count, use a separate quote-volume card (custom).

**Can I overlay events (campaign launch, system upgrade, supplier change)?**
Yes via the Vortex IQ workspace's annotations. Marked events show on every time-series card to help correlation across [Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/orders-over-time), [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time), [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time), etc.

**Today's number jumped from 145 to 167 in 30 minutes. Can that happen?**
Yes if you had a 30-minute promotion or email send. It is unusual on a quiet Wednesday afternoon. Cross-check against the marketing campaign calendar and against [Stripe charge count](/nerve-centre/stripe/stripe_charge_count_over_time). If Stripe didn't see 22 new charges in that window, somebody is creating Admin orders in bulk.

***

### Tracked live in Vortex IQ Nerve Centre

*Orders Over Time* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Refund Rate, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/refund-rate

Refund Rate for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> The percentage of orders in the period that have at least one Credit Memo against them. Defined as `COUNT(DISTINCT order_id WITH any Credit Memo created in the period) ÷ COUNT(orders created in the period) × 100`. Industry-typical for Adobe Commerce merchants is 2-6% in apparel, 0.5-2% in B2B/wholesale, 5-12% in returns-friendly DTC verticals.

|                            |                                                                                                                                                                                                                                                                                                                                                                                                          |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**         | The numerator: distinct orders that have any Credit Memo (full or partial) created in the period. The denominator: orders created in the period. The window aligns the order-creation date with the Credit Memo creation date, this is the "in-period refund rate", not the cohort refund rate (orders created this month, refunded later, would not be reflected here until they are refunded).         |
| **API field**              | Numerator from `GET /rest/V1/creditmemos` joined to orders by `order_id`. Denominator from `GET /rest/V1/orders` filtered on `created_at`.                                                                                                                                                                                                                                                               |
| **VAT / tax treatment**    | n/a, the card is a count ratio, not a value ratio. For value-weighted refund rate (`SUM(creditmemo.grand_total) ÷ SUM(orders.grand_total)`) use the value variant available in custom dashboards.                                                                                                                                                                                                        |
| **Shipping**               | n/a for the rate. Shipping-only Credit Memos count as "an order with a Credit Memo" so they push the rate up; merchants tracking product-only refund rate should configure a manifest filter to exclude `subtotal=0` Credit Memos.                                                                                                                                                                       |
| **Discounts**              | n/a.                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Cancelled orders**       | **Included in the denominator, excluded from the numerator.** A canceled order has no Credit Memo (cancellation reverses pre-capture authorisation) so it is in the order count but never in the refund count. This drags the rate slightly down compared to a denominator of "captured orders only". For a captured-orders-only rate, exclude `state=canceled` from the denominator via manifest tweak. |
| **Partial refunds**        | Each refunded order counts once in the numerator regardless of how many Credit Memos it has. So an order with 3 Credit Memos contributes 1 to the numerator (and 1 to the denominator). Use [Refund Count](/nerve-centre/kpi-cards/adobe-commerce/refunded-orders) for the document-count perspective.                                                                                                   |
| **State filter**           | All `state` values included in the denominator: `new`, `pending_payment`, `processing`, `complete`, `closed`, `canceled`, `holded`, `payment_review`. The numerator naturally excludes `pending_payment`, `payment_review`, and `canceled` because Credit Memos cannot be issued on those states.                                                                                                        |
| **Currency / multi-store** | The rate is unitless. All Store Views aggregated by default; Store View slicing available.                                                                                                                                                                                                                                                                                                               |
| **Time window**            | `30D vsP`, rolling 30-day with prior-period comparison.                                                                                                                                                                                                                                                                                                                                                  |
| **Alert trigger**          | `>5% absolute or +25% vs prior period`. The 5% absolute threshold is a soft DTC norm; B2B-heavy merchants should override to 2%.                                                                                                                                                                                                                                                                         |
| **Sentiment key**          | `refund_rate`                                                                                                                                                                                                                                                                                                                                                                                            |
| **Roles**                  | owner, operations                                                                                                                                                                                                                                                                                                                                                                                        |

## Calculation

```
COUNT(status=refunded) / COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC apparel merchant on Adobe Commerce 2.4.7. Period: 14 Apr 26 to 13 May 26.

**Order and refund counts:**

| Slice                                    | Orders created         | Distinct orders with any Credit Memo | Refund rate |
| ---------------------------------------- | ---------------------- | ------------------------------------ | ----------- |
| All orders                               | 4,820                  | 358                                  | **7.43%**   |
| DTC orders only (non-B2B Customer Group) | 4,512                  | 341                                  | 7.56%       |
| B2B orders (Adobe Commerce Companies)    | 308                    | 17                                   | 5.52%       |
| Excluding `canceled` from denominator    | 4,684 (canceled = 136) | 358                                  | 7.65%       |

**Comparison to prior 30 days:**

| Window              | Refund rate  | Threshold (5%)                | Threshold (+25% vsP)                 |
| ------------------- | ------------ | ----------------------------- | ------------------------------------ |
| 14 Apr to 13 May 26 | 7.43%        | breached                      | (vs prior 4.78%, **+55%**, breached) |
| 15 Mar to 13 Apr 26 | 4.78%        | clean                         | -                                    |
| **Sentiment**       | **degraded** | both alert conditions tripped |                                      |

What this is telling Operations:

1. **Both alerts fire.** Absolute rate (7.43%) is above the 5% threshold and the period-over-period jump (+55%) is well past the 25% relative threshold. This is not noise; it is a structural change.
2. **B2B refund rate jumped from 1.8% to 5.52%.** B2B normally runs \<2%; a 3x increase is the dominant signal. Cross-link with the [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value) example: 12 B2B accounts returned bulk uniform-line shipments due to supplier sizing error.
3. **DTC rate also rose from 4.95% to 7.56%.** Smaller relative jump but on a larger base; absolute volume growth in returns is mostly DTC.
4. **Canceled-excluded view (7.65%)** is the more honest figure for ops because it removes orders that never got captured. Most "refund rate benchmarks" in industry reports use this version. Use it when comparing to peers.
5. **The dashboard's "Reports > Sales > Refunds" report shows £46,220 / £950,000 = 4.86% (value-weighted).** The refund rate by count (7.43%) is higher than by value (4.86%), meaning refunded orders skew lower-value than the order-set average. That makes sense: low-AOV DTC apparel returns more frequently than high-AOV B2B shipments. Both numbers are correct, they answer different questions.
6. **Action:** investigate the supplier sizing issue immediately (highest-impact lever), and dig into [Top Refunded Products](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) to see whether the elevated DTC rate concentrates on the same uniform line or is broader.

## Sibling cards merchants should reference together

| Card                                                                                    | Why pair it with Refund Rate                                                                                                          |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| [Refund Count](/nerve-centre/kpi-cards/adobe-commerce/refunded-orders)                  | The numerator. Spike in count without rate-change suggests order volume rose proportionally (no problem).                             |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)                     | Money out the door. Value-weighted view of the same trend.                                                                            |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)           | Day-by-day shape of the rate.                                                                                                         |
| [Top Refunded Products](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) | The SKU concentration. Often 5 SKUs drive 50%+ of the rate.                                                                           |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)           | Pre-capture cancellations. Different problem (payment failure, fraud rejection, wrong-shipping-address rejection) but related signal. |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                     | The denominator. Slowing order volume can spike the rate even with stable refund volume.                                              |
| [Return Status](/nerve-centre/kpi-cards/adobe-commerce/return-status)                   | RMA pipeline. Approved RMAs are the next month's refunds.                                                                             |
| [`shopify.refund_rate`](/nerve-centre/kpi-cards/shopify/refund-rate)                    | Shopify peer for cross-platform agencies.                                                                                             |
| [`stripe.stripe_refund_rate`](/nerve-centre/kpi-cards/stripe/refund-rate)               | Payment-side rate. Should approximately match for Stripe-paid orders.                                                                 |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

Adobe Commerce does not expose refund rate as a single Admin number; it must be derived. The closest views:

> **Reports > Sales > Refunds** divided by **Reports > Sales > Orders** for the same period gives the value-weighted equivalent (which is not the same as this card's count-weighted rate). Use this for sanity-checking the order-of-magnitude only.

For count-weighted reconciliation:

> **Sales > Operations > Credit Memos**, count distinct `Order #` column values for the period. Then **Sales > Orders** with `Purchase Date` set to the same period, count rows. Divide. This matches this card to within sync-lag.

**Why our number may legitimately differ from a manual Admin computation:**

| Reason                                                                                                                                                                                                                                                         | Direction of divergence                               |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| **Time-zone**. Admin grids run in Store View locale; this card runs UTC. Orders and Credit Memos at day-edges shift between days.                                                                                                                              | ±1 day at edges                                       |
| **Cohort vs in-period framing**. This card divides "orders with Credit Memos in the period" by "orders created in the period". A merchant manually computing might use "orders refunded in period / all-time orders refunded ever" which is a different ratio. | Material divergence                                   |
| **Canceled in denominator**. This card includes `canceled` orders in the denominator by default. Some merchants prefer captured-only. The card output toggles via manifest.                                                                                    | Vortex IQ rate slightly lower than captured-only view |
| **Reports indexer lag**. The Reports module reads from the nightly-refreshed aggregated table. This card reads live OpenSearch (5-15 min behind).                                                                                                              | This card more current                                |
| **Distinct-order vs document-count**. This card counts distinct refunded orders. A merchant counting Credit Memos directly will get a higher numerator (multi-memo orders) and an inflated rate.                                                               | Merchant manual rate higher                           |

**Internal identity (within Adobe Commerce):**

`refund_rate = COUNT(DISTINCT order_id WITH any Credit Memo) ÷ COUNT(orders) × 100`

The legacy stub formula `refund_count ÷ order_count` is approximate, it equals the true rate only when every refunded order has exactly one Credit Memo. Real merchants average 1.05-1.20 Credit Memos per refunded order, so the legacy formula over-states by 5-20%. The card uses the distinct-order numerator.

Component cards (self-consistency, not reconciliation):

* [`adobe_commerce.refund_count`](/nerve-centre/kpi-cards/adobe-commerce/refunded-orders)
* [`adobe_commerce.order_count`](/nerve-centre/kpi-cards/adobe-commerce/total-orders)

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  This metric exists with the same definition on other commerce platforms.

  * [`shopify.refund_rate`](/nerve-centre/kpi-cards/shopify/refund-rate)
  * [`bigcommerce.refund_rate`](/nerve-centre/kpi-cards/bigcommerce/refund-rate)
  * [`stripe.stripe_refund_rate`](/nerve-centre/kpi-cards/stripe/refund-rate)
</details>

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  This metric exists with the same definition on other commerce platforms. This is **not** a reconciliation, your Adobe Commerce store doesn't have a parallel store on those platforms to compare against. These references exist purely so an agency running clients across multiple platforms can cross-link the same metric across docs.

  * [`shopify.refund_rate`](/nerve-centre/kpi-cards/shopify/refund-rate)
  * [`bigcommerce.refund_rate`](/nerve-centre/kpi-cards/bigcommerce/refund-rate)
  * [`stripe.stripe_refund_rate`](/nerve-centre/kpi-cards/stripe/refund-rate)
</details>

## Known limitations / merchant FAQs

**Why is my refund rate by count higher than by value?**
Refunded orders typically skew lower-AOV than the order-set average. A high-AOV B2B order is rarely returned; a low-AOV DTC apparel order is. So count-weighted rate is structurally higher than value-weighted rate for most merchants. This card uses count by default; the value-weighted variant is available in custom dashboards.

**My refund rate looks reasonable but my Reports > Sales > Refunds value is alarming, why?**
Two different lenses. A few high-AOV refunds drive value without moving the count-rate much. Look at average refund value (`Refund Value ÷ Refund Count`) to see if you have a "few whales" pattern.

**Should canceled orders be in the denominator?**
Depends on your business model. Cards default to including them because canceled-and-refunded orders are operationally similar (the customer didn't get the goods). For pure-product return rate, exclude `canceled` via manifest. Note that "canceled before capture" cannot have a Credit Memo so they only push the denominator up, not the numerator.

**The 5% threshold doesn't fit my B2B merchant, can I customise?**
Yes. The threshold is per-tenant configurable. B2B should typically run at 1.5-2% threshold; high-fashion DTC at 8-10%. The +25% relative threshold is more universally useful since it triggers on directional change regardless of base level.

**Why is the rate higher than `stripe.stripe_refund_rate`?**
Two reasons: (1) some refunds are issued via PayPal or manual bank transfer, never touching Stripe, but still in this card's numerator; (2) Stripe's rate denominator includes only Stripe-paid orders, this card's includes all orders, the proportions differ if Stripe is not 100% of payment. To compare like-for-like, filter this card to Stripe-paid orders only.

**Today's value swung from 4.2% to 6.1% in one hour, is that real?**
On low-volume stores (under 200 orders/day), one-hour numbers are noisy. A single batch of Credit Memos posted by Customer Service can spike the rate. The 30-day rolling smooths this. If your store is high-volume (over 1,000 orders/day) and you see hourly swings, that is real and worth investigating.

**Multi-currency, does the rate differ across currencies?**
The count-weighted rate is currency-agnostic. The value-weighted rate is sensitive to FX since `grand_total` is mixed-currency; use `base_grand_total` for FX-neutral comparison.

**A canceled order is in the denominator. Doesn't that artificially lower the refund rate?**
It lowers it slightly because the numerator excludes canceled orders (no Credit Memo possible). For most merchants the cancellation rate is 1-3%, so the dilution is small. If your store has cancellation rate above 8% (often a payment-fraud or stock-out problem), exclude canceled from the denominator for a cleaner refund rate, then track [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate) separately.

**My refund rate dropped to 0% on Sunday, why?**
Customer Service teams typically don't process refunds on weekends. The numerator is zero on those days, but the denominator (orders created) is non-zero. The rate dips, then catches up Monday-Tuesday as the weekend's RMAs get processed. Use 7-day rolling rather than daily to avoid the weekly weekend dip.

***

### Tracked live in Vortex IQ Nerve Centre

*Refund Rate* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Refund-Rate Spike Alert, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/refund-rate-spike-alert

Catches a bad batch / mis-priced SKU / regression-after-deploy before the chargeback wave hits. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> Catches a bad batch / mis-priced SKU / regression-after-deploy before the chargeback wave hits.

## At a glance

> Real-time alert that fires when the refund rate (Credit Memos issued per ordered unit) exceeds 2x the trailing 30-day baseline. Designed to catch a bad supplier batch (defective product), a mis-priced SKU (a £30 item rang up at £3 because of a decimal-point error), or a regression-after-deploy (a fulfillment integration is shipping wrong items). Each of these creates a refund wave that snowballs into chargebacks if not caught within hours.

|                                                        |                                                                                                                                                                                                                                                                                                                                                |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `COUNT(credit_memos in window) / COUNT(orders in window)` where the window is rolling 1-hour. The 30-day baseline is computed at the same hour-of-week for fair comparison. Fires when the current ratio is more than 2x the baseline mean, gated on absolute count (at least 5 credit memos in the hour) to avoid noise on low-volume stores. |
| **API field**                                          | Credit Memos via `GET /rest/V1/creditmemos` (separate document type in Adobe Commerce, not a status flag on the order). Order count via `GET /rest/V1/orders`. The card joins via `order_id`.                                                                                                                                                  |
| **VAT / tax treatment**                                | The refund-rate ratio is count-based, so tax treatment doesn't bias it. The companion "value at risk" estimate uses Credit Memo `grand_total` which is tax-inclusive (matches the original order's `grand_total`).                                                                                                                             |
| **Shipping inclusion**                                 | n/a for the count. Credit Memos can include or exclude shipping refund, depending on whether the merchant ticked "refund shipping" when creating the memo; the card counts the memo regardless.                                                                                                                                                |
| **Discounts**                                          | n/a for the count. Credit Memo `grand_total` deducts the prorated discount automatically.                                                                                                                                                                                                                                                      |
| **Credit Memo refund treatment**                       | This card IS the Credit Memo monitor. Adobe Commerce uses Credit Memos as separate documents (unlike Shopify which mutates the order). A Credit Memo can be partial (refund 1 of 3 line items) or full. The card counts each memo as one event regardless of partial/full status.                                                              |
| **`state` machine inclusion**                          | The order side uses all states. Credit Memos are typically issued against orders in `complete` (already invoiced, then partially refunded) or `closed` (fully refunded). A memo against `processing` is unusual but possible (refund before shipment); the card includes them.                                                                 |
| **`pending_payment` quirk**                            | Credit Memos cannot be issued against `pending_payment` orders (no captured payment to refund). Such cancellations show up under [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate) instead. The two cards together cover the full "money-back" surface area.                                                       |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a for the count ratio. The value-at-risk uses `base_grand_total` for cross-currency rollup.                                                                                                                                                                                                                                                  |
| **Store View scope (`store_id`)**                      | All Store Views by default. Per-Store-View variants are recommended because refund spikes are usually localised to one product category or one fulfillment region.                                                                                                                                                                             |
| **Time window**                                        | `RT` (real-time, rolling 1-hour).                                                                                                                                                                                                                                                                                                              |
| **Alert trigger**                                      | `refund rate >2x 30D baseline` at same hour-of-week. The 2x multiplier is empirically chosen to filter routine variance; lower (1.5x) for very steady stores, higher (3x) for high-variance stores.                                                                                                                                            |
| **Sentiment key**                                      | `refund_rate`                                                                                                                                                                                                                                                                                                                                  |
| **Roles**                                              | owner, operations, finance                                                                                                                                                                                                                                                                                                                     |

## Calculation

```
COUNT(status=refunded) / COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A houseware retailer on Adobe Commerce 2.4.6 with a US Store View, a UK Store View, and a B2B portal Store View. Snapshot taken Thursday 21 Apr 26, 13:00 BST. The alert just fired.

**30-day baseline (Thursdays 13:00 BST):**

| Stream            | Hourly orders | Hourly Credit Memos | Refund rate |
| ----------------- | ------------- | ------------------- | ----------- |
| US (consumer)     | 86            | 2.1                 | 2.4%        |
| UK (consumer)     | 124           | 3.8                 | 3.1%        |
| B2B portal        | 14            | 0.2                 | 1.4%        |
| Combined baseline | 224           | 6.1                 | 2.7%        |

**Current hour:**

| Stream        | Hourly orders | Hourly Credit Memos | Refund rate | vs baseline                    |
| ------------- | ------------- | ------------------- | ----------- | ------------------------------ |
| US (consumer) | 92            | 3                   | 3.3%        | within range                   |
| UK (consumer) | 118           | **17**              | **14.4%**   | **+11.3 pts, \~4.6x baseline** |
| B2B portal    | 16            | 0                   | 0%          | as expected                    |
| **Combined**  | 226           | **20**              | **8.8%**    | **3.3x baseline**              |

**The alert fired** because combined refund rate is 3.3x the 30-day baseline at this hour-of-week. The UK stream is 4.6x baseline.

What the investigation reveals:

1. **UK is the problem.** US and B2B are within normal variance.
2. **Pulling the 17 UK Credit Memos**: 12 of them are against the same SKU, `KETTLE-CC-1L` (a 1-litre stovetop kettle). The remaining 5 are normal scattered returns.
3. **`KETTLE-CC-1L` order velocity** has been climbing for a week (a TikTok video drove a viral spike). The merchant has been gleeful about the demand. But starting yesterday afternoon, the customer service inbox has had complaints: the kettle handle is loose on arrival.
4. **Cross-checking [Top Refunded SKUs](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers)**: `KETTLE-CC-1L` is now the #1 refunded SKU, accounting for 22% of UK refund volume in the last 24 hours. Last week it was not in the top 20.
5. **Root cause**: the supplier shipped a defective batch. The merchant received pallets of `KETTLE-CC-1L` from supplier 4 days ago; everything dispatched since then has the loose-handle defect.
6. **The fix sequence**:
   * Pause the `KETTLE-CC-1L` ad campaign immediately (use [Active Ads on OOS SKUs](/nerve-centre/kpi-cards/adobe-commerce/active-ads-on-out-of-stock-skus) workflow plus manual pause).
   * Mark `KETTLE-CC-1L` as out of stock in Adobe Commerce admin (Catalog > Products > KETTLE-CC-1L > Stock Status: Out of Stock). This stops new orders.
   * Email all UK customers who received `KETTLE-CC-1L` in the last 4 days with proactive replacement offers (about 320 customers per the Sales > Orders search).
   * Issue an RMA to the supplier for the defective batch.
   * Resume sales only when verified-good replacement stock arrives.
7. **Cost-of-detection**: at the moment of the alert, \~90 defective kettles were already in transit to UK customers. Without the alert, the merchant would have discovered the defect through customer service pressure on Friday (when most of the 90 had been delivered and complaint volume crested). Detecting at hour 0 means proactive comms to \~290 of the 320 customers, dramatically improving retention.
8. **Chargeback-risk avoidance**: refund-rate spikes that go unmanaged for 14+ days correlate strongly with chargeback waves (customers who can't get refunds from the merchant escalate to the card issuer). Catching at hour 0 means refunds processed before chargebacks are filed; merchant reputation with payment processors is preserved.

## Sibling cards merchants should reference together

This alert is most actionable when paired with product-level and payment-side cards.

| Card                                                                                     | Why pair it with Refund-Rate Spike Alert                                                                                                                      |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Top Refunded SKUs](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers)      | The smoking gun. A refund spike concentrated on a single SKU is almost always a defective batch or pricing error.                                             |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                        | The trailing percentage view. Confirms whether the spike is sustained (genuine product issue) or transient (a single weird hour).                             |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)            | Time-series view. Shows whether the spike is the start of a trend or an isolated event.                                                                       |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)                      | Dollar impact. A 4x rate spike on $10 SKUs is small money; on $400 SKUs it is severe.                                                                         |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)            | Pre-shipment refunds (orders cancelled before fulfillment) appear here. Cancellations + Credit Memos together cover the full money-back surface.              |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                    | Net cash impact. Credit Memos do not subtract from Total Revenue (gross), so a refund spike masks itself in revenue dashboards; this alert exists to flag it. |
| [`stripe.stripe_chargebacks`](/nerve-centre/stripe/stripe_chargebacks)                   | Lagging risk. Unmanaged refund waves become chargeback waves 14 to 30 days later.                                                                             |
| [`shopify.shopify_alert_refund_spike`](/nerve-centre/shopify/shopify_alert_refund_spike) | Cross-platform peer for agency teams.                                                                                                                         |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

For the Credit Memo list:

> **Sales > Credit Memos** lists every memo issued, with date, amount, and the originating order. Filter by date range to see the per-hour count. Adobe Admin shows the absolute count; this card derives a ratio against orders.

For per-SKU refund detail:

> **Reports > Sales > Refunds** aggregates Credit Memo amount by date. Useful for spotting trends but does not break down by SKU; use the manual workflow Sales > Credit Memos > export to CSV > pivot in spreadsheet for SKU detail. Or use the [Top Refunded SKUs](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) card.

For the underlying order side:

> **Sales > Orders** filtered to today gives the order denominator.

Other Adobe Commerce Admin views that look relevant but are not:

* **Reports > Sales > Tax**: tax aggregations, not refund rate.
* **Reports > Sales > Coupons**: coupon usage.
* **Sales > Invoices**: separate document; an invoice can be issued without a Credit Memo following.
* **Sales > Returns** (RMA module if installed): authorisations to return, separate from the actual refund issuance.

**Why our number may legitimately differ from a manual Admin count:**

| Reason                                                                                                                                                                                                                                                                   | Direction of divergence                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- |
| **Time-zone**. Admin renders in Store View timezone; the card runs UTC. Hour boundaries shift accordingly.                                                                                                                                                               | ±N hours of timezone offset                                         |
| **Partial Credit Memos**. The card counts each memo as one event regardless of partial/full. The Admin view also lists each memo. The "value-at-risk" companion uses Credit Memo `grand_total` which is the actual refunded amount; partials are smaller than originals. | No count divergence; value divergence                               |
| **`canceled` orders**. Cancellations are not Credit Memos; this card does not include them. The Admin "Refunds" report similarly excludes cancellations.                                                                                                                 | No divergence here                                                  |
| **RMA-only events**. If the merchant uses the Adobe RMA module, return authorisations exist before Credit Memos are issued. This card counts memos, not RMAs.                                                                                                            | Card may lag RMA volume by 1-3 days (the typical RMA-to-refund lag) |
| **Multi-Store-View scope**. Admin scopes to one Store View; the card sums by default.                                                                                                                                                                                    | Vortex IQ higher counts                                             |
| **Sync lag**. The card uses the most recent OpenSearch sync (5-15 min); Admin is live.                                                                                                                                                                                   | Vortex IQ slightly stale at the boundary                            |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                   | Expected relationship                                                                      | What divergence tells you                                                                                                                                                                                                                                                                     |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_refunds`](/nerve-centre/stripe/stripe_refunds)         | Stripe refunds should equal Adobe Credit Memos for Stripe-paid orders, with sub-second lag | If Stripe refund volume is higher than Adobe Credit Memo volume, refunds are being processed in Stripe directly without Adobe knowing (payment ops bypass). If Adobe Credit Memos exceed Stripe refunds, memos are being created without payment refund (likely store credit issued instead). |
| [`paypal.pp_refunds`](/nerve-centre/paypal/pp_refunds)                 | Same relationship for PayPal-paid orders                                                   | Same diagnostic.                                                                                                                                                                                                                                                                              |
| [`stripe.stripe_chargebacks`](/nerve-centre/stripe/stripe_chargebacks) | Lagging effect, expect chargebacks to rise 14-30 days after sustained refund spikes        | Customers who don't get refunds escalate to issuer; managing the refund wave avoids the chargeback wave.                                                                                                                                                                                      |
| Customer service ticket volume                                         | Should rise alongside refund spikes                                                        | If tickets are quiet but refunds are spiking, refunds are being issued without customers asking (proactive refund automation, sometimes a sign of fraud-controls overreach).                                                                                                                  |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same alert exists with platform-specific definitions on other commerce connectors.

  * [`shopify.shopify_alert_refund_spike`](/nerve-centre/shopify/shopify_alert_refund_spike)
  * [`bigcommerce.bc_alert_refund_spike`](/nerve-centre/bigcommerce/bc_alert_refund_spike)
</details>

## Known limitations / merchant FAQs

**The alert fired but my Stripe dashboard shows normal refund volume, why?**
Possible causes. First, store credit: a Credit Memo with `refund_to_store_credit = true` issues credit but does not refund the payment processor. Adobe records the memo, Stripe sees nothing. Second, manual cash refunds (rare in ecommerce but happens for B2B and high-touch merchants): the merchant refunded via bank transfer outside Stripe, recorded the Credit Memo for accounting accuracy, but Stripe is uninvolved. Third, sync lag: Stripe webhooks land within seconds, but if the integration is queueing them, you may see a brief Adobe-leads-Stripe gap.

**What's the difference between a Credit Memo and a cancellation, and which does this card track?**
A cancellation is `state = canceled` with no payment captured, no goods shipped, no Credit Memo. The customer abandons or the merchant cancels before fulfillment. A Credit Memo is a separate document issued after capture (typically after fulfillment, sometimes pre-shipment) that refunds money. This card tracks Credit Memos only. Cancellations are tracked by [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate). Together they cover the "money-back" surface area; merchants tend to focus on one and miss the other, which is a mistake.

**Adobe Commerce vs Magento Open Source: does this card work on the free edition?**
Yes. Credit Memos exist in both editions and the document structure is identical. The only edition-specific difference: Adobe Commerce's RMA (Returns Merchandise Authorisation) module adds a structured returns-management workflow, but Credit Memos are still the underlying record on either edition.

**Why does the alert use 2x baseline rather than a fixed rate threshold?**
Baseline refund rates vary enormously by category: fashion stores baseline at 15 to 30%, hardware stores at 1 to 3%, B2B accounts under 1%. A fixed 5% threshold would constantly fire on fashion and never on hardware. The 2x multiplier normalises against each merchant's own baseline.

**My multi-store Adobe Commerce, can I get per-Store-View alerts?**
Yes, configure per-Store-View variants. Refund spikes are usually localised; UK consumers may refund a defective batch while US is fine because the defective batch shipped from a UK warehouse. Per-Store-View variants surface the localisation immediately.

**B2B accounts have very low refund rates, will B2B variance trigger false alerts?**
The card has an absolute-count gate (5 memos in the hour) to avoid noise on low-volume streams. B2B going from 0.2 memos/hour baseline to 1 memo/hour is a 5x ratio, but absolute count is below threshold so it doesn't fire. For B2B-only stores, lower the absolute-count gate to 2 or 3 in the manifest.

**Does the alert distinguish partial refunds from full refunds?**
Not in the count. A partial refund (1 of 3 line items returned) counts as one memo, same as a full refund. The companion value-at-risk metric uses Credit Memo `grand_total` which captures the actual amount; a partial memo will show smaller. If you specifically need to monitor full-refund spikes (the worst signal: customer returned everything), filter the manifest to `Credit Memo grand_total = order grand_total`.

**Why is the rate calculated from this hour's orders rather than the original orders being refunded?**
Two approaches are valid. (a) Refunds-this-hour / orders-this-hour: a real-time pulse, captures "are refunds suddenly elevated right now". (b) Refunds-of-orders-from-the-last-30-days / orders-from-the-last-30-days: a quality-of-cohort view. The card uses (a) because the alert is for incident detection. Approach (b) is captured by the [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate) trailing card. Both views matter; this card is for "is the customer service inbox about to flood".

**The viral SKU is converting AND being refunded a lot, do I pause it?**
Not necessarily. If conversion rate is healthy and refund rate is acceptable on a per-SKU basis, the volume of both rising in lockstep is just demand. The alert's job is to flag when refund rate is rising disproportionately, signalling a quality issue. Cross-check [Top Refunded SKUs](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) and customer-feedback channels (reviews, support tickets) before acting.

**Why doesn't Google Analytics agree?**
GA4 attributes purchase events; it does not natively track refunds in the standard ecommerce event model (you can custom-implement refund events via Measurement Protocol but most merchants don't). The card uses Adobe-side server data which is the source of truth for Credit Memos.

***

### Tracked live in Vortex IQ Nerve Centre

*Refund-Rate Spike Alert* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Refund Value, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/refund-value

Refund Value for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> The total monetary value refunded in the period. Aggregates Credit Memo `grand_total` across every Credit Memo created in the window. Magento and Adobe Commerce treat refunds as separate Credit Memo documents, the order's `total_refunded` field is the cumulative sum of all Credit Memos against that order, but this card sums the **memo** values directly so partial refunds and shipping-only refunds are all captured.

|                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **What it counts**                                 | `SUM(creditmemo.grand_total)` over Credit Memos where `created_at` falls inside the period. Each Credit Memo's `grand_total` includes its own `subtotal` (line value refunded) + `shipping_amount` (shipping refunded) + `tax_amount` (tax refunded) − `adjustment_negative` + `adjustment_positive`.                                                                                                                                                                                                                                      |
| **API field**                                      | `grand_total` and `created_at` from the creditmemos index, also `base_grand_total`, `subtotal`, `shipping_amount`, `tax_amount` for the breakdown row. Adobe Commerce REST endpoint: `GET /rest/V1/creditmemos`.                                                                                                                                                                                                                                                                                                                           |
| **Why this approach over `orders.total_refunded`** | The `total_refunded` field on an order is cumulative-to-date; if the order was refunded in three tranches over six months, `total_refunded` shows the running total. Using `SUM(orders.total_refunded WHERE status=refunded)` (the legacy stub query) captures only the orders that ever ended up fully refunded and double-counts the running totals if you slice by order date vs refund date. Summing Credit Memo `grand_total` by Credit Memo `created_at` is the only way to get a clean "refund value posted in this period" figure. |
| **VAT / tax treatment**                            | **Tax-inclusive.** The Credit Memo `grand_total` mirrors the original order: it bundles refunded tax (`tax_amount` on the memo). For UK/EU merchants this is the customer-paid figure. Finance teams who book refunds net of VAT need to subtract `creditmemo.tax_amount`; that figure is exposed via the breakdown table on the card detail panel.                                                                                                                                                                                        |
| **Shipping inclusion**                             | **Included.** A shipping-only Credit Memo (`subtotal=0`, `shipping_amount>0`) contributes its shipping value to this total.                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Discounts**                                      | Customer-paid net is what gets refunded. If the original order had a 20% discount, the refund typically refunds the post-discount line value (Adobe Commerce defaults to this). The `adjustment_positive` and `adjustment_negative` fields let merchants override on a per-memo basis (e.g. add a \$5 goodwill credit to a return); those adjustments are included in `grand_total` and therefore in this card.                                                                                                                            |
| **Adjustment fee**                                 | Adobe Commerce supports a per-memo "Adjustment Fee" that can offset the refund (e.g. a restocking fee deducted from the customer's refund). It reduces `grand_total` and so reduces this card. Always reconcile to the customer's bank statement, not to `subtotal`.                                                                                                                                                                                                                                                                       |
| **Cancelled orders**                               | **Excluded.** Cancellations reverse authorisation pre-capture; no Credit Memo, no contribution here.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Currency**                                       | Uses display currency `grand_total`. Multi-currency merchants get a mixed total which is fine for trend but not for booking. The breakdown row always shows `base_grand_total` for accounting reconciliation.                                                                                                                                                                                                                                                                                                                              |
| **Multi-store scope**                              | Sums all Store Views by default. Configurable via `store_id` filter.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Time window**                                    | `30D vsP`, the rolling 30-day refund value, compared to prior 30-day window.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| **Alert trigger**                                  | None on this card directly. Use [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate) for the normalised version with a threshold.                                                                                                                                                                                                                                                                                                                                                                                             |
| **Roles**                                          | owner, operations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |

## Calculation

```
SUM(total_refunded) WHERE status=refunded
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC apparel merchant on Adobe Commerce 2.4.7 with the B2B Companies module enabled. UK-based, GBP base currency, single Store View. Period: 14 Apr 26 to 13 May 26.

**Credit Memo population for the window:** 188 Credit Memos.

**Value breakdown (sum across all 188 Credit Memos in GBP):**

| Component                                | Value       | Notes                                                                 |
| ---------------------------------------- | ----------- | --------------------------------------------------------------------- |
| `subtotal` (line items refunded)         | £36,420     | the goods being refunded                                              |
| `shipping_amount` refunded               | £1,830      | inc. 24 shipping-only Credit Memos for express upgrades not delivered |
| `tax_amount` refunded                    | £7,650      | 20% VAT on the goods + shipping                                       |
| `adjustment_negative` (restocking fees)  | -£420       | applied to 18 of the 188 memos                                        |
| `adjustment_positive` (goodwill credits) | +£740       | applied to 31 memos                                                   |
| **`grand_total` sum**                    | **£46,220** | this card's headline number                                           |

**Comparison to prior period:**

| Window              | Refund value | Refunded order count | Average refund value |
| ------------------- | ------------ | -------------------- | -------------------- |
| 14 Apr to 13 May 26 | £46,220      | 188                  | £246                 |
| 15 Mar to 13 Apr 26 | £29,140      | 142                  | £205                 |
| **Change**          | **+59%**     | **+32%**             | **+20%**             |

The card's headline number is up 59% but the more telling slice is the 20% jump in average refund value. Operations should investigate whether high-AOV B2B orders are starting to come back. Drilling into the breakdown:

1. **B2B refunds (Customers in any Adobe Commerce Company entity):** £21,400 of the £46,220, or 46% of refund value. B2B is typically \<10% of refund value because B2B orders rarely refund (they raise credit notes against future POs instead).
2. **Cause:** the merchant launched a new wholesale uniform line on 1 Apr 26 with a sizing chart that turned out to be misaligned (suppliers ran 1 size small). 12 B2B accounts returned bulk shipments through April. The pattern is visible in [Top Refunded Products](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers), where 6 of the top 10 refunded SKUs are uniform line items.
3. **Action:** pause the uniform line on the Adobe catalogue, update the sizing chart, contact affected B2B accounts with replacement quotes. Forward to Procurement to chase the supplier on the sizing claim.
4. **GL reconciliation note for Finance:** the Credit Memo `grand_total` includes £7,650 of refunded VAT. Net refund to book against revenue is £38,570; the £7,650 reverses the VAT liability (HMRC will see this on the next return). The card's headline £46,220 is the customer-side figure; Finance should use the breakdown row.
5. **Cross-check Stripe:** [`stripe.stripe_refund_value`](/nerve-centre/kpi-cards/stripe/refund-value) for the same period shows £41,800. The £4,420 gap is PayPal-routed refunds (£3,210) plus 2 manual bank-transfer refunds (£1,210). Sums add up.

## Sibling cards merchants should reference together

| Card                                                                                    | Why pair it with Refund Value                                                                                                                           |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Refund Count](/nerve-centre/kpi-cards/adobe-commerce/refunded-orders)                  | Volume vs value. Diverging signals (count up, value flat) point to lots of small partial refunds; (count flat, value up) points to a few whale refunds. |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                       | The percentage of revenue refunded; volume-normalised so seasonality does not deceive.                                                                  |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)           | Day-by-day shape. Helps catch a one-day batch posting that distorts the 30-day total.                                                                   |
| [Top Refunded Products](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) | The SKU drivers. Concentrate Operations attention where it matters.                                                                                     |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                   | The denominator pair. Refund value as % of revenue is the canonical refund rate.                                                                        |
| [Return Status](/nerve-centre/kpi-cards/adobe-commerce/return-status)                   | Pipeline of in-process RMAs. Today's RMA approvals are tomorrow's Credit Memos.                                                                         |
| [`stripe.stripe_refund_value`](/nerve-centre/kpi-cards/stripe/refund-value)             | Stripe-side gross refund value. Should match the Stripe-paid subset of this card.                                                                       |
| [`paypal.pp_refund_value`](/nerve-centre/kpi-cards/paypal/refund-value)                 | PayPal-side. Sum (Stripe + PayPal + manual) ≈ this card's value.                                                                                        |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Refunds** (Adobe Commerce 2.4.6+). Set the date range to the same period and the "Show By" to "Day" or "Month". The total at the bottom of the report is the figure to reconcile against. Note that this report uses `base_currency` (FX-converted) so it will not match this card's `grand_total` mixed-currency total for international merchants.

For the document-level audit:

> **Sales > Operations > Credit Memos**, sum the "Refunded" column. The grid total at the bottom matches `SUM(grand_total)` of every Credit Memo in the period.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                                                                                                                                                | Direction of divergence                         |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| **Currency**. Reports > Sales > Refunds aggregates in `base_grand_total` (FX-converted); this card uses `grand_total` (display currency). Multi-currency merchants should expect material differences. The breakdown row on the card detail panel shows `base_grand_total` for like-for-like reconciliation.                          | Material for multi-currency stores              |
| **Time-zone**. Admin reports run in the Store View locale; this card runs UTC by default. A Credit Memo created near midnight crosses different day boundaries.                                                                                                                                                                       | ±1 day at edges                                 |
| **Reports indexer lag**. Reports > Sales > Refunds reads from `sales_refunded_aggregated`, a denormalised table refreshed nightly via the Magento reports indexer (`indexer:reindex sales_order_grid` and the reports cron). If the cron has not run today, the report may be 24 hours stale. This card refreshes every 5-15 minutes. | Vortex IQ ahead of stale Reports                |
| **Adjustment fee handling**. The Reports module sometimes excludes `adjustment_negative` from the displayed total depending on the Magento minor version. This card always includes `adjustment_negative` and `adjustment_positive` in `grand_total`.                                                                                 | Magento-version dependent                       |
| **Off-platform refunds**. Refunds issued via gateway dashboards without back-filling a Credit Memo are invisible to both this card and the Admin Credit Memos grid. Bank statement is the only ground truth.                                                                                                                          | Both views under-count vs bank if process leaks |
| **Sync lag**. 5-15 minutes behind the database.                                                                                                                                                                                                                                                                                       | Vortex IQ slightly lower than live Admin        |

**Cross-connector reconciliation (when both connectors are connected for this merchant):**

| Pair                                                                        | Expected relationship                                    | What divergence tells you                                                                                                  |
| --------------------------------------------------------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_refund_value`](/nerve-centre/kpi-cards/stripe/refund-value) | Stripe ≈ Stripe-paid subset of this card                 | If Stripe is higher, refunds are being issued via Stripe Dashboard without Credit Memos in Adobe. The GL will not balance. |
| [`paypal.pp_refund_value`](/nerve-centre/kpi-cards/paypal/refund-value)     | PayPal-paid subset only                                  | Same logic as Stripe scoped to PayPal.                                                                                     |
| Sum of (Stripe + PayPal + manual transfer)                                  | should equal this card's `base_grand_total` to within 1% | Larger gaps signal off-platform refunds slipping through process.                                                          |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same metric exists with platform-specific definitions on other commerce connectors. This is **not** a reconciliation, your Adobe Commerce store does not have a parallel store on those platforms.

  * [`shopify.refund_value`](/nerve-centre/kpi-cards/shopify/refund-value)
  * [`bigcommerce.refund_value`](/nerve-centre/kpi-cards/bigcommerce/refund-value)
</details>

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  This metric exists with the same definition on other commerce platforms. This is **not** a reconciliation, your Adobe Commerce store doesn't have a parallel store on those platforms to compare against. These references exist purely so an agency running clients across multiple platforms can cross-link the same metric across docs.

  * [`shopify.refund_value`](/nerve-centre/kpi-cards/shopify/refund-value)
  * [`bigcommerce.refund_value`](/nerve-centre/kpi-cards/bigcommerce/refund-value)
</details>

## Known limitations / merchant FAQs

**Why does this card use Credit Memo `grand_total` instead of `orders.total_refunded`?**
Because `total_refunded` on the order is a running cumulative; an order refunded in three tranches has a single `total_refunded` field that grows over time, with no record of the per-event amounts. To get a clean "refund value posted in this period" number, you must sum each Credit Memo's `grand_total` by the memo's own `created_at`. The legacy stub query `SUM(total_refunded) WHERE status=refunded` was incorrect for partial-refund cases and is replaced by Credit Memo-side aggregation.

**The merchant says we refunded £50,000 but the card shows £46,220, gap?**
The £3,780 gap is most often: refunded VAT booked separately by Finance, manual gateway-side refunds without Credit Memos, or a handful of `adjustment_negative` restocking fees the merchant treats as "refund-in-spirit" but which reduce the customer-paid figure. Walk through the breakdown row (`subtotal`, `shipping_amount`, `tax_amount`, `adjustment_negative`, `adjustment_positive`) and reconcile component by component.

**Why is shipping refund value separated out?**
Because shipping refunds are operationally different. A shipping refund usually means the carrier failed (express upgrade not delivered) which is a fulfilment problem, not a product problem. Knowing 4% of refund value is shipping vs 75% being product lets Operations route the issue correctly.

**Multi-currency, can I see refund value in my base currency?**
Yes. The card shows `grand_total` (mixed currency, useful for trend) by default. The breakdown row shows `base_grand_total` (FX-converted at order time) for accounting. Both are exposed via the API endpoint.

**Does this include voucher / store credit refunds?**
Yes if the Credit Memo records them as `adjustment_positive`. Adobe Commerce supports refunding to "Store Credit" instead of to the original payment method; the Credit Memo's `grand_total` includes the store-credit portion. If you only want cash refunds, filter on `creditmemo.refund_to_store_credit_amount=0` (configurable in the manifest).

**Can a Credit Memo be issued on a `canceled` order?**
No. Cancellation reverses authorisation pre-capture; nothing was paid, so nothing can be refunded. Adobe Commerce blocks Credit Memo creation on `canceled` orders. Cancellation value is captured separately on [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate).

**Why doesn't Stripe match this card exactly?**
Three causes: (1) PayPal and Authorize.Net refunds are in this card but not in Stripe; (2) manual bank-transfer refunds posted as Credit Memos are in this card but not in Stripe; (3) Stripe-Dashboard-issued refunds without back-filling are in Stripe but not in this card. Sum (Stripe + PayPal + manual) should equal this card to within 1% if process is clean.

**My 90-day refund value is £200k, my 30-day is £46k. Why isn't 30-day a clean third?**
Because refunds are seasonal too. Returns spike after Black Friday, January, and post-Christmas. A 30-day window in mid-April is structurally lower than a 30-day in mid-January. Use day-of-week and month-on-month comparisons rather than expecting linear scaling.

**A Finance audit shows the GL refund line is higher than this card. What's wrong?**
Most likely Finance is including VAT in the GL refund line at full value (no VAT carve-out) while this card's GL-friendly view (`grand_total - tax_amount`) excludes refunded VAT. Or Finance is including unfunded "goodwill" credits that were issued as in-store credit rather than cash refunds. Walk the breakdown.

***

### Tracked live in Vortex IQ Nerve Centre

*Refund Value* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Refunded Orders, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/refunded-orders

Refunded Orders for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Count of distinct Credit Memo documents created in the period. In Magento and Adobe Commerce a refund is **never** a status flip on the order; it is a separate Credit Memo document that points back to the original order. This card counts those Credit Memos, not orders that ended up refunded.

|                                 |                                                                                                                                                                                                                                                                                                                                                                                               |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**              | `COUNT(creditmemo_id)` over `creditmemos` where `created_at` falls inside the period. One order can have multiple Credit Memos (partial refunds), each is counted once. Adobe Commerce REST endpoint: `GET /rest/V1/creditmemos`.                                                                                                                                                             |
| **API field**                   | `entity_id` (Credit Memo PK) and `created_at` from the creditmemos index. The parent order is referenced via `order_id`.                                                                                                                                                                                                                                                                      |
| **Credit Memo vs order status** | The card counts Credit Memo documents. The original order's `status` may still read `complete` even after a full refund, Magento does not auto-flip the order to `closed` unless the refund covers the whole `grand_total`. So a status filter of `status=refunded` (the legacy stub query) misses partial refunds entirely. This is the most common reconciliation question merchants raise. |
| **VAT / tax treatment**         | n/a for a count card. The Credit Memo document itself contains `tax_amount` but this card sums document count, not value. See [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value) for the monetary version.                                                                                                                                                                   |
| **Shipping inclusion**          | n/a for the count. A Credit Memo that only refunds shipping (`shipping_amount` field) is still one document, still counted once.                                                                                                                                                                                                                                                              |
| **Discounts**                   | n/a for the count.                                                                                                                                                                                                                                                                                                                                                                            |
| **Cancelled / voided orders**   | **Excluded.** A `canceled` order generates no Credit Memo (cancellation reverses authorisation before capture). Only captured-then-refunded orders produce a Credit Memo. This card does not count `canceled`; use [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate) for those.                                                                                   |
| **Partial refunds**             | **Each Credit Memo is one count.** An order with three partial refunds counts three. Merchants who want "orders that had any refund" need a `COUNT(DISTINCT order_id)` variant, currently roadmapped as a sibling card.                                                                                                                                                                       |
| **Source channel**              | All Adobe Commerce channels included (storefront, Admin-created, B2B portal, Marketplace if installed). Off-platform refunds (refund issued by the gateway directly without a Credit Memo) are **not** counted, those show in [`stripe.stripe_refund_count`](/nerve-centre/kpi-cards/stripe/refund-count) but not here.                                                                       |
| **Multi-store scope**           | Sums across all Store Views by default. Per-Store-View slicing available via `store_id` filter.                                                                                                                                                                                                                                                                                               |
| **Time window**                 | `30D vsP` (rolling 30-day, compared to prior 30-day window).                                                                                                                                                                                                                                                                                                                                  |
| **Alert trigger**               | None on this card. Volatility is captured on [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate) instead.                                                                                                                                                                                                                                                                       |
| **Roles**                       | owner, operations                                                                                                                                                                                                                                                                                                                                                                             |

## Calculation

```
COUNT(status=refunded)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A mid-market homewares merchant on Adobe Commerce 2.4.7 with B2B Companies enabled, running 14 Apr 26 to 13 May 26 (rolling 30 days).

**Raw counts pulled from `GET /rest/V1/creditmemos`:**

| Slice                                                                    | Credit Memo count | Notes                                                      |
| ------------------------------------------------------------------------ | ----------------- | ---------------------------------------------------------- |
| All Credit Memos in window                                               | 412               | one document per partial or full refund                    |
| Of which: full refunds (covered original `grand_total`)                  | 247               | order's `status` typically flipped to `closed`             |
| Of which: partial refunds                                                | 165               | order's `status` usually stays at `complete`               |
| Of which: shipping-only Credit Memos (`subtotal=0`, `shipping_amount>0`) | 38                | "we owe you the express upgrade you didn't get"            |
| Of which: tax-only adjustments                                           | 12                | post-Avalara reconciliation Credit Memos issued by Finance |
| **This card reports**                                                    | **412**           | every Credit Memo counted once                             |

**Distinct orders affected:** 358 (some orders had 2 or 3 Credit Memos each).

**Why the difference matters:** if the merchant runs the legacy report query `COUNT(orders WHERE status=refunded)`, they would see roughly 247, the count of full-refund orders that flipped to `closed`. The 165 partial-refund Credit Memos and the 38 shipping-only memos are invisible to a status-based count. Operations sees a benign "247 refunds this month" while Finance sees "412 Credit Memos posted this month, \$84,200 net refund value". Two truths, two systems. This card surfaces the document count which is the figure the Finance team needs for posting to the GL.

**Comparison to prior 30 days (`vsP`):**

| Window              | Credit Memos | Distinct orders | Avg Credit Memos per refunded order |
| ------------------- | ------------ | --------------- | ----------------------------------- |
| 14 Apr to 13 May 26 | 412          | 358             | 1.15                                |
| 15 Mar to 13 Apr 26 | 296          | 281             | 1.05                                |
| **Change**          | **+39%**     | **+27%**        | partials accelerating               |

The card's headline number is up 39% but the deeper signal is the rise in average Credit Memos per refunded order from 1.05 to 1.15. That's a 10% jump in partial-refund frequency, often a sign that warehouse pick errors or wrong-size shipments are increasing. Operations should drill into [Top Refunded Products](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) to see which SKUs are driving the partial-refund pattern.

## Sibling cards merchants should reference together

This count card is the volume signal; pair it with the value, rate, and root-cause cards to interpret it.

| Card                                                                                    | Why pair it with Refunded Orders                                                                                                                                                                  |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)                     | Counts vs dollars. A spike in count with flat value is small partial refunds (often shipping disputes). Spike in value with flat count is one whale refund.                                       |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                       | Normalises by order volume so seasonal traffic doesn't masquerade as a refund problem.                                                                                                            |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)           | Day-by-day shape. A Tuesday spike often signals a Monday batch of pick errors caught next-day.                                                                                                    |
| [Top Refunded Products](/nerve-centre/kpi-cards/adobe-commerce/top-refunding-customers) | The SKU-level cause. Concentrate Operations attention on the 3-5 SKUs producing 50% of refunds.                                                                                                   |
| [Return Status](/nerve-centre/kpi-cards/adobe-commerce/return-status)                   | RMA workflow status. Adobe Commerce B2B uses RMA for in-process returns; refunds are the downstream event.                                                                                        |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)           | Pre-capture cancellations and post-capture refunds are different problems. Cancellation = order never paid for; refund = paid then reversed.                                                      |
| [`shopify.refund_count`](/nerve-centre/kpi-cards/shopify/refunded-orders)               | Same metric on Shopify, where refunds are stored on the order itself rather than as a separate document. Useful for agencies running cross-platform clients.                                      |
| [`stripe.stripe_refund_count`](/nerve-centre/kpi-cards/stripe/refund-count)             | The payment-processor side. If Stripe refund count exceeds Adobe Commerce Credit Memo count, somebody is refunding on Stripe Dashboard without back-filling a Credit Memo, the GL will not match. |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

The canonical Credit Memo grid:

> **Sales > Operations > Credit Memos** with the "Created" date filter set to your period. The grid lists every Credit Memo with `creditmemo_id`, `order #`, `created_at`, and `refunded` amount. The row count at the bottom of the grid should match this card.

If the Credit Memos menu item is missing, the admin user lacks the `Magento_Sales::creditmemo` ACL. Have a Super Admin add it under **System > Permissions > User Roles**.

For the order-level view (which orders had any refund):

> **Sales > Orders** with the **Status** column filtered to `Closed` (full refunds) plus **Status = Complete** with the additional condition that the order has a Credit Memo. Adobe Commerce does not expose "has Credit Memo" as a default filter, so an exact reconciliation requires either a custom report or the **Sales > Operations > Credit Memos** grid.

Other Admin views that look relevant but aren't:

* **Reports > Sales > Refunds** in 2.4.6+: aggregates by day, not by document count. Useful for trend, not exact reconciliation.
* **Dashboard tile "Last Orders"**: limited to 5 rows; not aggregated.
* **Reports > Sales > Tax**: tax slice only, ignores non-tax Credit Memos.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                                                                                                                               | Direction of divergence                                      |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| **Time-zone**. The Credit Memos grid uses the Admin user's locale timezone (set via `Stores > Configuration > General > Locale Options`). This card uses UTC unless overridden. A Credit Memo created at 23:00 PST shows on different days.                                                                          | ±1 day at edges of period                                    |
| **Pending Credit Memos**. A Credit Memo started in Admin but never submitted (the form was abandoned) does not exist as a document, neither in the grid nor here. No divergence expected.                                                                                                                            | None                                                         |
| **Off-platform refunds**. A refund issued via Stripe Dashboard, PayPal Resolution Center, or Authorize.Net Virtual Terminal directly without back-filling a Credit Memo in Adobe is invisible here. The merchant's bank statement will show the refund; this card and the Admin Credit Memos grid will both miss it. | This card under-counts vs bank if off-platform refunds occur |
| **Multi-store scope**. The Admin Credit Memos grid defaults to "All Store Views"; this card matches that by default. If an Admin user has scope-restricted access (only one Store View), their grid will show fewer rows than this card.                                                                             | Vortex IQ ≥ scoped Admin grid                                |
| **Sync lag**. The OpenSearch index trails the database by 5-15 minutes. A Credit Memo posted in the last quarter-hour may not appear here yet.                                                                                                                                                                       | Vortex IQ slightly lower than live Admin                     |
| **Soft-deleted Credit Memos**. Adobe Commerce does not soft-delete by default, but customised installs sometimes do. A custom delete flag would hide rows from one view but not the other.                                                                                                                           | Custom-install dependent                                     |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                                   | Expected relationship                                                                                                 | What divergence tells you                                                                                                                                                                                                                                            |
| -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_refund_count`](/nerve-centre/kpi-cards/stripe/refund-count)            | Stripe ≈ this card for Stripe-paid orders. PayPal, manual Authorize.Net, and bank-transfer refunds are not in Stripe. | If Stripe shows more refunds than Credit Memos, somebody is refunding on Stripe Dashboard without back-filling Adobe. The GL will not balance. Fix: train the team to always issue refunds via Adobe Admin (which calls the gateway), never directly on the gateway. |
| [`paypal.pp_refund_count`](/nerve-centre/kpi-cards/paypal/refund-count)                | PayPal portion only                                                                                                   | Same logic as Stripe, scoped to PayPal-paid orders.                                                                                                                                                                                                                  |
| [`google_analytics.ga_refund_events`](/nerve-centre/google_analytics/ga_refund_events) | GA4 sees only refund events that the storefront fires, often \<50% of total                                           | GA4's refund attribution is unreliable; do not reconcile, use as directional only.                                                                                                                                                                                   |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same metric exists with platform-specific definitions on other commerce connectors. This is **not a reconciliation**; your Adobe Commerce store does not have a parallel Shopify or BigCommerce store.

  * [`shopify.refund_count`](/nerve-centre/kpi-cards/shopify/refunded-orders)
  * [`bigcommerce.refund_count`](/nerve-centre/kpi-cards/bigcommerce/refunded-orders)
</details>

## Known limitations / merchant FAQs

**Why does this card disagree with `Sales > Orders` filtered to `status=refunded`?**
Because Magento and Adobe Commerce do not auto-flip an order to `refunded` (or `closed`) on partial refund. A partial Credit Memo leaves the order's status at whatever it was (usually `complete`). A status-based filter only catches full refunds; this card catches every Credit Memo. Expect this card to be 30-60% higher than a status-based count for typical merchants.

**Is one order with three Credit Memos counted three times?**
Yes. The headline metric is Credit Memo count, not refunded-order count. If you specifically want "orders that had at least one refund", use the `COUNT(DISTINCT order_id)` variant (currently roadmapped, ping support to enable for your workspace).

**A refund was issued on Stripe directly without a Credit Memo, why isn't it counted?**
Adobe Commerce only sees Credit Memos. A refund issued in Stripe Dashboard without going back to Adobe is invisible here. The fix is process-level: train Customer Service to always issue refunds via Adobe Admin (Sales > Orders > \[order] > Credit Memo), which then calls the gateway under the hood. This keeps Adobe, the gateway, and the GL in sync.

**Why is shipping-only Credit Memos a thing?**
Common scenarios: customer paid for express shipping but received standard, the merchant issues a Credit Memo for the shipping difference only (`subtotal=0`, `shipping_amount>0`). Adobe Commerce supports this natively in the Credit Memo form. It is one document, one count.

**My multi-store Adobe Commerce, can I see Credit Memos per Store View?**
Yes. By default this card sums all Store Views. To slice by Store View, configure the manifest filter on `store_id`. The Admin Credit Memos grid offers the same Store View filter at the top of the page.

**Why does the Reports > Sales > Refunds total not match this card?**
That report aggregates monetary refund value, not document count. It also re-aggregates from the `sales_refunded_aggregated` denormalised table which Magento refreshes nightly via `magento/module-reports`. If the indexer has not run today, the report can be 24 hours stale; this card is 5-15 minutes behind real-time.

**Can a Credit Memo exist on a `canceled` order?**
No. Cancellation reverses payment authorisation before capture; there is nothing to refund and Adobe blocks Credit Memo creation on `canceled` orders. The two state machines are mutually exclusive at the document level.

**What about RMA returns? Are those counted here?**
RMA is a workflow stage that *precedes* refund. An order in RMA `Pending Approval` has no Credit Memo yet, so it does not count. Once the RMA is approved and the refund is issued, a Credit Memo is created and counts here. See [Return Status](/nerve-centre/kpi-cards/adobe-commerce/return-status) for the upstream workflow.

**Why does today's number sometimes drop?**
It does not, Credit Memos are immutable once created. If the count drops between two refreshes, the indexer was running mid-refresh and the cached row count was momentarily inconsistent. Wait one full refresh cycle (15 minutes) and it stabilises.

***

### Tracked live in Vortex IQ Nerve Centre

*Refunded Orders* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Repeat Customer Rate, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate

Repeat Customer Rate for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Percentage of customers who placed more than one order during the rolling 90-day window. Defined as `COUNT(customers WITH 2+ orders in window) ÷ COUNT(customers in window) × 100`. Headline retention KPI. Industry-typical: 25-40% for DTC, 50-80% for B2B-leaning Adobe stores.

|                                      |                                                                                                                                                                                                                                                                        |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                   | The set of distinct customers who ordered in the period; of those, how many ordered more than once. Aggregated by `customer_id` for registered customers, by `customer_email` for guests. B2B Companies are aggregated by `company_id` if the toggle is enabled.       |
| **API field**                        | `customer_id`, `customer_email`, `extension_attributes.company_attributes.company_id`, `created_at`, `entity_id` from `GET /rest/V1/orders`.                                                                                                                           |
| **In-window vs cohort framing**      | This is the **in-window** repeat rate: customers who placed 2+ orders within the 90-day window. Different from cohort retention which asks "of customers who first ordered in March, what % returned by April?". Both useful; this card is the simpler in-window view. |
| **VAT / tax / shipping / discounts** | n/a, the card is a customer count ratio.                                                                                                                                                                                                                               |
| **Refunds**                          | A refunded order still counts as an order placed; the customer is still counted.                                                                                                                                                                                       |
| **Cancelled orders**                 | Included by default. A customer who placed 1 captured + 1 cancelled order is "2 orders" → repeat. Toggle to exclude cancelled for "captured-only" repeat rate.                                                                                                         |
| **B2B Company toggle**               | Many B2B Companies have multiple buyers (head office + branch); aggregating to `company_id` reveals true Company-level repeat behaviour. Without the toggle, each buyer is counted separately, deflating B2B repeat rate.                                              |
| **Guest dedup caveat**               | Guests with two emails (work + personal, typo) appear as two distinct customers, deflating the rate. Real repeat rate is typically 5-10 percentage points higher than measured.                                                                                        |
| **Currency**                         | Unitless; no currency.                                                                                                                                                                                                                                                 |
| **Multi-store scope**                | All Store Views by default. A customer who shops on UK and US Store Views (same email) is counted once across views.                                                                                                                                                   |
| **Time window**                      | `90D` rolling. Shorter (30D) under-counts repeat (not enough time to repeat); longer (365D) over-counts (includes churned customers). 90D is the marketing standard.                                                                                                   |
| **Alert trigger**                    | `<25% (Tier-1 retention floor)`. Below 25% indicates an acquisition-heavy growth pattern with weak retention; over the long term, unsustainable.                                                                                                                       |
| **Sentiment key**                    | `repeat_rate`                                                                                                                                                                                                                                                          |
| **Roles**                            | owner, marketing                                                                                                                                                                                                                                                       |

## Calculation

```
COUNT(orders > 1 by customer_email) / CARDINALITY(customer_email)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC industrial-supplies merchant on Adobe Commerce 2.4.7. 90-day rolling, 14,420 orders, 9,820 distinct customers/companies (after Company aggregation).

**Customer-level repeat:**

| Slice                                    | Distinct customers | 2+ orders | Repeat rate                |
| ---------------------------------------- | ------------------ | --------- | -------------------------- |
| All customers (Company-aggregated)       | 9,820              | 2,640     | **26.9%**                  |
| DTC consumers only                       | 8,640              | 1,820     | 21.1%                      |
| B2B Companies only                       | 1,180              | 820       | 69.5%                      |
| Wholesale Customer Group (subset of B2B) | 950                | 740       | 77.9%                      |
| VIP Customer Group                       | 250                | 230       | 92.0%                      |
| Guest checkouts (by email)               | 1,840              | 110       | 6.0%                       |
| Excluding cancelled-only customers       | 9,720              | 2,610     | 26.9% (no material change) |

**Comparison to prior 90 days:**

| Window                 | Repeat rate | Threshold (25%) |
| ---------------------- | ----------- | --------------- |
| 13 Feb to 13 May 26    | 26.9%       | clean (above)   |
| 14 Nov 25 to 12 Feb 26 | 24.2%       | breached        |
| **Change**             | **+2.7 pp** | improving       |

**Insight pattern:**

1. **Headline 26.9% is just above the 25% floor.** Healthy for a B2B+DTC mix. Below 25% would have triggered the sentiment alert.
2. **DTC repeat at 21.1% drags the headline down.** This is the lever to pull, post-purchase email flows, second-order incentives, replenishment-product subscriptions.
3. **B2B repeat at 69.5%** is healthy but should be 80%+ for industrial-supplies (where buyers reorder consumables). The 20-30% non-repeat B2B Companies are either: (a) one-off purchasers, (b) accounts that went silent (cross-link with [B2B Account Silence](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet)), or (c) accounts that re-routed to a different supplier.
4. **VIP Customer Group at 92%** is the loyalty cohort working as designed. Use this as the upper-bound benchmark.
5. **Guest 6% repeat is low because of email-dedup caveat.** A guest using multiple emails appears as multiple "1 order" customers. The actual same-person repeat rate among guests is closer to 12-15%; the card under-counts.
6. **Improvement of +2.7 pp over the prior period** suggests retention work is landing. Cross-link with [`klaviyo.flow_revenue_share`](/nerve-centre/klaviyo/flow_revenue_share) for email-flow attribution.
7. **Cross-link with [Customer Order Frequency](/nerve-centre/kpi-cards/adobe-commerce/customer-order-frequency)** for the per-bucket distribution that this rate is the headline of.

## Sibling cards merchants should reference together

| Card                                                                                        | Why pair it with Repeat Customer Rate                                       |
| ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [Customer Order Frequency](/nerve-centre/kpi-cards/adobe-commerce/customer-order-frequency) | The per-bucket distribution this rate summarises.                           |
| [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers)                       | The first-time-buyer cohort; the conversion-to-repeat target.               |
| [Customer Count](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)                   | The denominator.                                                            |
| [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)         | Customer count over time; pair with this card for retention vs acquisition. |
| [B2B Account Silence](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet)       | B2B-specific retention card; flags the silent accounts.                     |
| [Churn Risk](/nerve-centre/kpi-cards/adobe-commerce/customer-churn-risk)                    | The forward-looking version of repeat rate.                                 |
| [Customer Segments](/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments)         | Customer Group breakdown.                                                   |
| [`shopify.repeat_rate`](/nerve-centre/kpi-cards/shopify/repeat-customer-rate)               | Cross-platform peer.                                                        |
| [`klaviyo.flow_revenue_share`](/nerve-centre/klaviyo/flow_revenue_share)                    | Email-flow attribution; pair to attribute repeat-rate lift.                 |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Customers > Customers by Number of Orders**. Lifetime view of repeat behaviour. Lifetime ≠ in-period; use as a directional check.

For the in-period customer set:

> **Sales > Orders** filtered to the period; export to CSV; group by `Customer Email`; count distinct emails with 2+ orders. Compare to total distinct emails. Tedious; the card is faster.

For B2B Companies:

> **Customers > Companies > \[Company]** > Orders tab for each Company. Manual, only practical for spot-checks.

**Why our number may legitimately differ from a manual Admin computation:**

| Reason                                                                                                                                                                                                                  | Direction of divergence       |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- |
| **Lifetime vs in-period framing**. Reports > Customers > Customers by Orders is lifetime; this card is 90D rolling. A customer with 50 lifetime orders but only 1 in the last 90 days is "repeat" lifetime, "new" here. | Material difference           |
| **B2B Company aggregation**. Default in this card is per-Company; Admin doesn't aggregate.                                                                                                                              | Card higher when toggle is on |
| **Guest dedup**. Card aggregates guests by email; multiple emails inflate the unique-customer count.                                                                                                                    | Card under-counts repeat      |
| **Cancelled inclusion**. Card includes by default; manual count usually excludes.                                                                                                                                       | Standard                      |
| **Time-zone, sync lag**. Standard.                                                                                                                                                                                      | Minor                         |

**Internal identity:**

`repeat_rate = COUNT(customers in period WITH 2+ orders) ÷ COUNT(customers in period) × 100`

Component cards (self-consistency):

* [`adobe_commerce.customer_count`](/nerve-centre/kpi-cards/adobe-commerce/unique-customers)
* [`adobe_commerce.order_frequency`](/nerve-centre/kpi-cards/adobe-commerce/customer-order-frequency) (sum of "2 orders" + "3-5" + "6-10" + "11+" buckets ÷ total = repeat rate)

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                                                 | Expected relationship                                                                                             | What divergence tells you                                                              |
| ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| [`klaviyo.repeat_segment_size`](/nerve-centre/klaviyo/repeat_segment_size)                           | Klaviyo's "2+ orders" segment should match this card's repeat-customer count                                      | Material gaps mean the order-event sync from Adobe to Klaviyo has data quality issues. |
| [`google_analytics.ga_returning_users_rate`](/nerve-centre/google_analytics/ga_returning_users_rate) | GA4 returning-user % is session-cookie based; usually higher than this card (sessions repeat more than orders do) | Don't reconcile directly; treat as directional.                                        |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.repeat_rate`](/nerve-centre/kpi-cards/shopify/repeat-customer-rate)
  * [`bigcommerce.repeat_rate`](/nerve-centre/kpi-cards/bigcommerce/repeat-customer-rate)
</details>

## Known limitations / merchant FAQs

**My DTC repeat rate is 21%, is that bad?**
Below the 25% Tier-1 floor, yes. DTC ecommerce typically should run 25-40%. Below 25% suggests acquisition is winning new customers but they're not coming back, classic "leaky bucket" growth. Investigate post-purchase email flows, second-order incentive thresholds, and product-quality (refund rate, NPS).

**B2B repeat at 70% but I think it should be higher, why?**
Two main causes: (1) Companies that went silent (cross-link [B2B Account Silence](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet)); (2) buyers within a Company who place once-per-quarter, falling outside the 90-day window. For B2B-heavy industrial supply, target 80%+. Use `Company` aggregation toggle for the right number.

**Why use 90 days and not 30 or 365?**
30 days under-counts repeat (not enough time for a second purchase). 365 days over-counts (includes anyone who bought 11 months ago who may have churned by now). 90 days is the marketing-standard balance for ecommerce.

**Guest dedup is undercounting my repeat rate, can I fix?**
Vortex IQ supports identity-resolution as an opt-in feature: matches guests by IP + credit-card-fingerprint + email-similarity to dedupe. Adds 5-10 percentage points to most merchants' apparent repeat rate. Contact support to enable.

**Wholesale Customer Group at 78% repeat, should we leave it?**
B2B Wholesale should approach 90%+ for healthy retention. 78% means \~20% of Wholesale accounts didn't repeat in 90 days, that's a churn risk. Cross-link with [B2B Account Silence](/nerve-centre/kpi-cards/adobe-commerce/b2b-accounts-gone-quiet) for the at-risk list.

**A customer placed 1 order, refunded the next day, do they count as 1 or 0 customers?**
1 customer (they ordered). They count for 1 in the denominator. If they later return for a 2nd order, they'd count for the numerator (2+ orders). Refund is a creation-time event; this card uses creation-time identity.

**My multi-store, can I see repeat per Store View?**
Yes. Filter by `store_id`. UK and US have very different repeat patterns (UK B2B-heavy, US DTC-heavy in this hypothetical).

**Why does the rate sometimes go down day-to-day?**
The denominator includes new customers who are inherently "1 order" until they return. A burst of new acquisition (e.g. a successful PR placement) deflates the rate temporarily. Use 7-day rolling on the rate itself for trend; the underlying retention behaviour didn't change.

**Klaviyo says my repeat rate is 35%, this card says 26.9%, gap?**
Klaviyo computes repeat from `placed_order` events; if event sync from Adobe to Klaviyo is incomplete, Klaviyo sees fewer customers and inflates the rate. Or Klaviyo uses a different window. The card uses Adobe's order index directly, more reliable.

**Cancelled-only customers, are they "real"?**
A customer who only ever placed cancelled orders (no captured) is debatable. The card includes them by default in the denominator, which slightly deflates the rate. Toggle to exclude for "captured-only" view; usually changes the rate by \<1 pp.

***

### Tracked live in Vortex IQ Nerve Centre

*Repeat Customer Rate* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Revenue at Risk (active incidents), Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/revenue-at-risk

Live $/min loss while incidents are open. Adobe merchants disproportionately run observability stacks, this is a high-hit-rate kill-shot. How to read it, ...

**Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> Live \$/min loss while incidents are open. Adobe merchants disproportionately run observability stacks, this is a high-hit-rate kill-shot.

## At a glance

> Live dollars-per-minute revenue loss while one or more observability incidents (Datadog, New Relic, PagerDuty, Adobe Commerce Cloud Pro) are open. Multiplies the typical per-minute Adobe `grand_total` rate (calibrated from the prior 4 weeks of same-DOW same-hour data) by the duration each incident has been open. Adobe Commerce merchants disproportionately run observability stacks; this is a kill-shot card for ops and finance.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | For each open incident in connected observability tools (Datadog monitor, New Relic alert, Adobe Commerce Cloud Pro alert), compute (incident\_duration\_minutes × baseline\_revenue\_rate\_per\_minute), where baseline rate = median Adobe `SUM(grand_total)` for the same hour-of-week in the prior 4 weeks. Sum across all open incidents. Returns USD (or the merchant's primary currency).                                                                                          |
| **API field**                                          | Adobe denominator: `grand_total` from `GET /rest/V1/orders` for the baseline calculation. Incident duration: from the connected observability tool (Datadog `monitor.created` / `monitor.resolved`, New Relic `incident.opened_at` / `closed_at`, etc.).                                                                                                                                                                                                                                  |
| **VAT / tax treatment**                                | **Tax-inclusive on the baseline.** Adobe `grand_total` already includes `tax_amount`. The dollar-per-minute figure represents what the customer would have paid (gross of tax remittance); ops and finance often want this, the lost top-line, not the post-tax recoverable.                                                                                                                                                                                                              |
| **Shipping inclusion**                                 | **Included on the baseline.** `grand_total` adds `shipping_amount`. Lost orders weren't going to be free-shipping orders, so including shipping is right.                                                                                                                                                                                                                                                                                                                                 |
| **Discounts**                                          | Already deducted on the baseline (post-promo `grand_total`). The card represents lost revenue at the typical promotional level, not at hypothetical full-price.                                                                                                                                                                                                                                                                                                                           |
| **Credit Memo refund treatment**                       | **NOT subtracted on the baseline.** `grand_total` is gross of refunds. Refund-heavy merchants will see this card slightly overstate true at-risk revenue (some lost orders would have been refunded anyway). For most merchants the bias is \<5%.                                                                                                                                                                                                                                         |
| **`state` machine inclusion**                          | **All states included on the baseline.** That covers `new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, `payment_review`. The Adobe quirk: a baseline calibrated on a high-`pending_payment` store inflates the at-risk figure (it assumes those `pending_payment` orders represent real lost revenue when many would have failed at the gateway anyway). For high-fail stores, prefer a baseline filtered to `state IN (processing, complete, closed)`. |
| **`pending_payment` quirk**                            | The asymmetric inflation described above. A 5% `pending_payment` rate inflates the at-risk number by \~5%. Consider it an upper bound on a high-fail store.                                                                                                                                                                                                                                                                                                                               |
| **Multi-currency `grand_total` vs `base_grand_total`** | The baseline uses `grand_total` per Store View, then converts each Store View's contribution to the merchant's primary currency at indicative daily FX rates. The total at-risk figure is in primary currency. Material FX moves over a long incident can shift the dollar figure \~1-3%.                                                                                                                                                                                                 |
| **Store View scope (`store_id`)**                      | **All Store Views included by default**, summed and converted to primary currency. If an incident affects only one region (e.g. a US-only CDN failure), the card overstates at-risk because it assumes the loss spans all regions. Configure per-Store-View incident-routing in the manifest for region-localised incidents.                                                                                                                                                              |
| **Time window**                                        | `RT` (real-time, ticks every minute while incidents are open).                                                                                                                                                                                                                                                                                                                                                                                                                            |
| **Alert trigger**                                      | `>$0 (any open incident)`. As soon as any connected observability incident opens, this card lights up. The dollar figure climbs each minute the incident stays open.                                                                                                                                                                                                                                                                                                                      |
| **Roles**                                              | owner, finance, operations, engineering                                                                                                                                                                                                                                                                                                                                                                                                                                                   |

## Calculation

```
SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A multi-region apparel brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views, running Datadog monitors and PagerDuty incident routing. Tuesday 12 Apr 26, 14:00 GMT.

**Baseline calibration** (median of the four prior Tuesdays at 14:00):

| Store View                       | Median hourly `grand_total` | Per-minute baseline                    |
| -------------------------------- | --------------------------- | -------------------------------------- |
| US (USD)                         | \$4,965                     | \$82.75/min                            |
| UK (GBP, ≈ \$1.25 indicative)    | £1,485 ≈ \$1,856            | \~\$30.93/min                          |
| B2B (USD)                        | \$97                        | \$1.62/min (low volume, high variance) |
| **Combined per-minute baseline** |                             | **\~\$115.30/min**                     |

**Active incidents at 14:00:**

| Source        | Incident                                                  | Duration so far                   | At-risk computed                                       |
| ------------- | --------------------------------------------------------- | --------------------------------- | ------------------------------------------------------ |
| Datadog       | "Adobe Commerce checkout latency >5s" (P1)                | 22 min                            | 22 × $115.30 = **$2,536.60\*\*                         |
| PagerDuty     | "Stripe webhook delivery failure" (linked to Datadog)     | 22 min (same root cause, deduped) | already counted above                                  |
| New Relic     | "Adobe Commerce admin login slowness" (P3, internal-only) | 8 min                             | 8 × $115.30 × 0.10 = **$92.24\*\* (P3 weighted at 10%) |
| **This card** |                                                           |                                   | **\~\$2,629** at-risk                                  |

What this is telling the merchant:

1. \*\*The headline $2,629 is the live cumulative loss estimate.** Each minute the P1 incident continues, ~$115 ticks onto the figure. Engineering, ops, and finance see this in real-time; gives the on-call a hard number to cite when prioritising the page.
2. **The Stripe webhook failure deduped against the Datadog checkout-latency incident.** Both are symptoms of the same root cause (gateway-callback path broken). The card avoids double-counting by deduping on PagerDuty's `incident_key` correlation. If the merchant didn't have PagerDuty correlating, both would count and the figure would be inflated by 22 × $115 = $2,536.
3. **The P3 internal-admin incident is weighted to 10% of revenue impact.** A slow admin login doesn't directly stop customers from buying; the card assumes a 10% indirect impact (operations team can't process queued orders as fast). Configurable per merchant.
4. **The baseline assumes business-as-usual hourly cadence.** A planned promo or BFCM peak would understate at-risk; a planned quiet period (Sunday morning) would overstate. The card uses a 4-week median which smooths out one-off spikes but can't anticipate today's specific demand.
5. **The figure assumes 100% of baseline traffic is lost during the incident.** If the incident is partial (say, only US customers affected by a US-only CDN issue), the card overstates by the share of revenue that comes from unaffected Store Views. Configure per-region incident routing in the manifest for accurate localised at-risk figures.
6. **The figure is gross of refunds and includes `pending_payment` baseline orders.** A high-`pending_payment` Adobe store inflates the at-risk by 2-5%. For a "realised cash" at-risk view, recalibrate the baseline to `state IN (processing, complete, closed)`.

## Sibling cards merchants should reference together

This card is the kill-shot. Pair with these to investigate root cause:

| Card                                                                                             | Why pair it with Revenue at Risk                                                                                                                                                                                         |
| ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert)                  | The earlier-firing canary. If this fires alongside Revenue Drop Alert, the incident is genuinely impacting customers. If only Revenue Drop fires without an open incident, your observability isn't catching everything. |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                            | Provides the baseline for the at-risk calculation. Movement on one drives the other.                                                                                                                                     |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)         | If `pending_payment` is spiking during an incident, the gateway callback is broken. Common Adobe-specific failure mode.                                                                                                  |
| [Active Ads on OOS SKUs](/nerve-centre/kpi-cards/adobe-commerce/active-ads-on-out-of-stock-skus) | Long-running incidents may correlate with stock-feed sync failures, OOS ads spike when the catalogue feed stalls.                                                                                                        |
| [Catalogue Drift](/nerve-centre/kpi-cards/adobe-commerce/catalogue-drift)                        | Sister cross-platform card. Drift can be a symptom of upstream incident (failed sync job).                                                                                                                               |
| [`datadog.datadog_open_incidents`](/nerve-centre/datadog/datadog_open_incidents)                 | The numerator on the incident side. Click through to the Datadog incident timeline.                                                                                                                                      |
| [`newrelic.nr_open_alerts`](/nerve-centre/newrelic/nr_open_alerts)                               | New Relic equivalent.                                                                                                                                                                                                    |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume)              | Cross-check: if Stripe revenue is unchanged during an incident, the incident isn't affecting payment. The contrast localises the problem.                                                                                |
| [`google_analytics.ga_sessions_trend`](/nerve-centre/google_analytics/ga_sessions_trend)         | If sessions cratered alongside the incident, it's a customer-facing outage; if sessions are steady, it's a back-office incident.                                                                                         |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

Adobe Commerce Admin doesn't have a native "revenue at risk during incident" view, the closest cross-checks are:

> **Reports > Sales > Orders** (or **Reports > Sales** in 2.4.6+) for the same hour vs. baseline. Set the time range to *Hourly* and look at the latest hour's revenue against the prior week's same hour.

For Adobe Commerce Cloud (PaaS) merchants:

> **Adobe Experience Cloud > Commerce > Site-Wide Analysis Tool** has incident timelines and surface-level performance metrics. Use it for incident causation analysis; not for revenue impact (it doesn't quantify dollar loss).

Other Adobe Commerce Admin views that *look* relevant but aren't:

* **System > Notifications**: internal Adobe Commerce admin notifications (login, indexer status), not customer-facing incidents.
* **System > Tools > Cache Management**: cache state, not incident state.
* **Reports > Sales > Coupons**: irrelevant.
* **Stores > Configuration > Advanced > System**: configuration only.

**Why our number may legitimately differ from a manual revenue-loss calculation:**

| Reason                                                                                                                                                                                                       | Direction of divergence                          |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
| **Time-zone**. Adobe Commerce Admin reports use Store View timezone; the at-risk baseline uses UTC same-DOW same-hour. The 4-week baseline window endpoints sit at different real-world cutoffs.             | Material on the boundary                         |
| **Currency**. Multi-currency baselines convert to primary currency at indicative daily FX. A material FX move during a long incident can shift the figure \~1-3%.                                            | Material for international merchants             |
| **Store View scope**. Card sums all Store Views; an incident affecting only one region overstates at-risk.                                                                                                   | Vortex IQ higher than per-region manual calc     |
| **`canceled` and `pending_payment`**. Baseline includes these; a manual calc using only "realised" orders gives a smaller at-risk figure.                                                                    | Vortex IQ higher than realised-only baseline     |
| **Incident weighting**. The card weights P3/internal incidents at 10% of full revenue impact. Adjustable per merchant. Manual calcs typically count 0% or 100%, no middle ground.                            | Card lands between extremes                      |
| **Incident dedup**. The card dedups same-root-cause incidents via PagerDuty correlation key. If your incident routing doesn't correlate, manual calcs may inadvertently double-count.                        | Vortex IQ lower than non-deduped manual calc     |
| **Baseline volatility**. The 4-week median smooths weekly seasonality but can't anticipate today's specific demand (a planned BFCM peak, a launched campaign).                                               | Up to ±20% on launch days                        |
| **Sync lag**. Card uses the most recent OpenSearch index sync (5-15 min behind real-time) for baseline; observability tools push incidents in real-time. The numerator is more current than the denominator. | Slight understatement on minute-1 of an incident |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

This card *is* a multi-connector synthesis. The honest reads:

| Pair                                                                                                           | Expected relationship                                         | What divergence tells you                                                                                                                                                                                                          |
| -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) hourly delta during the incident         | Should approximately match the at-risk figure                 | If actual revenue dropped less than the at-risk figure, the incident is partial (some customers still converting). If actual revenue dropped more, the at-risk is understated, the baseline didn't anticipate today's true demand. |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume) hourly during the incident | Stripe drop ≤ Adobe revenue drop                              | A bigger Stripe drop than Adobe drop means orders are being created but the gateway-callback path is failing. Classic Adobe-Stripe webhook outage.                                                                                 |
| [`google_analytics.ga_sessions_trend`](/nerve-centre/google_analytics/ga_sessions_trend)                       | Sessions drop tracks the customer-facing impact               | If sessions cratered, the outage is customer-visible (broken homepage, broken cart, CDN). If sessions are steady, the outage is back-office.                                                                                       |
| [`datadog.datadog_open_incidents`](/nerve-centre/datadog/datadog_open_incidents)                               | Should equal the count of incidents feeding the at-risk total | Mismatch means an observability connector is desynced.                                                                                                                                                                             |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same cross-platform concept exists on other commerce connectors. This is **not a reconciliation**; your Adobe Commerce store doesn't have a parallel Shopify or BigCommerce store.

  * [`shopify.shopify_xc_revenue_at_risk_from_incident`](/nerve-centre/kpi-cards/shopify/revenue-at-risk)
  * [`bigcommerce.bc_xc_revenue_at_risk_from_incident`](/nerve-centre/kpi-cards/bigcommerce/revenue-at-risk)
</details>

## Known limitations / merchant FAQs

**The card shows \$X at-risk but my actual revenue dropped less, why?**
The card is a baseline-projected loss assuming 100% of expected traffic is impacted. Real incidents are usually partial: some customers retry, some browse to product pages but don't checkout, some find their flow works while others fail. The actual loss is typically 30-80% of the at-risk figure. Treat the at-risk number as an upper bound, the headline cost-of-incident if nothing converts.

**The card shows \$X at-risk but my actual revenue dropped MORE, why?**
The baseline didn't anticipate today's specific demand. Common causes: (1) a campaign launched today (paid ads, email blast, influencer drop) that the 4-week median can't see; (2) a holiday or seasonal peak (Black Friday morning); (3) a planned promotion. The card understates at-risk in these conditions. Use the actual revenue gap during the incident as the true loss figure when reporting upward.

**What's the difference between `state` and `status` and does it affect the at-risk figure?**
The baseline uses `grand_total` summed across all `state` values. So `pending_payment`, `canceled`, `holded` orders all contribute to the baseline. A high-`pending_payment` Adobe store inflates the baseline by 2-5%, which inflates the at-risk figure by the same amount. For a "realised cash" at-risk view, recalibrate the baseline to `state IN (processing, complete, closed)`.

**My finance team uses `base_grand_total`, why doesn't this card?**
The baseline could use either. The card defaults to `grand_total` per Store View, FX-converted to primary currency at indicative daily rates. `base_grand_total` (FX-converted at order time, frozen) avoids today's FX noise but undercounts the customer-paid figure. For incident-cost reports to finance, use this card's figure (`grand_total` based) and footnote that it's at customer-paid value, not at remitted-cash value.

**My multi-store Adobe Commerce, can the card know which Store View an incident affects?**
Only if you configure incident routing in the manifest. By default the card assumes any open incident affects all Store Views (combined baseline). For region-localised incidents (a US-only CDN failure), set up per-Store-View incident routing so the card scales the baseline to only the affected region. Otherwise it overstates by the share of revenue from unaffected Store Views.

**Why doesn't Adobe Commerce dashboard show this?**
Adobe Commerce Admin doesn't natively know about your observability tools. Cloud Pro merchants get some incident telemetry but not revenue impact. This card is the synthesis layer that joins Adobe Commerce revenue data to observability incident data, neither tool does it alone.

**My Stripe revenue dropped during the incident but Adobe revenue looks normal, what does that tell me?**
Adobe Commerce is creating order skeletons but the Stripe-side capture-confirmation path is failing. Orders sit in `pending_payment`. The at-risk card may understate the cost because Adobe `grand_total` looks roughly normal (the orders exist, they just never paid). Cross-check with [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) to confirm the `pending_payment` spike, that's the actual revenue loss.

**Why doesn't Google Analytics agree the incident impacted revenue?**
GA4 fires `purchase` events client-side; if the customer's checkout failed before the page loaded, GA4 sees a session abandonment but no purchase event, the revenue is missing on both Adobe and GA4. If GA4 sessions are steady but conversions cratered, the issue is at checkout. If both sessions and conversions are steady, the incident is back-office and customer-invisible.

**Multi-currency: does FX volatility during a long incident affect the figure?**
Yes, but mildly. The card converts each Store View's per-minute baseline to the merchant's primary currency at indicative daily FX. A 1-2% FX move over the course of an hour-long incident shifts the at-risk figure by \~1-3%. For incidents lasting days, FX volatility can compound to 5%+; treat the figure as approximate over multi-day incidents.

**Why does the figure jump up so fast on minute 1?**
Because the per-minute baseline rate is computed straight away, the card doesn't ramp linearly during the first few minutes. If your store does $115/min on a typical Tuesday afternoon, minute 1 of an incident shows $115; minute 2 shows \$230; etc. There's no "warm-up" smoothing. Some merchants prefer a 5-minute moving average; configure in the manifest if needed.

***

### Tracked live in Vortex IQ Nerve Centre

*Revenue at Risk (active incidents)* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Revenue Drop Alert, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert

Catches the canary before the merchant notices, broken checkout, expired payment cert, regional outage. How to read it, why it matters, and how to act on it.

**Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> Catches the canary before the merchant notices, broken checkout, expired payment cert, regional outage.

## At a glance

> A real-time canary alert. Compares this hour's `SUM(grand_total)` to the same hour on the prior 7-day same-day-of-week baseline. Fires when revenue is more than 25% below baseline, signalling a likely outage: broken checkout, expired payment certificate, regional CDN failure, or a Store View configuration change.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | Hour-by-hour `SUM(grand_total)` from the Adobe Commerce orders index, compared against the median of the four prior same-day-of-week hours (e.g. this Tuesday 14:00 vs the prior four Tuesday 14:00s).                                                                                                                                                                                                                                                    |
| **API field**                                          | `grand_total` and `created_at` from the orders index. Adobe Commerce REST endpoint `GET /rest/V1/orders`.                                                                                                                                                                                                                                                                                                                                                 |
| **VAT / tax treatment**                                | **Tax-inclusive by definition.** `grand_total` already includes `tax_amount`. The alert ratio is dimensionless so tax inclusion doesn't bias it; it only matters that current and baseline use the same field.                                                                                                                                                                                                                                            |
| **Shipping inclusion**                                 | **Included.** `grand_total` adds `shipping_amount` (post-discount).                                                                                                                                                                                                                                                                                                                                                                                       |
| **Discounts**                                          | Already deducted, this is the post-promotion customer-paid figure. A discount campaign that legitimately depresses revenue can trip this alert; pair with [Discount % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue) when investigating.                                                                                                                                                                                         |
| **Credit Memo refund treatment**                       | **NOT subtracted.** Credit Memos are separate documents; the original `grand_total` doesn't change after a refund. A refund-heavy hour does NOT trigger this alert via the refund itself; only the underlying inflow matters.                                                                                                                                                                                                                             |
| **`state` machine inclusion**                          | **All states included** (matches [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)): `new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, `payment_review`. The Adobe quirk: a stuck-`pending_payment` outage shows up as steady revenue here even though no cash is being collected; cross-check with payment-processor cards (Stripe/PayPal) to confirm a real outage vs a gateway-callback failure. |
| **`pending_payment` quirk**                            | Included. This is intentional: if Adobe Commerce is creating order skeletons but the gateway never callbacks, `grand_total` looks normal here while Stripe falls off a cliff. The contrast pattern is itself a diagnostic, see the FAQs.                                                                                                                                                                                                                  |
| **Multi-currency `grand_total` vs `base_grand_total`** | Uses `grand_total` (display currency, mixed without FX). Multi-store merchants with multiple base currencies should treat the alert as per-currency-stream; a 25% drop on the USD stream may not reflect anything happening on the GBP stream. The roadmap includes per-Store-View alert variants.                                                                                                                                                        |
| **Store View scope (`store_id`)**                      | **All Store Views summed by default.** A US-only outage on a multi-Store-View store may dilute below the 25% threshold if the UK store is healthy. Set up per-Store-View alert variants for region-specific monitoring.                                                                                                                                                                                                                                   |
| **Time window**                                        | `RT` (real-time, hour-by-hour). The card refreshes every 5-15 minutes as new orders index.                                                                                                                                                                                                                                                                                                                                                                |
| **Alert trigger**                                      | `drop >25% vs prior 7-day same-DOW window`, driven by `sentiment_key: revenue_trend`. The same-DOW comparison handles weekly patterns (Sunday-quiet, Monday-spike) without false positives.                                                                                                                                                                                                                                                               |
| **Roles**                                              | owner, finance, marketing                                                                                                                                                                                                                                                                                                                                                                                                                                 |

## Calculation

```
SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A multi-region fashion brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views. Tuesday 14:00 GMT, the alert just fired.

**Baseline** (median of the four prior Tuesdays at 14:00):

| Tuesday             | Hourly `SUM(grand_total)`                             |
| ------------------- | ----------------------------------------------------- |
| 22 Mar 26           | \$4,810 + £1,420                                      |
| 29 Mar 26           | \$5,120 + £1,580                                      |
| 5 Apr 26            | \$4,640 + £1,510                                      |
| 12 Apr 26           | \$5,210 + £1,460                                      |
| **Median baseline** | \*\*$4,965 + £1,485** (≈ $6,820 at the indicative FX) |

**Current** (this Tuesday 19 Apr 26 at 14:00):

| Stream                        | Hourly revenue                 | vs median                   |
| ----------------------------- | ------------------------------ | --------------------------- |
| US (USD)                      | \$1,840                        | -63%                        |
| UK (GBP)                      | £1,510                         | +1.7%                       |
| B2B (USD)                     | \$0                            | -100% (baseline \~\$120/hr) |
| **Combined (mixed currency)** | \*\*$1,840 + £1,510** ≈ $3,640 | **-47%**                    |

The alert fired because combined revenue is 47% below baseline, well past the 25% threshold. What investigation reveals:

1. **The UK Store View is healthy at +1.7%.** Whatever broke is US-specific.
2. **The B2B portal contributed zero in this hour vs a baseline of \~\$120/hr.** Unusual but B2B order volume is too thin to be conclusive on a single hour.
3. **Pair with [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume) for the same hour:** Stripe shows $0 captured charges on the US stream but the Adobe Commerce side shows $1,840 of `grand_total`. **That gap is the smoking gun**, orders are being created in `pending_payment` but the gateway callback isn't completing. The merchant's Stripe webhook endpoint is misconfigured or down.
4. **The fix:** check Stripe Dashboard > Developers > Webhooks for failed delivery attempts to the merchant's Adobe Commerce endpoint. A 503 or 4xx burst within the last hour confirms it. Manually replay the failed webhooks and the `pending_payment` orders will transition to `processing`.
5. **The order count looks normal** (this is the giveaway). [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders) for the US stream is 12 in this hour vs a baseline of 14, only -14%. That's because Adobe Commerce is *creating* the orders fine; it's only the *capture-confirmation* that's failing. Without the cross-connector check this would look like a plain revenue dip.

## Sibling cards merchants should reference together

This alert is most useful when triangulated against payment-processor and operational cards. Pair with these:

| Card                                                                                          | Why pair it with Revenue Drop Alert                                                                                                                                                                                   |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                         | The underlying value. The alert is a derivative of this card's hourly slice.                                                                                                                                          |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                           | If revenue drops but order count is steady, the issue is basket-side (a popular high-AOV product went out of stock, or a discount code is auto-applying). If order count drops in lockstep, the issue is funnel-side. |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)      | If `pending_payment` is spiking while revenue drops, the gateway callback is failing. This is the diagnostic that distinguishes "real" outage from "callback" outage.                                                 |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)                 | A creeping cancellation rate before the drop suggests upstream payment issues.                                                                                                                                        |
| [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id)                     | Localises the drop. A US-only outage may dilute below the 25% threshold on the combined view.                                                                                                                         |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume)           | The Stripe canary. If Adobe Commerce revenue is flat but Stripe revenue cratered, the gateway-callback path is broken.                                                                                                |
| [`paypal.pp_total_volume`](/nerve-centre/paypal/pp_total_volume)                              | Same as Stripe but for PayPal-routed orders.                                                                                                                                                                          |
| [`google_analytics.ga_revenue_trend`](/nerve-centre/kpi-cards/google-analytics/revenue-trend) | If GA4 revenue cratered too, the issue likely sits before checkout (broken product page, broken cart, redirect loop).                                                                                                 |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

The closest Admin views for ground-truth comparison:

> **Reports > Sales > Orders** (or **Reports > Sales** in 2.4.6+) with the time range set to "Today" and the "Apply" set to *Hourly*. This shows hourly revenue for today which is what the alert evaluates.

For the live order grid:

> **Sales > Orders** with the "Purchase Date" filter set to today and ordered by `created_at` descending. Count rows in the most recent hour against your normal hourly cadence.

Other Adobe Commerce Admin views that *look* relevant but aren't:

* **Dashboard > Last Orders**: only the last 5 orders, not aggregated by hour.
* **Dashboard > Lifetime Sales**: all-time, not windowed.
* **Reports > Sales > Invoiced**: invoiced amount, lags real-time order creation.
* **Reports > Customers**: per-customer aggregation, no hourly breakdown.
* **System > Notifications**: Adobe Commerce internal alerts (admin login, indexer status), not revenue.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                                                                                                                                                                           | Direction of divergence                           |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Time-zone**. Adobe Commerce Admin renders hourly reports in the Store View timezone (`Stores > Configuration > General > Locale Options`). Vortex IQ runs UTC by default. The "current hour" boundary will be shifted depending on the merchant's timezone, an alert that fires at 14:00 UTC may correspond to 09:00 EST or 16:00 CET in the merchant's admin. | ±N hours of timezone offset                       |
| **Currency**. Adobe Commerce hourly reports aggregate in `base_currency` (FX-converted). This card sums `grand_total` without FX. Material for international merchants.                                                                                                                                                                                          | Material for multi-currency stores                |
| **Store View scope**. Admin reports default to a single Store View; this alert sums all Store Views. Set the admin scope to *All Store Views* for like-for-like.                                                                                                                                                                                                 | Vortex IQ higher than per-view admin filter       |
| **`canceled` filter**. Admin reports with status filter "All Orders" include canceled; this alert also includes them. Match unless the merchant overrode the report filter.                                                                                                                                                                                      | Usually no divergence                             |
| **Sync lag**. The alert evaluates on the OpenSearch index's most recent sync (typically 5-15 minutes behind real-time). The Admin order grid is live.                                                                                                                                                                                                            | Vortex IQ slightly stale at the 5-15 min boundary |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

This is where Revenue Drop Alert earns its keep, the cross-connector contrast is itself the diagnostic.

| Card                                                                                          | Expected relationship                            | What divergence tells you                                                                                                                                                                                                                       |
| --------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume)           | Stripe ≤ Adobe Commerce, gap stable hour-on-hour | **If Adobe revenue is flat but Stripe revenue cratered, the gateway callback is failing** (orders sitting in `pending_payment`). **If both cratered together, the issue is upstream of payment** (checkout broken, CDN issue, regional outage). |
| [`paypal.pp_total_volume`](/nerve-centre/paypal/pp_total_volume)                              | Subset of Adobe revenue (PayPal-checkout only)   | If PayPal cratered while Stripe is steady, only the PayPal route is broken (PayPal SDK script blocked, PayPal API token expired).                                                                                                               |
| [`google_analytics.ga_revenue_trend`](/nerve-centre/kpi-cards/google-analytics/revenue-trend) | GA4 ≈ Adobe revenue × (1 − tracking gap)         | If GA4 revenue cratered alongside Adobe revenue, the issue is before checkout. If GA4 sessions cratered (not just revenue), the issue is at the storefront level (broken homepage, redirect loop, CDN).                                         |

**Net contrast pattern:** if you can correlate the alert's exact start time with a Stripe webhook failure burst, an SSL certificate expiry, or a recent code deploy, you have your root cause. Vortex IQ Nerve Centre logs the alert timestamp to UTC second precision for exactly this purpose.

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same alert exists with platform-specific definitions on other commerce connectors. This is **not a reconciliation**; your Adobe Commerce store doesn't have a parallel Shopify or BigCommerce store. These cross-links exist so agencies running multi-platform client books can navigate between equivalent metrics across the docs.

  * [`shopify.shopify_alert_revenue_drop`](/nerve-centre/shopify/shopify_alert_revenue_drop)
  * [`bigcommerce.bc_alert_revenue_drop`](/nerve-centre/kpi-cards/bigcommerce/revenue-drop-alert)
</details>

## Known limitations / merchant FAQs

**The alert fired but my bank deposits look normal, why?**
Three Adobe-specific reasons can cause this: (1) `pending_payment` orders inflate the baseline, so a hour where the gateway callbacks succeeded for once may look like a "drop" even though it's actually a return to normal cash flow; (2) the alert uses `grand_total` (gross of Credit Memos) so a refund-heavy hour doesn't trip the alert via refunds, only via genuine inflow loss; (3) the `pending_payment` quirk works the other way too, if Adobe Commerce keeps creating order skeletons but the gateway is silently failing, this card looks normal while the bank deposits drop. Always cross-check Stripe/PayPal cards alongside this one.

**What's the difference between `state` and `status` and why does it matter for this alert?**
`state` is the system-level lifecycle (8 fixed values). `status` is a configurable user-facing label. This alert uses `state`-agnostic logic, it sums `grand_total` regardless of state, including `pending_payment` and `canceled`. That's intentional: a sudden spike in `canceled` orders won't suppress the alert because the original `grand_total` is still summed. To detect a `canceled`-spike specifically, use [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate) instead.

**Why does the alert use `grand_total` rather than `base_grand_total`?**
`grand_total` is what the customer paid in their display currency. `base_grand_total` is FX-converted to the store's base currency at order time. The alert uses `grand_total` because we want to detect drops in *what the customer pays*, not drops caused by FX-rate movement. A weakening pound that lowers `base_grand_total` but doesn't change `grand_total` shouldn't trigger a revenue-drop alert (it's not actually a revenue drop, it's an FX shift).

**My multi-store Adobe Commerce, can I get a per-Store-View alert?**
Not on this card by default; it sums all Store Views. A US-only outage may dilute below the 25% threshold if the UK is healthy. Configure per-Store-View alert variants by filtering `store_id` in the manifest, or use [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id) for a manual sanity check.

**Why doesn't the alert fire when Adobe Commerce dashboard shows revenue is down?**
Most commonly: (1) the dashboard is scoped to a single Store View while the alert sums all Store Views, the combined view may not be down 25%; (2) the dashboard is in Store View timezone, the alert is in UTC, so "today's revenue" boundaries differ; (3) the dashboard converts to base currency, the alert uses `grand_total`, FX swings can cause one to dip without the other.

**The alert fired but Stripe/PayPal show normal volume, what's happening?**
Counterintuitive but informative: this means orders are being created in Adobe Commerce *but never reaching the payment processor*. Likely causes: (1) `pending_payment` is being captured normally but the success-callback path from gateway to Adobe Commerce is failing, so `grand_total` looks low here even though Stripe captured the money; (2) a checkout-page bug is stopping orders from being created at all, so this card is correct and Stripe matches because nothing is reaching either system. Check Stripe Dashboard > Developers > Webhooks for failed deliveries.

**Why doesn't Google Analytics agree?**
GA4 typically misses 10, 25% of orders (ad blockers, consent, tag-fire failures). For an alert this is *useful*: if GA4 revenue cratered alongside Adobe revenue, the issue is upstream of checkout (broken homepage, broken cart, CDN). If only Adobe Commerce revenue dropped while GA4 sessions and revenue look normal, the issue is at the order-capture layer.

**Why is today's number jumping all over the place between -40% and +20%?**
Hourly numbers are noisy on low-volume stores. The 25% threshold can trip on a single low-traffic hour where one B2B order would have rescued it. The alert uses a 4-week median to smooth weekly seasonality but it can't smooth single-hour volatility on a thin baseline. If your store does \<100 orders/day, set the alert window to 6-hour rolling rather than hourly.

**Why does the alert use same-DOW comparison (this Tuesday vs prior Tuesdays) rather than yesterday?**
Ecommerce traffic is heavily day-of-week patterned. Sunday's revenue is naturally lower than Tuesday's; a "yesterday vs today" comparison would fire constantly on Mondays just because Sunday is quiet. Same-DOW vs same-hour neutralises that pattern and only fires on genuine deviation.

***

### Tracked live in Vortex IQ Nerve Centre

*Revenue Drop Alert* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Revenue Over Time, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time

Revenue Over Time for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Day-by-day revenue (`SUM(grand_total)`) over the last 90 days. The headline time-series card. Plotted with a 7-day moving average overlay to smooth weekly seasonality and a year-over-year overlay for stores with sufficient history.

|                         |                                                                                                                                                                                              |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**      | For each day in the 90-day window: `SUM(grand_total)` over orders created in that day.                                                                                                       |
| **API field**           | `grand_total`, `created_at` from the orders index. Adobe Commerce REST: `GET /rest/V1/orders`.                                                                                               |
| **VAT / tax treatment** | Tax-inclusive (`grand_total`). Toggle to net-of-tax via `grand_total - tax_amount` for VAT-net revenue.                                                                                      |
| **Shipping inclusion**  | Included (in `grand_total`).                                                                                                                                                                 |
| **Discounts**           | Already deducted, post-promotion paid revenue.                                                                                                                                               |
| **Cancelled orders**    | Included by default (matches [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)). Toggle to exclude for "captured-only" view.                                             |
| **Refunds**             | Not subtracted, the card is creation-time. For net-of-refund revenue, subtract Credit Memo `grand_total` from [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time). |
| **Currency**            | Mixed-currency display by default (visual-shape friendly). `base_grand_total` for FX-neutral.                                                                                                |
| **Multi-store scope**   | All Store Views by default. Per-Store-View slicing exposes regional patterns.                                                                                                                |
| **Time window**         | `90D` rolling. Configurable to 30D, 180D, 365D.                                                                                                                                              |
| **Alert trigger**       | None on this card directly. The hourly canary is on [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert).                                                         |
| **Sentiment key**       | `revenue_trend`                                                                                                                                                                              |
| **Roles**               | owner, marketing                                                                                                                                                                             |

## Calculation

```
DATE_HISTOGRAM SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC homewares merchant on Adobe Commerce 2.4.7. UK base, GBP. Snapshot 13 May 26, 90-day rolling.

**Aggregate stats:**

| Metric                               | Value      |
| ------------------------------------ | ---------- |
| Days                                 | 90         |
| Total revenue                        | £2,840,000 |
| Mean revenue / day                   | £31,556    |
| Median revenue / day                 | £30,200    |
| Min day (Sun 7 Apr 26)               | £8,400     |
| Max day (Mon 14 Apr 26, post-Easter) | £52,800    |
| Standard deviation                   | £8,200     |

**Notable events on the chart:**

| Date               | Revenue       | What happened                                          |
| ------------------ | ------------- | ------------------------------------------------------ |
| 24 Feb 26          | £48,200       | flash sale (SPRING25 launched), +52% vs Tue median     |
| 14 Mar 26          | £18,200       | -42% vs Sat median; storefront 502 outage at 11:00 GMT |
| 14 Apr 26          | £52,800       | post-Easter Monday catch-up                            |
| 28 Apr to 5 May 26 | £19k-£24k/day | sustained dip; supplier sizing PR crisis               |
| 6 May 26 onwards   | recovery      | merchant's PR response landed                          |

**Insight pattern:**

1. **Mean ≈ median (£31,556 vs £30,200).** Distribution roughly symmetric over the 90 days. Mean would be much higher than median if a single huge promotion dominated; here it's balanced.
2. **The 14 Mar 502 outage** is the canary; cross-link with [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert) which fired at 11:00. £18,200 day vs £30,200 median = £12,000 lost. Recovery the following day was complete.
3. **The 28 Apr to 5 May sustained dip is the most concerning.** Eight days below the 7-day moving average, with the average itself trending down. £19k average per day vs £30k median = £88,000 cumulative shortfall over the 8 days. Cross-link with [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time) for the parallel uniform-line return wave. Recovery began 6 May after the merchant's PR team posted corrections.
4. **Compare to [Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/orders-over-time):** order count dropped less proportionally during the 28 Apr-5 May dip (\~12% drop in orders vs 35% drop in revenue). That means AOV dropped during the dip, customers were cautious, ordering low-value test purchases rather than full baskets. Healthy sign that demand wasn't lost; just AOV.
5. **YoY overlay:** when 365-day data is available, year-over-year overlay reveals seasonality (Black Friday peak, January post-Christmas dip). The card supports the overlay automatically once history exists.
6. **Cancelled orders included.** The card includes \~1-3% canceled revenue. Toggle to exclude for true cash-flow signal; minor difference but matters for finance.

## Sibling cards merchants should reference together

| Card                                                                                          | Why pair it with Revenue Over Time                                         |
| --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                         | Aggregate of this card.                                                    |
| [Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/orders-over-time)                   | Order count companion; AOV diagnoses divergence.                           |
| [Revenue by Day of Week](/nerve-centre/kpi-cards/adobe-commerce/revenue-by-day-of-week)       | The DOW pattern this card displays.                                        |
| [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time)                 | Subtracted view for net revenue.                                           |
| [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert)               | Real-time canary; this is the historical context.                          |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                             | Per-order average; complements daily revenue.                              |
| [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)           | Customer count over time; pair to disentangle AOV vs traffic.              |
| [`shopify.revenue_over_time`](/nerve-centre/kpi-cards/shopify/revenue-over-time)              | Cross-platform peer.                                                       |
| [`google_analytics.ga_revenue_trend`](/nerve-centre/kpi-cards/google-analytics/revenue-trend) | GA4 traffic-attributed revenue; usually 10-25% lower due to tracking gaps. |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Orders** with "Show By" set to "Day", date range matching this card. The chart and revenue column should approximately match.

> **Dashboard > Sales > Revenue Chart** is a built-in chart on the Admin dashboard. Limited to 30 days and uses base currency. Useful for sanity-checking the most-recent month.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                        | Direction of divergence                        |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| **Currency**. Admin uses `base_grand_total`; this card defaults to mixed `grand_total`.       | Material for multi-currency stores             |
| **Reports indexer lag**. Reports use the nightly `sales_order_aggregated_*` tables.           | Vortex IQ ahead by \~12-24h on most-recent day |
| **Status filter**. Reports default to "Any". Match unless overridden.                         | Standard                                       |
| **Cancelled inclusion**. Card includes by default; Admin Reports include depending on filter. | None expected                                  |
| **Time-zone**. UTC vs Store View locale.                                                      | ±1 day at edges                                |
| **Sync lag**. 5-15 min.                                                                       | Standard                                       |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                                           | Expected relationship                                                | What divergence tells you                                                                                                    |
| ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [`google_analytics.ga_revenue_trend`](/nerve-centre/kpi-cards/google-analytics/revenue-trend)  | GA4 daily revenue ≈ this card × (1 − tracking gap, typically 10-25%) | Persistent \<70% means tracking is broken or consent is blocking events. Look at GA4's \[Realtime] view to confirm.          |
| [`stripe.stripe_charge_volume_over_time`](/nerve-centre/stripe/stripe_charge_volume_over_time) | Stripe daily volume ≤ this card                                      | Gap = orders paid via PayPal, Authorize.Net, manual transfer + orders in `pending_payment`/`canceled` that never hit Stripe. |
| Bank deposit per day (manual)                                                                  | Lags this card by 1-3 days (capture-to-deposit)                      | Deposit shape should mirror this card's shape with a 1-3 day delay.                                                          |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.revenue_over_time`](/nerve-centre/kpi-cards/shopify/revenue-over-time)
  * [`bigcommerce.revenue_over_time`](/nerve-centre/kpi-cards/bigcommerce/revenue-over-time)
</details>

## Known limitations / merchant FAQs

**Why does today's last data point look low?**
Because today is incomplete. The trailing point is in-progress; mentally exclude or wait for the day to close.

**Why is mixed-currency the default?**
For trend visualisation, mixed-currency works because the shape doesn't depend on FX. For absolute reconciliation against finance, switch to `base_grand_total` (FX-converted to store base currency at order time).

**My multi-store revenue per Store View doesn't sum to the headline, why?**
Currency mixing is the most common cause. Switch to base currency for both views. Otherwise: orders without an assigned Store View (rare), or sync-lag making the per-Store-View totals slightly out of sync with the combined.

**Cancelled orders are included by default. Why?**
For the headline trend, cancelled orders represent demand that almost-converted; including them gives a fuller customer-intent picture. For "actual cash received" view, exclude cancelled. The sentiment trend uses the included version.

**A long horizontal line near zero, what's that?**
Either an outage that wiped a day, or a Store View was disabled for that period. Cross-check against deployment logs and the [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) for that day.

**Why doesn't Stripe agree?**
Stripe is a subset (Stripe-paid orders only). PayPal, Authorize.Net, manual bank transfer revenue is in this card but not in Stripe. Sum (Stripe + PayPal + manual) should approximately match this card.

**Year-over-year overlay isn't showing, why?**
Need at least 365 days of order history. The card auto-disables YoY if data is shorter than that.

**Net-of-tax view, when do I use it?**
For Finance dashboards reconciling to GL revenue lines (which are net of VAT). For marketing dashboards (gross is the impressed-on-customer figure), keep the default.

**Net-of-refund view, when?**
For finance "true cash" dashboards. The Vortex IQ workspace can compute net-of-refund automatically when [Refunds Over Time](/nerve-centre/kpi-cards/adobe-commerce/refunds-over-time) is on the same dashboard.

**Why does my Black Friday spike not appear?**
Either the 90-day window doesn't reach back to Black Friday, or you toggled off the year-over-year overlay. Extend the window to 180D or 365D.

***

### Tracked live in Vortex IQ Nerve Centre

*Revenue Over Time* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Adobe Commerce sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag Adobe Commerce KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adobe-commerce) · [Audit Profile](/nerve-centre/kpi-cards/adobe-commerce/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adobe-commerce/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each Adobe Commerce KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **21** of the 59 Adobe Commerce cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                                                                                                          | Direction        | Good | Bad | Unit     |
| ------------------------------------------------------------------------------------------------------------- | ---------------- | ---- | --- | -------- |
| [Average Order Value](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                             | Watch for drops  | 0    | -5  | Currency |
| [B2B AOV vs B2C AOV](/nerve-centre/kpi-cards/adobe-commerce/b2b-aov-vs-b2c-aov)                               | Watch for drops  | 0    | -5  | Currency |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)                                 | Lower is better  | 1    | 3   | %        |
| [Customers with Zero Spend](/nerve-centre/kpi-cards/adobe-commerce/customers-with-zero-spend)                 | Lower is better  | 30   | 60  | Count    |
| [Discount % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue)                           | Lower is better  | 20   | 40  | %        |
| [Email Health](/nerve-centre/kpi-cards/adobe-commerce/email-health)                                           | Higher is better | 95   | 80  | %        |
| [Fulfillment Rate](/nerve-centre/kpi-cards/adobe-commerce/fulfillment-rate)                                   | Higher is better | 95   | 90  | %        |
| [Fulfilment Delay Alert](/nerve-centre/kpi-cards/adobe-commerce/fulfilment-delay-alert)                       | Higher is better | 95   | 90  | Count    |
| [Orders Over Time](/nerve-centre/kpi-cards/adobe-commerce/orders-over-time)                                   | Watch for drops  | 0    | -10 | Count    |
| [Out-of-Stock Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/out-of-stock-spike-alert)                   | Lower is better  | 0    | 5   | Count    |
| [Refund Rate](/nerve-centre/kpi-cards/adobe-commerce/refund-rate)                                             | Lower is better  | 2    | 5   | %        |
| [Refund-Rate Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/refund-rate-spike-alert)                     | Lower is better  | 2    | 5   | %        |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)                           | Higher is better | 25   | 10  | %        |
| [Revenue Drop Alert](/nerve-centre/kpi-cards/adobe-commerce/revenue-drop-alert)                               | Watch for drops  | 0    | -5  | %        |
| [Revenue Over Time](/nerve-centre/kpi-cards/adobe-commerce/revenue-over-time)                                 | Watch for drops  | 0    | -5  | Currency |
| [Revenue at Risk (active incidents)](/nerve-centre/kpi-cards/adobe-commerce/revenue-at-risk-active-incidents) | Watch for drops  | 0    | -5  | Currency |
| [Shipping Cost as % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/shipping-cost-as-of-revenue)           | Lower is better  | 5    | 15  | %        |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                                           | Watch for drops  | 0    | -10 | Count    |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                                         | Watch for drops  | 0    | -5  | Currency |
| [Unfulfilled Orders](/nerve-centre/kpi-cards/adobe-commerce/unfulfilled-orders)                               | Lower is better  | 10   | 50  | Count    |
| [Unverified Email Customers](/nerve-centre/kpi-cards/adobe-commerce/unverified-email-customers)               | Lower is better  | 10   | 30  | Count    |


# Total Discount Used, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/total-discount-used

Total Discount Used for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Total promotional discount value applied to orders in the period. Magento stores discounts as a **negative** number in `discount_amount`; the card returns the absolute value (positive). Aggregates everything that landed in the cart-rule discount bucket: SalesRules promotions, B2B Customer Group tier prices when discount-coded, "spend $X get $Y" rules, free-shipping rules, and BOGO rules. Special prices applied via catalogue (not cart rules) are NOT in this bucket; those are reflected in `subtotal` directly.

|                         |                                                                                                                                                                                                                                                                                                                                                                               |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**      | `SUM(ABS(discount_amount))` over orders created in the 30-day window. The Magento field is stored negative (e.g. -£15 for a £15 discount); the card converts to positive for display.                                                                                                                                                                                         |
| **API field**           | `discount_amount` (negative), `discount_description`, `coupon_code`, `base_discount_amount` from `GET /rest/V1/orders`.                                                                                                                                                                                                                                                       |
| **What's in scope**     | (a) Cart price rules from **Marketing > Promotions > Cart Price Rules** (the canonical Magento promo engine), (b) free-shipping rules that include a non-zero `discount_amount` portion, (c) Customer Group tier-discounts applied via SalesRules (rare but possible).                                                                                                        |
| **What's NOT in scope** | (a) Catalogue special prices (the SKU's permanent sale price; reflected in `subtotal` directly, no `discount_amount` attribution), (b) B2B negotiated tier pricing applied via `customer_group_price` (changes the line price, no rule-based discount field), (c) refunds (those are Credit Memos, separate document). The card is creation-time discount, not net-of-refund. |
| **VAT / tax treatment** | The discount is **excl-tax** by default in Magento (the rule applies to subtotal pre-tax, then tax is recalculated on the post-discount subtotal). UK/EU merchants who want the customer-perceived discount (incl-tax) need `discount_amount + discount_tax_compensation_amount`. The "incl-tax discount" view is more accurate for marketing P\&L.                           |
| **Shipping inclusion**  | Free-shipping discount goes to `shipping_discount_amount` not `discount_amount`. So the card excludes free-ship value by default. To include free-ship in the "marketing cost" view, add `shipping_discount_amount`. The discount-related cards on this connector default to product-discount only; free-ship is on its own.                                                  |
| **Discounts**           | The card IS the discount view.                                                                                                                                                                                                                                                                                                                                                |
| **Refunds**             | A refunded order's discount is not subtracted. If the refund partially reverses the order, the discount portion is partially reversed too via Credit Memo, but those reversed-discounts appear in `creditmemo.discount_amount`, not here.                                                                                                                                     |
| **Cancelled**           | Cancelled orders' discounts are excluded by default (they don't count as "applied").                                                                                                                                                                                                                                                                                          |
| **Currency**            | Mixed-currency display by default. `base_discount_amount` for FX-neutral.                                                                                                                                                                                                                                                                                                     |
| **Channels**            | All Adobe Commerce sources.                                                                                                                                                                                                                                                                                                                                                   |
| **Multi-store scope**   | All Store Views by default.                                                                                                                                                                                                                                                                                                                                                   |
| **Time window**         | `30D` rolling.                                                                                                                                                                                                                                                                                                                                                                |
| **Alert trigger**       | None on this card directly. The rate-side alert is on [Discount % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue).                                                                                                                                                                                                                                    |
| **Roles**               | owner, marketing                                                                                                                                                                                                                                                                                                                                                              |

## Calculation

```
SUM(discount_amount)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC apparel merchant on Adobe Commerce 2.4.7. UK base, GBP. 4,820 orders. Period: 14 Apr 26 to 13 May 26.

**Discount aggregates:**

| Source                                                                      | `SUM(ABS(discount_amount))`                      | Order count          | Avg discount per discounted order |
| --------------------------------------------------------------------------- | ------------------------------------------------ | -------------------- | --------------------------------- |
| WELCOME10 (10% first-order coupon)                                          | £8,400                                           | 1,120                | £7.50                             |
| SPRING25 (25% sitewide spring sale, ran 1-14 Apr)                           | £21,400                                          | 480                  | £44.58                            |
| LOYALTY-VIP (auto-applied 15%)                                              | £4,200                                           | 380                  | £11.05                            |
| BUNDLE-SAVE (10% on 3+ items rule)                                          | £6,800                                           | 320                  | £21.25                            |
| B2B Tier Discount (Customer Group rule)                                     | £12,200                                          | 80                   | £152.50                           |
| FREE-SHIP (rule with no `discount_amount`, only `shipping_discount_amount`) | (£0 in this card; £14,200 in shipping\_discount) | 970                  | n/a                               |
| **Total `discount_amount`**                                                 | **£53,000**                                      | 2,380 (some overlap) | avg £22                           |

**Insight pattern:**

1. **Total discount £53,000 on revenue £950,000 = 5.6% discount %.** Within healthy norms (typically 3-8% for DTC apparel; 1-3% for B2B-heavy stores).
2. **Spring sale (SPRING25) is the dominant driver at £21,400** (40% of total discount). A 14-day sitewide sale chunked the spring AOV down. Cross-link with [Discount Over Time](/nerve-centre/kpi-cards/adobe-commerce/discounts-given-over-time) to see the daily spike.
3. **Welcome coupon (WELCOME10) absorbed £8,400 across 1,120 first-time buyers.** Customer acquisition cost analysis: £7.50 per first-time buyer in coupon discount, plus the merchant's other CAC. Cross-link with [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers) to see if the welcome flow is attracting profitable cohorts.
4. **B2B Tier Discount £12,200** at avg £152.50/order across 80 B2B orders. This is the contract-tier discount the merchant has agreed with key accounts. Should be relatively flat month-on-month; if it spikes, either a new tier was activated or rule-application logic changed.
5. **Free-shipping is invisible here** by design (sits in `shipping_discount_amount`). To get the full "marketing cost", add £14,200 of free-shipping discounts, total marketing cost £67,200 or 7.07% of revenue.
6. **Cross-link with [Total Discount](/nerve-centre/kpi-cards/adobe-commerce/total-discount-used) prior period:** £36,400. Recent +46% jump is dominated by the spring sale, which the merchant chose. After 14 Apr the daily discount value should drop to baseline; if it doesn't, a rule got stuck enabled.
7. **Action:** ensure SPRING25 rule is auto-deactivated by date end (Magento sometimes leaves rules "From-Date set, To-Date null" causing rules to run forever). Verify in **Marketing > Promotions > Cart Price Rules > \[SPRING25] > To Date**.

## Sibling cards merchants should reference together

| Card                                                                                   | Why pair it with Total Discount Used                                  |
| -------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| [Discount % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue)    | Rate-side companion.                                                  |
| [Discount Over Time](/nerve-centre/kpi-cards/adobe-commerce/discounts-given-over-time) | Day-by-day shape; spots stuck-enabled rules.                          |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                  | Denominator-of-context.                                               |
| [Total Shipping](/nerve-centre/kpi-cards/adobe-commerce/total-shipping-revenue)        | Free-shipping discount sits in `shipping_discount_amount`, separate.  |
| [Free vs Paid Shipping](/nerve-centre/kpi-cards/adobe-commerce/free-vs-paid-shipping)  | The free-ship volume (which equates to absorbed shipping discount).   |
| [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers)                  | Welcome-coupon driven new buyers.                                     |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)                    | Discounts on refunded orders are partially reversed via Credit Memos. |
| [`klaviyo.coupon_redemption_count`](/nerve-centre/klaviyo/coupon_redemption_count)     | Email-issued coupon redemption rate.                                  |
| [`shopify.total_discount`](/nerve-centre/kpi-cards/shopify/total-discount-used)        | Shopify peer.                                                         |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Coupons** breaks down discount value by coupon code. Set the date range and Show By "Coupon Code" to see the per-rule contribution. The total at the bottom should approximately match this card.

For per-rule promotion data:

> **Marketing > Promotions > Cart Price Rules** lists every active rule. Click into a rule to see its from-date / to-date and conditions. A rule with discount value showing in this card but no end date is the most common reason for "discount keeps flowing after the sale ended".

Reports > Sales > Coupons does not include automatic (no-coupon) rules; the **Sales > Orders** grid does. For complete per-rule reconciliation, query `sales_order` with the `applied_rule_ids` field.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                                     | Direction of divergence                   |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
| **Reports > Sales > Coupons excludes auto-applied rules**. Rules without coupon codes (e.g. an auto "10% off if subtotal > £100") don't appear there. They DO appear in this card.                                         | Card higher than Admin Coupons report     |
| **Free-shipping discount**. Free-ship rules typically populate `shipping_discount_amount`, not `discount_amount`. Card excludes by default; Admin's Coupons report may or may not include depending on rule configuration. | Possible material gap if mismatched       |
| **Currency**. Admin defaults to base currency; this card defaults to display-currency.                                                                                                                                     | Material for multi-currency stores        |
| **Reports indexer lag**. Admin Coupons report uses nightly aggregation. This card refreshes every 5-15 min.                                                                                                                | Vortex IQ ahead by \~12-24h               |
| **Cancelled inclusion**. Card excludes cancelled orders' discounts; Admin may include depending on filter.                                                                                                                 | Card lower than Admin "Status=Any" filter |
| **Time-zone, sync lag**. Standard.                                                                                                                                                                                         | Minor                                     |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                                           | Expected relationship                                                                                         | What divergence tells you                                                                                                                                                                            |
| ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`klaviyo.coupon_redemption_count`](/nerve-centre/klaviyo/coupon_redemption_count)             | Klaviyo's redemption count for email-issued coupons should match this card's per-coupon count for those rules | If Klaviyo issues 200 codes and only 50 redeem, that's normal email open-rate dynamics; if Klaviyo issued 50 and 200 redeem here, customers are sharing codes (multi-use rule when it shouldn't be). |
| [`google_analytics.ga_promo_attribution`](/nerve-centre/google_analytics/ga_promo_attribution) | GA4 attributes orders to promo via UTM and coupon-code                                                        | GA4 misses \~10-25% due to tracking gaps; expect Adobe higher.                                                                                                                                       |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.total_discount`](/nerve-centre/kpi-cards/shopify/total-discount-used)
  * [`bigcommerce.total_discount`](/nerve-centre/kpi-cards/bigcommerce/total-discount-used)
</details>

## Known limitations / merchant FAQs

**Why does Magento store discounts as negative?**
Convention. The `discount_amount` field on the order is a signed delta against `subtotal`; a discount reduces subtotal so it's negative. The card converts to absolute value for display because "Total Discount Used = £53,000" reads more naturally than "−£53,000".

**Why is catalogue special-price not in this card?**
Because Magento doesn't track it as a discount event. A product with `price=£100` and `special_price=£75` ships at £75 line total; there's no `discount_amount` field populated. The `subtotal` is just lower. Catalogue special pricing is permanent (until removed), so it isn't really a "discount campaign" in the marketing sense.

**Free shipping is missing here, where is it?**
In `shipping_discount_amount`. The free-shipping rule populates that field separately. The card excludes it by default to keep "discount on goods" and "discount on shipping" distinct, both are merchant cost but they are different levers.

**A rule keeps applying after the sale ended, why?**
A Cart Price Rule with **From Date** set but **To Date** blank runs forever. The most common cause of "stuck" discounts. Always set both dates. **Marketing > Promotions > Cart Price Rules > \[rule] > To Date** is mandatory for time-bound campaigns.

**My multi-store discount, the same coupon shows different totals per Store View, why?**
Customer Group conditions on the rule. A rule that targets "Wholesale" Customer Group only applies on B2B Store Views; on DTC Store Views the rule fires zero times. Healthy. The card sums across; per-Store-View slice via filter.

**Why doesn't `klaviyo.coupon_redemption_count` match?**
Klaviyo issues codes; Adobe applies them. If Klaviyo issued 1,000 codes and Adobe applied 1,200, customers shared codes (multi-use rule + circulation). If Klaviyo issued 1,000 and Adobe applied 200, redemption is at 20%, normal email open rate × redeem rate.

**Discounts on refunded orders, are they counted?**
Yes; the card is creation-time. The discount was applied at creation. If the order is later refunded, the Credit Memo's `discount_amount` represents the reversal portion; it's tracked separately on [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value). For "net discount cost", subtract refunded discounts.

**Why is my B2B Tier Discount showing here? I thought tier prices were catalogue.**
Two paths. Catalogue tier prices (set on the SKU) bypass `discount_amount` (they reduce `subtotal` directly). Cart-rule-based tier discounts (set as a Customer Group condition on a SalesRule) DO populate `discount_amount`. The merchant probably has the latter; check **Customers > Customer Groups** for how the tier was configured.

**Today's number isn't moving even though I see orders coming in, why?**
Either today's orders aren't using any active promotions, or the promo's `discount_amount` is being added to `shipping_discount_amount` instead (e.g. it's a free-shipping rule). Cross-check the rules' discount target (subtotal vs shipping) in the rule definition.

**Can I see this by Customer Group?**
Yes. Filter via Customer Group. B2B groups should show low share (most B2B uses negotiated catalogue prices); DTC groups dominate.

***

### Tracked live in Vortex IQ Nerve Centre

*Total Discount Used* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Total Orders, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/total-orders

Total Orders for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> The raw count of order rows created in the period. Every Adobe Commerce order document with a `created_at` inside the window contributes one, regardless of `state`, payment outcome, or whether the customer ever paid.

|                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **What it counts**                                     | `COUNT(*)` of every order row in the Adobe Commerce orders index where `created_at` falls inside the period. The Adobe Commerce REST endpoint is `GET /rest/V1/orders`; one row per `entity_id`.                                                                                                                                                                                                                                           |
| **API field**                                          | The order document itself. There is no monetary aggregation, the count is on the document `_id` (mapped to Adobe Commerce `entity_id`).                                                                                                                                                                                                                                                                                                    |
| **VAT / tax treatment**                                | n/a, this is a count of order documents, not a money figure. Tax inclusion is irrelevant.                                                                                                                                                                                                                                                                                                                                                  |
| **Shipping**                                           | n/a. Shipping is a money concept; this is a count.                                                                                                                                                                                                                                                                                                                                                                                         |
| **Discounts**                                          | n/a, but worth noting: a 100%-off promo order still counts here. A free-with-coupon order is one order.                                                                                                                                                                                                                                                                                                                                    |
| **Credit Memo refund treatment**                       | **NOT excluded.** Adobe Commerce holds refunds on separate Credit Memo documents; the underlying order document still exists and is still counted here. A fully refunded order is still one order in this card.                                                                                                                                                                                                                            |
| **`state` machine inclusion**                          | **All states included by default.** That covers `new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, and `payment_review`. The Adobe-specific quirk is `pending_payment`: orders sit there when the shopper hit Place Order but the gateway never returned a result. They count here even though no cash was collected. To get a "realised orders" count, filter `state IN (processing, complete, closed)`. |
| **`status` distinction**                               | `state` is the system-level lifecycle (8 fixed values). `status` is a configurable, user-facing label that maps onto `state`, merchants rename "processing" to "Order Confirmed" or add custom statuses. This card uses `state`-based logic only; merchant-renamed statuses don't change the count.                                                                                                                                        |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a for the count itself. Worth calling out: a single B2B order at $25,000 and a single $4 sticker order both contribute one to this card. Pair with [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) for the value view.                                                                                                                                                                                             |
| **Store View scope (`store_id`)**                      | **All Store Views summed by default.** Orders from US, UK, DE, B2B portals, and any headless storefront are all counted together. Filter by `store_id` for a per-region view, or use [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id) for a value-weighted breakdown.                                                                                                                                             |
| **Time window**                                        | `T/7D/30D vsP` (default 30D vs the prior 30D)                                                                                                                                                                                                                                                                                                                                                                                              |
| **Alert trigger**                                      | `drop >20% vsP`, driven by `sentiment_key: order_count_trend`                                                                                                                                                                                                                                                                                                                                                                              |
| **Roles**                                              | owner, marketing, operations                                                                                                                                                                                                                                                                                                                                                                                                               |

## Calculation

```
COUNT(_id)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A multi-region apparel brand on Adobe Commerce 2.4.6 runs three Store Views: US (USD), UK (GBP), and a B2B wholesale portal (USD). The 30-day window covers 14 Mar 26 to 12 Apr 26.

| `store_id`                   | Store View           | Orders in window | Of which `state = pending_payment` | Of which `state = canceled` |
| ---------------------------- | -------------------- | ---------------- | ---------------------------------- | --------------------------- |
| `1`                          | US storefront        | 1,840            | 62                                 | 41                          |
| `2`                          | UK storefront        | 612              | 18                                 | 9                           |
| `3`                          | B2B wholesale portal | 41               | 0                                  | 1                           |
| **Total Orders (this card)** |                      | **2,493**        | **80**                             | **51**                      |

The headline reads **2,493 orders**. What's interesting:

1. **Store View 1 contributes 74% of order volume but the B2B portal contributes 17% of revenue from 1.6% of orders.** Order Count and Total Revenue tell different stories. Always read the two together. A drop in this card may be invisible in revenue if the B2B portal was steady, and vice versa.
2. **80 `pending_payment` orders are inflating the count by 3.2%.** These shoppers hit Place Order, the gateway didn't return success, and the order was never paid for. They count here. To see the "real" order count merchants typically use a `state IN (processing, complete, closed)` filter, which would land at 2,362 in this example.
3. **51 `canceled` orders also count.** Adobe Commerce keeps the order document after cancellation; this card doesn't filter them. If the warehouse refused 30 orders this week (out of stock, fraud, address invalid), they're still in the headline.
4. **The 30-day prior window had 2,612 orders.** This window is down 4.6% vs prior, which is below the `drop >20% vsP` alert threshold. Vortex IQ Nerve Centre stays quiet, but a per-Store-View slice would show the US store flat, UK down 8%, and B2B portal down 22%, an early warning that the wholesale pipeline is softening even though the headline looks fine.

## Sibling cards merchants should reference together

Order Count is the denominator under nearly every per-order ratio in the dashboard. Pair it with these for context:

| Card                                                                                              | Why pair it with Order Count                                                                                                                                                                |
| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                             | The numerator partner. Together they answer "did revenue move on volume or basket size?". Identical movement on both = volume change; revenue moves while orders flat = basket size change. |
| [Average Order Value](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                 | Mathematical sibling: AOV = Total Revenue ÷ Order Count. If Order Count rose and AOV fell, you grew on lower-value baskets (often new-customer surge).                                      |
| [Cancellation Rate](/nerve-centre/kpi-cards/adobe-commerce/cancellation-rate)                     | The proportion of these orders that ended in `state = canceled`. A creeping cancellation rate hides inside a healthy-looking Order Count headline.                                          |
| [Refund Count](/nerve-centre/kpi-cards/adobe-commerce/refunded-orders)                            | Number of orders that produced at least one Credit Memo. Pair as % of orders for refund rate.                                                                                               |
| [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown)          | Breaks this single number into `processing`, `complete`, `canceled`, `holded`, `pending_payment`. Surfaces the `pending_payment` quirk visually.                                            |
| [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id)                         | Per-`store_id` revenue. Combine with a per-Store-View order count to spot which region drove a headline change.                                                                             |
| [`stripe.stripe_charge_count`](/nerve-centre/stripe/stripe_charge_count)                          | Count of successful Stripe charges. Should sit at or below this card (Stripe never sees `pending_payment`, `canceled`, or non-Stripe-processed orders).                                     |
| [`google_analytics.ga_purchases_trend`](/nerve-centre/kpi-cards/google-analytics/purchases-trend) | GA4 `purchase` events. Typically 10, 25% lower than this card due to ad blockers and consent rejection.                                                                                     |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

The closest Adobe Commerce Admin view is:

> **Sales > Orders** (the order grid). Apply the same date range filter ("Purchase Date" between `period_start` and `period_end`), set Status to *All Orders*, and the row count at the bottom of the grid should match this card.

For a windowed-aggregate view rather than a row list:

> **Reports > Sales > Orders** in older Adobe Commerce 2.x versions, or **Reports > Sales** with the *Orders* tab in 2.4.6+. Set the same window, scope to *All Store Views*, and read the **Total Orders** column.

Other Adobe Commerce Admin views that *look* like the same number but aren't:

* **Reports > Sales > Invoiced**: counts invoices, not orders. One order can produce zero, one, or several invoices (partial shipments).
* **Reports > Sales > Refunded**: counts Credit Memos, a subset.
* **Dashboard > Last Orders**: only the last 5 orders, not aggregated.
* **Dashboard > Lifetime Sales**: all-time count, not windowed.
* **Customers > All Customers > Orders column**: per-customer running totals, not a window.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                                                                                              | Direction of divergence                                 |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| **Time-zone**. Adobe Commerce Admin renders the order grid in the Store View timezone configured under *Stores > Configuration > General > Locale Options*. Vortex IQ aggregates on UTC by default. Orders near midnight on the boundary days fall on different sides.              | ±1 day's orders at the boundary                         |
| **Store View scope**. The Adobe Commerce order grid filter typically defaults to the admin user's assigned scope (e.g. only the UK Store View). Vortex IQ sums across every Store View unless filtered. Set the admin scope dropdown to *All Store Views* for a like-for-like read. | Vortex IQ higher than per-view admin filter             |
| **`canceled` state**. The order grid includes canceled rows by default (Status filter "All Orders"). Some merchants set their default filter to exclude canceled. This card always includes them.                                                                                   | Vortex IQ higher than filtered admin grids              |
| **`pending_payment`**. Included here, included in the admin grid by default.                                                                                                                                                                                                        | Match (no divergence)                                   |
| **Currency irrelevance**. Order Count doesn't depend on `grand_total` vs `base_grand_total`, so the two views agree on currency-multi stores.                                                                                                                                       | No divergence on this axis                              |
| **API rate-limit gaps during sync**. Adobe Commerce REST has request quotas; if the indexer hit rate-limit during the most recent sync, the latest few minutes of orders may be missing.                                                                                            | Self-resolves at next sync, typically within 15 minutes |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

These connectors see *the same orders through different lenses*. They should agree within known tracking gaps; divergence is a data-quality signal worth investigating.

| Card                                                                                              | Expected relationship                                | What causes legitimate divergence                                                                                                                                                                                                                              |
| ------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_charge_count`](/nerve-centre/stripe/stripe_charge_count)                          | Stripe ≤ Adobe Commerce Order Count                  | Stripe sees only successfully captured charges. Excludes Adobe Commerce `pending_payment` (gateway never returned), `canceled`, `holded`, and any orders routed through a non-Stripe processor (Authorize.Net, Braintree, PayPal, gift cards, manual payment). |
| [`paypal.pp_transaction_count`](/nerve-centre/paypal/pp_transaction_count)                        | PayPal ≤ Adobe Commerce Order Count                  | PayPal sees only PayPal-checkout orders. Subset by definition.                                                                                                                                                                                                 |
| [`google_analytics.ga_purchases_trend`](/nerve-centre/kpi-cards/google-analytics/purchases-trend) | GA4 typically \~75-90% of Adobe Commerce Order Count | GA4 misses `purchase` events from ad-blocked, consent-rejecting, or tag-fail browsers. **Treat Adobe Commerce as the source of truth for order count.** Use GA4 to understand traffic source, channel, and device, not to count orders.                        |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same definition of Order Count lives on other commerce platforms. This is **not a reconciliation**; your Adobe Commerce store doesn't have a parallel store on Shopify or BigCommerce to compare against. These cross-links exist so agencies running multi-platform client books can navigate between identical metrics across the docs.

  * [`shopify.order_count`](/nerve-centre/kpi-cards/shopify/total-orders)
  * [`bigcommerce.order_count`](/nerve-centre/kpi-cards/bigcommerce/total-orders)
</details>

## Known limitations / merchant FAQs

**Why does the order count look higher than the number my finance team uses for revenue?**
Three Adobe-specific reasons stack: (1) `pending_payment` orders are counted but never collected cash, (2) `canceled` orders are counted even though they were voided, and (3) Credit-Memo-refunded orders are counted at full value (the refund lives on a separate document). Finance typically uses an *invoiced* count (one Adobe Commerce invoice per shipment, with refunds netted), which lands materially lower. Both numbers are correct for different jobs.

**What's the difference between `state` and `status` on an Adobe Commerce order?**
`state` is the system-level lifecycle, an 8-value enum: `new`, `pending_payment`, `processing`, `complete`, `closed`, `canceled`, `holded`, `payment_review`. It governs what actions the system allows. `status` is a configurable, user-facing label that maps onto `state`, merchants rename "processing" to "Order Confirmed" or add custom labels like "Awaiting Drop-Ship". This card uses `state` only; renamed statuses don't change the count. If you want to slice by your custom workflow statuses, use [Financial Status Distribution](/nerve-centre/kpi-cards/adobe-commerce/financial-status-breakdown).

**Why doesn't the Adobe Commerce dashboard match this card?**
Most commonly: the admin scope is set to a single Store View. The Sales > Orders grid filters by your admin user's assigned scope by default (e.g. only the UK Store View). Vortex IQ sums every Store View. Set the scope dropdown at the top-left of admin to *All Store Views* and re-run, the numbers should match.

**My multi-store Adobe Commerce, can I see per-Store-View order count?**
Not on this card directly; it's a single number summed across all `store_id` values. Use [Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) for the lifecycle breakdown, or filter the source data by `store_id` for a per-region count. A per-Store-View order-count card is on the roadmap.

**Why is my Stripe charge count smaller than this number?**
Payment processors only see *successfully captured* charges. Stripe excludes Adobe Commerce `pending_payment` (gateway never returned), `canceled`, `holded`, and any orders paid via a different processor (Authorize.Net, Braintree, PayPal, gift cards, manual). A typical multi-payment Adobe Commerce store splits orders across 2-4 processors; no single processor sees the full picture.

**Why doesn't Google Analytics match?**
GA4 typically misses 10, 25% of orders due to ad blockers, cookie consent rejection, and tag-fire failures. A typical UK Adobe Commerce store sees GA4's `purchase` event count run 75-90% of this card. The miss rate is structural, not a configuration bug. **Treat Adobe Commerce as the source of truth for order count.** Use GA4 for traffic source, channel, and device attribution.

**My multi-currency Adobe Commerce, does Order Count care?**
No. Order Count is a count, not a money figure, so `grand_total` vs `base_grand_total` is irrelevant. A USD order and a GBP order each contribute one. Pair with [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue) (which uses `grand_total`, mixed-currency without FX) or `base_grand_total` views (FX-converted) for the value picture.

**Why does today's number jump up and down so much?**
Today is incomplete data. As the day rolls forward, orders accumulate, and as it crosses midnight some orders flip date because of timezone differences between the Store View and UTC. **Use the rolling 7-day or 30-day view for stable numbers**; that's why the alert window is `30D vsP` and not `1D`.

***

### Tracked live in Vortex IQ Nerve Centre

*Total Orders* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Total Revenue, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/total-revenue

Total Revenue for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Headline gross revenue across every Adobe Commerce (Magento) order placed in the period. The arithmetic sum of `grand_total` for every order created in the window, regardless of state, fulfilment, or refund status.

|                              |                                                                                                                                                                                                                                                                                                                                                                   |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**           | `SUM(grand_total)` across every order in the window. `grand_total` is Adobe Commerce's authoritative customer-billed total, computed as `subtotal + shipping_amount + tax_amount − discount_amount`.                                                                                                                                                              |
| **VAT / tax treatment**      | **Tax-inclusive by definition.** `grand_total` already includes `tax_amount`. Pre-tax view sits in `subtotal` (or `base_subtotal` for the store's base currency).                                                                                                                                                                                                 |
| **Shipping**                 | **Included.** `grand_total` adds `shipping_amount` (post-discount).                                                                                                                                                                                                                                                                                               |
| **Discounts**                | Already deducted, this is the post-promotion, customer-paid figure.                                                                                                                                                                                                                                                                                               |
| **Refunds**                  | **NOT deducted.** Adobe Commerce tracks refunds as separate Credit Memo entities. The order's `grand_total` does not change after a refund, the refund lives on the credit memo. A fully refunded $200 order still contributes $200 here. Use [Credit Memo Total](/nerve-centre/adobe_commerce/credit_memo_total) for the offset.                                 |
| **Order state vs status**    | **Both unfiltered.** Adobe Commerce has a state machine (`new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, `payment_review`) AND a richer status overlay (configurable per merchant). This card includes every state, including `canceled` and `holded`. To see a "realised cash" view, filter to `state = complete OR closed`. |
| **`pending_payment` orders** | Included. Adobe Commerce creates the order as soon as the shopper hits Place Order, even before the payment authorisation completes. If the gateway never returns success, the order can sit in `pending_payment` indefinitely. These contribute to Total Revenue but never collected cash.                                                                       |
| **Currency**                 | **Multi-currency arithmetic sum WITHOUT FX conversion.** Adobe Commerce stores both `grand_total` (in the order's display currency) and `base_grand_total` (in the store's base currency, FX-converted at order time). This card uses `grand_total`. For multi-store merchants with multiple base currencies, prefer `base_grand_total` views.                    |
| **Channels / sources**       | **Not filtered.** Adobe Commerce uses Store Views (`store_id`) to separate web storefronts, country sites, and B2B portals. POS, marketplace, and headless storefronts also tag a `store_id`. This card sums across every Store View.                                                                                                                             |
| **Time window**              | `T/7D/30D vsP` (default 30D)                                                                                                                                                                                                                                                                                                                                      |
| **Alert trigger**            | `drop >15% vsP`, driven by `sentiment_key: revenue_trend`                                                                                                                                                                                                                                                                                                         |
| **Roles**                    | owner, marketing, operations                                                                                                                                                                                                                                                                                                                                      |

## Calculation

```
SUM(grand_total)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A multi-region brand on Adobe Commerce 2.4 with three Store Views: US, UK, and a B2B portal. The 30-day window covers 14 Mar 26 to 12 Apr 26.

| `store_id`                    | Store View                                   | Orders    | Avg `grand_total` | Channel revenue                          |
| ----------------------------- | -------------------------------------------- | --------- | ----------------- | ---------------------------------------- |
| `1`                           | US storefront (USD)                          | 1,840     | \$148             | \$272,320                                |
| `2`                           | UK storefront (GBP, summed without FX)       | 612       | £132              | £80,784                                  |
| `3`                           | B2B portal (USD, account-priced)             | 41        | \$1,420           | \$58,220                                 |
| (across)                      | `pending_payment` orders that never resolved | 78        | \$156             | \$12,168 (no cash taken)                 |
| **Total Revenue (this card)** |                                              | **2,571** |                   | **\$343,492 + £80,784 (mixed currency)** |

What's interesting:

1. **The mixed-currency total is meaningless on its own.** The card sums `grand_total` directly without FX, so the headline mixes USD and GBP. A multi-store merchant should use `base_grand_total` views instead, or split per-Store-View. The roadmap includes a `currency_filtered_total_revenue` card.
2. **The B2B portal is 17% of US revenue from 2% of order volume.** Big wholesale orders skew Total Revenue. If the B2B portal goes quiet for a week the headline drops noticeably even if the DTC store is stable. Watch [BC Revenue by Store View](/nerve-centre/adobe_commerce/bc_revenue_by_store_id) for the breakdown.
3. **`pending_payment` orders are silently inflating the headline by \$12,168.** These are shoppers who hit Place Order but the gateway never returned. Adobe Commerce keeps the order skeleton; this card includes it. Subtract these (or filter `state != pending_payment`) for a realised-cash view.
4. **The 30-day prior window was \$358,400 + £79,200.** Total Revenue is down 4.2% on USD and up 2.0% on GBP, which is below the `drop >15% vsP` alert threshold for either currency stream. Vortex IQ Nerve Centre stays quiet, but the card itself shows the trend and a per-Store-View slice surfaces the divergence.

## Sibling cards merchants should reference together

| Card                                                                                | Why pair it with Total Revenue                                                                                                                                   |
| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Average Order Value](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)   | Total Revenue ÷ Order Count. Tells you whether revenue moved on volume or basket size.                                                                           |
| [Order Count](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                  | The other half of the equation. If revenue moves but order count is flat, basket size changed.                                                                   |
| [Credit Memo Total](/nerve-centre/adobe_commerce/credit_memo_total)                 | This card is **gross** of refunds. Credit Memo Total tells you how much Adobe Commerce has actually credited back. Subtract for a net view.                      |
| [`pending_payment` Order Value](/nerve-centre/adobe_commerce/pending_payment_value) | Headline includes orders that never collected cash. This card surfaces how big that gap is.                                                                      |
| [Discount % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/discount-of-revenue) | Discounting always lifts Total Revenue mechanically. Watch them together.                                                                                        |
| [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id)           | Per-Store-View breakdown, essential for multi-region or B2B-plus-DTC merchants.                                                                                  |
| [Order State Distribution](/nerve-centre/adobe_commerce/order_state_distribution)   | Shows the mix of `processing`, `complete`, `canceled`, `holded`, `pending_payment`. A drift toward `holded` or `pending_payment` indicates payment-side trouble. |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

Sales → Orders → Reports → Sales (or Reports → Sales → Orders, depending on Adobe Commerce version). Set the same window (default 30D), keep the *Status* filter on "All Orders", and look at the **Total Revenue** column. That figure should match this card to within a couple of dollars.

Other Adobe Commerce Admin views that *look* like the same number but aren't:

* **Reports → Sales → Orders**: this DOES match (assuming "All Orders" status, same window, same Store View scope).
* **Reports → Sales → Invoiced**: this is invoiced amount only, post-Credit-Memo, so lower.
* **Reports → Sales → Refunded**: this is the refund total, not revenue.
* **Dashboard → Lifetime Sales**: all-time, not windowed.
* **Dashboard → Last Orders**: last 5 orders only, not aggregated.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                                     | Direction of divergence                      |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| **Time-zone**. Adobe Commerce Admin uses store timezone (configured per Store View); Vortex IQ runs on UTC by default. Orders near midnight on the boundary days fall on different sides.                                  | ±1 day's revenue at the boundary             |
| **Currency**. Multi-currency Adobe Commerce sites display `grand_total` in display currency in the order grid, but the Sales Report aggregates in `base_currency` (FX-converted). Vortex IQ sums `grand_total` without FX. | Material for international merchants         |
| **Store View scope**. Adobe Commerce reports run per Store View by default. Vortex IQ sums across every Store View unless filtered. The "All Store Views" report scope in Admin should match.                              | Vortex IQ higher than per-view report        |
| **`canceled` orders**. The default Sales Report status filter is "All Orders" which includes canceled; some merchants override the filter. This card always includes canceled.                                             | Vortex IQ higher than filtered admin reports |
| **API rate-limit gaps during sync**. If the Adobe Commerce REST API throttled during the most recent indexer run, the latest day's orders may be missing for a few minutes.                                                | Self-resolves at next sync                   |

**Cross-connector reconciliation (when the merchant has connected payment processors and analytics):**

These connectors see *the same transactions through different lenses*. They should agree within known tracking gaps. Divergence is a data-quality signal worth investigating.

| Card                                                                                          | Expected relationship                                   | What causes legitimate divergence                                                                                                                                                                                                                                                      |
| --------------------------------------------------------------------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`stripe.stripe_total_revenue`](/nerve-centre/kpi-cards/stripe/total-charge-volume)           | Stripe ≤ Adobe Commerce Total Revenue                   | Stripe sees only successfully captured charges. It excludes Adobe Commerce `pending_payment` (gateway never returned), `canceled`, `holded`, refunds (which sit on Credit Memos), and any orders routed through a non-Stripe processor (Authorize.Net, Braintree, PayPal, gift cards). |
| [`paypal.pp_total_volume`](/nerve-centre/paypal/pp_total_volume)                              | PayPal ≤ Adobe Commerce Total Revenue                   | PayPal sees only PayPal-checkout orders. Subset by definition.                                                                                                                                                                                                                         |
| [`google_analytics.ga_revenue_trend`](/nerve-centre/kpi-cards/google-analytics/revenue-trend) | GA4 ≈ Adobe Commerce Total Revenue × (1 − tracking gap) | GA4 typically misses 10, 25% of orders due to ad-blockers, cookie rejection, and tag-fire failures. **Treat Adobe Commerce as the source of truth for revenue.** Use GA4 for traffic and channel attribution, not for revenue figures.                                                 |

**Net of all processors and pending payments:** if you sum *Stripe + PayPal + Authorize.Net + Braintree + manual + gift cards*, the total should sit close to *this card minus pending\_payment value minus canceled value*. A persistent gap > 2% means a payment processor is missing from your Vortex IQ workspace.

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  The same definition of Total Revenue lives on other commerce platforms. This is **not a reconciliation**, your Adobe Commerce store doesn't have a parallel store on Shopify or BigCommerce to compare numbers against. These cross-links exist so agencies running multi-platform client books can navigate between identical metrics across the docs.

  * [`shopify.total_revenue`](/nerve-centre/kpi-cards/shopify/total-revenue)
  * [`bigcommerce.total_revenue`](/nerve-centre/kpi-cards/bigcommerce/total-revenue)
</details>

## Known limitations / merchant FAQs

**Why does my Total Revenue look higher than my bank deposits?**
Three reasons specific to Adobe Commerce: (1) `pending_payment` orders are included but never collected cash, (2) `canceled` orders are included even though they were voided, and (3) refunds live on Credit Memos and don't subtract from `grand_total`. To get a realised-cash floor, take this card minus *pending\_payment value* minus *canceled value* minus *Credit Memo Total*.

**What's the difference between `state` and `status` on an Adobe Commerce order?**
`state` is the system-level lifecycle (`new`, `processing`, `complete`, `closed`, `canceled`, `holded`, `pending_payment`, `payment_review`). It's a fixed enum used internally for what actions are valid. `status` is a configurable, user-facing label that maps onto `state`, merchants can rename "processing" to "Order Confirmed" or add custom statuses like "Awaiting Drop-Ship". This card uses `state` filtering for any state-based view; `status` is captured for display only.

**What is `grand_total` vs `base_grand_total`?**
`grand_total` is in the order's display currency (what the customer paid). `base_grand_total` is in the store's base currency (FX-converted at order time using the store's current FX rate). Multi-currency stores should use `base_grand_total` views for aggregate reporting, this card uses `grand_total` because it's the customer-paid figure.

**Why doesn't the Adobe Commerce dashboard match this card?**
Most commonly: (1) the dashboard scope is set to a single Store View while this card sums across all Store Views, or (2) the dashboard report filters out `canceled` while this card includes them, or (3) timezone difference (the dashboard uses Store View timezone, this card uses UTC).

**Why is my Stripe / Authorize.Net number much smaller than this card?**
Payment processors only see *successfully captured* charges. They exclude `pending_payment` (the gateway didn't return success), `canceled`, refunds (which subtract from the processor side), and any orders paid via a different processor (a typical Adobe Commerce store uses 2-4 payment methods).

**My multi-store Adobe Commerce, how do I see per-Store-View revenue?**
Use [Revenue by Store View](/nerve-centre/adobe_commerce/revenue_by_store_id). It groups by `store_id`. Useful for region-by-region performance reads (US vs UK vs DE) and for separating B2B portals from DTC.

**Why doesn't Google Analytics match?**
GA4 typically misses 10, 25% of orders due to ad blockers, cookie rejection, and tag-fire failures. The miss rate is *not* fixable; it's structural. **Treat Adobe Commerce as the source of truth for revenue.** Use GA4 for sessions, traffic source, and funnel behaviour, not revenue.

**Why does today's number jump up and down so much?**
Today is incomplete data. As the day progresses orders add into the bucket, and as the day rolls past midnight some orders flip date because of timezone effects. **Use the rolling 7-day or 30-day view for stable numbers**, that's why the alert window is `30D vsP` and not `1D`.

***

### Tracked live in Vortex IQ Nerve Centre

*Total Revenue* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Total Shipping Revenue, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/total-shipping-revenue

Total Shipping Revenue for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> The absolute customer-paid shipping revenue collected over the period: `SUM(shipping_amount)` over orders. Pairs with [Shipping Cost as % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/shipping-cost-as-of-revenue) (the rate version) and with [Free vs Paid Shipping](/nerve-centre/kpi-cards/adobe-commerce/free-vs-paid-shipping) (the composition view).

|                         |                                                                                                                                                                                                                                                                                                                        |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**      | `SUM(shipping_amount)` over orders created in the 30-day window. `shipping_amount` is the post-discount, excl-tax shipping the customer paid (after free-shipping coupons or threshold-based discounts).                                                                                                               |
| **API field**           | `shipping_amount` (post-discount, excl-tax), `shipping_discount_amount`, `shipping_tax_amount`, `base_shipping_amount` from `GET /rest/V1/orders`.                                                                                                                                                                     |
| **VAT / tax treatment** | **Excl-tax** by default. Adobe Commerce stores the shipping VAT separately as `shipping_tax_amount`. For UK/EU merchants, the customer's invoice line "Shipping inc. VAT" equals `shipping_amount + shipping_tax_amount`. Both are exposed; the headline uses the excl-tax view to mirror Finance accounting practice. |
| **Shipping**            | The card IS the shipping view.                                                                                                                                                                                                                                                                                         |
| **Discounts**           | Already deducted, this is post-discount paid shipping. The free-shipping discount portion is in `shipping_discount_amount` (positive number representing the discount applied). The pre-discount listed shipping is `shipping_amount + shipping_discount_amount`.                                                      |
| **Cancelled orders**    | Excluded by default. Cancelled orders typically have `shipping_amount=0` anyway, but the explicit exclusion ensures cleanliness.                                                                                                                                                                                       |
| **Refunds**             | Not subtracted, the card is creation-time. Refunded shipping (Credit Memo with `shipping_amount > 0`) reduces net but appears separately on [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value). Net shipping = this card − Credit Memo shipping.                                                      |
| **Currency**            | Mixed-currency display by default. `base_shipping_amount` for FX-neutral.                                                                                                                                                                                                                                              |
| **Channels / sources**  | All Adobe Commerce sources. B2B orders that use freight (LTL, FTL) charged outside Adobe (invoiced separately) do not appear here.                                                                                                                                                                                     |
| **Multi-store scope**   | All Store Views by default.                                                                                                                                                                                                                                                                                            |
| **Time window**         | `30D` rolling.                                                                                                                                                                                                                                                                                                         |
| **Alert trigger**       | None on this card directly. The rate-side alert is on [Shipping Cost as % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/shipping-cost-as-of-revenue).                                                                                                                                                             |
| **Roles**               | owner, operations                                                                                                                                                                                                                                                                                                      |

## Calculation

```
SUM(shipping_amount)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC homewares merchant on Adobe Commerce 2.4.7. UK base, GBP. 4,820 orders. Period: 14 Apr 26 to 13 May 26.

**Shipping aggregates:**

| Component                                                      | Value (GBP) |
| -------------------------------------------------------------- | ----------- |
| `SUM(shipping_amount)` (card default, excl-tax, post-discount) | £58,400     |
| `SUM(shipping_discount_amount)`                                | £14,200     |
| Pre-discount listed shipping                                   | £72,600     |
| `SUM(shipping_tax_amount)`                                     | £11,680     |
| `SUM(shipping_amount + shipping_tax_amount)` (incl-tax)        | £70,080     |

**Per-method breakdown** (joined with `payment.method` for shipping-method via `shipping_description`):

| Shipping method                     | Order count | `SUM(shipping_amount)` | Avg per order                     |
| ----------------------------------- | ----------- | ---------------------- | --------------------------------- |
| Royal Mail Tracked 48 (UK standard) | 2,840       | £25,560                | £9.00                             |
| Royal Mail Special Delivery         | 380         | £11,400                | £30.00                            |
| DHL Express (international)         | 220         | £8,800                 | £40.00                            |
| ParcelForce 24                      | 410         | £6,150                 | £15.00                            |
| Free shipping (>£75 threshold)      | 920         | £0                     | £0.00                             |
| Free shipping (loyalty perk)        | 50          | £0                     | £0.00                             |
| **Total**                           | **4,820**   | **£58,400**            | **avg paid £15** (excluding free) |

**Comparison to prior period:**

| Window              | `SUM(shipping_amount)` | Order count | Avg per non-free order |
| ------------------- | ---------------------- | ----------- | ---------------------- |
| 14 Apr to 13 May 26 | £58,400                | 4,820       | £15.00                 |
| 15 Mar to 13 Apr 26 | £52,200                | 4,640       | £13.50                 |
| **Change**          | **+11.9%**             | **+3.9%**   | **+11.1%**             |

What this is telling Operations:

1. **Shipping revenue grew 11.9% on order growth of only 3.9%.** The per-order paid shipping rose from £13.50 to £15.00. Cause likely a carrier rate increase (Royal Mail and DHL both raised in late Mar 26).
2. **Free-shipping share is 970 of 4,820 orders, 20.1%.** Healthy threshold-driven free-ship rate. £14,200 of free-ship discounts absorbed (the merchant "spent" £14,200 to chase the threshold-driven AOV lift).
3. **DHL Express at £40/order** is the highest per-order. Mostly international orders; investigate whether the carrier mark-up is passing through fully or being absorbed.
4. **Royal Mail Special Delivery at £30/order** is the second-highest. Used for high-AOV (>£100) DTC where customers opt for next-day. Consider raising threshold given the rate increase.
5. **Cross-link with [`shipstation.shipping_cost`](/nerve-centre/shipstation/shipping_cost):** carrier-paid £52,800 in the period. Net shipping revenue = collected £58,400 − paid £52,800 = £5,600 surplus. With £14,200 of absorbed free-ship discount, the *net economic position* on shipping is `+£5,600 − £14,200 = -£8,600`, i.e. shipping is a loss-leader for AOV. That is a deliberate strategy if AOV uplift covers it; verify with [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value) and the lift attribution.
6. **Action:** consider raising free-ship threshold to £85 to recover £4-6k/month if AOV elasticity supports it.

## Sibling cards merchants should reference together

| Card                                                                                        | Why pair it with Total Shipping                                          |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| [Shipping % of Revenue](/nerve-centre/kpi-cards/adobe-commerce/shipping-cost-as-of-revenue) | Rate-side companion.                                                     |
| [Free vs Paid Shipping](/nerve-centre/kpi-cards/adobe-commerce/free-vs-paid-shipping)       | Composition: how much of the order base avoided shipping fees.           |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)                       | Denominator-of-context.                                                  |
| [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value)                           | Free-ship thresholds drive AOV; pair to measure threshold effectiveness. |
| [Total Discount](/nerve-centre/kpi-cards/adobe-commerce/total-discount-used)                | Includes shipping discount portion.                                      |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)                         | Refunded shipping reduces net; this card is creation-time gross.         |
| [`shipstation.shipping_cost`](/nerve-centre/shipstation/shipping_cost)                      | Carrier-side cost; the merchant-paid figure for true margin.             |
| [`shopify.total_shipping`](/nerve-centre/kpi-cards/shopify/total-shipping-revenue)          | Shopify peer.                                                            |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Shipping** with date range matching the period. Total at the bottom should match this card. Default uses `base_currency`; switch this card to `base_shipping_amount` for like-for-like.

For per-method breakdown:

> **Reports > Sales > Shipping** with "Show By" = "Shipping Method". Shows shipping revenue per carrier/service.

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                                                                                | Direction of divergence                        |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| **Currency**. Admin defaults to `base_shipping_amount`; this card defaults to display-currency mixed `shipping_amount`.                                                                               | Material for multi-currency stores             |
| **Reports indexer lag**. Reports > Sales > Shipping uses nightly aggregated tables. This card refreshes every 5-15 min.                                                                               | Vortex IQ ahead by \~12-24h on most-recent day |
| **Cancelled inclusion**. Card excludes cancelled by default; Admin reports include or exclude depending on status filter. Cancelled orders typically have `shipping_amount=0` so the impact is small. | Minor                                          |
| **Status filter**. Admin reports default to "Status = Any". Match unless overridden.                                                                                                                  | None expected                                  |
| **Time-zone, sync lag**. Standard.                                                                                                                                                                    | Minor                                          |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                   | Expected relationship                                                                                                              | What divergence tells you                                                           |
| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| [`shipstation.shipping_cost`](/nerve-centre/shipstation/shipping_cost) | Carrier-paid cost. Merchant collected (this card) − carrier paid = gross shipping margin (before considering free-ship absorption) | If carrier-paid > collected, shipping is a cost centre; renegotiate or raise rates. |
| [`easypost.shipping_cost`](/nerve-centre/easypost/shipping_cost)       | EasyPost equivalent if used                                                                                                        | Same logic.                                                                         |
| Sum of (Royal Mail postage + DHL bill + …)                             | Should approximately match ShipStation total                                                                                       | Reconciles carrier integration vs invoices.                                         |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.total_shipping`](/nerve-centre/kpi-cards/shopify/total-shipping-revenue)
  * [`bigcommerce.total_shipping`](/nerve-centre/kpi-cards/bigcommerce/total-shipping-revenue)
</details>

## Known limitations / merchant FAQs

**Why is my "shipping revenue" number lower than the customer-facing total on invoices?**
Because Adobe stores shipping excl-tax in `shipping_amount` and the tax separately in `shipping_tax_amount`. Customer invoices show the inc-tax sum. Add them for the customer-facing figure: `SUM(shipping_amount + shipping_tax_amount)`. The card's headline excl-tax view aligns with how Finance books shipping revenue (net) in the GL.

**Free shipping is hurting my number, can I separate it?**
Free shipping isn't "hurting" the number; it just doesn't contribute. The pre-discount listed shipping (`shipping_amount + shipping_discount_amount`) shows what shipping would have been without promos. The discount portion is the cost of the free-ship strategy.

**Refunded shipping, where is it?**
On Credit Memos as `creditmemo.shipping_amount`. Aggregate via [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value). Net shipping = this card − refunded shipping. The card is intentionally creation-time gross because Finance books the refund separately.

**B2B freight orders aren't showing, why?**
Many B2B sellers charge freight outside the platform (carrier invoices the merchant after shipment, merchant invoices the customer separately). Those orders have `shipping_amount=0` in Adobe. To capture them, integrate the freight invoicing system (e.g., a 3PL connector) and combine.

**My multi-currency total looks weird, why?**
Mixed-currency `shipping_amount` is summed without FX. A USD store contributing \$5,000 and a GBP store contributing £4,000 sums to "9,000" with no unit. Toggle to `base_shipping_amount` (FX-converted to store base currency at order time) for a meaningful total.

**Why doesn't ShipStation match?**
ShipStation knows what you paid carriers (cost). This card knows what customers paid you (revenue). Both are correct at their endpoint. The interesting calculation is cost − revenue = margin (positive = you are profitable on shipping; negative = you are absorbing shipping cost as marketing).

**My free-ship threshold is £50; I see lots of orders just under £50, why?**
That is healthy. Free-ship thresholds intentionally pull AOV up via the "I might as well add another item" psychology. The cluster just under £50 is customers who decided not to add. The cluster just over £50 is the threshold-driven AOV lift. Together they suggest the threshold is calibrated to your AOV distribution.

**A spike in shipping revenue over the weekend, real or admin-bulk?**
Adobe Admin can create bulk orders manually (B2B PO imports). Those have `created_at = bulk-import time` even if real customer orders were over weekdays. Filter `admin_created` orders for the true customer-paid signal.

**Can I see this by Customer Group?**
Yes. Slice via Customer Group filter. B2B groups often have negotiated freight outside Adobe (so look low here); DTC groups carry the bulk of card-paid shipping.

**Why does today's number sometimes drop?**
Today's data is in-progress; the card might display "(in progress)" on the trailing point. Otherwise: a cancellation just occurred and the card excludes cancelled orders, so the cancelled order's shipping is removed retroactively. This is correct.

***

### Tracked live in Vortex IQ Nerve Centre

*Total Shipping Revenue* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Total Tax Collected, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/total-tax-collected

Total Tax Collected for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> The total tax (VAT, sales tax, GST) collected on orders in the period. The single-figure aggregate that pairs with [Tax Analysis](/nerve-centre/kpi-cards/adobe-commerce/tax-analysis) (the per-jurisdiction breakdown) and [Tax Over Time](/nerve-centre/kpi-cards/adobe-commerce/tax-collected-over-time) (the daily series). For Finance: this is "gross tax collected"; subtract refunded tax (Credit Memo `tax_amount`) for "net tax owed".

|                         |                                                                                                                                                                           |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**      | `SUM(tax_amount)` over orders created in the 30-day window. `tax_amount` is the per-order tax (sum of product-tax + shipping-tax).                                        |
| **API field**           | `tax_amount`, `base_tax_amount`, `shipping_tax_amount` from `GET /rest/V1/orders`.                                                                                        |
| **VAT / tax treatment** | The card IS the tax view. Includes both product tax and shipping tax. Toggle to product-only via `tax_amount - shipping_tax_amount`.                                      |
| **Shipping inclusion**  | Shipping tax included by default. UK shipping is taxable at standard 20%; some US states tax shipping (CA, NY, TX) and others don't.                                      |
| **Discounts**           | Tax computed post-discount per Magento default (configurable via `Apply Customer Tax`).                                                                                   |
| **Cancelled orders**    | Excluded by default. Cancelled-order tax shouldn't appear on a VAT return.                                                                                                |
| **Refunds**             | Not subtracted, the card is creation-time. Net-of-refund: subtract `SUM(creditmemo.tax_amount)` from [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value). |
| **Currency**            | Mixed-currency display by default. `base_tax_amount` for FX-neutral. **For VAT filing, always use base currency.**                                                        |
| **Channels**            | All Adobe Commerce sources.                                                                                                                                               |
| **Multi-store scope**   | All Store Views by default. Per-Store-View slicing essential for VAT filings (each Store View typically maps to one tax jurisdiction).                                    |
| **Time window**         | `30D` rolling. Quarterly windowing useful for tax filing (UK quarterly VAT, US quarterly sales tax).                                                                      |
| **Alert trigger**       | None on this card directly.                                                                                                                                               |
| **Roles**               | owner                                                                                                                                                                     |

## Calculation

```
SUM(tax_amount)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A B2B+DTC merchant on Adobe Commerce 2.4.7. UK base, GBP. UK + US Store Views with Avalara for US. Period: 14 Apr 26 to 13 May 26 (30 days).

**Tax aggregates:**

| Component                                 | Value            | Notes                                                      |
| ----------------------------------------- | ---------------- | ---------------------------------------------------------- |
| `SUM(tax_amount)` (this card, default)    | £142,800 (mixed) | combined UK + US, mixed currency                           |
| `SUM(base_tax_amount)`                    | £156,200         | FX-converted to GBP base                                   |
| `SUM(shipping_tax_amount)`                | £11,680          | shipping VAT only (UK; US shipping taxes only some states) |
| Product-only tax (`tax - shipping_tax`)   | £131,120         | for product-tax filing                                     |
| `SUM(creditmemo.tax_amount)` (refunded)   | £8,420           | reversed VAT on Credit Memos                               |
| **Net tax for filing (gross − refunded)** | **£134,380**     |                                                            |

**Per Store View:**

| Store View    | `SUM(tax_amount)`                     | Avg per order                         | Tax engine                                |
| ------------- | ------------------------------------- | ------------------------------------- | ----------------------------------------- |
| UK Store View | £126,000                              | £69.20 / order                        | Native Magento (20% standard, 5% reduced) |
| US Store View | \$90,500 (≈ £72,400 at indicative FX) | \$24.60 / order avg (varies by state) | Avalara                                   |

**Comparison to prior 30 days:**

| Window              | Total tax  | Revenue   | Effective rate |
| ------------------- | ---------- | --------- | -------------- |
| 14 Apr to 13 May 26 | £142,800   | £950,000  | 15.0%          |
| 15 Mar to 13 Apr 26 | £128,400   | £870,000  | 14.8%          |
| **Change**          | **+11.2%** | **+9.2%** | **+0.2 pp**    |

**Insight pattern:**

1. **Effective rate of 15.0%** is the blended rate across UK + US. UK alone is closer to 20% on Standard goods; US alone is 6-9% depending on states. The blend reflects the customer mix.
2. **Effective rate moved 0.2 pp.** Most likely the UK reduced-rate children's-clothing reclassification on 12 Mar pulled the UK blend slightly down (more reduced-5% rates).
3. **Net for filing: £134,380.** Finance should remit £126,000 (UK) − £6,800 (refunded UK VAT) = £119,200 to HMRC, and the equivalent net-of-refund US figure to each state via Avalara.
4. **Avalara reconciliation.** Avalara's Liability Worksheet for the same period should report the US-side \$90,500. If Avalara reports less, some orders failed to commit; reconcile via the AvaTax tools menu.
5. **Cross-link with [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue):** revenue rose 9.2%, tax rose 11.2%. Tax growing faster than revenue suggests either (a) more high-tax-jurisdiction orders (US customers with new state rates), or (b) fewer tax-exempt B2B orders. Drill into [Tax Analysis](/nerve-centre/kpi-cards/adobe-commerce/tax-analysis) per-jurisdiction to confirm.
6. **Quarterly tax filing window:** for the UK April-June quarter, this card configured to "Custom: 1 Apr to 30 Jun" gives the gross UK tax. Subtract refunded VAT from Credit Memos in the same window. Submit to HMRC.

## Sibling cards merchants should reference together

| Card                                                                            | Why pair it with Total Tax                            |
| ------------------------------------------------------------------------------- | ----------------------------------------------------- |
| [Tax Analysis](/nerve-centre/kpi-cards/adobe-commerce/tax-analysis)             | Per-jurisdiction breakdown.                           |
| [Tax Over Time](/nerve-centre/kpi-cards/adobe-commerce/tax-collected-over-time) | Daily series; useful for spotting tax-engine outages. |
| [Total Revenue](/nerve-centre/kpi-cards/adobe-commerce/total-revenue)           | Denominator-of-context; effective tax rate.           |
| [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value)             | Refunded tax to subtract for net VAT.                 |
| [`avalara.tax_liability_summary`](/nerve-centre/avalara/tax_liability_summary)  | Avalara-side total; should match for US merchants.    |
| [`shopify.total_tax`](/nerve-centre/kpi-cards/shopify/total-tax-collected)      | Cross-platform reference.                             |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Reports > Sales > Tax** with the date range matching the period. The grand total at the bottom should approximately match this card after currency-and-cancellation adjustments.

For the order-level audit:

> **Sales > Orders** with a custom column selector showing Tax Amount, exported to CSV; sum the Tax Amount column.

For Avalara users:

> Avalara Admin > Reports > Liability Worksheet for the period. The US-side of this card should match Avalara's total to the cent (after subtracting failed-commit orders).

**Why our number may legitimately differ from Adobe Commerce Admin:**

| Reason                                                                                                                                               | Direction of divergence            |
| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| **Currency**. Reports default to `base_tax_amount`; this card default is mixed-currency `tax_amount`. Switch to `base_tax_amount` for like-for-like. | Material for multi-currency stores |
| **Reports indexer lag**. Reports use nightly aggregation.                                                                                            | Vortex IQ ahead by \~12-24h        |
| **Cancelled inclusion**. Card excludes cancelled by default. Reports may include depending on filter.                                                | Standard                           |
| **Avalara commit failures**. Reports may show locally-computed tax for failed-commit orders; Avalara dashboard won't see them.                       | Per-order divergence               |
| **Time-zone, sync lag**. Standard.                                                                                                                   | Minor                              |

**Internal identity (within Adobe Commerce):**

`total_tax = SUM(tax_amount) over orders in period`

Component cards (self-consistency, not reconciliation):

* [`adobe_commerce.tax_over_time`](/nerve-centre/kpi-cards/adobe-commerce/tax-collected-over-time) (daily aggregation should sum to this card's period total)
* [`adobe_commerce.tax_analysis`](/nerve-centre/kpi-cards/adobe-commerce/tax-analysis) (per-jurisdiction sum should equal this card)

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Card                                                                           | Expected relationship                           | What divergence tells you                                      |
| ------------------------------------------------------------------------------ | ----------------------------------------------- | -------------------------------------------------------------- |
| [`avalara.tax_liability_summary`](/nerve-centre/avalara/tax_liability_summary) | Avalara total ≈ this card's US-side             | Failed commits, rate-table drift, or orders bypassing Avalara. |
| [`vertex.tax_summary`](/nerve-centre/vertex/tax_summary)                       | Vertex equivalent                               | Same logic.                                                    |
| HMRC VAT submission                                                            | This card UK-side − refunded VAT = Box 1 figure | Submission record.                                             |

***

<details>
  <summary><em>Documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.total_tax`](/nerve-centre/kpi-cards/shopify/total-tax-collected)
  * [`bigcommerce.total_tax`](/nerve-centre/kpi-cards/bigcommerce/total-tax-collected)
</details>

## Known limitations / merchant FAQs

**Why is mixed-currency the default? It makes the number look wrong.**
For trend visualisation, mixed-currency is fine, the shape of the chart is what matters. For Finance reconciliation and tax filing, switch to `base_tax_amount` (FX-converted to store base currency at order time). The card supports both views.

**Refunded tax isn't subtracted, but I owe HMRC the net, what do I do?**
For VAT submission: take this card's UK-side total minus the UK-side `creditmemo.tax_amount` from [Refund Value](/nerve-centre/kpi-cards/adobe-commerce/refund-value). The Vortex IQ workspace can pre-compute the net via the "Tax Filing" report.

**Why does Avalara say I owe a different amount?**
Three causes: (1) failed commits (orders that didn't reach Avalara); (2) currency framing (Avalara is in USD; this card mixes); (3) different status filters (Avalara may include or exclude cancelled depending on its config). Reconcile via base-currency mode and ensure cancelled-handling matches.

**My multi-store has zero-rated UK sales but tax appears on the chart, why?**
Zero-rated transactions have `tax_amount=0` per order; they don't add to this card. If you see tax appearing for a "zero-rated" Store View, then either the products aren't actually zero-rated (check product tax class) or non-zero-rated products are being sold on that Store View.

**My B2B customer has a resale certificate, why is tax still showing on their orders?**
The certificate either isn't uploaded to Avalara CertCapture, or hasn't been linked to the customer's Adobe `customer_id`, or the customer is in the wrong Customer Group. Adobe Commerce only honours tax-exemption when the conditions match the rule. **Customers > All Customers > \[customer]** > Account Information should show "Tax Class = Tax Exempt" and Avalara CertCapture should show an active certificate.

**Why does today's number stop updating?**
Tax updates with each new order (which already happens every 5-15 min). If the number is genuinely stale, the OpenSearch indexer is probably running re-aggregation; wait one full refresh.

**B2B with net-30 PO terms, when is the tax recognised?**
At order creation. Adobe records `tax_amount` when the order is placed, regardless of whether the invoice is paid. So `pending_payment` orders contribute their tax to this card. Most jurisdictions allow tax to be remitted on the invoice date even for net-30 terms; check with your tax advisor.

**A new tax rule was added mid-period, the rate effective from?**
Magento applies tax rules prospectively. The new rate kicks in from the moment it's saved in **Stores > Configuration > Sales > Tax**. Orders before that point retain their original rate. The chart will show a step change on the day of the rule update.

**Why does the per-Store-View slice not sum to the combined?**
Most likely a Store-View-less order (admin-created with no Store View). Adobe Commerce occasionally creates orders without a Store View if the admin form is not properly scoped. Filter to find these ([Order State Distribution](/nerve-centre/kpi-cards/adobe-commerce/order-state-breakdown) with Store View = "(unscoped)") and assign them retroactively.

**Can I see VAT separately from sales tax?**
Yes. UK Store View = VAT; US Store View = sales tax. Slice per Store View, or per tax-engine source (native = mostly VAT for UK; Avalara = sales tax for US).

***

### Tracked live in Vortex IQ Nerve Centre

*Total Tax Collected* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Unique Customers, Adobe Commerce
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adobe-commerce/unique-customers

Unique Customers for Adobe Commerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Distinct customer count over the trailing 30 days, computed via `CARDINALITY(customer_email)` on the orders index. Adobe Commerce uses email as the practical customer identifier (the `customer_id` field is null for guest orders). The count therefore conflates registered customers with guests-using-the-same-email. On Adobe Commerce specifically, the card distinguishes B2B Companies (single Company can have many billing emails) from consumer accounts.

|                                                        |                                                                                                                                                                                     |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                                     | `CARDINALITY(customer_email)` over orders in the 30-day window. Distinct emails. Compared to prior 30-day for delta.                                                                |
| **API field**                                          | `customer_email` from `GET /rest/V1/orders`. Optionally `customer_id` for registered-only counts.                                                                                   |
| **VAT / tax treatment**                                | n/a, this is a count metric.                                                                                                                                                        |
| **Shipping inclusion**                                 | n/a.                                                                                                                                                                                |
| **Discounts**                                          | n/a.                                                                                                                                                                                |
| **Credit Memo refund treatment**                       | A customer who ordered then was fully refunded still counts. They placed an order, the count reflects intent.                                                                       |
| **`state` machine inclusion**                          | All states except `canceled` (a customer whose only order was cancelled is not really an active customer).                                                                          |
| **`pending_payment` quirk**                            | Included. B2B net-30 customers whose orders sit in `pending_payment` are real customers in pipeline.                                                                                |
| **Multi-currency `grand_total` vs `base_grand_total`** | n/a.                                                                                                                                                                                |
| **Store View scope (`store_id`)**                      | All Store Views by default. The same email across multiple Store Views counts as one customer.                                                                                      |
| **B2B Company aggregation**                            | Each Company is counted as one customer when filtered to the B2B segment, even if multiple buyer emails sit under the Company. This is configurable; the default groups by Company. |
| **Time window**                                        | `30D vsP`.                                                                                                                                                                          |
| **Alert trigger**                                      | None by default.                                                                                                                                                                    |
| **Roles**                                              | owner, marketing                                                                                                                                                                    |

## Calculation

```
CARDINALITY(customer_email.keyword)
  WHERE date BETWEEN [period_start, period_end]
```

## Worked example

A homewares brand on Adobe Commerce 2.4.6 with US, UK, and B2B Store Views. Snapshot Monday 4 May 26.

**Customer count by Store View:**

| Store View            | Distinct emails (30D) | Distinct registered customers       | Distinct B2B Companies |
| --------------------- | --------------------- | ----------------------------------- | ---------------------- |
| US consumer           | 2,420                 | 1,840                               | n/a                    |
| UK consumer           | 1,910                 | 1,520                               | n/a                    |
| B2B portal            | 188 distinct emails   | 156 customers (linked to Companies) | 142 distinct Companies |
| **Blended (deduped)** | **4,396 emails**      | **3,360 registered**                | n/a                    |

**Vs prior 30-day:**

| Metric                | Current | Prior | Delta |
| --------------------- | ------- | ----- | ----- |
| Total distinct emails | 4,396   | 4,180 | +5.2% |
| Registered customers  | 3,360   | 3,210 | +4.7% |
| Guest emails          | 1,036   | 970   | +6.8% |
| B2B Companies         | 142     | 138   | +2.9% |

What this is telling marketing:

1. **Customer base grew 5.2% MoM.** Healthy.
2. **Guest growth (6.8%) is outpacing registered (4.7%).** New traffic is converting but not creating accounts. This may reflect a deliberate "guest checkout first" UX, or it may be a missed opportunity for retention (registered customers are worth 2 to 3x lifetime value of guests in most categories).
3. **B2B Company count grew slightly** (+2.9%, 4 net new Companies). Each Company is potentially worth tens of thousands per year, so 4 new Companies is a measurable acquisition win.
4. **The 188 B2B emails belong to 142 Companies**: average 1.3 buyer-emails per Company. Most Companies have one buyer; some have 2 to 5. This matters for B2B email marketing: each Company should receive one strategic-Sales-touch communication, not 1.3.
5. **Cross-checking [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)**: of the 3,360 registered customers, 1,420 are first-time orderers in this period (new customers). This means 1,940 are returning, a 57.7% repeat-share among registered customers. Cross with [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate) for the lifetime view.
6. **Strategic question**: should marketing push guest-to-registered conversion (post-purchase email cadence with account-creation incentive)? On a 1,036-guest base growing at 6.8%, converting 30% to registered would add \~310 registered customers/month, materially improving retention metrics.

The point: customer count is the simplest acquisition metric, but on Adobe Commerce the registered-vs-guest split and the B2B-Company-vs-emails split add necessary nuance.

## Sibling cards merchants should reference together

| Card                                                                                        | Why pair it with Customer Count                                           |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers)                       | First-time orderers, the leading-edge subset of customer count growth.    |
| [Customer Trend](/nerve-centre/kpi-cards/adobe-commerce/customer-acquisition-trend)         | Trend chart visualising count over time.                                  |
| [Repeat Customer Rate](/nerve-centre/kpi-cards/adobe-commerce/repeat-customer-rate)         | Loyalty companion. High customer count + low repeat = leaky bucket.       |
| [Guest vs Account Checkout](/nerve-centre/kpi-cards/adobe-commerce/guest-vs-account-orders) | Decomposes count into registered vs guest.                                |
| [Customer Segments](/nerve-centre/kpi-cards/adobe-commerce/customer-spend-segments)         | LTV-cohort decomposition.                                                 |
| [B2B Revenue Share](/nerve-centre/kpi-cards/adobe-commerce/b2b-revenue-share)               | The dollar-weighted view. Customer count is people-weighted; both matter. |
| [Total Orders](/nerve-centre/kpi-cards/adobe-commerce/total-orders)                         | Order count divided by customer count = order frequency.                  |
| [`shopify.customer_count`](/nerve-centre/kpi-cards/shopify/unique-customers)                | Cross-platform peer.                                                      |

## Reconciling against the vendor's own dashboard

**Where to look in Adobe Commerce Admin:**

> **Customers > All Customers** lists registered customers; the grid total at the bottom shows the count. This excludes guests by definition (guests don't have customer entities).

> **Reports > Customers > Customers by Number of Orders** is the closest aggregated view, ranks customers by order count.

> **Sales > Orders** filtered to a date range has a "Customer Email" column; the distinct-email count is your "this card" equivalent. Group by Customer Email in CSV export to compute manually.

For B2B (Adobe Commerce paid edition):

> **Customers > Companies** counts Company entities. **Customers > Companies > \[Company] > Users** shows users per Company.

**Why our number may legitimately differ from Admin:**

| Reason                                                                                                                                                                                                                         | Direction of divergence                         |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- |
| **Guest inclusion**. Card includes guest emails; Admin's customer list shows registered only.                                                                                                                                  | Card count higher                               |
| **Multi-Store-View deduplication**. Card dedupes the same email across Store Views. Admin's customer list often shows duplicate customer entities for the same email if the customer registered separately on each Store View. | Card count lower than admin all-Store-Views sum |
| **B2B Company aggregation**. Card can group by Company; Admin counts buyer-emails.                                                                                                                                             | Material if many Companies have multiple buyers |
| **Time window**. Card uses 30-day-ordering activity; Admin's customer list is all-time-registered.                                                                                                                             | Card count smaller                              |
| **Sync lag**. Card uses OpenSearch sync (5-15 min); Admin live.                                                                                                                                                                | Negligible at 30D                               |

**Cross-connector reconciliation (when these connectors are connected for this merchant):**

| Pair                                                                             | Expected relationship                                                    | What divergence tells you                                                                                                                             |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`google_analytics.ga_purchasers`](/nerve-centre/google_analytics/ga_purchasers) | GA4 purchasers ≈ Adobe customer count × (1 - tracking gap)               | GA4 typically misses 10-25%. Material lower divergence (>25%) suggests GA4 tag-fire issues at checkout.                                               |
| ESP active-list size                                                             | ESP list usually exceeds customer count (subscribers who haven't bought) | Inverse relationship would be alarming (customers buying without subscribing); sometimes legitimate (B2B where buyers don't sign up to consumer ESP). |

***

<details>
  <summary><em>Same-metric documentation cross-reference (for agencies running multiple platforms)</em></summary>

  * [`shopify.customer_count`](/nerve-centre/kpi-cards/shopify/unique-customers)
  * [`bigcommerce.customer_count`](/nerve-centre/kpi-cards/bigcommerce/unique-customers)
</details>

## Known limitations / merchant FAQs

**My customer count seems lower than my CRM, why?**
The card counts customers who placed an order in the trailing 30 days. Your CRM probably contains all-time-registered customers, including dormant or churned. For a like-for-like, filter your CRM to "ordered in last 30 days".

**Why use email rather than `customer_id` for distinct counting?**
Adobe Commerce stores `customer_email` on every order regardless of guest vs registered status. `customer_id` is null for guest orders. Using `customer_email` captures both. The trade-off: a guest who later registered with the same email is counted once across both order types (correct behaviour); a guest who used different emails on different orders counts as multiple customers (overcount).

**Adobe Commerce vs Magento Open Source: difference?**
None at the calculation. The B2B Companies module on the paid edition lets the card group by Company; Open Source merchants without the module count by buyer-email. For Open Source merchants who want B2B Company aggregation, custom attributes can be configured but it's manual work.

**My multi-store Adobe Commerce, can the same customer count differently per Store View?**
Yes if they registered separately on each Store View (Adobe Commerce historically created per-Store-View customer entities; modern installations use `customer_share_account_information` to share across websites). The card dedupes by email regardless. If your historical data has duplicate registrations, the card's count is more accurate than the Admin customer-grid count.

**B2B Company has 5 buyer emails, do I count it as 1 or 5?**
Depends on the question. For "how many decision-making units do we serve", group by Company (count = 1). For "how many people log in and order", count by email (count = 5). The card defaults to grouping by Company on the B2B segment; configurable per the use case.

**Why doesn't this card include cancelled orders?**
A customer whose only order was cancelled is functionally equivalent to a customer who never ordered. Counting them inflates customer count without reflecting purchasing behaviour. The exception: Adobe Commerce auto-cancellations from `pending_payment` timeout where the customer would have been a real customer if the gateway worked. Those are excluded too, which understates "intent to be a customer" slightly. For a count-of-intent metric, see Quote-Create count via [Cart-Abandonment Spike Alert](/nerve-centre/kpi-cards/adobe-commerce/cart-abandonment-spike-alert).

**My customer count grew but revenue is flat, what's happening?**
Likely AOV contraction. New customers are smaller-basket than existing customers; if customer count grew faster than revenue, the new customers are buying less per visit. Cross-check [AOV](/nerve-centre/kpi-cards/adobe-commerce/average-order-value) and [New Customers](/nerve-centre/kpi-cards/adobe-commerce/new-customers). This is the "successful acquisition, weak retention" pattern that needs an early-customer cadence intervention.

***

### Tracked live in Vortex IQ Nerve Centre

*Unique Customers* is one of hundreds of KPI pulses Vortex IQ tracks across Adobe Commerce 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.


# Active Dynamic Ads on Out-of-Stock SKUs, AdRoll
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/active-dynamic-ads-on-out-of-stock-skus

Active Dynamic Ads on Out-of-Stock SKUs for AdRoll stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Cross-Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> A cross-platform alert that joins AdRoll's live Dynamic Ads serving against your commerce platform's real-time stock levels and flags every case where AdRoll is still running a dynamic product ad for a SKU that is actually out of stock. AdRoll's Dynamic Ads are driven entirely by the product catalogue synced from your store, so an out-of-stock SKU left in the eligible pool is pure waste: you pay the click, the shopper lands on a product page they cannot buy, they bounce, and the conversion is impossible by definition. Because AdRoll is retargeting-first, the shopper has usually already viewed or carted that exact SKU, which makes the sold-out landing experience even more jarring. This card only exists because Vortex IQ sees both sides, AdRoll's serving layer and the commerce stock ledger, in one place. It is the highest-confidence "stop paying for this right now" signal in the AdRoll manifest, because there is no ambiguity: a quantity of zero cannot convert.

|                                      |                                                                                                                                                                                                                                                                                                                   |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                   | The count and the at-risk spend of active AdRoll Dynamic Ads whose target SKU has a current stock quantity of zero on the connected commerce platform (Shopify, BigCommerce, or Adobe Commerce). The alert is the breach state; the displayed value is the offending SKU list and the spend exposed to those ads. |
| **Cost basis**                       | **CPC-dominant.** Every click on an out-of-stock dynamic ad is billed and structurally cannot convert, so the cost basis is effectively a waste floor. CPM impressions on the same creative are softer waste but still spend against a dead SKU.                                                                  |
| **Currency**                         | Advertiser-account currency for the at-risk spend figure. The SKU match itself is currency-neutral.                                                                                                                                                                                                               |
| **Conversion attribution**           | Not applicable in the usual sense, the whole point is that conversion is impossible. Any attributed conversion on a zero-stock SKU is almost always a lagged credit from before the stock-out, picked up through the AdRoll Pixel.                                                                                |
| **Attribution window**               | 30-day click + 1-day view default (AdRoll's standard) for any residual lagged credit.                                                                                                                                                                                                                             |
| **Bot / invalid traffic**            | Not the relevant axis here; the waste is structural regardless of traffic quality.                                                                                                                                                                                                                                |
| **iOS 14.5+ ATT impact on the card** | **Low.** This card keys off stock state and ad-serving state, not Pixel attribution, so ATT and signal loss do not distort it. That is part of why it is high-confidence.                                                                                                                                         |
| **Catalogue-feed dependency**        | **Central.** The usual cause is a product feed that has not synced the stock-out yet: the storefront shows zero but AdRoll's catalogue still lists the SKU as available, so Dynamic Ads keep rendering it. Feed cadence is the lever.                                                                             |
| **Time window**                      | `RT` (real-time). Stock can flip to zero at any moment, so the join evaluates continuously rather than on a fixed period.                                                                                                                                                                                         |
| **Alert trigger**                    | `active dynamic ad on commerce-sibling SKU with qty=0`. An illustrative rule; the breach fires the moment a live AdRoll Dynamic Ad targets a SKU whose connected-store quantity is zero.                                                                                                                          |
| **Roles**                            | owner, marketing, operations                                                                                                                                                                                                                                                                                      |

## Calculation

Calculated automatically by joining your AdRoll data with your connected commerce platform. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

A UK homeware DTC retailer on BigCommerce runs AdRoll Dynamic Ads retargeting across a 1,800-SKU catalogue, mostly site-visitor and cart-abandoner audiences with a small prospecting layer. A weekend clearance sold through three hero SKUs faster than the feed refreshed. The join evaluates AdRoll's live Dynamic Ads serving against BigCommerce stock. Account currency GBP. Window is real-time, snapshot 19 Jun 26.

| SKU      | Product                    | BigCommerce qty | Still served by AdRoll? | Spend last 24h (GBP) | State  |
| -------- | -------------------------- | --------------- | ----------------------- | -------------------- | ------ |
| HOM-2207 | Linen Duvet Set, double    | 0               | Yes                     | 280                  | BREACH |
| HOM-1944 | Stoneware Dinner Set, 12pc | 0               | Yes                     | 165                  | BREACH |
| HOM-2310 | Wool Throw, charcoal       | 0               | Yes                     | 90                   | BREACH |
| HOM-2208 | Linen Duvet Set, king      | 52              | Yes                     | 140                  | OK     |

What the pattern tells you:

1. **Three hero SKUs at quantity zero are still being served.** That is roughly GBP 535 of at-risk spend in a single day on ads that cannot convert. Because these are retargeting placements, the clicks come from shoppers who already wanted the exact item, so click rates stay high and the waste accelerates. Every click sends a shopper to a sold-out product page. The waste is not hypothetical; it is billed and ongoing.
2. **The feed has not caught up to the stock-out.** BigCommerce recorded the sell-through, but AdRoll's catalogue still lists the three SKUs as in stock, so Dynamic Ads keep selecting them. The gap between the storefront and the synced feed is the entire problem, and feed cadence is the fix.
3. **A near-sibling SKU is fine.** The king-size duvet set (HOM-2208) is in stock and converting normally, which proves the campaign and audience are healthy. The fault is per-SKU stock-out, not a campaign-level failure, so the action is surgical, not a campaign pause.
4. **The fastest mitigation is a feed re-sync.** Force a catalogue push so AdRoll sees quantity zero and drops the SKUs from the dynamic pool automatically. Most stores running daily feed sync are exposed during clearance and flash events; moving to a faster stock sync closes the window.
5. **The structural fix is stock-aware feed rules.** Configure the product feed export to exclude or suppress zero-quantity SKUs at the source, so a stock-out removes the SKU from AdRoll's eligible pool the moment it happens rather than at the next scheduled sync.
6. **There may be a small residual conversion.** If any of these SKUs shows an attributed conversion in AdRoll, it is almost certainly lagged Pixel credit from a click before the stock-out, not a sale of an out-of-stock item.

Quick sanity tests:

* Breach concentrated on hero SKUs during a promotion = feed lag against fast sell-through, tighten sync cadence.
* Breach on a single SKU = isolated stock-out, suppress that SKU in the feed.
* Breach clears after a forced feed re-sync = confirmed feed-lag cause, no campaign change needed.
* Breach persists after re-sync = the feed export is not honouring stock state, fix the feed rule.
* At-risk spend is large relative to total = your feed cadence is too slow for your stock velocity.

## Sibling cards merchants should reference together

| Card                                                                                                                              | Why it matters next to Active Dynamic Ads on Out-of-Stock SKUs | What the combination tells you                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| [Spend on Campaigns with Active Feed Rejections](/nerve-centre/kpi-cards/adroll/spend-on-campaigns-with-active-feed-rejections)   | The other feed-driven waste card.                              | Stock-out waste and feed-rejection waste are the two ways a product feed costs you money; reviewing both gives the full feed-health bill.   |
| [Wasted-Spend Burst (retargeting pool exhaustion)](/nerve-centre/kpi-cards/adroll/wasted-spend-burst-retargeting-pool-exhaustion) | The acute zero-return burst detector.                          | If a hero SKU stock-out is large enough, it can also trip the burst card; both firing names the SKU and sizes the bleed.                    |
| [Wasted Spend](/nerve-centre/kpi-cards/adroll/wasted-spend)                                                                       | The trailing-period waste audit.                               | Persistent out-of-stock serving shows up here as chronic waste; this card catches it acutely.                                               |
| [Retargeting ROAS Dropped Below Threshold](/nerve-centre/kpi-cards/adroll/retargeting-roas-dropped-below-threshold)               | The efficiency tripwire for your core audience.                | Out-of-stock serving silently drags retargeting ROAS; clearing it is a direct efficiency win on the audience that matters most.             |
| [ROAS](/nerve-centre/kpi-cards/adroll/roas)                                                                                       | The efficiency headline.                                       | Out-of-stock serving quietly suppresses ROAS; removing dead SKUs lifts return without touching budget.                                      |
| [Landing Pages with Poor Web Vitals](/nerve-centre/kpi-cards/adroll/landing-pages-with-poor-web-vitals)                           | The other "the click lands badly" card.                        | A sold-out page and a slow page are both broken landing experiences; together they show where paid clicks are being wasted after the click. |

## Reconciling against AdRoll

**Where to look in AdRoll's own dashboard:**

> In the AdRoll dashboard at [app.adroll.com](https://app.adroll.com), open Product Feed (under Audiences and catalogue settings) to see which SKUs AdRoll currently treats as available, and your commerce platform's inventory view (Shopify Admin → Products → Inventory, BigCommerce → Products, or Adobe Commerce → Catalog → Products) for the live stock quantity.

AdRoll on its own cannot show you this card, because AdRoll only knows what its synced catalogue says, not what your storefront actually has in stock at this second. That is the cross-platform gap Vortex IQ closes. To reconcile manually, take the breached SKU list from this card, look each one up in AdRoll's Product Feed (it will show as available, which is the bug) and in your commerce inventory (it will show quantity zero, which is the truth). The mismatch between the two is exactly what this card surfaces automatically.

**Why our number may legitimately differ from a manual check:**

| Reason                          | Direction          | Why                                                                                                                                                                    |
| ------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Feed-sync timing**            | Moves with cadence | The breach reflects the moment-in-time gap between storefront stock and AdRoll's catalogue; a manual check minutes later may show fewer SKUs if a sync ran in between. |
| **Stock buffer rules**          | Either direction   | Some stores reserve safety stock or count committed-but-unfulfilled units; whether "quantity zero" means truly sold out depends on your inventory policy.              |
| **Multi-location inventory**    | Ours may differ    | If stock is summed across warehouses or locations, the relevant quantity is the sellable total, which the join uses; a single-location view can read differently.      |
| **Pre-order or backorder SKUs** | Ours may over-flag | A SKU at quantity zero that is still purchasable on backorder is not true waste; configure the feed rule to treat backorder SKUs as available.                         |

**Cross-connector reconciliation:**

This card is inherently cross-platform; the join is its whole reason for existing:

| Card                                                                                                                                                                                                                                                           | Expected relationship                                                                                                                    | What causes legitimate divergence                                                                                                            |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| [`shopify.inventory_on_hand`](/nerve-centre/kpi-cards/shopify/inventory-on-hand) / [`bigcommerce.inventory_level`](/nerve-centre/kpi-cards/bigcommerce/inventory-level) / [`adobe_commerce.stock_status`](/nerve-centre/kpi-cards/adobe-commerce/stock-status) | The commerce-platform stock truth is the authoritative side of the join; a SKU at zero there while AdRoll still serves it is the breach. | Inventory-policy nuances (safety stock, backorder, multi-location) decide what "out of stock" means; align the feed rule to the same policy. |
| [`shopify.total_revenue`](/nerve-centre/kpi-cards/shopify/total-revenue)                                                                                                                                                                                       | Helps size the opportunity cost: a high-velocity SKU that sold out is both lost sales and wasted ad spend.                               | A slow SKU stock-out wastes less spend than a hero SKU stock-out even at the same ad volume.                                                 |

## Known limitations / merchant FAQs

**Why does AdRoll keep serving ads for a product I have sold out?**
Because AdRoll serves Dynamic Ads from its synced catalogue, and the catalogue is only as fresh as your last feed sync. The storefront recorded the sell-through immediately, but AdRoll will not know until the next feed push tells it the quantity is zero. On a daily-sync store, that gap can be most of a day, long enough to waste real money during a fast-moving clearance. Tightening feed cadence is the direct fix.

**Is this really waste if the shopper might buy something else when they land?**
Some recovery happens, but you should not count on it, and it is even less likely on retargeting. The shopper was retargeted on a specific product they had already viewed or carted, found it sold out, and most will bounce rather than browse a substitute. Treat the spend as waste for planning purposes; any cross-sell recovery is a bonus, not a reason to tolerate the leak.

**What is the fastest way to stop the bleed when this fires?**
Force a product feed re-sync so AdRoll sees the zero quantity and drops the SKUs from the dynamic pool. That is minutes of work and stops the waste immediately. The durable fix is a feed export rule that suppresses or excludes zero-quantity SKUs at the source, so future stock-outs remove themselves from the eligible pool the moment they happen.

**My SKU is at zero but it is on backorder and still buyable, is this a false flag?**
Yes, and it is worth fixing. A backorder-enabled SKU at quantity zero can still convert, so it should not be treated as out of stock. Configure the feed rule and the inventory policy so backorder and pre-order SKUs report as available; otherwise the card will over-flag them. The card honours whatever stock definition your feed and inventory policy supply.

**Does ATT or Pixel signal loss affect this card?**
Barely, which is one of its strengths. The card keys off stock state and ad-serving state, both of which are observed directly rather than attributed through the AdRoll Pixel, so iOS ATT and Safari ITP do not distort it. A breach here is high-confidence: a quantity of zero cannot convert regardless of how attribution is measured.

**How is this different from feed rejections?**
Two distinct feed failures. A feed rejection means AdRoll refused the catalogue or specific items, so no creative renders at all. An out-of-stock-serving breach means the creative renders fine, the SKU just is not buyable. One stops ads; the other runs ads that cannot convert. Review both feed-health cards together for the complete picture.

**Does this matter more on retargeting than on prospecting?**
Yes, in practice it tends to hit retargeting hardest. Retargeting Dynamic Ads re-serve the precise SKUs a shopper already engaged with, so when one of those sells out the ad keeps chasing a warm, high-intent audience to a dead page, which is the most expensive form of this waste. Prospecting Dynamic Ads can hit it too, but the per-click intent is lower, so the sting is smaller per impression. Either way the fix is the same: keep the feed honest about stock.

***

### Tracked live in Vortex IQ Nerve Centre

*Active Dynamic Ads on Out-of-Stock SKUs* is one of hundreds of KPI pulses Vortex IQ tracks across AdRoll 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.


# AdRoll audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/audit

What the Vortex IQ AdRoll health audit checks: AdRoll: Spend Pacing, Retargeting ROAS & Cross-Platform Leak

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adroll) · [Audit Profile](/nerve-centre/kpi-cards/adroll/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adroll/sentiment)**

The questions an SMB / mid-market retargeting marketer asks at 9am on Monday: is AdRoll catching the cart-abandoners Meta and Google missed, is the Pixel still firing on conversion pages, is Roundtrip email retargeting still delivering, and is the prospecting-vs-retargeting spend mix right for the cohort. Cross-references commerce siblings (Shopify / BigCommerce / Adobe) and website\_performance for the highest-leverage findings - running dynamic catalog ads on out-of-stock SKUs and retargeting clicks into slow landing pages are the most common, most expensive, most fixable mistakes.

## What this audit checks

### Authentication & access

* OAuth refresh-token still valid against /auth/token (no re-auth required)
* Organization eid and advertisable eid resolve via /api/v1/organization
* Granted scopes cover read + write needed for reporting and pacing checks

### Spend & budget pacing

* Daily / lifetime budget utilisation per running campaign (under- or over-pacing vs budget)
* Wasted spend - zero-conversion spend above threshold on any running campaign (last 72h)
* Inactive / archived campaigns still consuming product-feed sync (hidden recurring data cost)
* Prospecting-vs-retargeting spend mix vs the acquisition-cohort target

### Campaign performance (ROAS / CTR / CPC)

* Cross-platform retargeting ROAS per campaign below merchant target (/api/v1/report/timeseries)
* Retargeting ROAS dropped >25% vs prior 7D same-day-of-week
* CTR below benchmark band on web / social / dynamic campaign types
* CPC creep - bidding pushing cost-per-click above category benchmark

### Conversion & attribution

* AdRoll Pixel firing on key conversion pages (purchase, signup-complete, add-to-cart)
* Conversion-rate below floor on running campaigns vs account average
* Roundtrip email retargeting deliverability and sender reputation after a send burst
* Attribution-window drift inflating reported conversions vs commerce-sibling orders

### Creative & audience health

* Custom audiences below AdRoll's 100-member delivery floor (won't serve, spend reallocates)
* Disapproved or rejected creatives in running campaigns (/api/v1/ad)
* Dynamic-product creatives falling back because the linked feed has rejections
* Stale creative pool - no new banner / native / video variants in >60d

### Cross-platform revenue at risk

* Active dynamic ads on out-of-stock SKUs (sibling = shopify / bigcommerce / adobe\_commerce product qty = 0)
* Retargeting landing pages with poor Web Vitals (sibling = website\_performance.page LCP\_p75 > 4000ms and CR \< 0.5x account avg)
* Branded retargeting clicks cannibalising organic (sibling = google\_search\_console branded organic queries)
* Roundtrip email audience overlapping the primary ESP (sibling = klaviyo / mailchimp) - paying to re-touch owned contacts

## Severity thresholds

| Signal            | Warn | Critical |
| ----------------- | ---- | -------- |
| `roas`            | 3.0  | -        |
| `ctr`             | 0.4  | -        |
| `conversion_rate` | 1.0  | -        |
| `budget_pacing`   | 70   | -        |

## Data sources

* `GET https://services.adroll.com/api/v1/organization` - Auth + org / advertisable eid sanity
* `GET https://services.adroll.com/api/v1/campaign` - Campaign state, budget, type and SKU join keys
* `GET https://services.adroll.com/api/v1/ad` - Creative status / format - disapprovals and feed-fallback checks
* `GET https://services.adroll.com/api/v1/report/timeseries` - Spend / impressions / clicks / conversions / ROAS time series
* `POST https://services.adroll.com/auth/token` - Refresh OAuth access token


# Branded Paid Clicks Cannibalising Organic, AdRoll
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/branded-paid-clicks-cannibalising-organic

Branded Paid Clicks Cannibalising Organic for AdRoll stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Cross-Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> A cross-platform gauge that estimates how much of your AdRoll retargeting spend is reaching shoppers who already know your brand and would very likely have returned on their own through direct or organic channels. AdRoll is retargeting-first: most spend chases site visitors and cart abandoners drawn from the AdRoll Pixel audience pool, and a meaningful slice of that pool is loyal, brand-aware buyers who were coming back anyway. Paying display, native, social or connected-TV impressions to win them back is margin you could reclaim. This card joins AdRoll click and conversion signal against your commerce-platform and analytics signal for repeat and direct-intent customers, and expresses the overlap as a percentage. It is not an argument to switch retargeting off, it is a tool to right-size the retargeting cycle so you are paying for incremental return, not re-buying customers you already had.

|                                      |                                                                                                                                                                                                                                                                                        |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                   | The estimated share of AdRoll branded retargeting clicks attributable to shoppers who show strong direct or organic return intent, expressed as a percentage gauge. Built by joining AdRoll retargeting click signal with commerce-platform repeat-customer and direct-session signal. |
| **Cost basis**                       | **CPC-dominant.** The reclaim opportunity is the CPC paid on clicks that would likely have arrived free, plus any view-attributed conversions credited to impressions on the loyal cohort.                                                                                             |
| **Currency**                         | The gauge value is a percentage. The implied reclaim is in advertiser-account currency when sized against retargeting spend.                                                                                                                                                           |
| **Conversion attribution**           | AdRoll claims these conversions under its default 30-day click + 1-day view window via the AdRoll Pixel; the cross-platform question is how many were incremental versus inevitable. This card estimates the inevitable share.                                                         |
| **Attribution window**               | 30D click + 1D view default on the AdRoll side (configurable in the dashboard). The cannibalisation estimate is a 30-day rolling read.                                                                                                                                                 |
| **Bot / invalid traffic**            | Excluded from both sides of the join where filtering identifies it.                                                                                                                                                                                                                    |
| **iOS 14.5+ ATT impact on the card** | **Moderate to high.** ATT and cookie deprecation shrink the AdRoll Pixel's identifiable pool, which concentrates retargeting on the most identifiable, most cookie-stable users, exactly the cohort most likely to return anyway, so post-ATT this percentage can drift upward.        |
| **Catalogue-feed dependency**        | Indirect. Dynamic Ads feed health affects which products get retargeted but not the brand-loyalty overlap this card measures.                                                                                                                                                          |
| **Time window**                      | `30D` (rolling 30 days). A monthly read smooths daily noise and matches the cadence of budget decisions.                                                                                                                                                                               |
| **Alert trigger**                    | `>30% of branded clicks would have been free organic`. An illustrative threshold; the gauge flags when the estimated cannibalised share crosses the ceiling, signalling room to reclaim margin.                                                                                        |
| **Roles**                            | owner, marketing                                                                                                                                                                                                                                                                       |

## Calculation

Calculated automatically by joining your AdRoll data with your connected commerce platform and analytics signal. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

Harbour & Field, a UK homeware DTC retailer with a strong repeat-purchase base, runs AdRoll retargeting (display plus a native line) alongside a healthy direct and organic channel. The gauge estimates how much of branded retargeting click volume overlaps with high direct-intent customers. Account currency GBP. Window is the rolling 30 days to 20 Jun 26.

| Cohort                                                   | Retargeting clicks | Conversions | Notes                                   |
| -------------------------------------------------------- | ------------------ | ----------- | --------------------------------------- |
| First-time visitors / cart abandoners, low direct-intent | 11,200             | 470         | Genuinely incremental retargeting value |
| Repeat buyers with strong direct/organic habit           | 6,800              | 620         | Likely to have returned without the ad  |
| **Total branded retargeting**                            | **18,000**         | **1,090**   | Gauge reads \~38% cannibalised          |

What the pattern tells you:

1. **Roughly 38% of branded retargeting clicks fall in the high-direct-intent cohort.** These are loyal buyers who type the URL, search the brand name, and reorder on their own rhythm. Paying a CPC to retarget them, or letting a 1-day view conversion claim their return, is largely re-buying a sale that was coming anyway. The gauge crossing the illustrative 30% line is the flag to act.
2. **The loyal cohort converts harder, which is misleading.** Notice the repeat cohort converts at a much higher rate (620 on 6,800 clicks) than the first-timers and abandoners. That high conversion rate is exactly why naive [ROAS](/nerve-centre/kpi-cards/adroll/roas) makes retargeting these users look brilliant, AdRoll takes credit for a sale that was always going to happen. Incrementality, not raw ROAS, is the right lens here.
3. **The reclaim is margin, not a kill switch.** The action is not to switch retargeting off. It is to cap frequency on the loyal cohort, exclude very recent purchasers from the retargeting audience, and shift the saved budget toward the genuinely incremental abandoner and first-time pool where the ad changes the outcome.
4. **Post-ATT this number tends to rise.** As the AdRoll Pixel's identifiable pool shrinks, retargeting concentrates on the most cookie-stable users, who skew loyal. So a rising gauge can partly reflect identity attrition rather than a new strategy fault. Read it alongside [AdRoll Pixel Tracking Broken](/nerve-centre/kpi-cards/adroll/adroll-pixel-tracking-broken).
5. **The honest test is a holdout.** The cleanest way to confirm cannibalisation is an incrementality holdout on the loyal cohort: suppress retargeting for a matched group and compare their return rate to the targeted group. If they return at nearly the same rate, the spend on that cohort was cannibalised. AdRoll supports holdout-style suppression by excluding a segment from the audience.

Quick sanity tests:

* Gauge high + strong direct/organic channel = real cannibalisation, cap frequency on loyalists.
* Gauge high + weak organic channel = suspect, the overlap may be over-estimated, validate with a holdout.
* Gauge rising post-ATT = partly identity attrition concentrating on loyal users, not only strategy.
* Gauge high + retargeting pool exhausted = double trouble, see [Wasted-Spend Burst (retargeting pool exhaustion)](/nerve-centre/kpi-cards/adroll/wasted-spend-burst-retargeting-pool-exhaustion).
* Gauge low = retargeting is mostly reaching genuinely incremental users, leave it alone.
* Holdout return rate near targeted rate = confirmed cannibalisation on that cohort.

## Sibling cards merchants should reference together

| Card                                                                                                                | Why it matters next to Branded Paid Clicks Cannibalising Organic           | What the combination tells you                                                                                  |
| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [ROAS](/nerve-centre/kpi-cards/adroll/roas)                                                                         | The headline efficiency reading this card cautions against trusting alone. | A high ROAS with a high cannibalisation gauge means the ROAS is inflated by inevitable conversions.             |
| [Conversions by Campaign](/nerve-centre/kpi-cards/adroll/conversions-by-campaign)                                   | Shows where the loyal-cohort conversions concentrate.                      | Helps target frequency caps and recent-purchaser exclusions to the right campaigns.                             |
| [Conversion Rate by Campaign](/nerve-centre/kpi-cards/adroll/conversion-rate-by-campaign)                           | High conversion rates flag the loyal cohort.                               | An unusually high conversion rate on a retargeting line is a cannibalisation tell, not always a success.        |
| [Total Revenue](/nerve-centre/kpi-cards/adroll/total-revenue)                                                       | AdRoll-attributed revenue.                                                 | The slice attributable to cannibalised clicks is revenue AdRoll claims but did not create.                      |
| [Total Spend](/nerve-centre/kpi-cards/adroll/total-spend)                                                           | Sizes the reclaim opportunity.                                             | The cannibalised percentage applied to branded retargeting spend estimates the recoverable margin.              |
| [Retargeting ROAS Dropped Below Threshold](/nerve-centre/kpi-cards/adroll/retargeting-roas-dropped-below-threshold) | The efficiency-decay context.                                              | A falling retargeting ROAS alongside a rising gauge means you are paying more to re-buy the same loyal returns. |
| [AdRoll Pixel Tracking Broken](/nerve-centre/kpi-cards/adroll/adroll-pixel-tracking-broken)                         | The identity-attrition context.                                            | A rising gauge alongside pixel decay means retargeting is concentrating on the few stable loyal cookies.        |

## Reconciling against AdRoll

**Where to look in AdRoll's own dashboard:**

> Sign in at app.adroll.com, then open Reporting and the Campaign or Audience performance views to read branded retargeting clicks and conversions, and check the attribution window selector (default 30-day click / 1-day view) under the reporting settings. Sit that alongside your analytics direct and organic channel reports (for example Google Analytics, Acquisition, Traffic acquisition) and your commerce platform's repeat-customer view.

AdRoll cannot show this card on its own. AdRoll sees the clicks and the conversions its Pixel served; it has no view of how those same shoppers behave in your direct and organic channels, which is the other half of the cannibalisation question. That cross-platform join, AdRoll retargeting against commerce repeat-customer and analytics direct-intent signal, is what Vortex IQ assembles. To sanity-check the gauge manually, compare AdRoll's branded retargeting conversion volume in the dashboard against your analytics direct and branded-organic conversion volume for the same period; a large overlap of the same customers is the cannibalisation this card estimates.

**Why our number is an estimate, not an exact figure:**

| Reason                         | Direction         | Why                                                                                                                                                                     |
| ------------------------------ | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Incrementality is inferred** | Either direction  | True cannibalisation can only be proven with a holdout; this gauge is a modelled estimate from observable direct and organic return signal, so treat it as directional. |
| **View-through attribution**   | Pushes ours up    | AdRoll's 1-day view window credits impressions on loyal users who would have returned regardless, inflating the apparent overlap.                                       |
| **Attribution overlap**        | Ours conservative | Where AdRoll and organic both claim the same conversion, the cross-platform join apportions rather than double-counts, which can read lower than a naive overlap.       |
| **ATT identity attrition**     | Pushes ours up    | A shrinking identifiable Pixel pool concentrates retargeting on loyal users, raising the estimate for reasons of measurement as much as behaviour.                      |
| **Brand strength**             | Varies by store   | Stores with strong direct and organic demand will legitimately show higher cannibalisation than low-awareness brands.                                                   |

**Cross-connector reconciliation:**

This card is inherently cross-platform:

| Card                                                                                                                                                                                                    | Expected relationship                                                                                                                                  | What causes legitimate divergence                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| [`google_analytics.ga_direct_sessions`](/nerve-centre/kpi-cards/google-analytics/direct-sessions) / [`google_analytics.ga_organic_sessions`](/nerve-centre/kpi-cards/google-analytics/organic-sessions) | Strong direct and organic return signal is the basis for the cannibalisation estimate; the more of it, the higher the likely overlap with retargeting. | Analytics attribution and AdRoll attribution use different models, so the overlap is estimated rather than summed.                       |
| [`shopify.repeat_customer_rate`](/nerve-centre/kpi-cards/shopify/repeat-customer-rate) / [`bigcommerce.repeat_customer_rate`](/nerve-centre/kpi-cards/bigcommerce/repeat-customer-rate)                 | A high repeat-customer rate raises the prior that retargeting is reaching buyers who would return anyway.                                              | A high repeat rate driven by subscription or replenishment behaviour cannibalises differently from one driven by discretionary reorders. |

## Known limitations / merchant FAQs

**Does a high reading mean I should stop retargeting?**
No. It means part of your retargeting budget is being spent on customers who would have returned anyway, which is a right-sizing signal, not a kill signal. The action is to cap frequency on the loyal cohort, exclude very recent purchasers from the AdRoll audience, and redirect that budget to genuinely incremental cart abandoners and first-time shoppers. Retargeting still earns its keep on the incremental pool.

**Is this an exact measurement of cannibalisation?**
No, it is a modelled estimate. The only way to prove cannibalisation precisely is an incrementality holdout: suppress retargeting for a matched group and compare their return rate to the targeted group. This gauge is the always-on directional read that tells you when a holdout test is worth running. Treat it as a flag, then validate the suspect cohort with a holdout, which AdRoll supports by excluding a segment from the audience.

**Why does the loyal cohort's high ROAS mislead me?**
Because ROAS credits AdRoll with conversions that were always going to happen. Loyal buyers convert at high rates whether or not they see the ad, so retargeting them produces a glittering ROAS that overstates incremental value. The high conversion rate on a retargeting line is often a cannibalisation tell, not proof the spend is working. AdRoll's 1-day view attribution makes this worse, since a passing impression can claim a return that direct or organic earned.

**My cannibalisation gauge rose after iOS ATT, did my strategy get worse?**
Not necessarily. ATT and cookie deprecation shrink the AdRoll Pixel's identifiable pool, so retargeting increasingly concentrates on the most cookie-stable users, who tend to be your loyal, brand-aware buyers, the exact cohort most likely to return on their own. So part of a post-ATT rise reflects identity attrition concentrating the audience, not a deliberate strategy change. Read it alongside [AdRoll Pixel Tracking Broken](/nerve-centre/kpi-cards/adroll/adroll-pixel-tracking-broken).

**How do I act on this without throwing away genuine retargeting value?**
Segment. Keep retargeting full-strength on the incremental pool (cart abandoners, first-time visitors, lapsed customers, low direct-intent traffic) and apply frequency caps plus recent-purchaser exclusions to the loyal cohort. That preserves the part of retargeting that changes outcomes and trims the part that re-buys inevitable returns. Then validate the trimmed cohort with a holdout to confirm you did not cut incremental value.

**Does my retargeting pool size change how I should read this?**
Yes. When the retargeting pool shrinks (frequency caps hit, audience exhausts, cookies expire), AdRoll keeps serving the names it can still reach, which skew loyal and identifiable. So a rising gauge can coincide with pool exhaustion rather than a deliberate over-investment in loyalists. Read it alongside [Wasted-Spend Burst (retargeting pool exhaustion)](/nerve-centre/kpi-cards/adroll/wasted-spend-burst-retargeting-pool-exhaustion) to tell the two apart.

**Does brand strength change how I should read this?**
Yes. A brand with strong direct and organic demand will legitimately show higher cannibalisation than a low-awareness brand, because more of its returners arrive free. A high reading for a strong brand is expected and actionable; the same reading for a low-awareness brand is more surprising and worth validating, because the overlap may be over-estimated.

***

### Tracked live in Vortex IQ Nerve Centre

*Branded Paid Clicks Cannibalising Organic* is one of hundreds of KPI pulses Vortex IQ tracks across AdRoll 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.


# AdRoll KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/index

Every AdRoll KPI pulse Vortex IQ Nerve Centre tracks: 65 metrics covering revenue, orders, customers, refunds, and more.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adroll) · [Audit Profile](/nerve-centre/kpi-cards/adroll/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adroll/sentiment)**

Vortex IQ Nerve Centre tracks **65** KPI pulses for AdRoll stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves.

The AdRoll connector brings the Vortex IQ **AI OS** to merchants using AdRoll's retargeting and prospecting platform - strong on cross-network display and CRM-segment retargeting. The **Nerve Centre** tracks 65 KPI pulses including the standard ad hero cards (*ROAS*, *Wasted Spend*, *Zero-Conversion Spend*, *Spend vs Budget*) plus campaign / device / geography / dayparting cuts. **Vortex Mind** investigates when retargeting ROAS drops; **Ask Viq™** lets you ask in plain English with citations back to the source card.

| Card                                                                                        | Metrics type       | Category                 | Chart           |
| ------------------------------------------------------------------------------------------- | ------------------ | ------------------------ | --------------- |
| [ROAS](/nerve-centre/kpi-cards/adroll/roas)                                                 | Key Metrics        | Executive Overview       | gauge           |
| [Spend vs Budget](/nerve-centre/kpi-cards/adroll/spend-vs-budget)                           | Key Metrics        | Budget Monitoring        | progress        |
| [Total Revenue](/nerve-centre/kpi-cards/adroll/total-revenue)                               | Key Metrics        | Executive Overview       | kpi             |
| [Total Spend](/nerve-centre/kpi-cards/adroll/total-spend)                                   | Key Metrics        | Executive Overview       | kpi             |
| [Wasted Spend](/nerve-centre/kpi-cards/adroll/wasted-spend)                                 | Key Metrics        | Keyword Intelligence     | kpi             |
| [Zero-Conversion Spend](/nerve-centre/kpi-cards/adroll/zero-conversion-spend)               | Key Metrics        | Alerts & Anomalies       | kpi             |
| [All Conversions](/nerve-centre/kpi-cards/adroll/all-conversions)                           | Supporting Metrics | Funnel & Conversion      | kpi             |
| [Budget Utilisation](/nerve-centre/kpi-cards/adroll/budget-utilisation)                     | Supporting Metrics | Budget Monitoring        | gauge           |
| [Campaign Comparison](/nerve-centre/kpi-cards/adroll/campaign-comparison)                   | Supporting Metrics | Campaign Performance     | table           |
| [Clicks vs Conversions](/nerve-centre/kpi-cards/adroll/clicks-vs-conversions)               | Supporting Metrics | Executive Overview       | dual\_axis      |
| [Conversion Actions Breakdown](/nerve-centre/kpi-cards/adroll/conversion-actions-breakdown) | Supporting Metrics | Funnel & Conversion      | donut           |
| [Conversion Drop Alert](/nerve-centre/kpi-cards/adroll/conversion-drop-alert)               | Supporting Metrics | Alerts & Anomalies       | kpi             |
| [Conversion Funnel](/nerve-centre/kpi-cards/adroll/conversion-funnel)                       | Supporting Metrics | Funnel & Conversion      | funnel          |
| [Conversion Lag](/nerve-centre/kpi-cards/adroll/conversion-lag)                             | Supporting Metrics | Funnel & Conversion      | bar             |
| [Conversion Rate by Campaign](/nerve-centre/kpi-cards/adroll/conversion-rate-by-campaign)   | Supporting Metrics | Campaign Performance     | bar\_horizontal |
| [Conversion Rate by Device](/nerve-centre/kpi-cards/adroll/conversion-rate-by-device)       | Supporting Metrics | Device Performance       | bar             |
| [Conversion Rate Trend](/nerve-centre/kpi-cards/adroll/conversion-rate-trend)               | Supporting Metrics | Funnel & Conversion      | sparkline       |
| [Conversions by Campaign](/nerve-centre/kpi-cards/adroll/conversions-by-campaign)           | Supporting Metrics | Campaign Performance     | bar\_horizontal |
| [Conversions by Country](/nerve-centre/kpi-cards/adroll/conversions-by-country)             | Supporting Metrics | Geography Performance    | geo\_map        |
| [Conversions by Day of Week](/nerve-centre/kpi-cards/adroll/conversions-by-day-of-week)     | Supporting Metrics | Day & Time Performance   | bar             |
| [Conversions by Device](/nerve-centre/kpi-cards/adroll/conversions-by-device)               | Supporting Metrics | Device Performance       | donut           |
| [Conversions by Hour](/nerve-centre/kpi-cards/adroll/conversions-by-hour)                   | Supporting Metrics | Day & Time Performance   | heatmap         |
| [Conversions Trend](/nerve-centre/kpi-cards/adroll/conversions-trend)                       | Supporting Metrics | Executive Overview       | sparkline       |
| [CPA by Keyword](/nerve-centre/kpi-cards/adroll/cpa-by-keyword)                             | Supporting Metrics | Keyword Intelligence     | table           |
| [CPA by Region](/nerve-centre/kpi-cards/adroll/cpa-by-region)                               | Supporting Metrics | Geography Performance    | bar\_horizontal |
| [CPA Trend](/nerve-centre/kpi-cards/adroll/cpa-trend)                                       | Supporting Metrics | Executive Overview       | sparkline       |
| [CPC Anomaly](/nerve-centre/kpi-cards/adroll/cpc-anomaly)                                   | Supporting Metrics | Alerts & Anomalies       | kpi             |
| [CPC by Campaign](/nerve-centre/kpi-cards/adroll/cpc-by-campaign)                           | Supporting Metrics | Campaign Performance     | bar\_horizontal |
| [CPC by Device](/nerve-centre/kpi-cards/adroll/cpc-by-device)                               | Supporting Metrics | Device Performance       | bar             |
| [CPC by Hour](/nerve-centre/kpi-cards/adroll/cpc-by-hour)                                   | Supporting Metrics | Day & Time Performance   | line            |
| [CPC Spike Detection](/nerve-centre/kpi-cards/adroll/cpc-spike-detection)                   | Supporting Metrics | Budget Monitoring        | kpi             |
| [CPC Trend](/nerve-centre/kpi-cards/adroll/cpc-trend)                                       | Supporting Metrics | Executive Overview       | sparkline       |
| [CTR by Campaign](/nerve-centre/kpi-cards/adroll/ctr-by-campaign)                           | Supporting Metrics | Campaign Performance     | bar\_horizontal |
| [CTR by Device](/nerve-centre/kpi-cards/adroll/ctr-by-device)                               | Supporting Metrics | Device Performance       | bar             |
| [CTR by Keyword](/nerve-centre/kpi-cards/adroll/ctr-by-keyword)                             | Supporting Metrics | Keyword Intelligence     | table           |
| [CTR by Region](/nerve-centre/kpi-cards/adroll/ctr-by-region)                               | Supporting Metrics | Geography Performance    | bar\_horizontal |
| [CTR Decline Alert](/nerve-centre/kpi-cards/adroll/ctr-decline-alert)                       | Supporting Metrics | Alerts & Anomalies       | kpi             |
| [CTR Trend](/nerve-centre/kpi-cards/adroll/ctr-trend)                                       | Supporting Metrics | Executive Overview       | sparkline       |
| [Impression Share](/nerve-centre/kpi-cards/adroll/impression-share)                         | Supporting Metrics | Alerts & Anomalies       | gauge           |
| [Impressions Trend](/nerve-centre/kpi-cards/adroll/impressions-trend)                       | Supporting Metrics | Executive Overview       | sparkline       |
| [Landing Page Conv. Rate](/nerve-centre/kpi-cards/adroll/landing-page-conv-rate)            | Supporting Metrics | Landing Page Performance | table           |
| [Landing Page CPC](/nerve-centre/kpi-cards/adroll/landing-page-cpc)                         | Supporting Metrics | Landing Page Performance | table           |
| [Landing Page Performance](/nerve-centre/kpi-cards/adroll/landing-page-performance)         | Supporting Metrics | Landing Page Performance | table           |
| [Landing Page Revenue](/nerve-centre/kpi-cards/adroll/landing-page-revenue)                 | Supporting Metrics | Landing Page Performance | table           |
| [Overspending Campaigns](/nerve-centre/kpi-cards/adroll/overspending-campaigns)             | Supporting Metrics | Budget Monitoring        | table           |
| [Quality Score Distribution](/nerve-centre/kpi-cards/adroll/quality-score-distribution)     | Supporting Metrics | Keyword Intelligence     | bar             |
| [Revenue by Campaign](/nerve-centre/kpi-cards/adroll/revenue-by-campaign)                   | Supporting Metrics | Campaign Performance     | bar\_horizontal |
| [ROAS by Campaign](/nerve-centre/kpi-cards/adroll/roas-by-campaign)                         | Supporting Metrics | Campaign Performance     | bar\_horizontal |
| [ROAS by Day of Week](/nerve-centre/kpi-cards/adroll/roas-by-day-of-week)                   | Supporting Metrics | Day & Time Performance   | bar             |
| [ROAS by Device](/nerve-centre/kpi-cards/adroll/roas-by-device)                             | Supporting Metrics | Device Performance       | bar             |
| [ROAS by Region](/nerve-centre/kpi-cards/adroll/roas-by-region)                             | Supporting Metrics | Geography Performance    | bar\_horizontal |
| [ROAS Trend](/nerve-centre/kpi-cards/adroll/roas-trend)                                     | Supporting Metrics | Executive Overview       | sparkline       |
| [Search Terms Report](/nerve-centre/kpi-cards/adroll/search-terms-report)                   | Supporting Metrics | Keyword Intelligence     | table           |
| [Spend Anomaly](/nerve-centre/kpi-cards/adroll/spend-anomaly)                               | Supporting Metrics | Alerts & Anomalies       | kpi             |
| [Spend by Campaign](/nerve-centre/kpi-cards/adroll/spend-by-campaign)                       | Supporting Metrics | Budget Monitoring        | bar\_horizontal |
| [Spend by Country](/nerve-centre/kpi-cards/adroll/spend-by-country)                         | Supporting Metrics | Geography Performance    | geo\_map        |
| [Spend by Device](/nerve-centre/kpi-cards/adroll/spend-by-device)                           | Supporting Metrics | Device Performance       | donut           |
| [Spend by Hour](/nerve-centre/kpi-cards/adroll/spend-by-hour)                               | Supporting Metrics | Day & Time Performance   | bar             |
| [Spend Over Time](/nerve-centre/kpi-cards/adroll/spend-over-time)                           | Supporting Metrics | Budget Monitoring        | area            |
| [Top Cities by Conversions](/nerve-centre/kpi-cards/adroll/top-cities-by-conversions)       | Supporting Metrics | Geography Performance    | table           |
| [Top Keywords by Conversions](/nerve-centre/kpi-cards/adroll/top-keywords-by-conversions)   | Supporting Metrics | Keyword Intelligence     | table           |
| [Top Keywords by Spend](/nerve-centre/kpi-cards/adroll/top-keywords-by-spend)               | Supporting Metrics | Keyword Intelligence     | table           |
| [Top Performing Campaigns](/nerve-centre/kpi-cards/adroll/top-performing-campaigns)         | Supporting Metrics | Campaign Performance     | table           |
| [Underspending Campaigns](/nerve-centre/kpi-cards/adroll/underspending-campaigns)           | Supporting Metrics | Budget Monitoring        | table           |
| [Worst Performing Campaigns](/nerve-centre/kpi-cards/adroll/worst-performing-campaigns)     | Supporting Metrics | Campaign Performance     | table           |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector. Replace this block when authored.*


# Landing Pages with Poor Web Vitals, AdRoll
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/landing-pages-with-poor-web-vitals

Landing Pages with Poor Web Vitals for AdRoll stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Cross-Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> A cross-platform table that joins the product and landing pages your AdRoll ads send shoppers to against your web-vitals measurement, and lists every landing page that is both slow (poor Largest Contentful Paint and related vitals) and converting below your account average. AdRoll is retargeting-first: most of your spend pays to bring a warm visitor or cart abandoner back to a specific page. If that page loads slowly, the retargeting cycle pays to deliver the click and then loses the shopper to a sluggish load before they can buy. This card finds the leak at the point it actually happens, the destination page, rather than blaming the campaign or the audience. It is where ad performance and site performance meet, and it only exists because Vortex IQ sees both the AdRoll serving layer and your web-vitals data.

|                                      |                                                                                                                                                                                                                                                                                                                                                                                            |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **What it counts**                   | The count and list of distinct landing pages targeted by AdRoll ads (Dynamic Ads and static display, native, social and CTV creative) that exhibit poor web vitals (slow LCP and related Core Web Vitals) and a conversion rate materially below the account average. The value is the number of offending pages; the table details each page, its vitals reading, and its conversion gap. |
| **Cost basis**                       | **CPC-dominant on the AdRoll side.** The wasted cost is the CPC paid to deliver a click to a page that then loses the shopper to slow load. AdRoll mixes CPM and CPC buying, so on CPM placements the same logic applies to the effective cost per click the placement produced.                                                                                                           |
| **Currency**                         | None for the headline count. The wasted-spend implication is in advertiser-account currency when the poor pages are weighted by their click cost.                                                                                                                                                                                                                                          |
| **Conversion attribution**           | 30-day click / 1-day view default on AdRoll, tracked via the AdRoll Pixel. The conversion-rate comparison uses AdRoll-attributed conversions per landing page against the account average.                                                                                                                                                                                                 |
| **Attribution window**               | 30-day click / 1-day view default (configurable in the AdRoll dashboard).                                                                                                                                                                                                                                                                                                                  |
| **Bot / invalid traffic**            | Excluded from the conversion-rate side where filtering identifies it; vitals are measured on real sessions.                                                                                                                                                                                                                                                                                |
| **iOS 14.5+ ATT impact on the card** | **Low to moderate.** Vitals are device-measured and unaffected by ATT; the conversion-rate side leans on AdRoll Pixel attribution, which the 1-day view window and ATT can understate, so weigh the conversion gap with that in mind on iOS-heavy pages.                                                                                                                                   |
| **Catalogue-feed dependency**        | Indirect. The product feed decides which PDPs Dynamic Ads send traffic to; this card judges how well those PDPs perform once the shopper arrives.                                                                                                                                                                                                                                          |
| **Time window**                      | `30D` (rolling 30 days). A monthly read smooths daily vitals variance and gives a stable conversion-rate comparison against AdRoll's default 30-day click window.                                                                                                                                                                                                                          |
| **Alert trigger**                    | `any landing with LCP >4s AND CR <0.5x account-avg`. An illustrative rule; a page is flagged when its load is slow and its conversion rate is well under half the account average, the combination that signals the page itself is the leak.                                                                                                                                               |
| **Roles**                            | owner, marketing, engineering                                                                                                                                                                                                                                                                                                                                                              |

## Calculation

Calculated automatically by joining your AdRoll landing-page data with your connected web-vitals measurement (CrUX field data and PageSpeed Insights). See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

Northfell Outfitters, a UK outdoor-gear DTC retailer on BigCommerce, runs AdRoll retargeting and prospecting that sends shoppers to product-detail pages via Dynamic Ads. A recent PDP template change added a heavy hero-video block and a third-party size-guide widget that slowed load on several pages. The join lists AdRoll landing pages by vitals and conversion rate against the account average. Window is the rolling 30 days to 19 Jun 26. Account average conversion rate on AdRoll-driven PDP sessions is 3.0%.

| Landing page               | LCP  | CLS  | AdRoll clicks | Conv. rate | vs account avg | State |
| -------------------------- | ---- | ---- | ------------- | ---------- | -------------- | ----- |
| /tents/4-season-expedition | 5.9s | 0.22 | 4,100         | 1.1%       | 0.37x          | FLAG  |
| /packs/65l-trekking        | 5.0s | 0.19 | 2,950         | 1.3%       | 0.43x          | FLAG  |
| /boots/alpine-gtx          | 2.0s | 0.04 | 2,700         | 3.2%       | 1.07x          | OK    |
| /jackets/hardshell-pro     | 4.5s | 0.17 | 1,850         | 1.4%       | 0.47x          | FLAG  |

What the pattern tells you:

1. **Three PDPs are both slow and converting at well under half the account average.** These are the leaks. AdRoll delivered warm, high-intent retargeting clicks (cart abandoners and recent visitors) to them, and the pages lost those shoppers before they could buy. The campaign is doing its job; the destination is failing.
2. **The healthy boot page proves it is the page, not the audience.** The /boots/alpine-gtx page loads in 2.0s and converts slightly above account average on the same kind of retargeting traffic. Same audience, same platform, good page, normal conversion. That contrast localises the fault to the slow pages, not to the retargeting pool.
3. **The flagged pages share the new heavy template.** All three slow pages use the PDP template with the hero-video block and the size-guide widget; the fast boot page predates it. That common factor points the engineering fix at the template, not at individual products.
4. **The wasted cost is concentrated on the highest-traffic slow page.** The 4-season tent page took 4,100 retargeting clicks at a 1.1% conversion rate; a page converting at account average would have produced far more sales from the same spend. Prioritise the fix by clicks-times-conversion-gap, not by which page is slowest in isolation.
5. **The fix lives in engineering, not in the ad account.** Defer or lazy-load the hero video, compress and correctly size hero images, load the size-guide widget on interaction rather than on page load, and reserve layout space to cut the CLS shift. As LCP improves toward the good band, conversion rate on retargeting traffic should climb back toward the account average.
6. **Re-measure after the fix before touching budget.** Do not pull spend off these products; fix the page and let the recovered conversion rate restore the ROAS. Pausing the campaign would forfeit warm demand that the page fix recaptures, and on AdRoll a paused retargeting line lets the audience pool cool while abandoners drift out of the window.

Quick sanity tests:

* Page slow + conversion well below average = genuine destination leak, fix the page.
* Page slow + conversion near average = the speed is tolerable for that product; deprioritise.
* Page fast + conversion below average = not a vitals problem; look at price, stock, or offer.
* Several flagged pages share a template = template-level fix, highest leverage.
* Conversion recovers after a vitals fix = confirmed the page was the cause.

## Sibling cards merchants should reference together

| Card                                                                                                                              | Why it matters next to Landing Pages with Poor Web Vitals | What the combination tells you                                                                                          |
| --------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| [Landing Page Performance](/nerve-centre/kpi-cards/adroll/landing-page-performance)                                               | The per-landing-page performance breakdown.               | This card adds the web-vitals dimension that explains why a landing page underperforms.                                 |
| [Retargeting ROAS Dropped Below Threshold](/nerve-centre/kpi-cards/adroll/retargeting-roas-dropped-below-threshold)               | The retargeting efficiency alarm.                         | When ROAS falls and the flagged pages are retargeting destinations, slow load is a prime suspect before you touch bids. |
| [Wasted-Spend Burst (retargeting pool exhaustion)](/nerve-centre/kpi-cards/adroll/wasted-spend-burst-retargeting-pool-exhaustion) | The other big leak on a retargeting-first account.        | Separates two failure modes: a shrinking pool wastes impressions, a slow page wastes the clicks you do win.             |
| [Active Dynamic Ads on Out-of-Stock SKUs](/nerve-centre/kpi-cards/adroll/active-dynamic-ads-on-out-of-stock-skus)                 | Feed-driven destination quality.                          | A page can be fast yet still convert poorly because the product is out of stock; rule that out before blaming vitals.   |
| [Conversions Trend](/nerve-centre/kpi-cards/adroll/conversions-trend)                                                             | Account-level conversion direction.                       | A dip aligned to a PDP template change points at a vitals regression as the cause.                                      |
| [ROAS](/nerve-centre/kpi-cards/adroll/roas)                                                                                       | The efficiency headline.                                  | Slow landing pages silently depress ROAS; fixing them is a site-side ROAS lever that needs no bid change.               |

## Reconciling against AdRoll

**Where to look in AdRoll's own dashboard:**

> AdRoll dashboard at [app.adroll.com](https://app.adroll.com), under Reporting, for clicks and conversions broken down by ad or product (the landing-page destination), and a web-vitals source (your real-user monitoring, CrUX field data, or Google PageSpeed Insights) for the LCP and CLS readings on those same URLs. AdRoll groups performance by campaign and ad rather than by URL, so you reconstruct the per-landing-page view from the destination URLs on the ads.

AdRoll cannot produce this card on its own. AdRoll sees the clicks it delivered and the conversions the AdRoll Pixel attributed per ad, but it has no idea how fast those landing pages load, that lives in your web-vitals measurement. The cross-platform join of AdRoll landing-page performance against web-vitals data is what Vortex IQ assembles. To reconcile manually, export AdRoll's per-ad clicks and conversion rate and map each ad to its destination URL, pull the LCP and CLS for the same URLs from your vitals source, and the pages that are both slow and below your account-average conversion rate are the ones this card flags.

**Why our number may legitimately differ from a manual check:**

| Reason                                 | Direction                  | Why                                                                                                                                                                          |
| -------------------------------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Field vs lab vitals**                | Either direction           | Real-user (field/CrUX) vitals and lab-tool (PageSpeed) readings can diverge; a page may pass in a lab test yet read poorly for real shoppers on slower devices and networks. |
| **Device and network mix**             | Ours reflects real traffic | Vitals vary by device and connection; a page that is fine on desktop can be poor on the mobile traffic AdRoll display and social placements actually send.                   |
| **Attribution on the conversion side** | Conversion gap can shift   | The conversion-rate comparison uses AdRoll-Pixel-attributed conversions on the default 30-day click / 1-day view window, which ATT and the short view window can understate. |
| **URL normalisation**                  | Ours may group variants    | Query-string, UTM, and variant URLs for the same product are grouped to the canonical landing page; a manual check that keeps them separate will count differently.          |

**Cross-connector reconciliation:**

This card is inherently cross-platform, joining ad landing-page data to web-vitals measurement:

| Card                                                                                                                                                        | Expected relationship                                                                                                                         | What causes legitimate divergence                                                                                                      |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| [`website.lcp`](/nerve-centre/kpi-cards/website/lcp) / [`website.cls`](/nerve-centre/kpi-cards/website/cls)                                                 | The web-vitals signal is the speed side of the join; the same poor LCP and CLS that hurt SEO and direct traffic also leak AdRoll-paid clicks. | Site-wide vitals can look acceptable while specific PDPs that AdRoll targets are poor, which is why a landing-page-level join matters. |
| [`shopify.total_revenue`](/nerve-centre/kpi-cards/shopify/total-revenue) / [`bigcommerce.total_revenue`](/nerve-centre/kpi-cards/bigcommerce/total-revenue) | Sizes the recoverable revenue from fixing the flagged pages.                                                                                  | The revenue upside depends on each page's traffic volume and product margin, not on how slow it is alone.                              |

## Known limitations / merchant FAQs

**Why is a slow landing page AdRoll's problem and not just a site problem?**
Because AdRoll's entire model is retargeting: it pays to bring a warm visitor or cart abandoner back to a specific page. If that page loads slowly, you have spent the CPC to deliver the click and then lost the shopper to a sluggish load before they could buy. The retargeting cycle's whole purpose is defeated at the final step. The cost is real ad spend, which is why this sits in the AdRoll manifest, not only in a site-health report.

**My site passes Core Web Vitals overall, so why are pages flagged here?**
Site-wide averages hide page-level problems. The specific product-detail pages AdRoll Dynamic Ads target, often newer templates, image-heavy hero blocks, or pages loaded down with third-party widgets, can be much slower than your homepage or category pages that dominate the site-wide average. This card looks page by page at exactly the URLs AdRoll sends paid traffic to, which is where the money is leaking.

**Should I pause campaigns to the slow pages?**
No, fix the pages. Pausing forfeits warm, high-intent demand that a page fix would convert, and on a retargeting-first account a paused line lets the audience pool cool while abandoners drift out of the attribution window. The right order is to fix the vitals (defer heavy media, compress and size images, load third-party widgets on interaction, reserve layout space to cut layout shift), re-measure, and let the recovered conversion rate restore ROAS. Reserve any budget reduction for cases where an engineering fix is genuinely impossible in the near term.

**How do I prioritise which page to fix first?**
By impact, not by raw slowness. Rank the flagged pages by clicks multiplied by the conversion gap, so the highest-traffic, worst-converting page comes first. A page that is the slowest on the list but takes little AdRoll traffic matters less than a slightly-slower page absorbing thousands of paid retargeting clicks. Fix for recovered conversions, not for the worst single LCP number.

**Could ATT or the 1-day view window distort this card?**
Partly, on the conversion side only. Web vitals are measured on the device and are unaffected by ATT. The conversion-rate comparison uses AdRoll-Pixel-attributed conversions on the default 30-day click / 1-day view window, which ATT and the short view window can understate on iOS-heavy pages, so a page might look slightly worse-converting than it truly is. The vitals reading itself is reliable; weigh the conversion gap with the traffic's iOS share in mind.

**Why combine slow load and low conversion instead of flagging on speed alone?**
Because speed alone over-flags. Some slow pages still convert acceptably for their product, and fixing them yields little. The card requires both poor vitals and a conversion rate well below the account average, which isolates the pages where the slowness is actually costing conversions. That keeps the list short and every entry worth an engineer's time.

**How is this different from the Dynamic Ads out-of-stock card?**
That card catches a feed problem: ads still serving for SKUs the catalogue marks out of stock, where even a fast page cannot convert because there is nothing to buy. This card catches a speed problem: the product is available and the ad is valid, but the destination page loads too slowly to convert the click. Run them together so you do not spend an engineer's afternoon optimising the load time of a page whose product is actually out of stock.

***

### Tracked live in Vortex IQ Nerve Centre

*Landing Pages with Poor Web Vitals* is one of hundreds of KPI pulses Vortex IQ tracks across AdRoll 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.


# AdRoll sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag AdRoll KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adroll) · [Audit Profile](/nerve-centre/kpi-cards/adroll/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adroll/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each AdRoll KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **0** of the 72 AdRoll cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                           | Direction | Good | Bad | Unit |
| ------------------------------ | --------- | ---- | --- | ---- |
| (no sentiment-tuned cards yet) |           |      |     |      |


# Spend on Campaigns with Active Feed Rejections, AdRoll
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adroll/spend-on-campaigns-with-active-feed-rejections

Spend on Campaigns with Active Feed Rejections for AdRoll stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Cross-Platform](/nerve-centre/connectors#connectors-by-type)

## At a glance

> A cross-platform alert that joins AdRoll Dynamic Ads spend against the live rejection status of the product catalogue each campaign is driven by, and flags any budget flowing into a dynamic campaign whose feed has active rejections. This is the single highest-leverage card in the AdRoll manifest because Dynamic Ads are catalogue-driven by design: the creative is assembled from product records in the synced feed, so when items are rejected, no product creative renders for them, and any spend the campaign keeps pacing is wasted on whatever fallback creative remains. Feed rejections are silent, they do not pause the campaign, they just hollow it out while it keeps retargeting your warmest audiences with broken ads. This card turns a buried catalogue warning into a money figure: here is exactly how much spend is exposed to a feed that is partly broken right now.

|                                      |                                                                                                                                                                                                                                                                                                                                     |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                   | The total dynamic-campaign spend over the window flowing into campaigns whose linked catalogue currently has active feed rejections (rejected products, suppressed SKUs, or a wholesale catalogue sync failure). The alert is the breach; the displayed table lists each affected campaign, its spend, and the rejecting catalogue. |
| **Cost basis**                       | **CPC / CPM dominant.** The exposed spend is real billed cost on a dynamic campaign whose product creative is degraded by the rejection.                                                                                                                                                                                            |
| **Currency**                         | Advertiser-account currency for the exposed-spend figure.                                                                                                                                                                                                                                                                           |
| **Conversion attribution**           | 30-day click + 1-day view default (AdRoll Pixel). Feed-rejected campaigns typically show depressed conversions because the intended product creative is not rendering.                                                                                                                                                              |
| **Attribution window**               | 30-day click + 1-day view default, configurable in the AdRoll dashboard.                                                                                                                                                                                                                                                            |
| **Bot / invalid traffic**            | Not the relevant axis; the waste is structural to the feed rejection, not to traffic quality.                                                                                                                                                                                                                                       |
| **iOS 14.5+ ATT impact on the card** | **Low.** The card keys off feed-rejection status and spend, both observed directly, so ATT and pixel signal loss do not distort it.                                                                                                                                                                                                 |
| **Catalogue-feed dependency**        | **This card is entirely about feed health.** It is the most direct expression of AdRoll's catalogue dependency in the whole manifest: spend exposed to a broken Dynamic Ads feed, named and costed.                                                                                                                                 |
| **Time window**                      | `30D` (rolling 30 days) for the spend total, evaluated against the current feed-rejection status.                                                                                                                                                                                                                                   |
| **Alert trigger**                    | `any spend on a dynamic campaign whose linked catalogue has active feed rejections`. An illustrative rule; the breach fires whenever a dynamic campaign with active linked-feed rejections continues to accrue spend.                                                                                                               |
| **Roles**                            | owner, marketing, operations                                                                                                                                                                                                                                                                                                        |

## Calculation

Calculated automatically by joining your AdRoll dynamic-campaign spend with your connected product-catalogue feed status. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

A UK outdoor-gear retailer on Shopify runs four AdRoll Dynamic Ads campaigns off a single product catalogue synced from the store. On 04 Jun 26 a bulk catalogue re-tag added unsupported HTML into the product titles, and the AdRoll catalogue sync rejected a large batch of products. Account currency GBP. Window is the rolling 30 days.

| Campaign                             | Linked catalogue  | Rejected products | Spend in window (£) | Conv. vs prior | State  |
| ------------------------------------ | ----------------- | ----------------- | ------------------- | -------------- | ------ |
| Dynamic retargeting, site visitors   | Shopify catalogue | 2,210 of 3,600    | 7,400               | -39%           | BREACH |
| Dynamic retargeting, cart abandoners | Shopify catalogue | 2,210 of 3,600    | 5,800               | -44%           | BREACH |
| Static prospecting, brand audiences  | (no catalogue)    | 0                 | 1,900               | flat           | OK     |
| Dynamic prospecting, lookalike       | Shopify catalogue | 2,210 of 3,600    | 2,300               | -18%           | BREACH |

What the pattern tells you:

1. **Three dynamic campaigns sharing the catalogue breached; the static prospecting campaign did not.** That instantly localises the fault to the catalogue, not to any campaign's bidding or audience. The static campaign serves fixed creative with no feed dependency, so it is unaffected. The shared dependency is the story.
2. **Roughly GBP 15,500 of spend is exposed to a catalogue that is 61% rejected.** That is the number this card exists to surface. Buried in the AdRoll Product Catalogue status page it is just a rejected-count warning; expressed as exposed spend it becomes an urgent, costed problem an owner or marketer can act on.
3. **Conversions fell hardest on the retargeting campaigns.** Cart-abandoner retargeting (most dependent on serving the exact products a visitor browsed) dropped 44%, while dynamic prospecting (broader product mix, less reliant on the precise rejected items) dropped only 18%. The conversion damage tracks the dependency.
4. **The campaigns did not stop, which is the trap.** A feed rejection does not pause an AdRoll campaign. It keeps pacing against the surviving 39% of the catalogue and generic fallback creative, so spend looks normal while effectiveness has collapsed. Only a feed-aware join makes this visible.
5. **The fix is at the catalogue source, not in AdRoll bidding.** Open the AdRoll Product Catalogue to read the rejection reason (here, unsupported HTML in the title field), correct the product data on the Shopify export, and trigger a re-sync. The rejected products re-enter dynamic eligibility within a sync cycle (typically a few hours to 24 hours) and conversions recover.
6. **Until the catalogue is fixed, the exposed spend keeps accruing.** If a same-day fix is not possible, consider reducing budget on the worst-affected retargeting campaigns so you are not pacing full spend against a half-broken catalogue while warm audiences burn down.

Quick sanity tests:

* Multiple dynamic campaigns breach + they share a catalogue = catalogue-level fault, fix the feed.
* One campaign breaches + others on the same catalogue are fine = campaign-specific issue, not the feed.
* Conversion drop scales with rejection share = confirmed feed-driven effectiveness loss.
* Breach clears after a catalogue re-sync = confirmed, no campaign restructure needed.
* High exposed spend + high rejection share + a shrinking retargeting pool = reduce budget until the catalogue is fixed.

## Sibling cards merchants should reference together

| Card                                                                                                                              | Why it matters next to Spend on Campaigns with Active Feed Rejections | What the combination tells you                                                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Active Dynamic Ads on Out-of-Stock SKUs](/nerve-centre/kpi-cards/adroll/active-dynamic-ads-on-out-of-stock-skus)                 | The other catalogue-driven waste card.                                | Rejections stop product creative rendering; out-of-stock serving runs creative that cannot convert. Together they are the full feed-waste bill on Dynamic Ads.              |
| [Wasted-Spend Burst (retargeting pool exhaustion)](/nerve-centre/kpi-cards/adroll/wasted-spend-burst-retargeting-pool-exhaustion) | The acute burst symptom on a retargeting-first account.               | A feed rejection here often coincides with a burst as the campaign hammers a shrinking pool with broken creative; both firing confirms the cause and sizes the acute bleed. |
| [Retargeting ROAS Dropped Below Threshold](/nerve-centre/kpi-cards/adroll/retargeting-roas-dropped-below-threshold)               | The efficiency-side symptom on AdRoll's core spend.                   | A retargeting ROAS drop that scales with rejection share confirms the feed as the cause rather than audience fatigue.                                                       |
| [Wasted Spend](/nerve-centre/kpi-cards/adroll/wasted-spend)                                                                       | The trailing-30-day waste audit.                                      | Sustained catalogue rejections show up here as chronic wasted spend across dynamic campaigns.                                                                               |
| [AdRoll Pixel Tracking Broken](/nerve-centre/kpi-cards/adroll/adroll-pixel-tracking-broken)                                       | The other silent failure mode that suppresses conversions.            | Rules out a pixel fault: if the pixel is healthy but conversions still fell on dynamic campaigns, the catalogue rejection is the more likely cause.                         |
| [ROAS](/nerve-centre/kpi-cards/adroll/roas)                                                                                       | The efficiency headline.                                              | Catalogue rejections silently drag account ROAS; fixing the feed is often the single biggest ROAS lever on an AdRoll account.                                               |
| [Total Spend](/nerve-centre/kpi-cards/adroll/total-spend)                                                                         | The account-level denominator.                                        | Sizes the exposed spend against total to judge how much budget is at risk.                                                                                                  |

## Reconciling against AdRoll

**Where to look in AdRoll's own dashboard:**

> In the AdRoll dashboard at app.adroll.com, open Product Catalogue (under Audiences and Catalogues, depending on your account layout) to read the rejection reasons and rejected-product counts for each catalogue, then open Reporting and group by campaign to read the spend on each Dynamic Ads campaign linked to the affected catalogue.

AdRoll holds both halves of this story but never puts them on the same screen: the Product Catalogue status page shows what is rejected, and Reporting shows what each campaign spent, but AdRoll does not connect "this dynamic campaign is driven by that rejecting catalogue, and here is the spend exposed". That join is exactly what this card does. To reconcile manually, read the rejected-product list and rejection reasons from the catalogue page, identify which dynamic campaigns are linked to that catalogue, then sum their spend in Reporting; the total should match this card's exposed-spend figure within rounding.

**Why our number may legitimately differ from a manual check:**

| Reason                            | Direction                  | Why                                                                                                                                                                                             |
| --------------------------------- | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rejection-status timing**       | Moves with cadence         | The breach reflects the current catalogue-rejection status; AdRoll re-evaluates products on each sync cycle, so a manual check after a re-sync may show fewer rejections.                       |
| **Partial vs full rejection**     | Either direction           | A campaign can depend heavily or lightly on the rejected subset; this card flags any exposure, while the conversion damage scales with dependency.                                              |
| **Time zone and ingest lag**      | Boundary days off          | AdRoll reports spend in the account time zone with a short reporting lag; Vortex IQ uses UTC boundaries, so the latest spend can differ slightly.                                               |
| **Catalogue-to-campaign mapping** | Ours captures shared feeds | Where several dynamic campaigns share one catalogue, the join attributes the rejection exposure to all of them; a manual check can miss a campaign linkage.                                     |
| **Static campaigns excluded**     | Ours is narrower           | The card counts only dynamic, catalogue-driven campaigns; static-creative campaigns have no feed dependency and are correctly left out, so they will not appear even if they share an audience. |

**Cross-connector reconciliation:**

This card is inherently cross-platform, joining ad spend to product-catalogue feed status:

| Card                                                                                                                                                                                                                                                                                     | Expected relationship                                                                                                                                                     | What causes legitimate divergence                                                                                                                                                                                      |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`shopify.product_feed_health`](/nerve-centre/kpi-cards/shopify/product-feed-health) / [`bigcommerce.product_feed_health`](/nerve-centre/kpi-cards/bigcommerce/product-feed-health) / [`adobe_commerce.product_feed_health`](/nerve-centre/kpi-cards/adobe-commerce/product-feed-health) | The commerce-platform feed-health signal is the upstream cause; rejections here originate from product-data problems on the store export that feeds the AdRoll catalogue. | A product can be valid on the storefront yet rejected by AdRoll for platform-specific rules (unsupported title markup, missing image, price or availability mismatch), so the two views are related but not identical. |
| [`shopify.total_revenue`](/nerve-centre/kpi-cards/shopify/total-revenue) / [`bigcommerce.total_revenue`](/nerve-centre/kpi-cards/bigcommerce/total-revenue)                                                                                                                              | Sizes the opportunity cost: a heavily rejected catalogue both wastes ad spend and suppresses the sales those products could have driven through retargeting.              | The revenue impact depends on how important the rejected products are to the assortment and to your retargeting audiences.                                                                                             |

## Known limitations / merchant FAQs

**Why is this called the highest-leverage card on AdRoll?**
Because AdRoll's Dynamic Ads are catalogue-driven at their core, and AdRoll is retargeting-first, so the dynamic spend tends to be the warmest, highest-intent budget on the account. A feed rejection does not just dent one metric, it hollows out the product creative that dynamic retargeting depends on, while the campaign keeps spending against site visitors and cart abandoners. Catching exposed spend the moment a catalogue breaks prevents the most expensive and most common failure mode on the platform. Fixing the catalogue is repeatedly the single biggest ROAS lever on an AdRoll account.

**A feed rejection did not pause my campaign, so why is it a problem?**
That is precisely the problem. A rejection silently removes the affected products from the eligible dynamic pool but leaves the campaign running, pacing budget against the surviving products and generic fallback creative. Spend looks normal while effectiveness has quietly collapsed, and on a retargeting-first account it is your warmest audiences seeing the broken ads. The campaign not stopping is what makes catalogue rejections so easy to miss and so expensive, which is why this card converts the warning into a money figure.

**What causes catalogue rejections most often?**
The usual suspects are unsupported markup or banned promotional text in title and description fields, missing or low-resolution product images, price or availability mismatches between the feed and the landing page, missing required attributes (product ID, image link, landing-page URL), and broken or redirecting product URLs. The AdRoll Product Catalogue status page names the reason per product. A bulk catalogue edit or a re-platform on the storefront is a frequent trigger, as in the worked example.

**Should I pause the campaign or fix the catalogue?**
Fix the catalogue. Pausing a dynamic retargeting campaign throws away the still-working part of the catalogue and lets your warm audiences cool or, worse, exhaust against your competitors. The right sequence is to read the rejection reason on the Product Catalogue page, correct the product data at the store export, trigger a re-sync, and let the rejected products re-enter dynamic eligibility within a sync cycle. Reduce budget on the worst-affected campaign only as an interim measure if a same-day catalogue fix is not possible.

**Does iOS ATT or pixel signal loss affect this card?**
Very little. The card keys off catalogue-rejection status and spend, both observed directly rather than attributed through the AdRoll Pixel, so iOS ATT and browser tracking restrictions do not distort the exposed-spend figure. The conversion-drop context shown alongside it is attribution-sensitive, but the core "spend exposed to a rejecting catalogue" signal is high-confidence.

**My product is fine on my storefront but AdRoll rejected it, how?**
AdRoll applies its own catalogue rules on top of your store data. A product that is perfectly valid in your store can still fail AdRoll's title, image, price-consistency, or availability checks when it is ingested into the catalogue. The store export is the bridge, and the fix is to make the exported product data satisfy AdRoll's rules, for example stripping unsupported markup from the title or supplying a valid image link, even though the storefront listing itself was never broken.

**Does this card cover both retargeting and prospecting dynamic campaigns?**
Yes. Any campaign that assembles creative from the product catalogue is in scope, whether it targets retargeting audiences (site visitors, cart abandoners) or prospecting audiences (lookalike, intent). Because AdRoll is retargeting-first, most of the exposed spend usually lands on retargeting campaigns, but a dynamic prospecting campaign on the same rejecting catalogue will breach too, and it will show in the table with its own spend line.

***

### Tracked live in Vortex IQ Nerve Centre

*Spend on Campaigns with Active Feed Rejections* is one of hundreds of KPI pulses Vortex IQ tracks across AdRoll 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.


# Adyen audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adyen/audit

What the Vortex IQ Adyen health audit checks: Adyen: Authorisation, Risk, Settlement & Payments-to-Revenue

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adyen) · [Audit Profile](/nerve-centre/kpi-cards/adyen/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adyen/sentiment)**

Adyen state matters when it's tied to captured revenue and friction. This audit answers: (1) is the API credential + webhook config healthy, (2) is authorisation holding and what's driving refusals, (3) are chargebacks / fraud / settlement under control, and (4) does payment friction map to lost revenue and support load via the commerce + support siblings.

## What this audit checks

### Authentication & configuration

* API key valid (auth on /v3/merchants) and live/test env matches
* Webhooks configured + reachable (else no event-driven updates)
* Active payment methods cover the merchant's key markets

### Authorisation & checkout health

* Authorisation rate below 92%
* Refusal rate above 8% (and which reasons dominate)
* A payment method authorising below 85% (method-specific breakage)
* 3DS challenge rate above 40% (added friction / abandonment risk)
* Capture rate below 98% (uncaptured authorisations expiring)

### Risk, disputes & settlement

* Chargeback rate above 1% (Visa/Mastercard programme threshold)
* Fraud rate above 0.5%
* Settlement age above 5 days (cash-flow risk)
* Refund rate above 5% of volume

### Cross-platform: payments-to-revenue (the killer area)

* Refused-payment shoppers opening support conversations (sibling intercom) - friction driving support load
* Adyen captured volume vs commerce-sibling order revenue mismatch > 2% (reconciliation gap)
* Refund spike correlated with a commerce returns spike
* Auth-rate drop during a campaign push (paying for traffic that can't pay)

## Data sources

* `GET https://management-live.adyen.com/v3/merchants` - Auth + merchant/store inventory
* `GET https://management-live.adyen.com/v3/merchants/{merchantId}/paymentMethodSettings` - Active payment methods
* `GET https://management-live.adyen.com/v3/merchants/{merchantId}/webhooks` - Webhook configuration / delivery health
* `GET report:settlement_detail` - Volume / auth / refusal / refund / settlement (async report)


# Adyen KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adyen/index

Every Adyen KPI the Vortex IQ Nerve Centre tracks: 26 metrics, each with definition, calculation, why it matters, and how to act.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adyen) · [Audit Profile](/nerve-centre/kpi-cards/adyen/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adyen/sentiment)**

Vortex IQ Nerve Centre tracks **26** KPI pulses for Adyen. Each metric has its own page.

The Adyen connector brings the Vortex IQ **AI OS** to teams running Adyen. The **Nerve Centre** tracks 26 KPI pulses, hero alerts on the most decision-critical, and cross-platform cards that tie Adyen to sibling connectors. **Vortex Mind** investigates regressions; **Ask Viq™** answers in plain English with citations back to the source card.

| Card                                                                                                 | Metrics type       | Category                            | Chart           |
| ---------------------------------------------------------------------------------------------------- | ------------------ | ----------------------------------- | --------------- |
| [Payments Health Score](/nerve-centre/kpi-cards/adyen/payments-health-score)                         | Key Metrics        | Executive Command Centre            | gauge           |
| [Payment Volume (30d)](/nerve-centre/kpi-cards/adyen/payment-volume-30d)                             | Key Metrics        | Executive Command Centre            | kpi             |
| [Authorisation Rate](/nerve-centre/kpi-cards/adyen/authorisation-rate)                               | Key Metrics        | Executive Command Centre            | gauge           |
| [Refusal Rate](/nerve-centre/kpi-cards/adyen/refusal-rate)                                           | Key Metrics        | Executive Command Centre            | kpi             |
| [Chargeback Rate](/nerve-centre/kpi-cards/adyen/chargeback-rate)                                     | Key Metrics        | Executive Command Centre            | kpi             |
| [Settlement Pending](/nerve-centre/kpi-cards/adyen/settlement-pending)                               | Supporting Metrics | Executive Command Centre            | kpi             |
| [Auth Rate by Payment Method](/nerve-centre/kpi-cards/adyen/auth-rate-by-payment-method)             | Supporting Metrics | Payments & Checkout Health          | bar\_horizontal |
| [Refusal Reasons](/nerve-centre/kpi-cards/adyen/refusal-reasons)                                     | Supporting Metrics | Payments & Checkout Health          | bar\_horizontal |
| [Payment Method Mix](/nerve-centre/kpi-cards/adyen/payment-method-mix)                               | Supporting Metrics | Payments & Checkout Health          | donut           |
| [Avg Transaction Value](/nerve-centre/kpi-cards/adyen/avg-transaction-value)                         | Supporting Metrics | Payments & Checkout Health          | kpi             |
| [3DS Challenge Rate](/nerve-centre/kpi-cards/adyen/3ds-challenge-rate)                               | Supporting Metrics | Payments & Checkout Health          | gauge           |
| [Capture Rate](/nerve-centre/kpi-cards/adyen/capture-rate)                                           | Supporting Metrics | Payments & Checkout Health          | gauge           |
| [Refunds (30d)](/nerve-centre/kpi-cards/adyen/refunds-30d)                                           | Supporting Metrics | Payments & Checkout Health          | kpi             |
| [Chargebacks (30d)](/nerve-centre/kpi-cards/adyen/chargebacks-30d)                                   | Supporting Metrics | Risk & Disputes                     | kpi             |
| [Fraud Rate](/nerve-centre/kpi-cards/adyen/fraud-rate)                                               | Supporting Metrics | Risk & Disputes                     | kpi             |
| [Dispute Win Rate](/nerve-centre/kpi-cards/adyen/dispute-win-rate)                                   | Supporting Metrics | Risk & Disputes                     | gauge           |
| [Active Payment Methods](/nerve-centre/kpi-cards/adyen/active-payment-methods)                       | Supporting Metrics | Configuration & Health              | kpi             |
| [Stores / Accounts](/nerve-centre/kpi-cards/adyen/stores-accounts)                                   | Supporting Metrics | Configuration & Health              | kpi             |
| [Webhooks Configured](/nerve-centre/kpi-cards/adyen/webhooks-configured)                             | Supporting Metrics | Configuration & Health              | kpi             |
| [Support Spike on Refused Payments](/nerve-centre/kpi-cards/adyen/support-spike-on-refused-payments) | Key Metrics        | Cross-Platform: Payments to Revenue | kpi             |
| [Captured vs Commerce Revenue](/nerve-centre/kpi-cards/adyen/captured-vs-commerce-revenue)           | Key Metrics        | Cross-Platform: Payments to Revenue | kpi             |
| [Refunds vs Commerce Returns](/nerve-centre/kpi-cards/adyen/refunds-vs-commerce-returns)             | Supporting Metrics | Cross-Platform: Payments to Revenue | kpi             |
| [Auth Rate Drop Alert](/nerve-centre/kpi-cards/adyen/auth-rate-drop-alert)                           | Key Metrics        | Alerts & Anomaly Detection          | kpi             |
| [Refusal Spike Alert](/nerve-centre/kpi-cards/adyen/refusal-spike-alert)                             | Supporting Metrics | Alerts & Anomaly Detection          | kpi             |
| [Chargeback Spike Alert](/nerve-centre/kpi-cards/adyen/chargeback-spike-alert)                       | Supporting Metrics | Alerts & Anomaly Detection          | kpi             |
| [Settlement Delay Alert](/nerve-centre/kpi-cards/adyen/settlement-delay-alert)                       | Supporting Metrics | Alerts & Anomaly Detection          | kpi             |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector.*


# Adyen sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/adyen/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag Adyen KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/adyen) · [Audit Profile](/nerve-centre/kpi-cards/adyen/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/adyen/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each Adyen KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **10** of the 26 Adyen cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                                                                           | Direction        | Good | Bad | Unit     |
| ------------------------------------------------------------------------------ | ---------------- | ---- | --- | -------- |
| [Auth Rate Drop Alert](/nerve-centre/kpi-cards/adyen/auth-rate-drop-alert)     | Higher is better | 97   | 92  | %        |
| [Authorisation Rate](/nerve-centre/kpi-cards/adyen/authorisation-rate)         | Higher is better | 97   | 92  | %        |
| [Chargeback Rate](/nerve-centre/kpi-cards/adyen/chargeback-rate)               | Lower is better  | 0.5  | 1   | %        |
| [Chargeback Spike Alert](/nerve-centre/kpi-cards/adyen/chargeback-spike-alert) | Lower is better  | 0.5  | 1   | Count    |
| [Payment Volume (30d)](/nerve-centre/kpi-cards/adyen/payment-volume-30d)       | Watch for drops  | 0    | -15 | Currency |
| [Payments Health Score](/nerve-centre/kpi-cards/adyen/payments-health-score)   | Higher is better | 90   | 70  | Count    |
| [Refunds (30d)](/nerve-centre/kpi-cards/adyen/refunds-30d)                     | Lower is better  | 2    | 5   | Currency |
| [Refusal Rate](/nerve-centre/kpi-cards/adyen/refusal-rate)                     | Lower is better  | 3    | 8   | %        |
| [Refusal Spike Alert](/nerve-centre/kpi-cards/adyen/refusal-spike-alert)       | Lower is better  | 3    | 8   | %        |
| [Settlement Delay Alert](/nerve-centre/kpi-cards/adyen/settlement-delay-alert) | Lower is better  | 2    | 5   | Count    |


# Afterpay audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/afterpay/audit

What the Vortex IQ Afterpay health audit checks: Afterpay: BNPL Approval, Settlement, Refund/Dispute & Payments-to-Revenue

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/afterpay) · [Audit Profile](/nerve-centre/kpi-cards/afterpay/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/afterpay/sentiment)**

Afterpay state matters when it's tied to captured BNPL revenue, settlement cash flow, and refund/dispute exposure. This audit answers four questions: (1) is the API credential + region/environment config healthy, (2) is Pay-in-4 approval holding and what's driving declines / 3DS friction, (3) are refunds, chargebacks and settlement timing under control, and (4) does Afterpay volume reconcile to the commerce sibling's order revenue (and do refund spikes track commerce returns).

## What this audit checks

### Authentication & configuration

* Basic credential valid (auth on GET /v2/configuration) - Merchant ID + Secret Key accepted
* Region host correct (global api.us.afterpay.com / anz api.afterpay.com) and environment matches (sandbox vs production)
* BNPL minimum/maximum order limits returned by /v2/configuration cover the merchant's basket range

### Approval & checkout health

* Success (approval + capture) rate below 90%
* Decline rate above 8% (and which decline reasons dominate)
* 3DS challenge abandonment above 30% (added friction / lost conversion)
* Approval-rate drop during a campaign push (paying for traffic Afterpay won't approve)

### Refunds, disputes & settlement

* Refund rate above 8% of captured volume, or a refund spike > 50% vs 7-day baseline
* Chargeback rate above 1% (Visa/Mastercard programme threshold)
* Dispute response overdue (respondBy passed with status OPEN / UNDER\_REVIEW)
* Oldest pending payout aging above 5 days vs the typical 1-3 day schedule (cash-flow risk)

### Cross-platform: payments-to-revenue (the killer area)

* Afterpay captured volume vs commerce-sibling Afterpay-paid order revenue mismatch > 2% (reconciliation gap; sibling = shopify / bigcommerce / adobe\_commerce)
* Afterpay refund spike correlated with a commerce-sibling returns / cancellation spike (product / fulfilment issue, not a payments glitch)
* Declined-Afterpay shoppers re-attempting on a card gateway sibling (recoverable basket signal)
* Afterpay AOV-lift erosion vs commerce-sibling card AOV (BNPL value proposition weakening)

## Severity thresholds

| Signal                     | Warn | Critical |
| -------------------------- | ---- | -------- |
| `success_rate_pct`         | 95   | 90       |
| `decline_rate_pct`         | 5    | 8        |
| `threedsecure_abandon_pct` | 15   | 30       |
| `refund_rate_pct`          | 3    | 8        |
| `chargeback_rate_pct`      | 0.5  | 0.9      |
| `dispute_rate_pct`         | 0.5  | 1        |
| `payout_age_days`          | 2    | 5        |
| `reconciliation_gap_pct`   | 1    | 2        |

## Data sources

* `GET https://api.us.afterpay.com/v2/configuration` - Auth probe + BNPL config / order limits
* `GET https://api.us.afterpay.com/v2/payments` - Volume / approval / decline / 3DS / payment-method mix
* `GET https://api.us.afterpay.com/v2/payments/{id}/refund` - Refund value + reasons per payment (refund rate / volume)
* `GET https://api.us.afterpay.com/v2/settlements` - Payout status + age (pending payouts, settlement timing)
* `GET https://api.us.afterpay.com/v2/disputes` - Chargeback / dispute inventory + response deadlines


# Afterpay KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/afterpay/index

Every Afterpay KPI pulse Vortex IQ Nerve Centre tracks: 16 metrics covering revenue, orders, customers, refunds, and more.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/afterpay) · [Audit Profile](/nerve-centre/kpi-cards/afterpay/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/afterpay/sentiment)**

Vortex IQ Nerve Centre tracks **16** KPI pulses for Afterpay stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves.

The Afterpay connector brings the Vortex IQ **AI OS** to merchants offering Afterpay BNPL - strong on basket sizes and AOV lift in DTC fashion, beauty, and homewares. The **Nerve Centre** tracks 16 KPI pulses for Afterpay accounts (Success Rate, Decline Rate, Refund Rate, Chargeback Rate, Dispute Rate, settlement metrics, Top Decline Reasons, Top Payment Methods, Volume Trend). **Vortex Mind** investigates when a number moves; **Ask Viq™** lets you ask in plain English with citations back to the source card.

| Card                                                                                   | Metrics type       | Category           | Chart           |
| -------------------------------------------------------------------------------------- | ------------------ | ------------------ | --------------- |
| [3DS Abandonment Rate](/nerve-centre/kpi-cards/afterpay/3ds-abandonment-rate)          | Supporting Metrics | Transaction Health | gauge           |
| [Average Transaction](/nerve-centre/kpi-cards/afterpay/average-transaction)            | Supporting Metrics | Volume             | kpi             |
| [Avg Settlement Time (days)](/nerve-centre/kpi-cards/afterpay/avg-settlement-time)     | Supporting Metrics | Settlement         | kpi             |
| [Chargeback Rate](/nerve-centre/kpi-cards/afterpay/chargeback-rate)                    | Supporting Metrics | Refunds & Disputes | gauge           |
| [Decline Rate](/nerve-centre/kpi-cards/afterpay/decline-rate)                          | Supporting Metrics | Transaction Health | gauge           |
| [Dispute Rate](/nerve-centre/kpi-cards/afterpay/dispute-rate)                          | Supporting Metrics | Refunds & Disputes | gauge           |
| [Oldest Pending Payout (days)](/nerve-centre/kpi-cards/afterpay/oldest-pending-payout) | Supporting Metrics | Settlement         | kpi             |
| [Pending Payouts](/nerve-centre/kpi-cards/afterpay/pending-payouts)                    | Supporting Metrics | Settlement         | kpi             |
| [Refund Rate](/nerve-centre/kpi-cards/afterpay/refund-rate)                            | Supporting Metrics | Refunds & Disputes | gauge           |
| [Refund Volume](/nerve-centre/kpi-cards/afterpay/refund-volume)                        | Supporting Metrics | Refunds & Disputes | kpi             |
| [Success Rate](/nerve-centre/kpi-cards/afterpay/success-rate)                          | Supporting Metrics | Transaction Health | gauge           |
| [Top Decline Reasons](/nerve-centre/kpi-cards/afterpay/top-decline-reasons)            | Supporting Metrics | Transaction Health | bar\_horizontal |
| [Top Payment Methods](/nerve-centre/kpi-cards/afterpay/top-payment-methods)            | Supporting Metrics | Transaction Health | pie             |
| [Total Transactions](/nerve-centre/kpi-cards/afterpay/total-transactions)              | Supporting Metrics | Volume             | kpi             |
| [Total Volume](/nerve-centre/kpi-cards/afterpay/total-volume)                          | Supporting Metrics | Volume             | kpi             |
| [Volume Trend](/nerve-centre/kpi-cards/afterpay/volume-trend)                          | Supporting Metrics | Volume             | area            |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector. Replace this block when authored.*


# Afterpay sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/afterpay/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag Afterpay KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/afterpay) · [Audit Profile](/nerve-centre/kpi-cards/afterpay/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/afterpay/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each Afterpay KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **9** of the 18 Afterpay cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business and **save it for your company** in **Settings → Dashboard Settings → Alert Rules**.

## How sentiment powers triage

Sentiment turns the dashboard into a focus list. Every KPI is sorted into one of three states you can filter on:

* **Performing** - comfortably inside the good band.
* **Needs Attention** - has breached the band you set. This is where to act.
* **Stable** - within range, or an informational card with no good/bad direction.

Any KPI that has not met its sentiment band is flagged **Needs Attention**, so you go straight to the handful of cards that need action instead of scanning hundreds of charts.

| Card                                                                                                                                | Direction        | Good | Bad | Unit     |
| ----------------------------------------------------------------------------------------------------------------------------------- | ---------------- | ---- | --- | -------- |
| [3DS Abandonment Rate](/nerve-centre/kpi-cards/afterpay/3ds-abandonment-rate)                                                       | Lower is better  | 15   | 30  | %        |
| [Afterpay-vs-Commerce Revenue Reconciliation Gap](/nerve-centre/kpi-cards/afterpay/afterpay-vs-commerce-revenue-reconciliation-gap) | Lower is better  | 0    | 2   | %        |
| [Chargeback Rate](/nerve-centre/kpi-cards/afterpay/chargeback-rate)                                                                 | Lower is better  | 0.5  | 0.9 | %        |
| [Decline Rate](/nerve-centre/kpi-cards/afterpay/decline-rate)                                                                       | Lower is better  | 5    | 8   | %        |
| [Dispute Rate](/nerve-centre/kpi-cards/afterpay/dispute-rate)                                                                       | Lower is better  | 0.5  | 1   | %        |
| [Oldest Pending Payout (days)](/nerve-centre/kpi-cards/afterpay/oldest-pending-payout-days)                                         | Lower is better  | 2    | 5   | Count    |
| [Refund Rate](/nerve-centre/kpi-cards/afterpay/refund-rate)                                                                         | Lower is better  | 3    | 8   | %        |
| [Success Rate](/nerve-centre/kpi-cards/afterpay/success-rate)                                                                       | Higher is better | 95   | 90  | %        |
| [Total Volume](/nerve-centre/kpi-cards/afterpay/total-volume)                                                                       | Watch for drops  | 0    | -15 | Currency |


# Agile CRM audit profile, Vortex IQ
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/agile-crm/audit

What the Vortex IQ Agile CRM health audit checks: Agile CRM: List Health, Deliverability, Automation & Revenue-at-Risk

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/agile-crm) · [Audit Profile](/nerve-centre/kpi-cards/agile-crm/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/agile-crm/sentiment)**

Agile CRM list and campaign numbers only mean something when joined to deliverability risk and real ecom revenue. This audit answers: (1) is the auth/key healthy, (2) is the list decaying (bounces / spam / unsubscribes) toward send-throttle territory, (3) are email campaigns and automation flows actually firing and converting, and (4) when email volume is high but revenue is flat, can we tie it to an ecom sibling to show which sends drove no orders?

## What this audit checks

### Authentication & access

* REST API key + account email valid (Basic auth on /dev/api/users/current-user)
* Account domain resolves to the correct subdomain host
* Account plan exposes campaign-log + tracking endpoints (some endpoints are plan-gated)

### List & subscriber health

* Marketable audience (active, non-unsubscribed, non-bounced contacts) shrinking vs prior period
* Share of bounced contacts on a list above 5% (list decay)
* Unsubscribe rate above 2% sustained over the window
* Lists with zero growth and rising inactive share (stale list)

### Deliverability

* Delivery rate below 95% (sender-reputation or list-quality drift)
* Hard bounce rate above 5%
* Spam-complaint rate above 0.3% (Agile CRM / upstream ESP throttling risk)
* Unsubscribe rate above 2% on a single campaign

### Campaign & automation performance

* Open rate below 10% or click-to-open below 3% (content/segment problem)
* Enabled automation flow with last\_enrolled\_time stale > 24h (broken trigger)
* Flow status distribution skewed to paused/draft (automations not running)
* Revenue-per-send collapsing vs prior period despite steady send volume

### Revenue & checkout funnel

* Checkout-to-order rate below baseline (tail-of-funnel leak)
* Refund rate above 8% on tracked orders
* Placed-orders total down vs prior period while sends held flat

### Cross-platform: revenue-at-risk (the killer area)

* Campaigns with a healthy open rate but \~0 attributed ecom revenue when an ecommerce sibling is connected (sibling = bigcommerce/shopify/adobe\_commerce.order joined on utm\_source/contact\_email)
* Ecom customers absent from every Agile CRM list - missed lifecycle email revenue
* Engaged subscribers (repeat clickers) with zero ecom purchases - nurture-to-purchase gap
* Agile CRM tracked orders with no matching ecom-platform order within 24h (attribution / sync drift)

## Severity thresholds

| Signal                | Warn | Critical |
| --------------------- | ---- | -------- |
| `delivery_rate`       | 97   | 95       |
| `bounce_rate`         | 2    | 5        |
| `spam_complaint_rate` | 0.1  | 0.3      |
| `unsubscribe_rate`    | 0.5  | 2        |
| `open_rate`           | 15   | 10       |
| `refund_rate`         | 5    | 8        |

## Data sources

* `GET https://{domain}.agilecrm.com/dev/api/users/current-user` - Auth + account sanity
* `GET https://{domain}.agilecrm.com/dev/api/contacts/count` - Marketable-audience size + subscriber drift
* `GET https://{domain}.agilecrm.com/dev/api/lists` - List inventory, sizes, type
* `GET https://{domain}.agilecrm.com/dev/api/filters` - Saved-segment inventory
* `GET https://{domain}.agilecrm.com/dev/api/campaign-logs` - Send / delivery / open / click / bounce / spam / unsubscribe / revenue stats
* `GET https://{domain}.agilecrm.com/dev/api/workflows` - Automation flow inventory + status + last-enrolled
* `GET https://{domain}.agilecrm.com/dev/api/track/orders` - Checkout-started / placed / refunded tracked orders for funnel + attribution


# Agile CRM KPIs, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/agile-crm/index

Every Agile CRM KPI pulse Vortex IQ Nerve Centre tracks: 29 metrics covering revenue, orders, customers, refunds, and more.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/agile-crm) · [Audit Profile](/nerve-centre/kpi-cards/agile-crm/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/agile-crm/sentiment)**

Vortex IQ Nerve Centre tracks **29** KPI pulses for Agile CRM stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves.

The Agile CRM connector brings the Vortex IQ **AI OS** to small businesses on Agile CRM - all-in-one sales + marketing + service CRM popular with budget-conscious SMB needing a single tool across the customer lifecycle. The **Nerve Centre** tracks 29 KPI pulses including subscriber, deliverability, engagement, and revenue-attribution metrics. **Vortex Mind** investigates when a number moves; **Ask Viq™** lets you ask in plain English with citations back to the source card.

| Card                                                                                     | Metrics type       | Category            | Chart           |
| ---------------------------------------------------------------------------------------- | ------------------ | ------------------- | --------------- |
| [Active Subscribers (Est.)](/nerve-centre/kpi-cards/agile-crm/active-subscribers)        | Supporting Metrics | Customer Lifecycle  | kpi             |
| [Bounce Rate](/nerve-centre/kpi-cards/agile-crm/bounce-rate)                             | Supporting Metrics | Deliverability      | gauge           |
| [Campaign Status Breakdown](/nerve-centre/kpi-cards/agile-crm/campaign-status-breakdown) | Supporting Metrics | Email Campaigns     | donut           |
| [Checkout-to-Order Rate](/nerve-centre/kpi-cards/agile-crm/checkout-to-order-rate)       | Supporting Metrics | Revenue Attribution | gauge           |
| [Checkouts Started](/nerve-centre/kpi-cards/agile-crm/checkouts-started)                 | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Click-to-Open Rate](/nerve-centre/kpi-cards/agile-crm/click-to-open-rate)               | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Conversion Rate](/nerve-centre/kpi-cards/agile-crm/conversion-rate)                     | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Delivery Rate](/nerve-centre/kpi-cards/agile-crm/delivery-rate)                         | Supporting Metrics | Deliverability      | gauge           |
| [Email Click Rate](/nerve-centre/kpi-cards/agile-crm/email-click-rate)                   | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Email Health KPIs](/nerve-centre/kpi-cards/agile-crm/email-health-kpis)                 | Supporting Metrics | Email Engagement    | kpi             |
| [Email Open Rate](/nerve-centre/kpi-cards/agile-crm/email-open-rate)                     | Supporting Metrics | Klaviyo Overview    | gauge           |
| [Engagement Funnel](/nerve-centre/kpi-cards/agile-crm/engagement-funnel)                 | Supporting Metrics | Email Engagement    | funnel          |
| [Flow Count Summary](/nerve-centre/kpi-cards/agile-crm/flow-count-summary)               | Supporting Metrics | Email Automation    | kpi             |
| [Flow Status Breakdown](/nerve-centre/kpi-cards/agile-crm/flow-status-breakdown)         | Supporting Metrics | Email Automation    | donut           |
| [Flow Trigger Types](/nerve-centre/kpi-cards/agile-crm/flow-trigger-types)               | Supporting Metrics | Email Automation    | donut           |
| [Flows List](/nerve-centre/kpi-cards/agile-crm/flows-list)                               | Supporting Metrics | Email Automation    | table           |
| [List Count](/nerve-centre/kpi-cards/agile-crm/list-count)                               | Supporting Metrics | Customer Lifecycle  | kpi             |
| [List Health Summary](/nerve-centre/kpi-cards/agile-crm/list-health-summary)             | Supporting Metrics | List Health         | kpi             |
| [Lists Overview](/nerve-centre/kpi-cards/agile-crm/lists-overview)                       | Supporting Metrics | Customer Lifecycle  | table           |
| [Placed Orders Total](/nerve-centre/kpi-cards/agile-crm/placed-orders-total)             | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Refund Rate](/nerve-centre/kpi-cards/agile-crm/refund-rate)                             | Supporting Metrics | Revenue Attribution | gauge           |
| [Revenue per Recipient](/nerve-centre/kpi-cards/agile-crm/revenue-per-recipient)         | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Revenue per Send](/nerve-centre/kpi-cards/agile-crm/revenue-per-send)                   | Supporting Metrics | Revenue Attribution | kpi             |
| [Segments Overview](/nerve-centre/kpi-cards/agile-crm/segments-overview)                 | Supporting Metrics | Customer Lifecycle  | table           |
| [Spam Complaint Rate](/nerve-centre/kpi-cards/agile-crm/spam-complaint-rate)             | Supporting Metrics | Deliverability      | gauge           |
| [Top Lists by Name](/nerve-centre/kpi-cards/agile-crm/top-lists-by-name)                 | Supporting Metrics | List Health         | bar\_horizontal |
| [Total Revenue](/nerve-centre/kpi-cards/agile-crm/total-revenue)                         | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Total Sends](/nerve-centre/kpi-cards/agile-crm/total-sends)                             | Supporting Metrics | Klaviyo Overview    | kpi             |
| [Unsubscribe Rate](/nerve-centre/kpi-cards/agile-crm/unsubscribe-rate)                   | Supporting Metrics | Deliverability      | gauge           |

*Appendix space for FAQs, reconciliation guidance, or cross-connector notes specific to this connector. Replace this block when authored.*


# Agile CRM sentiment settings, Vortex IQ Nerve Centre
Source: https://docs.vortexiq.ai/nerve-centre/kpi-cards/agile-crm/sentiment

Industry-standard benchmark bands Vortex IQ AI OS uses to flag Agile CRM KPIs as Performing Well or Needs Attention, and how to tune them per company.

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/agile-crm) · [Audit Profile](/nerve-centre/kpi-cards/agile-crm/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/agile-crm/sentiment)**

Vortex IQ **AI OS** ships **industry-standard benchmark bands** for each Agile CRM KPI, so your dashboard flags **Performing Well** or **Needs Attention** the moment you connect. **8** of the 31 Agile CRM cards are sentiment-tuned; the rest are informational (counts, lists, breakdowns) with no good/bad direction.

The benchmarks below are a starting point grounded in industry standards. Adjust any **Good** or **Bad** threshold to match your business a