> 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/custom-landing-page.md).

# Custom Landing page

EdgeTag's apps and plugins automatically capture all standard e-commerce events out of the box. For most merchants, installation is truly zero-code with complete funnel coverage from the moment you install our app or plugin.

However, modern e-commerce funnels often extend beyond a single core platform. Many brands use landing page builders (Webflow, Unbounce, Wix), pre-checkout page builders (Replo, Funnelish, Fermat), post-purchase checkout solutions (Checkout Champ, Cartrush), or multi-domain architectures.

When your funnel includes these elements, EdgeTag requires additional configuration across all your platforms to maintain complete visibility throughout the customer journey.

Navigate to the service/scenario you see in your funnel, and follow the provided implementation steps. During setup, use our [Validation Docs](https://docs.edgetag.io/implementation/validation) to make sure all events in your funnel are captured and your customer journey is visible.&#x20;

Don’t see your platform or setup here?&#x20;

Get in touch with the EdgeTag team on [Slack](https://join.slack.com/t/blotout-shared/shared_invite/zt-3gpja9dut-vQ4enN3EcGRg~q5roDAlmg) for assistance.


---

# 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/custom-landing-page.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.
