> For the complete documentation index, see [llms.txt](https://helps.ptengine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helps.ptengine.com/en/experience/campaign/delivery-conditions.md). # Experience Distribution Condition Settings ## Experience Distribution Condition Settings > **SUCCESS** > > **In the article "Experience Creation Management Screen"** > > The basic flow of experience creation is introduced below. This article provides detailed explanations of items 2, 3, and 4 in the flow below. > > Create, edit, and adjust distribution content > > Specify the distribution page range (Page Conditions) > > Specify the target users for distribution (Target Users) > > Specify the goal of the experience > > Final confirmation on the preview screen and publish > > If you would like to check via video, please see Chapters 3 and 4 below. *** > **SUCCESS** **Text↓↓↓** ## **Page Conditions** Page Conditions are important settings that determine which pages your created experience will be displayed on. #### Assignable Patterns **All Pages** 🌐 Apply to all pages where the Ptengine tag is inserted ``` Note: It will not be displayed on pages without tags ``` **Specific Pages** 🎯 Specify by combining matching rules and URL status ``` Use case: Display restrictions based on login status or specific conditions ``` #### How to Specify URL Conditions For details, refer to the [Matching Rules](/en/experience/campaign/delivery-conditions.md) article. > **DANGER** > > **Important Notes** > > Ptengine tag is required: Experiences will not be displayed on pages without tags > > Page editing experience limitations: If the edited content does not exist on the target page, it will not be displayed > **WARNING** When creating a new page edit, the URL you enter is solely for editing purposes. You must specify the pages for distributing the experience in the Page Conditions. **URL Structure** URLs typically consist of the following parts: Protocol (http\:// or https\://) Domain name (e.g., [www.ptengine.jp](http://www.ptengine.jp))) Path (e.g., /blog/article) Query parameters (starting with ? and separated by &) **Example** **Original URL** ``` ``` **URL After Parameter Removal** ``` ``` #### **Page Condition Checker** The "Page Condition Checker" is a tool used in Ptengine Experience's page condition settings to verify that the intended conditions are entered correctly. By using this tool, you can easily confirm the actual distribution target pages. **Input Conditions** After entering the page conditions, click the "Check Page Conditions" button. **Input the Actual URL** After the checker expands at the bottom of the screen, enter one actual page URL where you want to distribute the experience. **Result Confirmation** Click confirmation, and the result will be displayed below. > **INFO** URLs can only be entered one at a time, and the history of this operation remains at the bottom. > > Additionally, if the page conditions entered above are changed, the results at the bottom will be updated accordingly. \*Regular expression validation can also be done with tools like [this](/en/experience/campaign/delivery-conditions.md). ## **Target Users** Target User settings are an important feature that determines who the experience you created in Ptengine Experience will be displayed to. By setting appropriate target users, you can realize more effective marketing strategies. ### Assignable Patterns **All Users 👥** All users who visit the site as is ``` Note: Tracking users who visit pages without the Ptengine tag is not possible ``` **Specific Users 🎯** Specify with user segments Existing user segments can be used ``` You can also create a new segment on the spot ``` For more details on user segments, please refer to the article [here](/en/experience/campaign/delivery-conditions.md). ## **Bulk Paste Display Conditions** When dealing with complex URL structures or ID lists, you can significantly improve work efficiency by utilizing the "Bulk Paste Display Conditions" feature in Ptengine Experience. This feature is particularly useful when dealing with large amounts of data or when complex condition settings are needed. ### Bulk Paste Use Cases 🎯 **Pop-up for Visitors to Product Detail Pages** Set multiple product page URLs at once **Page Display Based on Specific ID Lists** Utilize ID lists compiled in Excel files and similar #### Steps Organize data in list format using Excel or a text editor Paste into the page conditions or target users input field \*Pasted data will be automatically processed as OR conditions > **WARNING** **Note:** > > When setting page conditions or target users, if you want to add AND conditions, click "＋Add Condition" to add a new row. ## **Experience Goal** Experience Goal settings are extremely important elements for effectively utilizing Ptengine Experience. By setting appropriate goals, you can accurately evaluate the success of your experience and link it to continuous improvement. ### Importance of Goal Setting 🎯 **Clarification of Success Metrics** Make the effect of the experience concretely measurable **Identification of Improvement Points** Understand at which stage of the user journey improvement is needed **ROI Calculation** Quantify the return on investment of marketing initiatives ### Goal Attribution Mode (View Conversion / Click Conversion) Experience Goals support an "attribution mode" that lets you choose **how a conversion is counted** per experience. For experiences with clickable elements (popups, bars, etc.), you can switch it under the goal's **Advanced settings** (the default is **View Conversion**). ![](/files/vP7Jfh06qgtH5JKwIA6x) * **View Conversion**: users who reach the goal after seeing the experience * View Conversion Rate ＝ converted UU ÷ view UU (users who saw the experience) * **Click Conversion**: users who reach the goal after clicking a button/link in the experience * Click Conversion Rate ＝ converted UU ÷ interaction UU (users who clicked a button/link in the experience) {% hint style="info" %} * Experiences without clickable elements (inline / redirect, etc.) do not show the mode option and continue to display as **Goal Reached**. * Click Conversion is measured using data from June 22, 2026 onward. Periods before that are shown as out of measurement scope. {% endhint %} ## **Schedule** In Ptengine Experience, you can flexibly set the distribution schedule for your experience. By setting distribution days of the week and time periods, you can also streamline the management of regular distribution/stops. \*This setting is optional. **Date and Time Settings** You can specify the start and end dates and times Ideal for campaigns and seasonal limited offers **Distribution Days of the Week and Time Periods** Automatic distribution/stop on specific days of the week or time periods Effective for regular promotions and time period-specific optimization **Time Zone**: You have the following 2 options. **Align with the project's time zone (Default)** Characteristics: All times are unified in the project's time zone ``` Data from different time zones is also converted ``` Benefits: High data consistency ``` Easy to manage the entire project ``` **Align with the visitor's time zone** Characteristics: Distribution adjusted to each visitor's local time Points to Note: There may be time differences in report data Benefits: Optimization of user experience ``` Effective timing distribution by region ``` When choosing, consider the balance between data consistency and user experience. Method 1 is easier for managing the entire project, but select Method 2 if you want to align with users' local time.