Event Field Not Updating Endpoint URL In Destination Configuration

Depends on the destination type, but often, "yes" More details?

You can also do this at the routing level, if you've got multiple destination configs you can point to:

Links for this message:
image.png

Correction from above: Most destinations do not inherently support dynamic URLs like this. The reason being that we establish connections to the destination continually, ready to flush events as they show up. If the connection URL is based on event content, we can't operate efficiently.

but you can absolutely define multiple destinations, and use the Enable Expression option in the routing table to send to the correct, pre-defined, output

Unfortunately, there maybe "several 100s" of destinations with this format, and it would be easier to "one shot" to the endpoint, it's more of a "webhook call" than "stream to a service"

@user :first_place_medal: You are correct: > When Load balancing is disabled, if an event that contains the internal field __url, that field’s value will override the General Settings > Webhook URL value. This way, you can determine the endpoint URL dynamically.

thank you for the correction

I could imagine that this would result in increased number of Concurrent Requests, depending on the cardinality. So you mayyyyy have to bump up the Advanced Settings > Request concurrency if you see Sender is at capacity messages in the logs

oooooooh, that is perfect. Thank you!