# QA step In AB Tasty, the QA (Quality Assurance) process allows you to preview and test your campaign privately, so only you (and anyone you specify) can see the changes. Here’s how it works: * Activate QA Mode: From the “QA & Overview” step, enable one or more QA parameters—by URL parameter, IP address, or cookie. This makes the campaign visible only to you or your team, not to your site visitors. * Use the QA Assistant: The QA Assistant helps you check that all changes, targeting, and tracking are set up correctly. You can see which campaigns are live on the page, verify targeting and segmentation, and ensure all events (like clicks or transactions) are tracked as expected. * Test on Desktop and Mobile: The QA Assistant works on both desktop and mobile, letting you browse your site as a user would and confirm everything displays and functions properly. * Advanced Checks: For more technical validation, you can use your browser’s console to inspect which campaigns and variations you’re assigned to, and to troubleshoot any issues with targeting or tracking. * Finalize QA: Once you’re satisfied, simply exit QA mode to prepare your campaign for launch. Curious to learn more or need step-by-step instructions? Explore our articles on QA Mode & QA Assistant, using the browser console for QA, and troubleshooting common QA issues. These guides will help you confidently validate your campaigns before they go live --- # 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://docs.abtasty.com/web-experimentation-and-personalization/qa-step.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.