Measure funnel conversion with explicit eligibility, event order, windows, identity rules, drop-off checks, and segment evidence.
Instructions your experts follow when using this skill.
Use this when the steps form a real ordered path. Do not force unrelated events into a funnel.
For every step record the exact event, eligible population, entity key, required order, conversion window, timezone, deduplication rule, and whether repeat attempts count. State whether the funnel is closed to one starting cohort or open to all events in a period.
Check missing steps, events out of order, duplicate events, client and server disagreement, identity changes, late arrival, version changes, and bot or test traffic rules supplied by the owner. Reconcile starts with an independent source when available.
For each step show entrants, completions, step conversion, overall conversion, drop count, and time to next step. Keep denominators visible. Show both account and user grain only if each has a defined business meaning.
Break down the largest drop by approved segments, then report sample size and whether the segment explains the total change or only has a low rate. A segment with a sharp fall and little volume may not drive the business result.
Link supplied releases, errors, price changes, or channel shifts by time and segment. Label them hypotheses unless a valid test supports cause. Give one instrumentation or product check that could disprove each leading explanation.
Never change the window, order, or exclusion rule after seeing the result without saying so. Do not hide tracking gaps, double count repeat events, or expose individual paths. Do not claim a product change caused conversion to move from a before-and-after comparison alone.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.