known schema to make sure it complies with an expected payload. If the received payload does not match a known schema, it will be rejected by Apache Unomi 2. Apache Unomi 2 also introduces a set of administrative "events" ("self.target" equals "events") The name of this schema is "contactInfoSubmitted", this MUST match the value of the "eventType" field in the event itself (below) To simplify our schema declaration illustrated in the following example: Upon received events, Apache Unomi will execute all the rules that match the current context, and return an updated context. This way of sending events is usually used upon

} } ] } EOF Upon received events, Apache Unomi will execute all the rules that match the current context, and return an updated context. This way of sending events is usually used upon count the number of objects that match a certain condition without retrieving the results. This can be used for example to quickly figure out how many objects will match a given condition before actually EXAMPLE In the following example a Persona represents a visitor from Europe, that can be used to match by location. { "itemId": "europeanVisitor", "itemType": "persona", "properties": {

To be considered part of a given segment, users must satisfies the segment’s condition. If they match, users are automatically added to the segment. Similarly, if at any given point during, they cease visitor is considered for scope-level goals while campaign-level goals only consider visitors who match the campaign’s conditions Apache Unomi 1.1.x - Documentation - 6 CAMPAIGN A goal-oriented, time-limited exactly what Unomi rules are supposed to do. Rules are guarded by conditions and if these conditions match, the associated set of actions will be executed. In our case, we want our new incrementTweetNumber