> ## 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. [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=amplitude) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Improve discovery, conversion, campaigns and repeat purchase. Find failures, leaks and risks before they cost sales. Identify missing, inconsistent or outdated product data. Keep tracking, access and change under governed control. Monitor orders, fulfilment, delivery and settlement. ### 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 40 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 | | -------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **D1 Retention %** | Merchant rule | Description pending editorial review; the signal is live. | | **D30 Retention %** | Merchant rule | Description pending editorial review; the signal is live. | | **Daily Active Users** | Watch only | Description pending editorial review; the signal is live. | | **Event Taxonomy Drift (new / unexpected events)** | Merchant rule | Sudden new event names = an untracked release or a renamed event breaking historical funnels. | | **Event Volume Drop (>25% vs baseline)** | Merchant rule | Alerts for Event Volume Drop (>25% vs baseline). | | **Event Volume by Platform** | Watch only | Event Volume by Platform. | | **Goal Completions** | Watch only | Goal Completions from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce against | | **Median Time to Convert** | Watch only | Description pending editorial review; the signal is live. | | **New vs Returning Users** | Watch only | New vs Returning Users, shown by share. | | **Pageviews per Session** | Watch only | Pageviews per Session from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce | | **Retention Curve (Nday)** | Watch only | Retention Curve (Nday) over time. | | **Top 10 Events by Volume** | Watch only | Top 10 Events by Volume. | | **Top Pages** | Watch only | Top Pages from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Ampl | | **Top Traffic Sources** | Watch only | Top Traffic Sources from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce ag | | **Total Event Volume** | Merchant rule | Description pending editorial review; the signal is live. | | **Weekly Active Users** | Watch only | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | ------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Amplitude Tracking Health Score** | Merchant rule | Composite: core events firing x funnel-conversion-stable x retention-healthy x no-attribution-drift. | | **Avg Events per User** | Watch only | Description pending editorial review; the signal is live. | | **Avg Session Length** | Watch only | Description pending editorial review; the signal is live. | | **Checkout Funnel Conversion %** | Merchant rule | End-to-end conversion across the merchant's primary purchase funnel. | | **Core Events Firing (purchase / add\_to\_cart)** | Merchant rule | If a core ecommerce event stops firing, every downstream funnel + attribution card silently lies. | | **Funnel Conversion Drop (>5pp in 24h)** | Merchant rule | Alerts for Funnel Conversion Drop (>5pp in 24h). | | **New Users** | Watch only | New Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amp | | **Real-Time Users** | Watch only | Real-Time Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce again | | **Returning Users** | Watch only | Returning Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce again | | **Session Conversion Rate** | Alert band 2 / 1 | Session Conversion Rate from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce a | | **Session Count** | Watch only | Description pending editorial review; the signal is live. | | **Stickiness (DAU/MAU)** | Merchant rule | DAU/MAU ratio , Amplitude-distinctive product-stickiness metric. | | **Top Cohorts by Conversion** | Watch only | Top Cohorts by Conversion. | | **Top Conversion Paths** | Watch only | Top Conversion Paths, broken down by row. | | **Users** | Watch only | Users from Amplitude, grouped under Traffic Acquisition. Computes when a live Amplitude integration is connected; reconciles ecommerce against Amplitu | | Signal | Alert behaviour | What it tracks | | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Amplitude Funnel Conversion vs Ecom Conversion** | Merchant rule | Description pending editorial review; the signal is live. | | **Biggest Funnel Step Drop-off** | Merchant rule | Step with the largest single-step abandonment , names where to focus UX work. | | **Bounce Rate** | Alert band 40 / 60 | Bounce Rate from Amplitude, grouped under Customer Behaviour. Computes when a live Amplitude integration is connected; reconciles ecommerce against Am | | **Cart Abandonment Rate** | Alert band 60 / 75 | Cart Abandonment Rate from Amplitude, grouped under Funnel Analysis. Computes when a live Amplitude integration is connected; reconciles ecommerce aga | | **Event Source vs Ecom Revenue Attribution** | Merchant rule | Event Source vs Ecom Revenue Attribution, broken down by row. | | **Landing Page Performance vs Bounce** | Merchant rule | Landing Page Performance vs Bounce, broken down by row. | | **Session Engagement vs Cart Abandonment** | Merchant rule | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | ------------------ | --------------- | --------------------------------------------------------------------- | | **D7 Retention %** | Merchant rule | Amplitude-distinctive , D7 is the canonical product-stickiness gauge. | | Signal | Alert behaviour | What it tracks | | ----------------------------------------------------- | --------------- | ------------------------------------------------------------- | | **Event Tracking Broken (core event stopped firing)** | Merchant rule | Alerts for Event Tracking Broken (core event stopped firing). | ### 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** 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` **Severity** high · **Outcome** Grow revenue · **Fix status** Report only Active users with zero purchase events almost always means purchase tracking is broken rather than nobody buying; every revenue metric downstream reads zero. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP09` **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` **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` **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: `AMP01` **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` **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` **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` **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only Weak day-7 retention means acquisition spend is filling a leaky bucket; improving early retention compounds every later cohort. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP04` **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only 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. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP02` **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only Conversion falling through a specific funnel step points at a concrete, findable obstacle: a form, a price reveal, a payment option, an error. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP03, AMP06` **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only Low stickiness (DAU/MAU) means the product or store is a destination people rarely return to; lifecycle marketing has little to work with. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP07` **Severity** low · **Outcome** Control risk and change · **Fix status** Report only Event naming drift splits the same behaviour across multiple names, silently corrupting every funnel and report built on it. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP08` **Severity** low · **Outcome** Grow revenue · **Fix status** Report only Missing ecommerce events in the tracking taxonomy mean revenue questions cannot be answered no matter how good the dashboards are. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `AMP05` #### 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 **5 read** and **0 write** operations across eventlists, funnels, retentions, sessionaverages, useractivitys on Amplitude. 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=amplitude) #### 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. | 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.