Formidable User Tracking - WordPress Plugin

Formidable User Tracking Guide: How to Read a Visitor’s Journey Before They Submit a Form

Formidable User Tracking becomes useful not when you need one more number in a report, but when a manager or site owner already has a specific submission and needs to answer a practical question: what did this person see before submitting the form, and what context led them to take that action? In Formidable documentation, this add-on is called User Flow. It connects a submission with the sequence of pages visited, available timestamps, on-site search queries, and the referral source when the browser provides that information.

This guide is not a promotional feature list. Instead, it explains a practical workflow: what to prepare before enabling the add-on, where to find the data, how to configure a notification for your team, when you should not display the journey on a public page, how to run a controlled test submission, and how to distinguish a browser limitation from a configuration issue. We will also look at a service lead form, since this is where the journey before submission most often affects a manager’s next decision.

It is important to set the right expectations from the start. Formidable User Tracking works alongside a Formidable Forms form and entry; it does not turn a site into a complete end-to-end web analytics platform. It can help you review a specific submission, but it should not be your only source for decisions about advertising channels, visitor identity, or consent to process data. This approach keeps the configuration useful without overwhelming the team with unnecessary information.

A practical framework for reading the journey before a form submission

Formidable User Tracking becomes genuinely useful not when an entry displays a long list of pages, but when that list answers a question you defined in advance. The official feature description links the journey to the form: information begins to be collected after the visitor arrives on the site and is recorded when the form is submitted. For that reason, it makes more sense to read an entry not as an abstract click log, but as the context of a specific conversion. A manager can see not only the contact details and message, but also where the visit began, which materials preceded the action, and where the submitted form appears within that sequence.

Before your first working day with the add-on, choose one form with a clear outcome. It might be an estimate request, a consultation inquiry, a booking, a registration, or a request for a proposal. Keep the goal concise. For example: "understand which material visitors read before requesting an implementation project." This framework protects you from two extremes. The first is trying to analyze every line in the history without a decision it can support. The second is drawing overly confident conclusions from a single journey. The add-on can help you notice recurring context, but it cannot explain a person’s motivation on its own, and it does not replace careful work on the form itself.

Define a checkpoint before the test submission

A good test starts with a small plan. First, identify the two or three pages that should actually be part of the journey: a service page, a case study, an explanation of the process, an FAQ, or a terms page. Then decide which relationship you want to see. For an agency website, that might be "case study - service - inquiry"; for an educational project, "program - module description - registration"; for a store with an inquiry form, "category - offer page - inquiry." You do not need to include the entire site in the expected journey. The more precise the use case, the easier it is to notice when an important step is missing.

1. Document the form’s goal. The goal explains what counts as a successful submission and which pages may lead to it.
2. Choose one journey to test. Two or three meaningful page transitions and one submission are enough to test the underlying behavior.
3. Prepare separate test data. A neutral name and a dedicated email address help you distinguish your test entry from a real inquiry.
4. Define the expected evidence. The entry should show the referral source or entry point, the relevant pages in the correct order, and the final form submission.

With this preparation, the test stops being a formality. If the entry has no User Flow data, check whether the add-on is active and whether the form was actually submitted. If the block is present but an expected page is missing, compare the real journey with the pages that were opened in the browser. If the journey looks correct, you can move on to notifications and day-to-day use. This is faster than changing several settings at once and later trying to guess which one affected the outcome.

Compare two honest journeys instead of one ideal-looking entry

Run the first journey in a new private browsing window. This reduces the influence of an existing WordPress login, earlier browsing activity, and stored browser data. Open the entry page, move through the prepared materials, fill out the form, and submit it once. Then find that exact entry in the Entries list and review the journey alongside the form data. Exact menu labels may vary in the interface, but the test itself remains the same: entry point first, then the sequence of actions, then the conversion.

Next, run a second test with the same data, but go directly to the form page. The journey should be shorter and should not include the materials viewed in the first test. This comparison reveals the feature’s real boundary: User Flow records what happened during the session before submission; it does not insert pages a marketer wishes had been viewed. The second test also helps the team understand what an inquiry looks like without prior reading, so they do not mistake a short journey for a technical issue.

If the site includes internal search, a separate third test can be helpful. Run a normal search query that genuinely leads to the appropriate page, follow the result, and submit the form. Do not use a meaningless word solely to create a test string. When search appears in the journey, it can suggest how the visitor described their need. That information only becomes meaningful alongside the submission itself and the pages they viewed.

Separate the referral source from the journey to the form

The source and the journey answer different questions. A source helps you understand where the visit began: it may be a search engine, an external link, an email campaign, or a direct visit. The journey shows which pages the person opened before reaching the form. If a visitor arrived from an external link, read a case study, and only then submitted a service inquiry, you should not treat those signals as interchangeable. The source answers "where from," while the page sequence offers a cautious clue about "what happened before the action."

Not every source will be equally detailed. Browser behavior, privacy settings, apps, cross-site navigation, and link parameters can all affect it. For that reason, an empty or generic source does not by itself prove that something is broken. First repeat the test using a clear external referral, and only then investigate a conflict in the site environment. For everyday inquiry handling, it helps to agree on a simple interpretation: a known source plus a meaningful journey can be used as context for a response; an unknown source should not be filled in with assumptions. When the business needs a direct answer to "How did you hear about us?", it is more reliable to ask that question in the form rather than trying to replace it with technical data.

Use time as a verification signal, not a judgment of the visitor

The journey may display timestamps and session duration. These are useful for orientation: you can see the order of actions and notice whether the journey was short or included several meaningful steps. However, a long pause does not automatically mean the person carefully studied a page. They may have left a tab open, been interrupted, or made their decision away from the site. Conversely, a short visit does not prove that a page was unnecessary. The person may already have known the answer and moved quickly to the form.

It is more reliable to work with a small group of similar inquiries than with a single entry. First, identify pages that repeatedly appear before one type of submission. Then compare whether internal search appears, what the entry point was, and where in the form people stop or complete the action. After that, make one reversible improvement: clarify the form link in a case study, move an answer to a common question higher on the page, add a clear next step, or simplify a field. Review new entries after the change. If the journey does not become clearer or the effect is not confirmed, restore the previous version. This is safer than redesigning the form, menu, advertising links, and copy all at once.

Give managers only useful context

User Flow data should not turn inquiry handling into reading a technical log. For the person responding to a customer, three questions are usually enough: where did the visit begin, which one or two pages were most meaningful before the form, and what did the person actually write? If the context helps shape the response, it can be captured briefly in an internal note. For example: "Reviewed the implementation page and a manufacturing case study before submitting the inquiry." There is no need to transfer the full browsing history into an email or external system unless necessary: it adds personal data and rarely improves the quality of the response.

Review notifications separately. If the team receives messages after form submission, test with a separate address and confirm that the email reaches the person who actually handles inquiries. The presence of User Flow in the entry does not mean every recipient needs to see the complete journey. Separate the operational task from analysis: a quick response needs minimal context, while periodic content review requires entry access for the responsible staff member. This reduces the risk of unnecessary data distribution and makes the process easier to understand.

A practical boundary: journey tracking is useful only when the form has a meaningful purpose and there is a clear access process for entries. Before launch, agree on the privacy policy wording, the retention period for inquiries, and which WordPress users genuinely need to view this context. Then run one clean test and make sure the site owner, manager, and technical specialist all interpret the outcome in the same way.

Ultimately, Formidable User Tracking helps you avoid guessing what happened before a submission by letting you review several concrete signals alongside the entry itself: the entry point, the page sequence, search activity when available, and event timing. The more carefully the question is framed and the more honestly the journeys are compared, the more useful this information becomes for the form, the content, and the visitor’s next response.

When pre-submission history genuinely helps the team

A standard form tells you that a visitor entered a name, contact details, and a message. That is enough to respond, but it is often not enough to understand intent. The same question, "How much does it cost?", may appear after a detailed service page, after an article explaining a problem, or immediately after an external referral. Those inquiries differ in how far along the person is and what kind of response they need. User Flow adds the missing context to the entry so that a specialist does not have to infer it from a short message.

The add-on is most valuable for forms where the journey through the site matters to the next action: consultations, estimates, service appointments, demo requests, event registrations, forms on comparison pages, or long questionnaires. In those cases, the page sequence can help show whether the person reached a key explanation, returned to the terms, and which internal materials preceded the submission. It does not give you permission to automatically judge a visitor, but it can help you ask a more precise first follow-up question.

What becomes part of the entry context

The official User Flow description identifies several kinds of information: a list of pages visited before submission, timestamps and time spent at each step, other forms submitted before the current one, terms entered in internal search, and the referral source when someone clicked through from another site. In Formidable, this appears as an action history connected to a specific inquiry. A page link in the history lets you open the visited address in a new tab and check what was published there.

The practical value appears only after interpretation. If the history contains a service page, an FAQ, and the form, you may reasonably assume that the terms matter to the person. If you see on-site search and an instructional article, the inquiry likely followed some independent research. If the list contains only the form page, do not label it a low-quality lead: the visitor may have arrived from a direct link, an email, a bookmark, or a closed channel that did not send a referrer.

Who the add-on suits, and when you need a different level of tracking

Formidable User Tracking is a good fit for a site owner, marketer, inquiry manager, or administrator already using Formidable Forms who wants to review the journey after a specific submission. For a team with several managers, it is important to decide in advance who can open the full inquiry entry, who sees the email, and who may export entries. This is not only an organizational matter; it also reduces unnecessary sharing of contact information.

The tool is less suitable as the primary solution when the requirement is different: building aggregated funnels across thousands of visits, matching campaigns to advertising spend, analyzing events without form submissions, or creating a persistent profile for an authenticated customer. For those needs, User Flow can remain a record of context for an individual inquiry, while web analytics, a CRM, or a customer portal should be treated as separate layers. A journey before a form should not be presented as proof of the exact cause of a conversion.

Quick summary. User Flow answers the question, "What happened before this inquiry?" It does not independently answer, "How many people saw this page?" or "Which campaign definitely produced a sale?"

How data moves from a page visit to an inquiry entry

The most useful way to understand the add-on is as a chain with five links. First, a visitor opens site pages and may use internal search. Next, the browser provides only the referral data that is not limited by privacy settings, extensions, or the type of navigation. The person then submits the form. After a successful submission, Formidable creates an entry, and User Flow attaches the context collected so far. Finally, a staff member opens the entry, notification, or permitted display and uses the information as a guide for responding.

This sequence explains two common misunderstandings. First, the add-on starts working after it is enabled, so older entries will not automatically receive history. Second, an empty external source is not the same as a direct visit. A referrer may be missing because of how the navigation occurred or because of browser settings, and similar symptoms have already been raised with Formidable support. The appropriate response is to compare several recent tests from different sources, not to change the form based on one empty field.

Where technical fact ends and interpretation begins

A technical fact is that the entry displays a sequence of available actions. A manager’s conclusion about the person’s intent is an interpretation. For example, moving from an article to a form confirms that the page was part of the journey, but it does not confirm that the article text was the only reason for the inquiry. It is therefore helpful to phrase observations neutrally: "The comparison page was opened before the form," rather than, "The customer chose us after comparing options."

This approach preserves the quality of analysis and prevents verifiable information from being replaced by assumptions. Within the team, you can agree on a simple template for an inquiry note: the last meaningful page, one notable intermediate step, the available source, the question from the form, and the next action. The template does not need to be displayed to the visitor, and it should not become a required form field. Its only purpose is to help the history support a response instead of remaining decorative log data.

Why User Flow is not the same as a visitor account

Even when a form is connected to registration or includes contact details, User Flow and a WordPress profile serve different purposes. Registration creates or updates a user according to the rules of the relevant form action, while the User Flow journey belongs to the entry and history available for that individual submission. Do not create access rules or personalization based on the assumption that a browsing sequence represents a permanent user identity. Those decisions require separate fields, agreed authentication rules, and access-rights checks.

Preparing the site: the form, roles, and access boundaries

Before installation, do not start with the add-on toggle. First choose one real form where you can safely run a test. It is better to use a contact form on a test page or a duplicate form than to enable tracking across every use case immediately. This lets the team see exactly how the journey appears with its theme, caching, and notification delivery method without mixing test entries into live work.

Confirm that the main Formidable Forms plugin is installed and active, and that your license provides access to the add-on. User Flow documentation specifies the Plus plan or higher and an up-to-date installed Formidable Forms premium base. There is no need to explain file access details or licensing actions to site visitors. For an administrator, it is enough to verify that the User Tracking card is available in the add-ons section and that the main plugin is not disabled.

Checklist before enabling the add-on

• Choose one form for testing and record its address so you do not have to search among similar pages.
• Check who can view entries and who genuinely needs the IP address, browser details, referrer, and journey history to handle an inquiry.
• Review the data-processing policy and agree with the responsible specialist on how the site informs people about collecting technical and contact information.
• Review caching and optimization: after enabling the add-on, do not clear everything at random. Prepare one controlled test before and after clearing the relevant cache.
• Create a restore point in the site’s normal backup system, or at minimum capture the initial form settings and email actions in a screenshot for the team.

Discuss public display separately. The documentation allows information to be shown with shortcodes on a page, in an entry, or in a confirmation message. Technical availability does not mean that this display is appropriate for a visitor. For most lead forms, it is safer to leave the full User Flow in the admin area and a private manager notification, while showing only a standard submission confirmation on the public site.

Privacy without a false sense of security

Notifications and entry details may include an IP address, browser information, and the referrer URL, while User Flow shows visited pages. That means this configuration affects more than manager convenience; it affects the information being processed. Review the consent wording, privacy policy, inquiry retention period, list of staff with access, and process for removing outdated entries in line with your organization’s rules and applicable requirements. This article is not legal advice, but this step should not be skipped.

A required practical step is to test permissions under a standard staff account, not only under the primary administrator account. If a staff member can see more data than they need to respond to an inquiry, narrow access first, then connect the history to emails or public display.

Installation and the first controlled test without unnecessary changes

In WordPress, open Formidable → Add-Ons, find the User Tracking add-on, and enable it with its toggle. The official instructions describe this step as activating the add-on from the catalog after confirming access. Once it is enabled, do not expect older rows in Entries to change. The add-on begins collecting information for future submissions, so your first task is to create a new, easily recognizable test.

1. Open a starting page in a separate window, then a service page or article connected to the test form.
2. If search is available, enter a simple unique query, such as the service name, so you can later see whether that step appears in the journey.
3. Go to the form page and submit a test entry with a marker in the name or message, such as "User Flow Check."
4. Return to Formidable → Forms, open the relevant form, go to Entries, and select View for the new entry.
5. Scroll to the User Flow block and compare the history with the pages you actually opened.

If everything is visible, record the outcome in the team’s working instructions: where the relevant form is located, what the block is called, and who checks the test after a theme update or major site redesign. If there is no history, do not immediately add several third-party tracking tools or change the form content. First make sure the entry was created after activation, that you opened the correct form, and that you are viewing the detailed entry rather than only the inquiry list.

How to test an external referral

The second test is not just a box to check. Open a link to the site’s starting page from another domain where you can control the referral, then navigate to the form and submit a separate inquiry. After that, compare the entry with the first test. If the referrer appears, the team will see its format and understand where it is displayed. If it does not appear, do not draw a conclusion from a single experiment: some types of navigation do not pass a source. Record the test condition and check another channel without changing Formidable.

Result check: a successful initial launch is not a polished report; it is a new entry whose history matches your controlled journey. At least one test entry must be created after the add-on is activated.

How to read User Flow in an inquiry entry without mistaking assumptions for facts

In a working entry, do not focus on just any first URL. Look at the chain. Start with the last meaningful page before the form, since it often shows where the person’s attention settled. Then check whether an article, pricing page, FAQ, category, or internal search appeared before it. Next, review available timestamps and step durations. Finally, compare the journey with the form fields themselves. This order helps you avoid losing the important details in a long list of addresses.

If User Flow shows another form submitted before the current one, that can be useful context: the visitor may have subscribed, tried an estimate, or registered before making the main inquiry. However, do not manually merge entries just because the journeys look similar. First verify the contact data, your process for handling duplicates, and whether your team even has a valid reason to connect those records. Journey history can help you notice a sequence, but it does not replace data verification.

Three questions for a manager before responding

1. What was the last useful piece of content? If it was a terms or comparison page, the response may need a clear explanation of that specific point.
2. Was there an on-site search? The search phrase shows the visitor’s language and can help you choose a human, relevant wording for the response, but it is not a ready-made marketing segment.
3. Is a referral source available? Use it as context, not as unquestionable attribution. A direct or empty source does not explain the person’s full path to the inquiry.

Example of a neutral CRM note

Instead of a subjective comment such as "hot lead from advertising," leave a short, verifiable note: "Before the form, the visitor opened the service article and FAQ; the final page was the estimate page. Internal search: 'project launch timeline.' No external source was provided. In the response, clarify the desired timeline and offer a link to the estimate." This kind of note separates observation from the next action and remains understandable to a colleague.

Do not automatically copy the full journey into a third-party system until you have considered access, retention, and whether that transfer is necessary. For most small teams, it is enough for a staff member to review User Flow in Formidable and save only a brief business conclusion in the CRM. This reduces duplication of technical data and keeps the customer record cleaner.

Notification settings: when a manager needs the journey in the email itself

If one or more managers monitor inquiries, opening the admin area for every new entry can be inconvenient. The official documentation allows User Flow information to be appended to an email notification. In the form editor, open Settings → General → Actions & Notifications, select the Email Notification action, find the message area, and enable Append IP Address, Browser, and Referring URL to message. Once saved, a new submission will add the information to the end of the email.

Before enabling it, assess the delivery channel. A manager’s inbox, a shared support queue, forwarding to personal addresses, and a CRM mailbox provide different levels of control. If the email contains an IP address, browser details, referrer, and journey, the recipient list should be limited to those who need that information. Do not add this block to the visitor’s autoresponder: the information is for staff, not for the person who has just submitted the form.

How to make the email useful rather than overloaded

Start the message with the fields a manager needs to respond: name, contact method, subject, and inquiry text. Leave User Flow information at the end as context. If one form handles several inquiry types, use Formidable’s built-in conditional logic for different recipients or actions only when the condition is based on form fields and has been tested. Do not attempt to route emails based on every URL in User Flow; that quickly becomes fragile behavior that is difficult to maintain.

After enabling the option, submit a new test and check three things at once: the email arrived, the added context appears where expected, and the recipient is authorized to see it. If no email arrives at all, first check standard WordPress delivery and the email action settings. Formidable documentation specifically recommends beginning delivery troubleshooting with the recipient address, other site emails, the spam folder, and an SMTP solution when delivery is failing. User Flow is not a reason to rewrite the form.

When it is better to keep the data only in Entries

Keep User Flow only in the Entries record if inquiry volume is low, managers have different roles, or the email contains enough information from the form itself. This is also a sensible approach for inquiries involving sensitive topics, where technical details are not needed for the initial response. Email convenience should not outweigh the principle of minimum access: a staff member can open the detailed entry only when the context genuinely helps them complete the task.

How to interpret different page types in an inquiry history

A URL list becomes useful only once the team understands what different page types mean. You do not need to remember the address of every publication. It is enough to identify a few meaningful groups in advance: entry pages that introduce an offer, articles and guides, categories or collections, service pages, comparisons, FAQs, calculators, contact pages, and the form itself. Then a manager sees not a collection of technical addresses, but a normal reader journey from first learning about a topic to asking a question.

Start with the last meaningful address before the form. If it is a service page, it can be helpful to review which terms or options it explains. If it is an article, check which question it answers and whether the inquiry message repeats that question. If it is an FAQ, the response usually has one of two follow-ups: briefly confirm a condition or ask for missing information. Do not turn the history into a word-for-word summary of pages for the customer. Its purpose is to make the first response more relevant.

An article or guide before the form

Visiting an article often means the person was trying to understand the topic independently. A manager’s most common mistake is to begin with a sales pitch and repeat what the page already explained. Instead, take one topic from the journey and connect it to the form question: "You were reviewing our project preparation guide. Do you already have the initial information, or do we first need to define the scope?" The question does not reveal unnecessary details about journey tracking, but it removes uncertainty.

For a site editor, recurring "article - form" combinations can be a reason to review the material. If several inquiries show that readers almost always move from one guide to the form with the same question, the article may be missing a step, an example, or a clear link to the next type of help. This is a content-improvement hypothesis, not proof that the page is effective. Test it with a larger group of inquiries and do not change the page after one submission.

A service, pricing, or comparison page

These addresses more often indicate a point of choice. A manager can prepare a response with specific details: timing, the scope of the first stage, the consultation format, or project boundaries. However, the word "price" in a URL or page heading does not mean the visitor is ready to buy. They may be comparing options, checking a range, or looking for terms on behalf of a colleague. Use the journey to choose a follow-up question, not to apply a label such as "ready" or "not ready."

On the site side, this group of pages is especially sensitive to accuracy. If User Flow frequently shows an old address that no longer matches the current service, review redirects and menu links. This is not a User Flow configuration issue; it is ordinary site maintenance. The add-on simply helps you notice that the real visitor journey does not match what the team considers the primary path.

Internal search and repeat visits to the form

An internal search phrase can be more useful than a long list of URLs because it shows the words a person used to describe the task. Do not copy it word for word into a response template or use it as a reason for advertising segmentation. It is enough to check whether the site has a high-quality answer to the query and whether additional material would help in the email. If searches for one term recur, that may indicate a need to improve navigation or add a clear FAQ section.

Returning to a form does not necessarily point to a technical issue. The visitor may have returned after reading, discussed the question with a colleague, refreshed the page, or corrected fields. Alongside the Formidable entry, the more important check is whether one completed inquiry was created or several separate submissions. If duplicates occur, use the form’s standard tools for controlling unique values and your organizational handling process rather than trying to diagnose the issue from User Flow alone.

A practical principle. One journey should lead to one improvement: a follow-up question, a useful link, a page hypothesis, or a navigation check. If it does not change any decision, there is no need to transfer it to the CRM or collect it for archival purposes.

Working rules for the team: how not to turn inquiry context into noise

After the first successful test, it is tempting to connect journey history to every form, inbox, and staff member. In practice, it is better to establish a simple handling process. It does not require new automation: define which forms have User Flow enabled, who opens the details, where the business note is stored, and when the history is no longer needed. This agreement is more useful than dozens of formal metrics because it protects the team from interpreting the same page sequence in different ways.

A minimal process for one inquiry

The staff member first reads the form fields, then the final meaningful step in the journey, and, when available, one earlier piece of content. They then choose one action: clarify the context, provide a link to the appropriate explanation, pass the inquiry to the right specialist, or handle it normally without mentioning User Flow. Only the business wording needed by the next person is saved in the CRM or task. The complete URL list remains in Formidable, where it is linked to the original entry.

This process is especially useful when inquiries include both marketing and service requests. For a marketing question, the journey may suggest interest in a service. For a service request, the form, error description, and customer data matter more, while the history may be secondary. A staff member does not need to search for meaning in every page. They use User Flow where it reduces the number of follow-up questions.

How to train a new manager with test data

Create three test entries with different controlled journeys. The first: article - service - form. The second: comparison page - FAQ - form. The third: direct visit to the form. For each, prepare a short task: identify the last meaningful material, create one neutral follow-up question, and explain why a missing referrer is not an error. This training does not require real personal data and quickly shows whether the staff member understands the boundary between fact and interpretation.

It is useful to add a fourth entry with internal search in the history. Ask the staff member not to copy the query into an email, but to decide which site page could be offered in response. Then confirm that all test entries are deleted or marked after training according to internal rules. The training set should be clean: do not use real contacts, active customer inquiries, or staff members’ random addresses.

When to perform a monthly review

A regular review of several new entries is justified after changes that affect the visitor journey: a new menu structure, moving a form to another page, rewriting an article, caching changes, a new email-delivery system, a change in advertising provider, or changes to WordPress roles. Check not only whether the User Flow block exists, but also whether the team still opens the correct entry and does not send the expanded notification to unnecessary recipients.

If a month passes without meaningful changes, there is no need to create artificial tests simply for reporting. It is enough to check behavior during the first planned form revision or when a symptom appears: the journey disappears, the notification becomes incomplete, or a staff member cannot open an entry. The purpose of monitoring is to maintain a repeatable process, not to increase the number of records.

Example of an internal instruction card

• Form: service consultation; the journey is used for the initial response.
• Where to look: Formidable → Forms → Entries → View, User Flow block.
• What to transfer: only one fact about the last meaningful material and the next question.
• What not to do: do not tell the visitor their journey was reviewed, do not copy the entire URL list, and do not draw conclusions about identity.
• Post-change check: a new test inquiry using a known journey, then verification in Entries.

This card works better than a long policy because it can be opened while handling an inquiry. However, it does not replace the company’s official policy for legal and organizational requirements. If the data being collected or shared changes, update both the working instructions and the related process documents.

Public journey display: confirmations, pages, and safe boundaries

The documentation offers two ways to display User Flow. For an already known entry on a page or post, use [frm-show-entry id=x user_info=1], where x is replaced with the entry ID. For a confirmation message after submission, use [frm-show-entry id=[id] user_info=1]. These examples show what is technically possible, but the safe use case depends on who will see the output and how the URL is protected.

For a normal contact form, do not insert the full journey into a public confirmation message. The visitor already knows which pages they opened, and a published display can expose technical information where it is unnecessary. This approach is appropriate only in a private working process, for example for a staff member signed in under a controlled role who opens an entry from a protected link. Even then, first verify that the person cannot change the identifier and view someone else’s inquiry.

A safe working setup without public disclosure

The most reliable setup for a lead form looks like this: the visitor receives a standard confirmation that the inquiry was received; the manager receives a notification or opens Entries; the full User Flow remains in the internal interface; only a short internal note is sent to the CRM if needed. In this setup, the technical journey helps the team work, but it does not become part of the public page or create a new risk of accidental access.

If display is still needed in a private area

First create a separate test entry and use its identifier. Place the shortcode on a draft or private page, open it under the role intended to view it and under a role without access. Confirm that only the required block is visible, that no unnecessary entries appear, and that the output disappears after the shortcode is removed. Do not insert the shortcode into theme files or modify WordPress or Formidable core files: that approach is harder to reverse and provides no advantage over the standard editor.

Practical example: a consultation form after an article and service page

Imagine an agency website with an article about project preparation, a service page describing the work scope, an FAQ, and a form titled "Request a Consultation." The manager receives inquiries, but a short message does not always show what to discuss first. The goal of the setup is not to rate the visitor, but to help the manager see whether they read the introductory material, reviewed the terms, and which page led them to the form.

Preparing the example

The form has clear fields: name, email or phone number, topic, desired timeline, and message. The email notification already arrives in a shared business inbox. Formidable User Tracking is enabled, while the complete User Flow block remains in Entries. For testing, choose a dedicated address that will not enter normal handling and prepare three pages in advance: the article, the service page, and the FAQ. This makes the journey verifiable.

Sequence of actions

1. Open the article and read one section, then go to the service page.
2. Open the FAQ, return to the service page, and proceed to the consultation form.
3. Enter a unique phrase in the message, such as "Journey test: project timeline," and submit the form.
4. Check the basic fields in the notification. Then open the new entry through Formidable → Forms → Entries → View.
5. In the User Flow block, compare the journey with the sequence you created: article, service, FAQ, form.
6. Write a neutral internal note: which material was the final meaningful step and which clarification would be appropriate in the response.

The expected outcome is not a perfect history of every click, but a recognizable chain of meaningful pages connected to the test. If the journey contains extra technical pages, do not immediately try to hide them with code. First assess whether they genuinely interfere with the work. A utility page may appear only during testing or may be part of the normal journey, while removing data could make the inquiry less understandable.

How to turn the journey into a useful response

Suppose the final meaningful page was an FAQ about timelines and the form indicates that the project needs to start soon. Instead of a generic email saying, "Thank you for contacting us," the manager can begin with a business-focused clarification: "You mentioned a tight timeline. Is it correct that your priority is to agree on the scope of the first phase first?" This email does not tell the visitor that the team analyzed their journey. It uses the context to eliminate an unnecessary round of questions.

If the history shows only the form, the response should not become worse. The manager works from the inquiry fields, just as they would without the add-on. This is an important process-quality check: User Flow improves some inquiries, but the core response workflow must function without it. Otherwise, the team becomes dependent on technical context and loses the ability to handle incomplete data properly.

Checking the outcome after updates, caching changes, and form revisions

The setup is complete not when the add-on is switched on, but when the behavior can be repeated. After updating Formidable Forms, changing the theme, adjusting caching, moving a domain, or substantially revising a form, repeat a short test journey. You do not need to run a full audit every day. It is enough to visit two or three pages, submit a test, and open the new entry. This takes only a few minutes and confirms that the "visit - form - entry" connection remains intact.

For ongoing checks, create an internal test use case with fixed steps. For example: open an article, search for "consultation," go to the service page, fill out the form with a test address, open Entries, and check User Flow and the email. A consistent journey is more useful than a random one because the team knows exactly what to expect. Mark the test entry clearly so that it is not treated as a real lead.

Checkpoint table

This table does not replace the detailed inquiry entry. It helps separate verification of the add-on from verification of the regular form and email.

After a successful test, do not leave permanent demo forms published on the site. Remove the test page or return it to draft status, save short instructions for the team, and use the same journey for the next check. This is safer than leaving a technical form accessible to visitors.

When to hide User Flow for a particular form

Not every form needs the same amount of context. A short callback request, an internal employee questionnaire, and a form with sensitive content may require different viewing rules. Official User Flow documentation includes a PHP example that removes the tracking block when viewing an entry for a specified form. This is not a way to "clean" data retroactively or a universal privacy setting; it is a targeted adjustment to the admin-area display.

Use this code only in a child theme or in a trusted custom-snippet mechanism already approved for the site. Test it first on a site copy and with one known form. In the example below, only the form ID number is changed. Do not add untested conditions, and do not edit the plugin’s own files.

add_action('frm_show_entry', 'hide_user_flow', 9);
function hide_user_flow( $entry ) {
    $exclude_form_id = 1659; // Replace with the ID of the required form.
    if ( $exclude_form_id !== (int) $entry->form_id ) {
        return;
    }

    remove_action( 'frm_after_show_entry', 'FrmUsrTrkAppController::show_tracking_data' );
}

After saving, open one entry for the target form and one for another form. The User Flow block should disappear from the target form’s view and remain visible for the other form. If the block disappears everywhere, restore the snippet to its original state and verify the form ID again. The rollback is simple: disable or remove only this custom snippet. You do not need to remove the add-on or the entries themselves.

The limitation matters: hiding the block is not a substitute for retention policies and access controls. If data should not be collected or should not be available to certain roles, the decision must be made at the form level, through admin-area access, and through internal rules, not only by visually hiding one part of a page.

Troubleshooting: why the journey or referral source looks incomplete

It is best to investigate User Flow issues as a chain of evidence. Start with a new inquiry and its detailed entry, then move to the specific type of missing data. Do not mix form behavior, email delivery, and referrer availability in one diagnosis: they have different causes and different fixes.

A new inquiry has no User Flow block

Symptom: the entry was created, but its detailed view does not contain the expected block. Likely cause: the add-on is not enabled, the entry was created before activation, or the wrong screen is open. Check: Formidable → Add-Ons, the creation date of the test entry, the path Forms → Entries → View, and the form name. Fix: enable the add-on, create a completely new test submission, and open it through View. When to roll back: if the test form is no longer needed, remove only the test entry and page, but do not disable the add-on based on an old entry.

There is an inquiry, but the page list is shorter than expected

Symptom: the history shows the form or part of the journey, but one of the test pages is missing. Likely cause: the test was run in another window, involved cross-domain navigation, used an old cached tab, or some actions did not enter the available context. Check: repeat the same journey in one clean browser window without changing the form or adding third-party scripts. Fix: compare two new entries and document the consistent behavior. When to roll back: if the issue appeared immediately after a specific caching or optimization change, temporarily restore that exact change and repeat the short test.

The external referral source is not displayed

Symptom: User Flow shows activity on the site but does not show the site the visitor came from. Likely cause: the source was not provided by the browser, or the navigation type does not allow the referrer to be obtained. In the Formidable community, support also recommends checking how the data is displayed rather than treating this as proof of a direct visit. Check: run two controlled referrals from different external pages, then review the new entries. Fix: use an available referrer as additional context, and do not create artificial rules when it is absent. When to roll back: there is usually nothing to roll back in Formidable; reverse only a recent site change if it simultaneously broke other form behavior.

The email has no journey even though it is visible in Entries

Symptom: the inquiry entry contains User Flow, but the email shows only form fields. Likely cause: the selected Email Notification does not have the option to append the IP address, browser, and referrer URL enabled, or a different notification action is being checked. Check: the path Settings → General → Actions & Notifications, the selected email action, and the Append IP Address, Browser, and Referring URL to message checkbox. Fix: enable the option, save the action, and submit a new test inquiry. When to roll back: if the recipient does not need expanded context or the mailbox is not sufficiently protected, disable the checkbox and keep the data in Entries.

The form email does not arrive at all

Symptom: the entry is created, but no notification arrives. Likely cause: standard WordPress delivery, the recipient address, or the email action configuration, not User Flow. Check: the recipient, the spam folder, other system emails from the site, and the normal delivery configuration. Fix: resolve the delivery issue using Formidable documentation and the SMTP solution used on the site, then repeat the test. When to roll back: disable only a recently added address or condition if testing confirms that it is interfering with the notification.

Using CRM and web analytics alongside User Flow without mixing their roles

Formidable User Tracking can be used alongside a CRM and web analytics, but only with a clear division of responsibility. Formidable stores the inquiry and its context at the entry level. The CRM manages communication, processing status, and later agreements. Web analytics handles aggregated visits, events, and channel comparisons. Do not promise a customer an official integration unless the developer documents one: it is safer to begin with a manager’s manual note or an existing approved process for passing form fields.

A practical option for a small team

First enable User Flow and run tests only in Formidable. Then agree on which two or three observations a staff member will copy to the CRM manually: the last meaningful page, the search query when available, and a short clarification for the response. Contact fields and the inquiry itself are passed to the CRM through the site’s usual approved method. This approach does not create an untracked transfer of technical data and can be discontinued without affecting inquiry history.

The point of friction here is usually organizational rather than technical: different staff members describe the journey differently. The solution is a small one-sentence note format, not long URL copying. The verification is simple: another manager should understand the context without opening Formidable. If the note becomes long or contains unnecessary data, reduce it to the fact and the next action.

What not to do with a visitor journey

• Do Not Use History As The Sole Basis For Automatically Rejecting Or Rating A Person.
• Do Not Send The Full Journey In A Visitor Autoresponder Or To A Broad Group Email List.
• Do Not Build Fragile Conditions Around Every URL When Form Fields And A Clear Process Are Enough.
• Do Not Treat An Empty Referrer As Proof That The Person Arrived Directly.

The capitalization in these items does not mean they are system commands. They are ordinary team rules that should be adapted to your inquiry-handling process. When the article is published on a site, they also help readers notice that User Flow is context, not an automated judge of an inquiry.

When Formidable User Tracking is the right choice

Formidable User Tracking is worth using when a site already runs on Formidable Forms and the team needs more context for one specific inquiry. Start with one important form, enable User Flow in the add-ons section, run a controlled submission, check the Entries record, and only then decide whether to add the context to a protected notification. This order produces a clear outcome without unnecessary automation.

The best outcome comes when the journey helps make the next response more precise rather than becoming another collection of data no one reads. Keep the complete history where it is needed, check it after meaningful site changes, and avoid conclusions about a visitor when all you have is a technical trace. If this workflow fits your form, you can download Formidable User Tracking and begin with a safe test on one page.

Formidable User Tracking Setup Video

This video complements the guide: a product video. Open it after the basic setup to compare the interface and sequence of actions.