Skip to main content

Understanding Coverage

The Coverage page shows which of a client's data sources are connected to Omega — and what each missing connection would unlock.

Written by Schae Lilley

Why coverage matters

Omega can only diagnose what it can see. A client with every data source connected gets the full depth of analysis; a client with gaps gets a narrower read, and some checks can't run at all. Coverage makes that visible per client, so you know exactly what you're working with — and what to fix.

Open Coverage in the left rail of the Workflow product, and pick a client in the client picker.

Reading the grid

The heart of the page is the client's data-source list, with a score like 6/9 connected — the count of applicable sources currently feeding data. Sources span the categories you'd expect:

  • Paid channels — Meta Ads, Google Search, Performance Max / Shopping, TikTok Ads, Programmatic / DSP

  • Email and lifecycle — Klaviyo, Attentive, and similar platforms

  • Affiliate — Impact, CJ, and similar networks

  • Commerce — the client's order system (Shopify or equivalent), which anchors signals to real revenue

  • Retail — Amazon / retail data

  • Measurement — media mix modeling (MMM), when a model exists for the client

Each row shows one of three states:

  • ✓ connected — data is flowing and the diagnostics it powers are active.

  • + not connected — a gap. The row shows what connecting it unlocks (for example, "unlocks +4 diagnostics"), so you can see which gap is costing the most.

  • – marked N/A — someone confirmed this source genuinely doesn't apply to the client, so it's excluded from the score.

What "connected" actually means

Connected means the source's data is landing in the client's pipeline and Omega's checks for that channel are live. It isn't a login or a bookmark — it's data flowing nightly. The status updates automatically: once a new source's data starts arriving, the row flips to connected on its own.

Fixing a gap

Connections happen through nova. For most ad and email platforms, expand an unconnected row to see exactly what to wire up in nova for that source.

A few sources aren't self-serve:

  • The order system and Amazon are set up by the data engineering team — the row explains what to request.

  • MMM appears once a media mix model has been built for the client; it isn't something you connect yourself.

Tip: Prioritize the order system above everything. Without a revenue anchor, signals can't be tied to dollars and scanning for the client stays paused — it gates far more than any single channel.

Note: If a source truly doesn't apply to the client, don't leave it sitting as a gap — mark it N/A so the score reflects reality. See "Marking Categories Not Applicable."

Did this answer your question?