and executed. ANATOMY OF A GROOVY ACTION To be valid, a Groovy action must follow a particular convention which is divided in two parts: An annotation used to define the associated action type The function present in this list once added. 5.2.2. READ A SCHEMA It’s possible to get a schema by its id by calling the endpoint POST {{url}}/cxs/jsonSchema/query with the id of the schema in the payload of the CREATE / UPDATE A JSON SCHEMA TO VALIDATE AN EVENT It’s possible to add or update JSON schema by calling the endpoint POST {{url}}/cxs/jsonSchema with the JSON schema in the payload of the request. If

This is the way that the Analytics.js library handles it.So make sure you are aware of this when calling it.This is to avoid having two page views on a single call and to be compatible with old versions and executed. ANATOMY OF A GROOVY ACTION To be valid, a Groovy action must follow a particular convention which is divided in two parts: • An annotation used to define the associated action type • The that are implemented as Java classes, and as such may perform any kind of tasks that may include calling web hooks, setting profile properties, extracting data from the incoming request (such as resolving

identifier>, "properties": } Some types can be dynamically defined at runtime by calling to the REST API while other extensions are done via Unomi plugins. Part of extending Unomi, therefore generate a session identifier for our request since Unomi currently requires one. • We’re calling the ContextServlet using the default install URI, specifying the session identifier: