Skip to main content
Every time the engine looks at a visitor and reaches a decision, that is a moment, and it is kept: when, on which page, why the moment surfaced, what the engine decided and at what tier, the sentence it composed, whether the sentence was shown, and what the visitor did in the ten and thirty minutes after. Moments is the list; Reasons is the same list grouped by why the visitor stalled. The shop-owner walkthroughs are Moments and Reasons; this page is the view for your website.

​
Moments

GET /v1/sdk/{id}/moments returns the newest first. limit (up to 200, default 50), before (a timestamp, for the next page; the answer’s next is the value to pass), since, and verdict (engage, wait, quiet) narrow it. GET /v1/sdk/{id}/moments/{moment_id} returns one moment with the snapshot the engine saw. Each row carries:
  • when and where: the time and the page path.
  • the reason: the gate rule that surfaced the moment, in the engine’s own words (“sitting on the cart (48s, idle 31s)”).
  • the verdict: engage, wait or quiet, and for an engage the mode and tier.
  • the sentence: what was composed from the facts sheet, or what would have been in watch mode.
  • delivery: whether a card was placed, shown, clicked or dismissed, or withheld (held back, watch mode, visitor left).
  • the outcome: what the visitor did next, from the ten- and thirty-minute checks: converted, kept researching, lingered, left soon after.
The console filters the list three ways: we spoke, we waited, we stayed quiet. The first is where credited orders come from; the third is worth reading in the first week because it shows the visitors the engine chose to leave alone and why.

​
Reasons

GET /v1/sdk/{id}/reasons groups the same moments by why the visitor stalled. A moment’s reason comes from the visitor’s record when there is one (a discount they had that stopped working, a hunt for a code, a hesitation the engine classified as shipping, fit, price, an error, delivery, returns, trust or comparing), and otherwise from the gate rule that fired: stuck in a form, discount code not taking, sitting on the cart, choosing a size or colour, form would not go through, something not responding, going back and forth, hunting on the page, racing through help, comparing options, on a page people leave from, deciding on one thing. Each group carries the count, how many were spoken to and how many were left silent, the share who left soon after and the share who converted (shown once the group has thirty moments; thin until then), the four pages it happens on most, and a few example moments.

​
What to do with them

Reasons is the shortest route to a better facts sheet. “Sitting on the cart” at the top means the shipping line and fillers are the facts to check. “Choosing a size or colour” means size notes for the products in top_pages. “Stuck in a form” on a non-store site means the form’s own validation is failing people, which the engine can only rescue if the page reports its validation messages. Moments is where you check the sentences themselves: read twenty engages in watch mode before turning shadow off, and read the “stayed quiet” list once, to confirm the engine is leaving the right people alone.