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/cross-tool-data-flow-patterns.md
View on GitHub# Cross-tool data flow patterns
Identity threading, context capture, segment tagging, sequence-tool integration.
When the audience moves from one tool to another in the funnel, the audience signal travels with them. Done well, cross-tool data flow makes the audience experience continuous and lets the brand match content to the audience's specific journey. Done poorly, every tool starts from scratch and the audience signal is lost.
---
## The continuity principle
The audience experience should feel continuous across tools. Their interactions in one tool inform their experience in the next.
**The win.** A visitor takes a quiz; the quiz tags them as "mid-market mid-funnel." When they later open the calculator, the defaults reflect mid-market context. When they download a lead magnet, the sequence delivered matches the segment. The visitor experiences a coordinated brand journey.
**The fail.** The same visitor takes the quiz; the calculator does not know they took it; the lead magnet sequence is generic. Each tool is an island. The audience signal captured in one tool is wasted in the next.
The discipline. Data flows. Each tool's interactions inform subsequent interactions.
---
## Pattern A: Identity threading
When the audience is identified, their identity carries forward across tools.
**How it works.**
- The audience opts in (email submission, account creation, login).
- Subsequent interactions are associated with that identity.
- Tools across the funnel access the identity record to personalize.
**Strengths.**
- Most powerful continuity mechanism.
- Lets all tools share context for the same person.
**Weaknesses.**
- Requires identity infrastructure (CRM, data warehouse, customer data platform).
- Privacy considerations (handling identity data carefully).
**When to use.** When the program has identity infrastructure and the audience is willing to be identified (typically post lead-magnet download or account creation).
---
## Pattern B: Context capture
Inputs from one tool feed into the next interaction.
**How it works.**
- Tool A captures specific inputs (calculator values, quiz answers, form responses).
- Those inputs are stored with the identity (or with an anonymous session token).
- Tool B reads the inputs; uses them as defaults or context.
**Example.**
- Quiz captures "team size: 75."
- Calculator's defaults reflect team size 75.
- Lead magnet's recommended resource matches team size 75.
**Strengths.**
- Concrete continuity; the audience sees their inputs reflected.
- Reduces re-entry friction.
**Weaknesses.**
- Requires structured data capture (not just behavioral signals).
- Inputs from different tools must align (no conflict if quiz and calculator both capture team size).
**When to use.** When tools capture overlapping or related context that benefits from shared use.
---
## Pattern C: Segment tagging
Each interaction tags the audience with segment information that informs future routing.
**How it works.**
- Tool A determines the audience's segment based on inputs (the quiz result; the calculator's input pattern).
- The segment tag attaches to the audience record.
- Subsequent tools and sequences route based on the tag.
**Example.**
- Quiz result: "Mid-market operator."
- Tag: segment = mid-market.
- Subsequent: lead magnet sequence is the mid-market sequence; calculator defaults are mid-market; chatbot routing is mid-market-aware.
**Strengths.**
- Lightweight. The tag is small; the routing logic uses it.
- Compatible with most marketing automation.
**Weaknesses.**
- Tag accuracy depends on the source tool's accuracy.
- Tags can conflict (different tools assign different segments).
- Tag staleness (the audience's segment may change over time).
**When to use.** Default pattern for cross-tool routing.
---
## Pattern D: Sequence-tool integration
Email sequences include links to specific tools matched to the audience's segment.
**How it works.**
- Sequence email includes a CTA: "based on your situation, this calculator can help you compare."
- The CTA link includes parameters that pre-fill the calculator with the audience's known context.
- Audience clicks; calculator opens with their context already populated.
**Strengths.**
- Explicit cross-tool connection; the audience sees the journey.
- Reduces friction at the calculator (audience does not re-enter known information).
**Weaknesses.**
- Requires tooling for parameterized links and pre-fill.
- The pre-fill must respect what the audience consented to share.
**When to use.** When the sequence is steering the audience toward specific tools and pre-fill would meaningfully reduce friction.
---
## Conflict and source-of-truth
When different tools capture different values for the same attribute.
**The pattern.** The quiz says team size 75; the multi-step form says team size 60. Which is correct?
**Approaches.**
- **Latest wins.** The most recent capture overrides earlier captures.
- **Source authority.** Specific tools are designated as authoritative for specific attributes (form > quiz for verified data).
- **User confirmation.** Conflict surfaces a confirmation prompt: "We have you down as 75; is that still correct?"
**The discipline.** Define source-of-truth for important attributes. Latest-wins is simple but can lose data; source authority is more disciplined but requires explicit definition.
---
## Privacy and consent
Cross-tool data flow involves handling user data. Consent matters.
**The principle.** The audience should know what data flows where. Pre-filling a calculator with previously captured information is fine if the audience expects it; surprising them with knowledge they did not consent to share breaks trust.
**Consent patterns.**
- Explicit opt-in to identity tracking ("save my progress").
- Disclosure of data flow ("we use your quiz answers to personalize subsequent recommendations").
- Easy data deletion or account closure.
**Privacy regulations.** GDPR, CCPA, and other regulations affect what data can flow and how. Compliance is essential; the architecture must respect the regulations applicable to the audience.
---
## Anonymous-session continuity
When the audience is not yet identified.
**The pattern.** Browser-based continuity (cookies, local storage) lets tools share context within the same session even before identity capture.
**Strengths.**
- Continuity without requiring early opt-in.
- Smooth experience across same-session tool interactions.
**Weaknesses.**
- Lost when the audience switches devices or clears cookies.
- Limited persistence (typically days, not weeks).
- Privacy considerations (cookies-based tracking has its own complications).
**When to use.** As a supplement to identity-based continuity; for early-funnel interactions before opt-in.
---
## Cross-tool data flow architecture
How to design the data flow at the architecture level.
**The data layer.** A single data layer (CRM, customer data platform, data warehouse) holds the audience records. All tools read from and write to this layer.
**The integration layer.** Tools integrate with the data layer either directly (API) or through a middleware (Zapier, Segment).
**The privacy layer.** Consent and data-control mechanics live across the architecture; the data layer respects them.
**Architecture-level discipline.** Cross-tool data flow is infrastructure work, not just tool work. Building the infrastructure is part of the funnel architecture investment.
---
## Cross-tool measurement
Track how data flows across tools.
**Metrics.**
- **Cross-tool engagement.** What percentage of subscribers who engaged with tool A also engaged with tool B?
- **Identity capture rate.** What percentage of visitors who interact with tools become identified?
- **Pre-fill usage.** When pre-fill is offered, what percentage of users engage with the pre-filled tool?
- **Segment tag accuracy.** Sample-based audit of whether segment tags match actual audience profiles.
Diagnostic uses. Low cross-tool engagement signals tools are not connecting in the audience's journey; low pre-fill usage signals the pre-fill is not visible or not valued.
---
## Cross-tool data flow audit
Periodically audit the data flow.
**The audit.**
- Walk through critical journeys end-to-end. Does data actually flow?
- Verify identity threading works (logged-in user is recognized across tools).
- Verify context capture works (inputs in tool A appear in tool B as expected).
- Verify segment tagging works (quiz result tag triggers correct downstream sequences).
- Verify sequence-tool integration works (sequence links pre-fill correctly).
**The drift.** Integrations break silently. Tool updates change data formats. Audit catches the drift.
---
## Common data flow failures
**No data flow.** Each tool isolated; identity and context lost between tools.
**Identity threading broken.** Logged-in user not recognized across tools; same person treated as new visitor multiple times.
**Context capture incomplete.** Tool A captures inputs but tool B does not access them.
**Segment tag conflicts.** Different tools tag the same person differently; downstream routing inconsistent.
**Pre-fill broken.** Sequence link includes parameters but the tool does not honor them; audience re-enters known information.
**Privacy violations.** Cross-tool data flow happens without consent; audience surprised; trust damaged.
**Stale data.** Audience's situation has changed but tools still use old captured data.
---
## Methodology-level choices that stay in the public skill
The continuity principle. Patterns A through D (identity, context, segment, sequence-tool integration). Conflict and source-of-truth. Privacy and consent. Anonymous-session continuity. Cross-tool data flow architecture. Cross-tool measurement. Audit cadence. Common failures.
## Implementation choices that stay internal
Specific data layer choices for the team's stack. Specific integration tooling. Specific consent flows and privacy disclosures. The team's audit calendars. 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 |