> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/siblings/product-siblings/siblings-metafields.md).

# Siblings metafields

{% hint style="info" %}
Our companion app for Broadcast, [Presidio+](https://presidiodev.com/install-presidio-plus), simplifies setting up siblings.

We created Presidio+ help setup advanced features such as siblings. It creates metafields automatically and guides you through setup.

The app is free during Early Access and sibling integrations will always remain free. Presidio+ users also benefit from access to a premium support inbox.

[<img src="https://2636770384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsD7BEEDU3B7WiEJlN0F7%2Fuploads%2FfRFemChP0E6kuJpVPsAb%2Fbadge-shopify-app-store-light.svg?alt=media&amp;token=172cd3aa-135d-49d6-93b0-17845ab51fa7" alt="" data-size="original">](https://presidiodev.com/install-presidio-plus)
{% endhint %}

> Feature introduced in Broadcast v3.5

There are two product metafields definitions required to connect each of the products together and generate linked swatches.

Use the **Metafields and metaobjects** editor under **Settings** in the **Shopify Admin**:

<figure><img src="https://2636770384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsD7BEEDU3B7WiEJlN0F7%2Fuploads%2FVVpUicY8sZFuw1ohqH6e%2Fmetafields-and-metaobjects.jpg?alt=media&amp;token=b58b2e0d-b382-4479-9dd2-55632e886354" alt=""><figcaption></figcaption></figure>

Both metafields will be defined under the category of Products:

<figure><img src="https://2636770384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsD7BEEDU3B7WiEJlN0F7%2Fuploads%2FEezzLzsG1SSaTVtYsvHk%2Fproducts.jpg?alt=media&amp;token=ee5032f4-c5b2-4ab9-a068-6320da2d3bc8" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Tip: If you are new to creating custom metafields, a good step-by-step walkthrough is also available in the [Upselling with metafields ](https://broadcast.presidiocreative.com/promotions/upselling/upselling)article.
{% endhint %}

Next, create these two metafields:

{% embed url="<https://broadcast.presidiocreative.com/siblings/product-siblings/siblings-color>" %}

{% embed url="<https://broadcast.presidiocreative.com/siblings/product-siblings/siblings-collection>" %}


---

# 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://broadcast.presidiocreative.com/siblings/product-siblings/siblings-metafields.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.
