> ## 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. # Salesforce on Vortex IQ > 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) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Monitor orders, fulfilment, delivery and settlement. Find failures, leaks and risks before they cost sales. Improve discovery, conversion, campaigns and repeat purchase. Find storefront, speed, accessibility and journey problems. Identify missing, inconsistent or outdated product data. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. 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. ### 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. | 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. | | 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 | | 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. | | 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. | ### 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. **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` **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` **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` **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` #### 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. ### 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. | 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.