We will review the types of default data we collect on events. By default we collect Time, Segments, permutive IDs and client properties on each event captured.
There are 2 types of data collected: non-properties and properties.
These are data points that are collected on every event, that aren't properties of the event. When creating segments you cannot explicitly refer to this data, however you can build segments based on time, sessions and the segments a user is in.
|Partition Time||_PARTITIONTIME||String||Required||Date Stamp|
|Time||time||String||Required||The exact time (non-nullable)|
|Event ID||event_id||String||Required||Unique identifier for that event (non-nullable)|
|User ID||user_id||String||Required||Unique identifier for that user|
|Session ID||session_id||String||Required||Unique identifier for that session|
|View ID||view_id||String||Required||Unique identifier for that page|
|Segments||segments||String||Required||The segments the user is currently in, listed as an array of the segments' codes.|
Although each Events can have custom properties, they will all contain Client Properties. These can be explicitly used when creating segments.
|URL||url||String||Required||The client URL|
|Title||title||String||Required||The client title|
|Type||type||String||Required||The client type e.g. 'web', 'fia', 'amp', 'ios', 'android'.|
|Domain||domain||String||Required||The client domain|
|Referrer||referrer||String||Required||The client referral url.|
|User Agent||user.agent||String||Required||The client user agent.|