Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Darkly)
  • No Skin
Collapse
brainCloud Forums
  1. Home
  2. Suggestions
  3. Portal-X Suggestions
  4. [Feature Request] Design > Segments – Condition for missing attributes (or segment membership as an alternative)

[Feature Request] Design > Segments – Condition for missing attributes (or segment membership as an alternative)

Scheduled Pinned Locked Moved Portal-X Suggestions
3 Posts 3 Posters 90 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    LEE JONG GUN
    wrote last edited by
    #1

    Hello,

    I'd like to request a feature for the Segments configuration under the Design section.

    Currently, when setting up segment criteria based on player attributes, it seems that a player can only be matched if the attribute actually exists on their profile. However, there is no way to define a condition for players who do NOT have a specific attribute (i.e., the attribute is missing / has never been set).

    Alternatively, this could also be solved with a segment membership condition — for example, "player is a member of Segment X" or "player is NOT a member of Segment X". With this, I could create a segment of players who have the attribute, and then simply exclude that segment to get the same result as an "attribute does not exist" condition.

    So either of the following would cover this use case:

    1. An operator like "does not exist" (or "is not set") for player attribute conditions
    2. A condition based on segment membership: "is in segment" / "is not in segment"

    If there is already a workaround for this, please let me know.

    Thank you!

    1 Reply Last reply
    0
    • J Offline
      J Offline
      JasonL
      bitHeads
      wrote last edited by
      #2

      Thanks for the suggestion, you’re correct that current segment criteria only support value comparisons and simple membership/range checks, so there’s no explicit “attribute does not exist / is not set” operator, nor any way to reference segment membership (e.g., “is in segment X” / “is not in segment X”) in segment definitions, so we don’t currently have a real workaround that delivers the exact semantics you’re asking for, I’ll forward your request to the team for consideration.

      1 Reply Last reply
      1
      • johnhJ Offline
        johnhJ Offline
        johnh
        wrote last edited by
        #3

        Created case 14475

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Solved
        • Unsolved
        • Users