opensite-ai/opensite-skills / funnel-flow-architecture
funnel-flow-architecture
VerifiedArchitecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. Honest about silo-funnels (every tool standalone), kitchen-sink-funnels (every audience squeezed through one path), and matched-funnels (architecture matched to audience-and-stage) patterns. Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration. Also triggers when the team's growth tools are working individually but not together, when audience segments share one nurture path, or when a funnel is being architected from scratch.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.8 KB |
| references/architecture-anti-patterns.md | markdown | 8.7 KB |
| references/audience-and-stage-segmentation.md | markdown | 9.2 KB |
| references/common-funnel-architecture-failures.md | markdown | 7.9 KB |
| references/cross-tool-data-flow-patterns.md | markdown | 9.9 KB |
| references/entry-point-architecture-patterns.md | markdown | 8.7 KB |
| references/funnel-iteration-discipline.md | markdown | 8.3 KB |
| references/funnel-measurement-patterns.md | markdown | 9.3 KB |
| references/nurture-sequence-architecture.md | markdown | 10.7 KB |
| references/tool-to-funnel-mapping.md | markdown | 9.7 KB |
references/funnel-measurement-patterns.md
View on GitHub# Funnel measurement patterns
Architecture-level vs tool-level metrics. What to measure, what is noise.
Funnel measurement should reveal architecture quality, not just tool quality. Tool-level metrics tell you whether each tool is working; architecture-level metrics tell you whether the tools work together.
---
## The architecture-vs-tool measurement distinction
Two layers of measurement.
**Tool-level metrics.** Each tool's individual performance (calculator conversion, quiz completion, lead-magnet downloads). Detail in each tool's skill.
**Architecture-level metrics.** How the tools and sequences compose. Cross-tool conversion, sequence-to-tool conversion, segment-level downstream conversion, funnel-stage progression.
**The discipline.** Measure both layers. Architecture-level metrics are often the missing measurement.
---
## Architecture-level metric: Cross-tool conversion
What percentage of audience that hits tool A then engages with tool B.
**The metric.** Count the visitors who interact with tool A (calculator, quiz, lead magnet, etc.). Of those, how many subsequently interact with tool B?
**Why it matters.** Cross-tool engagement signals whether the funnel is composing. High cross-tool conversion means the architecture is working; low cross-tool conversion means tools are silos.
**Measurement methods.**
- Identity-based tracking (same identified user across tools).
- Session-based tracking (same session sees multiple tools).
- Cohort analysis (cohorts entering through tool A and their downstream tool engagement).
**Diagnostic uses.**
- Low cross-tool conversion: tools may not be promoted to each other's audiences; transitions may be broken.
- Specific tool pairs underperforming: those transitions need design attention.
---
## Architecture-level metric: Sequence-to-tool conversion
What percentage of nurture sequence subscribers engage with downstream tools.
**The metric.** Count subscribers in a sequence. Of those, how many click through to a tool the sequence promoted?
**Why it matters.** Sequences should drive subscribers toward tools matched to their segment-and-stage. Low sequence-to-tool conversion signals that the sequences are not effectively bridging to tools.
**Diagnostic uses.**
- Specific sequence emails with low click-through: the email's tool promotion may not match the audience.
- Specific tools with low sequence-driven traffic: the sequences may not be promoting those tools enough.
---
## Architecture-level metric: Segment-level downstream conversion
Per-segment conversion to the program's main goal.
**The metric.** For each segment in the matrix: what percentage convert to the main goal (trial, demo, purchase) within a defined timeframe?
**Why it matters.** Different segments will convert at different rates; segments significantly underperforming relative to peers signal architecture issues.
**Diagnostic uses.**
- Segments with low downstream conversion: the funnel architecture for that segment may be broken or under-developed.
- Segments with high downstream conversion: investigate what is working; replicate to other segments.
---
## Architecture-level metric: Funnel-stage progression
What percentage of audience moves from awareness to consideration to decision over time.
**The metric.** Track audience as they progress through stages. Awareness audience this month; what percentage are in consideration next month; what percentage in decision the following.
**Why it matters.** The funnel's job is to progress audience through stages. Low progression signals the nurture sequences and tools are not advancing the relationship.
**Diagnostic uses.**
- Slow progression: sequences may be too educational without enough advancement; or the audience may be getting stuck.
- Fast progression but low conversion: progression without quality.
---
## Tool-level metrics
Each tool has its own metrics. Detail in each tool's skill.
**Calculator.** Conversion rate per visitor; tier-2 (email gate) conversion; downstream conversion of calculator-sourced leads.
**Quiz.** Completion rate; per-segment downstream conversion; recommendation click-through.
**Lead magnet.** Download rate; sequence engagement; downstream conversion of magnet-sourced subscribers.
**Multi-step form.** Completion rate; per-step drop-off; lead quality.
**Chatbot.** Resolution rate per intent; escalation rate; downstream conversion.
The tool-level metrics tell you whether each tool is doing its job. The architecture-level metrics tell you whether the tools are doing the funnel's job.
---
## What is noise
Metrics that look important but are not.
**Total tool engagements.** Volume without context. A tool with 10000 engagements per month tells you nothing without conversion context.
**Email open rate alone.** Open rate is a leading indicator at best; sequence-to-conversion is the metric that matters.
**Time on page or session length.** Often correlates with confusion as much as engagement.
**Bounce rate alone.** High bounce rate on awareness content may be normal; on decision content may signal a problem; aggregate bounce rate is noise.
The discipline. Measure outcomes, not activity. Activity metrics are noise unless connected to outcome metrics.
---
## Measurement granularity
How granular to measure.
**Per-tool measurement.** Standard. Each tool tracked.
**Per-segment-per-tool measurement.** Measure each tool's performance per segment. Surfaces segment-specific tool issues.
**Per-segment-per-stage measurement.** Measure progression and conversion per cell in the matrix.
**Per-cohort measurement.** Track cohorts (groups arriving in the same period) over time. Surfaces evolution and decay.
**The discipline.** Granularity matters when it informs decisions. Per-segment-per-stage is often where the diagnostic value lives; per-cohort surfaces decay.
---
## Attribution
Connecting outcomes to specific tools and sequences.
**The challenge.** Audiences interact with multiple tools and sequences. Which one drove the conversion?
**Approaches.**
- **First-touch attribution.** Credit goes to the first interaction.
- **Last-touch attribution.** Credit goes to the most recent interaction.
- **Multi-touch attribution.** Credit distributed across interactions.
- **Position-based attribution.** Credit weighted by position (often U-shaped or W-shaped).
**The honest framing.** Attribution is a model. No model is perfectly accurate. Choose a model deliberately; understand its biases; report consistently.
---
## Measurement and architecture decisions
How metrics inform architecture changes.
**The pattern.** Metrics surface gaps; architecture decisions address them; subsequent metrics validate.
**Examples.**
- Cross-tool conversion low: redesign transitions; promote tool B in tool A's exit; measure improvement.
- Specific segment underperforming: review segment's funnel path; adjust tools or sequences; measure.
- Funnel-stage progression slow: review sequence design; add or refine; measure.
**The discipline.** Metrics inform decisions; decisions are tested; results validated. Without measurement, architecture changes are guesswork.
---
## Measurement instrumentation
What needs to be in place.
**Identity tracking.** Identified users tracked across tools.
**Event tracking.** Each tool interaction logged with event data.
**Funnel definition.** The funnel stages and segments defined in the analytics tool.
**Cohort capability.** Ability to define and track cohorts.
**Reporting.** Dashboards or reports that surface architecture-level metrics.
**The discipline.** Instrumentation should be in place before launch, not added later. Retrofitting measurement is harder than building it in.
---
## Measurement cadence
How often to look at architecture-level metrics.
**Weekly review.** For high-velocity programs or recently launched architectures. Catches regressions and informs rapid iteration.
**Monthly review.** For stable programs. Tracks trends and surfaces gradual decay.
**Quarterly review.** Comprehensive architecture audit. Per-cell analysis; segment-level deep dive; funnel-stage progression.
**Triggered review.** When tools change, when segments shift, when external factors (market, competition) change.
---
## Common measurement failures
**Tool-level only.** Architecture-level metrics not tracked; cannot diagnose composition issues.
**Vanity metrics.** Volume metrics without conversion context.
**No segment-level granularity.** Aggregate metrics hide segment-specific issues.
**Attribution model not chosen.** Reports inconsistent because attribution is ad-hoc.
**No cohort tracking.** Cannot see decay or evolution.
**Metrics without action.** Metrics reviewed but no decisions follow.
**Confounded data.** Multiple changes deployed without isolation; cannot attribute outcomes to changes.
---
## Methodology-level choices that stay in the public skill
The architecture-vs-tool measurement distinction. Architecture-level metrics (cross-tool, sequence-to-tool, segment-level, funnel-stage). Tool-level metrics (cross-reference). What is noise. Measurement granularity. Attribution approaches. Measurement and architecture decisions. Instrumentation requirements. Measurement cadence. Common failures.
## Implementation choices that stay internal
Specific dashboards for specific programs. Specific tooling for measurement. Specific attribution models. The team's reporting conventions. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |