Skip to main content

Setting Metrics and Goals

The Metrics page is where you tell Omega what matters for a client — targets, goals, and priority weights that drive how signals are scored and ranked. Tune it first when onboarding.

Written by Schae Lilley

Why this comes first

Everything Omega surfaces for a client — which signals rise to the top, how urgent they look, what the agents optimize toward — flows from this page. Five minutes here when a client onboards pays back every week after.

Open Metrics in the left rail of the Workflow product, and pick the client in the client picker — everything on this page is saved per client.

Targets

The Targets card holds the client's numeric targets, fed to Scan and every agent that works on the client — results are judged against the client's real numbers, not generic benchmarks. Edit a value and save.

The metrics table

Under Available metrics, each row is a metric with three controls:

  1. KPI tiles — toggle whether the metric shows in the KPI band on Overview and the compact live ticker. Visibility is saved in your browser — your view of the client, not your teammates'.

  2. Goal — the target value for that metric (for example, $300k revenue or 2.50% conversion rate). Once a goal is set, a period selector appears beside it — see below.

  3. Scan weight — how much priority signals about this metric get. Four levels:

    • Muted — surfaces only if severe

    • Normal — default priority

    • Elevated — surfaces sooner

    • Critical — surfaces on small moves

Weights are how you encode "for this client, CAC is everything."

Note: Only two metrics can be Critical at a time. That's a guardrail, not a limitation — if everything is critical, nothing is.

You'll only see metrics that fit the client's business model — an ecommerce brand gets revenue and ROAS-style metrics, a B2B client gets pipeline metrics — so you're never setting goals on numbers the client's data can't carry.

Goals cover a period

Every goal applies to a period: per month by default, per quarter, or a custom window with dates, for goals tied to a campaign rather than the calendar.

Volume goals (like revenue or leads) pro-rate to the window you're viewing — a 7-day view compares against a week's worth of a monthly goal, so "% of goal" always means "% of goal pace." Rate goals apply as-is; a custom-window goal counts only while your view overlaps it.

Define what a metric means

Under each metric's name you can write the client's own definition — say, that Revenue means gross sales less returns. It shows on hover wherever the metric appears, and agents read it too, so analyses describe the number in the client's terms.

An opt-in revenue basis on the Revenue row goes further, changing the number itself: Net sales (default), Gross sales, or Gross sales − returns. Revenue across Omega follows the choice.

Goals and context in plain words

Two free-text cards round out the setup:

  • Goals for the agent — priorities that don't fit a single number: "Q3 is brand awareness over efficiency." Agents read this verbatim and frame their work against it.

  • Context & scope for the agent — operating realities: what you do and don't manage, planned promotions, channels run by another agency. This keeps agents from generating work for things out of scope.

Tip: Revisit this page whenever the client's strategy shifts — a new quarter's goal or a channel changing hands should be reflected here the same week, or the signal ranking will lag reality.

Did this answer your question?