> For the complete documentation index, see [llms.txt](https://community.commandersact.com/customer-success/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/customer-success/inspiration/server-side/tracking-events-and-interactions.md).

# Tracking events and interactions

To remedy this, in this section we explain how to unify your event reporting.

You will learn how to configure Firebase Analytics for your application ecosystems and how to use webhooks to synchronise your server interactions in real time with your third-party tools.

#### **Benefits:**

* **True omnichannel:** With Server-Side, you can reconcile Firebase in-app interactions with your web journeys for a 360° view of your customers.
* **Maximum flexibility**: Using webhooks allows you to push your business events (validated purchases, qualified leads) to any internal tool or API without adding heavy SDKs.
* **Reliability of critical data**: You secure the reporting of the most important interactions by triggering them directly from your server, eliminating the risk of loss due to customer disconnections.


---

# 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://community.commandersact.com/customer-success/inspiration/server-side/tracking-events-and-interactions.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.