# Segment Version

## Overview

Every Segment includes a version number on the top-right corner of the screen. Once the Segment is published, the Version is set to **1**. This is Version 1.

## Version Number Location

After subsequent edits and only after publishing, the version number updates to the latest version—such as **Version 2**, **Version 3**, and so on.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2Fqkh16eZDfq7xCran2Ehr%2Fimage.png?alt=media&#x26;token=f0f48c1d-e1a8-4768-b5a5-6cc93d8e9090" alt=""><figcaption></figcaption></figure>

## Versioning Logic

* When a new Segment is created and published for the first time, it is assigned **Version 1**.
* Every time the Segment is edited and then published again, the version number increments:\
  **Example:** Version 2, Version 3, and so on.

#### **Note 1:**

For the default Segments, the version is always set to **“1”** because these are populated from the template.

#### **Note 2:**

Until the Segment is published, the status displays **Pending Publish**. Once the Segment is published in the staging or production environment, the status updates accordingly on the Segments screen.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FMNM1UgkBcO57olgvx87W%2Fversioning.mp4?alt=media&token=027d8d9c-8ef2-4106-bb2f-b2c2c1dcd335>" %}
