# Setting Up Instances

{% hint style="warning" %}
DT uses instances to support network mediation which is only available for **DT FairBid customers**.
{% endhint %}

Mediated network instances, also known as *instances*, indicate the networks you want DT to mediate your placement.

Manage all network instances from the **Instances** section of the **Placement details** screen.

<div align="left" data-with-frame="true"><img src="https://2949766846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLbREhkP3WlLtP6TNVZ2Q%2Fuploads%2FjGTSWkN3INrUahDi3tE5%2FPlacement_Details_2024-08-27_12-58-18.png?alt=media&#x26;token=199c4b27-a1a4-4615-8684-4cf444f94f59" alt="Instances on the Placement Details screen"></div>

To access the **Placement details** screen:

1. Select an app from the [Apps Dashboard](https://docs.digitalturbine.com/dt-console/app-management/apps-dashboard).
2. Go to the **Placements** tab.
3. Select the placement that you want to mediate.\
   The **Placement details** screen displays all networks where DT offers the placement.

## Adding an Instance

Adding instances to placements specifies the networks on which you want DT to mediate the placement. Before you begin adding instances to placements, ensure that you have completed the following tasks:

* [Add the mediated network](https://docs.digitalturbine.com/dt-console/app-management/setting-up-mediated-networks#adding-a-mediated-network) to your app.
* [Add placements](https://docs.digitalturbine.com/dt-console/app-management/setting-up-an-existing-app/setting-up-placements) to your app.

Once you network and placements have been added you your app, you can add the following types of instances to your placements:

* **Waterfall**: Allows for traditional waterfall mediation. When adding a Waterfall instance, confirm that you have a corresponding placement in your network setup. You must provide a name and ID for the instance. DT highly recommends using network placement identifiers so that you can easily identify the placement in the DT Console and on the network. For more information, see [Adding a Waterfall Instance](#h_01JREWSZ35BVDEVSB8XDXFHKZW).
* **Bidding**: Allows for programmatic bidding mediation. You can add bidding instances in the following ways:
  * **Manual**: When manually adding a Bidding instance, confirm that you have a corresponding placement in your network setup. You must provide a name and ID for the instance. DT highly recommends using network placement identifiers so that you can easily identify the placement in the DT Console and on the network. Use manual instance creation for Waterfall networks and manually managed Bidding networks.

    For more information, see [Manually Adding a Bidding Instance](#h_01J3RD5A45GD79RK31ERHWMV3R).
  * **Automatic**: When automatically adding Bidding instances, DT creates the corresponding placement on the network on your behalf and generates the instance name and ID based on the new network placement. Use automatic instance creation for automatically managed bidding networks.

    For more information, see [Automatically Adding a Bidding Instance](#h_01JR13WRNMJEPRFCC26PZBZGMH).

### Adding a Waterfall Instance

In general, DT requires a unique name and ID when adding instances. DT suggests using a unique name and Instance ID derived from a unique network identifier for the corresponding placement on the network. This allows you to reference DT placements with the corresponding network placements. For more information about which network parameter to use, see the appropriate [Network Integration Guide](https://app.gitbook.com/s/4IftQ9WUOy9feTA5sZeE/fairbid-sdk/supported-networks/network-integration-guides).

However, you may reuse instance names and IDs under the following conditions:

* The placements are of the same type. For example, you can reuse an instance in a Banner placement for an instance in any other Banner placement. However, you cannot reuse an instance in a Banner placement for an instance in an Interstitial placement.
* Enter the exact name and ID of the instance you want to reuse. You cannot reuse an instance name with another ID, and conversely, you cannot reuse an instance ID with another name.
* You have integrated FairBid SDK version 3.56.0 or later.

When you add a Waterfall instance, DT uses default settings for CPM and targeting. You can modify these values after adding the instance. For more information, see [Editing an Instance](#editing-an-instance).

To add an instance of a Waterfall network:

1. From the **Instances** section of the **Placement details** screen, click **Add instance**.\
   The **Add instance** window opens and displays a list of mediated networks associated with your app.

{% hint style="info" %}
If the mediated network for which you want to create an instance does not appear in this list, then the network has not been added to your app. For more information, see [Adding a Waterfall Network](https://docs.digitalturbine.com/dt-console/app-management/setting-up-mediated-networks#adding-a-waterfall-network).
{% endhint %}

2. On the **Add instance** window, click the tile for the waterfall network.\
   The **Add instance** naming form appears.

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/H4Be1RW0STOMXA3BbOVp/19580115199900" alt=""></div>

3. Enter a **Name** for the instance. You can enter a unique name or reuse an existing instance name from the same network and placement type. DT uses this name for all reporting activities.
4. Enter an **Instance ID**. DT suggests using the unique identifier for this placement from the mediated network. For more information about what network identifier to use, see the appropriate [Network Integration Guide](https://app.gitbook.com/s/4IftQ9WUOy9feTA5sZeE/fairbid-sdk/supported-networks/network-integration-guides).
5. Enter the minimum price you are willing to accept (CPM) for this placement in the **Worldwide CPM** field. DT uses this CPM until it establishes an automatic eCPM.
6. Click **Add instance**.\
   The instance now appears in the **Waterfall** section of the **Placement details** screen.

### Manually Adding a Bidding Instance

In general, DT requires a unique name and ID when adding instances. DT suggests using a unique name and Instance ID derived from a unique network identifier for the corresponding placement on the network. This allows you to reference DT placements with the corresponding network placements. For more information about which network parameter to use for instance naming, see the appropriate [Network Integration Guide](https://app.gitbook.com/s/4IftQ9WUOy9feTA5sZeE/fairbid-sdk/supported-networks/network-integration-guides).

However, you may reuse instance names and IDs under the following conditions:

* The placements are of the same type. For example, you can reuse an instance in a Banner placement for an instance in any other Banner placement. However, you cannot reuse an instance in a Banner placement for an instance in an Interstitial placement.
* Enter the exact name and ID of the instance you want to reuse. You cannot reuse an instance name with another ID, and conversely, you cannot reuse an instance ID with another name.
* You have integrated FairBid SDK version 3.56.0 or later.

To manually add an instance:

1. From the **Instances** section of the **Placement details** screen, click **Add instance**.\
   The **Add instance** window opens and displays a list of mediated networks associated with your app.

{% hint style="info" %}
If the mediated network for which you want to create an instance does not appear in this list, then the network has not been added to your app. For more information, see [Adding a Manually Managed Bidding Network](https://docs.digitalturbine.com/dt-console/app-management/setting-up-mediated-networks#adding-a-manually-managed-bidding-network).
{% endhint %}

2. On the **Add instance** window, click the tile for the manually managed bidding network.\
   The **Add instance** naming form appears.

<div align="left" data-with-frame="true"><img src="https://2949766846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLbREhkP3WlLtP6TNVZ2Q%2Fuploads%2F5IWSJXoruWYH8vqr8mI3%2FFB_Add-Manual-Bidder_2025-04-09_22-24-39.png?alt=media&#x26;token=ea896453-ee9c-4ca8-a4b3-3e5fbf8b2770" alt="FB_Add-Manual-Bidder_2025-04-09_22-24-39.png" width="563"></div>

3. Enter a **Name** for the instance. You can enter a unique name or reuse an existing instance name from the same network and placement type. DT uses this name for all reporting activities.
4. Enter an **Instance ID**. DT suggests using the unique identifier for this placement from the mediated network. For more information about what network identifier to use,see the appropriate [Network Integration Guide](https://app.gitbook.com/s/4IftQ9WUOy9feTA5sZeE/fairbid-sdk/supported-networks/network-integration-guides).
5. Click **Add instance**.\
   The instance now appears in the **Bidding** section the **Placement details** screen.

### Automatically Adding a Bidding Instance

If you have added an automatically managed bidding network to your app, you can automatically generate instances for that network in your placements. When you automatically generate an instance, DT adds the corresponding placement on the network on your behalf, and then generates a name and ID for the instance based on the newly added placement on the network. For more information about how to add an automatically managed network to your app, see [Adding an Automatically Managed Bidding Network](https://docs.digitalturbine.com/dt-console/app-management/setting-up-mediated-networks#adding-an-automatically-managed-bidding-network).

{% hint style="info" %}
Instances can be automatically generated for the following bidding networks:

* Google Bidder
* Liftoff Monetize Bidder
* Mintegral Bidder
* Pangle Bidder
  {% endhint %}

To automatically add an instance:

1. From the **Instances** section of the **Placement details** screen, click **Add instance**.\
   The **Add instance** window opens and displays a list of mediated networks associated with your app.

{% hint style="info" %}
If the mediated network for which you want to generate an instance does not appear in the list, then the network has not been added to your app. For more information, see [Adding an Automatically Managed Bidding Network](https://docs.digitalturbine.com/dt-console/app-management/setting-up-mediated-networks#adding-an-automatically-managed-bidding-network).
{% endhint %}

2. On the **Add instance** window, click the tile for the automatically managed bidding network.\
   The **Add instance** naming form appears.

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/ps4WMDksqJvCTGmr7nLe/19580115203100" alt=""></div>

3. Click **AUTO GENERATE**.\
   A status message confirms that a corresponding placement was created on the network, and DT populates the instance name and ID based on the new network placement.
4. If needed, modify the generated name of the instance.

{% hint style="info" %}
You cannot modify the pre-populated Instance ID, as it is based on a unique ID for the network placement.
{% endhint %}

5. Click **Add instance**.\
   The instance now appears in the **Instances** section.

## Editing an Instance

The DT Console creates Waterfall instances with default pricing and targeting settings. You can adjust these defaults as needed. Make all instance modifications on the **Instance settings** window. From the **Placement details** screen, click the Waterfall instance you want to modify.

{% hint style="info" %}
You can only modify pricing and targeting settings for Waterfall instances.
{% endhint %}

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/S5gaLcIdipFkSId5WTXA/15127024651164" alt="Instance Settings window"></div>

<details>

<summary><strong>Pricing</strong></summary>

When adding an instance, the DT Console applies Auto CPM by default. Auto CPM automatically adjusts the CPM based on historical pricing. While DT gathers pricing data to determine the best CPM, DT applies the Worldwide CPM. Once the DT Console gathers enough data to make CPM predictions, the instance shifts to use the CPM determined by Auto CPM.

If you do not want to use Auto CPM, deactivate Auto CPM, and manually enter either a Worldwide CPM or targeted CPMs. Additionally, some networks (Google Ad Manager and BIGO Ads) do not support Auto CPM and require you to manually enter a CPM.

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/hsQBGEUkATm0KFXCFrW9/15126823509788" alt="Pricing method for instances"></div>

### Applying Manual Worldwide Pricing

To apply manual worldwide pricing:

1. Ensure that the **AUTO CPM** checkbox is deselected.
2. Enter the CPM for the **Worldwide** entry.
3. Click **Save**.

### Applying Manual Pricing by Country

To apply manual pricing by country or region:

1. Ensure that the **AUTO CPM** checkbox is deselected.
2. Click **Add countries**.\
   A list of countries available for targeting displays.

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/2xBGfH5FZMX0bcR8eaBa/15127040022428" alt="Countries for Targeting" width="188"></div>

3. Select the countries or regions you want to target.\
   As you select countries, they move to the top of the list.
4. In the **CPM** field, enter the CPM for the selected countries.
5. Click **Apply**.
6. Repeat Steps 2-5 until you have specified all of your CPM targets.\
   The list of countries in the Pricing sections updates as you add targets, and the `Worldwide` target changes to `Rest of the World`.
7. Click **Save**.

</details>

<details>

<summary><strong>Targeting</strong></summary>

You can target the availability of the instance by country or user type. Modify all Instance targeting settings in the **Targeting** section of the **Instance settings** window.

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/15jPVog8fYVxEltPZ3Rt/15126872666652" alt="Instance Targeting Options"></div>

### Targeting Instance by Country

The DT Console defaults to exclude no country or region. You can include or exclude countries or regions as needed.

### Targeting Instance by User Tracking Status

To target by User Tracking status, select the tracking status for which you want to allow this instance.

1. Under **TARGET BY USER TRACKING STATUS**, select the tracking status for which you want to allow this instance.
2. Click **Save**.

</details>

## Activating and Deactivating an Instance

Deactivated instances are not mediated, and you cannot modify the settings of a deactivated instance.

On the **Placement details** screen, deactivated bidding instances display as greyed-out rows, while deactivated waterfall instances are hidden from the list of instances. To display deactivated waterfall instances, click the show/hide instances icon ( <img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/RVJCvLmlW0J6CQjstYjI/19580178799516" alt="2025-02-03_20-43-28.png" data-size="line"> ). All deactivated instances are labeled as `INACTIVE`.

<div align="left" data-with-frame="true"><img src="https://content.gitbook.com/content/LbREhkP3WlLtP6TNVZ2Q/blobs/uWAOClXpOQHWUlK8Ilmj/15610052529436" alt="Click this icon to show or hide inactive instances."></div>

To deactivate an instance:

1. On the **Placement details** screen, locate the active instance you want to deactivate.
2. Click the three-dot menu for the instance, and click **Deactivate**.\
   A confirmation message appears.
3. Click **Confirm**.\
   The instance is now deactivated.

To activate an inactive instance:

1. On the **Placement details** screen, locate the inactive instance you want to activate.
2. Click the three-dot menu for the inactive instance, and click **Activate**.\
   The instance is now an active instance for mediation.

## Deleting an Instance

Deleting an instance stops mediation of the placement on the network.

{% hint style="success" %}
If you want to stop mediation of the placement while preserving settings such as pricing, targeting, instance names, and IDs, consider deactivating the instance instead of deleting it. For more information, see [Activating and Deactivating an Instance](#activating-and-deactivating-an-instance).
{% endhint %}

To delete an instance:

1. On the **Placement details** screen, locate the instance you want to delete.
2. Click the three-dot menu for the instance, and click **Delete**.\
   A confirmation message appears.
3. Click **Confirm**.\
   DT no longer offers the placement for mediation on the network.
