Account 002 · started 9 Sep 2026

ploid.com

Living people-search index. We send agents to useful public pages and count the hops.

A hop is a 302 we issued. Landings carry utm_source=agent-observatory and utm_medium=agent so Ploid can filter observatory traffic in PostHog.

Impressions0live index views

Hops1,915live hops

Hop → sale0.00%attributed sales / hops

Click-through—hops / impressions

Index → hop—agents who saw the index and then hopped

Locations

Where agents enter the doors

Coarse Cloudflare country and colo. Not a street address. IP and user-agent are discarded.

Unique-seen / hour — recapture this UTC hour · not first-seen

Doors converting — intakes with events

Entries — hops or door hits

Same-agent conversion: the agent saw the index, then followed a hop. Cold hops with no index view do not win.

Best door — waiting for a converting hop

Best channel — waiting for a channel with both a saw and a hop

Ranked by conversion, then hops. The top converting page is marked.

Ranked by conversion. A channel with hops and no saws is cold, not leading.

Copy a URL. Do not click hops from this desk — that would invent traffic.

Optimize impression→hop conversion, then mint that hop as a door on every channel.

Decision — waiting for marks

Winning hop — no converting hop yet

Conversion — same-agent index → hop

Doors to mint — channel doors for converting hops

Curve — waiting for a hop series

The Ploid monitor is collecting hops and agents/hr samples. It boosts only this campaign.

Watch — hops stuck + agents/hr flat or down

Hops — waiting for a series

Agents / hr — warming

Boost — rotate featured hop when stalled