# Dynamic Responses

*I work for a games company which runs interactive puzzle rooms. We have a new experience where players have to scan various objects with a sci-fi device (a modified android phone) to view security and interview footage. Each object will have a discrete NFC tag on it and We have the footage as unlisted videos on YouTube. Each tag needs to point to a different YouTube video and ideally, we should be able to manage it all without having to scan each tag.*

> **We needed all our tags to go to the same Website, but each tag then needed to go to a unique page.**

With all our videos on YouTube, we looked at the URL's for a few videos and noticed that **each one was similar** but had **a different code at the end**. We decided that the best way to do this in ixkio would be using **Subtags.** 

We put all our **Footage Tags** into a **Tag Group** and put them into two **Batches:** 

* Interview
* Security

In the **Tag Group** we then set the **Rule Set Default URL** to the generic part of the YouTube URL (<mark style="background-color:green;"><https://www.youtube.com/watch?v=></mark>).

We then went into both **Batches** and downloaded the **Tag Encoding Data.** This would let us use **Associate Data** to make sure that every tag contained a code for a different YouTube video. We decided to use the **Customer Unique ID (CUID)** to store our unique YouTube code.&#x20;

And so, in the Tag Group, at the end of our YouTube URL we put a **Subtag** so that the **CUID code** would automatically be added to the URL (<mark style="background-color:green;"><https://www.youtube.com/watch?v=></mark><mark style="background-color:orange;">{cuid}</mark>). Now we just needed to make sure each tag had YouTube video code as it's **CUID**.

Next we opened the first **Tag Encoding Data** we'd downloaded into Excel and we found the **CUID Column.** We kept the **XUID** and **CUID** columns, so the data could be matched up to the tags, but we deleted the other columns that we didn't want to change along with the **Batch Name** at the top.&#x20;

Using the **Tag Encoding Data** we'd downloaded, we found the **CUID** column and pasted each YouTube code against an **XUID**.&#x20;

We also put the video title against the **Tag Name** so we could keep track of them in ixkio.

Once we'd put all the codes into our trimmed back **Tag Encoding Data** spreadsheet, we saved it under a new name (e.g. InterviewUIDs) and opened up ixkio again.&#x20;

We found the **Batch** we download the **Tag Encoding Data** from, went to **Associate** and clicked on **Choose File.** We selected our **UID** data file (InterviewUIDs) and then, on ixkio, clicked the **Associate Tags** button.

Each Tag now had a **CUID** which was also a YouTube video code.&#x20;

To check, we opened up a random tag and clicked the dropdown arrow next to the **XUID**, found in the **Tag Detail** box. We copied the URL, pasted it into our browser, and it linked through to one of our videos with the same title as the **Tag Name** we'd put in for it.

{% content-ref url="/pages/sLR5FeGK6xEYv2LsgOIl" %}
[Broken mention](broken://pages/sLR5FeGK6xEYv2LsgOIl)
{% endcontent-ref %}

{% content-ref url="/pages/JO3Q28IXpITKUTAd4e8G" %}
[Subtags](/features/subtags.md)
{% endcontent-ref %}

{% content-ref url="/pages/5zI3iFfSh0PWk2SYKdzx" %}
[Creating a Rule](/features/rules/creating-a-rule.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ea5GmQw4cIVwYsbP0WUr" %}
[Associate Data](/features/associate-data.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ixkio.com/explainers/use-cases/dynamic-responses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.