Getting Started with FullStory

Welcome to the FullStory family – we’re glad to have you join us in the movement to make the web more user-friendly!

The first step toward recording all in-browser interactions and making them available for pixel-perfect playback is deploying FullStory’s JavaScript snippet. 

A couple of notes about the recording script:

  • It’s super small, asynchronous and designed to be unnoticeable to your users. You can read more about the negligible performance impact of FullStory in this article.
  • No need to instrument any elements in your application or site. Once the FullStory script loads, it records all in-browser interactions and mutations. Don’t fret about how to record that particular “submit” button – if it’s in the page, FullStory sees it, records it, and makes it available to search.

You can find the script by clicking on Settings > General

Simply paste the snippet into the <HEAD> element either via your Content Management System (CMS) or directly into your application’s code. Recordings will appear in your dashboard within a few minutes, as long as users are visiting your site and navigating. (If you want to use GTM to install, read more here: Google Tag Manager for installation)

While you’re installing, you’ll likely want to think about excluding some elements. FullStory allows you to block sensitive data from being recorded through a construct called “Excluded Elements.” It allows you to identify the CSS selectors of data you want to keep private.

The privacy of your customer data is a shared responsibility. FullStory diligently ensures that your customer data is securely stored and accessible only to you. In addition, we provide you a tool to easily exclude sensitive customer information.

Within Settings you’ll notice an area called Recording & Exclusions. You can enter CSS selectors there to block any data from those form elements from ever being captured. Excluded data never leaves your customers browser. Which is exactly what you want. You can also use Inspect Mode to quickly add excluded elements.

Our blocked element syntax supports a subset of CSS. We currently support:

#idselectors
  .classselectors
  tagname
  tagname[attribute=foo]
  parent>child

Invite your team

FullStory is better with friends. While you wait for sessions to roll in, go ahead and invite your teammates

Watch some sessions

As sessions start recording, you’ll see them populate in the main FullStory screen. The green “Online” icon indicates that the user may still be online and the session is still recording. The blue icon with the date and time indicates the session is complete (we close sessions after 30 minutes of inactivity).


Session Recording Still in Progress

Session Recording is Complete

Once you've clicked on a session, the icon will no longer be filled in with color, indicating that it has already been watched. The watched indicator is at a user level, so your teammates will not see a session marked as watched if they haven't watched it using their own login. 

Image title


FullStory provides a mechanism to pass in non-session-specific variables via our API. Common use cases include unique identifiers (e.g. application ID “friendly” names) and data about things like subscription level, items in cart, and tools integrated into your platform.

Customize your data

There are 2 different methods to add custom data to FullStory:

  • FS.Identify– supports the passing of a unique identifier like application ID (optional), email address and an optional “friendly” display name. Learn more about installation here.


You can find this optional code snippet by clicking on Settings > General


Take advantage of integrations

FullStory offers native integrations with leading platforms including Desk.com, Help Scout, UserVoice, Zendesk, and Olark.

These integrations place a link to the FullStory recording into your help desk platform as an attachment to the ticket, so your customer service agents can see what happened before, during and after a ticket was submitted.

You can also integrate with communication tools such as Slack, Hipchat, and Trello or project management tools like Bugsnag, JIRA, or Mixpanel.

Every integration gets your current tools tied into FullStory so you always have a FullStory session to settle all bets. 

Need something we haven't built? Roll your own with FS.getCurrentSessionURL().


OmniSearch, for the win!

Watching all sessions is nearly impossible, not to mention has very little analytical value. Try FullStory’s powerful search capabilities to narrow down recordings to only those relevant to your query.

With OmniSearch, you just type your thoughts into the search box and we help you get where you're going. 

Here are some possibilities with search:

  • Look at user-centric variables like location, operating system, browser, and device, or search based on any of the custom variables you’ve pulled into FullStory.
  • Search by pages visited, path, query parameter, etc.
  • Search by any element in a page and how a user interacted with it, like form fields changed, or objects clicked.

When you build a search you’d like to repeat in the future, just click the “Save Segment...” button to add this search to “Your Segments.” You can revisit your segments later, and even share them with the rest of your team.

To learn more about Search and become a Search Star, take a look at our detailed user guide Getting Acquainted with Search.


Can’t find what you’re looking for?

The FullStory team awaits your every question.

Contact Us