first (beta) version of the Unomi GraphQL API. 1.1.1. INTRODUCING PROFILES ALIASES Profiles may now have alias IDs, which is a new way to reference profiles using multiple IDs. The Unomi ID still exists You can read more about profile aliases here. 1.1.2. SCOPES DECLARATIONS ARE NOW REQUIRED Scopes declarations are now required in Unomi 2. When submitting an event and specifying a scope, that scope differences is the removal of open maps. The properties field in the events objects provided by unomi are now restricted by JSON schema. This means object properties must be declared in a JSON schema for an event

.json (which isn’t very useful at this point). You can now find an introduction page at the following location: http://localhost:8181 Also now that your service is up and running you can go look at the pagePath : location.pathname + location.hash, destinationURL: location.href } } Now if you want to provide your own custom page information for the initial page view, you can simply events and that they contain the expected data. If not, check your tracking code for any errors. Now that the data is properly sent using an event to Apache Unomi, we must still use it to perform some

0-incubating-SNAPSHOT.jar ../../package/target/unomi-1.0.0- incubating-SNAPSHOT/deploy TESTING THE SAMPLE You can now go to http://localhost:8181/index.html to test the sample code. The page is very simple, you will of the properties coming from Unomi. Additionnally, the raw JSON response is displayed. We will now explain in greater details some concepts and see how the example works. 2.2.3. INTERACTING WITH THE value pairs>, requireSegments: } We will now look at each part in greater details. Apache Unomi 1.1.x - Documentation - 15 SOURCE A context request