> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/1.7/manual/components/coherence-tag-query.md).

# CoherenceTagQuery

In addition to filtering object by distance using a [LiveQuery](/1.7/manual/components/coherence-live-query.md), coherence also supports **filtering objects by tag** with **CoherenceLiveQuery**. This is useful when you have some special objects that should always be visible regardless of their position.

{% hint style="info" %}
The tag used by the **CoherenceTagQuery** component is **not** based on [Unity's tag system](https://docs.unity3d.com/Manual/Tags.html).
{% endhint %}

{% hint style="warning" %}
Having **at least one query** in the scene **is necessary** to receive any network update!
{% endhint %}

## Using TagQueries

To create a TagQuery, right click a GameObject in the scene and select *coherence > TagQuery* from the context menu.

<figure><img src="/files/VG4qcluDxBJxPUdRcOoV" alt=""><figcaption><p>CoherenceTagQuery component</p></figcaption></figure>

All networked GameObjects with matching tags will now be visible to the Client. The **coherence** tag can be any string and can be configured in the *Advanced Settings* section of the `CoherenceSync` component.

![](/files/cGKJ2K7omBpglMt2PmQx)

Tags and TagQueries can be updated at any time while the application is running, either from the Unity inspector or setting `CoherenceSync.coherenceTag` and `CoherenceTagQuery.coherenceTag` in code.

Currently, only a single tag per GameObject and TagQuery is supported. To include objects with different tags, you can create multiple TagQuery objects for each tag.

{% hint style="info" %}
In the future, we plan to integrate TagQueries with LiveQueries allowing combined query restrictions, e.g., only show objects with tag "red" within an extent of 50.
{% endhint %}

### Limits

The Replication Server imposes limits on number of queries a Client can create. Read more about it in the [Replication Server](/1.7/manual/replication-server.md#maximum-query-count-per-client) section.