Analytics troubleshooting

Diagnose Wevion Analytics issues: stale data, ROAS vs platform mismatch, empty view, storefront KPIs/funnel missing, currency confusion, empty export.

Written By Salvatore Sinigaglia

Last updated About 1 hour ago

Diagnose Wevion Analytics issues: stale data, ROAS vs platform mismatch, empty view, storefront KPIs/funnel missing, currency confusion, empty export.

Analytics troubleshooting

The most common Analytics issues in Wevion, what causes them, and how to fix them. For each: a one-line diagnosis plus an actionable next step. Start with data freshness — sync cadence and postback lag explain most "numbers don't match" complaints.

Who is this for

Anyone hitting a discrepancy or missing element in Analytics. First stop before contacting support.

Issue 1: Data behind the platform's native UI

Symptom: Wevion shows older or slightly different numbers than the platform dashboard.

Cause: Wevion syncs platform insights roughly every 15 minutes, and purchase-based metrics (ROAS, CPA, purchases, sales) settle over 24-72h via postback.

Fix: Wait the cycle. For ROAS/CPA/MER decisions, use a last_7d minimum so recent, still-settling days don't distort the read. See an-114.

Issue 2: The view is empty / "no accounts selected"

Symptom: KPI cards and charts show no data or an empty state.

Cause: no accounts applied in the cascade selector, or the applied accounts had no activity in the window.

Fix: Open the platform + account selector, choose platforms or accounts, and click Applica — the page only recomputes once you apply. Then confirm those accounts had spend in the selected period.

Issue 3: Storefront KPIs or the site funnel are missing

Symptom: In Store & Business, Sessioni, CVR sito, or the Funnel sito don't appear (or the funnel shows an empty state).

Cause: no storefront session data yet. These are data-driven — Wevion shows them only once the store's ShopifyQL data has been collected.

Fix: Reconnect the store with the read_reports scope so session data starts flowing; the KPIs and funnel light up automatically once data lands. No manual toggle exists.

Issue 4: ROAS looks wrong vs the platform UI

Symptom: Wevion shows a different ROAS than Meta/Google for the same accounts and dates.

Causes + fixes:

  1. Postback lag (most common) — recent days are incomplete; use last_7d minimum and let data settle.
  2. Attribution windows differ across platforms — totals won't match exactly.
  3. Platform ROAS over-counts — cross-check with blended MER in the Store & Business view, which is attribution-independent.
  4. Currency conversion — if your display currency isn't the account's native currency, small FX variance appears (see an-115).

Issue 5: Platform ROAS and MER disagree

Symptom: The Advertising view shows a strong ROAS but the Store & Business MER is flat.

Cause: not a bug — platforms attribute conversions generously (view-through, cross-device), so platform ROAS overstates. MER (store revenue ÷ ad spend) reflects real blended return.

Fix: Trust MER for budget decisions; treat platform ROAS as a directional signal. See an-106.

Issue 6: Currency looks unexpected

Symptom: figures appear in a currency you didn't expect, or accounts don't compare cleanly.

Causes + fixes:

  1. The display-currency preference defaults to each account's native currency; multi-currency accounts then show different scales.
  2. Switch the preference to a single currency to compare accounts on one scale (conversion uses per-day rates).

See an-115 exchange rates.

Issue 7: Wrong store or "All stores" aggregate

Symptom: Store & Business numbers don't match a single store's expected figures.

Cause: the store selector defaults to All stores (team-wide aggregate).

Fix: Pick the specific store in the store selector next to the view toggle.

Issue 8: Export file looks empty or wrong

Symptom: the CSV/Excel download has no rows or the wrong data.

Causes + fixes:

  1. The selection had no data for the period — widen the range or check accounts/store.
  2. The export mirrors the active view and applied filters — switch to the right view and apply your selection before exporting.
  3. Accented characters garbled — open the Excel-format file (it carries a UTF-8 BOM) rather than importing raw CSV without UTF-8.

See an-116 export.

Issue 9: Compare deltas not showing

Symptom: KPI cards don't show a period-over-period delta.

Cause: the Compare to previous period toggle isn't enabled in the date picker.

Fix: Enable Compare in the date picker; deltas then appear on the KPI grid. See an-113.

Issue 10: My KPI layout reset

Symptom: custom KPI cards reverted to defaults.

Cause: you left edit mode with Annulla, or navigated away before Salva layout.

Fix: Re-enter edit mode, add your cards, and click Salva layout. Each view stores its selection independently. See an-103.

Escalation

If none of the above match:

  1. Capture: view, applied accounts, exact date range, observed vs expected value, timestamp
  2. Check whether a last_7d window changes the picture (rules out postback lag)
  3. Contact support with those details

FAQ

Why does Wevion Analytics show older numbers than my platform dashboard?

Because of layered lag. Wevion syncs platform insights roughly every 15 minutes, and purchase-based metrics such as ROAS, CPA, purchases, and sales settle over 24-72 hours via postback. A platform's own dashboard is closer to real-time. Wait the cycle and use a last_7d minimum window for ROAS or CPA reads before assuming a bug. See data freshness for the full picture.

Why is my Analytics view empty?

Most often no accounts are applied. Open the platform + account cascade selector, choose platforms or accounts, and click Applica — the page only recomputes once you apply a selection. Then confirm those accounts actually had spend in the selected period. In the Store & Business view, also check the store selector isn't pointing at a store with no orders in the range.

Why don't Sessioni, CVR sito, or the site funnel appear?

Those storefront elements are data-driven, not toggled. Wevion shows them only once the connected store's ShopifyQL session data has been collected, which requires the store to reconnect with the read_reports scope. Until data lands they stay hidden (the funnel shows an empty state) so you never see broken, empty cards. Once data arrives they appear automatically.

Why does my ROAS differ from what the platform reports, and which number do I trust?

The most common cause is postback lag — recent days are still settling — so use a last_7d minimum. Attribution-window differences and currency conversion add small variance too. Crucially, platform ROAS over-counts via view-through and cross-device attribution, so for budget decisions trust blended MER in the Store & Business view, which divides real store revenue by ad spend and doesn't depend on platform attribution.