What the gauge measures
Omega diagnoses a client by running hundreds of individual checks across their marketing and commerce data — ad platforms, analytics, email, search, and the store's revenue source. Each data source you connect unlocks a share of those checks.
The coverage gauge is the percentage of possible diagnostics currently unlocked for this client. It appears as a compact strip on the client's Overview, showing the percentage, how many channels are connected, and how many diagnostics are live. Click the strip to open the full Coverage view, where every source is broken out.
Why coverage matters
More connected data means better signals:
Fewer blind spots. A problem in a channel Omega can't see is a problem nobody flags.
Sharper diagnoses. Signals are cross-checked against more evidence, so confidence goes up.
Better dollar estimates. Revenue-at-risk figures are only as good as the revenue data behind them.
A client at high coverage gets the full strength of the scanning fleet. A client at low coverage still gets signals — just from a narrower slice of reality.
The full-screen notice
If a client is missing the essentials, the Overview cockpit steps aside entirely and shows a full-screen notice instead. This happens when, for example:
No performance data has landed recently, so there's nothing to scan.
Data exists but the feed has gone stale, so Omega holds signals back rather than show numbers built on old data.
Channel data is flowing but no revenue source (such as the store's order system) is connected, so signals can't be anchored to dollars.
The notice explains which situation applies, in plain terms, and lists what to connect — ranked by how many diagnostics each connection would unlock, so you always know the highest-impact fix.
Fixing coverage gaps
Data connections are made in Nova, not in Omega. To close a gap:
Open the client's Overview and click the coverage strip (or read the full-screen notice if one is showing).
Note the recommended connections — the list is ranked by diagnostics unlocked.
Follow the link to Nova and set up the missing integrations there.
Once data starts landing, the gauge updates and the cockpit comes back on its own.
Tip: If you only have time for one fix, connect the revenue source first. Without it, signals can't be tied to dollars and automations stay paused.
Note: A stale feed usually means an upstream sync stopped, not that anything is wrong in Omega. Check the client's sync in Nova, or flag the data team if it doesn't recover.