> For the complete documentation index, see [llms.txt](https://docs.digia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digia.tech/digia-engage/user-guides/live-testing.md).

# Live Testing Campaigns

Live testing lets you send a saved campaign from the Digia Engage dashboard to a connected debug device. Use it before launch to check the campaign UI, variables, screen targeting, and device behavior without waiting for the campaign to go live through your campaign platform.

Live tests use the campaign's current saved setup. This means you can test drafts and recent edits on a debug device before activating the campaign.

If you are setting up Guides or Inline campaigns, review synced pages, anchors, and slots in [Component Registry](/digia-engage/user-guides/component-registry.md) before testing. That keeps live tests focused on real app components that campaign builders can safely use.

{% hint style="warning" %}
Live testing works only with debug builds. Release builds do not connect as live test devices.
{% endhint %}

## Before You Start

Make sure you have:

* Access to the correct Digia Engage project.
* A debug build of the app installed on the device you want to test.
* The app opened at least once after installation.
* The campaign saved in Digia Engage.
* Test values ready for any variables used in the campaign, such as `first_name`, `coupon`, or `expiry_time`.

For iOS, you also need the app's URL scheme, for example `acmeapp` if the app opens links like `acmeapp://`.

{% hint style="info" %}
If the QR opens a browser page but cannot open the app, the app's debug settings link may not be wired yet. Complete the [SDK Debug Settings](/digia-engage/developer-guides/debug-settings-deeplink.md) setup and try again.
{% endhint %}

## 1. Connect A Debug Device

In the Digia Engage dashboard, open the project and go to **Test & Debug**.

This page shows a QR code that opens the SDK debug settings screen on your test device. From that settings screen, enable **Sync**. When Sync is connected, the device can receive live campaign tests.

<figure><img src="/files/mEyxqaw2vDVhsr9T75I8" alt="Digia Engage Test and Debug page with iOS QR setup and a connected live device"><figcaption><p>Use Test &#x26; Debug to open the SDK settings screen and see connected live devices.</p></figcaption></figure>

{% tabs %}
{% tab title="Android" %}

1. Select **Android**.
2. Open the debug build once on the device.
3. Open the device camera and scan the QR code.
4. Open the link.
5. Tap **Open app** on the Digia connect page.
6. Enable **Sync** on the SDK debug settings screen.
   {% endtab %}

{% tab title="iOS" %}

1. Select **iOS**.
2. Enter the app's URL scheme, for example `acmeapp`.
3. Press **Enter** to generate the QR code.
4. Open the debug build once on the device.
5. Open the device camera and scan the QR code.
6. Open the link.
7. Tap **Open app** on the Digia connect page.
8. Enable **Sync** on the SDK debug settings screen.
   {% endtab %}
   {% endtabs %}

After Sync connects, the device appears in the **Live devices** section.

<figure><img src="/files/ymOYn5v1Jz11Y1rSMZaQ" alt="Digia Debug Settings screen showing Sync enabled and Live test connected"><figcaption><p>Enable Sync in the SDK debug settings screen. Live test should show as connected.</p></figcaption></figure>

{% hint style="info" %}
If the device does not appear, keep the app open, confirm you are using a debug build, check that Sync is enabled, and make sure the device is connected to the same Digia Engage project.
{% endhint %}

## 2. Send A Campaign Test

You can start a live test from the campaign builder or from **Test & Debug** after a device is connected.

When the **Test on device** modal opens:

1. Confirm the campaign name.
2. Select one or more connected devices.
3. Enter test values for variables, if the campaign uses them.
4. Select **Test**.

<figure><img src="/files/05VqtWuUeXz5WH8IxHPf" alt="Test on device modal with connected device selection and variable values"><figcaption><p>Select the connected device and add variable values before sending the live test.</p></figcaption></figure>

{% hint style="info" %}
If **Test** is disabled, select at least one connected device and fill any required variables.
{% endhint %}

{% hint style="info" %}
If the device list is empty, go back to **Test & Debug**, scan the QR again, and confirm the SDK settings screen shows Sync enabled.
{% endhint %}

## 3. Check The Result

After you send the test, watch the dashboard status and the test device.

| Status          | What it means                                                                                                                                    |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Sent**        | Digia sent the test request to the selected device connection.                                                                                   |
| **Received**    | The SDK received the test payload.                                                                                                               |
| **Shown**       | The campaign was rendered on the device.                                                                                                         |
| **Failed**      | The SDK could not show the campaign. Check the reason shown in the dashboard.                                                                    |
| **Unconfirmed** | Digia did not receive a response from the device quickly enough. The device may have disconnected or the app may not have acknowledged the test. |

{% hint style="info" %}
If the test stays unconfirmed, keep the app open in the foreground, confirm Sync still shows as connected, and send the test again.
{% endhint %}

## Common Issues

| Issue                                                 | What to check                                                                                                                           |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| QR opens a browser page but not the app               | The debug settings deep link may not be wired. See [SDK Debug Settings](/digia-engage/developer-guides/debug-settings-deeplink.md).     |
| Device does not appear in Live devices                | Use a debug build, open the app once, scan the QR again, and enable Sync in SDK settings.                                               |
| Device appears, but the campaign does not show        | Make sure the app is on a screen where the campaign can render. For tooltips, the required anchor key must exist on the current screen. |
| Campaign uses variables but renders with missing text | Enter values for every variable in the test modal before sending the test.                                                              |
| Test fails immediately                                | Check the failure reason in the dashboard. Common causes are missing variables, unsupported template setup, or no matching screen.      |
| Works on one device but not another                   | Confirm both devices are using a debug build with the SDK version that supports live testing.                                           |