> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Segments
> Group partners into dynamic or static segments that target content, notifications, permissions, and more - audiences that keep themselves current.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> Segments are how you target the right partners: build an audience from live filters or a hand-picked list, then use it across the product so the right partners get the right experience.
## What it does
A segment is a named group of partners and contacts you can reuse everywhere. You can
build a **dynamic** segment from filters, so membership updates itself as partner data
changes in your CRM, or a **static** segment by hand-picking exactly who belongs. Either
way, the segment becomes a single audience you point other features at.
Segments do more than tag partners. They drive what partners see and receive: which
portal experiences appear, which notifications go out, what permissions apply, and who
gets targeted by courses, content, and campaigns. Because dynamic segments react to live
CRM data, your targeting stays accurate without anyone maintaining lists, which is what
lets you move beyond static tiers toward audiences defined by real behavior and fit.
Segments are also safe to layer. When a partner belongs to several segments, the most
permissive settings win, so each segment a partner earns only ever adds capabilities.
That is what powers progressive unlocking: start everyone restricted, and let the portal
open up as partners qualify for more.
## The problem it solves
Targeting partners usually means maintaining lists that are out of date the moment you
save them:
* **Targeting lists go stale immediately** → Dynamic segments update from live filters, so the audience is always current without manual upkeep.
* **One-size-fits-all messaging misses the mark** → Segments let partner marketing tailor content, courses, and campaigns to the partners they actually fit.
* **Static tiers are too blunt for targeting** → Multi-axis segments group partners by real attributes and behavior, not just a single tier label.
* **Reusing an audience means rebuilding it** → A segment is defined once and reused across portal, notifications, courses, and more.
## From problem to solution
Segments give your program a reusable targeting layer. Partner ops defines an audience
once, as a live filter or a fixed list, and every other feature can target it. Dynamic
segments keep themselves accurate from CRM data, so partner marketing reaches the right
partners with the right experience instead of curating lists by hand.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
define["Define an audience"] --> keep["Live filter or fixed list"]
keep --> target["Every feature targets it"]
```
## Use cases
Build dynamic segments from partner attributes that update as the data changes.
Create a static segment for a specific, fixed group of partners.
Show different experiences and content to different segments.
Tune which updates a segment receives and how they are delivered.
## Impact
* **Low total cost of ownership** - Partner ops defines and reuses segments with no-code, no list maintenance.
* **CRM-native** - Dynamic segments react to live CRM data, so targeting stays accurate automatically.
## Who it's for
Defines the segments the rest of the program targets.
Uses segments to tailor content, courses, and campaigns to the right partners.
## Works with
{/* CONNECTS:START - generated content goes here */}
Gate portal tabs and sections.
Power progressive unlocking.
Control which assets and folders partners see.
Target an announcement at the right partners.
Auto-enroll a segment in a course.
Issue a certificate to a segment.
Show a form only to selected partners.
Restrict products to a segment.
Set goal targets for a segment.
Control who can see a report or dashboard.
Scope a deal coach to a segment.
Target tier benefits and assignments.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.