Testing in your app
Run a published Experience with your app’s identity, events, and integrations.
Testing in your app lets you try an Experience with your real customer identity, events, and integrations. You can submit answers, open app screens, and complete a store purchase using the same paths your customers will use.
Use Preview while you’re working on the Experience, then publish it and run it in an installed app to try the connected behavior. For an update, Your device first lets you do this before selecting Go live.
Connection and presentation
To run your published Experience:
Publish for testing
Publish the Experience. For an update you want to try before release, choose Publish to → Your device first.
Configure the development build
Open Connect your app and configure your development build with the pk_test_ key under Debug builds. This build receives the preview version; release builds using the pk_live_ key continue receiving the production version.
Run as your test customer
Identify your test customer if the app uses signed-in accounts, then perform the app action that sends the Experience’s trigger.
If the SDK isn’t installed yet, start with the quickstart.
Use the test environment in Nuxie when looking up this customer’s activity and responses. Test and live data are separate, so a customer record in production won’t show what happened in your development build.
The panel shows Connected once your app reaches Nuxie with its publishable key. Shown appears when the app presents a version from the publish. These are separate steps: connecting the SDK makes delivery possible, and a matching trigger starts the Experience for a customer who qualifies.
App actions and purchases
Try the Experience’s screens and actions in your app. Actions handled by your integration, such as opening a particular app screen, need a matching handler. Store purchases run through the store or your configured purchase integration.
Use store test accounts for checkout. Verify iOS purchases covers buying, restoring, and checking the Feature access a purchase grants.
You can find collected answers in the published Experience’s Responses tab. If you’ve set a conversion goal, Nuxie measures it within its conversion window. Finishing the screens and reaching that goal are separate events; for example, a customer can leave a paywall and subscribe later within the window.
Test an Experiment variant
Open the Experiment card and expand Test on a device. Enter your customer or device ID, choose a Variant, and click Pin. The next eligible Journey for that identity uses the selected path, so you can try every variant without waiting for a random assignment.
Pinned customers are left out of Experiment results. Delete the pin when you want the identity to return to normal assignment. If a Journey is already running, it keeps its variant until it ends.
Eligibility
Your test customer follows the same audience and re-entry rules as other customers. Their profile shows the properties, Segment memberships, and previous Journeys that affect delivery.
Connected, but nothing appears
Check that your app sends the exact trigger event and uses the environment where you published the Experience. The Experience also needs to be within its schedule, unpaused, and available to that customer’s audience.
It only appears once
A One time Experience won’t start again for a customer who has already entered it. Once per window waits until the configured interval has passed. Open the customer’s Journeys tab to see their previous run and start time.
An offer is skipped
A customer who already owns the access an offer sells can skip it. Check the offer’s eligibility settings and the Feature it grants, especially when testing with an account you’ve already used for a purchase.
The previous version is still visible
Check which version is live and whether the Journey began before the update. An existing Journey can finish on its original version. Eligibility and re-entry explains when the same customer can start another one.