> ## Documentation Index > Fetch the complete documentation index at: https://docs.digifist.com/llms.txt > Use this file to discover all available pages before exploring further. # Analytics > Back-in-Stock performance metrics — active subscriptions, notifications sent, click rate, conversion rate, and revenue attribution. Back-in-Stock analytics measure the commercial impact of the module — how many customers are waiting for restocked products, how many received notifications, and how many converted to a purchase. Because the pipeline is fully automated, analytics are the primary tool for evaluating whether the module is performing well and identifying opportunities to improve conversion. ## What this covers * All five available metrics and what each measures * How to interpret the metrics together * What good performance looks like * Using analytics to diagnose pipeline issues ## Metrics **Active subscriptions** is the count of subscription records currently in `ACTIVE` status — customers who have subscribed and are waiting for a restock notification. This metric tells you how much pent-up demand exists across your out-of-stock catalog at any given time. A growing active subscription count on a specific product is a signal of strong demand — it can inform restocking decisions and inventory planning beyond its role in the notification pipeline. **How to read it:** A high active subscription count on a variant that has been out of stock for a long time may indicate that restocking is overdue. Conversely, a low active subscription count on a frequently out-of-stock variant may indicate the widget is not visible or is not converting visitors to subscribers effectively — check widget placement and copy. Active subscriptions decrease when: * Notifications are sent (subscriptions move to `NOTIFIED`) * Customers cancel (subscriptions move to `CANCELLED`) * Customers opt out of WhatsApp marketing (subscriptions remain `ACTIVE` but become ineligible for notification dispatch) Review active subscription counts before planning a restock. A variant with 500 active subscribers warrants a different restocking quantity decision than one with 5 — and both warrant a WhatsApp notification campaign at launch. **Notifications sent** is the total count of WhatsApp restock notification messages successfully dispatched — across all variants, all products, and all time periods within the selected date range. This is the primary volume metric for the module. It reflects how active your inventory restocking is and how many subscriber notification opportunities the pipeline has processed. **How to read it:** Notifications sent in isolation is a volume number — it becomes meaningful when compared against active subscriptions and conversion rate. A high notifications sent count with a low conversion rate suggests the notification content or timing is not driving action. A low notifications sent count may indicate infrequent restocking, low subscription capture, or pipeline issues preventing notifications from firing. Notifications sent does not equal messages delivered. A dispatched notification may fail delivery due to phone number issues, insufficient credits, or consent state changes. Cross-reference with campaign or automation analytics for delivery confirmation. **Click rate** is the percentage of notification recipients who tapped the product link in the restock message. ``` Click rate = Clicks ÷ Notifications sent × 100 ``` Click rate measures message relevance and CTA effectiveness. A customer who subscribed to a specific variant and receives a notification that confirms that variant is back should have strong motivation to click — a low click rate on a well-configured notification is unusual and worth investigating. **Common causes of low click rate:** * The notification arrived significantly after the restock — if a variant sold out again before the subscriber received the notification, clicking the link leads to an out-of-stock page * The product link in the template is broken or redirects incorrectly * The notification message does not clearly confirm which product is back and why the customer should act now * The notification arrived outside of the customer's active hours — a 3 AM notification may be dismissed before it is read **Conversion rate** is the percentage of notified customers who completed a purchase of the restocked product. ``` Conversion rate = Purchases ÷ Notifications sent × 100 ``` Conversion rate is the definitive measure of the module's commercial effectiveness. Back-in-Stock should consistently outperform other campaign types on conversion rate because the audience is self-selected high-intent customers — they actively requested to be notified about this specific product. **Factors that improve conversion rate:** * Fast notification dispatch — customers who receive the notification while inventory is still available convert at higher rates * Urgency signals in the notification template — "Limited stock" performs better than a generic "It's back" message when inventory is genuinely constrained * A direct product link that takes the customer to the specific variant page, not just the product root page * Notification timing that reaches the customer during their active hours **Revenue generated** is the attributed revenue from purchases made by customers who received a Back-in-Stock notification within a defined attribution window. This metric translates the module's activity into a concrete business outcome — the revenue that would not have been captured without the notification pipeline. It is the primary metric for evaluating ROI and justifying the module's billing cost. **How to use it:** Revenue generated should be compared against: * The cost of notifications sent (credits consumed per notification × credit cost) * The value of active subscriptions not yet notified (potential revenue awaiting a restock event) A healthy Back-in-Stock module should produce revenue attribution that clearly exceeds its credit cost — if this ratio is poor, investigate conversion rate and click rate for the optimization opportunities those metrics surface. ## Reading the metrics together The five metrics form a funnel from subscription capture to revenue: ``` Active subscriptions → How much demand is captured and waiting ↓ Restock event fires Notifications sent → How many customers were reached ↓ Customer opens message Click rate → How compelling the notification was ↓ Customer visits product Conversion rate → How effectively the product page closed the sale ↓ Purchase completed Revenue generated → The commercial outcome of the full pipeline ``` Each step in the funnel can be optimized independently. A high notifications sent count with low click rate points to the notification content or delivery timing. A high click rate with low conversion rate points to the product page experience or post-click availability. A high conversion rate with low revenue points to low subscription volume — not enough customers are subscribing in the first place. ## Accessing analytics Navigate to **Back-in-Stock → Analytics** to view the full metrics dashboard. Metrics can be filtered by date range and by specific product or variant to isolate performance for individual items. ## Best practices * **Review active subscription counts before restocking.** Use the data to inform inventory decisions — a variant with 200 active subscribers is a stronger restocking candidate than one with 3. * **Monitor click rate after template changes.** If you update the restock notification template, watch for changes in click rate in the first batch of notifications after the change goes live. * **Investigate any sudden drop in notifications sent.** A drop that does not correspond to fewer restocks may indicate the pipeline is not firing — check for automation deactivation, template approval status, or a failed Shopify webhook connection. * **Compare conversion rate across product categories.** High-demand categories (limited edition, seasonal) typically convert at higher rates than replenishment restocks (basics, consumables). Separate analysis by product type prevents aggregate metrics from masking underperformance in specific segments. ## Related guides * [Notification Logic](./notification-logic) — Understanding what drives the notifications sent count * [Subscription Lifecycle](./subscription-lifecycle) — How subscription status affects the active subscriptions count * [Back-in-Stock Add-on Billing](/whatsapp/billing/add-ons/back-in-stock) — Credit cost per notification relative to revenue generated