Analytics and attribution
Find out which sources actually produce applications
Bullhorn can tell you how many applications you received. It cannot tell you how many people looked at the job and gave up, or which board sent the ones who finished. That half of the funnel happens on your website, so your website is where it is measured.
First-party, on your own site. Nothing is recorded before consent.
| Started | Trigger | Duration | Result |
|---|---|---|---|
| 09:14:02 | WP-Cron | 6.2s | 34 changes |
| 09:09:01 | WP-Cron | 5.4s | No changes |
| 09:04:00 | WP-CLI | 2.1s | 3 submissions |
| 08:59:02 | WP-Cron | 1.3s | 1 skipped |
What it is
The gap between a view and a placement
Agencies spend money on job boards and aggregators and then judge them on applications that arrive in Bullhorn with no reliable record of where they came from. The honest answer is usually a guess, and the budget follows the guess.
W3Bullhorn records the four moments that matter on your own site — the job was viewed, an application was started, it was completed, it reached Bullhorn — and labels each one with the source it arrived from. The result is a funnel you can act on: not just how many applied, but how many nearly did, and from where.
What is measured
Four moments, each with a source
Enough to show where candidates are lost, without following anybody around the internet.
-
Interest
Job viewed
Somebody opened the job page, and the source they arrived from.
-
Intent
Application started
They began the form. The gap between this and the step before is the honesty of your job advert.
-
Applied
Application completed
They finished and submitted. The gap here is the honesty of your form.
-
Site → Bullhorn
Delivered to Bullhorn
It reached your consultants against the right job. A gap here is a technical problem, and you want to know about it.
Where the source comes from
Tagged feeds, so an aggregator cannot claim credit it is not owed
The feeds W3Bullhorn publishes to aggregators carry their own campaign tags, so a candidate who arrives from one is recognised as such. The tag is added to the copy of the address in the feed only — the job page’s own canonical address stays clean, which matters because a tagged URL competing with an untagged one is how job pages lose their place in search. The canonical address is also written back to the job record in Bullhorn, so the board and the CRM agree on where the role lives.
- XML feeds for Indeed, Jooble and a generic format
- Campaign tags on the feed copy of the address only
- The canonical job address written back to Bullhorn
- Direct, organic and referred visits labelled as such
One of 412 roles, each on its own URL. Eligibility for Google’s job experience remains Google’s decision.
Consent
Nothing is recorded before consent, by construction
Most analytics tools load first and ask permission afterwards. Here the job page carries a loader that is inert: it cannot fetch the measurement script without consent, and until consent exists that file is never requested, never parsed and never run. The difference between a policy and a mechanism is that a mechanism can be checked, and this one is checked by its own tests.
- No event recorded before consent exists
- The measurement script is not even fetched until then
- First-party: the data stays on your own site
- No measurable effect on how the page loads or how it is crawled
Specification
What it supports
The detail a technical buyer asks before a demo.
| What is recorded | Job viewed, application started, application completed, application delivered — each with a source label |
|---|---|
| Where it is stored | On your own site. It is first-party data, not a feed to a third party |
| Before consent | Nothing. The measurement script is not requested until consent exists |
| Where you read it | A funnel view in the WordPress admin |
| Feed tagging | Campaign tags applied to the feed copy of the job address, leaving the canonical address untagged |
| Back to Bullhorn | The canonical job address is written to the job record, repeatably |
Boundaries
What this is not
-
It is not placement attribution
It measures the website funnel up to the point an application reaches Bullhorn. What happens after that — interview, submission, placement — is Bullhorn’s to report, and we do not claim to tie a placement back to a click.
-
It is not a replacement for your analytics
It answers questions about jobs and applications. If you want site-wide marketing analytics, keep the tool you have; this sits beside it.
-
It does not follow people between sites
There is no cross-site tracking and no third-party audience to sell your visitors into. It records what happened on your own pages.
W3Bullhorn is an independent product. It is not affiliated with, endorsed by or sponsored by Bullhorn, Inc. Bullhorn is a trademark of its owner.
FAQ
Questions about analytics and attribution
Short answers here. Anything else, ask us directly.
Related features