This repository was archived by the owner on May 5, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Segment
Benjamin Diolez edited this page May 5, 2026
·
1 revision
The parameter segment describes the context of the segment. It is composed of different parameters:
| SECTION | DESCRIPTION | POSSIBLES VALUES |
|---|---|---|
| scope | The scope defines which kind of segmentation you will use. Find mode information in the help centre. | visit_id user_id visitor_id event_id |
| segmentKey | In case your segment has been saved, you can directly use the key to refers to the segment. | String |
| content | Description of the segment. | See below |
| mode | Two modes are available to choose if you want to include or exclude the behaviour in your segment. | include or exclude |
| period | In case of visitor or user segmentation, define the period on which the behaviour should have been made. | See here |
| space | In case of visitor or user segmentation, define the space on which the behaviour should have been made. | See here |
| CONTENT | DESCRIPTION | VALEURS POSSIBLES |
|---|---|---|
| condition | The condition contains the filter you want to have in your segment. | Can only contain filter |
| filter | The filter describes all the behaviour you want to follow. | See here |
// Segment on the device type "Desktop"
"segment": {
"section": {
"scope": "visit_id",
"content": {
"condition": {
"filter": {
"device_type": {
"$eq": "Desktop"
}
}
}
},
"mode": "include"
}
},# Segment on the device type "Desktop"
"segment": {
"section": {
"scope": "visit_id",
"content": {
"condition": {
"filter": {
"device_type": {
"$eq": "Desktop"
}
}
}
},
"mode": "include"
}
},# Segment on the device type "Desktop"
"segment": {
"section": {
"scope": "visit_id",
"content": {
"condition": {
"filter": {
"device_type": {
"$eq": "Desktop"
}
}
}
},
"mode": "include"
}
},# Segment on the device type "Desktop"
"segment": {
"section": {
"scope": "visit_id",
"content": {
"condition": {
"filter": {
"device_type": {
"$eq": "Desktop"
}
}
}
},
"mode": "include"
}
},-
Data API
- Data flow
- Advice optimizations data flow
- Error codes data flow
- Faq data flow
- General information data flow
- Technical information data flow
- Reporting API v3
- Getting started
- Methods
- Parameters
- Technical information
- REST API
- Campaigns
- Custom variables
- Getting started rest
- Methods rest
- Response structure parameters rest
- Fixed periods
- Parameters compatibility
- Relative periods
- Structure of the response
- “code” parameter
- “columns” parameter
- “evo” parameter
- “filter” parameter
- “include” parameter
- “lng” parameter
- “max-results” parameter
- “page-num” parameter
- “period” parameter
- “period” parameter: “H” v. “He” & “MN” v. “MNe”
- “retention” parameter
- “segmentdesc” parameter
- “segment” parameter
- “sep” parameter
- “sort” parameter
- “space” parameter
- Technical specifications rest
- Data flow
-
Data collection
- Android
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- Apple
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- General
- Cddc renew staging process
- Changelog
- Craft your hit
- Encoded parameters
- Server side cookie management
- Supported taggings
- Tagging deletion
- Utilisation of dispatch sdks
- JavaScript
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Partners javascript
- Users
- Piano Analytics
- Event tagging piano analytics
- Getting started piano analytics
- Piano analytics tagging
- Feeding piano analytics with as2 tagging
- Tagging custom properties sdk
- Android