Events sent to Destination Functions Dropped by Integrations Object – Twilio Support

Issue

You observe that events sent to a specific Segment Destination Function are filtered out, and your delivery logs display the error code FILTERED_BY_INTEGRATIONS_OBJECT. This issue persists even after you attempt to reference the destination inside the integrations object using various name combinations.

Product

Twilio Segment

Environment

Segment Console

Cause

This error occurs when the destination reference inside the integrations object does not match the required case-sensitive formatting. Unlike standard catalog destinations, Destination Functions require the reference to include both the destination name and the workspace name, structured exactly as Destination Function Name (Workspace Name).

Because Destination Functions are custom-built, Segment requires this appended workspace name to uniquely identify your specific function. Any discrepancies in spacing, casing, or punctuation (such as missing or extra periods or commas) within either the function name or the workspace name will cause the integrations object filter to fail and drop the event.

Resolution

To resolve this error, update the integrations object in your event payload to match the exact syntax and punctuation of your Segment workspace by following these steps:

Log into your Segment Console and verify the precise spelling, capitalization, and punctuation of both your Destination Function name and your workspace name.
Update the reference in your payload's integrations object using the exact format: "Destination Function Name (Workspace Name)": true.
Ensure that all punctuation matches exactly. For example, if your workspace name contains a trailing period but lacks a comma, your payload string must reflect that exact configuration.
Send a test payload to confirm that the Destination Function successfully receives the event and no longer triggers the FILTERED_BY_INTEGRATIONS_OBJECT error.

Additional Information

Destination Functions are custom-built, which is why Segment automatically appends the workspace name to guarantee a unique identifier across the platform.
Standard destinations generally only require their standard integration name (for example, "Google Analytics 4 Web": true), making this strict formatting requirement unique to Destination Functions.