> 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/knowledge-base/ecommerce-best-practice-for-first-time-setup/add-more-channels.md).

# Add more channels

Add more channels now that your customer funnel and ID Graph is operational

**Critical Note**: like we did with Meta, Google, and GA4, ensure that your channels do not have duplicated data or conversions with the rest of the channel setup.

To add more channels you can follow general instructions;

1. For top of funnel channels like TikTok, Snapchat, etc. you have to use ONLY one stream of data \[ like Blotout ] and you CANNOT have two sets of data
   1. For Bing and other bottom funnel conversion systems ensure ONLY one set of conversions are primary
2. Note: we support Meta Leads but not via this setup, you can email [here](mailto:support@blotout.io) with Subject: Meta Leads support required
3. For other channels just follow instructions in our [docs](https://docs.edgetag.io/)

If you need paid support email [here](mailto:support@blotout.io) or join community Slack [here](https://join.slack.com/t/blotout-shared/shared_invite/zt-1u7acylg2-uLRq7g~fVi_zhJzzGjh~bw) 


---

# 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/knowledge-base/ecommerce-best-practice-for-first-time-setup/add-more-channels.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.