> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/duel/onboarding.md). # Onboarding Duel channel integration enables your site to send **Purchase** event to Duel with simple credential-based setup. ### Video Guide {% embed url="" %} ### Add Channel To add a channel, begin by entering the channel's name. We recommend choosing a name that clearly describes the channel you are adding. This will assist with debugging if any issues arise. Once you have entered the name, get an API user name and password from **Duel**
### **Get credentials of an API user** Log in to your **Duel** account, navigate to the **Settings** page by clicking **Organization settings** from the top bar **Profile** → **⚙ Settings**, and select **API User** here, you can create or use an existing user credentials (*Username* & *password*)
Copy the **Username & Password** of the user you wish to connect with EdgeTag.
Paste the **Username & Password** on the EdgeTag form Click **Save & Deploy** Congratulations :tada:, the basic setup is now complete.\ Let's proceed to the next section to explore additional configuration options. --- # 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.edgetag.io/channels/duel/onboarding.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.