Skip to main content
Metrics type: Key MetricsCategory: Cross-Platform: Revenue at Risk

At a glance

Session Source vs Ecom Revenue Attribution is a cross-platform table that lines up where your FullStory sessions came from against the revenue your ecommerce platform attributes to each source. When a large share of revenue ends up unattributed, more than about a quarter, you have a measurement gap: traffic and orders are real, but the source link is being lost somewhere between the landing session and the order record. That gap distorts every channel ROI decision, so the table flags it as revenue at risk of being misallocated.

Calculation

Calculated automatically from your FullStory and ecommerce-platform data. Vortex IQ joins each session’s source with the revenue the platform attributes to it, lists the breakdown, and surfaces the revenue that could not be attributed to a source for the period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A representative reading of Session Source vs Ecom Revenue Attribution for a typical merchant on FullStory. Suppose the table shows paid search and email attributed cleanly, but 31% of revenue sits in an unattributed bucket, over the 25% guardrail. The cause is a redirect on a campaign link that strips the source parameter before the session lands, so those orders lose their origin. Fixing the redirect reattributes the revenue and the paid channel suddenly looks far more profitable than the prior, broken numbers suggested. For deeper investigation, use Vortex Mind to trace where the source parameter drops; for natural-language exploration, ask Ask Viq which channel is being under-credited.

Sibling cards merchants should reference together

Reconciling against the vendor’s own dashboard

Where to look in FullStory’s own dashboard: The source side comes from FullStory’s referrer and campaign data; the revenue side comes from your ecommerce platform’s attribution. Reconcile each against its own source over identical dates, then compare the joined view. Why the Vortex IQ value may legitimately differ: Cross-connector reconciliation: this card is itself a join, so use Vortex Mind to trace where source-to-revenue links are being lost.

Known limitations / merchant FAQs

Q: How often does Session Source vs Ecom Revenue Attribution update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard. Q: Is some unattributed revenue always expected? Yes. Direct traffic, dark-social referrals, and privacy settings always leave a residual unattributed share. The alert is about a large or growing bucket, not the existence of one. Q: Why does my FullStory dashboard show a different number? The most common reasons are the attribution model, lost source parameters, and period or currency differences. Align these before assuming a real divergence. Q: Can I customise the alert threshold? Yes, the unattributed-share alert threshold is configurable per profile in the Alert Rules tab. The 25% default is a starting point; tune it to your normal residual.

Tracked live in Vortex IQ Nerve Centre

Session Source vs Ecom Revenue Attribution is one of hundreds of KPI pulses Vortex IQ tracks across FullStory 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.