Skip to main content
Metrics type: Supporting Metrics • Category: Ecommerce Platform

​
At a glance

Daily revenue per channel_id plotted over the trailing 90 days. The trend view that complements BC Channel Revenue Mix (single-snapshot pie) and BC Alert Channel Revenue Drop (real-time alarm). Surfaces channel cyclicality, growth slope per channel, and the leading indicators of channel decay before the alert fires. For BC stores running 5+ channels, this is the canonical “where is the business going” card.

​
Calculation

Calculated automatically from your BigCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US homewares brand on BigCommerce Enterprise. Window 1 Feb to 30 Apr 26 (90 days). Per-channel weekly totals smoothed. What’s interesting:
  1. Facebook Shop two-week dip 5-12 Apr to 0.3−0.4kfrom0.3-0.4k from 1.3k baseline (a -75% drop). The alert correctly fired during this window. Investigation revealed a Meta policy flag triggered by an automated content review; the merchant resolved with a single Business-Manager click and revenue recovered the next week. The 90-day trend view makes the dip-and-recovery shape obvious; the daily alert catches the dip in real time; together the two views are complementary.
  2. B2B portal shows extreme bi-weekly cyclicality. 42−66konevery−other−weekwith42-66k on every-other-week with 0 in between. This is the structural PO-cycle pattern; this merchant’s largest wholesale customers all order on a Tue-of-odd-weeks cadence. Reading B2B portal at daily granularity is meaningless; always read at 14-day or monthly rollups.
  3. Mar 1 web spike + Mar 8 dip is a promotion’s signature. 80k(+3080k (+30%) on Mar 1 followed by 59k (-7%) on Mar 8. The post-promo dip is normal and not a problem; customers who would have bought in the post-promo week pulled forward to take advantage of the discount. Net effect across both weeks is +$8k vs baseline; the promo lifted net revenue, just not as much as the spike suggests.
  4. Web channel underlying growth is +20% over the 90 days (58k→58k → 70k). Modest but healthy DTC growth. Amazon also +30% (13k→13k → 17k) suggesting strong cross-platform demand. Facebook Shop flat ex-incident. The growth pattern is “DTC + Amazon both up, Facebook flat, B2B flat”, suggesting the brand is succeeding with discoverability channels (web, Amazon) but not with social (Facebook).
  5. POS is the steady eddy. 4.8k→4.8k → 5.4k over 90 days, a steady 12% growth, no spikes, no dips. The flagship store has built loyal regulars; the trend is the regulars-base growth, not promotional flux. POS trend is the truest customer-loyalty proxy on this dashboard.
Action priority order:
  1. Smooth daily noise. Read at 7-day moving average for web, 14-day for B2B, weekly for POS.
  2. Annotate promo cycles. Cross-reference BC Top Coupons to mark spike-and-dip patterns as promo-driven rather than channel-strength signals.
  3. For dips like the Facebook Shop incident, the per-channel trend tells you the recovery shape; combine with BC Alert Channel Revenue Drop for real-time response.
  4. Compute slope per channel. A flat 90-day trend on a channel that should be growing is the leading indicator of channel decay.
  5. For multi-currency stores, view in constant-currency mode to separate FX from genuine growth.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in BigCommerce Control Panel: Analytics → Sales shows store-wide daily revenue; per-channel decomposition is available on Plus / Pro / Enterprise as “Sales by channel”. For B2B-specific trend: Channel Manager → B2B Edition → Analytics. For per-marketplace trend: Channel Manager → individual marketplace → Reports. Why our trend may differ from BC Sales by channel: Cross-connector reconciliation (when payment processors and analytics are connected): The per-channel revenue trend view is BC-aligned with similar cards on Shopify (per source_name and date) and Adobe Commerce (per store_id and date); merchant-facing semantics are equivalent.

​
Known limitations / merchant FAQs

My B2B portal trend looks crazy with bi-weekly $0 days. Is something broken? No, that’s the structural B2B PO-cycle pattern. Wholesale customers order on schedules (every-other-Tue, monthly on the 15th, quarterly). Reading B2B portal at daily granularity is meaningless. Always view B2B portal in 14-day or monthly rollup mode. My Mar 1 web spike disappeared by Mar 8. Was the promo a failure? Probably not. Promo spikes pull future demand forward; the post-promo dip is the result. Compute net-of-promo lift across the spike-and-dip pair. If the 2-week net is +X% above baseline, the promo lifted revenue; if it’s flat or negative, the promo only shifted demand without adding it. Always evaluate promos on a multi-week net basis. My alert threshold is 20% WoW but Facebook Shop is naturally that volatile. What should I do? Configure cohort-specific thresholds. Marketplace and social-commerce channels are noisier than web; raise their threshold to 30-40% WoW. Web should stay at 20%. B2B should switch to MoM rather than WoW (weekly comparisons are meaningless). Configure under Settings → Alerts → Channel cohort. The trend shows my Pinterest channel growing 50% MoM but absolute revenue is 400.ShouldIprioritiseit?∗∗Pinterest50400. Should I prioritise it?** Pinterest 50% growth from 400 to 600isimpressivepercentagebutsmallabsolute.Don′tprioritisebasedonpercentagegrowthalone;usetheabsolute−revenueviewalongsidetrendslope.∗∗Achannelunder600 is impressive percentage but small absolute. Don't prioritise based on percentage growth alone; use the absolute-revenue view alongside trend slope. **A channel under 5k/month at 50% growth gets less management attention than a channel at $50k/month at 5% growth, the latter is bigger absolute opportunity for both growth and risk. Multi-currency stores: does the chart show converted or native? Configurable. Native shows each channel in its own currency; converted shows all in your reporting currency using daily FX rates. Native is right for finance reads; converted is right for board reports. Be aware that converted view introduces FX drift into the trend shape, a 5% USD/GBP move appears as a 5% revenue lift on USD channels even with no volume change. My headline trend is up 10% over 90 days but no individual channel grew. How? Mix shift. If you opened a new channel mid-period or your high-AOV channel grew its order count, the headline can grow without per-channel growth. Cross-reference with BC Channel Revenue Mix to see whether a new channel entered or the channel mix shifted. Do refunds show on the trend? By default no, the trend is gross revenue. Refunds appear as a separate line via BC Refund Trend. Configure net-trend mode under Settings → Refund handling if your finance team prefers net. Should I include Cancelled / Incomplete? Default no. Including Cancelled introduces noise (orders that never billed); including Incomplete inflates the figure with abandoned-checkout dollars that never converted. Both are excluded for clean trend reads. My time-zone is GMT but my BC store TZ is PST. Do days align? By default we use the BC store’s configured TZ. Configure under Settings → Time zone if you want a different display TZ. This shifts day boundaries by up to 8 hours; mostly cosmetic but affects “day-of-promo” reads. Can I export the trend data? Yes, click the export button on the card; CSV / XLSX formats. Exports include raw daily values per channel for further analysis in Excel / BigQuery / Snowflake.

​
Tracked live in Vortex IQ Nerve Centre

Channel Revenue Trend is one of hundreds of KPI pulses Vortex IQ tracks across BigCommerce 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 or book a demo to see this metric running on your own data.