NewRaasid is now live - activate it on your store or site in one click.Start free

Monitoring and trust

If measurement stops or shifts, you find out before you build a decision on short data.

Raasid watches the state of each connection, its delivery and its coverage, and tells you early when the data's behaviour changes. Every alert says what happened, why it matters to you, and what to do next.

The problem

The most dangerous measurement problem is the one you don't know happened.

A connection's authorisation can expire, rejected events can climb, order coverage can fall. Keep reading ROAS and CPA without knowing the data is short, and you may move budget to the wrong place.

The financial impact

A short number reads exactly like a weak one.

  • A working campaign cut back

    An authorisation that expired overnight makes a week's results read weaker than the week performed.

  • Two periods compared that cannot be compared

    A period at 81% coverage and one at 54% are not the same basis, and comparing them measures coverage rather than performance.

  • A late fix that does not recover the window

    Reconnecting restores delivery from now on; it does not complete the window that passed.

What Raasid shows

The state, the alert, and every number's source.

  • Connection states

    • Connected and receiving.
    • Later than usual.
    • Rejected events.
    • Expired, or needing a reconnect.
    • The last successful sync, and the window that may be affected.
  • What every alert carries

    • What happened - for instance, order coverage fell from 78% to 42%.
    • Why it matters to you - campaign numbers in that window rest on a smaller slice of your orders.
    • Since when - the time the change began.
    • What to do - check the store or platform connection.
    • What is affected - the platform, the events, the campaigns and the window.
  • Privacy

    Customer identifiers are SHA-256 hashed before they are sent to the platforms, so they are used for matching without being shown as readable text. Privacy and compliance are a shared responsibility, and hashing alone is not the whole of it.

The screen

One alert, start to finish

Coverage falls, the alert fires, the connection is repaired - and the window in between stays marked. The last row is the point: repairing a connection does not retroactively complete the period behind it.

Raasid
Illustrative example

Open the alert from start to finish

Open any time to see its impact and the right action.

Coverage 54% - high alert

Why it matters
Comparing this window with a complete one can mislead the decision.
What to do
Pause the comparison and open the cause of the drop.

An illustrative example

What a number carries before you act on it

Every number opens onto its source, its definition, its period, its attribution model, when it last updated and the coverage it was read on - and from there down to the orders or events behind it. A number that cannot answer those is not ready for a decision.

The decision it enables

You learn when to read a number and when to wait.

  • A connection needing a reconnect - fixed today, not discovered a week later in a low number.
  • A window marked incomplete - left out of the comparison rather than read as performance.
  • A change in tracking behaviour - checked before it turns into a budget decision.

The limitAn alert detects a change in the data or the connection; it does not prove that the campaign's own performance changed. And technical processing controls are not a substitute for your own legal obligations as the data controller.

Start

Don't lean on a number before you know the measurement is working.

Connect your store and one ad channel, then compare what Raasid confirms against what the platform reports over a period you know.