> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/congratulations-youre-productive.md).

# Congratulazioni! Sei produttivo!

Congratulazioni! Ora che hai dato il via al tuo programma, sei pronto ad ampliare le tue partnership, esplorare nuove opportunità e far crescere ancora di più il tuo marchio.

Sentiti libero di consultare l'ampio [centro assistenza](https://help.impact.com/) per ulteriori conoscenze, best practice e approfondimenti su come utilizzare al meglio il programma in base alle tue esigenze.

Se vuoi iniziare anche uno degli altri tipi di programma, dai un'occhiata alla guida pertinente qui sotto:

* [Sono anch'io nuovo di Creator](/brand/it/what-would-you-like-to-learn-about/creator-program/introduction-welcome-to-creator.md)
* [Sono nuovo anch'io di Advocate](/brand/it/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate.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://help.impact.com/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/congratulations-youre-productive.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.
