> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/admin-portal/event-log.md). # Event log See a log of all events associated with a single subscription or customer's overall actions on the customer details page. The event log on a subscription's page allows you to easily keep track of all actions associated with a customer’s subscription.
Gif showing the event log in a subscription. The event log appears when you switch to the "Orders and event data" tab. It shows events such as "Successful billing attempt" and is grouped under the date and shows the time stamp to the right of the event.
There are four possible “actors” that can make edits to a subscription: 1. **Smartrr** – Automatic process by Smartrr 2. **Admin** – Merchant admin 3. **Script** – Any merchant-configured scripts in subscription program 4. **API** – External partner (Integrations, migrations, etc.) The following actions are currently recorded in the events timeline: * Subscription Order Processed * Frequency Changed * Subscription Paused * Subscription Cancelled * Subscription Reactivated * Subscription Skipped * Subscription Unskipped * Item Price Changed * Shipping Price Changed * Discount Successful * Discount Failed * Discount Removed * Address Changed * Item Added-On * Item Removed * Sequential Subscription Updated * Change Order Date * Successful Billing Attempt * Failed Billing Attempt * Undo Gift * Swap Line Item (From Member Portal) * Update Line Item * Create Transaction The event log also records notifications sent and manual actions made to the subscription (eg. "customer swapped variant x for variant y", or "Carlene () updated product x's quantity to 1 and price to $x") by the customer in the Smartrr account portal or staff with admin privileges in the app.
The comment box is found below the "Event log" heading. You can add a comment to the event log. For example: you decided to add a discount code to the subscription, you could leave a comment to say what the discount was added for.
--- # 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://help.smartrr.com/docs/support/admin-portal/event-log.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.