Overview
Master labels allow you to assign custom internal names to your automated groups (masters). These labels help you organize and identify automated campaigns, ad sets, and ads within the Hunch platform.
Key benefits:
Clearer identification of master vs. generated entities
Faster navigation in grouped views
Better organization through meaningful naming
Internal-only labels that never publish to Meta
Understanding Master labels vs. Child Patterns
Master label: An optional custom label for the parent automation entity (master). This name appears in the Hunch interface to help you organize and navigate your automations.
Child Name Pattern: The required naming pattern that generates actual Meta campaign/ad set/ad names based on your data feed values.
These two fields work together:
The Automated Name identifies the automation group in Hunch
The Child Pattern generates the actual names published to Meta
If you don't provide an Automated Name, the system uses the Child Pattern as the master label
Where to Find Automated Entity Naming
Campaign Editor (Creation & Editing)
When creating or editing an automated campaign, ad set, or ad, you'll see the "Automated [Entity] Name" field in the configuration section, typically above or next to the "Child Name Pattern" field.
Campaign Overview - Individual View
In the campaign overview, each child entity's detail panel includes a field showing which automation created it.
Adding a Name During Campaign Creation
In the campaign editor, navigate to the master entity
Locate the "Automated [Entity] Name (Optional)" field
Enter a descriptive name
Example: "Black Friday Retargeting Campaigns"
Example: "Q1 2026 Prospecting - High Value"
Configure the Entity Name Pattern as usual
Complete the setup and save
Editing an Existing Automation's Name
Navigate to the master you want to rename
Modify the "Automated Name" field:
Add a name if previously blank
Change existing name to something else
Clear the name to revert to Child Pattern display
Save your changes
The new name appears immediately in all views
Note: Changing the Automated Name does not affect any entities already published to Meta or trigger a sync operation.
Leaving the Field Blank
If you don't provide an Automated Name, the system automatically uses your Child Name Pattern as the master label. This maintains existing behavior for users who prefer not to use custom names.
Example:
Automated Name: (empty)
Name Pattern: "#category | #region"
Master displays as: "#category | #region"
Campaign insights view
Grouped View
The grouped view organizes your campaigns hierarchically, showing masters with their generated children nested underneath.
What you'll see:
Masters display using Automated Names (or Child Pattern if blank)
Children nest under their parent masters
You can expand/collapse masters to manage visual complexity
Frequently Asked Questions
Q: Do Automated Names get published to Meta?
A: No. Automated Names are internal to Hunch only. Your Meta campaigns will always use the names generated by your Child Name Pattern.
Q: Can I use the same Automated Name for multiple masters?
A: Yes. Multiple masters can share the same name, which groups them together in the interface. This is intentional and can be useful for organization.
Q: What happens if I change the Automated Name?
A: The new name appears immediately in all views (editor preview, grouped view, exports). It does NOT affect entities already published to Meta or trigger any sync operations.
Q: Can I remove an Automated Name after adding it?
A: Yes. Simply edit the automation and clear the field. The master will revert to displaying the Child Name Pattern.
Q: Does this affect my existing automations?
A: Existing automations continue working as before. The Automated Name field will be empty, so they'll display using the Child Pattern. You can add custom names anytime by editing the automation.