Case studyPixel
Anonymous traffic,
turned to pipeline.
Pixel is a multi-tenant lead-capture and retargeting platform. One lightweight pixel on a client's site identifies visitors, enriches them, and pushes them straight into HubSpot — no forms, no friction.
Beacon active
acme.io→ HubSpot
northwind.co→ HubSpot
anonymousqueued
lumen.health→ HubSpot
parallax.dev→ HubSpot
anonymousqueued
resolved today 1,284match rate 42%
# EngagementLead-gen platform
# RoleDesign → deploy
# StackReact · Python · Supabase
# SurfaceMulti-tenant SaaS
# IntegrationHubSpot CRM
# StatusIn production
# 01 /The problem
Most of your traffic
leaves no name.
Forms capture a sliver of intent. Everyone else — the researching buyer, the returning visitor, the high-intent lurker — leaves anonymous. The pipeline they represent is invisible, and the retargeting you can run on them is generic at best.
Pixel closes that gap — without asking the visitor for anything.
# 02 /What we built
One pixel.
The whole funnel.
A single embedded beacon captures every visit, resolves who's behind it, and routes it into the client's CRM in real time — the entire path from anonymous hit to CRM-ready contact, automated.
01VisitAnonymous hit
02Pixel1×1 beacon fires
03IngestPython API
04ResolveIdentity + enrich
05SupabaseRow-level store
06HubSpotCRM sync
# 03 /How it works
A keyed beacon. One line of code.
Each client gets a uniquely keyed pixel. It drops onto any site in a single tag — no SDK, no build step. From that moment, every visit streams into the capture API.
- Per-client key isolates every tenant's data end-to-end.
- Captures far more than forms — across the whole session.
- Runs for many clients at once on shared infrastructure.
# 04 /Architecture
Four layers.
One multi-tenant system.
A React console on top, a Python capture-and-resolution API underneath, Supabase Postgres for isolated multi-tenant storage, and a real-time HubSpot sync layer.
L1DashboardReact · Next.js · TailwindPer-client analytics, audience builder, CSV / API exports.
L2Capture APIPython · FastAPIPixel ingest, identity resolution, third-party enrichment.
L3DataSupabase · Postgres · RLS · RealtimeMulti-tenant store with row-level isolation per client.
L4SyncHubSpot API · WebhooksContacts, lists, and retargeting audiences, pushed in real time.
# 05 /Results
The numbers
behind the pixel.
What form-free capture looks like once it's running in production — across every client on the platform.
0
forms required. Every visitor is captured on the pixel itself — never behind a gate.
0.0m
anonymous visitors resolved and enriched into named, CRM-ready contacts across the platform.
<0s
from capture to a live HubSpot contact — visitors sync to the CRM in near real time.
0
clients run concurrently on one platform — fully isolated, on shared infrastructure.
↳ Illustrative figures — replace with audited numbers before publishing.
# 06 /Capabilities
What Pixel ships with.
Everything a growth team needs to turn raw traffic into a working, CRM-native pipeline.
# 01Form-free capture
Identify visitors from a single embedded pixel — no gated content, no forms, no friction.
pixel · beacon
# 02Identity resolution
Match anonymous traffic to companies and roles, then enrich with firmographic data.
match · enrich
# 03Multi-tenant by design
One platform, many clients. Strict row-level isolation in Postgres keeps every tenant sealed.
rls · per-tenant
# 04Real-time HubSpot sync
Resolved visitors land in the client’s CRM in seconds — as contacts, lists, and audiences.
crm · <2s
# 05Retargeting audiences
Build and export high-intent segments from real behaviour, ready for ad platforms.
segments · export
# 06Client dashboard
A React console for live capture, audience building, and exports — one login per client.
react · realtime
# Engage
Let's talk growth.
30-minute scoping call. You leave with a written scope and a target ship date — or with an honest “we're not the right firm.”