「funnel」の検索結果

Audit a landing page or funnel step and produce a prioritised CRO test plan. Use when asked to improve conversion rate, audit a landing/signup/checkout page, reduce funnel drop-off, or plan A/B tests for a page. Produces a CRO plan — a heuristic conversion audit, the diagnosed friction, prioritised test hypotheses (ICE), test designs with sample-size math, and the measurement guardrails.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose Meta Ads campaign performance and account gaps using Meta's actual system mechanics — including customer-journey coverage, Breakdown Effect, Learning Phase, Auction Overlap, Pacing, and Creative Fatigue. Use for performance diagnosis, account audits, full-funnel or TOF/MOF/BOF gap analysis, deciding what to test or create next, and producing novice-friendly recommendations without forcing every campaign or ad into a funnel stage.

日本語の概要は準備中です。原文の説明を表示しています。

Build forest plots (HR, OR, RR, beta-coefficient summaries with CIs) and funnel plots (meta-analysis publication-bias diagnostics) using forestplot, metafor, ggforest, and MendelianRandomization with proper axis-scaling, summary-diamond placement, subgroup nesting, and Egger / trim-and-fill asymmetry tests. Use when summarizing effects across subgroups, trials, or instruments — meta-analysis, Mendelian randomization, subgroup HRs.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

How to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.

日本語の概要は準備中です。原文の説明を表示しています。

Growth marketing covering experimentation, funnel optimization, acquisition channels, retention, and viral growth. Use when designing A/B experiments, optimizing AARRR funnel stages, or prioritizing channels by CAC and LTV.

日本語の概要は準備中です。原文の説明を表示しています。

Product analytics for instrumenting products, defining metrics, and building retention funnels. Use when designing a metric tree, instrumenting a feature, auditing instrumentation, defining a North Star, or building an analytics roadmap.

日本語の概要は準備中です。原文の説明を表示しています。

Find funnel drop-offs from stage numbers you give or connected data, benchmarked, ranked by revenue. "where are we losing people"

日本語の概要は準備中です。原文の説明を表示しています。

Design the optimal funnel from click to conversion. Trigger on "funnel", "conversion path", "booked calls".

日本語の概要は準備中です。原文の説明を表示しています。

Write an email drip sequence for affiliate marketing. Triggers on: "write me an email sequence", "create a drip campaign", "email nurture sequence", "affiliate email funnel", "welcome email series", "email onboarding sequence", "write emails for my list", "set up a drip sequence", "email campaign for [product]", "nurture my subscribers", "email follow-up sequence", "build my email funnel", "write 5 emails promoting [product]", "email automation sequence".

日本語の概要は準備中です。原文の説明を表示しています。

Build multi-sequence email automation flows with branching logic. Triggers on: "build email automation", "create email funnel", "email automation flow", "welcome series with branches", "conditional email sequence", "set up automation", "email workflow builder", "segmented email flow", "advanced email sequence", "nurture funnel", "cart abandonment sequence", "win-back email flow".

日本語の概要は準備中です。原文の説明を表示しています。

Criterios de evaluación para auditorías de funnel NGX, incluyendo checklist visual, UX, copy y conversión

日本語の概要は準備中です。原文の説明を表示しています。

When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing marketing, messaging, offers, funnels, or content strategy. Triggers on "audit my marketing", "review my landing page", "improve my funnel", "content strategy review", "messaging review", "offer feedback", "marketing checkup", "why isn't my marketing working", "audit my brand". Works at any budget or company size.

日本語の概要は準備中です。原文の説明を表示しています。

Build forest plots (HR, OR, RR, beta-coefficient summaries with CIs) and funnel plots (meta-analysis publication-bias diagnostics) using forestplot, metafor, ggforest, and MendelianRandomization with proper axis-scaling, summary-diamond placement, subgroup nesting, and Egger / trim-and-fill asymmetry tests. Use when summarizing effects across subgroups, trials, or instruments — meta-analysis, Mendelian randomization, subgroup HRs.

日本語の概要は準備中です。原文の説明を表示しています。

The practice of collecting, analyzing, and acting on data to drive product decisions. Great analytics isn't about dashboards—it's about insights that lead to action. Every metric should answer a question that changes behavior. This skill covers event tracking, metrics design, dashboards, user behavior analysis, and data-driven decision making. The best analytics teams measure what matters, not what's easy to measure. Use when "analytics, metrics, tracking, dashboard, funnel, cohort, retention, events, KPI, measure, data, insights, conversion, engagement, analytics, metrics, data, dashboards, tracking, funnels, cohorts, KPIs, insights" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Conversion Rate Optimization auditing for landing pages, signup flows, checkout funnels, forms, and CTAs. Identifies friction points, runs heuristic evaluations, produces prioritized recommendations using ICE/PIE frameworks. Use when the user asks about conversion optimization, funnel analysis, landing page audits, form optimization, CTA testing, or checkout improvement.

日本語の概要は準備中です。原文の説明を表示しています。

🇺🇸 Hardware + SaaS GTM Playbook — End-to-end go-to-market for consumer hardware products with software subscription models. Covers crowdfunding engineering (Kickstarter/Indiegogo/Makuake), KOL matrix for physical products, hardware PMF validation metrics, device-as-funnel subscription design, localization entry timing, and community flywheel mechanics. Built from verified Plaud, Insta360, and DJI case data. 🇨🇳 硬件+软件订阅 GTM 实操手册 — 面向消费硬件产品的完整出海及增长打法。覆盖众筹超额工程（KS/IGG/Makuake）、硬件 KOL 矩阵策略、硬件 PMF 验证、设备即漏斗订阅设计、本地化进入时机判断、社区飞轮构建。基于 Plaud/Insta360/大疆真实案例数据撰写。 🇯🇵 ハードウェア＋SaaS GTMプレイブック — クラウドファンディング（Kickstarter/IGG/Makuake）を起点とした消費者向けハードウェア製品のGTM戦略。KOLマトリクス、PMF検証、デバイスをファネルとするサブスクリプション設計、ローカライゼーション進入タイミング、コミュニティフライホイールまで網羅。Plaud・Insta360・DJIの実例データに基づく。 🇰🇷 하드웨어+SaaS GTM 플레이북 — 크라우드펀딩(Kickstarter/IGG/Makuake) 기반 소비자 하드웨어 제품의 엔드투엔드 GTM 전략. KOL 매트릭스, PMF 검증, 디바이스-as-퍼널 구독 설계, 현지화 진입 타이밍, 커뮤니티 플라이휠 포함. Plaud·Insta360·DJI 실제 사례 데이터 기반. Triggers: "hardware GTM" | "crowdfunding strategy" | "hardware+SaaS" | "Kickstarter launch" | "hardware KOL" | "hardware PMF" | "device subscription" | "hardware product launch" | "consumer hardware growth" | "Makuake" | "众筹策略" | "硬件出海" | "硬件+订阅" | "硬件GTM" | "KS众筹" | "硬件PMF" | "设备订阅" | "硬件冷启动" | "ハードウェアGTM" | "クラファン" | "하드웨어 GTM" | "크라우드펀딩"

Product analyst — metrics architecture, funnel analysis, A/B test design, retention, and growth measurement. Use when asked to "design an A/B test", "analyze the funnel", "define a north star metric", or "measure retention".

日本語の概要は準備中です。原文の説明を表示しています。

Conversion rate optimization audit — analyze a landing page, signup flow, or checkout funnel using the 5-layer CRO stack (technical performance, traffic quality, offer/pricing, design/layout, copy/messaging). Produces prioritized fix list with expected impact. Use when "CRO audit", "conversion audit", "why isn't this converting", "improve conversion rate", "landing page not converting", "optimize funnel", "signup flow audit", or any request to diagnose and fix conversion problems.

日本語の概要は準備中です。原文の説明を表示しています。

Implement the 5-stage Funnel workflow (Notes → Leads → Primitives → Findings → Reports) for structured bug bounty hunting. Based on Critical Thinking Bug Bounty Podcast Episode 166.

日本語の概要は準備中です。原文の説明を表示しています。

Marketing analytics and data-driven optimization for B2B SaaS campaigns. Use this skill when analyzing marketing performance, optimizing conversion rates, running A/B tests, conducting customer research, creating marketing dashboards, building attribution models, analyzing funnel metrics, or storytelling with data. Also triggers on: marketing ops, performance analytics, CRO, A/B testing, data storytelling, customer insights, tracking plan, event taxonomy, UTM taxonomy, GA4 audit, consent mode, instrumentation contract, sample size calculation, minimum detectable effect, test duration, not enough traffic to A/B test, statistical significance, Bayesian vs frequentist, sample ratio mismatch, experiment feasibility, martech stack, marketing tech stack audit, tool consolidation, build vs buy, vendor evaluation, shadow IT tools, ESP/CRM/platform migration, switching cost, cutover plan, suppression list migration, data portability, customer interviews, survey design, sampling frame, non-response bias, how many people should I interview, thematic saturation, voice of customer, jobs-to-be-done, buyer persona research, is this finding real, data enrichment, which enrichment provider should we buy, waterfall enrichment, contact data quality, match rate, our list data is bad, email verification, catch-all domain, accept-all, bounce rate from bad data, B2B data decay, how often should we re-verify contacts, ZoomInfo vs Apollo vs Clearbit evaluation, cost per usable record, where did this list come from, GDPR Article 14 notice, purchased list compliance, suppression screening, TAM list building, demand planning, marketing plan, how many leads do we need, what pipeline target should marketing carry, funnel model, top-down vs bottom-up plan, plan of record, annual marketing planning, quarterly planning, pipeline coverage we have to create, sales cycle lag, our leads cannot close this quarter, carry-in pipeline, scenario planning, conservative moderate aggressive forecast, stretch target, reforecast, re-forecast triggers, assumption register, capacity ceiling, addressable audience ceiling, marginal cost per lead, blended CPL is wrong, we missed plan and nobody knows why, AI policy for the marketing team, AI governance, AI acceptable use policy, which AI tools are we allowed to use, can I paste customer data into ChatGPT, shadow AI, AI use register, human review of AI output, when can we stop reviewing every AI draft, can the agent send on its own, the AI made a mistake now what, pull back AI autonomy, AI evals, our AI vendor changed the model, AI output went out wrong, prompt injection, can our AI read prospect replies safely, lethal trifecta, the AI leaked internal notes, turn off auto-generated ad assets, auto-applied recommendations, AI literacy training, EU AI Act Article 4, duplicate records in the CRM, dedupe before import, which value wins in a merge, CRM cleanup.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when designing lead nurture journeys in MCAE (Account Engagement / Pardot) Engagement Studio — mapping content to funnel stages (Awareness, Consideration, Decision), behavioral trigger rules, branching program paths, and MQL handoff criteria to Sales. NOT for building a journey in Marketing Cloud Journey Builder — use admin/journey-builder-administration. NOT for the scoring and grading model behind MQL — use admin/mcae-lead-scoring-and-grading.

日本語の概要は準備中です。原文の説明を表示しています。

Author and own one flow's design document (the FLOW.md objective flow) at .unikit/gamedesign/flows/FLOW-<slug>.md — the dynamics layer of the GDD (what the player does over time). Create the skeleton and walk the collaborative section-cycle to write its objectives, pacing, dependencies, and funnel events ("design the first-session flow", "map the onboarding sequence", "write the FLOW for the boss encounter"), AND revise it after approval under the delta discipline ("retune the pacing", "add a branch", "change a GOAL", "rework the onboarding") — a cue/number change is Tuning, a small step change a Tweak, restructuring a Rework; each bumps the version and logs the delta. Selects the wiring mode (linear | conditional | emergent) and re-renders the ## Flow Map [gen] / ## Funnel [gen] blocks in GAME.md. To add or detail a system use /unikit-gd-system; to edit GAME.md content use /unikit-gd-spec; to apply a multi-zone edit use /unikit-gd-apply; for a new game concept use /unikit-gd-brainstorm.

日本語の概要は準備中です。原文の説明を表示しています。