> For the complete documentation index, see [llms.txt](https://docs.lootlocker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lootlocker.com/shared-systems/player-segments.md).

# Player Segments

Player Segments let you target Triggers or Broadcasts to specific groups of players based on their behavior, activity, platform usage, or play history. Each Segment is made up of one or more conditions. To qualify for a Segment, a player must match all conditions within that Segment.

If multiple Segments are attached to the same Trigger or Broadcast, they are evaluated as an OR condition. This means a player only needs to qualify for one of the attached Segments to be eligible for the Trigger reward or Broadcast content.

Segments make it easier to deliver more relevant rewards and messaging to the right players at the right time.

### Use Cases

* Reward players who have reached a specific playtime threshold
* Show platform-specific news or updates to players on Steam, Xbox, or PlayStation
* Target returning players who have not played recently
* Reward players who have also played another game in your portfolio
* Run campaigns for specific player groups without affecting your entire player base
* Create claimable rewards in Discord using Squire

### How To

* [Create a Segment](/shared-systems/player-segments/how-to/create-a-segment.md)


---

# 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.lootlocker.com/shared-systems/player-segments.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.