agentleFS
scumunnascumunna/programmatic-skills/skills/cross-platform-taxonomy-governance/SKILL.md

cross-platform-taxonomy-governance

Skill1 starsChanged 5 months agoMITView on GitHub

Govern campaign, ad group, line item, placement, creative, UTM, cost-center, and reporting naming across platforms so operations, billing, and analytics join cleanly. Use when the user asks for naming conventions, taxonomy, UTM governance, campaign codes, reporting keys, dashboard joins, or taxonomy cleanup.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every token must have an owner, allowed values, and a reason.

    line 26
  2. Distinctive:

    Do not encode values that change daily into the name.

    line 28
  3. Distinctive:

    Do not rename live entities without checking downstream reports and billing joins.

    line 29
  4. Distinctive:

    Use a local codebook, but keep these token groups available across platforms:

    line 33
  5. Distinctive:

    Use lowercase, stable values.

    line 62
  6. Distinctive:

    If the landing-page analytics team has a different source or medium standard, adopt that standard rather than forcing a media-only …

    line 72
  7. Distinctive:

    Define allowed values: Create a codebook for each token.

    line 79
  8. Distinctive:

    Validate before launch: Every launch QA should check taxonomy fields before go-live.

    line 83
  9. Distinctive:

    All required tokens are present and valid.

    line 92
  10. Distinctive:

    No spaces, special punctuation, or one-off abbreviations.

    line 94
  11. Distinctive:

    No live rename is made without a downstream impact check.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cross-platform taxonomy governance

Taxonomy is not cosmetic. It is how the desk finds work, joins reports, reconciles billing, audits launches, and explains campaigns to clients. A naming convention that only looks tidy but cannot join to spend, tags, creative, and invoices is not a taxonomy.

This skill defines a cross-platform taxonomy operating model. It complements dv360-account-setup-and-taxonomy by making the rule platform-neutral.

When to use this skill

  • A user asks for campaign naming, taxonomy, UTM standards, or reporting keys.
  • A launch needs names, labels, cost centers, or codes approved.
  • A dashboard, billing file, or reconciliation is failing because names do not join.
  • The team needs to clean up old names without breaking live reports.
  • A bulk taxonomy change is proposed.

Core principles

  • Names are for operators and humans. IDs and codes are for systems. Use both.
  • Every token must have an owner, allowed values, and a reason.
  • The taxonomy must work across campaign, ad server, analytics, warehouse, and billing.
  • Do not encode values that change daily into the name. Use labels, reports, or metadata.
  • Do not rename live entities without checking downstream reports and billing joins.

Required token model

Use a local codebook, but keep these token groups available across platforms:

Token groupExamplesPurpose
Client or advertiser codeacmeJoin to client and billing
Market or regionus, ca, emeaGeo reporting and budget pools
Objectiveawareness, traffic, leads, salesKPI and optimization logic
Funnel stageprospecting, retargeting, crmAudience and reporting logic
Channel or formatdisplay, video, ctv, audio, native, searchSupply and creative grouping
Platformdv360, ttd, amazon, meta, tiktok, msadsCross-platform joins
Flight or quarter2026q3, jul2026Calendar grouping
Campaign codecmp00123Stable join key
Creative or test codecr001, hook-aAsset and test reads
Cost center or POpo4567Billing and finance

Naming pattern

Choose one delimiter, usually _, and prohibit free-form punctuation.

client_market_objective_funnel_channel_platform_flight_campaigncode
acme_us_sales_retargeting_video_dv360_2026q3_cmp00123

Shorten only through the codebook. Do not let teams invent one-off abbreviations inside the platform.

UTM pattern

Use lowercase, stable values. Match UTM values to the platform taxonomy where possible.

utm_source=platform
utm_medium=paid_media
utm_campaign=campaigncode
utm_content=creativecode
utm_term=audience_or_keyword_code

If the landing-page analytics team has a different source or medium standard, adopt that standard rather than forcing a media-only convention.

Core process

  1. Confirm downstream consumers. Identify who needs the taxonomy: trader, ad ops, analytics, billing, client reporting, finance, creative, and data engineering.
  2. Define allowed values. Create a codebook for each token. Include spelling, allowed abbreviations, owner, and examples.
  3. Map platform limits. Some platforms have name length limits, label limits, or fields that do not export cleanly. Use stable IDs or labels where the name cannot carry the token.
  4. Validate before launch. Every launch QA should check taxonomy fields before go-live. Invalid taxonomy is a launch blocker if it breaks reporting, billing, or automation.
  5. Govern changes. New values require an owner and date. Deprecated values stay in the codebook until no active reports depend on them.
  6. Bulk changes safely. Any live rename or taxonomy backfill runs through bulk-change-governance-and-rollback.

Taxonomy acceptance checks

  • All required tokens are present and valid.
  • Values are lowercase unless the platform requires otherwise.
  • No spaces, special punctuation, or one-off abbreviations.
  • Campaign code and creative code match the source plan.
  • UTM campaign and content join to reporting keys.
  • Cost center or PO is present when billing requires it.
  • No live rename is made without a downstream impact check.

Common pitfalls

  • Treating taxonomy as a naming style exercise rather than a reporting and billing contract.
  • Encoding objective in some platforms and not others, then losing cross-platform reporting.
  • Renaming live campaigns to fix cosmetics and breaking dashboard history.
  • Letting each client team define vid, video, and olv differently.
  • Using free-text creative names as the only asset identifier.

Related artifacts

  • templates/ops/taxonomy-convention.csv
  • tools/utm_builder.py
  • dv360-account-setup-and-taxonomy
  • marketing-analytics-warehouse-and-dashboards
  • programmatic-month-end-close
  • bulk-change-governance-and-rollback

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.