0

Necessary to set "active" false ? (In the context field of a Page/Identify call)

Hi, guys,

 

Can I ask if someone knows if I'm supposed to set "active" false in the context field of a Page or Identify call, at some point? Or would inactivity imply a user is not active? Therefore, no need to set it false? (I was thinking of setting "active" true, say, when a user logs in.)

 

Also, wouldn't it imply a user is active, as long as a tracking called is made? Why do I need to set this "active" at all?

 

Thank you for your help! 😊

 

/J

1reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Hi,  JJ,

     

    Thanks for your message! You shouldn't have to trigger calls with "active: false" too often, but so you know - this is typically used in .identify() calls when you want to update a user's traits but not a "last seen" attribute. This is mostly useful if, say, you have frequent in-person or phone interactions with your users, whose profiles you then wish to update.

     

    For example:

     

    • on of your team members finds out via a telephone call that a customer always prefers ice vanilla cream over chocolate;
       
    • this use has not visited your website or used your app for one month;
       
    • you fire off a one-off .identify() with "active: false" in the context:
       

      • this updates that user's traits to reflect this new preference;
         

      • but does not falsely update "last seen" attribute;
         

      • your metrics continue to show that they have not visited your site or app in a month;
         


    Similarly, these can be passed in the context of Track calls and Page calls (though doing so would be counterintuitive to me at first glance unless your specific use case permits it.


    I hope this makes sense! Thanks again for writing in.

    Reply Upvote