How to identify users by something other than key in the UI


1 comment

  • Dave Murphy

    Hi Brandon, first, apologies for missing this post!  To answer your question, we do need to put an ID in for the whitelist.  Two thoughts:

    1) Unfortunately, we overload the term attributes, and your link references using attributes to target users using key/value pairs at runtime.  Those we refer to as custom attributes are used for targeting using rules and never make their way back to Split.  Identify attributes are used to associate metadata with an ID.  This article describes the difference in more detail. Here's a link to the docs for using the Admin API to add metadata to a key.

    2) Segments might help here.  I understand that's not quite the same thing and addresses a somewhat different use case, but I thought I'd bring it up to think about.


    Comment actions Permalink

Please sign in to leave a comment.