Core concepts

Pathbound is the customer-context layer for AI agents and humans. It connects data from your CRM, website analytics, email, and other tools into a single profile per contact and company — then exposes that context through three surfaces: the REST API, the MCP server, and Events.

The object model is small. Once you understand contacts, companies and events, the rest of the docs is the API surface around them. Deals, tags and segments build on those three.

A contact is a person tracked across all connected sources. Every contact has:

• A unified profile — properties merged from CRM, enrichment providers, and form submissions.
• An event timeline — chronological cross-system activity (page views, opens, replies, syncs).
• Notes — free-form internal annotations.
• Conversations — email threads, Intercom chats and recorded meetings (when those sources are connected).
• An association with one company.
• Tags, and membership of segments.

→ Contacts API

A company is the primary B2B unit. Individual contacts roll up to company-level intelligence. Companies are identified by domain and have properties like industry, employee_count, and lifecyclestage. When you query a company, Pathbound returns its associated contacts (up to 25).

→ Companies API

An event is a tracked interaction across any connected source — a page view, button click, form submission, video play, email open. Events are linked to a contact (when the visitor is identified) and provide the behavioral signal layer of the unified profile.

The events snippet is the most common source of events, but events can come from email opens, CRM webhooks, and embedded video players.

→ Events API

A deal is a revenue opportunity: a name, a stage, an amount, a close date and a status (open, won or lost). A deal is linked to a company, a contact, or both. Deals are created in Pathbound, through the API or by an AI agent.

→ Deals API

A tag is a short label on a contact, a company or a deal, such as vip or webinar-oct. Your code, your teammates and your AI agents can all add and remove tags, and filter on them.

A segment is a named set of filters over contacts or companies, such as “customers in Germany with more than 200 employees”. Save it once, then use it by name to list, count, tag, enrich or email everyone in it.

→ Tags API · Segments API

Snippet  ───▶  Events  ───┐
                          │
Connected sources  ───▶  Contact  ───▶  Company
(CRM, email, etc.)        │
                          ▼
                  Unified customer profile
                  (read by your code, your
                   AI agents, or Claude.ai
                   over MCP)

A typical loop:

1. The snippet captures behavioral events on your site.
2. A form submission (public form endpoint) identifies the visitor — events are now linked to a contact.
3. CRM, enrichment, and email sources merge into the contact’s unified profile.
4. Your code (or an AI agent connected over MCP) reads the profile and timeline to make a decision.
5. It acts on the decision: a tag, a note, an email, or a stream that pushes the change to your own systems.