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.
Guides and Surveys lets you target content to end users based on Fullstory segments. Instead of rebuilding audience definitions inside Guides and Surveys, you can reuse a segment you've already defined in Fullstory and target a guide, survey, banner, or checklist directly against it.
This works best for historical or attribute-based cohorts—for example, suppressing a survey for users who recently saw it, or targeting an onboarding campaign by days since registration (see When to use Fullstory segment targeting). Fullstory segment membership is not evaluated in realtime: it refreshes periodically rather than in the current session (see Segment timing and freshness). If you need to react to same-session behavior, such as a rage click or pages visited during the current visit, use a Tag value or User properties condition instead.
In this article:
- How to target using a Fullstory segment
- When to use Fullstory segment targeting
- Segment timing and freshness
- Fullstory segments vs. Guides and Surveys user segments
- Frequently Asked Questions
How to target using a Fullstory segment
A Fullstory segment condition is available alongside the other audience conditions for any guide, survey, banner, or checklist.
- Open the Settings for your guide, survey, banner, or checklist.
- In the Page & Audience Targeting section, click Only certain pages and user segments.
- Under the "...of the following conditions match" area, change the condition to Fullstory Segment.
- Select the Fullstory segment you want to target from the list. Guides and Surveys lists the segments defined in your Fullstory org.
When to use Fullstory segment targeting
Fullstory segment targeting is most useful when you want to reuse an audience definition you've already built in Fullstory instead of maintaining the same logic separately in Guides and Surveys. It works well for historical or attribute-based cohorts, such as:
- Showing a survey only to active, paying users who haven't seen the same survey in the last 30 days.
- Targeting an onboarding campaign to new users based on days since registration.
- Triggering a quarterly NPS survey to everyone who belongs to a specific segment.
- Sending a reminder to users who started a checklist but haven't finished it within a set number of days.
Note: Fullstory segment membership is not evaluated in realtime—see Segment timing and freshness below. For same-session reactions, such as targeting a user who rage-clicked or visited three pages in the current session, use a Tag value or User properties condition set through in-session Fullstory user properties instead.
Segment timing and freshness
Fullstory segment definitions become available to Guides and Surveys as soon as you create or update them in Fullstory. Segment membership—the list of users who currently match a segment—works differently:
- Membership refreshes periodically, on a default interval of up to 4 hours, rather than in realtime.
- Refreshes are scheduled outside peak business hours, so a change to who matches a segment during the business day may not be reflected in Guides and Surveys targeting until the next scheduled refresh.
- Private segments aren't available for targeting. Only non-private Fullstory segments sync to Guides and Surveys.
Note: Fullstory segment targeting is not realtime or in-session. If your use case depends on reacting to behavior within the current session, use Fullstory user properties or tags instead.
Fullstory segments vs. Guides and Surveys user segments
Fullstory segments are distinct from Guides and Surveys user segments, even though both are used to group and target users.
- Fullstory segments: defined in Fullstory using session and analytics data, and reused in Guides and Surveys through the Segment condition described in this article.
- Guides and Surveys user segments: defined directly in Guides and Surveys from tag and user property conditions, and managed under Users > Segments.
If you already maintain a Fullstory segment that captures the audience you need, target it directly rather than recreating the same logic as a Guides and Surveys user segment.
Frequently Asked Questions
What happens if Fullstory can't evaluate a user's segment membership?
If Fullstory is unable to determine whether a user currently belongs to a targeted segment, the Fullstory Segment condition resolves to "not a match," and the content won't show for that user.
Can I target a private Fullstory segment?
No. Private segments aren't shared with Guides and Surveys. To target a segment, make sure it isn't marked private in Fullstory.
Why isn't Fullstory segment targeting realtime?
Evaluating segment membership requires querying Fullstory's analytics data for every active user, which isn't feasible to do in realtime at scale. Instead, Guides and Surveys periodically recomputes segment membership—by default at least every 4 hours—which covers most targeting use cases while keeping the underlying system efficient. For use cases that need to react within the current session, use Fullstory user properties or tags instead.