> ## 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.

# Session Source vs Ecom Revenue Attribution, Microsoft Clarity

> Session Source vs Ecom Revenue Attribution for Microsoft Clarity 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:** [Cross-Channel: Revenue at Risk](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Session Source vs Ecom Revenue Attribution maps the traffic sources Microsoft Clarity observes against the revenue your ecommerce platform attributes to each one. When a source brings plenty of sessions but little or no attributed revenue, you can see where spend or effort is not paying back, or where attribution is failing. For merchants, it is a clear read on which channels actually drive sales versus which only drive visits.

|                       |                                                                                                                            |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | A per-source table mapping Clarity-observed traffic sources to the ecommerce platform's attributed revenue.                |
| **Sample type**       | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| **Why it matters**    | Sources with high sessions but low attributed revenue reveal wasted spend or broken attribution worth investigating.       |
| **Reading the value** | Rows where session share and revenue share diverge sharply are the sources to question first.                              |
| **Currency**          | your store currency                                                                                                        |
| **Time window**       | `30D`                                                                                                                      |
| **Alert trigger**     | `>25% revenue unattributed`                                                                                                |
| **Sentiment key**     | `clr_xc_traffic_source_vs_revenue`                                                                                         |
| **Roles**             | owner, marketing                                                                                                           |

## Calculation

Vortex IQ joins the traffic source breakdown Microsoft Clarity exposes from session behaviour with the revenue your ecommerce platform attributes to each source, then lays both out in a per-source table over the selected window. The source side reflects what Clarity observes; the revenue side comes from your store platform, not Clarity. See At a glance for the headline definition and the worked example below for a representative reading.

## Worked example

*A representative reading of **Session Source vs Ecom Revenue Attribution** for a typical merchant on Microsoft Clarity.* Over the 30 days to 12 Mar 26, the table might show a social channel sending 22% of sessions but only 4% of attributed revenue, while more than 25% of revenue sits unattributed and trips the alert. That pattern hints at either a low-intent source or lost attribution on the converting paths. Use Vortex Mind to trace where the unattributed revenue is coming from, then ask Ask Viq in plain English to compare each source's session share against its revenue share so you can rebalance spend.

## Sibling cards merchants should reference together

| Card                                                                                                             | Why merchants reach for it                                                      |
| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| [`clr_top_traffic_sources`](/nerve-centre/kpi-cards/clarity/top-traffic-sources)                                 | Gives the Clarity-side source ranking this card pairs with revenue.             |
| [`clr_xc_funnel_vs_ecom_conversion`](/nerve-centre/kpi-cards/clarity/clarity-session-outcome-vs-ecom-conversion) | Shows whether low-revenue sources also under-convert or just under-attribute.   |
| [`clr_xc_landing_page_perf_vs_bounce`](/nerve-centre/kpi-cards/clarity/landing-page-performance-vs-quick-back)   | Checks whether weak landing pages are throttling revenue from specific sources. |
| [`clr_sessions_by_country`](/nerve-centre/kpi-cards/clarity/sessions-by-country)                                 | Adds geographic context to where source sessions and revenue diverge.           |
| [`clr_session_conversion_rate`](/nerve-centre/kpi-cards/clarity/session-conversion-rate)                         | Confirms whether a high-session, low-revenue source is a conversion problem.    |

## Reconciling against Microsoft Clarity

**Where to look in Microsoft Clarity's own dashboard:**

Review the Dashboard insights for traffic sources to confirm the session side, but note the attributed revenue figure comes from your store platform's reporting, not Clarity. Confirm the period and any device, channel, or bot filters match the Vortex IQ profile before comparing.

**Why the Vortex IQ value may legitimately differ:**

| Reason                                                                                                  | Direction | What to do                         |
| ------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------- |
| **Period boundary.** Vortex IQ uses rolling windows by default; Clarity may use calendar periods.       | Variable  | Match the period range.            |
| **Sampling.** Clarity may sample sessions on high-traffic sites; Vortex IQ reads what Clarity exposes.  | Variable  | Allow for sampling on busy stores. |
| **Filter scope.** Profile-level filters (device, channel, bot exclusion) may narrow the Vortex IQ view. | Variable  | Match filter settings.             |

**Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

## 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: Why does my Microsoft Clarity dashboard show a different number?**
The source side may be sampled by Clarity on high-traffic sites and reflects its own channel and bot definitions, while the revenue side comes from your ecommerce platform's attribution model. Period boundaries and filter scope can differ between the two. Match the period and filters on both sides before assuming a real divergence.

**Q: Why is some revenue marked unattributed?**
Attribution can break when tracking parameters are stripped, when shoppers move across devices, or when direct and dark-social traffic cannot be sourced. A large unattributed share is itself a signal to audit your tracking, not just to judge channel performance.

**Q: Can I customise the alert threshold?**
Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. Adjust to match your business baseline rather than relying on the generic default.

***

### Tracked live in Vortex IQ Nerve Centre

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