You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by GitBox <gi...@apache.org> on 2019/08/04 17:31:44 UTC

[GitHub] [unomi] lhwong commented on issue #73: .identify() does not send events to dmp

lhwong commented on issue #73: .identify() does not send events to dmp
URL: https://github.com/apache/unomi/pull/73#issuecomment-518021591
 
 
   https://segment.com/docs/spec/identify/
   "Our recommendation for when and how often you should call identify is as follows:
   
   After a user registers
   After a user logs in
   When a user updates their info (eg changes or adds a new address)"
   
   
   In this case, should I use
   1. "(Preferred) Use you own custom event(s) to send data you want to be inserted in a profile, and use rules to map the event data to the profile." as given under section 3.2.3. HOW TO UPDATE A PROFILE FROM THE PUBLIC INTERNET (https://unomi.apache.org/manual/latest/index.html#_how_to_update_a_profile_from_the_public_internet)
   or
   2. "performs an server-to-server call to send the login event to Apache Unomi using the Unomi key." as given under section 3.2.8. HOW TO SEND A LOGIN EVENT TO UNOMI (https://unomi.apache.org/manual/latest/index.html#_how_to_send_a_login_event_to_unomi)
   
   To comply with the integration implementation of analytics.js for Javascript client, I believe the option 1 (invoke call from Javascript) seems to be the way. 
   
   
   Then, "Setup a rule that can check a profile property to see if profiles can be merged on an universal identifier such as an email address by calling analytics.identify([userId], [traits], [options], [callback]). The example of rule is similar to https://github.com/apache/unomi/blob/master/samples/login-integration/src/main/resources/META-INF/cxs/rules/exampleLogin.json
   This rule calls an action called :
   mergeProfilesOnPropertyAction
   What this means is that upon successful login using an email, Unomi will look for other profiles that have the same email and merge them into a single profile." 
   
   
   However, this doesn't seems to solve the security concern you have: "Normally an identify should be a secure operation because it can merge with other profile". How can we call identity from public internet and merge profile based on userId?
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services