. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 8.11. Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint... Initializing scoring service endpoint... Initializing campaigns service endpoint description", "configType": "oneshot", "properties": { "period": "2m30s", "segment": "contacts", "mapping": { "0": "firstName", "1": "lastName",

Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint... Initializing scoring service endpoint... Initializing campaigns service endpoint description", "configType": "oneshot", "properties": { "period": "2m30s", "segment": "contacts", "mapping": { "0": "firstName", "1": "lastName", "period": "2m30s", //Same as 'consumer.delay' option in the import source path "segment": "contacts", //Segment ID to use to collect profiles to export "mapping": { ... } }

profiles or sessions subdirectory then directory Rule rules Scoring scorings Segment segments Tag tags ValueType values Blueprint is used to declare what the plugin provides and inject SEGMENTS `Segment`s represent dynamically evaluated groups of similar profiles in order to categorize the associated users. To be considered part of a given segment, users must satisfies the segment’s condition condition. If they match, users are automatically added to the segment. Similarly, if at any given point during, they cease to satisfy the segment’s condition, they are automatically removed from it. TAG