> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Tags Overview, Klaviyo > Tags Overview. A governance table of Klaviyo tags and how many flows, campaigns, lists, and segments carry each one. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Email Marketing](/nerve-centre/connectors#connectors-by-type) > Not a performance metric, an organisation one. This is the map of how your Klaviyo account is labelled, and a quick way to spot tags that have sprawled or gone stale. ## At a glance > A table of the Klaviyo tags in the account, each shown with a count of how many objects carry it. Tags are labels applied to flows, campaigns, lists, and segments to keep a growing account organised, for example by team, by campaign theme, by season, or by client for an agency. This card is a governance and housekeeping view rather than a performance metric: it does not measure revenue or engagement, it measures structure. Reading it regularly catches tag sprawl, near-duplicate tags, and orphaned labels before they make the account hard to navigate. Sourced from `GET /api/tags`. | | | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Each tag in the account and the number of objects (flows, campaigns, lists, segments) that carry it. A structural inventory, not a performance figure. | | **API endpoint + statistics field** | `GET /api/tags` for the tag list and the counts of objects associated with each tag. | | **Email vs SMS aggregation** | Tags label objects regardless of channel, so a tag on a flow that contains both email and SMS steps is counted once for that flow. There is no channel split on this card. | | **What carries a tag** | Flows, campaigns, lists, and segments. The same tag can sit across several object types, so a count of, say, 12 may span flows and campaigns together. | | **Not a performance view** | Tags Overview does not report sends, opens, clicks, or revenue. For performance by tag, pivot to the per-object cards the tags point at. | | **Chart type** | Table. | | **Time window** | Real-time snapshot of the current tag structure. | | **Alert trigger** | None. This is a housekeeping view; act on it during account reviews rather than on alert. | | **Roles** | owner, marketing | ## Calculation Calculated automatically from your Klaviyo data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A mid-size beauty brand on Shopify whose marketing team has been tagging campaigns and flows for two years without a clean-up. Snapshot taken 12 Apr 26. All figures are illustrative. | Tag | Objects carrying it | Mostly applied to | | ---------------- | ------------------- | ----------------- | | `Welcome` | 6 | Flows | | `Abandoned Cart` | 4 | Flows | | `BFCM 2024` | 18 | Campaigns | | `BFCM 2025` | 21 | Campaigns | | `Black Friday` | 9 | Campaigns | | `VIP` | 7 | Segments, lists | | `Test` | 14 | Campaigns, flows | | `do not use` | 3 | Flows | | **Total tags** | 8 (shown) | | Five observations: 1. **`BFCM 2024`, `BFCM 2025`, and `Black Friday` are three tags for one concept.** This is classic tag sprawl. Anyone trying to pull all Black Friday activity has to remember three labels. Consolidating onto a single convention, for example `BFCM` plus a year, makes the account searchable and the reporting consistent. 2. **`Test` carries 14 objects, which is a lot of clutter.** Test campaigns and draft flows accumulate this label and rarely get cleaned up. Fourteen tagged test objects suggests old experiments are still hanging around; this is a prompt to archive or delete the ones that are finished. 3. **`do not use` is a warning sign in itself.** A tag literally named "do not use" on three flows means someone flagged them as dangerous but never removed them. Those flows should be audited and archived; a live flow nobody is supposed to use is a reputation risk waiting to happen. 4. **The functional tags look healthy.** `Welcome`, `Abandoned Cart`, and `VIP` map cleanly to recognised programme areas with sensible counts. These are the tags doing real organisational work, and they are worth keeping consistent as new objects are created. 5. **Use this card to drive a naming convention, not to measure success.** Nothing here tells you whether Black Friday made money; that lives on the revenue and campaign cards. What this card does is keep the account legible so the right objects can be found, reported on, and governed, especially valuable for agencies managing many clients in one account. ## Sibling cards merchants should reference together Tags Overview is a structural view; pair it with the object inventories it labels: | Card | Why pair it with Tags Overview | | -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | [Flows](/nerve-centre/kpi-cards/klaviyo/flows) | The flow inventory tags are applied to. Cross-reference to see which flows carry which labels. | | [Flow Count](/nerve-centre/kpi-cards/klaviyo/flow-count) | The high-level flow tally that tag governance helps keep organised. | | [Segments](/nerve-centre/kpi-cards/klaviyo/segments) | Segments are tagged too; this card shows how segment labelling is structured. | | [Lists Overview](/nerve-centre/kpi-cards/klaviyo/lists-overview) | Lists carry tags as well; pair to audit list labelling. | | [Top Segments by Revenue Send](/nerve-centre/kpi-cards/klaviyo/top-segments-by-revenue-send) | The performance side. Tags organise segments; this card shows which actually drive revenue. | ## Reconciling against Klaviyo **Where to look in Klaviyo:** * **Account settings → Tags** (the tag manager) lists every tag in the account and lets you create, rename, merge, and delete them. This is the direct equivalent to this card. * **Flows**, **Campaigns**, **Lists & Segments** views, each of which can be filtered by tag, so you can see exactly which objects a tag is attached to. * The tag filter at the top of those object lists is the fastest way to verify a count this card shows. **Why our number may legitimately differ:** | Reason | Direction of divergence | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | | **Snapshot timing.** Tags and their associations change as the team works. Klaviyo's tag manager updates instantly; this card reflects the most recent pull, so a tag created moments ago may not yet appear. | Transient. | | **Object scope.** A tag's count spans flows, campaigns, lists, and segments. If Klaviyo's view is filtered to one object type, its count for that tag will be smaller than the all-object count here. | Vortex IQ count can be higher. | | **Archived objects.** Whether archived flows or campaigns still count toward a tag can differ between views. | Variable. | | **Page caps.** `GET /api/tags` and the object reads paginate at 50 per page; accounts with very many tags or objects are assembled across pages with minor mid-pull drift possible. | Marginal. | | **Permissions.** Objects a given user cannot see in the Klaviyo UI may still be counted by the API-level pull, so the card can show more than a restricted user sees. | Vortex IQ count can be higher. | ## Known limitations / merchant FAQs **Does this tell me which tags make the most money?** No. Tags Overview is a governance view, not a performance one. It counts how many objects carry each tag, not what those objects earned. For revenue and engagement, follow a tag to the underlying flows, campaigns, and segments and read their performance cards. **Why does one tag's count look higher here than in Klaviyo?** Usually because this card counts a tag across all object types (flows, campaigns, lists, segments) while you are looking at a filtered, single-object view in Klaviyo. Switch off the object-type filter in Klaviyo and the counts should converge. **I have three tags that mean the same thing. What should I do?** Consolidate them in Klaviyo's tag manager, which supports renaming and merging. Pick one naming convention, for example a programme name plus a year, and retire the duplicates. This card is the fastest way to spot that kind of sprawl in the first place. **What is a sensible tagging convention?** Tag by stable concepts you will want to report on later: programme area (welcome, abandoned cart), campaign theme or season (BFCM, summer-sale), audience (VIP), and ownership for agencies (client name). Avoid one-off labels and "test" tags that never get cleaned up. **Are tags the same as lists or segments?** No. A tag is just a label for organising objects; a list is a static opt-in group of profiles and a segment is a dynamic rule-based group. You can tag a list or a segment, but the tag does not change who is in it. This card is about the labels, not the audiences. **Should I delete a tag with a zero or tiny count?** Often yes. A tag attached to nothing, or to a single stale object, is clutter. Before deleting, confirm it is not part of an automated workflow or a saved view someone relies on. The card helps you find these candidates; the clean-up happens in Klaviyo's tag manager. *** ### Tracked live in Vortex IQ Nerve Centre *Tags Overview* is one of hundreds of KPI pulses Vortex IQ tracks across Klaviyo and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.