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.

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, page, and screen methods.

Track calls

Feature Experimentation receives this call as an EVENT hit:

analytics.track('Clicked AddToCart Button');

{
  "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:

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

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

Page calls

Feature Experimentation receives this call as a PAGEVIEW hit:

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

{
  "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:

analytics.screen('Home');

{
  "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.

You must use the exact same visitorID between Segment.com and the call to the Decision API.

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

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.