RESOURCES · EXPERTINI ATS

Job Feeds and Structured Job Data

The structured data underneath every ad campaign, and how Expertini's ad tools actually read it.

2 min read · Updated July 2026 · Expertini Editorial

Every distribution channel — organic search, a Google Ads campaign, a paid programmatic order — needs to know the same basic facts about a job: title, location, description, category, and where to send a candidate who clicks. This page covers what that structured job data is generically, and how Expertini's ad tools use the job data that already lives in the ATS rather than requiring it to be re-entered per channel.

▶ Watch the 30-second overview — no sign-up needed

1source of job data driving both organic distribution and paid campaigns — the job record itself

3ad tools reading from that same job data: Google Ads Connector, Microsoft Ads Integration, Programmatic Job Ads

0separate keyword lists or ad-copy documents required — the campaign build reads the job record directly

251country sites the same job record mirrors to automatically on publish

01What a job feed is, generically

In the wider industry, a job feed is typically a machine-readable file — commonly XML — published at a URL that partner networks retrieve on a schedule, describing each job's attributes and where to route a click. It's the mechanism by which an external network learns what jobs exist and whether they're still active, without a human manually re-entering the same data into a separate system.

02How Expertini's own job data feeds the ad tools

Rather than a separate feed export, the ad connectors read directly from the same job record you already maintain in the ATS: title, location, category and taxonomy, description text, and the job's real application page. When the Google Ads Connector or Microsoft Ads Integration builds a campaign, it's working from that one source of job data — you're not maintaining a parallel keyword list or ad-copy document by hand, and there's no separate feed file to keep in sync with the job posting.

03Why freshness matters, mechanically

A campaign built from stale job data — a role marked filled that a campaign doesn't know about, for instance — keeps spending against a position nobody's hiring for anymore. Because Expertini's ad tools read live from the job record rather than a periodically-refreshed export, a status change on the job (filled, paused, expired) is visible to campaign management immediately rather than waiting on the next scheduled feed refresh a separate export-based system would require.

04What this isn't

This isn't a public feed-export API for third-party job aggregators to pull from independently — that's a different product surface than what's covered here. This page is specifically about how the structured job data already in your ATS gets used by Expertini's own ad tools, not about syndicating jobs to arbitrary external partners.

Frequently asked questions

Do I need to maintain a separate feed file for the ad tools to work?⌄

No. The ad connectors read directly from the job record you already maintain in the ATS — title, location, description, category, application page — there's no separate export or feed file to keep synchronised.

What happens if I mark a job filled while a campaign is running?⌄

The status change is visible to campaign management immediately, since the tools read the live job record rather than a periodically-refreshed export — reducing the window where a campaign keeps spending on a role that's no longer open.

Is there a public API for external job aggregators to pull my listings?⌄

That's a different capability than what's covered here — this page is about how Expertini's own ad tools use your existing job data internally, not about third-party syndication.

What structured fields actually feed a campaign build?⌄

Job title, location, occupational category, description text, and the job's real application page are the core fields the Google Ads Connector and Microsoft Ads Integration read when constructing a campaign.

At a glance

Ad tools read your job record directly — no separate feed file to maintain
Same source of job data drives organic distribution and paid campaigns alike
Status changes (filled, paused, expired) are visible to campaigns immediately
No parallel keyword list or ad-copy document required per campaign
Not a public feed-export API for third-party aggregators — a different surface
One job record, read by all three ad tools consistently

See job feeds and structured job data on your own hiring.

Bring a real job description to a 30-minute demo — free trial included.

Book a demo