π·οΈMetadata Tags
Metadata Tags in Euno allow you to extend and customize the data model by adding your own tags to resources. These tags can be used to categorize, organize, and filter resources based on your organization's specific needs.
Domains: Metadata tags are scoped to domains. Each tag belongs to a domain. If your account has more than one domain, you will see a domain selector when creating tags. See Domains for more information.
Types of Metadata Tags
Metadata tags come in two main categories:
Fixed Tags
Fixed tags allow users to manually set values for resources. These include:
Single Select: Choose one option from a predefined list
Multi Select: Choose multiple options from a predefined list
Date/Time Field: Date and time values
Fixed Boolean: True/False values
Number: Numbers only
Text Field: Free form text value
Active Tags
Active tags automatically calculate their values based on defined rules:
Categorical Assigned Value: Multiple values based on EQL conditions
Live Boolean: True/False based on an EQL condition.
Propagated Tags: Propagate a boolean value based on the value of a resource
AI Select: A single/Multi Select tag that is based on the result of an LLM prompt
Coalesce: Automatically picks the first non-null value from a list of properties (e.g., use "display name" if set, otherwise "name", otherwise "id")
Creating a Metadata Tag
To create a new metadata tag:
Select the "Metadata Activation βMetadata Tags" option from the side menu
Click the "Create a new tag" button found in the top right hand corner of the screen
If your account has more than one domain, select the Domain for this tag. Tags are scoped to domains; each tag belongs to one domain.
Enter the basic information
Enter a unique Name for the tag.
EQL name is automatically set by Euno based on the name provided by the user. The EQL name is used when querying with EQL.
(Optional) Add a Description to help other users understand the tag's purpose. Providing a description also improves the accuracy of Euno's natural language search results.
Owner is automatically set by Euno and is attributed to the user who creates the metadata tag.
(Optional) Enable Push proactively to ensure this tag is always included in API responses to AI agents, even when the agent has not explicitly requested it. Use this to surface important metadata to AI agents. See Push Proactively for more details.
(Optional) Configure Group to organize the tag within the side panel. Select an existing group or create a new one.
(Optional) Enable Visible in Data Model if you want this tag to appear in the resource overview panel. This is especially useful if the tag is used as a compound tag (a tag created for the purpose of building another tag).
Add tag Details
Select tag Type
Enter the Values for the metadata tag
To create a Category Assigned Value (Active Tag) metadata tag:
Add the Value Name (e.g. mart layer)
Add the EQL associated with the Value Name (e.g.,
name ~ "mart"β any model with a name like "mart" will be tagged with the category name).To add an additional category, click on the
buttonTo reorder the values (which affects the order in which they are assigned to resources), click the
or down
arrows within the value's box.To delete a category, click on the
located within the value's box.When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Live Boolean (Active Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="dbt_model"β applies only to dbt models).Add the logic for the positive EQL statement using the True If text box (e.g.,
tags in ("sales data")β this means the tag will evaluate to true if the resource has the tag "sales data", and false if it does not, applicable only to dbt models).When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Propagated Boolean (Active Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="dbt_model"β applies only to dbt models).Add the Propagating Resource, which is the resource from which you wish to propagate (e.g.,
contains_pii is trueβ will propagate the value ofcontains_pii)Add the Propagation Direction, which is the direction from the propagated resource than you want to propagate towards (e.g. from PII it would be downstream towards a Dashboard, and from a Dashboard it would be downsteam towards a dbt Model [highly used, etc.])
Add the Propagation Type, which determines whether it is enough for one upstream/downstream resource that is propagated to meet the condition (e.g. PII usually requires at least 1) vs if ALL upstream/downstream resources that propagate meet the condition (e.g. a Certified dashboard is one that ALL upstream resources are from the Gold Layer).
To create an AI Select (Active Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="dbt_model"β applies only to dbt models).Add the Properties to Include, which are the resource properties that the LLM will need access to in order to classify the resource (e.g.
raw_code)Add the Prompt, which is the directive to the LLM with instructions on how to decide what the expected output of each resource should be, based on the supplied properties.
Add the Options, which are the possible values that the tag can receive.
To create a Coalesce (Active Tag) metadata tag:
Add the Scope, which is an optional EQL expression that limits which resources this tag applies to (default:
truefor all resources).Add the Properties to Include, which are two or more indexed properties of the same type, in priority order. The tag's value will be the first property's value, unless it is null, in which case it will use the second property's value, and so on. Order matters: the first non-null value wins.
Use the up/down arrows to reorder properties as needed.
When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Single Select (Fixed Tag) metadata tag :
Add the Tag Scope, which is an EQL statement that defines what this tagapplies to (e.g.,
type="looker_dashboard"β applies only to Looker Dashboards).Add the Values, which are the options that the tag can be set to.
To add a value, click on the
buttonTo delete a value, click on the
buttonWhen satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Multi Select (Fixed Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="tableau_workbook"β applies only to Tableau Workbooks).Add the Values, which are the options that the tag can be set to.
To add a value, click on the
buttonTo delete a value, click on the
buttonWhen satisfied with the definition click "Save" found in the bottom right hand corner of the screen.\
To create a Date & Time (Fixed Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this Tag applies to (e.g.,
type="tableau_workbook"β applies only to Tableau workbooks).When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Fixed Boolean (Fixed Tag ) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="dbt_model"β applies only to dbt models).When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Number (Fixed Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="dbt_source"β applies only to dbt sources).When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
To create a Text (Fixed Tag) metadata tag:
Add the Tag Scope, which is an EQL statement that defines what this tag applies to (e.g.,
type="dbt_source"β applies only to dbt sources).When satisfied with the definition click "Save" found in the bottom right hand corner of the screen.
Managing Metadata Tags
Once a metadata tag has been created, it will be displayed in the Tag Manager table found in the Metadata Tags screen. This table displays:
Tag name
Description
Owner
Group
Visibility
The table can be filtered by type or group, and can be searched by the tag name. From this table, you can delete, edit, or copy tags from the action list.

To view how a specific tag is configured, click on the tag, and you will be redirected to the tag's screen. This page has three sections:
Information: Displays the basic details about the tag, including:
Description
Creation time and date
Owner
EQL name
Grouping
Visibility
Push proactively status
Insight: Shows a bar chart that breaks down the various resources within the scope, tagged with different values.
Configuration: Displays the configuration of the tag. In this section, the user can click the 'Edit Tag' button, if they have the correct permissions to edit the tag's details.

Editing a Metadata Tag
To edit an existing metadata tag:
Navigate to the Metadata Tags screen.
Click on the action icon in the row for the tag you wish to edit, and select "Edit" from the drop-down list.
Modify the settings as needed.
Click "Done" to apply your changes.
Note: Some settings, like the tag type, cannot be changed after creation.
Deleting a Metadata Tag
To delete a metadata tag:
Navigate to the Metadata Tags screen.
Click on the action icon in the row for the tag you wish to delete, and select "Delete" from the drop-down list.
A dialog box will appear, asking you to confirm: "Are you sure you want to delete this metadata tag? This action cannot be undone."
Confirm the deletion by clicking "Delete."
Note: Deleting a metadata tag will remove all its values from resources. This action cannot be undone.
Creating a New Metadata Tag Using an Existing One as a Template
If you wish to create a new metadata tag based on the logic of an existing tag, you can generate a template from the existing tag.
To create a template from an existing tag:
Navigate to the Metadata Tag screen.
Click on the action icon in the row for the tag you wish to use as a template, and select "Use as Template" from the drop-down list.
Once the template is created, fill in the additional details to create the new metadata tag.
Setting Fixed Tags
Unlike Active Tags, Fixed tags are not set automatically. Instead, each tag must be manually set for every resource. To set a manual tag, follow these steps: once created, navigate to the data model screen, search for the desired resource, and open the side panel. In the 'About' section at the top of the side panel, metadata tags are listed. Expand the tag group where the fixed tag was set, and click on the tag to configure the desired values.

If you cannot locate the fixed tag, it may be hidden. Simply click 'Show # unset values'. If the tag still isn't visible at the resource level, it's possible that the resource isn't within the scope of the tag, and you may need to edit the tag to expand its scope.

Push Proactively
Metadata tags can be marked to push proactively. Properties with push proactively enabled appear in responses to AI agents, even if the agent has not requested them. This is useful for ensuring that AI agents are always aware of important pieces of metadata when interacting with your data model.
When to Use Push Proactively
Enable push proactively when:
The tag represents essential context that AI agents should always consider (e.g., PII classification, data quality status, certification level).
You want to ensure that agents working with your data model are always informed about key governance or compliance metadata.
The tag is part of a workflow where missing context could lead to incorrect or incomplete agent responses.
How It Works
When a metadata tag has push proactively enabled:
API behavior: When users or agents query the data model search or single resource endpoints with a specific list of properties, properties with push proactively enabled are automatically added to the response β even if they were not included in the request.
Opt-out: API consumers can pass the
ignore_critical_properties=truequery parameter to suppress this behavior and only receive the explicitly requested properties.No effect when all properties are requested: If no specific properties are requested (i.e., all properties are returned), push-proactive properties are naturally included and the flag has no additional effect.
Setting Push Proactively
To enable push proactively for a tag, turn on the Push proactively toggle when creating or editing a metadata tag. This toggle is found in the tag creation/edit form, in the "AI interaction" section above the AI Instructions text box.
Best Practices
Clear Names: Use descriptive names that clearly indicate the tag's purpose
Documentation: Always add a description to help other users understand how to use the tag
Testing: For computed tags, test your EQL expressions with different scenarios
Organization: Use the "Visible" flag judiciously to avoid cluttering the UI
Maintenance: Regularly review and clean up unused metadata tags
Using Metadata Tags
Once created, metadata tags can be used in the following ways (in the scenario below, the metadata tag 'usage,' a category-assigned value, is being displayed):
Used as filters in the data model view

Added as columns in the tabular view

Viewed in the resource overview panel (if 'Visible' is enabled)

Used in other EQL expressions

Troubleshooting Metadata Tags
In certain cases where the metadata tag uses extreme EQL that traverses multiple relationships in various directions, the tag may time out. When this happens, users will see the following icon
both on the tag's page and in the main Tag Manager table.
If the EQL query used to calculate the tag times out after a one-minute delay, the user will see a yellow clock icon. Clicking this icon will display the following message: "The tag timed out while calculating, so the values might be delayed. Consider simplifying the EQL conditions. For more details, refer to the documentation."

In such cases, it's recommended to simplify the queries and create compound tags for better performance. For additional guidance, refer to the Optimizing Complex Searches section.
Last updated