> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/pricing-experiences/price-testing-integration-guides/integration-guide-using-checkout-scripts/step-5-qa-your-integration-and-publish-your-changes.md).

# Step 5: QA your integration, and publish your changes

After you have completed all previous integration steps, go through your store using Preview Mode in (you can access preview mode by clicking on the Eye icon next to your test, or by adding /?ig-preview=true to the end of your website's URL) and make sure everything looks correct. Follow our QA checklist [here](/pricing-experiences/price-test-qa-checklist.md)!

Once you have verified Intelligems is fully integrated, you can publish your theme changes (if you haven't already) and start your test from the Intelligems App! Check out our step-by-step guide on doing this [here](/pricing-experiences/pricing-experiences-overview/starting-a-price-test.md).

#### What happens next?

Now that you've started your first test, here are some things to do next:

* Check the Analytics Dashboard in the Intelligems app to see how the test is doing frequently. Note that it may take one to two hours for data to flow in!
* Start thinking about your [testing roadmap](/general-features/best-practices/test-design-best-practices.md).
* Review some [test suggestions](/general-features/common-use-cases.md).


---

# 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.intelligems.io/pricing-experiences/price-testing-integration-guides/integration-guide-using-checkout-scripts/step-5-qa-your-integration-and-publish-your-changes.md?ask=<question>&goal=<user_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.