> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/web-experimentation-and-personalization/qa-step.md). # QA step QA step in a campaign configuration is essential to ensure your campaign works as intended before it goes live. 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 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.abtasty.com/web-experimentation-and-personalization/qa-step.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.