> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/marketers-and-editors/ab-testing/front-end-rendering.md).

# Front end Rendering

Umbraco Engage takes care of applying the correct styles to the pages part of your A/B tests.

The A/B Test will automatically be rendered in your front end. If you have set up a [Single page A/B test](/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/single-page-ab-test.md) Umbraco Engage will automatically render the correct properties.

If you have set up one of the other tests and added some CSS and JavaScript this will automatically be added to your webpage.

You do not have to do anything to render the A/B test. If you want to run a more advanced A/B test that requires more coding, you can always do that.


---

# 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.umbraco.com/umbraco-engage/marketers-and-editors/ab-testing/front-end-rendering.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.