Referrer (traffic source)
The query parameter: referrer labels where a jobseeker was on your properties when they clicked through to Talroo.
Use it to slice performance by acquisition surface—rolled up in Analytics (pie chart: Referrer domain) and in Earnings Report detail downloads (column referrer_url aligns with the value you pass).
| Channel | Where you set referrer |
|---|---|
| XML (and other click-URL flows) | Append referrer to the outbound job url from the feed |
| Search API | Add referrer on each GET api request. |
Set referrer to a website domain or host that best represents the source (for example jobs.example.com or www.example.com). For a mobile app or email program where there is no literal web referrer, send a stable stand-in (Maybe your public marketing or home page domain—so reporting stays consistent).
What to put in the value
- Web surfaces — Use the domain (or hostname) users were on when they clicked (for example the subdomain that served the job list).
- Non-web or blended inventory — Pick a canonical domain your team agrees represents that channel (app store listing domain, careers site, newsletter domain, etc.).
- Encoding —
referrermust be URL-encoded when the value contains reserved characters (&,=, spaces, UTF-8, etc.).
Use referrer for source / placement identity. Use t1, t2, t3 when you need arbitrary campaign or experiment labels — see T-Values (Tracking Tags). The dimensions are independent: combine them when you need both “which site” and “which campaign.”
Where it shows up in TAP
- Earnings Report — Downloaded click rows include
referrer_urlreflecting the referrer you attributed. - Analytics — Publisher Summary includes a Referrer domain pie chart summarizing click mix by the domains you labeled.
Related
- Click validation — Valid vs. expired or stale clicks (referrer does not bypass eligibility rules).
- Tracking tags —
t1–t3for additional dimensions. - RDR (Redirect) — Optional fallback URL when a listing stops earning (orthogonal to referrer).