> For the complete documentation index, see [llms.txt](https://pipeline.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pipeline.groupthought.com/pipeline-5/products/additional-unique-content.md).

# Additional unique content

Pipeline includes a tag feature to allow extra unique product information to be displayed below the product images

{% hint style="success" %}
New in Pipeline 5.2
{% endhint %}

Many product page content features are shared with all products. What if you need unique content for some products and would like to display that additional information only on those product pages? Pipeline has a feature you can use to place that custom unique information below the product image area:

![](https://894491487-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LovEU3LvzkJzFkXarYD%2F-MeaaqRqXFFGEMk9mffL%2F-MeadK71L3E_xGFaAjuS%2FScreen%20Shot%202021-07-14%20at%201.10.11%20PM.png?alt=media\&token=c9211a25-f8d9-45e1-a763-b5fb4f64218a)

This space can be used for additional product information pertaining to this product alone. 

## How to

There are two components to setting up this feature:

1. Create a Shopify page for your custom content
2. Add a custom tag to the product

This feature is simple to setup and use. The first step is to create a Shopify page with the additional content you'd like to use. 

{% hint style="success" %}
Once you've created the page, we'll need to find the page handle. Click on Edit website SEO at the bottom of the page to find the page handle
{% endhint %}

Edit website SEO:

![Copy the handle to your clipboard](https://894491487-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LovEU3LvzkJzFkXarYD%2F-MeXMEvAOQjLpwUw0T7C%2F-MeXYZtZTPnQnrR3U5zE%2Fpage.gif?alt=media\&token=3e9ac548-0060-43f3-bd86-446f7c51549a)

#### Creating the custom tag

Once you have the page handle, we can create our custom tag which will be added to the product. 

Start your custom tag with: `_info_` and add your page handle after. For example, we'll use the page handle from the above page which is `detox-serum-extra-content`

{% hint style="success" %}
Completed handle: `_info_detox-serum-extra-content`
{% endhint %}

#### Add the tag to your product

Simply tag the product with this custom tag and the content from the page will appear on the product page. The page content will only appear on the page(s) that have this custom tag:

![Add the custom tag to the product](https://894491487-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LovEU3LvzkJzFkXarYD%2F-MeXMEvAOQjLpwUw0T7C%2F-MeXa5lbfl13CmL6bUgl%2Ftagged.gif?alt=media\&token=92d49a5f-5860-41e1-b7eb-fea7aa741ef4)

#### Result

![Content from page placed in addition to regular product description](https://894491487-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LovEU3LvzkJzFkXarYD%2F-MeXMEvAOQjLpwUw0T7C%2F-MeXawU3F-LRy9n-vlel%2FScreen%20Shot%202021-07-13%20at%206.21.52%20PM.png?alt=media\&token=87ed9621-6af8-44ab-9a71-07cb41f8d22e)

#### Tips

* If multiple products have the same content, use the same tag and add the tag to those products
* Create as many unique custom tags, one per page that you'll be using. 
* Remember, each tag must start with `_info_` and then followed by the page handle


---

# 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://pipeline.groupthought.com/pipeline-5/products/additional-unique-content.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.