custom_label_4
The fifth and final custom label slot. Often left for ad-hoc or experimental segmentation since the first four typically encode the stable dimensions.
Also known as: custom label 4
Channel support
| Channel | Status | Field name | Notes |
|---|---|---|---|
| Google Merchant Center | Optional | custom_label_4 | — |
| Meta Commerce Manager | Optional | custom_label_4 | — |
| TikTok Shop | Not supported | — | — |
| Pinterest Catalog | Optional | custom_label_4 | — |
| Amazon | Not supported | — | — |
| Bing Merchant Center | Optional | custom_label_4 | — |
Why it matters
Reserving custom_label_4 for experiments means you can run A/B tests and short-term tactical campaigns without disturbing the stable product set structure built on labels 0-3.
`custom_label_4` is conventionally the experiment slot — reserved for A/B tests, short-term tactical campaigns, and anything you want to be able to clean up without disturbing the stable structure built on labels 0-3. Treating one slot as the "scratch space" keeps the rest of your segmentation discipline intact when you need to try something quickly.
Practical examples: testing a new product set definition before promoting it to a permanent label; tagging a creative-test cohort during a campaign experiment; flagging items that need manual review without removing them from active serving. The value is that experiments don't pollute your stable segmentation — when the test ends, the label clears, and your label 0-3 hierarchy is untouched.
Some teams skip this convention and use all five labels for stable dimensions. That works for catalogs with five orthogonal segmentation needs, which is rare. More common is three or four stable dimensions plus the occasional need for tactical labelling — which is what custom_label_4 makes clean.
Format rules
-
Free-form string, max 100 characters
Applies to: Google Merchant Center, Meta Commerce Manager, Pinterest Catalog, Bing Merchant Center
Valid examples
test-creative-v2 A/B test cohort
Related tools
FAQ
Why use the labels in numerical order?
Convention, not requirement. Channels don't care which slot holds which dimension. But teams find numerical order makes shared documentation cleaner — everyone knows `custom_label_0` is ROAS and `custom_label_1` is margin.
Last reviewed: 26 May 2026
Why wait? Try it free today.
Stop managing feeds manually. Start optimising with AI in 30 seconds.
- Free plan, no credit card required
- 1 brand, 1 feed, 100,000 products per feed
- Full AI Product Optimisation, Rule Engine, and 200+ channel exports
- Pay only for AI credits when you need them