|
This article covers the following: |
Overview
Wingify Journey Analytics is the quantitative analytics module within the Wingify platform that tracks and reports visitor behavior across your site or mobile app.
Wingify Journey Analytics turns raw visitor activity on your site or app into a clear picture of what visitors do, where they convert, and where they drop off. It connects the numbers with behavioral context, so your team can find conversion friction, understand what is driving it, and move straight into testing and optimization.
All of this starts with data that Wingify Journey Analytics captures automatically the moment tracking is enabled. It captures clicks, page views, form submissions, and custom events, without any manual setup.
Wingify Journey Analytics serves as the quantitative analytics layer for a platform built around behavioral analysis and experimentation. Together, these capabilities give your team a unified view of the numbers, the behavior behind them, and the means to act on both, without leaving the platform.
Most analytics workflows split this job across separate tools: one to show what happened, another to explain why, and a third to test what you learned. Wingify Journey Analytics is built for Conversion Rate Optimization (CRO) teams who need to move through all three steps without switching platforms. It is built directly into Wingify, so you can go from a question to a report without leaving your workflow. It is not a replacement for your existing web analytics tool. It is the layer that turns the numbers from any source into a testable hypothesis.
This article introduces what Journey Analytics does, the value it delivers, and how to access it from your Wingify account.
Common Scenarios Wingify Journey Analytics is Built For
The scenarios below show how Journey Analytics fits into everyday CRO work, from spotting an anomaly to shipping a fix.
| Scenario | Details |
| From a metric spike to a root cause. |
A CRO manager notices a spike in the number of unique visitors to a landing page after a content update, but sign-ups do not move with it. A metric report shows an increase in traffic. A quick drill-down into heatmaps on that page shows visitors are not scrolling past the fold, turning a vague traffic not converting observation into a specific, testable hypothesis about page layout. |
| From a funnel drop-off to a fix, same day. |
A funnel report shows a 40% drop-off between add-to-cart and checkout. Instead of filing a ticket to pull session recordings from a separate tool, the CRO practitioner drills into the recordings for that exact step directly from the funnel and finds visitors abandoning at a surprise shipping cost. The team builds a fix that goes into the next test cycle immediately instead of the next sprint. |
| From an unexpected path to a new test idea. |
A growth team builds a flows report starting from the homepage, expecting most visitors to head toward the product pages. Instead, a large share detours through the FAQ page first. That detour becomes the next A/B test: surface FAQ content earlier in the flow rather than making visitors search for it. |
| From a historic question to an answer, without new tracking. |
A product manager wants to know how a checkout redesign performed over the last two months (a question nobody thought to track in advance). Because Wingify captures interactions automatically from day one through a single SmartCode, the team analyzes this retroactively instead of waiting weeks for new tracking to accumulate data. |
| From a pile of data to a ranked list of hypotheses. | Instead of an analyst manually cross-referencing funnel data, recordings, and heatmaps, Wandz AI cross-examines all three together and surfaces a ranked set of optimization hypotheses. This cuts the time between 'something changed' and 'here's what to test' from days to minutes. |
| From siloed views to one shared source of truth. |
A CRO team preparing for a seasonal sale builds a board combining a traffic metric report, a checkout funnel report, and a flows report from the homepage. Marketing, product, and the CRO team all watch the same live board during the sale instead of each pulling numbers from a different tool, catching a broken checkout step within hours instead of at the end of the campaign. |
| From an existing analytics tool to a testing pipeline. | A team already using Google Analytics or a similar platform for traffic reporting adds Wingify Journey Analytics specifically for the CRO layer. It catches conversion friction, explains the reason through recordings and heatmaps, and pushes straight into an A/B test, without ripping out or duplicating the existing analytics setup. |
Across each of these scenarios, the underlying objective is the same: to go from a change in the numbers to an explanation and a testable hypothesis without leaving the workflow. Wingify Journey Analytics meets that requirement through two building blocks, Reports and Boards, covered in the next section.
Understand Boards and Reports - The Building Blocks of Journey Analytics
Everything you build in Journey Analytics is either a report or a board.
Let’s understand each building block in detail.
Reports in Journey Analytics
A report is a single visualization built on your data, and it is available in three types:
-
Metric report
Spots trends before they become problems. It tracks user behavior by measuring events over time, such as page views, clicks, or custom events. For example, you can use it to monitor KPIs such as weekly active users or blog traffic.
For more information, see Use Metric reports in Journey Analytics. -
Funnel report
Finds where conversion breaks down. It analyzes conversion and drop-off across a defined sequence of events and conveys the exact point and percentage where visitors drop off. For example, you can use it to see how many visitors move from product view to add-to-cart page to checkout.
For more information, see Use Funnel Reports in Journey Analytics. -
Flows report
Shows how people move through your product or website. It helps you explore the paths visitors take before or after a key event, including paths that do not follow a predefined flow, to catch friction you were not looking for. For example, you can use it to discover unexpected navigation patterns.
For more information, see Build and Analyze Visitor Paths with Flows Reports in Journey Analytics.
Boards in Journey Analytics
A board is a container that groups multiple reports, and optionally text blocks, into a single dashboard. Boards are how you turn individual reports into a shareable, living view for a team or a stakeholder.
For example, an e-commerce team preparing for a seasonal sale could build a single board to monitor performance in real time. It might include:
- A metric report tracking daily site traffic and revenue against the previous week
- A funnel report showing conversion from product page view to add-to-cart to checkout to purchase, with the exact percentage of visitors lost at each step, and
- A flows report starting from the homepage that reveals whether users are taking the expected path to checkout, or getting sidetracked into support pages, or abandoning after viewing shipping costs.
Instead of a marketer requesting these numbers from an analyst and waiting on a spreadsheet, and a product manager separately checking a different tool for funnel data, both teams open the same board and see the same live picture. This lets them catch a broken checkout step or a traffic drop the same day it happens, rather than at the end of the sale.
Key Benefits of Journey Analytics
- Capture without setup: get clicks, page views, form submissions, and custom events automatically from day one, with no manual tracking required. For more information, see Automatic Data Capture in Journey Analytics for what's captured by default and how to customize it.
- Centralized reporting: build metric, funnel, and flows reports on the same underlying data, in the same interface.
- Flexible organization: group related reports into boards, or keep individual reports standalone.
- Shareable dashboards: boards act as live dashboards your team can revisit and monitor over time.
- Context without switching tools: drill from any report into the session recordings or heatmaps behind it, so you understand why a metric moved, not just that it moved.
- Fits your existing stack: use Journey Analytics alongside your current analytics setup to add behavioral context and experimentation, without replacing what already works.
- Fast access to past work: quickly return to the reports and boards you use most often, without rebuilding them each time.
Access Journey Analytics
- Log in to your Wingify account.
-
From the left navigation panel, click Journey Analytics.
From here, you can access Overview, Starred/Recents, or Browse. For details on what each of these views shows and when to use them, see Understand the Journey Analytics Dashboard Layout.
If your account has not yet been fully configured for Wingify Journey Analytics, you will see a setup screen instead of the Overview page. The screen you land on depends on how far along your account is:
-
You have not started a free trial or registered a domain.
In this case, you are prompted to start a free trial and register the website or app you want to track. -
You have registered a domain but have not enabled tracking.
In this case, you are prompted only to enable data tracking on that domain, since the trial and domain steps are already complete.
Once tracking is enabled, Wingify Journey Analytics starts capturing data automatically.
This automatic capture covers common high-intent interactions, such as clicks, page views, form submissions, and custom events, without requiring you to set up any tracking manually. For a full breakdown of what's captured by default, what's excluded, and how to customize capture behavior, see Automatic Data Capture in Journey Analytics.
Overview is one of three ways to locate your boards and reports in Wingify Journey Analytics. For more information on how Starred/Recents and Browse sections work, see Navigate the Journey Analytics Dashboard.
FAQs
-
Who can view my Boards and Reports?
All users added to your account can view all boards and reports available in Journey Analytics.
-
Do I need to be on a separate plan to use Journey Analytics?
Yes. Additionally, plan and add-on requirements can vary by account. Contact your account manager to confirm what's included with your current plan.
-
Can I use the same report in more than one board?
Yes. A standalone or existing report can be added to multiple boards using the Add existing report option, so you don't need to rebuild it for each dashboard.
-
How is Wingify Journey Analytics different from Web Experimentation reporting?
Web Experimentation reporting focuses on the results of a specific test, such as variation performance against a primary goal. Wingify Journey Analytics is broader. It tracks general user behavior, conversion, and navigation across your site or product, independent of any single test.
Need more help?
For more information or further assistance, contact Wingify Support.