Chargement de la page...
Chargement de la page...
METHODOLOGY
This page describes what the engine reads, which way each signal pushes the decision, and what it does not know. It is dated: it changes when the engine changes.
Last updated
WHAT IS READ
Everything comes from the store itself and from the history of messages already sent. No data is bought, no profile is built outside the store.
Its amount, how many items it holds, and where it sits against the store's average cart. The same amount does not mean the same thing in two different stores.
How far checkout went, and how long the cart has been sitting there. A checkout abandonment does not read like a cart left open yesterday.
Whether a first name and a phone number are there, and what kind of domain the address uses. These are hints about how the form was filled in, not enriched data.
Orders already placed with that address, opens and clicks on earlier messages. A customer who never opens counts as much as one who always does.
Disposable address, address that looks generated, repeated abandonments within twenty-four hours, identical carts coming from the same store. These are the signals that silence the engine.
HOW THEY WEIGH
Each signal pushes the verdict one way, and the verdict is their sum. The weights are not published: they are tuned as the engine learns, and a number published today would be wrong tomorrow.
A checkout abandonment, a cart above the store's average, a customer who already ordered, a history of opens and clicks, a complete form, a cart that is still fresh.
A cart far below the average, a cart several days old, a disposable or generated-looking address, a history without a single open, repeated abandonments within the day.
Three cases take the cart out with no discussion: no email address, order already placed, cart expired. No favourable signal buys them back.
A cart is called non-human only when two signals from two independent families agree. Proof of a human, an order placed or a click observed, closes the debate before that. The verdict itself cannot be bought back.
WHAT THE ENGINE DOES NOT KNOW
A method that never says where it stops cannot be checked. Here is what the decision ignores, by construction.
WHAT IS NOT SHOWN
The engine works with an internal value, and it is shown nowhere. The merchant reads a level, excellent, good, weak or very weak, and the reasons behind it. A number invites tuning a threshold nobody can interpret, while the reasons can be checked cart by cart.
WHAT CHANGES
The criteria above describe the current state of the engine, not a final one. The date at the top moves with every change. Decisions already made were made under the method in force that day.
See what gets written when the verdict is yesWHAT IT RESTS ON
A method is checked against documents. Here are the public references this page depends on, and what it takes from each.
Shopify
Admin API webhooks
The event that opens the decision comes from Shopify, not from a tracker dropped on the store. This reference lists the events an app can subscribe to, checkout abandonment among them.
Shopify
The AbandonedCheckout object in the Admin GraphQL API
The fields an abandoned cart exposes bound what the engine can read. What is not there cannot be guessed: that is where the section on what the engine does not know comes from.
Email sender guidelines
Google asks senders to keep the spam complaint rate below 0.3% in Postmaster Tools. That threshold puts a price on one message too many, and turns silence into a measurable decision rather than a pose.
IETF
RFC 8058, one-click unsubscribe
The standard describing the unsubscribe header expected from bulk senders. A recovery message that ignores it gets filed before it is read.
Links checked on
What is left is watching this method run on your own carts.
Start the 14-day trial14-day free trial · No credit card required