> 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/versions.md).

# Versions

Publish your website integration and review its history.

**Versions** is where your [website integration](https://docs.crobox.com/how-to-guides/settings/website-integration.md) goes live. Changes you make in its tabs, such as a new placeholder or trigger, are saved to a draft version. Your website keeps running the published version until you publish the draft.

Open **Settings → Versions**. The top of the page shows the **Published Version** and who published it. Each row is a version, with when it was **Created**, when it was **Published**, and its **Status**: **Published**, **Draft**, or **Unpublished**.

### Review a version

Click a row to expand it. It shows the version's **Version Message** and a table of what changed compared with the version before it, or **No differences**.

### Publish a version

{% stepper %}
{% step %}

#### Review the changes

Expand the draft version and check its changes.
{% endstep %}

{% step %}

#### Describe the release (optional)

Add a **Version Message**, or click **Generate message** to draft one from the changes.
{% endstep %}

{% step %}

#### Publish

Click **Publish version**. You can also publish from the menu at the end of a row.
{% endstep %}
{% endstepper %}

Publishing an older version is how you roll back.

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

### Unpublish

Select **Unpublish** in the menu of the published version. To confirm, type your container's name in **Confirmation text**.

{% hint style="danger" %}
Unpublishing disables all campaigns and tracking. Your experiences are no longer visible and no data is collected until you publish a version again.
{% endhint %}

### Delete a version

Select **Delete** in the menu of a version that isn't published, and confirm by typing your container's name. Deleting removes that version's settings and can't be undone.

{% hint style="info" %}
Publishing, unpublishing, and deleting versions need publish permission.
{% endhint %}

### Frequently asked questions

<details>

<summary>I published an experience, but my changes aren't live. Why?</summary>

Crobox publishes in two places:

* **An experience**, such as a Campaign, Finder, or Sagent, is published from its own page. This covers its own settings, such as targeting and content.
* **Your website integration** is published here, in Versions. This covers everything experiences rely on, such as components, placeholders, triggers, and page types.

If you changed something in both, publish both. For example, after changing the component a campaign uses, publish the campaign and then the draft version here.

</details>

<details>

<summary>Do General settings go through Versions?</summary>

No. Changes in **Website integration → General** take effect when you save them. Versions covers the other Website integration tabs.

</details>

<details>

<summary>Do I publish campaigns and Finders here?</summary>

No. Each experience has its own versions and is published from its own page. Versions here covers your website integration, including the components your experiences use.

</details>


---

# 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/versions.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.
