> For the complete documentation index, see [llms.txt](https://docs.cooltix.com/cooltix-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cooltix.com/cooltix-support/organizers/marketing/website-integration.md).

# Website integration

With web integration it is possible to integrate the ticket sales into other websites by using a widget. This way customers make the purchase on the website the sales is integrated into with the widget, and will not be redirected to the Cooltix site.

When the widget is generated, you have to copy and paste it into the code of the target website to the spot where the widget should appear. The code can be copied anytime in the future, so you can change the colors whenever you want to.

### Creating a widget

You can create a widget for each event on the admin site:\
**Event / Invite and promote / Web integration**

### Widget theme and color

When creating the widget, you can choose if you prefer light or dark theme, and you can also set your primary color to match the style of your website.

### Integration type

You can choose between two integrations: showing the list of the ticket directly on your website, or put a button what opens the ticket list in a new window.

### Updating the widget to a new version

Widget automaticaly updates itself to the latest version, you don't have to do anything to make it happen. If you are using the old legacy Cooltix widget, then you can simply create a new widget, and replace the old on your website, and widget will update itself in the future.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cooltix.com/cooltix-support/organizers/marketing/website-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
