Guides and Surveys - Fullstory User Properties

If you would like to evaluate Guides and Surveys, please reach out to a member of your account team.

Who can use this feature?
- Part of Guides and Surveys, an add-on for Business, Advanced, and Enterprise plans.
- Requires an Admin, Architect, or Standard role to configure.

Guides and Surveys is in active development. Product functionality and documentation may change without notice.

With Guides and Surveys, user properties that you send to Fullstory using the browser API will show up in Guides and Surveys as user tag values. You can filter for tag values both when targeting for user-based conditions on a specific guide or survey and when creating a Guides and Surveys user segment.

In this article:

Fullstory user properties in settings for guides and surveys

You can filter for Fullstory user properties directly in the settings for a specific guide or survey. To target users based on a Fullstory user property:

In the image above, carMake is a Fullstory user property, which shows up in Guides and Surveys as a Tag value.
  1. Open the Settings for your guide or survey.
  2. In the Page & Audience Targeting section, click Only certain pages and user segments.
  3. Under the "...of the following conditions match" area, make the following changes: 
    • Change the condition to Tag value.
    • Tag name: set the Fullstory user property name that you want to match against.
    • Operator: choose an operator, e.g. is, contains, etc.
    • Tag content: set the Fullstory user property value that you're comparing.

Fullstory user properties in Guides and Surveys user segments

If you want to apply the same Fullstory user property conditions across multiple guides and surveys, consider creating a Guides and Surveys user segment instead. To filter for Fullstory user properties when creating a user segment:

  1. From within Guides and Surveys, click Users on the left hand menu.
  2. Click Segments.

    Note: While they share the same name, Guides and Surveys user segments are completely separate from Fullstory segments.
  3. Click + Add Segment.
  4. Provide a Segment name and Description
  5. Under Conditions,
    • Change the condition to Tag value.
    • Tag name: set the Fullstory user property name that you want to match against.
    • Operator: choose an operator, e.g. is, contains, etc.
    • Tag content: set the Fullstory user property value that you're comparing.
  6. Click Create.

Note: When you create your segment, Guides and Surveys may provide a message telling you how many users match this segment. However, when you view the segment in the list of segments, you may notice a message that says "Waiting for segmentation" along with a value of 0 for Users This Month. This is because Guides and Surveys syncs user property data with Fullstory every 5 minutes. You can see the Last Segmented timestamp above the list of segments. Once the next user property sync completes, the Users This Month value will be updated.

Once you've created a segment, you can target it as a user-based condition for any guide or survey you create.

Frequently Asked Questions

Can I use date values in tag conditions?

If a tag condition uses the higher than or lower than operator and either the condition value or the tag value is in ISO 8601 format (YYYY-MM-DD), the system performs a string comparison. For properly formatted ISO 8601 dates, higher than and lower than effectively function as "after" and "before."

For example, if a user has a tag trialEndDate with a value of 2026-03-15, you can create a condition where Tag name is trialEndDate, the operator is lower than, and Tag content is 2026-02-28 to target users whose trial ends before February 28, 2026.


Was this article helpful?

Got Questions?

Get in touch with a Fullstory rep, ask the community or check out our developer documentation.