T-Values (Tracking Tags)
t1, t2, and t3 are optional tags you add to outbound job click URLs (or to eligible Search API query parameters) to segment reporting by campaign, placement, traffic source, or any scheme you maintain. They behave like UTMs or affiliate SubIDs but roll up directly in Talroo's publisher reporting.
- What you get: Performance by segment — clicks and earnings with your tag dimensions preserved
- Where you see it: Exported detail rows from Earnings Report in TAP—use Details (download) per day or period total;
t1,t2, andt3show up as CSV columns when you populate them on click URLs upstream. T-Values Reporting API still serves hourly JSON for grandfathered setups. - Why it helps: Clean A/B tests, source comparison, and moving spend toward winning segments without waiting on a separate web analytics toolchain
These tags describe traffic you label. How clicks are judged valid or stale is unchanged — see Click Validation.
Compared to UTMs and SubIDs
| Feature | UTM parameters | SubID | T-values (t1, t2, t3) |
|---|---|---|---|
| Purpose | Marketing analytics | Affiliate / network tracking | Flexible Talroo publisher segmentation |
| Common fields | utm_source, utm_medium, utm_campaign | subid, subid1-5, etc. | t1, t2, t3 |
| Reporting | Web analytics stacks | Partner dashboards | TAP earnings export (+ optional legacy API) |
Specifications
| Property | Rule |
|---|---|
| Parameters | t1, t2, t3 — each optional |
| Maximum length | 100 characters per tag |
| Encoding | Append as normal query parameters; URL-encode values that include reserved characters |
Common naming patterns
| Tag | Typical role | Examples |
|---|---|---|
t1 | Campaign or product surface | email_2026, home_hero_jobs |
t2 | Source or placement | google, newsletter_q1 |
t3 | Detail keyword / variant | nursing_remote, variant_b |
How to attach tags
Use the t1, t2, and t3 query parameters wherever your integration exposes a Talroo job click: Search url payloads, XML <url> values, and widget-produced links.
XML and affiliate-style click URLs
Append query parameters to the click URL Talroo provides (do not strip required tracking keys).
Original URL:
https://www.jobs2careers.com/click.php?jid=abc123&ri=def456
With optional tracking tags:
https://www.jobs2careers.com/click.php?jid=abc123&ri=def456&t1=campaign_name&t2=traffic_source&t3=keyword_variant
If you also use rdr (fallback when a job is no longer monetized), keep both values correctly URL-encoded — RDR (Redirect).
Search API publishers
Pass t1, t2, and t3 on GET search.php so job-level url fields inherit the segments you need — see API Integration.
Earnings Report (TAP)
Step-by-step UI (filters, feed chips, Downloads column): Earnings Report. Exports reconcile against the same tagging rules summarized above.
Operational tips
- Stable dictionaries — Pick naming conventions early (
snake_case, fixed campaign IDs) so pivots remain readable quarter over quarter. - Avoid exploding cardinality — Ultra-granular
t3values make exports noisy; collapse variants when you don’t truly need row-level fidelity.
Related
- RDR (Redirect) — optional redirect targets for listings that stopped earning
- Click Validation — valid vs stale / expired payout considerations
- T-Values Reporting API — hourly JSON API (legacy, permissions required)
- Programmatic TAP access — OAuth/App Client reporting paths over time