Results for “segment”

Automate push notifications, segments, templates, and messaging via OneSignal through Composio's toolkit and Rube MCP.

Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio.

Generate, send, validate, and export AI-powered emails from the terminal; manage contacts, segments, tags, domains, and webhooks with Migma CLI.

Generate a comprehensive product strategy using the 9-section Product Strategy Canvas, covering vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.

Klaviyo marketing operations and analyst expertise. Audit flows, segments, campaigns, deliverability, and revenue attribution. Use when the user asks about Klaviyo marketing strategy, email/SMS automation, customer segmentation, flow optimization, or lifecycle marketing. For API integration, SDK, webhook, or developer questions, see the klaviyo-developer skill.

Google and Meta paid media account structure evaluation. Audits campaign/ad set architecture against conversion volume minimums, budget thresholds, and targeting overlap. Identifies over-segmentation, under-segmentation, budget fragmentation, and structural anti-patterns blocking algorithmic learning. Provides consolidation roadmaps with migration plans. Use when inheriting accounts, quarterly health checks, or before scaling budgets.

根据STP（市场细分、目标市场定位、市场定位）框架撰写结构化学术论文，涵盖引言、概述、细分、定位、挑战和结论等章节，并遵循指定的字数和内容要求。

Research markets with sizing, segmentation, competitor mapping, pricing checks, and demand validation that turn fuzzy ideas into decision-ready evidence. Use when (1) you need TAM, SAM, SOM, whitespace, or category sizing; (2) you must compare competitors, pricing, positioning, or customer segments before acting; (3) the user asks whether a niche, launch, expansion, or go-to-market bet is actually worth pursuing.

Trigger: PostHog event, Segment schema, event properties, user funnel track, track taxonomy. Scope: Product behavioral telemetry, user funnel event models. Boundary: Excludes system performance exceptions.

Design and optimize email sequences, drip campaigns, and automated email flows with complete drafts, metrics plans, and segmentation rules.

Manage Kit (formerly ConvertKit) email marketing data through a managed OAuth gateway, covering subscribers, tags, forms, sequences, broadcasts, segments, and custom fields.

Design products and pricing around validated willingness to pay, using the framework from Ramanujam & Tacke's "Monetizing Innovation" to avoid common monetization failures.

Braze customer engagement platform expertise. Audit campaigns, Canvases, segments, messaging channels, and data architecture. Use when the user asks about Braze, customer engagement, push notifications, in-app messaging, cross-channel orchestration, or lifecycle marketing at scale.

Design a detailed value proposition using a 6-part Jobs-to-be-Done template covering who, why, current situation, solution, improved outcome, and alternatives.

Guide product managers through discovering and articulating product positioning by asking adaptive questions about target customers, unmet needs, product category, benefits, and competitive differentiation.

Configures Salesforce Media Cloud for advertising sales management, covering ad product catalogs, rate cards, audience targeting, revenue recognition, and ad-server integration.

Analyzes multi-step conversion funnels in Adobe Analytics to identify visitor drop-off points, compute step conversion rates, and pinpoint the worst leakage steps.

Analyzes a multi-step conversion funnel in Adobe Customer Journey Analytics to find where users drop off and which steps have the worst leakage.

Synthesize customer research data to define the Ideal Customer Profile (ICP) including demographics, behaviors, Jobs to Be Done, and pain points.

Diagnose which organic growth path to pursue by identifying where the growth constraint lives, using a fast triage based on the McKinsey Growth Pyramid.

Define product positioning by mapping competitive alternatives, unique attributes, and best-fit customers to the right market category using a structured canvas and 5-step process.

Navigate the technology adoption lifecycle to cross from early adopters to mainstream markets using the D-Day strategy, beachhead selection, whole product assembly, and competitive positioning.

Fill the fb.ai CRM with sendable leads — search (0.25/query), import, and enrich (0.075/lead) so emails are unmasked, then build the lists and segments a campaign targets. Unenriched leads are silently dropped by a send, so this skill's real job is getting emails unmasked. Run on demand.

Pick the right business-model canvas (Lean Canvas, Business Model Canvas, or Value Proposition Canvas) for the stage and fill it with specifics — one segment, one primary canvas, top-3 assumptions, no fluff in the moat or channel boxes. Load when the user asks to fill a business model canvas, lean canvas, value proposition canvas, model this business, map the business model, says "fill the BMC", "make a Lean Canvas", "Value Proposition Canvas for this", "model this idea", "what's the business model", "design the business model". Sub-skill of `venture-exploration`. Hard-bans "everyone" segments, generic channels ("SEO/social/content/ads"), and "unfair advantage = AI/data/network effects" with no concrete asset. Does NOT score viability — for that use `idea-evaluation`.

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.

Profiles 5 competitors, identifies white space, and delivers a positioning recommendation — not a feature comparison table. Use this skill — proactively and without waiting to be asked — whenever entering a new market, before defining bets in product strategy, when pricing needs a competitive anchor, or when losing deals to a specific competitor. Also triggers for: "competitive analysis", "competitor research", "who are my competitors", "market landscape", "white space", "differentiation angle", "competitive positioning", "market entry risk", "losing to X", "pricing strategy", "threat assessment", "who owns this segment", "competitive brief", "how do we differentiate", "what are competitors doing". Produces a decision-ready competitive map: 5 competitor profiles, white space analysis, and a Where-to-Win recommendation with explicit areas to ignore.

Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, campaign groups, transactional groups, audience segments, email messages, themes, and components), and workflow inspection. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.