Switch between Single Platform and Cross-Channel

Last updated: May 19, 2026

Switch between Single Platform and Cross-Channel

Top toolbar mode toggle: Single Platform | Cross-Channel. Single Platform is always available. Cross-Channel is gated by the ENABLE_CROSS_CHANNEL_ANALYTICS env flag (admin-level setting). If your toggle is missing the Cross-Channel option, the flag is off — ask your admin.

Who is this for

Anyone wondering "which mode should I use?" or "where did the Cross-Channel option go?"

How the toggle works

Single Platform (always available)

  1. Top toolbar → Mode toggle → Single Platform

  2. Below: pick a platform (Meta / Google / TikTok / Taboola / Snapchat)

  3. 6 widgets render with that platform's data only

URL pattern reflects the mode (e.g. /analytics?mode=single&platform=meta).

Cross-Channel (gated)

  1. Top toolbar → Mode toggle → Cross-Channel

  2. Below: multi-select platforms to include

  3. 5 narrative blocks render aggregated across selected platforms

If the Cross-Channel option isn't shown in the toggle: ENABLE_CROSS_CHANNEL_ANALYTICS env flag is off for your workspace. Admin needs to enable it at deployment level.

When to use which

Question

Mode

"How is Meta performing this week?"

Single Platform → Meta

"Which Meta ads need pausing?"

Single Platform → Meta → Top/Flop widget

"Should I shift budget from Google to Meta?"

Cross-Channel

"What's our cross-platform ROAS this month?"

Cross-Channel → KPI strip

"What % of spend is going to TikTok?"

Cross-Channel → Channel mix

"Top 10 campaigns across all platforms by ROAS"

Cross-Channel → Top campaigns

Decision rule:

  • Single Platform: tactical (within one platform)

  • Cross-Channel: strategic (allocation, comparison, executive)

What stays the same

Switching modes preserves:

  • Date range

  • Compare-to-previous toggle

  • Target currency

What changes:

  • Widget set (6 single-platform vs 5 cross-channel)

  • Data aggregation (per-platform native vs cross-channel rolled-up with currency conversion)

  • Date range cap (90 days max in Cross-Channel; no hard cap in Single Platform but practical limits apply)

How feature flag works (admin)

ENABLE_CROSS_CHANNEL_ANALYTICS is an env var set at deployment level:

  • true / 1 → mode toggle includes Cross-Channel; cross-channel routes (/api/v1/analytics/unified, /channel-mix, /comparison, /recommendation, /top-campaigns-cross-platform) respond

  • false / unset → toggle hides Cross-Channel option; routes return 404 or 403

Admins enable via env update + service restart (similar to other env-level features in Wevion).

If you need it: ask your admin / DevOps. Most modern workspace deployments have it on.

Data scope per mode

Single Platform scope

  • Native platform metrics (Meta-format CTR / CPA / etc.)

  • Native currency per ad account (no conversion)

  • All accounts for that platform in your visible scope (RBAC applies)

Cross-Channel scope

  • Unified metrics interface (CTR / CPA / etc. defined identically across platforms)

  • target_currency (default workspace currency) — all spend converted via EUR intermediate

  • Only platforms you select in the picker

  • 90-day max date range

Common mistakes

  • Looking for Cross-Channel and it's missing: flag off; ask admin

  • Picking Cross-Channel for single-platform tactical edits: you can't act on rows from cross-channel view — switch to Single Platform or use Ads Manager (PRD-16)

  • Date range > 90 days in Cross-Channel: request rejected; split or use Single Platform mode

  • Currency confusion: in Cross-Channel mode, all values are in target_currency (default workspace currency); in Single Platform mode, values are in each ad account's native currency

Related