> For the complete documentation index, see [llms.txt](https://support.soberpeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.soberpeer.com/enterprise/client-triggers.md).
# Client Triggers
Client Triggers can be viewed from the client’s profile. Triggers are added by the client using the mobile app. The counter for each trigger is automatically as the client ventures into the tagged area.
{% hint style="info" %}
Some clients are very sensitive about the idea of sharing their location, so keep in mind that it is not mandatory to use in order to access the rest of Sober Peer's tools.
{% endhint %}
### Viewing Client Triggers
1. Navigate to the specific client using the search function located on the Dashboard > App Subscribers > Explore App Subscribers section.
2. Search the client’s first or last name, and then pick from the drop down list.
3. Once the page refreshes, the Trigger’s Map will appear on the left hand side of the page. You can navigate around the map using the +/- buttons on the screen or by holding CTRL and scrolling in/out on your mouse.
4. You can toggle between several view options including:
5. Activity from the past 7 days.
6. Activity from the past 30 days.
7. Activity within a custom time period.
The red counter shows the number of times the client visited that particular location within the given time frame.
---
# 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://support.soberpeer.com/enterprise/client-triggers.md?ask=
```
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.
