Issue

When setting up a Segment Destination Filter using glob patterns, events are not being blocked as expected and continue to be forwarded to the destination. This frequently occurs when trying to filter based on character classes (such as [a-z] or [1-6]) or when utilizing the "Event Name" filter field for Page calls instead of Track calls.

Product

Twilio Segment

Cause

This behavior is caused by two separate configuration misunderstandings:

1. Field Mismatch: The "Event Name" field in Destination Filters explicitly targets the top-level event field, which is natively present in Track events. It does not map to the name field used in Page events.

2. Syntax Limitation: Segment Destination Filters utilizing glob patterns do not support character classes or regular expression brackets like [a-z] or [0-9].

Resolution

To successfully filter Page events, update your Destination Filter configuration with the following logic:

1. Target the correct Event Type: Instead of using "Event Name", add a filter criteria setting Event Type to page.

2. Filter by the specific page name: Add an additional filter condition targeting properties.name (or the specific property tracking your page name) and set it to match your exact page title string (e.g., Home Page).

3. Avoid character classes: Refrain from using regex-style character sets inside glob patterns. Use explicit string matching or supported wildcard characters (*) instead.

Additional Information

• Segment Documentation: Destination Filters