> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/product/segment.md).

# Segment

## **Why syncing my Segment data to** [**Whaly**](https://whaly.io)**?**

Syncing your Segment can be useful for various use cases:

* Track your Users behaviours and your conversion ratios
* Communicate with your Customer Success team the product usage of each of your customer to detect upsells opportunities and churn risks
* Link your product usage data with your CRM and Revenue data to identify correlation and get insights into your offerings
* ...

## Connecting Segment data

Whaly recommend to use the native Segment connector to your Data Warehouse:

* [For BigQuery](https://segment.com/docs/connections/storage/catalog/bigquery/)
* [For Snowflake](https://segment.com/docs/connections/storage/catalog/snowflake/)

Once the data will be loading in your Data Warehouse, [you'll be able to import it into Whaly](broken://pages/HHJENGqi53AufePzj458).


---

# 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.whaly.io/connectors/source-catalog/product/segment.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.