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

# Segment on Vortex IQ

> 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 cols={5}>
  <Card title="14">
    performance signals
  </Card>

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

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

  <Card title="0">
    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 cols={2}>
      <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>