Onfrey Products — Website Intelligence
Most teams don’t have a data problem — they have a dashboard problem. Four different reports, three different definitions of “conversion,” and a metric that clearly moved without anyone able to say why, or what to do next. PathFlight is Onfrey’s answer to that gap: a platform that turns consented website activity into verified answers your team can reuse, monitor, investigate, and test — so the next move is backed by evidence, not a guess dressed up as a chart.
Ask PathFlight a plain-language question about your website, and it doesn’t just hand you a number — it shows you what changed, connects that change to something your team can actually act on, and tracks whether the fix worked. Instead of stitching together analytics tools, spreadsheets, and tribal knowledge every time leadership asks “why did conversion drop,” you get one verified answer, with visible limits and an approved next move attached to it.
That’s the shift PathFlight is built around: from reporting to responsible action. See what changed, understand why it matters, and know what happens next — all from one installation, one shared source of truth, and one decision path that stays intact from signal to outcome.
What PathFlight Does
PathFlight is built around a simple three-step loop — capture, identify, explain, act — that turns raw website behavior into decisions your team can stand behind:
📈 Movement
Find the change that deserves attention across the user journey, and see exactly who was affected — not just that a number moved.
🔗 Lever
Connect that movement to the page, campaign, release, or experience your team has the power to change — the “why,” not just the “what.”
🎯 Outcome
Track the metric and guardrails that show whether the next move actually delivered, instead of assuming a fix worked and moving on.
🛠️ One Installation, Many Outputs
A single verified answer can become a dashboard, an alert, an experiment, or an investigation — no separate tools bolted on for each need.
Movement: Know What Changed, Not Just That Something Did
Every team has watched a number move on a dashboard with no clear explanation — mobile checkout completion fell 11.2%, and nobody can say why. PathFlight is built to surface that kind of movement across the full user journey, from product to cart to address to payment to completion, so the team can see exactly where in the funnel the drop happened and which segment of users was affected.
This isn’t a generic anomaly alert buried in a report nobody opens. PathFlight surfaces the movement that deserves attention, in plain language, tied to the specific step of the journey where it occurred — so the first five minutes of investigating a problem aren’t spent hunting across four different dashboards with three different definitions of the same metric.
This is the same underlying discipline Onfrey applies at the Discover stage of a client’s growth journey — audience and behavioral data that isn’t just collected, but actively used to decide what happens next.
Lever: Ask in Plain Language, Get a Verified Reason
Once PathFlight has identified a movement worth investigating, it doesn’t stop at the symptom. Ask a plain-language question — “what changed for returning customers?” — and PathFlight connects the movement to a lever your team can actually pull: a specific page, campaign, release, or experience change, backed by evidence and a visible source.
In the checkout example, that might mean tracing the drop to address field errors that increased right after a release — evidence complete, source available, no guesswork required. That’s the difference between “the number moved” and “here’s what changed and what to do next,” which is the entire premise PathFlight is built on.
Because every answer is tied to a stable, versioned definition of the underlying event, teams stop arguing about whose dashboard is right and start acting on a single shared source of truth.
Outcome: Test the Fix, Don’t Just Assume It Worked
Identifying the cause of a problem is only half the job — the other half is proving the fix actually worked. PathFlight closes that loop by turning a verified answer directly into an experiment, with guardrails attached, so a change like “test address autocomplete on mobile” gets measured against the metric it was meant to improve, not just shipped and forgotten.
Experiments in PathFlight are honest about uncertainty. If a test shows a promising lift but hasn’t reached its minimum sample size, PathFlight says so directly — “insufficient data,” decision gate open — rather than declaring a winner prematurely and letting a team ship a change based on noise.
That closes the full decision path: signal, question, proof, and next move, kept intact from the moment something changes to the moment the team can confirm whether their response actually delivered.
One Verified Answer, Whatever Shape the Decision Needs
Rather than forcing teams to choose between a BI tool, an alerting system, and an experimentation platform, PathFlight lets one verified answer become whatever the next decision requires. As a dashboard, it’s built around decisions rather than a wall of chart inventory — conversion, visits, and activation shown together because they belong to the same question, not scattered across unrelated panels.
As an alert, PathFlight watches what matters and tells you when it moves — “checkout completion fell 14%, concentrated on Safari, quality healthy” — with enough context in the notification itself to know whether it’s worth an immediate response or can wait for the next standup.
As an experiment, it tests the next move directly against the metric and guardrails that matter, with a decision gate that only declares a result once there’s enough evidence to trust it. One installation, one set of definitions, several outputs — instead of a heavier analytics stack stitched together from tools that don’t talk to each other.
Built on the PathFlight SDK: Consented, Versioned, Verifiable
Underneath every answer PathFlight gives is the PathFlight SDK — the layer that connects approved signals on your site to stable, versioned definitions of pages, elements, campaigns, conversions, and experiments. That versioning matters: it’s what stops “conversion” from quietly meaning three different things across three different reports over the course of a year.
Consent gating is built into the SDK from installation, so signals are only captured with the appropriate consent in place, and coverage validation confirms that events are actually arriving as expected — rather than a team discovering months later that a key conversion event was silently broken by a site update.
Installation is a short snippet — initialize the SDK with a project key and your site’s consent function, then define the conversions that matter. From there, PathFlight verifies events are arriving in production before a single dashboard or alert is built on top of them.
Who Uses PathFlight
PathFlight is built to be useful for a five-person team and credible for the enterprise. Product teams use it to understand exactly where users drop off in a flow and whether a shipped fix actually closed the gap. Growth teams use it to catch movement in acquisition and conversion metrics early, and connect that movement to a specific campaign or channel rather than a vague “traffic changed” observation.
Marketing teams use PathFlight to see which campaigns and pages are genuinely driving the outcomes leadership cares about, backed by verified evidence rather than a dashboard number nobody can defend in a meeting. Plans start from $20 per editor per month, with viewers free and usage allowances applying — scoped to let a small team start immediately and scale as usage grows.
“The number moved” isn’t an answer — it’s the start of a question nobody finished asking. PathFlight is built to finish it: what changed, why it matters, and what to do next, all backed by evidence your team can trust.
Our Mission With PathFlight
Ask your website. Act with confidence. PathFlight was built because most teams don’t lack data — they lack a defensible answer they can act on immediately. By turning consented website behavior into verified answers, dashboards, alerts, and experiments, PathFlight replaces “the number moved” with a decision path a team can actually stand behind, from the first signal to a measured outcome.
Start With Your Site →Why Onfrey Built PathFlight
We build products the same way we build growth strategy for clients — by starting with a real, recurring problem instead of a generic template. Every team we work with has hit the same wall: dashboards that report numbers but never explain them, and no clean path from “something changed” to “here’s what we did about it.” PathFlight is that discipline turned into a product, applying the same rigour behind our digital strategy work and digital marketing services to a standalone website intelligence platform.
See how PathFlight fits alongside the other platforms and campaigns we’ve built across our portfolio, including MyTicket Africa and the Radio47 app — Onfrey products built on the same principle of turning raw activity into something a team can actually act on.
Frequently Asked Questions
What is PathFlight?
PathFlight is a verified website intelligence platform that turns consented website behavior into answers your team can reuse as dashboards, alerts, and experiments — helping product, growth, and marketing teams act on evidence instead of guesswork.
How is PathFlight different from standard analytics dashboards?
Standard dashboards report that a number moved. PathFlight identifies the movement, connects it to a specific, evidence-backed cause your team can act on, and lets you test whether the fix actually worked — one connected path instead of separate tools for reporting, alerting, and testing.
Is website data collected through PathFlight consent-compliant?
Yes. The PathFlight SDK includes consent gating from installation, so signals are only captured with appropriate consent in place, alongside versioned event definitions and coverage validation to confirm data is arriving correctly.
Can PathFlight run experiments, or just report on data?
PathFlight can turn a verified answer directly into an experiment with guardrails attached, and it only declares a result once there’s enough sample data to trust it — flagging “insufficient data” rather than calling a winner too early.
How much does PathFlight cost, and how big a team is it built for?
Plans start from $20 per editor per month, with viewers free, so it’s accessible for a five-person team while remaining credible for enterprise usage as data volume and team size grow.
Ready to turn your website’s activity into answers you can act on?
🚀 Start With Your Site Talk to Onfrey About PathFlightPathFlight is one product in the Onfrey suite. See how audience insight feeds the whole growth journey at the Discover stage →