UAE · ENBook a demo
IT CompanyProductInvestigator

Product Analytics Agent

Tracks usage funnels and retention.

Product Analytics AgentStrategy and Roadmap
Industry
IT Company
Department
Product
Team
Strategy and Roadmap
Kind
Investigator
Approver
Head of Product
Code
PRD-06

It tracks the SaaS products' usage funnels (sign-up, activation, team invites, integration set-up, retention) and explains any drop. It weighs the competing causes, from a release or an outage to a change in the traffic mix, and records the finding for the product team. **The problem it solves:** Why a funnel step or retention metric dropped: which step, by how much and since when, which segments, and whether a release, outage, experiment, traffic mix, pricing or tracking explains it.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the cloud monitoring and observability stack: product event counts by funnel step and cohort, with incidents and deploys over the same period..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Weighs competing explanations against the evidence and shows which one holds up.

  5. 05Asks a person

    Hands the work to Head of Product with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the project management tool: it logs the finding on the product's analytics board and opens follow-up tasks. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The product analytics standard: event definitions, funnel and cohort definitions, activation milestones by product, targets and the release calendar.

Reads from

the cloud monitoring and observability stack: product event counts by funnel step and cohort, with incidents and deploys over the same period.

Acts in

the project management tool: it logs the finding on the product's analytics board and opens follow-up tasks.

Hands back

An object with metric, change (from, to and percent), causes (a ranked list with cause, evidence, confidence and how_to_confirm), segments_hit (a list) and next_steps (a list).

Asks a person when

The cause points to a release defect or a data-tracking fault, or a drop affects enterprise accounts' retention.

ApproverHead of Product

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Drop that needs explaining (%)10A step falling this much against its trailing four weeks is explained.
Smallest cohort to judge200Smaller cohorts are noted but not called a trend.
Days to activate14A new account is activated when it hits the activation milestone within this window.
Leave out internal and test accountsOnWhen on, staff and test tenants are excluded.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Explain any step that dropped 10 percent or more, in cohorts of at least 200.
  • Weigh the competing causes: a release or bug, an outage, an experiment, a change in traffic source or segment mix, a pricing change or a tracking fault; say what would confirm each.
  • Measure activation within 14 days of sign-up.
  • When on is true, exclude internal and test accounts.
  • A change just before the first sign of the drop outranks other causes.

See the Product Analytics Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Product Analytics Agent · IT Company | Basinwright Industries