Enable Partial Match Filtering for EUM User ID in Analytics

Problem Statement

When filtering EUM Analytics data in the Website/Page Loads view, the User > ID field only supports exact-match operators (equals, does not equal, is present, is not present). This limitation prevents us from performing partial matches based on User ID prefixes or substrings.

In contrast, custom metadata fields support additional operators including CONTAINS, which creates an inconsistency in the product's filtering capabilities.

Use Case

Our organization structures User IDs with meaningful prefixes that identify tenants, agencies, or business units (e.g., "AGENCY_001_user123", "TENANT_WEST_user456"). We need to:

• Filter analytics data by User IDs that contain a specific tenant or agency identifier
• Analyze user behavior by User IDs that start with a particular prefix
• Group and segment users based on partial User ID patterns

Current Workaround

We must duplicate the prefix information as a separate custom metadata field, which:

• Increases client-side instrumentation complexity
• Requires parsing User IDs in the browser
• Maintains redundant data
• Adds unnecessary overhead to our implementation

Requested Enhancement

Enable partial match operators for the EUM User ID field, including:

• CONTAINS - Match User IDs containing a specific substring
• STARTS WITH - Match User IDs beginning with a specific prefix
• ENDS WITH - Match User IDs ending with a specific suffix

This would align User ID filtering with the capabilities already available for custom metadata fields.

Special Consideration: Review our support case. There is disparity with your use User.ID and User.Name in different contexts, that design decision attributed to this limited option on this field  because it had "ID" in it.

Expected Behavior

When filtering on User > ID in the Analytics UI, we should see the same operator options available for custom metadata fields, allowing us to perform substring and pattern-based matching on User IDs.