-
Notifications
You must be signed in to change notification settings - Fork 0
segmentdesc parameter
When your API URL contains a visitor segment (cohort), you will find in your URL a parameter that will display a description of your segment. The subset period indicates the period on which the segment is applied.
Thanks to this parameter, you can dynamically change the period of the cohort directly within the URL.
Examples:
.={p1:{R:{D:-1}}}&segment=100026916&segmentdesc={period:{D:2017-03-02}
Analysis context: Visitors who came on the site on the 2nd of March 2017 (cohort defined in “segmentdesc”) and see their action on yesterday (dataset period defined in “period”)
.={p1:{R:{D:-1}}}&segment=100026916&segmentdesc={period:{M:2017-03}}
Analysis context: Visitors who came on the site in March 2017 (cohort defined in “segmentdesc”) and see their action on yesterday (dataset period defined in “period”)
.={p1:{R:{D:-1}}}&segment=100026916&segmentdesc={period:{D:{start:'2017-06-08',end:'2017-06-10'}}}&
Analysis context: Visitors who came on the site between the the 8th & the 10th of August 2017 (cohort defined in “segmentdesc”) and see their action on yesterday (dataset period defined in “period”)
The period displayed in the “segmentdesc” parameter is different from the period defined for the entire dataset (defined in the period parameter).
For example, you can analyse the visitors who bought a product on your website last month (period of the cohort), and see if they came back last week (period of the Dataset). Or, it is also possible to have both periods identical.
Note:
The segmentdesc only works with fixed (Start/End, Day, Week, Month) and continuous periods.
The period of the visitor segment is limited to 31 days maximum.
Last update: 09/08/2017
-
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