> For the complete documentation index, see [llms.txt](https://help.littledata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.littledata.io/advanced/live-event-feed.md). # Live event feed Watch the events Littledata sends to your destinations as they happen, check that each one arrived, and send a test order to confirm your tracking works. {% hint style="info" icon="rectangle-beta" %} The live event feed is still in beta. If you have questions or ideas, don't hesitate to contact our support team at [help@littledata.io](mailto:help.littledata.io)! {% endhint %} The live event feed shows the server-side events Littledata sends from your Shopify store, as they happen. For every event you can see which destinations received it, which did not, and why.
Use it to: * Check that a new destination is receiving events * See whether a specific order reached Google Analytics, Meta, Klaviyo or any other destination * Find out why an event was not sent, or failed to send * Send a test order and watch it arrive {% hint style="info" %} The live event feed is in beta. If something doesn't look right, contact . {% endhint %} ### Open the feed In the Littledata app, click **Live event feed** in the side menu. The feed shows your most recent 600 server-side events, newest first. Older events drop off the end of the feed as new ones arrive, so it's a window on recent activity, not a full history. The badge next to the page title tells you the state of the feed: * **Live**: new events appear at the top as they happen. * **Paused**: new events are being held. See [Reading without interruptions](#reading-without-interruptions). ### What each event shows Each event is a card. The closed card gives you the essentials at a glance: * **What happened**, such as Order placed, Started checkout, Added to cart, Refund issued or Subscription created. Order events also show the order number. * **The details**, such as the products involved and the order or cart value. * **Where it went**: an icon for each destination the event was sent to. If a destination didn't get the event, you'll see a **Failed** or **Not sent** badge instead. * **When it happened**, such as "Just now" or "12 mins ago". Events older than 30 days show the date. A **Test** badge marks events from a [test order](#send-a-test-order). A **Custom** badge marks events you created in the [Event Editor](https://help.littledata.io/event-editor/overview). Click a card to open it. The open card adds: * **A table of destinations** with the status of each one and, where needed, a short description of what happened. * **An order summary** for order events: total value, tax, shipping, coupon, order affiliation and the products in the order, with a link to view the order in your Shopify admin. * **Extra context**, such as the sales channel, the Shopify market and whether the customer is new or returning. * **Edit in Event editor** for custom events, so you can adjust the event without leaving the feed. ### Destination statuses Each destination in an open card has one of four statuses. | Status | What it means | | -------------- | ------------------------------------------------------------------------------------- | | **Sent** | The destination received the event. | | **Processing** | The event is on its way. This usually takes a few seconds. | | **Not sent** | Littledata chose not to send the event to this destination. The description says why. | | **Failed** | Littledata tried to send the event but the destination didn't accept it. |
**Not sent** is often expected. Common reasons include: * The order value is $0.00 or less (this applies only if the destination is set to [exclude zero-value orders](https://help.littledata.io/advanced/developer/data-pipeline-settings#data-customization-settings)). * The visitor couldn't be identified, so the destination can't link the event to a person. * The event didn't match the conditions you set in the Event Editor. * The destination doesn't receive this type of event. **Failed** usually means something in the destination's setup needs attention. Common reasons include: * Littledata lost access to the connected account (e.g your Google account password was changed). Reconnect it from the destination's settings. * The connected account is missing a permission the destination needs. * The destination didn't accept your tracking ID or conversion action. Check it in your destination settings. If a Failed description doesn't tell you enough, contact . ### Find a specific event The toolbar at the top of the feed helps you narrow down what you see. * **Tabs**: switch between **All events**, **Orders** only, or **Custom** events from the Event Editor. * **Search**: type an order number, product name or event name. * **Filter**: narrow by **Status** (Sent, Processing or Failed), **Destination** or **Event type**. The Event type filter also has a **Test order** option. * **Sort**: order the feed by date (newest or oldest first) or by event name. While you're searching or filtering, new events are held so the results don't change under you. Clear the search and filters to go back to the live feed. ### Reading without interruptions The feed stops adding new events to the list while you're looking at something, so cards don't move around while you read. This happens when you: * Scroll down the feed * Open a card * Search or filter * Click **Pause** The feed badge shows **Paused** and a **New events** pill appears over the feed. Click the pill to add the held events and jump back to the top. If you clicked **Pause**, click **Resume** or the pill to continue. Events keep arriving in the background while the feed is paused. Nothing is lost. ### Send a test order A test order is the quickest way to check that your destinations are receiving data. Littledata creates an order for you and sends it through the same path as a real order, so you can watch it arrive. {% stepper %} {% step %} #### Click Send test order Click **Send test order** at the top of the feed. You'll see a confirmation listing the destinations the test order will go to. Click **Send test**. {% endstep %} {% step %} #### Watch it arrive A card shows the test order's number and a row for each destination. Each row changes from **Waiting** to **Received** as the destination confirms the event. This usually takes under a minute. {% endstep %} {% step %} #### Check the result When every destination has answered, a banner confirms which destinations received the test order. The test order stays in the feed as a normal card, marked with a **Test** badge, so you can open it and see the details each destination received. {% endstep %} {% endstepper %} If the test order hasn't appeared after three minutes, the feed lets you know. Click **Check setup** to review your destinations, or **Contact support**. A few things to know about test orders: * The order number starts with **#LD-TEST-ORDER**, and the order is tagged `littledata-test`. * The order has a value of $0.00. {% hint style="info" %} If a destination is set to exclude [zero-value orders](https://help.littledata.io/advanced/developer/data-pipeline-settings#data-customization-settings), the test order shows as **Not sent** for that destination, with the reason "The order value is $0.00 or less." That is expected and doesn't mean your tracking is broken. {% endhint %} * Along with the order, Littledata sends a matching **Added to cart** event, so you may see two test cards in the feed. Destinations that don't receive orders, such as Attentive, receive this cart event instead. * The order is not created in Shopify, so it won't appear in your Shopify admin or affect your Shopify sales reports. If you haven't connected a destination yet, the feed asks you to connect one first. The **Send test order** button appears once at least one destination is connected. ### Related articles * [How server-side tracking works](https://help.littledata.io/get-started/how-server-side-tracking-works) * [Tracking plans and event schemas](https://help.littledata.io/advanced/developer/what-does-littledata-track) * [Event Editor overview](https://help.littledata.io/event-editor/overview) * [Exclude staff and test orders](https://help.littledata.io/event-editor/common-setups/exclude-staff-and-test-orders)