---
title: "Preview"
description: "Try an Experience with different answers, customer states, and purchase outcomes."
search:
  tags: ["Features"]
  keywords: ["simulated purchase", "test persona", "run log"]
---

Preview lets you use an Experience before publishing it. Enter answers, follow its branches, and try purchases without charging anyone. You can also set up different customer personas to see how the same Experience behaves for a new user, a subscriber, or someone assigned to another Experiment variant.

<span id="try-the-main-path" />

## Run the Experience

Open the Experience and choose **Preview**. It starts at the entry point and follows the screens and actions you've configured. Choose **Stop preview** to return to the Canvas.

The controls show the current screen and whether the run is **Interactive** or **Ended**. When it ends, the last screen stays visible alongside the exit reason. **Restart** starts a new run from the beginning.

If you edit the flow while previewing, **Journey changed** appears. Choose **Restart to pick up** to start using the new version of the flow.

<span id="try-other-paths" />

## Branches and state

Open **Preview as…** to choose the customer state for a run. For example, you could add a past `workout_completed` event for a returning user, then compare their route with a new user who has no event history.

### Customer persona

**Traits** supplies values for conditions, and **History** supplies past event names and how long before the run they occurred. Turn on **Subscribed** to start with purchases available to restore.

Choose **Apply & restart** to run the Experience with those settings. **Save as** saves a named persona to the Project for reuse. **Reset** clears the draft persona settings.

### Experiment variants

**Experiments** can assign a variant automatically or use a specific variant you choose. Select a variant when you want to inspect its screens directly without waiting to be assigned to it.

<span id="color-scheme-and-content" />

### Content

You can enter different answers, including long text, to see how personalized content wraps and how it affects the route.

## Simulated purchases

A purchase or restore action opens a simulated sheet. Choose **Buy** or **Restore** to follow the success path, **Cancel** to follow cancellation, or **Simulate failure** in the additional options to follow the failure path. A subscribed persona gives you existing purchases to restore.

> **Note**
>
> These choices update the preview's state. They don't charge a customer or verify a transaction with the store, so you can try each outcome while working on the flow.

## Run Log

Select the run status to open **Run Log**. It shows the screens visited, actions taken, branch decisions, waits, and the reason the run ended. This is useful when a screen leads somewhere you didn't expect or a branch doesn't open.

A visited screen with a saved checkpoint offers **Restart from here**. It restores the state from that visit, so you can try a later part of onboarding again without re-entering all the earlier answers.

When the flow is waiting, **Skip** moves the preview clock through that wait. You can use it to try timed behavior without waiting for the full duration.

<span id="test-the-integration" />

## App integration

Preview helps you work on the Experience itself. SDK delivery, audience eligibility, real store purchases, and App Action handlers also depend on your installed app and its integration.

[Publish a version](/docs/guides/publishing) and follow [Testing in your app](/docs/guides/testing-in-your-app) to try those parts together. For a paywall, a store test purchase covers checkout and the Feature access granted afterward.