> ## 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 Source vs Ecom Revenue Attribution, Mixpanel

> Event Source vs Ecom Revenue Attribution for Mixpanel 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

> **Event Source vs Ecom Revenue Attribution** maps the event source and UTM data Mixpanel captures against the revenue your ecommerce platform actually recorded, so you can see which sources drive real sales. It does two jobs at once: it ranks your sources by revenue, and it exposes how much revenue cannot be tied back to any tracked source at all. A large unattributed slice is a budgeting blind spot, you are spending on channels you cannot credit, and crediting channels you may be overspending on. This card turns the gap between behavioural source data and recorded revenue into a number you can act on.

|                       |                                                                                                                                                                 |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | Revenue from your ecommerce platform allocated to the Mixpanel event source or UTM that preceded it, plus the share of revenue that maps to no tracked source.  |
| **Sample type**       | Backend API data joining Mixpanel event source and UTM data against revenue pulled from your ecommerce platform connector.                                      |
| **Why it matters**    | If a large share of revenue is unattributed, channel spend decisions are being made half-blind. Surfacing it protects the budget from mis-allocation.           |
| **Reading the value** | A table of sources with the revenue mapped to each, and an unattributed row. Watch the unattributed share; a rising figure means tracking coverage is slipping. |
| **Currency**          | currency                                                                                                                                                        |
| **Time window**       | `30D`                                                                                                                                                           |
| **Alert trigger**     | `>25% revenue unattributed`                                                                                                                                     |
| **Sentiment key**     | `mix_xc_traffic_source_vs_revenue`                                                                                                                              |
| **Roles**             | owner, marketing                                                                                                                                                |

## Calculation

Vortex IQ joins the event source and UTM data Mixpanel records for converting users against the revenue your ecommerce platform reports for the same orders over the window. Revenue is allocated to the source associated with each purchase, and any revenue whose order cannot be matched to a tracked source is grouped into an unattributed bucket. The card ranks sources by mapped revenue and shows the unattributed share alongside. The alert latches when the unattributed share rises above the configured threshold, by default more than a quarter of revenue, since a large unmatched slice undermines any channel-level decision built on the data.

## Worked example

*A representative reading of **Event Source vs Ecom Revenue Attribution** for a typical merchant on Mixpanel.* Suppose over the 30 days to 18 Jun 26 your platform recorded 100,000 units of revenue. The card maps roughly 38,000 to paid search, 27,000 to organic, and 19,000 to email, leaving about 16,000 units, or 16%, unattributed, comfortably under the threshold. A week later a campaign launches with UTM tags that the site strips on redirect. The unattributed share climbs to 29% and the alert fires. The table shows paid search revenue looking artificially flat while the unattributed row swells. You fix the redirect so the UTM parameters survive, and attribution coverage recovers. The revenue was always there; the tracking just stopped crediting it. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.

## Sibling cards merchants should reference together

| Card                                                                                                                 | Why merchants reach for it                                                                        |
| -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| [`mix_top_sources`](/nerve-centre/kpi-cards/mixpanel/top-traffic-sources)                                            | The source ranking by traffic, the behavioural side of this revenue view.                         |
| [`mix_funnel_conversion`](/nerve-centre/kpi-cards/mixpanel/primary-funnel-conversion)                                | Shows how well each source's traffic converts, explaining why revenue concentrates where it does. |
| [`mix_xc_funnel_vs_ecom_conversion`](/nerve-centre/kpi-cards/mixpanel/mixpanel-funnel-conversion-vs-ecom-conversion) | A sister cross-channel card; confirms whether tracking drift, not demand, is behind a gap.        |
| [`mix_flows_conversion_path_share`](/nerve-centre/kpi-cards/mixpanel/conversion-path-share)                          | Reveals the paths converting users take, useful when a single source claims too much credit.      |
| [`mix_event_volume`](/nerve-centre/kpi-cards/mixpanel/total-event-volume)                                            | A drop in total events often precedes a rise in unattributed revenue from lost tagging.           |

## Reconciling against Mixpanel

**Where to look in Mixpanel's own dashboard:**

In Mixpanel, break your purchase event down by source or UTM over the last 30 days to see how conversions distribute across channels. Then read total revenue from your ecommerce platform for the same range. Comparing the source split against total revenue, and noting how much revenue has no matching source, reproduces what the card does. Make sure the purchase event and the attribution model (first-touch vs last-touch) match what the card uses, since those choices move revenue between sources.

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

| Reason                                                                                         | Direction                              | What to do                                                         |
| ---------------------------------------------------------------------------------------------- | -------------------------------------- | ------------------------------------------------------------------ |
| **Attribution model.** First-touch and last-touch credit different sources for the same order. | Variable                               | Match the attribution model the card uses before comparing splits. |
| **Lost UTM tags.** Redirects or stripped parameters push revenue into the unattributed bucket. | Vortex IQ may read higher unattributed | Fix tag preservation, then re-check coverage.                      |
| **Order-match basis.** Some orders may not join to a Mixpanel session at all.                  | Vortex IQ may read higher unattributed | Confirm the order identifier links cleanly across both systems.    |

**Cross-connector reconciliation:** this card joins Mixpanel source data with revenue from your ecommerce platform, so the totals should reconcile to the platform's recorded revenue once the unattributed bucket is included. When the split looks wrong, check the attribution model and order-match logic before reallocating budget. For divergence investigations, use Vortex Mind.

## Known limitations / merchant FAQs

**Q: How often does Event Source vs Ecom Revenue Attribution update?**
It refreshes as both feeds report for the window. Mixpanel source data and your ecommerce platform's revenue data update on their own cadence, so the attribution split settles once both sides have reported for the period.

**Q: Why is so much revenue unattributed?**
The usual causes are lost or stripped UTM tags, redirects that drop parameters, direct traffic with no source, and orders that never joined to a tracked session. A rising unattributed share almost always points to a tagging or linking break rather than a real shift in channels.

**Q: The revenue total does not match my platform exactly. Why?**
Small differences come from refunds, currency conversion timing, or orders that fall just outside the window on one side. The card is for understanding the relative source split and the unattributed share, not for replacing your platform's official revenue figure.

**Q: Can I customise the alert threshold?**
Yes, the unattributed-revenue threshold (more than a quarter by default) and the attribution model are configurable per profile in the Sensitivity tab. Tighten the threshold if your tagging is usually clean and you want early warning, loosen it if a structural share of direct or untaggable traffic is normal for your store.

***

### Tracked live in Vortex IQ Nerve Centre

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