Track completed exports from an Astro server endpoint
A concrete Astro endpoint pattern for recording completed exports in Butters, with server-only credentials, stable user IDs, and a clear failure policy.
Signups, billing, orders and the numbers that move money. 6 articles.
A concrete Astro endpoint pattern for recording completed exports in Butters, with server-only credentials, stable user IDs, and a clear failure policy.
A practical Next.js App Router pattern for sending one paid-order event to Butters after a verified payment webhook, with duplicate-delivery and failure handling.
Avoid lost updates when workers increment the same insight card, and learn why atomic arithmetic doesn't solve duplicate delivery or reconciliation.
Add a native Astro feedback component, clean it up during page transitions, and choose which page and user context to attach to messages in your Butters feed.
Some numbers don't need a chart or a BI tool. They need to be somewhere you'll see them. Here is how insight cards work in Butters, how to keep them current from cron, and how to tell whether a number belongs on a card, in the feed, or in an analytics tool.
The temptation is to track everything. The useful move is to track the handful of things that happen to your revenue: signups, payments, failures, cancellations. Here is how to pick them, name them, and wire them in without making a mess.