Journey Analytics

Journey Analytics connects a form entry with the path that led to it. Instead of seeing only a name and message, you can review the pages, clicks, sections, scroll depth and form activity that happened before the visitor submitted the form. The feature then combines entries with a path into charts, funnels and goal reports inside WordPress.

Journey Analytics reads paths attached to form entries. It is not a replacement for a visitor analytics service and does not count visitors who never submit a form or trigger a recorded goal.

Where to find it and what it requires

Open Baza Helper → Journey analytics. The page is a Pro feature and contains three tabs:

• Analytics: figures and charts built from entries with a visitor path.
• Funnels and goals: ordered steps, goals, templates and conversion reports.
• Collecting: visitor-path collection, buy-click goals and diagnostics.

The collector loads only when the required licence features are available, Form entries is active, path collection is enabled and Baza Helper analytics tracking is on. If analytics consent is required, collection begins only after the visitor accepts analytics.

Start collecting visitor paths

1. Open Baza Helper → Journey analytics → Collecting.
2. Enable “Collect the visitor’s path and attach it to entries (only after the visitor accepted analytics)”. This setting is on by default when the licence allows the collector.
3. Make sure analytics tracking is enabled in Baza Helper.
4. Save the settings.
5. Submit a test form as a visitor after accepting analytics consent.
6. Open the new item under Form entries and expand its Journey field.

The journey is stored in the visitor’s browser tab during the session. When an eligible POST form is submitted, the collector adds a hidden baza_helper_journey field. The field is removed from the page after five seconds. Contact Form 7 receives it through its submit event, although an unregistered form field is not included in Contact Form 7 emails.

What the collector records

One journey contains up to 120 steps. Consecutive identical steps are not repeated. When the limit is reached, the earliest step after the first one is removed so that the beginning of the visit is preserved.

• Page: the page path, including history and hash changes.
• Click: a button, link, tracked control or element with role="button".
• Section: an identified section, an Elementor section or container with an ID, or an H1 to H3 heading that enters the viewport.
• Scroll: 25, 50, 75 and 90 percent.
• Form: the first focus inside a form and the form submission.
• Goal: a recognised buy action when buy-click collection is enabled.

Click labels use data-track-id, aria-label, the element ID or visible text, limited to 40 characters. Telephone and email links are stored as phone and email. Form values are never included.

Read the journey inside an entry

Open Baza Helper → Form entries and select an entry. A Journey field is shown as a timeline with:

• total time on the site;
• number of steps;
• pages and kinds of activity;
• the time, type, label and page of every step;
• repeated steps folded into a compact ×N row.

Journey text may use up to 30,000 characters so the end of a longer visit is not cut off. Other long form fields use a smaller storage limit.

Use the Analytics tab

The Analytics tab aggregates the newest 500 entries that match the selected form and period. Use the header filters to choose all forms or one form and one of these periods: all time, 7, 30, 90, 365 days.

The four figures show:

• entries with a journey;
• average time;
• median time;
• average number of steps.

When a fixed period is selected, the figures can show the change from the preceding period.

Eight chart cards cover:

• time on the site before sending;
• steps per visit;
• kinds of activity;
• most used buttons and sections;
• pages with the most activity;
• landing pages;
• the last step before sending;
• entries and average time during the last 30 days.

List charts can switch between “Bars” and “Ring”. The menu on each chart can download SVG, PNG or CSV. The selected view is remembered in the browser.

Build funnels and goals

A funnel describes the ordered steps you expect a lead to take and the goal it should reach. You can save up to 10 funnels with up to 12 steps in each funnel.

1. Open Funnels and goals.
2. Read “How funnels work” if this is your first funnel.
3. Press “Add a funnel” or start with “Templates from my site”.
4. Name the funnel and add its steps in order.
5. Define the final goal.
6. Press “Save funnels” or use Ctrl/Cmd + S.

A step can match any action, a page view, click, section, scroll depth or form activity. A goal can also be “Entry sent” or “Goal reached”. Conditions can check the label or page and compare it with equals, contains or starts with. Matching is case-insensitive. An empty value means any event of the selected kind where the interface allows it.

The report shows how many leads reached each step, its share of all entries, conversion from the preceding step, how many left there, the largest drop-off, how many reached the goal and the average time to the goal.

Use templates from your site

“Templates from my site” scans the actual site and offers funnels supported by what it finds. Sources include site pages, WooCommerce routes, forms with entries, supported form plugins, common landing pages and clicked buttons already present in collected journeys.

The available templates can include:

• contact form lead;
• call or email;
• messenger chat;
• pricing to order;
• booking or request;
• shop product to order;
• reader to lead;
• the most common collected path;
• engaged visitor.

An unavailable template remains visible with the reason. Press “Add to my funnels”, review every rule and then save. Each rule is also written as a sentence below its fields, and known values are suggested while you type.

Funnels on multilingual sites

One Text field can contain alternatives separated by |, for example /contact|/kontakty|/kontakt or Order now|Замовити|Bestellen. Page rules ignore a trailing slash.

Templates use Polylang or WPML translations to add the available page paths automatically. The home page of each language is also included. Button text is language-specific, so add the button wording for the other languages yourself. Language-neutral steps, such as form activity, scroll depth, phone clicks, email clicks and recorded buy goals, work across languages.

Record buy clicks as goals

Some checkout or payment links leave the site before a form can be submitted. To keep those actions as goals:

1. Open Collecting.
2. Enable “Record clicks on buy links as goals (only after the visitor accepted analytics)”. It is off by default.
3. Review “Words that mark a buy link”. Add one word or phrase per line for every language you use.
4. Add optional CSS selectors under “Buy buttons by CSS selector”.
5. Save the settings.

A recognised action is stored as a read entry for the form “Goal: buy click”, with no messenger alert. The visitor path contains a goal | buy step, so funnels do not depend on the visible language of the button. Checkout, cart, /buy, add-to-cart and supported payment-host links can be recognised by their address. A picture-only button with a normal page address needs a selector or data-track-id.

Why Journey Analytics may be empty

The built-in “Why is it empty?” card checks:

• whether the collector script exists in the installed build;
• whether the licence permits Journey Analytics;
• whether collection is enabled;
• whether Baza Helper analytics tracking is enabled;
• whether consent is required and a cookie banner is available;
• whether entries exist;
• how many of the newest 500 entries contain a Journey field;
• which entries predate collection and which later entries arrived without a path;
• how missing paths are distributed by source form plugin.

When no journey exists, diagnostics are opened in place of empty charts. Once data exists, the same card remains available in a folded state.

Privacy and consent

• Nothing is collected until analytics consent is true when consent is required.
• Withdrawing consent clears the journey stored in the browser session and removes the collector’s event listeners.
• The collector sends nothing by itself. The path travels with a form submission or an enabled buy-click goal.
• Form values, names, email addresses and phone numbers are not recorded in the journey.
• Telephone and email links become the neutral labels phone and email.
• Email-like text and numbers of six or more characters are removed from labels.
• Only the path is kept. Query strings are not recorded, and long numbers or codes in paths become :id.
• Form entries remain as private content in the site’s own WordPress database.

These controls are designed to respect the visitor’s analytics choice. You remain responsible for the wording and legal basis of your site’s consent and privacy notices.

Supported forms and limits

Baza Helper records entries from Contact Form 7, Elementor Forms, WPForms, Gravity Forms and Fluent Forms. Other integrations can create entries through the plugin action described below. Classic WooCommerce checkout orders can include a journey. WooCommerce block checkout orders are recorded without a journey.

Only entries that contain a valid path count in charts and funnels. A visitor who does not submit a supported form or trigger an enabled buy goal is not represented. Journey Analytics therefore complements visitor analytics but does not replace it.

The reports use at most the newest 500 matching entries. The collector and Journey Analytics are not included in the WordPress.org build.

For developers

• The private entry post type is baza_helper_entry.
• Collector settings are stored in baza_helper_entries.
• Funnels are stored in baza_helper_journey_goals and are included in Baza Helper settings export and import.
• A custom integration can call do_action( 'baza_helper_record_entry', 'My plugin', 'Form name', array( 'Label' => 'value' ) ).
• The frontend exposes window.bazaHelperJourney.text(), steps() and active() when the collector is loaded.
• The exact licence feature is Journey analytics, with key journeyAnalytics.

Frequently asked questions

Does it work without the Baza Helper cookie banner?

The collector reads the analytics-consent state supplied by Baza Helper tracking. When consent is required, collection starts only after analytics consent becomes true. The diagnostic card reports when consent is required but no Baza Helper cookie banner is enabled.

Does it record form values, phone numbers or email addresses?

No form values are added to the journey. Phone and email links use the neutral labels phone and email. Email-like text and long numbers are removed from labels, and query strings are not stored.

Why is a path missing from an entry?

The entry may predate collection, the visitor may not have accepted analytics, a cached page may not have included the collector, the form may have been submitted by a script, or a required feature or setting may be off. Open “Why is it empty?” for checks.

Does it work on a multilingual site?

Yes. Page templates can use Polylang and WPML translations. Put language-specific alternatives in one funnel rule with |. Button wording must be added for each language, while scroll, form, phone, email and buy-goal steps are language-neutral.

Which forms can carry a visitor path?

The built-in entry integrations cover Contact Form 7, Elementor Forms, WPForms, Gravity Forms and Fluent Forms. Classic WooCommerce checkout can carry a path. WooCommerce block checkout entries do not include one.

Do I need a separate analytics account?

No. Journey Analytics reads entries stored on your WordPress site and draws reports in the WordPress dashboard. It does not require a separate analytics account.