> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Iterable on Vortex IQ > 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. 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. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) ยท [How connecting works](/integrations/connector-catalogue) | **31** | **12** | **Build your own** | **Ready to build yours** | **12** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 31 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | -------------------------------------- | ------------------- | -------------------- | -------------------------------------------------------------------------------------------------- | | **Abandoned-Cart Recovery Value** | Protect revenue | Merchant rule | Currency recovered per 30D by the abandoned-cart journey. Goes to zero if the journey is disabled. | | **Email Share of Total Store Revenue** | Protect revenue | Merchant rule | Healthy DTC ranges 20-30%. Below 15% = email under-leveraged; above 40% = paid-acq atrophy risk. | | **Active Subscribers (Est.)** | Run operations | Merchant rule | Estimated subscribed, reachable contacts. | | **Bounce Rate** | Protect revenue | Alert band 2 / 5 | Share of sends that bounced. Rising bounces hurt sender reputation. | | **Campaign Status Breakdown** | Grow revenue | Merchant rule | Campaigns grouped by state (Draft, Scheduled, Running, Finished). | | **Checkout-to-Order Rate** | Grow revenue | Alert band 70 / 50 | Share of started checkouts that became paid orders. | | **Checkouts Started** | Customer experience | Merchant rule | Checkouts begun from email clicks, where Iterable reports it. | | **Click-to-Open Rate** | Grow revenue | Alert band 10 / 3 | Clicks as a share of opens - engagement quality independent of open-rate inflation. | | **Conversion Rate** | Grow revenue | Alert band 3 / 1 | Purchases as a share of emails sent. Ties send volume to revenue. | | **Delivery Rate** | Protect revenue | Alert band 98 / 95 | Share of sends accepted by the inbox provider. Below 95% needs attention. | | **Email Click Rate** | Grow revenue | Alert band 2 / 0.5 | Unique clicks over delivered. The clearest engagement signal. | | **Email Health KPIs** | Protect revenue | Merchant rule | Delivered, bounced and unsubscribed at a glance - your deliverability vitals. | | **Email Open Rate** | Run operations | Alert band 20 / 10 | Unique opens over delivered. iOS Mail Privacy inflates this; pair with click-to-open. | | **Engagement Funnel** | Protect revenue | Merchant rule | Sent -> Delivered -> Opened -> Clicked. Drop-offs expose deliverability vs content weakness. | | **Flow Count Summary** | Customer experience | Merchant rule | How many journeys exist on the account. | | **Flow Status Breakdown** | Customer experience | Merchant rule | Journeys split by enabled vs disabled. | | **Flow Trigger Types** | Customer experience | Merchant rule | Journeys grouped by what triggers them. | | **Flows List** | Customer experience | Merchant rule | Every Iterable journey and its current status. | | **List Count** | Grow revenue | Merchant rule | Number of audiences on the account. | | **List Health Summary** | Run operations | Merchant rule | Total reachable members across all lists. | | **Lists Overview** | Grow revenue | Merchant rule | Every audience with its member count. | | **Placed Orders Total** | Run operations | Merchant rule | Orders attributed to email in the window. | | **Refund Rate** | Protect revenue | Alert band 2 / 8 | Share of attributed orders later refunded. | | **Revenue per Recipient** | Grow revenue | Merchant rule | Revenue divided by emails sent - what each address is worth per send. | | **Revenue per Send** | Grow revenue | Merchant rule | Revenue divided by emails sent - the efficiency of each send. | | **Segments Overview** | Run operations | Merchant rule | Saved segments and their sizes. | | **Spam Complaint Rate** | Protect revenue | Alert band 0.1 / 0.3 | Complaints per send. Above 0.1% Gmail/Yahoo start marking the sender domain. | | **Top Lists by Name** | Grow revenue | Merchant rule | Largest audiences by member count. | | **Total Revenue** | Grow revenue | Merchant rule | Placed-order revenue Iterable attributes to email sends in the conversion window. | | **Total Sends** | Grow revenue | Merchant rule | Total emails sent across campaigns in the window. | | **Unsubscribe Rate** | Protect revenue | Alert band 0.5 / 2 | Unsubscribes per send. A spike signals list fatigue or off-target content. | ## 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. | Check | Severity | Outcome | Why it matters | Fix status | | -------------------------------------------------- | -------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | **Spam complaint rate > 0.1%** | critical | Protect revenue | 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 co | Report only | | **API key missing required permissions** | high | Control risk and change | 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. | Report only | | **Abandoned-cart flow not live** | high | Protect revenue | 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 con | Report only | | **Bounce rate > 5%** | high | Protect revenue | 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 go | Report only | | **Delivery rate \< 95%** | high | Protect revenue | 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 | Report only | | **Spam Complaint Rate too high** | high | Protect revenue | 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 reven | Report only | | **Email Bounce Rate too high** | medium | Protect revenue | 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. | Candidate remediation | | **Inactive workflows (disabled journeys)** | medium | Protect revenue | 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. | Candidate remediation | | **Welcome flow not live** | medium | Grow revenue | New subscribers are at their most engaged in their first days; without a live welcome flow that window closes unconverted. | Candidate remediation | | **Limited lists / segmentation** | low | Grow revenue | Broadcasting to one undifferentiated list sends the same message to buyers, prospects and lapsed customers alike, which depresses engagement and accelerates unsubscribes. | Report only | | **Limited segmentation , fewer than 3 segments** | low | Protect revenue | 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 e | Report only | | **Too many draft flows (> 3) , launch tech debt** | low | Grow revenue | 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 | Candidate remediation | ### Build your own automated fixes 12 checks report findings on Iterable today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **8 read** and **4 write** operations across campaigns, campaign metrics, channels, exportdatajsons, lists, listgetusers on Iterable. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=iterable) | 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. ### 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. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*