> For the complete documentation index, see [llms.txt](https://fotello.co/university/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fotello.co/university/delivering-listings/listing-activity.md). # Listing Activity See when agents open your gallery and download listing assets. The **Activity** tab shows how agents engage with a delivered listing. It sits beside **Orders** in the listing tab row. Use it to see when an agent opens the gallery or downloads its assets. Activity is available to every merchant. It has no feature flag or plan requirement. ### What Activity records Fotello logs an entry when an agent: * Opens the gallery. * Downloads assets from the gallery. Each entry shows: * Who took the action and when. * Whether they used the delivery link or the client portal. * The downloaded formats and sections, when applicable. Visitors who are not signed in to a shared gallery appear as **Someone**. Fotello does not record visits from your own team. It also excludes the **Share gallery** preview. Repeat gallery opens within a short period appear as one visit. ### Review new activity New entries display a **New** badge. The **Activity** tab label also shows the number of unseen entries. Open the listing, then select **Activity** to review them. ### First download notification When an agent downloads from a listing for the first time, Fotello emails you and the members assigned to that listing. The email links directly to the listing's **Activity** tab. This is a Fotello-sent notification. It is not an editable email template. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://fotello.co/university/delivering-listings/listing-activity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.