Skip to content
Platform · Analytics & Asklytics

Ask the question. Get the answer, not the ticket.

Product analytics over behaviour, with delivery reported alongside it, so the two are read together.

Asklytics

Type a question the way you'd ask a colleague and get a live answer with the chart.

The model proposes a plan, the plan is validated, deterministic code compiles and runs it. A bad plan fails loudly. It never returns a plausible wrong number.

Conversations are kept, so a line of enquiry can be resumed and audited.

Over the same dataset

Seven ways to read behaviour with delivery alongside it.

BOARDS

Boards that show who you can actually reach.

Eight kinds of event tile, segment overlap and leaderboards, and channel reachability: not how many people are in a segment, but how many you can contact on each channel. Shared boards are cached and pre-warmed.

FUNNELS

Funnels that don't flatter themselves.

Per-contact, in-order steps inside a window you set. Segment by channel, country or property at the entry step.

METRIC TREE

A live KPI model computed from your events, with a named owner on every node.

It separates what is derived by formula from what merely moves together, and shows the sample size behind every correlation. Open it and every node carries its current value.

DASHBOARDS

Dashboards on day one.

Eight standing views, including delivery performance with campaigns excluded, savings from routing in your own currency, and the fallback paths actually taken.

CONVERSION EVENTS

Opens measure the platform. Conversions measure the decision.

Define which events count and what each is worth. Campaign lift, funnels and journey attribution all measure against it.

SESSION JOURNEYS

See every step, and how long it took.

Sessions are tracked automatically on web and app. Open one and see the entry point, the exit point, and how long the person spent on every step. Thirty seconds on a product page and four minutes on a form is a form with a problem.

SESSION ANALYZER

Write a rule for what did not happen.

Start a journey when a session ends that way. Frequency caps, fail-closed evaluation, one trigger per rule per session. A misconfigured rule sends nothing, not everything.

The pilot

One use case. Six to eight weeks. A number you agreed first.

Book a Demo