Actually this is by design and used for anonymous profiles. To properly create a profile the context.json endpoint should be used.
Regards, Serge... Serge Huber CTO & Co-Founder T +41 22 361 3424 9 route des Jeunes | 1227 Acacias | Switzerland jahia.com <http://www.jahia.com/> SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER <https://twitter.com/sergehuber> | VCARD <http://www.jahia.com/vcard/HuberSerge.vcf> > JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained and to discover why Jahia is a leading User Experience Platform (UXP) for Digital Transformation. On Fri, Feb 7, 2020 at 11:09 AM Gilad Weinbach <gweinb...@yotpo.com> wrote: > sending a new event(new session, new profileId ) > using POST http://{{UNOMI_URL}}/eventcollector > i get profile'Id with prefix temp_ > > using POST http://{{UNOMI_URL}}/context.json > it is a regular profileId > > is it a bug in eventcollector? > > > body example: > { > "sessionId" : "gil2", > "events":[ > { > "eventType":"orderCreated", > "scope": "store1", > "properties" : { > "email" : "g...@mail.com", > "store_id": "store1", > "key": "store1#g...@mail.com", > "value": 100, > "currency": "USD" > } > } > ] > } >
