1) Can I trigger an engagement when a certain feature is used OR not used?
Yes. Navigate to Create Engagement > Audience > Choose Product Mapper from list of Trigger Rules available on the right > Choose Feature from the dropdown available > Set your criteria.
2) Can I stylize the engagements according to our branding?
Yes. Using WYSIWYG editor or CSS Code editor.
3) Can I preview the engagement before triggering?
Yes. By using Edit Guide In-App OR by clicking on Preview button.
4) How do I test engagements?
You can do it in either of the following ways:
- If you have PX Tag installed on your non-production environment, you can create and test engagements on the Non-Prod environment (OR)
- Use Preview by navigating to Engagements > Editor > Edit in-app > Click on Preview (this will launch the engagement on your web app only as a Preview to you) (OR)
- Create a Segment. Add Internal users who will be testing the engagement. Navigate to Create Engagement > Audience > Choose ‘Segment’ from the list of Trigger Rules available on the right > Choose your Test User Segment > Trigger the engagement with other criteria in place only to Test Users; (OR)
- Navigate to Create Engagement > Audience > Choose ‘User’ from the list of Trigger Rules available on the right > Choose email attribute from the dropdown available > Set your email id > Trigger the engagement only to yourself.
5) Once I set up with Audience Rules for my engagements, what’s the importance of Qualification Scope?
Audience defines “Who” to target, Editor “What" to target, and Qualification Scope “When” to target. For example:
- Every time a user logs in to your Web app.
- Every time user triggers the engagement criteria.
- Using a certain feature or only once in user’s lifetime.
6) Do you have any documentation explaining how to apply Audience Rules? I think Users, URL, Product Mapper, and Segments are the popular ones.
It's purely depends on the use case. See the following examples:
Users: You can use this rule in Audience when you want to target specific set of users based on their user attributes. For example, User ID, Email ID, Role, etc.
URL: This rule should be used when one wants to trigger engagements on certain pages/ URL’s. “How many times” can be defined under Qualification Scope like every time, only once, and once per visit.
Product Mapper: This rule should be used when one wants to trigger engagements upon certain feature usage by end users. For example, Trigger Engagement XX when feature AB is used/ not used.
Segments: This rule should be used mostly for targeting a specific cohort/ user group. For example, One has created a Segment for “Internal Users” or for “Test Users” or customers who were given training on a certain date. You can then target engagements to this group of users only.
7) In Qualification Scope, what would “Show 3 times every 2 months mean”?
If the Audience Criteria is met, Show/Attempt Once every 2 months for up to 3 times 'if' engagement is 'not completed' and then stop/die. Will not show a 2nd or third time 'if completed' on 1st or 2nd time.
8) If there are multiple engagements triggered for a user, where do surveys fall in prioritization?
9) How soon can I view an engagement after its launched?
All engagements are available 30 seconds after they are launched. You can view the engagement if you are included in the audience of the engagement and when you are qualified to view it.
10) When pausing a Guide engagement, the badge stays out there for a while, although clicking it does nothing. When will the badge disappear after the pause?
When you are pausing an engagement, the badge will be removed from the browser after 5 and a half minutes typically. This is because of a sync mechanism from the client every 5 minutes.
11) In a Guide engagement, which of the following is considered a view: seeing a hotspot or clicking a hotspot?
Seeing a hotspot is considered a view. However for a Badge, that is triggered by click and audience is everyone, a view is counted only when the user clicks on it.
12) Does the 'Skip Tour' button perform the same action as that of 'X' button? Does the user view the engagement after he clicks either of the buttons?
Yes, the 'Skip Tour' button performs the same action as that of 'X' button. The user will see the engagement again if the qualification scope is configured for multiple views.