# Management Screen Before and After Creating an Experience

### Creating Your First Experience

When you create an experience for the first time in Experience, click Experience > Experience Management to see the following screen.

On this screen, select the type of campaign you want to create:

1. Web Engagement
2. Page Edit
3. A/B Test
4. Redirect Test

In addition to the campaign types listed above, you can also select campaigns by theme from the templates at the bottom of the screen. However, the available campaign types are limited to the four listed above.

### Creating a Second Experience or More

You will be on the same Experience > Experience Management tab, but if experiences have already been created, the screen will look as follows.

In this case, click the green button in the upper right corner to create a new experience.

After clicking the create button, you will be taken to the campaign type selection screen (shown above).

## Management Screen After Creating an Experience

After configuring and saving the experience content (such as popups or page content changes), you will proceed to a screen with the following important settings.

On this screen, you can configure the following items:

* Detailed Settings
* Experience Creation
* Page Conditions
* Target Users
* Experience Goal
* Schedule
* Publish

### Detailed Settings

Ptengine Experience provides a description feature and a label feature for each experience to make management easier when many experiences are being delivered.

In the Detailed Settings section, you can add a description and labels for each experience.

#### Description

Click the edit button to the right of Detailed Settings to display a field where you can add a description.

We recommend including the background, purpose, changes made, and hypotheses (in the case of A/B tests) for this experience.

Feel free to customize the description according to your team's or company's needs.

#### Labels

When many experiences are being delivered across teams, we recommend using the label feature so that each team member can easily find the experiences they have created.

Labels are typically assigned by team, page, purpose, or similar categories.

**Creating a Label**

Enter a label name in the green text field and click the area highlighted in red in the screenshot to create the label.

**Assigning Labels**

You can assign multiple labels to a single experience.

**Editing and Deleting Labels**

Hover over the label you want to edit or delete, and pencil and trash can icons will appear on the right side.

Click the respective icon to edit the label name or delete the label.

### Experience Creation

In the Experience Creation section, the number of items (1 through 6 in the screenshot) varies slightly depending on the type of experience.

We will use an A/B test experience as an example.

#### 1. Settings

You can configure the A/B test distribution ratio, minimum delivery time, and anti-flicker feature ON/OFF.

For details on each setting and how to configure them, please refer to [this article](https://www.notion.so/experience-campaign-abtest-overview-9ae8007761f146bfb791a5251afbad9c?pvs=21).

#### 2. A/B Test Toggle

When an A/B test experience is created, this toggle is automatically turned ON.

Turning it OFF will delete all test patterns except the control pattern.

If all patterns are test patterns, all patterns except the top one will be deleted.

To stop an A/B test, please stop each individual experience.

{% hint style="warning" %}
In some cases, data may also be deleted. We recommend keeping this toggle ON whenever possible.
{% endhint %}

#### 3. Preview

Click the eye-shaped icon to generate a preview link and QR code.

We recommend using this to verify the behavior before going live.

For more details on preview features, please refer to [this article](/en/experience/campaign/preview.md).

#### 4. Pattern Settings

Each pattern has a vertical three-dot icon.

Click here if you need to delete an unnecessary pattern or rename a pattern.

#### 5. Editing the Experience

If you need to modify content that has already been edited, click the pencil icon.

Clicking here will open the editor.

#### 6. Adding Patterns

You can add up to 5 patterns per experience. Including the control group, you can deliver up to 6 patterns simultaneously.

For more details on adding patterns, please refer to [this article](/en/experience/campaign/create-new-2/creative-production.md#patnno).

### Page Conditions

In Page Conditions, you can specify which pages the content edited in this experience will be displayed on.

### Target Users

In Target Users, you can configure who will see this experience.

### Experience Goal

For A/B tests and redirect tests, setting an experience goal is required.

### Schedule

In Schedule, you can specify the start time, stop time, and delivery frequency for the experience.

<mark style="background-color:green;">For detailed instructions on configuring the four items above, please refer to</mark> [<mark style="background-color:green;">this article</mark>](https://gitlab.com/PtmindDev/ptx/ptengine-helps/-/blob/main/DOCS/en/experience/campaign/set-delivery-conditions.md)<mark style="background-color:green;">.</mark>

### Publish

If the experience editing is incomplete or there are issues (missing settings), an alert will be displayed as shown below.

If an alert appears, follow the instructions to complete the settings.

If there are no issues, check the confirmation items and publish.

## Basic Flow for Creating an Experience

Regardless of the type of experience you create, the general process follows these steps:

1. Create, edit, and adjust the delivery content
2. Specify the delivery page scope
3. Specify the target users
4. Set the experience goal
5. Verify on the preview screen and publish

In the following articles, we will explain the detailed creation process for each experience type, following these basic steps.

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helps.ptengine.com/en/experience/campaign/management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.