SDR
Pre-signup intent
When a contact identifies themselves, your SDR agent already knows the pricing pages they read, the demos they watched, and the case studies they sat with. First outreach lands with full context — no cold opens.
Auto-captures every page view, click, form submit, video, and in-app action — and links each one to the unified customer profile in real time. The behavioral half of every contact's record.
Behavioral data is what separates an agent that knows your customer from one that just knows their record. The tracker is what every agent on the team draws from.
When a contact identifies themselves, your SDR agent already knows the pricing pages they read, the demos they watched, and the case studies they sat with. First outreach lands with full context — no cold opens.
Every in-app action mapped to the contact. Your CSM agent knows which features stuck, where onboarding dropped, and which seats have gone dormant — without instrumenting a separate product analytics tool.
When a customer opens a ticket, your support agent already sees what they did before — the page they were on, the error they hit, the setting they just changed. No "can you walk me through what you tried?"
Your retention agent gets paged when usage drops, a key feature stops being touched, or a documented churn signal fires — not at the end-of-month dashboard review.
Anonymous events are stitched onto the contact the moment they identify themselves — sub-second, retroactive, no duplicates. The pre-signup half of the SDR story below.
The pricing-page visits, the half-watched demo, the blog posts that brought them in. All of it stitched onto the contact the moment they sign up — so your agent can answer "why is Jane here, and how warm is she?" with real evidence.
Senior PM evaluating Acme's billing integration. Visited /pricing 3× in the past week, watched 75% of the demo, read the Atlas fintech case study. High intent, late-funnel — best reached with pricing-context outreach, not top-of-funnel content.
{ "contact_id": "ctc_01H…", "email": "[email protected]", "name": "Jane Reyes", "title": "Senior PM",
"company": { "domain": "acme.com", "industry": "fintech", "employees": 240 },
"lifecycle_stage": "trial", "intent_score": 0.86, "first_seen_at": "2026-04-15T…",
"summary": "Senior PM evaluating billing integration. /pricing 3×, demo 75%, read Atlas case study. High intent, late-funnel.",
"signals": ["pricing_intent", "compared_alternatives", "technical_evaluator"],
"events": [
{ "type": "page_view", "path": "/blog/customer-context", "at": "…14d", "resolved_from": "visitor_a91c" },
{ "type": "page_view", "path": "/pricing", "at": "…6d", "scroll_depth": 1.0 },
{ "type": "video", "name": "product_demo", "at": "…6d", "progress": 0.75 },
{ "type": "page_view", "path": "/pricing", "at": "…2d", "visit_count": 2 },
{ "type": "signup", "email": "[email protected]", "at": "…now", "merged_visitors": 1 }
],
"_meta": { "tokens": 312, "pii_redacted": false, "freshness_ms": 480 }
}No SDK to install, no .identify() to call, no event taxonomy to design. The tracker auto-captures what matters; the cookie is the identity signal.
One line in <head>. Page views, clicks, form submits, scroll depth, video milestones — all auto-captured for every visitor.
<script async src="https://tracker.pathbound.ai/tracker.js"></script>Set one cookie with your internal user ID. The tracker reads it from then on and binds every event — past and future — to the unified profile.
// In your app, after login or signup:
document.cookie =
"pathbound_external_contact_id=user_4f3a...;"
+ " path=/; max-age=31536000; SameSite=Strict; Secure";DNT honored · HTTPS-only · no third-party cookies · content-stable fingerprint (not cross-site identifying) · full audit trail of every merge.
Sign up. Drop in the tracker snippet. Connect one CRM. Point your MCP client at mcp.pathbound.ai/mcp.