> 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.md).

# Scaling Playbook

You've switched your Meta, Google Ads, and Klaviyo campaigns to EdgeTag's data stream; now it's time to scale. With clean, reliable conversion data powering your core channels, the next phase is expanding this foundation across your entire growth strategy.

This section provides playbooks for the most common scaling scenarios, **from connecting additional advertising platforms to optimizing for new customer acquisition** to implementing multi-country tracking.&#x20;

Each playbook addresses a specific growth lever with step-by-step implementation guidance.

Navigate to the scaling scenario that matches your current growth priority. Don't see your use case? Join our community[ Slack](https://join.slack.com/t/blotout-shared/shared_invite/zt-3gpja9dut-vQ4enN3EcGRg~q5roDAlmg) to discuss custom implementation strategies with our team and other EdgeTag users.

Refer to the guide below if you are looking to switch TikTok, Pinterest, Snapchat, and other advertising/retention/analytics platforms to your EdgeTag data stream.&#x20;

{% content-ref url="/pages/vRp3IbGXBAKQobl3qanz" %}
[Expanding to more channels](https://docs.edgetag.io/onboarding/e-commerce/scaling-playbook/expanding-to-more-channels.md)
{% endcontent-ref %}

Follow the guide to create custom conversion events to optimize campaigns specifically for new customer acquisition, not returning customers.

{% content-ref url="/pages/2EAhmoxYZPmaldpSXOqU" %}
[Optimize for New Customer acquisition](https://docs.edgetag.io/onboarding/e-commerce/scaling-playbook/optimize-for-new-customer-acquisition.md)
{% endcontent-ref %}


---

# 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.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.
