Redirect will send deployments that meet the parameters to a single specified Card Pool.
Example rule parameters (Card Pool A):
-
Spend type: Air
-
Amount threshold: £500.00
-
Currency: GBP
-
Rule type: Redirect (Deployments redirected to Card Pool B)
If you create an air deployment using Card Pool A and the total amount is equal to or greater than £500.00, then the deployment will be redirected to Card Pool B.
Load balance divides every 100 deployments between specified Card Pools, and this is referred to as the load balance percentage.
The load balance percentage is the number of cards out of every 100 that will be re-routed to configured Card Pool/s.
Re-routing is triggered when a deployment meets, or exceeds the amount threshold.
Example rule parameters (Card Pool A):
-
Amount threshold: £200
-
Spend type: Generic
-
Rule type: Load balance (Card Pool B: 50%, Card Pool C: 50%)
If you create 50 card deployments from Card Pool A, the deployments will be re-routed to Card Pool B. If you then create 50 more card deployments from Card Pool A, the deployments will be re-routed to Card Pool C. After 100 cards have been re-routed, the routing will return to Card Pool B.
Alternative example rule parameters (Card Pool A):
-
Amount threshold: £200
-
Spend type: Generic
-
Rule type: Load balance (Card Pool B: 20%, Card Pool C: 20%, Card Pool D: 60%)
If you create 120 card deployments from Card Pool A, the first 60 deployments will be re-routed to Card Pool D, as this is the Card Pool with the highest weighting balance. The following 20 will be routed to Card Pool B, then the next 20 to Card Pool C, and the last 20 will be routed to Card Pool D.
After this, there would still be 40 further deployments that will be re-routed to Card Pool D, before the routing returns to Card Pool B.