StudySmarter Jobboard — Application Overview

Range: 7d 30d 90d

Cross-country headline (current vs prior period)

Daily applications — all geographies

Direct customers — at-risk accounts

Data quality — SLA status across feeds

Applications (30d)

Unique applicants

Companies applied to

Mega Apply success

Remote/Hybrid share

Super-applicants (≥20 apps)

Live jobs total

Imported in last 24h

Newly processed (24h)

created_at < 24h ago

SP2 freshness

Apply opens (Amp, 30d)

wp_job_application_open

Apply complete (DB, 30d)

jbbrd applications

Open → Complete conversion

apply_complete ÷ apply_open

Apply funnel — Germany (30d)

Daily applications (30d)

Job type split

Top 20 categories — applications

Jobs vs Applications by category (top 20 by apps)

Top 20 job-location cities

Top 20 applicant home cities (Wohnort)

Applications by Bundesland

Apps per applicant (distribution)

Mega Apply funnel (ATS integration outcomes)

Remote mode

Top applicant email domains

SP2 freshness segment — Search Priority 2 jobs imported in last 24h

Distribution of high-priority jobs from the most recent feed refresh. “City (50km)” clusters each job to the nearest major DE hub within 50km.

SP2 per company (top 20, last 24h)

SP2 per feed (top 20, last 24h)

Apps per feed (top 20, 30d)

Live jobs per feed (top 20)

Per-feed traffic vs feed size — Germany

Compares feed size (live jobs) vs traffic (Amplitude clicks, applications, ATS-success Mega Apply submits). per-1k-jobs columns let you see which feeds get disproportionate traffic for their size. Amplitude clicks attributed via partner-name match; — means no matching partner found.

Traffic vs feed size — Amp clicks per 1k jobs (top 30 by clicks/1k jobs)

Bar = clicks per 1,000 live jobs. Hover for raw jobs and clicks. Tall bar = punching above its size; short bar on a big feed = under-trafficked.

Feed economics bubble — Amp clicks per 1k jobs (X) vs avg CPC (Y)

Each bubble is a feed (size = live jobs, both axes log scale). Top-left = expensive but low traffic per job (cut candidate). Bottom-right = cheap and high-traffic (scale candidate).

SP2 combinations with >1 job — City(+50km) × Category × Job type

City (50 km) Category Job type SP2 jobs

Applications (30d)

Unique applicants

Companies applied to

ATS integration

rarely used on UK

Remote/Hybrid share

Super-applicants (≥20 apps)

Daily applications (30d)

Job type split

Top 20 categories — applications

Jobs vs Applications by category (top 15 by apps)

Top 20 job-location cities

Apps per applicant (distribution)

Applications by UK region vs population share

Remote mode

Top email domains

Live jobs total

Imported in last 24h

Newly processed (24h)

created_at < 24h ago

Jobs vs apps snapshot

Apply opens (Amp, 30d)

wp_job_application_open

Apply complete (DB, 30d)

jbbrd applications

Open → Complete conversion

apply_complete ÷ apply_open

Apply funnel — United Kingdom (30d)

Apps per feed (top 20, 30d)

Live jobs per feed (top 20)

Per-feed traffic vs feed size — United Kingdom

Compares feed size (live jobs) vs traffic. Mega Apply isn't used on UK so the "ATS submit" column shows application_type='ats' count. Amplitude clicks attributed by partner-name match; — means no matching partner found.

Traffic vs feed size — Amp clicks per 1k jobs (top 30 by clicks/1k jobs)

Bar = clicks per 1,000 live jobs.

Feed economics bubble — Amp clicks per 1k jobs (X) vs avg CPC (Y)

Each bubble is a feed (size = live jobs, both axes log scale). Top-left = expensive but low traffic; bottom-right = cheap and high-traffic.

Applications (30d)

Unique applicants

Companies applied to

Live jobs total

Imported in last 24h

Newly processed (24h)

created_at < 24h ago

Apply opens (Amp, 30d)

wp_job_application_open

Apply complete (DB, 30d)

jbbrd applications

Open → Complete conversion

apply_complete ÷ apply_open

Apply funnel — United States (30d)

Daily applications (30d)

Job type split

Top 20 categories

Top 20 job-location cities

Applications by US state

Apps per applicant (distribution)

Remote mode

Top email domains

ATS (direct apply)

Per-feed traffic vs feed size — United States

Compares feed size (live jobs) vs traffic. Mega Apply isn't used on US so the "ATS submit" column shows application_type='ats' count. Amplitude clicks attributed by partner-name match; — means no matching partner found.

Traffic vs feed size — Amp clicks per 1k jobs (top 30 by clicks/1k jobs)

Bar = clicks per 1,000 live jobs.

Feed economics bubble — Amp clicks per 1k jobs (X) vs avg CPC (Y)

Each bubble is a feed (size = live jobs, both axes log scale). Top-left = expensive but low traffic; bottom-right = cheap and high-traffic.

Active contracts

companies with goal > 0

Total monthly goal

apps / month contracted

MTD delivered

Projected EOM vs goal

At-risk accounts

Avg attainment

across active accounts

Contracted deal revenue

click any "Deal €" cell below to add/edit

Account Manager scorecard — pacing across portfolio

Contract leaderboard — Goal vs MTD (with EOM projection & attainment)

Company AM Apply setup Goal / mo MTD 6mo Source split Apply type 7d Last mo Proj EOM Attainment Deal € Target CPA Effective CPA Ends
Source: application_goal_monthly > 0 + end_date >= today. MTD counts all apps for the company's company_id (direct-feed + aggregator-feed combined). Source split: “Direct” = apps via a feed whose company_id meta points to this customer; “Agg” = apps for the same company that came via an aggregator feed (Whatjobs, XING, Stepstone, …). Apply setup: MA = Mega Apply enabled (sts_core_integration_mega_apply=1) · ✉ = contact email set. Apply type: ATS (direct submit), RED (redirect), E (email) counts within MTD.

Top customers by monthly goal

Top customers by MTD delivery

Open in new tab ↗

Amplitude revenue (30d)

Actual revenue (30d)

Actual / Amplitude

Data coverage

Trust-adjusted revenue (calibrated partners only)

Per-partner — Amplitude vs partner-reported (30d totals)

Each row sums 30d of the live Amplitude chart vs what the partner's own platform (Appcast publisher, Tideri Metabase, Whatjobs / J-Vers APIs) reports. Applications follows the business rule CPA or 5×CPC: CPA partners (MA-enabled) use Amplitude's wp_job_application_submit event count (CPA); CPC partners use clicks ÷ 5 as a proxy (÷5). Internal SUCCESS = sts_ats_integration_status = 'SUCCESS' rows from jbbrd_*_sts_job_applications (DE + US sites). A dash means that data source doesn't track that partner.

Per-partner CPA breakdown — CPA-tracked partners

For CPA partners (MA-enabled), the meaningful unit-cost is cost per application, not cost per click. Amp CPA = Amplitude revenue ÷ Amplitude MA-submit events. Actual CPA (vs SUCCESS) = real partner billing ÷ internal sts_ats_integration_status='SUCCESS'. Actual CPA (vs submits) = real partner billing ÷ Amp MA-submits — same denominator as Amp side, so the ratio of these isolates the revenue difference. Big gap between the two "Actual CPA" columns means our ATS integration drops a lot of submits before they convert (e.g. WhatJobs).

Per-feed CPC breakdown — actual cost-per-click by partner feed

One row per feed in the KPI scraper config. Actual CPC = partner-reported revenue ÷ partner-reported clicks (30 d). The Amp partner CPC column repeats the partner's blended Amplitude CPC for context — feeds within the same partner share that value. Diff = how much the feed's actual CPC differs from the Amplitude blended figure. Big positive = Amplitude under-charges relative to reality; big negative = over-charges. Source backfill = scraped /by-day; csv = nightly KPI scraper CSV.

Partner drilldown — daily trend

Pick a partner to see how Amplitude tracks each day against partner-reported numbers.

Revenue (€) — daily

Clicks — daily

Avg CPC (€ / click) — daily

Actual % of Amplitude — revenue & clicks — daily

Underlying Amplitude charts

· — total revenue formula PROPSUM(cpc + cpo + cpa)
· — MA-only revenue
· Bot-free segment: userdata_cohort ≠ jgdixuci

Amplitude revenue vs actual billed revenue — per partner, by month

amp / billed ratio: 1.0 = aligned · >1 = Amplitude over-counts (we're over-reporting our own revenue) · <1 = Amplitude under-counts. Manual billed numbers go in dashboard_data/billed_revenue_overrides.json; KPI scraper auto-fills March+ where available.

Geo monthly drift — Amp / Billed ratio over time

A flat line = stable calibration. A rising or falling line = the gap between Amplitude and actual billing is shifting. Y-axis log-scaled to show big swings clearly.

Per-feed drift — pick partners to compare

Click partners on the left to plot their amp/billed ratio month-over-month. Only partners with ≥1 month of billed data are listed.

V26 Job-Alert Performance

Loading…
Attribution:
View:

Pacing against plan (v26 window vs same days of plan_daily())

By geography (v26 actual · April baseline · plan window)

By template type

Geo × Template

Geo × Template × Build (active builds only)

Daily timeline

Sends / unsubs / spam: SendGrid Categories Stats API. Unique opens: SendGrid raw (includes machine opens — apples-to-apples vs April). Clicks: local SendGrid Click-Bot-Analysis webhook with scanner-IP/UA filter (Azure / AWS / Mimecast / Proofpoint / Defender / CloudFront / Google-Image / Yahoo / Apple-Privacy). Click numbers from before webhook history (pre-2026-04-15) fall back to SendGrid raw and are marked with a *. Plan: pool-projection model from plan_daily() in /opt/uk_v8_alerts/jobalerts_dashboard.py, V14-quality assumptions, 7% / day growth capped at full mailable pool.
Open in new tab ↗

Partner Bid Optimization

Loading…
Auction replay: for each logged dedup matchup the partner participated in, we simulate the comparator at +€0.05, +€0.10, +€0.20 and +€0.40 CPC. New auction wins × current clicks-per-won-auction → projected 30d clicks. Recommendation = smallest Δ with ≥10% clicks uplift and ≥5% revenue lift.
Partner Current CPC (€) Clicks / 30d Revenue / 30d (€) Auctions Recommend Δ (€) Proj. clicks @ rec Uplift %
Source: talents.jbbrd_sts_* (DE) and talents.jbbrd_2_sts_* (UK) on RDS · Window: last 30 days (2026-03-24 → 2026-04-23). Category / job-type for DE use direct job link + company-peer fallback (≈76% coverage, “(unknown)” hidden in charts). Remote mode reflects only applications whose job row is still live (~20% of apps), since the flag lives on the job record. Mega Apply = StudySmarter EasyApply / ATS integration outcomes (sts_ats_integration_status). Applicant home cities/states read from jbbrd_postmeta.Wohnort (≈100% coverage, DE only). Population baselines: DE Destatis 2024, UK ONS mid-2023. Job-location state baseline shows live-job count share.