> ## 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. # Event Volume Drop (>25% vs baseline), Amplitude > Event Volume Drop (>25% vs baseline) for Amplitude stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Analytics](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Event Volume Drop (>25% vs baseline)** is a real-time alert card in Nerve Centre that fires when total event volume coming from Amplitude falls more than 25 percent below its recent baseline. A drop that steep is almost always a signal problem rather than a real traffic collapse. The usual culprits are a broken SDK initialisation after a deploy, a consent or cookie change blocking tracking, a tag-manager misconfiguration, or an ad-blocker shift. The card counts how many such alerts are currently active so you can confirm whether your data pipeline is healthy before you trust any downstream metric. | | | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The count of active alerts where total Amplitude event volume has fallen more than 25 percent below the trailing 7-day baseline. | | **Sample type** | Real-time alert evaluation against Amplitude event volume, refreshed continuously in Nerve Centre. | | **Why it matters** | If events stop arriving, every funnel, retention, and conversion metric built on them becomes unreliable. This card protects the integrity of the whole Amplitude dataset. | | **Reading the value** | A value above zero means event volume has dropped past the threshold. Open the alert to see when the drop began and which platforms or events are affected. | | **Currency** | count | | **Time window** | `RT` | | **Alert trigger** | `total event volume down >25% vs 7D baseline` | | **Sentiment key** | `amp_alert_event_volume_drop` | | **Roles** | owner, marketing | ## Calculation Nerve Centre tracks total event volume reported by Amplitude and compares the current reading against a trailing 7-day baseline of normal volume. When current volume falls more than 25 percent below that baseline, the alert fires and is added to the active count shown on this card. The card value is the number of such alerts currently open. See the At a glance summary above for what the card tracks and the worked example below for a typical reading. ## Worked example *A representative reading of **Event Volume Drop (>25% vs baseline)** for a typical merchant on Amplitude.* Over the prior week the store averaged about 480,000 events per day. On 18 Mar 26 volume came in at roughly 310,000, about 35 percent below baseline, which crosses the threshold, so the alert fires and the card reads 1. The team opens the alert and sees the drop is concentrated on web events while mobile is unaffected, which points at the website rather than the app. Vortex Mind traces the gap to a tag-manager release that loaded the Amplitude SDK after the consent banner, suppressing events for users who had not yet interacted. Ask Viq is used to ask, in plain English, which event names lost the most volume so the team can confirm the fix once the SDK load order is corrected. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | [`amp_event_volume`](/nerve-centre/kpi-cards/amplitude/total-event-volume) | Shows the total event count this alert watches for drops. | | [`amp_alert_tracking_broken`](/nerve-centre/kpi-cards/amplitude/event-tracking-broken-core-event-stopped-firing) | Confirms whether a specific core event has stopped firing entirely. | | [`amp_core_events_firing`](/nerve-centre/kpi-cards/amplitude/core-events-firing-purchase-add-to-cart) | Checks that purchase and add-to-cart events are still flowing. | | [`amp_alert_conversion_drop`](/nerve-centre/kpi-cards/amplitude/funnel-conversion-drop-5pp-in-24h) | Tells a tracking gap apart from a real funnel conversion drop. | | [`amp_health_score`](/nerve-centre/kpi-cards/amplitude/amplitude-tracking-health-score) | Gives overall instrumentation confidence behind event volume. | ## Reconciling against Amplitude **Where to look in Amplitude's own dashboard:** Open Event Segmentation and chart total event count over the last 7 to 14 days to see the dip in context. Amplitude's own anomaly detection and Alerts can also be set on event volume; compare what Nerve Centre flagged against Amplitude's volume trend and any native alert in the same window. Confirm the date range, the events included, and the platform or segment scope match the Vortex IQ profile before concluding the readings disagree. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ------------------------------------------------------------------------------------------------------------------------------------ | --------- | ---------------------------------------- | | **Period boundary.** Nerve Centre compares against a rolling 7-day baseline; Amplitude charts may use calendar periods. | Variable | Align both to the same window. | | **Time zone.** Amplitude uses the project time zone; Vortex IQ aligns to the merchant reporting time zone. | Marginal | Confirm time zone match. | | **Filter and segment scope.** Profile-level filters (platform, event set, test traffic) can change which events count toward volume. | Variable | Match the event set and filter settings. | **Cross-connector reconciliation:** when this fires, complement the Amplitude volume view with the sibling cards above and your server-side order or pageview logs to confirm whether real traffic moved. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How quickly does this alert fire after volume drops?** It evaluates in real time against incoming Amplitude event volume, so it surfaces within the same Nerve Centre refresh cycle once volume crosses 25 percent below baseline. There is a short detection lag while enough of the current window accumulates to compare cleanly. **Q: Why does my Amplitude chart look normal but the alert fired?** Often the baseline window or the events included differ between Amplitude and the Vortex IQ profile, or a real dip is masked by a calendar-period view. Match the date range, event set, and time zone before assuming a false alarm. **Q: Could a genuine traffic decline trigger this rather than a tracking issue?** Yes. A real drop in visits, a paused campaign, or a seasonal lull can all pull volume down. Read this card next to your platform's order and session data to tell a real traffic decline apart from a broken pipeline. **Q: Can I customise the alert threshold?** Yes, the 25 percent trigger and the baseline window are configurable per profile in the Sensitivity tab. Tune them to your normal daily volume variance rather than relying on the generic default. *** ### Tracked live in Vortex IQ Nerve Centre *Event Volume Drop (>25% vs baseline)* is one of hundreds of KPI pulses Vortex IQ tracks across Amplitude and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.