SOP: Design a Sub-ID Naming Taxonomy

SOP: Design a Sub-ID Naming Taxonomy

Messy sub-IDs make reporting useless. Standardize before scaling.

— Step 1: Fix the slot order and never change it: source_campaign_creative_geo_device.
— Step 2: Use short codes, not full names. fb not facebook; sub-IDs have length limits.
— Step 3: Reserve one slot for the fallback tier so reports show A/B/C performance.
— Step 4: Use a single delimiter (underscore) consistently; mixing breaks split-by-column reporting.
— Step 5: Avoid spaces and special chars; they URL-encode and corrupt the network's parser.
— Step 6: Document the schema in a one-pager every operator can read.

A fixed slot order means any report column maps to a known field. That's the whole point.

Repeat: review the taxonomy quarterly; add slots only at the end, never reorder.