Path segment destination variables

We’ve added a segments destination variable from 0 to 9 to be used as either a replacement tag or in dynamic destinations. This can be helpful when using partial path matching and then forwarding a specific path element to the destination.

For example, you have a request like example.com/test1/test2. In this case, you always want to use the second path segment. You can now use the segments variable: {segments.1}. The first segment of the path can be found under {segments.0}.