# Tags {% hint style="info" %} Read the [playwright-tags](https://docs.currents.dev/guides/playwright-tags "mention") guide {% endhint %} Tagging is a convenient way to augment your executions with extra data that can be helpful for managing your tests. You can tag the runs (executions) by adding `--tag tagA,tagB` flag. For example, running the next command `@currents/playwright` (version 1.7.0+): {% code overflow="wrap" %} ``` npx pwc --key RECORD_KEY --project-id PROJECT_ID --ci-build-id CI_BUILD_ID --tag run, tagA, tagB ``` {% endcode %} or for Cypress: ``` cypress-cloud run --parallel --record --tag run, tagA, tagB ``` would generate a run with the corresponding tags:

The run, spec and test execution recordings will inherit the tags. You can use the tags as a filter when browsing the dashboard to narrow down the results, for example: * filter runs by tags * filter insights and analytics to only include records with a particular tag * filter errors, tests and spec performance explorers to only include records with a particular tag The tags are also available as part of [http-webhooks](https://docs.currents.dev/resources/integrations/http-webhooks "mention") payload.

Example of filtering Run Status Metrics by Tags

--- # 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.currents.dev/dashboard/runs/tags.md?ask= ``` 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.