# How to Configure Tag-Based Cost Attribution: Step by Step

> How to Configure Tag-Based Cost Attribution. A practical walkthrough with ZopNight: read-only setup, production excluded by default, reversible at every step.

Source: https://zop.dev/learn/how-to/configure-tag-based-cost-attribution
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, how-to, learn

---

Use ZopNight tag attribution to slice cloud cost by AWS tags, GCP labels, Azure tags, or accepted smart tags. Pagination, batched values, and trend chart per tag value.

This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 20 minutes. Billing sync configured; A ZopNight account.

## The steps

1. Confirm tag coverage.
2. Open Reports and the Tags tab.
3. Use pagination and batched values.
4. Read batched tag trends.
5. Encode slashful tag values.

## Why this is safe to do today

The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.

If you want the fuller context behind this task, the [FinOps](https://zop.dev/learn/finops) guide covers where it fits, and the [AWS EC2 scheduling](https://zop.dev/zopnight/aws/ec2) page shows the same loop applied to a specific resource.

## Getting started

Getting started is intentionally low-stakes:

- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.

## Frequently asked questions

### Does tag attribution split cost like team attribution?

No. Each tag key-value pair gets the full resource cost. A resource with environment:prod and team:platform contributes its full cost to environment:prod and its full cost to team:platform.

### What happens to resources with no tags?

They are excluded from tag attribution. Use the Tag Coverage donut on the dashboard to find them and apply smart tags rules to fill gaps.