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

Signal quality

Make sure your store's events reach the platforms with the best data available.

The pixel depends on the browser and can miss part of your events. Raasid sends eligible events from the server, removes duplication, and shows you the delivery state and data completeness for each platform.

The problem

A platform cannot measure or learn from an event that never reached it.

When purchase events, or the identifiers inside them, are short, the platform's ability to match an event to a user and to an ad falls with them. That does not mean sending more events guarantees a higher ROAS - it means giving the platform a better basis than the pixel alone.

The financial impact

The same spend, read wrong.

  • Cost per order reads higher than it is

    If the denominator is pixel events rather than your store's orders, the same spend divides across a smaller count.

  • A campaign stopped on a short result

    Events that never reached the platform are not in its report, and the campaign reads weaker than it performed.

  • Short identifiers cap the match

    An event can be accepted and still go unmatched, because the fields inside it are not enough.

What Raasid shows

What is inside the event, and how far it got.

  • Event match quality

    Completeness for email, phone, external ID and click ID, split into what you can raise from your own store, what Raasid gathers automatically, and what this integration does not carry. A not-collected state is shown as it is.

  • Delivery state per platform

    • Sent.
    • Accepted by the platform.
    • Rejected by the platform, with the reason.
    • The match rate, where the platform returns one.
  • Two separate measures

    Identifier quality and measurement coverage are not folded into one score. A high identifier score with low order coverage means the events that arrived were complete - not that most of your orders arrived.

The screen

The event's path, from your store to the platform's answer

Raasid receives the event, checks its fields, uses an event ID to deduplicate against the pixel where that is supported, sends it over the official integration, and keeps the answer as it came. Where delivery fails it retries on a stated policy.

Raasid
Illustrative example

Follow the event from the store to the platform's reply

Open each stage to see what happens there, and where each party's responsibility ends.

Store event

Purchase, add to cart, checkout

An illustrative example

Work it out on your own store's figures

Illustrative example - change the numbers to your store's

Add up what the platforms report for the same period. It may contain overlap, because more than one can claim the same order.

Store orders: 1,000
  • Captured by the pixel: 650
  • Not seen by the pixel in this example: 350
Pixel coverage in this example
65%
Potential signal gap
350 orders
Value of the orders the pixel did not see, in this example
‭⃁87,500‬

Same spend - cost per order looks 54% higher because the denominator is short.

Cost per order, on store orders
‭⃁50‬
Cost per order, on pixel events
‭⃁76.92‬

Your inputs stay in your browser and are not sent anywhere.

The same spend, but the cost per order reads higher because the order count in the arithmetic is short.

The decision it enables

You learn what arrives, and what you can raise yourself.

  • A repeated rejection with a written reason - a fix, not a guess.
  • A short identifier that is yours - a change at checkout raises it.
  • Low order coverage - the numbers wait rather than get compared.

The limitDelivery is not attribution. A platform accepting an event does not mean it matched it to a user or credited it to an ad, and server-side sending does not guarantee that every event is captured.

Start

See what reaches the platforms, and what needs work.

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