# Listening to events from Beacon Bar

Many a times, you may want to execute a specific action based on user's activity within beacon bar or capture the event data for your analytics. To facilitate this, beacon emits events for every action user does within beacon bar, you can capture them and write your own logic on top of that.

{% content-ref url="/pages/S1aBY1gTvaQCLJEIVTAQ" %}
[Adding event listeners in Beacon](/listening-to-events-from-beacon-bar/adding-event-listeners-in-beacon.md)
{% endcontent-ref %}

{% content-ref url="/pages/gt24XR9A8l3F4ng0UfaY" %}
[Removing event listeners in Beacon](/listening-to-events-from-beacon-bar/removing-event-listeners-in-beacon.md)
{% endcontent-ref %}

{% content-ref url="/pages/D6NzR0d99z5q2y1ZHa7w" %}
[React Example for Event Listeners in Beacon](/listening-to-events-from-beacon-bar/react-example-for-event-listeners-in-beacon.md)
{% endcontent-ref %}

{% content-ref url="/pages/GSMC9oAMXBpEl28zlUZ3" %}
[List of events emitted by Beacon Bar](/list-of-events-emitted-by-beacon-bar.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://api.beacon.li/listening-to-events-from-beacon-bar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.