At a glance
Top tags applied to products in the BC catalogue, ranked by product count. Tells you how the merchandising team is organising the catalogue, which tags are heavily used vs underused, and where tag governance has drifted (typos, duplicates, abandoned campaigns).
| What it counts | GROUP BY product.tags over every product in the catalogue. Each tag-product link counts once; a product with 5 tags contributes to 5 different tag buckets. |
| VAT / tax treatment | n/a, catalogue metadata. |
| Shipping | n/a. |
| Discounts | n/a. |
| Refunds | n/a. |
| Cancelled / voided orders | n/a. |
| Currency | n/a. |
| Channels / sources | Catalogue-wide; tags are a global product attribute in BC. Some channels use tags for routing logic (Amazon Channel Manager listing categories, Facebook Shop product groups); tag changes have downstream channel effects. |
| What tags are for in BC | Tags serve four merchandising purposes: (1) storefront filtering (“Sale”, “New Arrivals”, “Bestseller”), (2) promotion targeting (a coupon valid only on tagged products), (3) automation rules (workflow apps trigger on tag changes), (4) category-style grouping (when categories are insufficient). |
| Common tag governance problems | Typo-duplicates (“bestseller” vs “best-seller” vs “Best Seller”), abandoned campaign tags (“BlackFriday2023”), inconsistent capitalisation, plural vs singular drift. Tags are unrestricted free-text in BC, the merchandising team is the only governance. |
| B2B Edition | B2B catalogues often use tags for buyer-segment routing (“ContractA”, “Wholesale-Only”, “Trade”). Healthy B2B tag governance is critical because tags drive who-sees-what logic. |
| Why this matters more than the tag-count abstraction suggests | Tags drive merchandising automation. A product with the wrong tag may be excluded from a promotion (revenue loss), included in a wrong-channel feed (channel-violation), or hidden from the right customer segment (retention loss). Tag hygiene is operational hygiene. |
| Time window | RT (real-time, refreshed each catalogue sync) |
| Alert trigger | None at this card. Pair with promotion-targeting validators for the operational-impact view. |
| Roles | owner, marketing, operations |
Calculation
Worked example
A US homewares brand on BigCommerce Pro, snapshot at 12 Apr 26.| Tag | Product count | Notes |
|---|---|---|
bestseller | 218 | Storefront filter, ranked badge |
new-arrival | 184 | Auto-applied for first 30 days post-launch |
sale | 162 | Active promotion-targeted |
eco-friendly | 95 | Marketing/SEO landing page |
gift-idea | 88 | Holiday navigation category |
best-seller | 12 | Typo duplicate of bestseller |
blackfriday2023 | 47 | Abandoned campaign tag |
BestSeller | 8 | Capitalisation duplicate |
eco friendly | 6 | Spacing duplicate |
Gift Idea | 4 | Capitalisation duplicate |
b2b-only | 412 | B2B portal targeting |
wholesale | 380 | Pricing-tier rule |
- Three duplicate clusters cost real money. The
bestsellergroup (218 + 12 + 8 = 238 actual) is split across three tags. The “bestseller filter” on the storefront probably uses one of the three; the products tagged with the other two are excluded from the filter, missing impressions. blackfriday2023is dead weight, but worse than that. If a Black Friday 2023 promotion still triggers on this tag (some merchants forget to disable old promotions), 47 products are getting Black Friday pricing in April. Audit promotions: any active promotion targeting an old campaign tag is an unintended discount.- The
b2b-onlyandwholesaletags overlap. Likely 350-400 products carry both tags (the same set in two namespaces). Consolidating to one tag reduces cognitive load and prevents drift; pick the canonical one and migrate. new-arrivalat 184 products is healthy if you launch ~6 SKUs/day; lower if you launch faster. The auto-apply / auto-remove timing matters: ifnew-arrivaldoesn’t expire, the catalogue accumulates “new arrivals from 18 months ago” and the storefront filter loses meaning.- Underused tags are also opportunities. Tags appearing on <5% of catalogue but on the storefront filter menu serve dead air. Either delete the filter or apply the tag to more products.
- Run a tag-typo audit. Sort tags alphabetically; visually scan for case duplicates, spacing duplicates, and singular/plural pairs. Most stores find 5-15 duplicate clusters in a typical 50-tag catalogue.
- Migrate via bulk update. BC’s bulk-edit UI supports “find products with tag X, also add tag Y”. Sequence: add canonical tag to all duplicates, verify counts match, then remove the duplicate tag.
- Audit active promotions for tag dependencies. Any promotion still targeting an old campaign tag that no longer applies as intended is a margin leak.
- Establish a tag-governance protocol. Naming convention (lowercase, hyphenated, no spaces), expiry rules for campaign tags, ownership of new tags. Without governance, tags drift.
- For B2B + retail hybrid stores, audit tag-driven channel routing. A B2B product without
b2b-onlyshows up on retail; a retail product accidentally taggedb2b-onlydisappears from retail.
Sibling cards merchants should reference together
| Card | Why pair it with Top Product Tags |
|---|---|
| Product Status | Tags + status combinations show whether tagged products are actually live. |
| Products by Type | Type vs tag overlap; tags often replicate type. |
| Products by Vendor | Vendor-as-tag pattern; some merchants tag-by-brand instead of using the brand field. |
| Top Products | Revenue-ranked. The top tags should align with top revenue concentrations. |
| BC Top Coupons | Promotion targeting via tags. Audit overlap between tagged products and active coupons. |
| Missing SEO Title Count | SEO + tag governance both signal catalogue-management quality. |
| Collection Health | Collections often defined by tags; tag drift breaks collection logic. |
| BC Channel OOS per Channel | Tag-driven channel listing. Wrong tags = wrong channel exposure. |
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce Control Panel: Catalogue → Products supports filter by Tags. There is no native “tag count distribution” tile; you’d run multiple filters or bulk-export and group manually. For tag-driven promotion validation, Marketing → Promotions shows which tags trigger which promotions; cross-reference active promotions to tag list to identify orphan-tag-driven promotions. Why our number may legitimately differ from BC catalogue view:| Reason | Direction |
|---|---|
Case sensitivity. We treat tags case-sensitively (matches BC’s storage); bestseller and BestSeller are different. A merchant manually counting may collapse case variants. | Vortex IQ MORE granular |
Whitespace handling. eco-friendly and eco friendly and a leading-space eco-friendly variant are three tags; we count separately. | Vortex IQ MORE granular |
| Disabled product tags. We include disabled-product tags in the count by default; BC’s filter may default to visible products. | Vortex IQ HIGHER |
| Sync lag. Recent tag changes propagate within 5-30 minutes. | Vortex IQ slightly LAGS |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
klaviyo.kl_segment_tag_overlap | Klaviyo segments built from BC tags should match this card’s tag-product counts | Sync timing; Klaviyo refreshes hourly. |
google_shopping.gs_product_categories | Google Shopping product categorisation often derived from BC tags | Google’s category taxonomy is fixed; BC tags are free-text. Mapping is approximate. |
shopify.product_tags(planned)adobe_commerce.product_tags(planned)
Known limitations / merchant FAQs
My tag list has 200+ tags, is that a problem? Probably yes. Healthy tag governance limits active tags to 30-80; beyond that the team can’t keep mental track. Audit the long tail; consolidate near-duplicates; archive abandoned campaign tags. Most stores can cut tag count 30-50% with no merchandising impact. How do I find typo-duplicates? Sort the tag list alphabetically and visually scan adjacent rows. Common patterns:bestseller / best-seller / Best Seller, eco-friendly / ecofriendly / eco friendly. Tools: BC bulk export to CSV, sort, scan; or use a tag-management app from the BC marketplace.
Should campaign tags expire?
Yes, with discipline. Add a date suffix (spring-launch-2026-04) so older tags are obvious. At quarter-end review tags older than 6 months; archive ones whose campaign ended.
Why do my tag-driven promotions sometimes miss products?
Because the tag has duplicates. A promotion targeting bestseller doesn’t apply to products tagged Best Seller or best-seller. The fix is consolidation; the prevention is governance.
Can I rename a tag without losing the products?
Not in one step. BC’s API doesn’t offer a “rename tag” operation. The pattern: bulk-add the new tag to all products with the old tag, verify counts match, then bulk-remove the old tag.
My B2B-only tag is on retail-visible products, what happened?
A merchandising error. Either someone accidentally tagged a retail product as b2b-only, or a B2B-imported SKU was published to retail without removing the tag. Audit Channel Manager → retail channel for products tagged b2b-only; either un-tag them or hide from retail.
Should I use tags or categories for organisation?
Both, but for different purposes. Categories are hierarchical and structural (“Bedding > Sheets > King Size”); tags are flat and orthogonal (“Sale”, “Bestseller”, “Eco-Friendly”). A product belongs to one category but can carry many tags. Use categories for navigation; tags for filtering and merchandising rules.
Why do my POS terminals show different filter options than my web?
Because POS interfaces typically use a different filter list than web. POS often shows category-style tags (“Cleaning Supplies”, “Decor”) while web shows feature-style tags (“Bestseller”, “Eco”). Both pull from the same underlying tag list; the difference is which subset is exposed in each interface.
My theme uses tags for sale-badge logic, can I rely on this card to count sale items?
Yes if the tag is consistently applied. Audit your theme’s sale-badge logic for which tag it triggers on. Some themes use sale (lowercase), some use Sale (capitalised), some use a custom field instead of a tag. Match the storage exactly.
Can I see tag adoption over time?
Not from this card directly. Pair with periodic catalogue exports for historical comparison. We’re working on a tag-trend card; track the V2 backlog.