- A bridge table is an intermediate mapping table used to connect two tables with many-to-many relationships.
- For example, Customers could belong to multiple Segments and each Segment had many Customers.
- Direct relationship caused duplicate counts and wrong totals in reports.
- We created a bridge table with Customer ID and Segment ID combinations.
- Both dimension tables connected to the bridge using one-to-many relationships.
- This controlled filter flow and removed ambiguity in the model.
- Slicers then showed correct customer counts per segment.
- It is required whenever direct many-to-many relationships distort aggregations.
- Commonly used in scenarios like tagging, categories, and multi-assignment mappings.
What is bridge table and when is it required?
Updated on February 19, 2026
< 1 min read
