Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Framework guide
AARRR Pirate Metrics source-backed Guide
Defines source-backed acquisition, activation, retention, referral, revenue, event definition, cohort, attribution, funnel, experiment, and growth review, evidence handling, and action boundaries.
Read the fileOverview
AARRR Pirate Metrics Overview
source-backed framework bundle for acquisition, activation, retention, referral, revenue, event definition, cohort, attribution, funnel, experiment, and growth review, evidence reconciliation, reviewable.
Read the fileWorkflow
AARRR Pirate Metrics source-backed Triage
1. State the decision and direct answer possible now. 2. Record Verified, Provided, Assumed, and Needs verification separately. 3.
Read the fileTemplate
AARRR Pirate Metrics review brief
Review-ready artifact for acquisition, activation, retention, referral, revenue, event definition, cohort, attribution, funnel, experiment, and growth review.
Read the fileIs this bundle right for your task?
Who it is for
- Growth and product teams, analysts, founders, marketers, experiment owners, and data practitioners defining or reviewing AARRR metrics
When to use it
- A product needs explicit acquisition, activation, retention, referral, and revenue stage definitions tied to its users and business model.
- A funnel or cohort result needs event instrumentation, identity, deduplication, attribution, windows, filters, refunds, and source queries reconciled.
- A growth experiment or campaign needs a baseline, evaluation plan, privacy constraints, uncertainty, and a boundary between association and causal lift.
What you need to provide
- The local AARRR variant, product and user scope, event taxonomy and instrumentation, identity and deduplication rules, acquisition sources and attribution method, activation definition, and cohort retention window.
- Referral and revenue definitions including refunds, filters and exclusions, source queries, baselines, experiment design and results, privacy requirements, owners, decision threshold, and approvals.
Tasks and expected outputs
Questions it helps answer
- Prepare an aarrr pirate metrics review brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- AARRR Pirate Metrics review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Load the AARRR Pirate Metrics bundle and provide the product and user scope, current stage definitions, event taxonomy, instrumentation checks, identity and deduplication rules, attribution method, cohort window, referral and revenue logic, refunds, filters, source queries, baseline, and experiment evidence. Ask the agent to map evidence to each stage and draft a growth review brief without claiming causal impact beyond the design.
Context path: bundles/frameworks/aarrr-pirate-metrics
What the bundle includes
Frameworks
- AARRR Pirate Metrics
- source-evidence matrix
- qualified-review gate
Evaluations
- AARRR Pirate Metrics source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Guessing stage definitions, event accuracy, identity, cohort retention, attribution, referral, revenue, causal growth, or product outcomes; changing tracking or metrics, launching experiments or campaigns, contacting users, exporting personal data, spending budget, or publishing causal claims without approval.
Known limitations
- Use the listed authoritative or identified source surfaces for general AARRR Pirate Metrics guidance; local facts, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for source interpretation and local framework variant, product and user scope, event taxonomy and instrumentation, identity and deduplication, acquisition source and attribution, activation definition, cohort and retention window, referral event, revenue definition and refunds, filters and exclusions, source queries, baselines, experiments, privacy, owner, and approvals.
- Do not infer stage definition, event accuracy, identity, cohort retention, attribution, referral, revenue, causal growth, or product outcome.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that change tracking or metric definitions, launch experiments or campaigns, contact users, collect or export personal data, spend budget, publish metrics, or claim causal growth.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.