31
performance signals
12
automated checks
0
prepared fixes
0
proven workflows
12
API operations
- Overview
- Monitor (31)
- Audit (12)
- Automate
What you can achieve
Capabilities are grouped around merchant outcomes, not API terminology.Protect revenue
Find failures, leaks and risks before they cost sales.
Run operations
Monitor orders, fulfilment, delivery and settlement.
Grow revenue
Improve discovery, conversion, campaigns and repeat purchase.
Customer experience
Find storefront, speed, accessibility and journey problems.
Control risk and change
Keep tracking, access and change under governed control.
From connection to verified outcome
The controlled sequence every capability follows. Nothing changes a connected system without the approval step.1
Connect
Authorise the source. Scopes are shown before access is granted.
2
Monitor
Watch the signals against your own baselines, not universal defaults.
3
Detect
Run checks and gather evidence specific to your store.
4
Recommend
Explain what happened, why it matters and the proposed action.
5
Approve
You review scope, risk and reversibility before anything changes.
6
Execute
Apply through governed connector operations.
7
Verify
Confirm the intended result and keep the receipt.
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.Grow revenue (12 signals)
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. |
Protect revenue (9 signals)
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. |
Run operations (5 signals)
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. |
Customer experience (5 signals)
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. |
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.Spam complaint rate > 0.1%
Spam complaint rate > 0.1%
Severity critical · Outcome Protect revenue · Fix status Report onlySpam 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-002API key missing required permissions
API key missing required permissions
Severity high · Outcome Control risk and change · Fix status Report onlyWhen 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:
ITE06Abandoned-cart flow not live
Abandoned-cart flow not live
Severity high · Outcome Protect revenue · Fix status Report onlyAbandoned-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, ITE03Bounce rate > 5%
Bounce rate > 5%
Severity high · Outcome Protect revenue · Fix status Report onlyMore 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-001Delivery rate < 95%
Delivery rate < 95%
Severity high · Outcome Protect revenue · Fix status Report onlyMore 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-003Spam Complaint Rate too high
Spam Complaint Rate too high
Severity high · Outcome Protect revenue · Fix status Report onlySpam 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:
ITE02Email Bounce Rate too high
Email Bounce Rate too high
Severity medium · Outcome Protect revenue · Fix status Candidate remediationBounced 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:
ITE01Inactive workflows (disabled journeys)
Inactive workflows (disabled journeys)
Severity medium · Outcome Protect revenue · Fix status Candidate remediationAutomations 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:
ITE04Welcome flow not live
Welcome flow not live
Severity medium · Outcome Grow revenue · Fix status Candidate remediationNew 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-002Limited lists / segmentation
Limited lists / segmentation
Severity low · Outcome Grow revenue · Fix status Report onlyBroadcasting 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:
ITE05Limited segmentation , fewer than 3 segments
Limited segmentation , fewer than 3 segments
Severity low · Outcome Protect revenue · Fix status Report onlyWith 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 spamVortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.Reference:
EM-LIST-001Too many draft flows (> 3) , launch tech debt
Too many draft flows (> 3) , launch tech debt
Severity low · Outcome Grow revenue · Fix status Candidate remediationMore 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 tA likely corrective 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-004Build your own automated fixes
Turn any finding into an automated fix with a Vortex IQ workflow: over 13,000 read and write operations across more than 200 connectors are available as building blocks, with approval, verification and rollback on every change.Automate approved work
Vortex IQ is integrated with 8 read and 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 workflowReady 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.Browse the operations you can build with
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 |