If you would like to evaluate Guides and Surveys, please reach out to a member of your account team or fill out this form to be connected with a Fullstory team member.
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
- Fullstory user properties in Guides and Surveys user segments
- Fullstory user properties on the User Profile
- Frequently Asked Questions
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:
Note: A Fullstory user property becomes available for Tag value targeting through one of two methods:
-
Set in the browser before your content loads: Properties set client-side (for example, with
FS('setProperties')) before your Guides and Surveys content loads are available for targeting immediately, and aren't limited to properties used in targeting rules. -
Synced from Fullstory: Other user properties sync to Guides and Surveys approximately every five minutes and are available only if they're also used in the content's targeting rules. The reserved
displayNameandemailproperties aren't available through this method—set them in the browser before your content loads if you want to target on them.
carMake is a Fullstory user property, which shows up in Guides and Surveys as a Tag value.- Open the Settings for your guide or survey.
- In the Page & Audience Targeting section, click Only certain pages and user segments.
- 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.
Note: If you already have a Fullstory segment that captures the audience you want to target, you can target that segment directly instead of recreating its logic as individual Tag value conditions. See Guides and Surveys: Target Fullstory Segments for how to use the Fullstory Segment condition and how its timing differs from Tag value targeting.
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:
- From within Guides and Surveys, click Users on the left hand menu.
-
Click Segments.
Note: While they share the same name, Guides and Surveys user segments are completely separate from Fullstory segments. - Click + Add Segment.
- Provide a Segment name and Description
- 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.
- 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. The Users This Month count is refreshed by a periodic sync of user property data with Fullstory that runs approximately every 5 minutes—this only affects how quickly the count updates, not how quickly a Tag value condition can match a user. You can see the Last Segmented timestamp above the list of segments. Once the next 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.
Fullstory user properties on the User Profile
In Guides and Surveys, you can view a user's Fullstory user properties directly from their profile. To see them, navigate to Users in the left hand menu, select a user, and then click the User Tags & Properties tab.
The Fullstory User Properties section at the top of the tab displays all properties that Fullstory has received for that user. These are the same properties you send to Fullstory using the browser API, and the same ones available as tag values for targeting and segments.
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.