INTEGRATIONS · EXPERTINI ATS

Google Ads Connector

Create and manage Google Ads campaigns for your published jobs without leaving the ATS.

2 min read · Updated July 2026 · Expertini Editorial

Organic reach fills many roles, but some vacancies — niche skills, unglamorous locations, urgent backfills — need paid demand. The Google Ads Connector lets you create and manage Google Ads campaigns directly from the jobs you have already published in Expertini ATS, so the job description, location, and apply URL you spent time getting right become the raw material of the campaign instead of being retyped into another console.

The gap this closes is the disconnect between advertising spend and hiring outcomes. When ads are run from a separate tool by a separate person, nobody can say which campaign produced which hire. Running campaigns from inside an ATS with Google Ads integration keeps the job, the ad, and the resulting applications in one system, so the hiring pipeline tells you what the spend actually bought. The connector is part of your subscription — you pay Google for the ads through your own Google Ads account, and nothing extra to Expertini.

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

01From published job to live campaign

Pick a published job and the connector carries its essentials into the campaign: the role you are promoting, the landing page candidates should reach, and the geography that matters. You keep full control of budget, bidding, and targeting in your own Google Ads account — the ATS removes the copy-paste, not your control.

Because campaigns start from real job records, they end when jobs do. Closing a role is your prompt to stop spending on it — no more orphaned ads promoting a vacancy that was filled a fortnight ago.

02Your account, your billing, your data

You connect your own Google Ads account, and Google bills you directly at Google's rates. Expertini adds no margin, no percentage of spend, and no per-campaign fee — the connector itself is included in the subscription. Your advertising history stays in your account even if you change ATS.

03Paid and organic, working together

Paid campaigns work best on top of a solid organic base. Every published job already reaches Google for Jobs automatically and can fan out across the Expertini network with programmatic distribution, so ads become the targeted boost for hard-to-fill roles rather than the only source of applicants. A well-written listing converts ad clicks better too — the job posting best practices guide covers what to fix first.

Engineering notes

Platform architecture & operations

A1Connection architecture

The connection model for this integration is stated honestly on its card: where a public API exists it is used with your own account and consent, and where a vendor requires a partner agreement the page says so instead of showing a Connect button that cannot work.

Once available, credentials follow the platform standard: encrypted at rest, presence-flag display, immediate removal on disconnect.

A2Write semantics and data flow

Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.

Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.

Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.

A3Operational considerations

Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.

Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.

A4Placement in the integration topology

This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.

Dependency map

Connection typestated per-vendor on the card

Secrets at restencrypted; UI shows presence flags, never values

Action journalats_app_activity — one row per action, vendor errors verbatim

Auto-push rulesoff by default, per-provider, every run logged

Registry statuslive

Interface blueprint

Structural schematic of the surface — panels, hierarchy, and interaction affordances. A contract, not a screenshot.

Connection card

● connected — presence flag

scopes: minimum required disconnect

Actions

push — explicit clickimport — deduplicated

Activity journal

Fig. 1 — Google Ads Connector: structural interface schematic. Panels and states are the contract; data shown is placeholder.

Interaction flow — states, validations, feedback

Every state below is enforced server-side; the interface reports it, it doesn't decide it.

Connectowner/admin clicks Connect on the Connectors page

Vendor consentthe vendor's own screen lists the exact scopes

Token exchangeserver-side callback; secrets never touch the browser

Connectedencrypted store; card flips with presence flag

Explicit actionspush / import / schedule — each one journalled

Consent denied → the vendor's error code surfaces in a toast, namedPlatform keys missing → honest setup pointer, not a silent bounceToken expired → automatic refresh at the chokepointRefresh rejected → visible reconnect prompt, features never break silentlyPlan below minimum → lock card names the exact plan

Fig. 2 — interaction flow: navy = states, gold = server-enforced gates, green = confirmed outcomes; tags list the edge cases and their feedback.

Frequently asked questions

Do I need my own Google Ads account?⌄

Yes. You connect the Google Ads account your company owns and Google bills you directly for ad spend. Expertini adds no markup and takes no percentage of your budget.

Does the connector cost extra?⌄

No. It is included in your Expertini ATS subscription. Your only advertising cost is what you choose to spend with Google.

Can I still manage campaigns in the Google Ads console?⌄

Yes. Campaigns created from the ATS live in your own account, so budgets, bids, and reports remain fully accessible in Google's own tools.

Which jobs can I advertise?⌄

Any job published in your ATS. Draft jobs need to be published first so there is a live landing page for the ad to send candidates to.

At a glance

Launch campaigns from published jobs in a few clicks
No retyping job details into another console
Your own Google Ads account and billing
No markup or percentage-of-spend fees
Connect spend to pipeline outcomes
Included in every subscription

See google ads connector on your own hiring.

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

Book a demo