Issue
When using Segment’s destination, you may encounter a system limit of 50 mappings per destination. When attempting to add more than 50 mappings (for example, to support multiple brands or customer types), the system prevents additional mappings from being created. This can impact workflows that require a higher number of mappings per destination.
Product
Twilio Segment
Environment
Segment Console
Cause
The 50-mapping limit per destination is a system constraint designed to ensure performance and stability. This limit applies to all customers and cannot be increased on a per-customer or per-destination basis.
Resolution
To work within the current mapping limit, consider the following approaches:
- Mapping Consolidation: Review your mappings to see if some can be combined or generalized, reducing the total number required.
- Multiple Destinations: Split your mappings across multiple destinations, each handling a subset of brands or customer types.
- Pipeline Adjustments: If your pipeline generates mappings automatically, consider updating the logic to only create and maintain mappings that are actively needed, avoiding the recreation of unused ones.
Additional Information
- Deleting unused mappings may not be effective if your pipeline automatically recreates them.
- There is currently no option to request an increase to the mapping limit for individual destinations.
- For more details, see the Segment documentation on customizing mappings.