Job Tags: Campaign Tracking & Feed Syndication

Many clients insert campaign tracking hashtags - like #FSIND, #ZR, or #LI-DNI - directly into their ATS job description. Aggregators like Indeed and LinkedIn read those tokens to automatically enroll the role in a sponsored campaign. The problem: AI summary rewrites typically strip them, and a stripped token means the job silently misses the campaign.

Boostie solves this by extracting campaign tags from the raw ATS description before any rewriting happens, storing them separately as Job Tags, and carrying them into every outbound feed and the board job page automatically - so sponsored campaigns stay active without recruiter follow-up.

What Job Tags Are

A Job Tag is a short label attached to a job page. Boostie populates them two ways:

• Automatically extracted - campaign hashtags found in the ATS description (e.g., #FSIND, #LI-DNI) are parsed out when the job page is built and stored as tags. The tags are then stripped from the public job summary so candidates see a clean description.
• Recruiter-entered - any label you add manually on the Job Page tab, including a missed campaign token or a freeform tag for your own tracking.

Tags appear in two places for candidates and aggregators:

• Board job page - displayed in the meta line alongside the job ID and published date, formatted as Tag1 | Tag2.
• All outbound feeds - Indeed, LinkedIn, ZipRecruiter, and custom XML feeds all append the full tag set to the job description so aggregator campaign rules can match the role.

Viewing and Editing Tags

Go to Jobs in the left navigation, open a job record, and click the Job Page tab. The Job Tags field shows the current tags for that job.

To add, change, or remove tags, click Edit to open the edit drawer and scroll to the Job Tags section.

1. Click Add Job Tag and type the tag text.
2. Repeat for each tag you want to add.
3. Click the remove icon next to any tag to delete it.
4. Click Save when done.

Tag format: Each tag can be up to 50 characters. Extracted campaign tokens include a # prefix - if you're adding one manually, enter it exactly as the aggregator expects (e.g., #FSIND). Freeform tags for your own tracking don't need a #. Tags are matched case-insensitively for duplicates, so #FSIND and #fsind count as one entry.

How Auto-Extraction and Manual Edits Work Together

Boostie keeps tags in sync with the ATS description automatically: when the ATS description changes and new campaign tokens appear, Boostie updates the tags on the next sync. That automatic sync stops the moment you save any manual change to a job's tags - from that point on, Boostie treats the job's tags as recruiter-managed and won't overwrite them.

Important: This includes clearing the tag list. If you remove all tags and save, the job stays tag-free even if the client later adds campaign tokens to the ATS description. Any new tokens will need to be added by hand.

Pro Tip: If a job should be in a campaign but wasn't tagged when the job page was built, add the campaign token manually in the edit drawer. It will flow into the next feed generation automatically.

Why It Matters

A missing campaign token is invisible - the job still publishes, the feed still runs, but the aggregator's campaign rule never matches, and ad spend stops with no error or alert. Boostie's automatic extraction closes that gap for every new and updated job. The manual editor gives you the override when a token was missed or when you want to tag jobs for your own reporting, without waiting on an ATS description change to trigger a sync.