Live Testing Campaigns
Test Digia Engage campaigns on connected debug devices before launch.
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 before testing. That keeps live tests focused on real app components that campaign builders can safely use.
Live testing works only with debug builds. Release builds do not connect as live test devices.
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, orexpiry_time.
For iOS, you also need the app's URL scheme, for example acmeapp if the app opens links like acmeapp://.
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 setup and try again.
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.

Select Android.
Open the debug build once on the device.
Open the device camera and scan the QR code.
Open the link.
Tap Open app on the Digia connect page.
Enable Sync on the SDK debug settings screen.
Select iOS.
Enter the app's URL scheme, for example
acmeapp.Press Enter to generate the QR code.
Open the debug build once on the device.
Open the device camera and scan the QR code.
Open the link.
Tap Open app on the Digia connect page.
Enable Sync on the SDK debug settings screen.
After Sync connects, the device appears in the Live devices section.

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.
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:
Confirm the campaign name.
Select one or more connected devices.
Enter test values for variables, if the campaign uses them.
Select Test.

If Test is disabled, select at least one connected device and fill any required variables.
If the device list is empty, go back to Test & Debug, scan the QR again, and confirm the SDK settings screen shows Sync enabled.
3. Check The Result
After you send the test, watch the dashboard status and the test device.
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.
If the test stays unconfirmed, keep the app open in the foreground, confirm Sync still shows as connected, and send the test again.
Common Issues
QR opens a browser page but not the app
The debug settings deep link may not be wired. See SDK Debug Settings.
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.
Last updated