Top toolbar mode toggle. Single Platform always available; Cross-Channel gated by ENABLE_CROSS_CHANNEL_ANALYTICS env flag (shown but disabled/greyed when off). Pick mode by question.

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). When the flag is off, the Cross-Channel option is still shown but disabled / greyed out (opacity-50, non-clickable, with an explanatory tooltip) — it is not hidden. Ask your admin to enable it.

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 / Outbrain)
3. A configurable widget grid renders with that platform's data only (up to 19 widgets available from the widget library)

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 is greyed out / not clickable 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

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 (configurable single-platform grid, up to 19 widgets, vs 5 cross-channel narrative blocks)
• 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 → Cross-Channel toggle is enabled; cross-channel routes (/api/v1/analytics/unified, /channel-mix, /comparison, /recommendation, /top-campaigns-cross-platform) respond
• not true (false / unset) → toggle shows Cross-Channel greyed-out/disabled; routes return 404 (empty payload)

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

FAQ

Where is the mode toggle in Wevion Analytics?

The mode toggle sits in the top toolbar of /analytics and switches between Single Platform and Cross-Channel. Single Platform is always available; once selected, you pick a platform (Meta, Google, TikTok, Taboola, Snapchat, or Outbrain) and a configurable widget grid (up to 19 widgets) renders with that platform's data. The URL reflects the mode, for example /analytics?mode=single&platform=meta.

Why is the Cross-Channel option greyed out in my toggle?

The Cross-Channel option is disabled (greyed out with a tooltip, not hidden) because the ENABLE_CROSS_CHANNEL_ANALYTICS env flag is off for your workspace. This is an admin-level, deployment setting, so an admin or DevOps must enable it via an env update and service restart. When it's off, cross-channel routes like /api/v1/analytics/unified and /channel-mix return 404 with an empty payload.

What is preserved when I switch modes in Wevion Analytics?

Switching modes preserves your date range, the compare-to-previous toggle, and the target currency. What changes is the widget set (a configurable single-platform grid of up to 19 widgets versus 5 cross-channel blocks), the data aggregation (per-platform native versus rolled-up with currency conversion), and the date-range cap — Cross-Channel enforces a 90-day maximum (MAX_DATE_RANGE_DAYS=90) while Single Platform has no hard cap.

Which mode should I use for budget allocation across platforms?

Use Cross-Channel mode for budget allocation, comparison, and executive review — for example deciding whether to shift budget from Google to Meta. Use Single Platform for tactical questions within one platform, such as how Meta is performing this week or which Meta ads need pausing. The rule is simple: Single Platform is tactical, Cross-Channel is strategic.

Why does spend show different currencies between the two modes?

In Cross-Channel mode all values appear in the target_currency (your default workspace currency), with spend converted via an EUR intermediate. In Single Platform mode, values stay in each ad account's native currency with no conversion. This difference is intentional, so don't treat the two modes' spend figures as directly interchangeable without accounting for the conversion.

Related articles

• Analytics overview — Single Platform vs Cross-Channel
• Cross-Channel overview — 5 narrative blocks
• Single Platform — widget grid explained