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.
Fullstory Elements let you pick a named part of your site, such as a Checkout button, anywhere the Guides and Surveys editor asks for an element. You choose the Element by name instead of writing or capturing a CSS selector.
In this article:
- What are Fullstory Elements
- Before you start
- Where you can use Elements
- Pick an Element
- What happens after you publish
- Tips
- Troubleshooting
What are Fullstory Elements
Fullstory Elements are named, reusable definitions of parts of your site or app, such as a Checkout button, a search bar, or a navigation menu. Each Element is defined once in Fullstory under Settings > Elements. It has a name, an optional description and role, and a selector for each platform it appears on: a CSS selector for web, and iOS or Android selectors for mobile apps. To learn how to create Elements, see Naming Elements in Fullstory.
In Guides and Surveys, you can pick an Element by name anywhere your content needs to point at, sit inside, or react to something on the page.
Why use Elements instead of CSS selectors
Elements keep your content connected to the same definitions your team uses for analytics:
- One definition, used everywhere: Your tours, smart tips, and surveys use the same Elements your team already uses in Fullstory analytics.
- Fewer broken guides after UI changes: When someone updates an Element's selector in Fullstory, content that uses it follows the change. You don't have to find and edit each guide.
-
Readable for everyone: Authors see "Checkout button" instead of
div.cart-footer > button:nth-of-type(2). - The right selector for each platform: On web, content uses the Element's CSS selector. In mobile apps, it uses the iOS or Android selector.
Before you start
Check the following before you pick Elements in the editor:
Prerequisites:
- Your Fullstory org has at least one Element.
- To create or edit Elements, you have a Fullstory role that can configure Elements. See Naming Elements in Fullstory.
Where you can use Elements
Any field in the editor that asks for an element can use a Fullstory Element. The tables below list where those fields appear and what the Element does in each place.
Positioning: attach content to an Element
Use an Element to decide where content appears on the page:
| Content | Where to set it | What happens |
|---|---|---|
| Tour step (pointer) | Step > Position by > Element | The pointer points at the Element. You can turn on highlight. |
| Smart tip | Tip > Position by > Element | The tip and its hotspot sit on the Element. You can turn on highlight. |
| Banner, checklist, or survey (embedded) | Settings > Layout > Position by > Element | The content is embedded inside the Element. |
| Tour or checklist launcher button | Settings > Aligned to element > Select by > Element | The button is placed next to the Element instead of in a corner of the page. |
Note: For Aligned to element, the target element on your page must have a CSS position other than static.
Targeting and triggers: show content based on an Element
Use an Element in targeting rules and triggers to decide when content appears. For the full list of rules, see Guides and Surveys - Page and Audience Targeting and Guides and Surveys - Triggering Content.
| Rule or trigger | Where to set it | What happens |
|---|---|---|
| Element exists or Element doesn't exist | Targeting rules | Content shows only when the Element is (or isn't) on the page. |
| Element text contains or Element attribute contains | Targeting rules. Pick the Element, then type the text or attribute. | Content shows only when the Element's text or attribute matches. |
| User clicks on element (tour start) | Tour triggering > Start on specific user action or page event | The tour starts when the user clicks the Element. |
| Element appears (step) | Step > page event | The step opens when the Element appears on the page. |
| User clicks on element (checklist item) | Checklist item | The item is marked complete when the user clicks the Element. |
| Element condition (step or checklist item) | Add an element condition > Select by > Element | The condition passes when the Element is on the page. |
Actions: interact with an Element
Automatic tour steps can act on an Element for the user:
| Step type | What happens |
|---|---|
| Page action: Click | The step clicks the Element. |
| Page action: Fill | The step types a value into the Element (an input field). |
| Trigger event: JavaScript event | The event fires on the Element. If you leave the Element empty, it fires on the window. |
Pick an Element
Every element field has a switch with two options: Element and CSS Selector. New fields start on Element and show the placeholder Select element.
- Click the element field to open the Element picker.
- Find the Element you need:
- Browse: Elements are grouped by role. Elements without a role are listed under All Elements. Your current choice is pinned at the top under Selected.
- Search: Type part of a name, description, role, selector, or property. If nothing matches, the picker shows No matches for "…". The search clears when you close the picker.
- Hover over a row, or move to it with the arrow keys, to see its details in the right pane: name, description, mapped element, selector, properties, and who created and last updated it.
- Click the Element, or press Enter. The picker closes and the field shows the Element's name.
- Save your content.
When you reopen the content, the switch is on Element and the field shows the Element's name, not its selector.
Keyboard shortcuts
You can open and use the picker without a mouse:
| Key | Action |
|---|---|
| Enter or ↓ (field focused) | Open the picker |
| ↑ or ↓ | Move the highlight and preview details |
| Enter | Select the highlighted Element |
| Esc | Close the picker and return focus to the field |
Create a new Element
If the Element you need doesn't exist yet, click Create Element in the picker. Fullstory Elements settings open in a new tab. Create the Element there, then come back to the editor and reopen the picker. If the new Element is not listed, reload the editor.
Edit an Element
To change an Element's definition, highlight it in the picker and click Edit. The Element opens in Fullstory settings in a new tab. Your changes apply to every tour, smart tip, and survey that uses the Element.
Use a CSS selector instead
Each field uses either an Element or a CSS selector, never both. To use a CSS selector:
- Set the switch to CSS Selector.
- Type a selector, or use the crosshair to pick an element on the page. For details, see Guides and Surveys - Finding Element Selectors on Your Website.
Switching between Element and CSS Selector clears the previous value. On pointer steps, Filter element and element data options are only available in CSS Selector mode. They're cleared when you switch back to Element.
What happens after you publish
Published content that uses an Element stays linked to it in Fullstory. This is how that content behaves as Elements change:
- Your content keeps up with changes in Fullstory: When an Element is renamed or its selector changes in Fullstory, Guides and Surveys picks up the change automatically. The editor shows the new name, and published content uses the new selector.
- Each platform gets its own selector: Web visitors get the Element's CSS selector. In mobile apps, content uses the iOS or Android selector.
- Archived Elements keep working: If an Element is archived in Fullstory, content that uses it keeps using its last known selector, so nothing moves or disappears unexpectedly. Replace it with an active Element or a CSS selector when you can.
- Content won't attach to the wrong element: If an Element has been deleted, or has no selector for the visitor's platform, your content isn't attached to some other element on the page. A pointer step falls back to a slideout, and embedded content is not shown.
- Existing content isn't affected: Content saved with a CSS selector opens in CSS Selector mode and works as before. There's nothing to migrate. Switch a field to Element whenever it suits you.
Tips
A few habits keep Elements reliable across your content:
- Use Elements for UI that changes often or appears in several guides.
- Give Elements clear names, short descriptions, and a role. The picker searches all of these and groups the list by role.
- Make sure the Element's web selector matches the element you mean on every page where your content runs.
- Before you archive or change an Element in Fullstory, check with your Guides and Surveys authors. The change applies to all content that uses the Element.
Troubleshooting
Use the table below to resolve common issues with the Element picker. For content that isn't showing for other reasons, see Guides and Surveys - Troubleshooting.
| What you see | What to do |
|---|---|
| The picker is empty. | Your org has no Elements yet. Click Create Element. |
| The picker shows an error. | The list couldn't load. Click Try again. Published content isn't affected. |
| A new Element is missing from the list. | Close and reopen the picker. If it's still missing, reload the editor. |
| Content doesn't appear where expected. | Click Edit on the Element and check that its web selector matches the element on that page. For Aligned to element, check that the element isn't position: static. |