Measure funnel conversion with explicit eligibility, event order, windows, identity rules, drop-off checks, and segment evidence.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.