Signals for the things that quietly break

Scheduled checks and webhooks watch for inactive accounts, rejected ads, sharp CPM or CPA moves, weak spend, broken URLs, disconnected sources and falling orders.

Get early access All featuresHow it works
app.roasfinity.com/measure/signals
Signals screen in the ROASfinity app, with test data

Floating cards and figures are examples on sample data, not a customer account.

1The proof

Every number comes with its receipt.

Sample data, fictional brand. This is how Signals shows a figure: the value, where it came from, the formula behind it and when it was last updated.

SignalsSample data, fictional brand
HighCPM +38% vs 7 days agoSource and formulaMeta, 3 ad setsUpdatedsee source
MediumAd rejectedSource and formulaHealth claim policyUpdatedsee source
LowGA4 connector lateSource and formulaLast success 7 h agoUpdatedsee source

Rule: every number shows its source, formula and update time. A missing source reads "not measured", never 0.

2Part of Measure

Signals: what it does.

One of four areas of the product, sharing the same client record, roles and log.

01

Each signal links to evidence

Open the signal and see the metric, the comparison and the time it was measured.

Signals in the app, with test data
02

Connector health included

Last success, lag, error and rate limit are visible per connector, so stale data is never mistaken for a real drop.

03

Routed to tasks

Turn a signal into a task with an owner and a deadline in one step.

Works with

4 platforms, read-only first

Connections start read-only. Writing is switched on per account, only after you grant the rights.

At a glance

Stated up front

things it does
3
steps start to finish
4
platform connections
4
limits stated
2
3The data path

How the data moves. Source to screen.

Lines draw as you scroll. Platforms on the left are read-only first, Signals sits on the one client record, and each output keeps its receipt.

Meta AdsBuilt
Google AdsBuilt
ShopifyBuilt
Google Analytics 4Built
ROASfinitySignals
Each signal links to evidence
Connector health included
Routed to tasks

Sources are read first, the numbers are stored once per client, and every output shows its source, formula and update time.

How the work moves in Measure

The same four moves apply to every module in this area.

  1. 1 ReadConnected sourcesOrders, spend and results come from the store and ad platforms, read-only first.
  2. 2 ComputeFixed formulasMER, CAC and the rest are defined once, in the open, the same for every client.
  3. 3 ShowSource on every numberEach figure carries its source, formula and the time it was updated.
  4. 4 FlagNot measured, never zeroWhen data is missing the screen says so, instead of showing a made-up value.
4The routine

How it works, step by step.

From first connection to the number a client sees.

  1. 1

    Watch

    Scheduled checks and webhooks run per client and per account.

    Signals app screen with test data
    Step 1Watchexample
  2. 2

    Compare

    Values are compared to history with a minimum sample.

    Step 2Compareexample
  3. 3

    Notify

    People with the right role get the signal with its evidence.

    Signals app screen with test data
    Step 3Notifyexample
  4. 4

    Resolve

    Close it, or open a task or a proposed change.

    Step 4Resolveexample
5In use

Built for businesses like these. Example scenes.

Photos are stock images that show the kind of business this is built for. They are examples, not customers.

Examplethe weekly reporting desk
Examplean online shop
Examplea creator studio
Examplea small team

Stock photos and example labels, not customers.

6In practice

Common mistakes, and a short checklist.

General practice for this kind of work, not a claim about any one tool.

Mistake

Too many alerts to act on

When every small move sends a message, people stop reading them. Set thresholds from the changes that would actually alter a decision.

Mistake

An alert with no owner

An alert that lands in a shared inbox often gets no action. Name who reviews each signal and what that person does first.

Mistake

Reacting to a one-day spike

One unusual day is often a tracking gap, a holiday or a one-off event. Check the data source and the trend over several days before you move budget or change a page.

A short checklist

Your ticks stay in this browser only.

7Honest limits

What it will not claim, and what it works with.

What it will not claim

  • A signal says something changed, not why. The explanation is a separate step.
  • Webhook coverage differs by platform, so some checks rely on periodic pulls.

Works with

Connections are read-only first and go live only after the platform access is approved.

Meta AdsBuiltGoogle AdsBuiltShopifyBuiltGoogle Analytics 4Built

Built: the connector exists in the product and goes live per account once access is granted. Planned: not built yet.

Used instead of

No single tool replaces this module; it connects work that is usually split across several.

9Guides

Learn more. Short guides.

Short guides on the numbers and routines behind this module.

GuideA UTM standard for ad accounts that stay consistentUTM tags are only as useful as they are consistent. One standard, applied by tooling instead of memory, keeps reports readable.5 min readGuideWhy your MER is wrong: currencies, time zones and refundsMost disagreements between a store and its ad reports are not strategy problems. They are mismatches in how two data sets were cut.5 min read
10FAQ

Questions about signals.

How is a stale connector shown?

As its own signal with the last success and the lag, so a missing data feed is not read as a performance drop.

Can signals pause campaigns?

Only through narrow rules with a minimum sample, a cooldown and a kill switch, and every action is logged.

Who gets notified?

People whose role covers that client. Client approvers see only their own brand.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Get early access How we plan to price it