Cross-channel analytics with Wevion — complete guide

Last updated: May 19, 2026

Cross-channel analytics with Wevion — complete guide

TL;DR: Wevion's Analytics combines per-platform deep-dive (Single Platform mode) with unified cross-platform analysis (Cross-Channel mode, behind ENABLE_CROSS_CHANNEL_ANALYTICS flag). Hard limits: 90-day max cross-channel + 10-min Redis cache + 24h demographics cache + 24-72h postback lag. Export PDF / CSV / scheduled.

Table of contents

Analytics overview (Single + Cross-Channel)

/analytics. Two modes:

Mode

When

Single Platform

Per-platform deep dive (Meta OR Google OR TikTok individually)

Cross-Channel

Unified view across selected platforms (behind feature flag)

KPI strip + channel mix + comparison

Budget recommendation

Rule-based (NOT AI) optimal allocation. Backed by getOptimalMixRecommendation in cross-channel-analytics.service.ts. Returns MixRecommendation rows (current_budget_pct vs recommended_budget_pct).

Top campaigns cross-platform

Best-performing campaigns aggregated across all selected platforms.

Comparing periods

Period vs previous-period delta_pct. WoW / MoM / YoY patterns.

Data freshness + exchange rates

Critical for accurate decisions:

  • 15-min sync cadence per platform

  • 10-min Redis cache TTL for cross-channel queries

  • 24h cache for audience demographics

  • 24-72h postback lag for ROAS / CPA on Meta-native conversions

  • Per-day exchange rates (EUR intermediate) for multi-currency

  • an-114 data freshness

  • an-115 exchange rates

Export PDF / CSV

Async via SQS EXPORT_UNIFIED_REPORT worker. 90-day max date range. Subscription required.

Troubleshoot

  • an-122 Analytics troubleshooting

  • Common: data stale, cross-channel UI missing (flag not enabled), 90-day rejected, ROAS vs platform UI mismatch (postback + attribution + FX)

FAQ

What's the difference between Single Platform + Cross-Channel?

Single Platform = per-platform deep dive (Meta-only, Google-only, etc.). Cross-Channel = unified view aggregating across platforms (behind ENABLE_CROSS_CHANNEL_ANALYTICS env flag).

Why is Cross-Channel grayed out?

Env flag not enabled. Ask admin.

90-day max date range — why?

Cross-channel query is expensive (joining many platforms with currency conversion). 90-day cap balances depth + performance. For longer ranges: split into multiple queries + concatenate externally.

Why does ROAS differ from platform UI?

Postback lag (24-72h) + attribution window (Meta 7d click vs Google 30d click) + currency conversion + cache lag. All explained in an-122.

How fresh is the data?

Platform → Wevion sync: 15 min. Cross-channel cache: 10 min. Demographics: 24h. Conversion postback: 24-72h.

What about real-time / hourly data?

Wevion's minimum cycle is 15 min. Sub-15-min is not supported by design.

Budget recommendation — is it AI?

NO — rule-based. Computes optimal allocation from historical ROAS + spend patterns. Predictable + auditable.

Strategic intelligence / saturation insights / seasonal tab / dashboard layouts / team performance owner view?

NOT implemented (DEFERRED — see PRD-19 deferred articles).

Next steps

Related