Background

T433621's "Essential work done through the kit" card defines ten tiles; nine are shipped. Tile 10 — accounts created via kit recruit links — is the one with no data source: the card deliberately omits unshipped tiles, so nothing user-facing is broken, but the metric itself is wanted and the blocker is attribution, not UI.

Split from T433621 so that task can close on deploy instead of staying open indefinitely on an externally-blocked item.

Current state

The kit already tags its recruit links: the share dialog (RecruitDialog.vue) builds Special:CreateAccount?utm_source=starterkit&utm_medium=<channel>, so every shared link carries attribution parameters today. What is missing is any known way to consume them — we are not aware of anything on the MediaWiki side that reports utm_* values back per created account, so the parameters currently ride along unread.

Open questions (for analytics)

Carrying over the open ask from T433621 (2026-07-30):

• Can the campaign= URL parameter on Special:CreateAccount be used for this instead of (or alongside) utm_source? Our understanding is that MediaWiki records it server-side, but whether that is so, where those records live, and whether a Toolforge tool can read them are all open.
• If campaign-attributed creation counts exist somewhere, how can the kit acquire them — e.g. periodic aggregate exports per (wiki, campaign, month)? Any cadence works: the tile can ship as a slower-refreshing metric, since the card already tolerates per-tile refresh differences.
• If neither parameter is consumable, is there any other analytics-side path to attributing account creations to a shared link?

Acceptance criteria (sketch — firm up once a source exists)

• Recruit links carry whatever identifier the answered questions above call for (utm_source=starterkit is already stamped today; adding campaign= is a one-line change if that is the consumable one).
• Tile counts account creations attributed to that identifier, windowed like the rest of the card, honoring the exclusion filters where applicable.
• The tile appears on the card only once real data flows (no placeholder values) — same shipping flag the other nine tiles used.
• Metric definition documents the attribution mechanism and its known blind spots.

Blocked on

Analytics guidance on a readable source for campaign-attributed account creations. No kit-side work is possible until that exists.