> ## 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. # Amplitude on Vortex IQ > Monitor traffic, conversion and tracking integrity from Amplitude, and catch instrumentation breaks before decisions are made on bad data. Monitor traffic, conversion and tracking integrity from Amplitude, 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) | **40** | **14** | **Build your own** | **Ready to build yours** | **5** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 40 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 | | ----------------------------------------------------- | ----------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Amplitude Tracking Health Score** | Grow revenue | Merchant rule | Composite: core events firing x funnel-conversion-stable x retention-healthy x no-attribution-drift. | | **Biggest Funnel Step Drop-off** | Protect revenue | Merchant rule | Step with the largest single-step abandonment , names where to focus UX work. | | **Checkout Funnel Conversion %** | Grow revenue | Merchant rule | End-to-end conversion across the merchant's primary purchase funnel. | | **Core Events Firing (purchase / add\_to\_cart)** | Grow revenue | Merchant rule | If a core ecommerce event stops firing, every downstream funnel + attribution card silently lies. | | **D7 Retention %** | Catalogue quality | Merchant rule | Amplitude-distinctive , D7 is the canonical product-stickiness gauge. | | **Event Source vs Ecom Revenue Attribution** | Protect revenue | Merchant rule | Event Source vs Ecom Revenue Attribution, broken down by row. | | **Event Tracking Broken (core event stopped firing)** | Control risk and change | Merchant rule | Alerts for Event Tracking Broken (core event stopped firing). | | **Event Volume Drop (>25% vs baseline)** | Run operations | Merchant rule | Alerts for Event Volume Drop (>25% vs baseline). | | **Funnel Conversion Drop (>5pp in 24h)** | Grow revenue | Merchant rule | Alerts for Funnel Conversion Drop (>5pp in 24h). | | **Landing Page Performance vs Bounce** | Protect revenue | Merchant rule | Landing Page Performance vs Bounce, broken down by row. | | **Stickiness (DAU/MAU)** | Grow revenue | Merchant rule | DAU/MAU ratio , Amplitude-distinctive product-stickiness metric. | | **Amplitude Funnel Conversion vs Ecom Conversion** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Daily Active Users** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Session Engagement vs Cart Abandonment** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Total Event Volume** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Bounce Rate** | Protect revenue | Alert band 40 / 60 | Bounce Rate from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **Cart Abandonment Rate** | Protect revenue | Alert band 60 / 75 | Cart Abandonment Rate from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **Event Taxonomy Drift (new / unexpected events)** | Run operations | Merchant rule | Sudden new event names = an untracked release or a renamed event breaking historical funnels. | | **Event Volume by Platform** | Run operations | Watch only | Event Volume by Platform. | | **Goal Completions** | Run operations | Watch only | Goal Completions from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **New Users** | Grow revenue | Watch only | New Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **New vs Returning Users** | Run operations | Watch only | New vs Returning Users, shown by share. | | **Pageviews per Session** | Run operations | Watch only | Pageviews per Session from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude da | | **Real-Time Users** | Grow revenue | Watch only | Real-Time Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **Retention Curve (Nday)** | Run operations | Watch only | Retention Curve (Nday) over time. | | **Returning Users** | Grow revenue | Watch only | Returning Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **Session Conversion Rate** | Grow revenue | Alert band 2 / 1 | Session Conversion Rate from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude dat | | **Top 10 Events by Volume** | Run operations | Watch only | Top 10 Events by Volume. | | **Top Cohorts by Conversion** | Grow revenue | Watch only | Top Cohorts by Conversion. | | **Top Conversion Paths** | Grow revenue | Watch only | Top Conversion Paths, broken down by row. | | **Top Pages** | Run operations | Watch only | Top Pages from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **Top Traffic Sources** | Run operations | Watch only | Top Traffic Sources from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data | | **Users** | Grow revenue | Watch only | Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitude data. | | **Avg Events per User** | Grow revenue | Watch only | Description pending editorial review; the signal is live. | | **Avg Session Length** | Grow revenue | Watch only | Description pending editorial review; the signal is live. | | **D1 Retention %** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **D30 Retention %** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Median Time to Convert** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Session Count** | Grow revenue | Watch only | Description pending editorial review; the signal is live. | | **Weekly Active Users** | Run operations | Watch only | Description pending editorial review; the signal is live. | ## 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 | | **Active Users but Zero Purchase Events** | high | Grow revenue | Active users with zero purchase events almost always means purchase tracking is broken rather than nobody buying; every revenue metric downstream reads zero. | 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 | | **Core Ecommerce Event Stopped Firing** | high | Control risk and change | 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. | 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 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 | | **D7 Retention Below Baseline** | medium | Protect revenue | Weak day-7 retention means acquisition spend is filling a leaky bucket; improving early retention compounds every later cohort. | Report only | | **Event 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 | | **Funnel Conversion Drop** | medium | Grow revenue | Conversion falling through a specific funnel step points at a concrete, findable obstacle: a form, a price reveal, a payment option, an error. | Report only | | **Low Product Stickiness (DAU/MAU)** | medium | Grow revenue | Low stickiness (DAU/MAU) means the product or store is a destination people rarely return to; lifecycle marketing has little to work with. | Report only | | **Event Taxonomy Drift** | low | Control risk and change | Event naming drift splits the same behaviour across multiple names, silently corrupting every funnel and report built on it. | Report only | | **Missing E-commerce Events in Taxonomy** | low | Grow revenue | Missing ecommerce events in the tracking taxonomy mean revenue questions cannot be answered no matter how good the dashboards are. | Report only | ### Build your own automated fixes 14 checks report findings on Amplitude 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 **5 read** and **0 write** operations across eventlists, funnels, retentions, sessionaverages, useractivitys on Amplitude. 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=amplitude) | Resource | Read operations | Write operations | | --------------- | --------------- | ---------------- | | eventlists | 1 | 0 | | funnels | 1 | 0 | | retentions | 1 | 0 | | sessionaverages | 1 | 0 | | useractivitys | 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 Amplitude 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.*