> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/setting-up-limio-for-salesforce/subscriber-timeline/activity-timeline.md).

# Showing the Activity Timeline of Events

Limio for Salesforce can chronologically display past events related to a subscription. Details are shown according to specific actions and their sequence.

To access the feature in Salesforce Flows, click the down arrow next to the relevant subscription, then select "View Events."<br>

<figure><img src="/files/8pDgRjP0uOHiSk1Y2YAT" alt=""><figcaption></figcaption></figure>

You will then see a Timeline with the following functionality.

For each action such as a new order, switch, save, cancel, change payment, change address, or renewal, display the following information:

* **Action Type**: Specify what the action is.
* **Date**: Indicate when the action occurred.
* **Product**: Identify the product involved.
* **Offer**: Mention any associated offer.
* **Amount**: State the amount involved.
* **Start Date**: Provide the start date of the action.
* **End Date**: Provide the end date, if applicable.
* **Term**: Specify the term or duration.
* **Source**: Indicate the source of the action.
  * If the source is LFS, specify the user involved.

To enhance readability and user experience, users can toggle details on and off.

The events you will see are detailed on [How Limio Events Update Zuora](/integrations/keeping-zuora-and-limio-in-sync/how-limio-events-updates-zuora-for-commerce.md). You can find some detailed examples below:

<figure><img src="/files/rRP1Mebb1NPVEz4Yd5MH" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/lRldvodkqX2TxpObZ6yW" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/XRw6zo2O4qMGUGUpkDlL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ecpWktC2w7gNCh8fVM5K" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/zvqr45zH2j17PSjxGGi1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/A41ILXXUOerui47wKeVl" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/wH1GTRcgZKgB11wlpSPx" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/WewZHwfHFI5HWmGqp18w" alt=""><figcaption></figcaption></figure>

### Timestamps

In LFS version **12.19** or higher, timestamps are synchronised with the timezone and locale settings of the current Salesforce user, ensuring accurate and localised time representation and a more contextually relevant agent experience.<br>

<figure><img src="/files/lbNlWywX5NdxAsZadlCU" alt=""><figcaption></figcaption></figure>

### Custom Events

From release 112 onwards, it is possible to send custom events to Limio via API so that they are shown in Limio for Salesforce. The payload to send would look like:

```json
{
  "forSubscription": {
    "name": "string"
  },
  "name": "Order Received",
  "type": "order.event_received",
  "source": "webhook",
  "fields": [
    {
      "label": "Offer Name",
      "type": "string",
      "value": "My offer",
      "additionalInfo": "GBP"
    }
  ]
}
```

Go to <https://docs.limio.com/api/objects-api/subscriptions>for more details.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/integrations/setting-up-limio-for-salesforce/subscriber-timeline/activity-timeline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.