Skip to main content

Flow Navigation: Intro

Learn about the different possibilities to navigate through your Heyflow.

Creating an intuitive and seamless experience for your visitors is key to increasing conversions. With Heyflow, you can easily structure and optimize your flow navigation to guide users through your funnel effortlessly.

In this article, you'll learn how to set up, customize, and optimize navigation elements like buttons, use conditional logic and master navigation via hashtag to enhance user engagement and improve flow performance.


Navigation Possibilities

Buttons

Buttons are essential for guiding users through your flow and creating a smooth interaction. In Heyflow, you can customize buttons to control navigation, trigger actions, or branch users based on their responses.

You can choose out of a range of buttons, tailored to your needs. By strategically placing and configuring buttons, you can create a seamless user journey and improve conversions. Get to know our buttons better with this article.

💡 As buttons are a strong indicator for getting active, it might be a good choice to always place a button in your flow. Check out more of our best practices here.

Multiple and Picture Choice

Our Multiple Choice and Picture Choice blocks are the most popular input blocks. They are crucial to navigate through your flow, as an input value is usually needed to proceed further.

By using these blocks, you can already unlock different navigation patterns than just moving straight further, according to the answers of your users. The term in use here is conditional logic, and you can find out more about that here.

🔎 You can learn more about how to unleash all the potential of the Multiple Choice block here and of the Picture Choice block here.

Loader

The Loader is another element, designed to navigate through your flow and improving the user experience. You can use the tool to redirect to different pages or to a different URL. This feature gives users a sense of ongoing backend processing for their submissions, needless to say, this is in your interest.

🔎 Learn more about the Loader here.

Links

Another block to enable your users to navigate through your flow in a meaningful way. You can insert links to redirect to different, significant pages of your flow. For example, to the start. But any other page can also be mentioned. Learn how below.

🔎 Find out more about Links here.

Scroll to Top / Scroll to Block

The Scroll to Top and Scroll to Block navigation options let you control where the page scrolls when a visitor clicks a Universal Button or Link Button. This is useful for guiding attention, improving navigation on longer pages, or letting users quickly jump back to the top.

Setting it up

In the button's Navigation settings, open the action dropdown and choose either Scroll to Top or Scroll to Block.


Scroll to Top

Scrolls the visitor back to the top of the current page. After selecting it, you only need to choose one thing:

  • Scroll behaviorSmooth (animated scroll) or Instant (jumps immediately)


Scroll to Block

Scrolls the visitor to a specific block on the current page. You have three options to configure:

  • Target block — Select which block on the page to scroll to

  • Scroll behaviorSmooth or Instant

  • Block alignment — Whether to align the viewport to the Top, Center, or Bottom of the target block

💡 Note: Scroll to Block only works within the same page — you cannot scroll to a block on a different page.

That's all there is to it! Once configured, clicking the button will scroll the visitor exactly where you want them.


# Navigation

Another useful tool is the navigation via hashtag. An important prerequisite for this is to rename your pages. Afterward, you can directly jump to any page, simply by adding it with a hashtag to the URL.

If you view your flow in your browser, you will always see the name of your page at the end of the URL. A good example of this useful tool is already applied in our Links block, as you can see above.

❗ It's not possible to not show the #page in the URL in a stand-alone flow, since this is how it navigates.

Did this answer your question?