Custom Labels in XML Job Feeds: Strategic Guide for Job Distribution

When recruitment and staffing agencies manage hundreds of open jobs simultaneously, manual campaign management breaks down. Job aggregators and media channels default to distributing budgets toward jobs with the highest natural search volume, regardless of their commercial value to your agency. Consequently, high-volume junior roles quickly exhaust your entire recruitment ad spend, while niche specialist roles carrying substantial placement fees remain starving for applicants.

The technical solution to this imbalance is implementing custom labels within your XML job feed. By enriching your feed data with programmatic tags, you turn a passive job inventory into an intelligent, automated distribution engine that dynamically steers on margin, urgency, and candidate funnel velocity.

What are custom labels in a job feed?

Custom labels are standardized, optional attributes in an XML feed (commonly labeled custom_label_0 through custom_label_4). Adapted from e-commerce feed standards, these tags are widely supported across programmatic job platforms, Google for Jobs, Indeed, ZipRecruiter, and dynamic ad networks across Meta and LinkedIn.

Unlike public elements like job title, salary range, or office location, custom labels are invisible to job seekers. They serve entirely as backend metadata for ad engines to execute automated filtering, bid multipliers, and budget segmentation.

The 5-tier architecture model for custom labels in recruitment

To gain precise programmatic control over multi-channel job distribution, structure the 5 available custom label slots using a standardized framework. A field-tested setup for staffing and executive search firms includes:

• custom_label_0: Gross Margin or Placement Fee Tier (e.g., Fee_Tier_A for fees above 15,000 EUR, Fee_Tier_B for 8,000-15,000 EUR, Fee_Tier_C for low-margin temporary staffing).
• custom_label_1: Sourcing Difficulty and Talent Scarcity (e.g., Hard_To_Fill, Medium_Difficulty, Volume_Easy).
• custom_label_2: Hiring Urgency and Pipeline Health (e.g., Urgent_Fill_Under_7_Days, Standard_Pacing, Backlog_Maintenance).
• custom_label_3: Geographic Cluster or Territory (e.g., Metro_Core, Regional_Hub, Remote_Flexible).
• custom_label_4: Contract Type and Talent Category (e.g., Permanent_Placement, Interim_Contractor, Graduate_Trainee).

Calculation example: Dynamic budget allocation with custom labels

Suppose a staffing agency managing 150 active vacancies allocates a monthly programmatic advertising budget of 6,000 EUR. Without custom labels, media algorithms distribute this evenly or skew toward popular search terms, amounting to an uncalibrated 40 EUR per vacancy.

By applying rule-based bidding driven by custom_label_0 (Fee Tier) and custom_label_1 (Difficulty), the budget allocation is strategically rebalanced in this calculation example:

• Tier 1 (Fee_Tier_A + Hard_To_Fill): 30 critical jobs capture 60 percent of total spend (3,600 EUR, or 120 EUR per job) with an aggressive CPC bid of 1.20 EUR.
• Tier 2 (Fee_Tier_B + Medium_Difficulty): 70 standard jobs capture 30 percent of total spend (1,800 EUR, or 25.71 EUR per job) with a moderate CPC bid of 0.60 EUR.
• Tier 3 (Fee_Tier_C + Volume_Easy): 50 high-volume jobs receive the remaining 10 percent of spend (600 EUR, or 12 EUR per job) with a strict CPC ceiling of 0.25 EUR.

Through this structured feed approach, 80 to 90 percent of your media capital is purposefully directed toward requisitions that drive the highest commercial return or require focused market visibility.

Implementing custom labels in your ATS and feed infrastructure

Technical deployment of custom labels follows a three-stage integration workflow:

• 1. ATS Data Extraction: Ensure critical attributes such as target placement fee, margin, open date, and job discipline are exposed via your applicant tracking system XML or REST API feed.
• 2. Feed Transformation via Business Rules: Use middleware or a feed optimization platform to map raw ATS values into uniform labels. For example: IF Discipline = 'DevOps Engineer' AND Location = 'Amsterdam', THEN set custom_label_1 = 'Hard_To_Fill'.
• 3. Publisher and Channel Mapping: Connect the enriched XML feed to your programmatic platforms, Google job campaigns, or Meta dynamic product catalogs. Configure ad sets and automated bid adjustments directly based on these active label values.

Common pitfalls when setting up custom labels

A common mistake is creating too many unique values within a single label slot. Defining 40 distinct labels in custom_label_0 fragments campaign budgets into tiny sub-segments, preventing advertising algorithms from collecting enough conversion events to optimize bids. Keep label variations between 3 and 5 distinct categories per tag.

Another frequent error is static tagging without automated synchronization. When an urgent requisition hits 8 qualified candidates in late-stage interviews, custom_label_2 should automatically trigger from 'Urgent' to 'Maintenance' to prevent media spend from burning on a job that is already on the verge of closing.

How Leadstars solves this for you

Structuring complex XML feeds, writing algorithmic business rules, and managing programmatic bidding across diverse channels takes hours of specialized work that keeps your recruiters away from placing talent. Through the Job Acquisition Machine (JAM) and our dedicated Multi-Channel Job Distribution service, Leadstars handles your complete feed architecture and programmatic job marketing execution from end to end.

Leadstars operates on a predictable monthly or annual retainer paired with an upfront onboarding fee, backed by a clear lead volume result guarantee and a 7-day delivery turnaround. Schedule an introductory strategy session today to see how we can transform your job distribution into an automated, high-margin candidate generation engine.

Want to go deeper? Read more about our client results and the videos in our knowledge base and our recruitment marketing agency page.