Allocation

Tags and tag coverage

See the tag keys Costfluent found in your cost data, measure how much cost is tagged, state the keys a workspace's cost must carry, and set a coverage alert.

Tags are the key-value labels your teams put on cloud resources. Costfluent reads them with every collection; it never writes them. Tag keys and the workspace's tag policy are under Allocation, then Tags, a page Settings also lists; tag coverage is measured on the Insights page.

Before you start

  • Tag keys appear once a sync brings in tagged resources. Nothing creates a key in Costfluent: a key exists because a resource carries it.
  • Deleting a tag key needs the Owner or Integration owner organization role. Setting a coverage alert or changing the tag policy needs the Editor team role in a workspace your team can edit; every team role can read the policy.

Read tag coverage

Open Insights. The "Tag coverage" card always covers the last 30 days, ending today, and states those days and what it measures: the share of cost on resources that carry at least one tag. It shows:

  • "Overall coverage": the share of cost on tagged resources;
  • "Tagged spend" and "Untagged spend";
  • "Top tag keys": the five keys carrying the most cost.

Allocation, then Tags, carries the same "Tag coverage" card for the workspace, above the tag keys.

While some cost is untagged and the workspace has no tag policy, the card links "Set a tag policy", the section below.

The Tags page with the Tag coverage card, showing Overall coverage, Tagged spend, Untagged spend and the Top tag keys, above the Tag keys table with each key's Last seen date, Providers and Hidden and Preferred switches

Settings, then Tags: the workspace's tag coverage above the tag keys found in your cost data. The Tag policy card is left out.

AWS cost read from Cost Explorer, the history before an export's first delivery, carries no tags, so it counts as untagged; the card names those months (History and first delivery).

A key Costfluent adds itself does not make cost tagged: aws:payerAccountId, which every AWS cost line carries, and ai:user, the user a line of Anthropic, OpenAI or Cursor spend belongs to, count toward none of these figures and are not among the "Top tag keys". You can still filter and group by them as by any tag.

Set a coverage alert

  1. On the Insights page's "Tag coverage" card, select "Set alert".
  2. In Set tag coverage alert, enter an Alert name and set the Coverage threshold in percent with the slider.
  3. Optionally, pick notification channels under Send to. An in-product notification is always sent too.
  4. Select "Create alert". "Tag coverage alert created" confirms it.

The alert fires when coverage over the last 30 days falls below the threshold, and again only after coverage has recovered and fallen below it once more. See Alerts.

The alert appears on the Alerts page under Configured alerts as Low tag coverage, and on the Insights page's Alerts card, where it can be paused, resumed, edited and deleted.

Set a tag policy

A tag policy names the tag keys a workspace's cost must carry: one or more rules, each with the keys it requires and the provider and accounts it applies to. The Tag policy card under Allocation, then Tags, holds it.

Costfluent only measures your tags against the policy. It changes nothing in your cloud accounts and enforces nothing there.

  1. Open Allocation, then Tags, and select "Add rule" in the Tag policy card.
  2. Under Provider, keep "Every provider" or pick one. Under Accounts, leave the rule on "Every account" or add the account ids as your provider writes them; the field suggests the accounts in the workspace's cost data as you type.
  3. Under Required tag keys, select "Add a required tag key" and pick keys from your cost data, or type a key not seen yet.
  4. Select "Save tag policy". "Tag policy saved." confirms it.

Saving the first rules creates the report "Untagged cost by account": the cost of the last 30 days missing a required key, grouped by account. The Tag policy card and the Insights page's "Tag coverage" card link to it.

Follow untagged cost

  • Filter any report on Tag compliance to split cost into the rows that carry every required key and the rows missing one; see Filter with CQL.
  • Group the policy's report by segment instead of account to see the untagged cost of each owner; see Segments and allocation rules.
  • Schedule the policy's report weekly; see Share and schedule reports. Its digest adds the share of the last seven days' cost that carried every required key, its change in points against the seven days before, and the three accounts with the most cost missing a key.
  • Once the policy has rules, a coverage alert measures that share instead of any tag; the alert's dialog says which measure applies.

How a tag policy behaves

  • A rule applies to cost from its provider and accounts. Rules add up: a cost line must carry the keys of every rule that applies to it.
  • A key counts only with a value, and keys are case-sensitive, as your provider's tags are: a line tagged Team does not carry team.
  • A policy holds up to 20 rules; a rule requires 1 to 20 keys and names up to 50 accounts.
  • Without rules, every cost line counts as carrying the required keys, and the coverage alert measures any tag again. Removing every rule keeps the report "Untagged cost by account", which then lists nothing.
  • A report reads the policy each time it runs, so changing the policy changes what an existing report counts.

Review tag keys

Tag keys lists each key found in your organization's cost data with the date it was Last seen and the Providers it came from; the search box above the list finds a key by name. To make Costfluent forget a key, select the bin on its row and confirm with Delete in Delete this tag key?; it reappears on the next sync if your resources still carry it.

A provider can bring hundreds of keys, most of them noise. Turn on Hidden on a key's row to leave it out of the filter and group-by menus, or Preferred to list it first there. A key is one or the other, so turning one on turns the other off. A hidden key stays on this list and keeps its values in your cost data; a filter or report that already names it keeps working. Only the Owner or Integration owner organization role can change either switch, and the card says so to every other member.

Use tags in reports and rules

  • Filter or group a cost report by Tag and choose the Tag key; see Explore cost data. Tagged splits cost into tagged and untagged lines by the same rule as coverage, and "has no value" on a Tag clause finds the lines without that key.
  • Match an allocation rule on a tag; see Segments and allocation rules.
  • When the same meaning is spread over several keys, or some resources are untagged, a virtual tag gives every cost line one value. The Tag keys card links the Virtual tags page.