> 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/spotify/onboarding.md). # Onboarding Spotify channels offer a simple onboarding experience through direct pixel ID configuration, which connects your Spotify pixel with EdgeTag. This integration enables your site to send events to Spotify's analytics platform. Let's walk through the process. ### Video Guide {% embed url="" %} ### Authorization To add a channel, begin by entering the channel's name. We recommend choosing a name that is descriptive and clearly describes the purpose of the channel integration. This will assist with debugging if any issues arise. Once you have entered the name, next we need to add the Spotify Pixel ID.

### Spotify Pixel ID This is your unique identifier from Spotify's analytics platform that enables event tracking on your website. The Pixel ID is used to configure the Spotify pixel script and associate all events from your site with your specific Spotify account. You can find your Spotify Pixel ID in your Spotify Ad Studio dashboard under the **Ad Analytics Dashboard → Manage → Your Pixels** section.

### Enable browser pixel? This is checked by default; no action is required from your end. This checkbox enables browser-side pixel tracking for your website. {% hint style="warning" %} This is checked by default and cannot be unchecked. Spotify currently only supports browser pixel integration. {% endhint %}

Click "Save & Deploy." Congratulations, the setup is now complete. --- # 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://docs.edgetag.io/channels/spotify/onboarding.md?ask=&goal= ``` `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.