> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/segment-feature-experimentation-integration/import-segment.io-trackers-to-feature-experimentation.md).

# Import Segment.IO Trackers to Feature Experimentation

### Segment integration

Segment is a customer data platform (CDP) that helps you collect, clean, and control your customer data.

Segment manages data and integrations across your growth, product, and marketing stack. Track events and users through Segment's API and libraries. Then, send product data to your analytics and marketing platforms with minimal instrumentation.

### Configuration

To use the Segment integration, you need:

* A Segment account.
* An active Feature Experimentation plan.

Configure the integration through the [Segment catalog](https://app.segment.com/goto-my-workspace/destinations/catalog/flagship).

Beyond the initial SDK or API integration, Feature Experimentation requires no additional configuration.

### How Segment calls map to Feature Experimentation

Segment automatically transfers each triggered call to Feature Experimentation. This removes the need to reimplement Universal Collect hits.

Segment `track` calls are sent as `EVENT` hits. Calls with `transactionId` or `revenue` are sent as `TRANSACTION` hits.

Segment `page` and `screen` calls are sent as `PAGEVIEW` and `SCREENVIEW` hits.

Review Segment's documentation to understand the [`track`](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#track), [`page`](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#page), and [`screen`](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#screen) methods.

#### Track calls

Feature Experimentation receives this call as an `EVENT` hit:

```javascript
analytics.track('Clicked AddToCart Button');
```

```json
{
  "cid": "<environmentId>",
  "ea": "Clicked AddToCart Button",
  "ec": "Action Tracking",
  "t": "EVENT",
  "vid": "visitorId1234567",
  "ds": "APP"
}
```

#### Transaction calls

Feature Experimentation receives a `track` call with `transactionId` or `revenue` as a `TRANSACTION` hit:

```javascript
analytics.track('Purchase', {
  transactionId: 'QWERTY12345',
  revenue: 349
});
```

```json
{
  "cid": "<environmentId>",
  "ta": "Purchase",
  "tid": "QWERTY12345",
  "t": "TRANSACTION",
  "vid": "visitorId1234567",
  "ds": "APP"
}
```

#### Page calls

Feature Experimentation receives this call as a `PAGEVIEW` hit:

```javascript
analytics.page('Home', {
  title: 'Welcome | Home',
  url: 'http://www.example.com'
});
```

```json
{
  "cid": "<environmentId>",
  "dl": "http://www.example.com",
  "t": "PAGEVIEW",
  "pt": "Welcome | Home",
  "vid": "visitorId1234567",
  "ds": "APP"
}
```

#### Screen calls

Feature Experimentation receives this call as a `SCREENVIEW` hit:

```javascript
analytics.screen('Home');
```

```json
{
  "cid": "<environmentId>",
  "t": "SCREENVIEW",
  "pt": "Home",
  "vid": "visitorId1234567",
  "ds": "APP"
}
```

Events appear in reports for campaigns assigned to the visitor. Reports can take up to three hours to update.

{% hint style="warning" %}
You must use the exact same visitorID between Segment.com and the call to the Decision API.
{% endhint %}

Segment hits appear in the **Basic information** step of a feature. Select one or more KPIs to include in the report.

<img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2F9HC1xFu6trKIJaacGCXL%2Funknown.png?alt=media&amp;token=e8e3a8f4-7b7d-4eea-84d6-5205fe01f35d" alt="" height="176" width="602">

Feature Experimentation and Segment must use the same visitor ID. Confirm that your Decision API and Segment calls use the same value.

Depending on your server-side or client-side implementation, call order can differ. Always use the same Segment user ID and Feature Experimentation visitor ID. This avoids analytics discrepancies.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/segment-feature-experimentation-integration/import-segment.io-trackers-to-feature-experimentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.