> 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/onboarding/e-commerce/scaling-playbook/expanding-to-more-channels.md).

# Expanding to more channels

You've validated EdgeTag's impact on Meta, Google Ads, and Klaviyo. The same server-side data infrastructure can now powers 50+ advertising, retention, and analytics platforms with zero additional configuration.

EdgeTag's single data stream automatically transforms to meet each platform's API specifications, delivering the same signal quality improvements across your entire marketing stack. Whether you're adding TikTok for prospecting, Pinterest for catalog ads, or Amplitude for product analytics, the setup takes minutes and the performance lift is immediate.

### **Why expand your EdgeTag implementation:**

* Consistent signal quality: Same first-party data enrichment and match rates you see on Meta and Google Ads
* Zero marginal effort: No additional tracking setup. EdgeTag handles transformation and delivery for each platform, all you do is authenticate and configure
* Unified observability: Monitor delivery status and performance across all channels from a single dashboard

[View complete channel list and setup documentation →](https://docs.edgetag.io/channels)

<br>


---

# 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/onboarding/e-commerce/scaling-playbook/expanding-to-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.