About segmentation
A skill for designing campaign segments based on persona, lifecycle, engagement, and behavior. It provides checks for data integrity and compliance, along with tiering and signal-driven templates for targeting and reporting.
Key features
- 01Lifecycle and engagement grid
- 02Consent, completeness, and recency checks
- 03Priority scoring for high-value segments
- 04Suppression filters for compliance
- 05Launch tiers and signal-driven templates
- 06Shared segment schema guidance
Use cases
- 01Plan persona- or lifecycle-based campaigns
- 02Exclude unsubscribed or legally blocked contacts
- 03Create engagement tiers for experiments and reporting
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ gtmagents/ gtm-agents --skill segmentationAfter installing, type/segmentationin Claude Code to confirm it loaded.
Bundled filesassets/segmentation_matrix.md
Details
From the project READMEAdvanced Segmentation Playbooks
When to Use
- Planning campaigns requiring persona, lifecycle, or behavioral splits.
- Creating suppression logic to protect deliverability and compliance.
- Building engagement tiers for experimentation and reporting.
Framework
- Lifecycle Grid – axis of lifecycle stage vs engagement level.
- Data Integrity – confirm consent, field completeness, and recency.
- Priority Scoring – route high-value segments to premium workflows.
Checklist
- ✅ Primary filter (persona, stage, product usage)
- ✅ Secondary filters (intent, region, business size)
- ✅ Suppress: unsubscribed, bounced, low engagement, legal blocks
- ✅ Personalization fields: {{first_name}}, {{company}}, dynamic modules
Templates
- Segmentation Matrix: See
assets/segmentation_matrix.mdfor tier definitions and logic examples. - Launch Tiering – VIP, Prospects, Dormant with separate cadence and pacing table.
- Signal-Driven – product milestones trigger micro-segments; includes trigger → audience matrix.
- Compliance Safe – CASL/GDPR consent matrix + suppression filters by region.
Tips
- Keep segment definitions in a shared schema doc for consistency.
- Use dashboards to monitor size changes week over week.
- Pair segmentation with A/B testing to validate hypotheses.
Comments
Markdown supported