> ## Documentation Index > Fetch the complete documentation index at: https://www.referly.so/docs/llms.txt > Use this file to discover all available pages before exploring further. # Live activity > Watch events reach Referly Atlas and your ad platforms in real time: delivery statuses, event payloads and platform responses, filters by status, event, conversion and destination, and how to use the feed to debug your tracking. **Live activity** is the running log of everything Referly Atlas receives and everything it sends on. Each page view, add to cart, order and conversion appears as it reaches Atlas, followed by one row per destination it was delivered to, with the platform's answer. Open it from **Live activity** in the left sidebar. ![Live activity page with the Live indicator, Pause button, Filter dropdown and a table of deliveries with Failed, Deduped, Skipped and Filtered statuses](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/reports/live-activity--page.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=8be046b40c1898193da0f4bda6bc09c5) ## What the feed shows The subtitle reads "Events from" your store "as they reach Atlas and your destinations." (or "from every store of this business" with **All stores** selected). A green dot and **Live** in the header mean the feed is refreshing: Atlas checks for new rows every 3 seconds while the tab is visible, and slows down to every 15 seconds when nothing changes. Press **Pause** to freeze the list while you read it (the label turns to **Paused**) and **Resume** to catch up. Newest rows are at the top. The columns: | Column | What it shows | | - | - | | **Time** | When Atlas received the event, the order or conversion happened, or the destination answered, in your store's time zone. | | **Event** | The event name, with a line under it saying whether the row is an **Event**, an **Order** or a **Conversion**. Conversions are shown in green. | | **Status** | **Received** for rows that reached Atlas; for delivery rows, the destination's answer. | | **Destination** | Where the event was sent. Rows marked **Atlas** are the events as they arrived, before any delivery. | | **Store** | The store the event belongs to (All stores only). | | **Details** | Source, page, value, country and consent: for example the UTM source and landing page of a page view, the value of an order, or "no consent" when the visitor declined marketing. | Delivery rows only appear for stores that are **Running** or **Awaiting data**. A paused store records events but sends nothing, and orders placed while [test mode](/docs/help-center/atlas/settings/store-settings.md#testing) is on are recorded as **Test** and never sent. [Pixels and destinations](/docs/help-center/atlas/pixels.md) explains which events each pixel receives. ## Delivery statuses Every row carries a status pill. Hover the **Status** header for the one-line meaning of each: | Pill | Meaning | | - | - | | **Received** | Events that reached Atlas | | **Sent** | Accepted by the platform | | **Failed** | Rejected or out of retries | | **Retrying** | Trying again shortly | | **Queued** | Waiting to be sent | | **Filtered** | Stopped by an event filter | | **Skipped** | No consent or nothing to match | | **Deduped** | Already sent | | **Test passed** or **Test failed** | The result of a test event sent from a pixel | ![Rows of the live feed showing the Failed, Deduped, Skipped and Filtered status pills with their reasons in the Details column](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/reports/live-activity--status-pills.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=152b0f73e4a17d2ac9898fb725e3ddd6) For **Filtered**, **Skipped** and **Deduped** rows the **Details** column says why: the rule that stopped it, "Visitor declined marketing consent", "Consent unknown in a consent-required region", "No identifiers the platform can match" or "Already sent within 48 hours". A failed delivery is retried up to 8 times, with the wait growing from 10 seconds, before it is marked **Failed**. The full list, with what to do about each, is in [Delivery statuses](/docs/help-center/atlas/statuses.md#delivery-statuses). ## Open an event Hover a row and click the code icon at its right end. What opens depends on the row: * **Event payload** for an incoming event: what your site or app sent to Atlas. * **Platform response** for a delivery: the status, the HTTP status, how long the call took, the attempt number, the platform's error message, the event filter rule that stopped it (if any), the event key, the payload Atlas sent and the platform's raw response. * **Order** or **Conversion** for ledger rows: the record Atlas stored. ![Platform response popover of a failed delivery showing the status, HTTP status, error message, event key and payload summary](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/reports/live-activity--platform-response.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=a07212fdcf47874a1e3a2bd9be2c4ab5) The error message in **Platform response** is the platform's own wording, so it is the first thing to search for in that platform's help when a delivery fails. ## Filter the feed **Filter** (top right) opens a menu with four categories: **Status**, **Events**, **Conversions** and **Destination**. Each option shows how many rows matched in the last 24 hours, given the other filters you have on. Hold Shift and click to select more than one option. ![Filter menu of the live feed with Status, Events, Conversions and Destination](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/reports/live-activity--filters.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=0fba51e0b3cd419ed16f05963a3e84de) An active filter becomes a chip above the table, such as **Status is Sent**. Click the chip to change its options or its × to remove it, and **Clear all** to start over. You can also hover an **Event**, **Status** or **Destination** cell and use its **Filter by** button to filter on that value in one click. ![Live activity feed paused and filtered to Status is Sent, with the filter chip and Clear all](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/reports/live-activity--filter-chip.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=6decd7a443978e9abcfe9ba69fb7c05f) ## Load older events The feed loads 50 rows at a time and keeps up to 500 on screen; as new rows arrive, the oldest drop off. Press **Load older** at the bottom to bring in the next 50. For anything further back, narrow the feed with a filter, or use [Reporting](/docs/help-center/atlas/reports/reporting.md) for totals. Atlas keeps delivery rows for 90 days. Events and sessions are kept for the event history your plan includes; see [Billing](/docs/help-center/atlas/settings/billing.md#plans-and-prices). ## Use it to debug Live activity answers most "is it working?" questions in a minute. > **Is my site sending events at all?** > > Open your site in another tab and browse to a product page. A page view row with **Atlas** as the destination should appear within seconds. If nothing shows, the tracking script or app embed is not live: run **Test connection** in Store settings and follow [Test the connection](/docs/help-center/atlas/setup/test-connection.md). > **Is a platform accepting them?** > > Filter **Destination** to the platform and **Status** to **Failed**, then open **Platform response** on a row and read the error. It is the platform's own message, so [Troubleshooting](/docs/help-center/atlas/troubleshooting.md#a-pixel-shows-error) lists the common ones and what to change. > **Why was an event Skipped, Filtered or Deduped?** > > The reason is in the **Details** column. **Skipped** means the visitor had no marketing consent or the event carried nothing the platform can match; **Filtered** names the [event filter](/docs/help-center/atlas/event-filters.md) rule; **Deduped** means the same event already went to that pixel within 48 hours. See [Consent and privacy](/docs/help-center/atlas/pixels/consent-and-privacy.md) and [Avoid double counting](/docs/help-center/atlas/pixels/avoid-double-counting.md). > **Did my test event go through?** > > **Send test event** from a pixel's menu on [Pixels and destinations](/docs/help-center/atlas/pixels.md#send-a-test-event) adds a row with a **Test passed** or **Test failed** pill. Filter **Status** to **Test** to see only those. ## Related > **[Delivery statuses](/docs/help-center/atlas/statuses.md#delivery-statuses)** > > Every status pill and what to do about it. > **[Event filters](/docs/help-center/atlas/event-filters.md)** > > Rules that stop events before they reach a destination. > **[Troubleshooting](/docs/help-center/atlas/troubleshooting.md)** > > No events, failed deliveries and numbers that differ from Ads Manager. > **[Pixels and destinations](/docs/help-center/atlas/pixels.md)** > > Add, test, edit and detach the pixels your events go to. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.