Question

How can I connect multiple Microsoft Bing Conversions API (CAPI) destinations to a single Segment Reverse ETL source, and is it possible to override the UET Tag and ApiToken dynamically or lift the one-destination-per-source restriction?

Product

Segment

Environment

Segment Console

Answer

Currently, only one Microsoft Bing Conversions API (CAPI) destination can be added per Segment source. The UET Tag and ApiToken credentials are set at the destination level and cannot be overridden dynamically in the payload or mapping. This is a product limitation and cannot be lifted on a per-destination basis.

As a workaround, consider using a Repeater Destination to forward events to additional sources, each with its own Bing CAPI destination, or use a Webhooks (Actions) Destination for more flexible routing and transformation. However, these approaches may require additional setup and maintenance.

Additional Information 

Feature requests, such as supporting multiple Bing CAPI destinations per source are reviewed by the Product team on a quarterly basis. For updates, refer to the Segment documentation.