← All patents

Family 04 · 2015 — 2016 · 3 filings · Priority March 20, 2015

Direct Response Platform

On-Line Direct Response Platform

Trigger events + preselected profiles = an atomic opportunity. A pre-agentic formulation of real-time event-to-action systems.

WOUS

Representative filings

  • WO/2016/154153
  • WO/2016/154155
  • US 2016/0275566

The problem

The prior families answered "who is this user" and "how valuable are they" — this one answers "when do we act." Before 2015 most targeted advertising was scheduled or audience-retargeted; it fired when the advertiser decided to buy impressions, not when the real-world situation actually changed. The patent makes the trigger the situation itself — a preselected profile appearing at a specific location is the signal that an opportunity exists right now.

The mechanism

The system maintains preselected user profiles (identified by device ID and associated with a home location) and trigger events (a rule asserting that a profile has been observed at a second, campaign-specified location). When the trigger fires, the system instantiates an advertisement opportunity and routes it — with the user's profile score attached — to an advertiser, who may deliver content to the device. The novelty is the tight coupling of three signals into one atomic event: identity (device ID), location (second location), and qualitative score (from Family 2), bound by a rule. The exchange becomes event-driven rather than auction-scheduled.

What it proved

Real-time event-to-action is a distinct pattern from audience-targeting. Once you have good enough identity and a good enough scoring function, situational triggers are the highest-leverage moment to act, because the situation itself is evidence of intent. This is the conceptual ancestor of geofenced retargeting, real-time CDPs, event-driven marketing automation, and every "moment-based" marketing pitch of the last decade.

If it were built today

Trigger-event architecture in 2026 is agentic tool-calling with a rules layer. The preselected profile becomes a memory entry in an agent's context (persistent per-user). The trigger event becomes a streaming condition evaluated by a real-time event bus (Kafka, Redpanda, Tinybird, or Temporal workflows). The "advertisement opportunity" generalizes to any agent-executable action: send a message, initiate a payment, unlock a door, dispatch a dispatcher, enroll in a benefit. The device-ID + location tuple is joined by richer telemetry — biometric state (HRV, sleep), transaction stream, calendar context, even LLM-inferred intent from conversational history — and a policy layer decides which triggers are permitted and under what consent. The cleverest part in 2026 is reversibility: trigger events in an agentic system must be auditable, undoable, and rate-limited because an LLM-driven trigger can do actual damage (send money, lock an account). The Family 4 pattern is the architectural template; the 2026 version bolts on policy, provenance, and reversibility.

Three marketplace applications

Outside the context it was born in.

  1. 01

    Chronic-care patient outreach

    ProblemA diabetic patient skips blood-sugar logs for five days; by the time a nurse sees the chart, the window is closed.

    ApproachPreselected patient profile + trigger event (no log for ≥ N days AND location ≠ clinic) → care-team alert, possibly a pre-composed text from the care coordinator's agent.

  2. 02

    Agentic replenishment across contexts

    ProblemA household's dog food runs out on a trip, but the auto-reorder system is geo-ignorant.

    ApproachHousehold profile + trigger (pantry IoT reports low AND user's phone location is >50mi from home) → agent negotiates delivery to the travel address, inside a pre-authorized policy envelope.

  3. 03

    Workplace-safety interventions

    ProblemLone field workers (linemen, EMTs, drivers) are hardest to protect because conventional alert flows are batch.

    ApproachWorker profile + trigger (location enters high-risk polygon AND biometric stress spike AND no scheduled task here) → dispatcher agent checks in, escalates, or dispatches backup.

Architecture sketch

The components the system needs to exist.

  • 01Preselected profile store (device ID + home/primary location + Family 2 index)
  • 02Trigger-rule engine (situation-detection DSL: where, when, with whom)
  • 03Real-time location / event ingest (streaming, low-latency)
  • 04Opportunity instantiator (bundles profile + event + score into an atomic event)
  • 05Advertiser / actuator routing layer (who gets to act on this opportunity)
  • 06Delivery channel (device in the original patent; any actuator in 2026)
  • 07Consent + policy envelope (2026 addition) — what triggers are allowed, at what rate, reversible how
  • 08Agent audit log (2026 addition) — every fired trigger is a reviewable event