TEAS × URSY · PAID SPONSORSHIP

Sponsor Trail

What the URSY sponsor links brought to TEAS, and what the evidence can actually establish.

Status: counting. Snapshot: 2026-09-13 09:10:23 UTC. This is a recent stored snapshot.

Campaign

teas-ursy-2026-09-v1 · 2026-09-01T00:00:00Z to 2026-09-30T23:59:59Z

Registered placements: 1150. This describes available placements, not observed deliveries.

Tracking redirect requests · Grade A

GET and HEAD redirects recorded at the TEAS origin with HTTP 302. Browser POST receipts appear separately below. Counts are best-effort observations; caching, database failures, logging limits and disabled periods can leave gaps.

Browser arrival receipts · consent required

The TEAS landing page sends a first-party POST after statistics consent. Each accepted event is recorded once with HTTP 204; retries do not create extra arrivals. These receipts are measured separately from tracking redirects, so a cached redirect does not need to write an arrival or set a session cookie.

Transport: enabled. Collection began: 2026-09-12 05:05:32 UTC. Consent and JavaScript limited. Windows before collection began are partial; disabled periods, browser delivery failures and write limits can leave gaps. These are events, not unique people, clicks or sales.

Human classification comes from the existing user-agent rules; a POST or JavaScript execution does not prove a human visitor. Verified tests and unverified test claims are excluded. Counts describe events, not unique people, ad clicks or sales. Existing signed-session associations remain private.

Legacy origin imports

Each row comes from a separately dated origin snapshot. These are machine deliveries carrying the sponsor block; generated files are not counted as delivered responses. Human-page placement availability does not create a per-human origin event.

Import status: partial_or_unavailable. Import run: 2026-09-13 09:10:23 UTC. Source times and per-site unavailable states are retained; this is not a cross-site matched funnel.

Later same-family reads · Grade B

Fixed windows: 15 minutes, 1 hour, 6 hours, 24 hours, 72 hours and 7 days. The reader uses the existing TEAS mint v4 served-read qualification rule and waits for completed UTC source days. A shared family name does not establish the same machine or causation.

unavailable: no completed correlation projection is available. Open, unprocessed or failed windows are not recorded as zero.

Sponsor probes are excluded from production arrival cohorts.

Historical source baseline · Grade C

Qualified TEAS source observations before this campaign, compared with completed campaign days. This is a historical baseline comparison, not evidence that sponsorship caused a change. It cannot fill missing tagged-arrival or outcome links.

Status: observed_source_context. Snapshot 2026-09-13 03:25:20 UTC; completed period ends 2026-09-13 00:00:00 UTC. Observed source days: 42 / 42. Earliest retained observation: 2026-06-02 12:34:57.640.

A day with retained source activity can still contain ingestion gaps. Counts describe observed eligible records, not all traffic. A missing or failed source day nulls any period requiring it; no interpolation or missing-day zero is used.

Rolling family baselines · Grade C

These dated rolling windows reuse the same retained qualified TEAS source records. They describe source activity and cannot establish sponsor exposure, event matching or a causal effect.

Completed UTC boundary: 2026-09-13 00:00:00. Retained completed-job UTC boundary, capped at campaign end; no post-campaign rolling continuation is claimed.

Existing TEAS outcomes · estate context

These existing mint records are shown for context. The current public evidence does not establish which URSY exposure led to a human clickback or sale, so sponsor-attributed outcomes remain unavailable. An outcome is never relabelled merely because it happened later.

Verified and probable human clickbacks remain separate. Refund counters are separate additive records. Uses the existing mint rules and their published source exclusions. Legacy outcome sources do not provide a complete independent sponsor-probe cohort.

What this proves — and what it does not

• Grade A records a request to a validated campaign/placement tracking URL, not proof that a particular earlier exposure caused it.
• Browser arrivals count separate, deduplicated POST receipts after statistics consent. JavaScript and consent limit coverage; a browser receipt is not proof of a unique person, an ad click or a sale.
• Browser session association, when eligible, uses an existing signed TEAS session and remains private. Browser collection creates no visitor identifier or session cookie.
• Caller family and worker come from the existing TEAS user-agent classifier; this does not authenticate the organisation operating the requester.
• A later same-family read is correlation. An AI-referred human or later sale is not automatically attributable to URSY.
• Registered placements are capabilities, not observed sponsor deliveries. Cached URSY responses may be unseen by application logging.
• The system stores no raw IPs, user agents, referrer URLs, cookies, nonces or cross-site actor pseudonyms. Public output is aggregate only.

Retention: append-only; no automatic purge. Rule 2026-09-11.v1. At most 600 arrivals per minute; lock contention or database failures skip telemetry and keep the redirect working.