---
title: Configuring load balancing strategies
description: To create and configure a new load balancing strategy in PingAccess:
component: pingaccess
version: 9.0
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_configuring_load_balancing_strategies
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_user_interface_reference_guide/pa_configuring_load_balancing_strategies.html
revdate: July 28, 2025
section_ids:
  about-this-task: About this task
  steps: Steps
  choose-from: Choose from:
  choose-from-2: Choose from:
---

# Configuring load balancing strategies

## About this task

To create and configure a new load balancing strategy in PingAccess:

## Steps

1. Click **Settings**, then go to **Networking > Load Balancing Strategies**.

2. Click **[icon: plus, set=fa]Add Load Balancing Strategy**.

3. In the **Name** field, enter a unique and descriptive name for the strategy.

4. In the **Type** list, select one of the following strategy types:

   ### Choose from:

   * **Header-Based**

   * **Round Robin**

5. Configure the options for the selected load balancing strategy type.

   ### Choose from:

   * For a **Header-Based** load balancing strategy:

     1. In the **Header Name** field, enter the name of the header that contains the selected target host.

     2. To configure PingAccess to use the first available target defined for the site, click **Show Advanced** and select the **Fall Back to First Available Host** option if the target specified in the header is not available or if the header is not present in the request.

        |   |                                                                                                                                                                   |
        | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        |   | If this option isn't enabled, and the specified target isn't available or the request header isn't present, the client receives a `Service Unavailable` response. |

   * For a **Round Robin** load balancing strategy:

     1. If browser sessions shouldn't be pinned to a persistent backend target, clear the **Sticky Session Enabled** checkbox.

        This checkbox is selected by default.

     2. If **Sticky Session Enabled** is selected, enter a cookie name to use in the **Cookie Name** field.

        The PingAccess engine uses this cookie to track the persistent backend targets for a session.

        |   |                                                                                                                                                                            |
        | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        |   | When you define a web session, the **Cookie Name** field defines a cookie prefix to use. The rest of the cookie name comes from the **Audience** field in the web session. |

6. Click **Save**.