Why did my attributed revenue drop in Northbeam?

The Northbeam help pages give 4 common reasons. The first to rule out: If an order never reaches Northbeam from the store or order feed, it is missing from revenue.

Money · Is money moving the way it should?

Is it broken, or just quiet?

A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Northbeam help pages give, and how to check each one yourself.

What causes it?

  1. If an order never reaches Northbeam from the store or order feed, it is missing from revenue.

    In the Northbeam help: Northbeam may not have received the server-side order. Purchases or Orders Are Missing, read 2026-11-12.

  2. The purchase event on the site and the order record must carry the same order ID, or the two can fail to match.

    In the Northbeam help: firePurchaseEvent and the backend order must use the same identifier. Purchases or Orders Are Missing, read 2026-11-12.

  3. On checkouts outside Shopify, Northbeam needs the purchase event to fire only once for each order, so a setup that fires it more often can cause problems.

    In the Northbeam help: For non-Shopify checkouts, firePurchaseEvent must fire only once per order. Purchases or Orders Are Missing, read 2026-11-12.

  4. Orders placed outside a web checkout, such as subscription renewals or in-store sales, have no browser data to attribute.

    In the Northbeam help: Some orders do not complete through a web checkout and are not expected to have browser pixel data. Purchases or Orders Are Missing, read 2026-11-12.

How do I check it myself?

  1. Pick one missing order and note its order ID, time, checkout domain and payment flow before looking further.

    In the Northbeam help: Start with one example order. Record its exact order ID, timestamp, checkout domain, and payment flow. Purchases or Orders Are Missing, read 2026-11-12.

  2. If your orders reach Northbeam through its API, confirm they went to the intended endpoint.

    In the Northbeam help: Confirm that the request used the intended production or UAT endpoint. Purchases or Orders Are Missing, read 2026-11-12.

How does Northbeam work with Feder?

  • Connect Northbeam to Feder and it joins your Money apps.
  • When you connect Northbeam, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See whether you can trust the numbers in Northbeam, one of your Money apps. Feder only reads. It never changes anything in Northbeam.

Where do these answers come from?

Every cause and check on this page comes from the Northbeam help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.