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

# Website integration

Control how the Crobox snippet runs on your website.

**Website integration** controls how the Crobox snippet runs on your website: which pages it recognizes, where experiences can appear, what makes them appear, and the general settings of your container.

Open **Settings → Website integration**. Its tabs:

| Tab                                                                                                    | What it's for                                                                                |
| ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- |
| [**General**](https://docs.crobox.com/how-to-guides/settings/website-integration/general.md)           | Your container's name and URL, allowed origins, session and reporting settings, and privacy. |
| [**Actions**](#actions)                                                                                | What the snippet does on your page, such as rendering an experience.                         |
| [**Dependencies**](#dependencies)                                                                      | The Crobox packages your website loads.                                                      |
| [**Page Types**](#page-types)                                                                          | How Crobox recognizes each type of page on your website, such as product or listing pages.   |
| [**Extractors**](#extractors)                                                                          | How Crobox reads information from your pages, such as product IDs.                           |
| [**Triggers**](#triggers)                                                                              | What makes an experience appear, such as a page type loading.                                |
| [**Placeholders**](https://docs.crobox.com/how-to-guides/settings/website-integration/placeholders.md) | The places on your pages where experiences can appear.                                       |

### How changes go live

* **General** settings take effect as soon as you click **Save**.
* Changes in the other tabs are saved to a new draft version of your website integration. They go live on your website when you publish that version in [**Settings → Versions**](https://docs.crobox.com/how-to-guides/settings/versions.md).

{% hint style="warning" %}
Check your changes in a preview before you publish. A published version applies to every visitor on your website.
{% endhint %}

### Actions

An **action** is something the Crobox snippet does on your page, such as rendering experiences into a placeholder or sending an event. Each action runs when the triggers listed under **Activated by** fire. The tab lists each action's **Name**, **Type**, **Activated by**, and **Status**.

{% hint style="info" %}
The Crobox team sets up actions with you during onboarding. Contact your Customer Success Manager to change one.
{% endhint %}

### Dependencies

**Dependencies** lists the Crobox packages your website loads, such as the packages that render Product Finders and Sagent, with their **Version**.

{% hint style="info" %}
The Crobox team manages your dependencies. Contact your Customer Success Manager to add or update a package.
{% endhint %}

### Page Types

A **page type** tells Crobox what kind of page a visitor is on, such as a product detail page, a product listing page, or the cart. Experiences use page types to decide where they appear, and analytics use them to break down results by page. Your website reports the page type with every pageview; see [Event Tracking Implementation](https://docs.crobox.com/getting-started/first-steps/event-tracking-implementation.md).

To add one, click **Add Page type** and fill in:

* **Code** - The number your website sends for this page type in the pageview. It can't be changed after saving.
* **Abbreviation** - A short label, such as *PDP*.
* **Name** - The full name, such as *Product Detail Page*.

Page types are used in a campaign's **Locations** step, on [placeholders](https://docs.crobox.com/how-to-guides/settings/website-integration/placeholders.md), and in the **Page type** filter of a trigger.

{% hint style="warning" %}
A page type only works if your website sends its **Code**. Check with your developer before adding one.
{% endhint %}

### Extractors

An **extractor** reads a piece of information from your page, such as the product ID of each product tile on a listing page. Placeholders and actions use extractors to know which product they're showing an experience for. The tab lists each extractor's **Name**, **Level**, **Status**, and when it was last updated.

{% hint style="info" %}
The Crobox team sets up extractors with you during onboarding. Contact your Customer Success Manager to change one, for example after a redesign of your website.
{% endhint %}

### Triggers

A **trigger** decides when something happens on your page: when a placeholder becomes active, or when an action runs. It combines one or more events with optional filters. Each trigger shows its **Name**, events, **Filters**, and **Status**: **Active** when a placeholder or action uses it, **Inactive** when none does.

To create one, click **New trigger**, enter a **Name** that says when it fires, such as *PDP – page loaded*, and select:

* **Triggers** - The events it listens for: **DOM ready** (the page has loaded), **Crobox Event**, **Click**, **Page Visiblity**, **Delay**, **History Change** (the URL changes without a page load), **Script Ready** (the Crobox snippet has loaded), or **Mutation** (an element appears on the page). Some events have their own settings.
* **Filters** (optional) - Where it may fire: **Page type**, **Page URL**, **Market** country or language, **CSS Exists**, or a **Conditional** rule.

Use a trigger by selecting it under **Activated by** on a [placeholder](https://docs.crobox.com/how-to-guides/settings/website-integration/placeholders.md) or an action. To remove one, open the menu at the end of its row and select **Remove**. Check its **Status** first: removing an **Active** trigger stops the placeholders and actions that use it.


---

# 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.crobox.com/how-to-guides/settings/website-integration.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.
