How to ensure element selectors configured in Gainsight are resilient against UI changes?
Example use case for the question:
- Main menu - the tool identifies selector as nth-child(2) = this will cause the tracking to fail if we add another menu before this
- Safer would be using a combination of element name/id attributes. Any way to config the tool to prefer a selector or have to provide it manually?
Our tool prefers a unique selector on the page being used in the following order of preference:
- Element id
- Element tag name
- Href for an element from type a
- What it means is, we will prefer to have a selector with id if it is available.
- In case you are aware of any other attributes on an element that can be unique, it is possible to add them to our SDK settings (Settings > SDK Settings > DOM Elements) so our selector detector will use them as well.
Pages with unique URLs to a test? Can I use a * in the middle of a URL and at the end?
Yes, it works.
Is a search box trackable?
Yes, using Custom Events. You'd need a developer to help you with this, it is that 3rd option of tracking mentioned in the following:
- Tag UI element: clicks, buttons, etc
- URL: Link clicks, page views, etc
- Custom Events for tracking specific flows. Share this document on using Custom Event API with your developer and they will know how to make it happen.
Are radio buttons trackable?
Yes, trackable using Tag UI Elements.
How do you tag/track a model?
You need to have a CSS Selector inside a Model and you will find they have a class, which makes the selector is more robust.
If I don’t name our modules/features with a more robust naming convention, will the customer success team see how they are nested in Gainsight CS? I do anticipate the CS team looking at an individual level.
CS has a productized connector which they are using to pull PX Usage data and currently it is available at a Feature level, which CS teams usually care for. If they want it at a Module Level, they can aggregate it within CS using a couple of rules. Following would be our recommendation
- In PX, build your Product Tree and Hierarchy as needed
- [some work needed by engineering to send the modules and features]
- In CS, Use filters to get at the data you need.
Can we get historical matches if a feature is created after a few months?
Yes, using backfill feature. This will fill in all usage data from the date of PX tag installation.