> For the complete documentation index, see [llms.txt](https://docs.fullsession.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullsession.io/19.-integrations/fullsession-with-segment.md).
# FullSession with Segment
The FullSession integration with Segment allows you to install and enable FullSession on your website or app. With the click of a button, you’ll be able to capture sessions and send custom events and user traits from Segment to FullSession . This means no custom coding is necessary to get up and running, saving you time and development resources.
### Prerequisites:
* A Segment account
* A FullSession account
* Admin access to FullSession Account
Setting Up the Integration
Segment's *Destination Actions* allows more functionality and improves upon the existing process by enabling you to see and control how event data is captured and sent to action-based destinations. The actions available in Segment that can be mapped to FullSession's API are Identify User, Track Event, Viewed Page.
1. Log in to Segment, click Catalog, then click Destinations.
2. Find and Select FullSession , then click Add destination.
3. Select the source site you want to add the integration to
4. Give the integration unique name
5. In the settings tap enter the customer ID (link to how to get the customerId) and toggle the enable destination
6. Don’t forget to save the changes
And that’s it, now FullSession snippet code will be installed automatically into your source along with segment snippet code and all (Track, identify, Page) events that you configured in segment will be sent automatically to FullSession dashboard
---
# 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.fullsession.io/19.-integrations/fullsession-with-segment.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.