Issue
When syncing Engage audiences to a destination, audience data fails to send, and the Delivery Overview tab shows events as dropped or filtered with a NO_MATCHING_MAPPING error. This error indicates that events sent to the destination do not match any enabled mapping, preventing your audience data from being delivered as expected.
Product
Twilio Segment
Environment
Segment Console
Cause
This error occurs when there is no mapping configured for the event type being sent (such as Identify or Track), or when the mapping triggers are not enabled.
In Segment's Actions-based framework, the destination requires explicit instructions on what to do when a user enters or exits an audience. Without the baseline "Add" and "Remove" mappings set up, Segment does not know how to route the events, causing them to drop. Additionally, syncs may begin before mappings are fully configured and enabled, resulting in these failed deliveries.
Resolution
- Navigate to your specific destination within the Segment workspace.
- Go to the Mappings tab and click New Mapping.
- Review the destination configuration and ensure mappings exist for all event types being sent.
- Ensure the trigger conditions match the output payloads of the audiences (for example, setting the trigger condition to
event = "Audience Entered"orevent = "Audience Exited"). - Save and enable the necessary mapping triggers before activating the destination.
Additional Information
- Syncs may start before mappings are enabled, so it is highly recommended to complete and activate all mappings prior to connecting a destination to an audience.
- Once these mappings are saved and enabled, the filtering errors will stop, and Segment will begin successfully sending events.
- Please keep in mind that, depending on the destination, it may take 24 to 48 hours for the synced users to actively appear and populate within the downstream tool's platform.