> ## 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. # Plausible Analytics on Vortex IQ > 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. 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) | **13** | **11** | **Build your own** | **Ready to build yours** | **5** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 13 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 | | --------------------------- | --------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Real-Time Users** | Grow revenue | Merchant rule | Current visitors on the site right now (Realtime API). | | **Session Conversion Rate** | Grow revenue | Alert band 3 / 1 | Goal conversions ÷ sessions - the headline funnel-health gauge. | | **Sessions** | Grow revenue | Merchant rule | Total visits (sessions) over the window - the headline Plausible traffic pulse. | | **Avg Session Duration** | Grow revenue | Alert band 120 / 30 | Average visit\_duration in seconds over the window. | | **Bounce Rate** | Protect revenue | Alert band 35 / 60 | Share of single-page visits. Higher is worse. | | **Cart Abandonment Rate** | Protect revenue | 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 connected. | | **Goal Completions** | Grow revenue | Merchant rule | Total conversions across configured goals over the window. | | **New Users** | Grow revenue | Merchant rule | First-time visitors (visitors filtered to visit:is\_returning=false). | | **Pageviews per Session** | Grow revenue | Alert band 3 / 1.5 | views\_per\_visit - depth-of-visit signal. | | **Returning Users** | Grow revenue | Merchant rule | Returning visitors (visitors filtered to visit:is\_returning=true). | | **Top Pages** | Grow revenue | Watch only | Top pages by pageviews (dimension event:page). | | **Top Traffic Sources** | Grow revenue | Watch only | Top referrer sources by visitors (dimension visit:source). | | **Users** | Grow revenue | Merchant rule | Unique visitors over the window. | ## 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 | | ------------------------------------------------------------------------- | -------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **Key events not configured (purchase event firing but conversions = 0)** | critical | Grow revenue | 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 repor | Report only | | **Attribution divergence with ecommerce platform > 25% over 30d** | high | Protect revenue | 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. | Report only | | **Cart abandonment rate above 75%** | high | Protect revenue | 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, | Report only | | **Goal Stopped Converting** | high | Grow revenue | Goals present but never completing typically means the goal or its tracking broke, not that every visitor changed their mind on the same day. | Report only | | **Plausible Conversions but Zero Ecom Orders** | high | Protect revenue | 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. | Report only | | **Session Conversion Rate Below Floor** | high | Grow revenue | Session conversion below the floor while traffic holds means the store is buying visits it cannot convert; the cause is usually specific and findable. | Report only | | **Session conversion rate below 1%** | high | Grow revenue | 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, | Report only | | **Average engagement time below 30 seconds** | medium | Grow revenue | 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 t | Report only | | **Bounce Rate Spike** | medium | Protect revenue | A bounce-rate spike after a release or campaign change is the earliest cheap warning that something on the landing experience broke. | Report only | | **Bounce rate above 70% over 30d** | medium | Protect revenue | 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 v | Report only | | **Session Volume Drop vs Prior Period** | medium | Control risk and change | 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. | Report only | ### Build your own automated fixes 11 checks report findings on Plausible Analytics 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 **4 read** and **1 write** operations across querys, stataggregates, statbreakdowns, statrealtimevisitors, stattimeserys on Plausible Analytics. 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=plausible) | 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. ### 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. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*