> 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/testing-and-switching.md).

# Testing and Switching

EdgeTag streams event data from your site to the marketing platforms of your choice. However, before switching your live campaigns to EdgeTag's data stream, you need to validate data quality through parallel testing. 

We recommend that you run EdgeTag alongside your existing tracking infrastructure, feeding the B/test pixel on Meta, secondary conversions on Google Ads, and running incremental flows in Klaviyo, all while your live campaigns continue running on your current data stream.  This side-by-side comparison reveals whether EdgeTag captures incremental conversions and improves attribution accuracy. When test results confirm measurable lift, migrate your live campaigns to EdgeTag. This validation process typically takes 1-2 weeks.

Follow the guides below to complete testing on each platform.

{% hint style="info" %}
Connect your Klaviyo account to accelerate results. By syncing your existing Klaviyo contacts, we'll build a more complete customer identity graph from day one, helping you see performance lift faster.
{% endhint %}

{% hint style="info" %}
Add payload validator for custom / headless setups if you have not done so already. This will help you in observation / validation step outlined above.<br>
{% endhint %}

{% content-ref url="/pages/KdCP6TkQ1duXdLekaL42" %}
[Meta](/onboarding/e-commerce/testing-and-switching/meta.md)
{% endcontent-ref %}

{% content-ref url="/pages/dm3I5vboCMH4XPzzDQo0" %}
[Google Ads](/onboarding/e-commerce/testing-and-switching/google-ads.md)
{% endcontent-ref %}

{% content-ref url="/pages/TbZwqw7KdFX8g9zFePLr" %}
[Klaviyo](/onboarding/e-commerce/testing-and-switching/klaviyo.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 dynamically 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/testing-and-switching.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 `build a script that syncs our docs to a CMS` 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.