> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/overview/segmenting.md).
# Segmenting
Assigning one **Category** but different **Keywords** to Daylite helps you segment your Contacts, which you can then use when doing a search. Each of the object types in Daylite can be given one Category but multiple Keywords from a pre-determined list. These lists can be customised according to the specific client’s business requirements.
{% hint style="info" %}
**Did you know?**
You can only assign a single **Category** to a Person or Company, such as Prospect, Client or Vendor, but you can assign as many different **Keywords** as needed, such as Newsletter, Christmas card or Webinar.
{% endhint %}
This would let you know they are part of your newsletter mail out, require a Christmas card, or were part of the webinar you ran to attract new customers. Now each time you run a search using any of these Categories or Keywords you will see a list of your customers (Category) who receive your newsletter (Keyword).
Congratulations, you have successfully segmented your database.
---
# 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.daylite.app/help/mac-fundamentals/overview/segmenting.md?ask=&goal=
```
`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.