Options for Handling Duplicate Users


1 comment

  • Kylee Graff

    I agree that a better way to handle this would be incredibly beneficial. I find that when updating attributes to track certain behaviors (for example, registration for events) that I am required to update multiple records when they are really the same person.  We use email address as the unique identifier for a user and I'm unsure why the system doesn't recognize that across all levels.  Further, it makes messy segments with duplicates visible when CSMs are wanting a clean view of users registered for X event.  Unfortunately, I haven't found a way around this since I must use an attribute (or tag) to exclude from future invite campaigns.

    Comment actions Permalink

Please sign in to leave a comment.