/segment-audience

name: segment-audience
description: "Build or update audience segments in the brand's CRM, email, or ad platform (Salesforce, HubSpot, Mailchimp, Meta Custom Audiences, Google Customer Match, and more) via connected MCPs — with size estimation, overlap analysis, exclusion impact, ad-consent compliance checks, RFM modeling, and cross-platform sync with match-rate verification. Creation halts at a mandatory approval gate showing criteria, estimated members, and sample profiles before anything is pushed live. Triggers on \"/digital-marketing-pro:segment-audience\", \"create a segment of lapsed customers\", \"build a lookalike seed audience\", \"who should we target for the win-back campaign\", \"sync this list to Meta\". Reads the brand profile; pairs with /digital-marketing-pro:lead-import (get contacts in first) and /digital-marketing-pro:data-export (send segment data out)."
disable-model-invocation: false
argument-hint: "[segment-name or criteria]"

/digital-marketing-pro:segment-audience

Purpose

Create or update audience segments in the brand's CRM or email platform based on behavioral, demographic, or engagement criteria. Segments can be used for ad targeting, email campaigns, retargeting, or personalization. Ensures segments are well-defined, properly sized, actionable across platforms, and documented with clear criteria for reproducibility — so the team can understand exactly who is in a segment and why. Supports RFM (recency, frequency, monetary) modeling, lifecycle-based segmentation, and predictive scoring criteria for advanced audience strategies.

Use this command to build targeting audiences before campaign launches. For importing new contacts into the CRM first, use `/digital-marketing-pro:lead-import`. For exporting segment member data to external tools, use `/digital-marketing-pro:data-export` after segment creation.

Execution gate (MANDATORY — cannot be skipped)

1. Present the full preview — recipients / spend / changes / compliance — as an **Execution Summary** before touching any live system. 2. The user must type `yes` (or an equivalent explicit approval). ANY other input — ambiguous, implied, partial, or absent approval — cancels the run. 3. Never proceed on ambiguous input. Never auto-retry a failed execution; a failure needs human review before any re-run. 4. Record the approval with `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action create-approval --data '{"risk_level":"<tier>","summary":"..."}'` **before** executing, then `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action mark-executed --id {approval_id}` after the platform confirms success.

Input Required

The user must provide (or will be prompted for):

• **Segment criteria**: The rules that define segment membership — demographics (age, location, job title, company size, industry), behaviors (pages visited, emails opened, links clicked, purchases made, events attended), engagement levels (active last 30/60/90 days, lapsed, at-risk, churned), purchase history (recency, frequency, monetary value, product category), lifecycle stage (subscriber, lead, MQL, customer), or custom field filters
• **Target platform**: Where the segment will be created — CRM (Salesforce, HubSpot, Zoho, Pipedrive), email platform (ActiveCampaign, Mailchimp), or ad platform (Meta Custom Audiences, Google Ads Customer Match, LinkedIn Matched Audiences, TikTok Custom Audiences)
• **Segment name**: A descriptive, standardized name following the brand's naming conventions — e.g., "High-Value-Customers-Last-90d" or "MQL-SaaS-Enterprise-US"
• **Segment purpose**: How this segment will be used — email campaign targeting, paid ad audience, retargeting pool, personalization cohort, suppression/exclusion list, lookalike seed audience, or cross-sell/upsell targeting
• **Dynamic vs. static**: Whether the segment should auto-update as contacts meet or leave criteria (dynamic/smart list) or remain fixed at time of creation (static/snapshot) — dynamic for ongoing campaigns, static for one-time sends or point-in-time analysis
• **Refresh frequency (if dynamic)**: How often the segment membership should be recalculated — real-time (event-triggered), daily, weekly, or on-demand before each campaign send
• **Exclusion criteria (optional)**: Contacts to explicitly exclude — unsubscribed, hard bounced, competitors, internal team members, existing customers (for acquisition campaigns), contacts in another active campaign (frequency capping), or suppression lists from partners
• **Minimum segment size (optional)**: The smallest acceptable segment size for the intended use case — ad platforms typically require 1,000+ for effective delivery, lookalike seeds perform best at 1,000-10,000, and email segments should be large enough for statistical significance in A/B testing
• **Cross-platform sync (optional)**: Whether this segment should be automatically synced to additional platforms — e.g., create in CRM and push to Meta Custom Audiences and Google Ads simultaneously
• **Segment description**: A human-readable explanation of the segment's purpose and criteria for team documentation — stored alongside the segment for future reference and knowledge transfer
• **RFM parameters (optional)**: If using recency-frequency-monetary segmentation — define the scoring thresholds for each dimension, the lookback window for transaction history, and the number of segments to create (e.g., Champions, Loyal, At Risk, Lost)
• **Lookalike expansion (optional)**: If this segment will seed a lookalike audience — specify the expansion percentage (1-10%) and target platform, so the segment can be optimized for seed quality rather than just size

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/comp