> For the complete documentation index, see [llms.txt](https://www.feinfra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.feinfra.com/technical-functional-requirements/user-experience-tracking.md).

# User Experience Tracking

## **Todo**

* Usage Metrics
* Talk w/ Marketing and PM about tooling to keep track of metrics&#x20;
* Usage of app: Mixpanel, Fullstory Errors,&#x20;
* Logging: Datadog, Sentry&#x20;
* Marketing: Google Ads, FB Pixel&#x20;
* Feature Flagging: LaunchDarkly - feature flagging conversion tracking or segments

### **Feature Flagging**

* LaunchDarkly&#x20;
* Are we turning on features slowly? One by one? For specific segments? By type of user?&#x20;
* Blue/Green Deploys&#x20;
* Rolling back deploys strategy?&#x20;
* Horrible error?&#x20;
* Automatically track errors and roll back?&#x20;
* A/B testing using feature flags, collect metrics on what does better

### Ad Platform Integration


---

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

```
GET https://www.feinfra.com/technical-functional-requirements/user-experience-tracking.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.
