Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Use Cases

Pass Appcues Flow Events to Fullstory to See User Interactions

Learn how to gain additional insights into user behavior, stay ahead of flow errors, and optimize experiences for even better performance.

Written by RJ Bayani

Updated at December 11th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • FAQs
  • Support
  • Installation & Developers
    Installing Appcues Web API & Data Extras Troubleshooting Installing Appcues Mobile
  • Web Experiences
    Studio Building Web Experiences Customization & Styling FAQ Targeting Troubleshooting Use Cases
  • Mobile Experiences
    Building Mobile Experiences Installation & Overview Troubleshooting Mobile Analytics & Integrations
  • Account Management
    Subscription Users & Data
  • Analytics
    Experience and Event Analytics Data
  • Best Practices
    Product-led Growth Pro Tips Best Practices Use Cases
  • Integrations
    Integration Documents Extras Use Cases
  • System Status
    System Status & Incidents
  • Workflows
    Use Cases Building & Configuration Workflow Analytics and Integrations
+ More

Get a more complete picture of how users are interacting with your in-product experiences by passing events directly to Fullstory. This is a great way to gain additional insights into user behavior, stay ahead of flow errors, and optimize experiences for even better performance. 

What you need:

  • Appcues account (Essentials, Growth, or Enterprise)
  • Fullstory account

In this example, we’ll focus on watching users interact with a specific flow, but you can also do this same process for Click-to-Track (CTT) events (which can be great for seeing how users interact with specific and new features). 

 

Build Guide

Step 1: Make sure your Fullstory account is enabled

Before starting this workflow, you'll need a Fullstory account and their JS snippet installed in your app to utilize the Appcues integration.

Step 2: Enable the Appcues <> Fullstory integration

Login to the Appcues Studio to enable the integration. For help getting it set up, review our installation guide.

Step 3: In Fullstory, search for users who interacted with a Flow

In our example, we’re looking to see how users interacted with a flow announcing Screen Capture for our Appcues Mobile product.

We can see the Flow Event here in Events Explorer, which provides us with some basic learnings about how users are interacting with the flow. 

Next, head to Fullstory and open the Segments area. We’ll search for the flow name and look to learn more about those users who interacted with the flow–the top result. 

Step 4: Navigate the list of users

Scroll down the page and you’ll see that Fullstory has automatically generated a list of all of the users exposed to the flow.

Select any of the items in the “Session Playlist” to watch an individual session.

Step 5: Watch the section of each session where the Flow appeared

Each session will immediately skip ahead to right before that event occurred so it’s easy to watch only what’s relevant.

Step 6: Cycle through all sessions that include those Flow interactions 

You can quickly review all of the sessions by clicking on the arrow in the top right-hand corner. This will provide you with a great deal of learnings within a couple of minutes! 

That’s it! Restart the process for any flow you’d like to watch users start, interact, skip, and complete flows to really get a sense of what they are doing in-product. 

Step 7: Optimize your Appcues experiences based on what you learn

Watching your users interact with your flows will give you great insight into how they are performing. Complete the feedback loop by taking those learnings and making changes to enhance those experiences further.

Here are some things we’ve spotted in our own account following this workflow and how we’ve made changes after watching users' interactions in Fullstory: 

  1. We’ve noticed users highlighting or slowing their cursor downs on bits of copy, indicating the wording might be confusing -> leading us to make tweaks to simplify it.
     
  2. We’ve seen users hover or try to click on an image that wasn't clickable -> leading us to in some cases remove the image and in others link the image.
     
  3. And (an embarrassing, but true admittance), we’ve shipped a new feature with a flow describing it only to recognize that we made an error in deployment and users were getting a 404 page -> leading us to an immediate fix (we all make mistakes, right?).
     

Happy Building!

 

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Fullstory Integration
DON'T TAKE OUR WORD FOR IT

Start building with Appcues for free

Try before you buy
No credit card required
Support included
Start building for freeBook a demo
or take an interactive tour
Appcues logo

Product

In-app messaging
Email
Push notifications
Workflows
Data
How it works
Pricing
What's new

Use cases

Onboarding
Free-trial conversion
Feature adoption
Feedback
Support

Integrations

Why connect
All integrations
All workflows

Company

About
Careers
HIRING
Why Appcues
Teams
Customers

Support

Request a demo
Start free trial
Developer Docs
Help Center
Customer Success
Contact

Resources

Product Adoption Academy
Courses
Workshops
Templates
Examples
Made with Appcues
The Appcues Blog
PLG Collective
Product-led Experience Report
The Product Experience Playbook
The Product-Led Growth Flywheel
© 2025 Appcues. All rights reserved.
SecurityTerms of ServiceWebsite Terms of UsePrivacy PolicyCookie Preferences
Expand