> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/list-growth/opt-in-tools-popup-preview.md). # Opt-in Tools - Popup Preview ### Table of Contents 1. [Overview](#overview) 2. [What Popup Preview Shows](#whatpopuppreviewshows) 3. [How to use Popup Preview](#howtousepopuppreviews) 4. [Testing the Full Popup Flow](#testingthefullpopupflow) 5. [Supported Opt-In Tools](#suportedoptintools) 6. [Preview Device Sizes](#previewdevicesizes) 7. [Preview vs Live Behavior](#previewvslivebehavior) 8. [When to Use Popup Preview](#whentousepopuppreview) 9. [Common Use Cases](#commonusecases) 10. [Best Practices](#bestpractices) ### ### Overview Popup Preview allows you to see exactly how your popup will appear to visitors before it is published. This helps you validate layout, copy, buttons, images, and overall flow without affecting live traffic. Using Preview is strongly recommended before activating or editing any popup, especially for time-sensitive campaigns or compliance-related changes. ### ### What Popup Preview Shows Popup Preview lets you render a popup **directly from the editor** in a safe testing mode. The preview opens in a **new browser window** and renders the popup on **your live website** in a safe testing mode. This allows you to: * See how the popup looks in its **real environment** * **Test designs instantly** without waiting for triggers * Review popups **without affecting analytics** or visitors Preview mode: * Ignores all trigger logic (entry, exit intent, scroll, timing, frequency) * Does not generate impressions, conversions, or revenue metrics * Works for draft and inactive popups ### How to Use Popup Preview 1. Go to [**Opt-in Tools**](https://app.recart.com/optin-tools) **→ Popups** in your Recart dashboard 2. Open the popup you want to review 3. Click **Preview** in the editor ![PopupPreview](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FAv0EhloS383OsbmTuX0Q%2Fopt-in-tools-popup-preview-1.png?alt=media) 4. Review the popup as it would appear to a visitor 5. Make any adjustments and preview again before saving or publishing You can preview as many times as needed — previews do **not** impact live traffic or targeting rules. ### Testing the Full Popup Flow Popup Preview allows you to test the entire popup journey using mock data. You can safely walk through: * Multi-step popups * Email + phone collection * Verification and success steps **Mock data behavior:** * Email: any format is accepted * Phone number: must be valid format, but no message is sent * Verification code: auto-filled as 123456 This makes it possible to validate full flows end-to-end before publishing. ### Supported Opt-In Tools Popup Preview supports: * All popup types, including gamified popups * Custom popup implementations Popup Preview does **not** support Landing pages and Embedded forms. These tools use a different editor and cannot currently be previewed. ### Preview Device Sizes Popup Preview uses standard screen resolutions: * **Mobile:** 390 × 844 * **Desktop:** 1440 × 899 The preview matches the editor view: * Editing mobile → mobile preview ![PopupPreview1](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2F73eeTlZuUrAn7x1cgUvV%2Fopt-in-tools-popup-preview-2.png?alt=media) * Editing desktop → desktop preview ![PopupPreview2](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fn0wridD2vYP0na1en1ub%2Fopt-in-tools-popup-preview-3.png?alt=media) ### Preview vs Live Behavior (Important) Popup Preview is designed for **visual and content validation only**. Please note: * Preview does **not** apply targeting rules (geolocation, device, frequency, force-true logic, etc.) * Preview does **not** confirm whether a popup will trigger on your site * Preview does **not** replace live testing in a controlled environment * Preview reflects your **current draft configuration**, not historical versions. If a popup looks correct in Preview but does not appear live, review: * Targeting settings * Active popups that may be taking priority * Frequency and display rules Some cookie consent services may interfere with Popup Preview. If you encounter any issues, clear cookies for the site and try again and/or use a US-based VPN (issue appears less common from US IPs) ### When to Use Popup Preview We recommend using Preview: * Before publishing a new popup * After editing copy, CTAs, or discount codes * Before activating seasonal or promotional popups * When troubleshooting layout or content issues ### Common Use Cases * Checking that discount messaging matches the correct offer * Confirming success steps and confirmation text * Reviewing brand consistency across popups * Validating multi-step flows before launch ### Best Practices * Always preview after making edits — even small ones * Use Preview before asking Support to confirm targeting behavior * Pair Preview with a quick live test using controlled conditions where possible If you have any questions, please feel free to contact us, we are always happy to help. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://help.recart.com/list-growth/opt-in-tools-popup-preview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.