> 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/fr/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/congratulations-youre-productive.md).

# Félicitations ! Vous êtes productif !

Félicitations ! Maintenant que vous avez lancé votre programme, vous êtes prêt à développer vos partenariats, à explorer de nouvelles opportunités et à faire rayonner encore davantage votre marque.

N’hésitez pas à consulter les nombreuses ressources du [centre d’aide](https://help.impact.com/) de impact.com pour approfondir vos connaissances et découvrir des bonnes pratiques et des conseils pour tirer le meilleur parti de votre programme, selon vos besoins.

Si vous souhaitez également vous lancer dans un autre type de programme, consultez le guide correspondant ci-dessous :

* [Je débute également avec Creator](https://help.impact.com/brand/fr/what-would-you-like-to-learn-about/creator-program/introduction-welcome-to-creator.md)
* [Je débute également avec Advocate](https://help.impact.com/brand/fr/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/fr/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.
