# SKAdNetwork Testing on the Demand Test App
The [DT Exchange Demand Test App](https://docs.digitalturbine.com/dt-exchange/advertisers/dsp-test-app) allows you to test your SKAdNetwork setup on Digital Turbine to confirm the proper tracking of installations with Apple's SKAdNetwork framework. DT has two methods to test SKAdNetwork on DT's Demand Test App:
* Option 1: [Manually testing the SKAdNetwork bid response](#manually-testing-the-skadnetwork-bid-response)
* Option 2: [Programmatically testing the SKAdNetwork bid response](#programmatically-testing-the-skadnetwork-bid-response)
## Manually Testing the SKAdNetwork Bid Response
Manually testing the SKAdNetwork bid response setup allows you to:
* Configure data on the [Web Tool](https://forest.fyber.com/demand#/login).
* Send data to DT's Demand Test App by scanning the QR code.
* Send data to DT's servers, which triggers DT's internal bidder.
* Override DT's internal SKAdNetwork setup when you add `bid.ext.skadn.dfs` to key-value pairs. This allows SDK to fire your SKadNetwork parameters and receive postbacks at your endpoint.
To manually test your SKAdNetwork bid response:
1. Download and install the latest version of DT's Test App on your device, as described in [Downloading the Demand Test App](https://docs.digitalturbine.com/dt-exchange/advertisers/dsp-test-app/..#step-1-download-the-demand-test-app).
2. In the Demand Test App [Web Tool](https://forest.fyber.com/demand#/login), select **Creative Tester**.
3. Click **CREATE** to add a new creative.
4. In the description field, add a description for your creative.
5. To add extra properties, click **+** (plus).
6. From the accordion drop-down list below, select your SKAdNetwork version and add the required key-value pairs:
{% hint style="info" %}
Note the following:
* Source App: If you use `sourceapp=0`, you may receive Error 851.\
Ignore this error and check if the postback sends a notification after completing this procedure.
* Nonce: `nonce` value must be unique each time you test and cannot be zero. Use `nonce =str(uuid.uuid4())` to generate a new nonce for each test.
* Signature: Valid signatures are usually 72 -76 characters when you use a p192 private key with a p192 constant.
{% endhint %}
SDKAdNetwork 2.0 and 2.1
The following table describes the Keys and Values for SDKAdNetwork 2.0 and 2.1.
| KEY | VALUE |
| -------------------------- | ---------------------------------------------------------- |
| `bid.ext.skadn.sourceapp` | Your source app or `0` |
| `bid.ext.skadn.itunesitem` | Your itunesitem |
| `bid.ext.skadn.network` | Your SKAdNetwork ID |
| `bid.ext.skadn.nonce` | Your nonce |
| `bid.ext.skadn.signature` | Your signature |
| `bid.ext.skadn.version` | `2.0` or `2.1` |
| `bid.ext.skadn.campaign` | Campaign name |
| `bid.ext.skadn.dfs` | Enter `a` to override DT's SKAdNetwork setup with your own |
| `bid.ext.skadn.timestamp` | Your timestamp |
SKAdNetwork 2.2
The following table describes the Keys and Values for SDKAdNetwork 2.2, which uses a `fidelities` based bid response:
| | |
| -------------------------- | ----------------------------------------------------------- |
| `bid.ext.skadn.sourceapp` | Your source app or `0` |
| `bid.ext.skadn.itunesitem` | Your itunesitem |
| `bid.ext.skadn.network` | Your SKAdNetwork ID |
| `bid.ext.skadn.version` | `2.2` |
| `bid.ext.skadn.campaign` | Your campaign ID |
| `bid.ext.skadn.dfs` | Enter `a` to override DT's SKAdNetwork setup with your own. |
Add the following to test a single `fidelities` type (SKAdImpression or SKAdNetwork for StoreKit):
| | |
| --------------------------------------- | -------------------------------------------------------------------------------------------------- |
| `bid.ext.skadn.fidelities[0].nonce` | nonce |
| `bid.ext.skadn.fidelities[0].signature` | Signature |
| `bid.ext.skadn.fidelities[0].timestamp` | Timestamp |
| `bid.ext.skadn.fidelities[0].fidelity` | SKAdImpression: Value = 0.
SKAdNetwork for StoreKit: Value = 1
|
Add the following to test both `fidelities` types together:
| | |
| --------------------------------------- | -------------------------------------------------------------- |
| `bid.ext.skadn.fidelities[0].nonce` | The nonce for SKAdImpression Fidelity |
| `bid.ext.skadn.fidelities[0].signature` | The signature for SKAdImpression Fidelity |
| `bid.ext.skadn.fidelities[0].timestamp` | The timestamp for SKAdImpression Fidelity |
| `bid.ext.skadn.fidelities[0].fidelity` | Enter a value of 0. This captures your SKAdImpression fidelity |
| `bid.ext.skadn.fidelities[1].nonce` | The nonce for StoreKit Fidelity |
| `bid.ext.skadn.fidelities[1].signature` | The signature for StoreKit Fidelity |
| `bid.ext.skadn.fidelities[1].timestamp` | The timestamp for StoreKit Fidelity |
| `bid.ext.skadn.fidelities[1].fidelity` | Enter a value of 1. This captures your StoreKit fidelity |
7. Click ✔ (check icon) after adding each key-value.
8. To add extra rows, increase the row display from five to ten, then click **CREATE SKADN**.
