> ## 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, PostHog > Event Source vs Ecom Revenue Attribution for PostHog 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:** [Analytics](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Event Source vs Ecom Revenue Attribution** is a cross-channel table that lines up each traffic source PostHog records against the ecommerce revenue attributed to it. It answers the question every owner asks: which channels actually drive sales, not just sessions. Crucially, it surfaces unattributed revenue, the orders that arrive with no clear source, which is where budget gets misallocated and where a tracking gap hides spend you cannot justify. | | | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Each event source (traffic source) with the ecommerce revenue attributed to it, including an unattributed bucket. | | **Sample type** | Backend API data from PostHog source data joined with revenue from the connected ecommerce platform, on the standard data refresh. | | **Why it matters** | Knowing which sources convert into revenue, and how much revenue has no source, is the foundation of efficient spend. A large unattributed share means you are flying partly blind. | | **Reading the value** | Read each row as a source and its revenue. When more than 25% of revenue is unattributed, attribution needs attention. | | **Currency** | currency | | **Time window** | `30D` | | **Alert trigger** | `>25% revenue unattributed` | | **Sentiment key** | `ph_xc_traffic_source_vs_revenue` | | **Roles** | owner, marketing | ## Calculation Calculated automatically from your PostHog data joined with revenue from your connected ecommerce platform. 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 **Event Source vs Ecom Revenue Attribution** for a typical merchant on PostHog.* Suppose the table shows paid search at the top with the most attributed revenue, then organic, then email, with a "direct / none" bucket holding 18% of revenue. After a UTM change on 09 May 26 breaks tagging, the unattributed bucket jumps to 31%, crossing the 25% alert. Real revenue did not move, but a third of it can no longer be credited to a channel, which would distort every spend decision. Cross-reference Top Traffic Sources for the source list and the funnel-vs-ecom card for the conversion side. 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 | | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | [`pos_top_sources`](/nerve-centre/kpi-cards/posthog/top-traffic-sources) | Engagement sibling: the source list. | | [`ph_xc_funnel_vs_ecom_conversion`](/nerve-centre/kpi-cards/posthog/posthog-funnel-conversion-vs-ecom-conversion) | Cross-channel sibling: funnel vs platform conversion. | | [`ph_xc_landing_page_perf_vs_bounce`](/nerve-centre/kpi-cards/posthog/landing-page-performance-vs-bounce) | Cross-channel sibling: landing performance vs bounce. | | [`pos_sessions`](/nerve-centre/kpi-cards/posthog/sessions) | Audience sibling: sessions by source. | | [`ph_paths_top_route`](/nerve-centre/kpi-cards/posthog/top-user-path) | Funnels sibling: routes from source to purchase. | ## Reconciling against the vendor's own dashboard **Where to look in PostHog's own dashboard:** In PostHog, break a revenue or purchase trend down by the source property to see revenue per channel. For the revenue figures themselves, your ecommerce platform's own reports are the source of truth. Differences here are almost always about attribution model, not raw revenue. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ----------------------------------------------------------------------------------------------------- | ------------------- | ------------------------------ | | **Attribution model.** First-touch, last-touch, and platform-native models split revenue differently. | Variable | Confirm the attribution model. | | **UTM coverage.** Missing or broken UTM tags inflate the unattributed bucket. | Unattributed higher | Audit your campaign tagging. | | **Currency and time zone.** Revenue totals shift with currency conversion and period boundaries. | Variable | Align currency and time zone. | **Cross-connector reconciliation:** this card already joins PostHog sources with platform revenue. For persistent gaps, use Vortex Mind to trace the attribution path. ## Known limitations / merchant FAQs **Q: How often does Event 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 is so much revenue unattributed?** Usually broken or missing UTM tags, direct traffic, dark social, and users who clear cookies between visit and purchase. A modest unattributed share is normal; a sudden jump points to a tagging break. **Q: The same order seems credited to two sources. Why?** Different attribution models assign credit differently. First-touch credits the discovering channel, last-touch credits the closing one. Pick one model and read the table consistently against it. **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 *Event Source vs Ecom Revenue Attribution* is one of hundreds of KPI pulses Vortex IQ tracks across PostHog 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.