# Experience Preview > **SUCCESS** > > **Before Delivering the Experience** > > You can check the experience content and display conditions using the following 2 methods. > > Preview environment > > Production environment After completing the editing of an experience, many people are concerned about whether the experience content is displaying properly and whether it is displaying according to the configured display conditions. This article will guide you on how to confirm the display results **between preview and after actual delivery**. ## How to Check in Preview **1. Click the preview icon** **2. Scan the QR code or open the preview link** If checking on a smartphone, use the QR code; if checking on a PC, open the link. In the case of preview, the specified page conditions and user conditions are not reflected; however, in the case of pop-ups only, the display/stop conditions are reflected. > **WARNING** If multiple test patterns exist, please specify the pattern before opening the preview. (If you are not conducting A/B tests or redirect tests, pattern selection is not necessary.) ## How to Check in Production Environment This is a method of actually delivering the experience using test parameters and confirming the display condition. By adding arbitrary test parameters to the page conditions, you can check the delivery status of the experience without worrying about being seen by general users, in the same way as general users. **Open the settings screen for the experience you want to check** **Specify the delivery ratio of the pattern you want to check as 100%** > **WARNING** If it is not an A/B test or redirect test experience, this operation is not necessary. For A/B test or redirect test experiences, if you want to check either pattern, please set the delivery ratio of the pattern you want to check to "Custom" → "100%". (After verification is complete, do not forget to return the delivery ratio to its original setting.) **Add an arbitrary test parameter string to the page conditions** In the page conditions, please add additional conditions to the settings. Example: Contains "ptengine\_test" (test parameter) And please save. The test parameter string can be arbitrary. The purpose is to avoid visits from general users. **Open a URL that matches the page conditions specified in step 3 and check the display status of the experience** After the above settings are complete, please publish the experience and check the display status. > **INFO** In the case of the example in step 3 above, please access a URL with "?ptengine\_test" added to the end of the page URL you originally want to deliver. Example: "" > **INFO** If you want to check a specific ad traffic channel, please open a URL like the one below based on operational rules such as UTM parameters. Example: "" **5. Stop delivering the experience and return the settings to their original state** Once you have confirmed the display, please perform the following operations and then publish. 1. For A/B tests, return the delivery ratio settings to their original state 2. Delete the test parameter settings added to the page conditions If you are concerned about the data measured during test verification, we recommend that you copy the experience and publish it again. --- # 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/preview.md?ask= ``` 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.