> For the complete documentation index, see [llms.txt](https://tappadsdocs.gitbook.io/tappads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tappadsdocs.gitbook.io/tappads/advertisers/instructions-for-integration/sdk-integration-instructions/steps-for-testing-the-integration.md).

# Steps for Testing the Integration

1. **Creating a Test Offer**
   * To verify your integration, we create a test offer named **Your Project Test**.
   * This offer is available in our test publisher.
2. **Using the Test Publisher**
   * For testing, please use our test publisher: @tappads\_bot.
   * Inside the test publisher, you will find your offer **Your Project Test**.
3. **Conducting Testing**
   * Check your integration using the target actions you have configured in the SDK.
   * Ensure that event data is sent correctly and appears in the analytics system.
4. **Reporting Results**
   * After completing the testing, inform us of the results via our chat.
   * In your message, state that the testing is complete and describe what exactly was tested.
5. **Final Verification**
   * We will perform our own testing of your offer to ensure the integration works correctly.
   * If all checks are passed successfully, your offer will be launched.

> Important: Please perform testing only through the test publisher to avoid incorrect data and errors.


---

# 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://tappadsdocs.gitbook.io/tappads/advertisers/instructions-for-integration/sdk-integration-instructions/steps-for-testing-the-integration.md?ask=<question>&goal=<endgoal>
```

`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.