Triggering the Resource Center

Leverage the use of the Resource Center by triggering it in the right place, and at the right time.

Resource Center Triggering

This section will describe the set of options that can be used to trigger the Resource Center within your application

These options will define how will the Resource Center widget be launched.

Options 

1. When the user clicks the beacon (default)

If the user is evaluated as eligible to see the Resource Center, the widget can be launched after clicking on the displayed beacon. You can specify the eligible users based on page, domain, and audience targeting as described in this article.

2. When the user clicks on a specific element in my app 

You can require a certain element to be clicked on your web app for the widget to be shown. Once selected, you can specify the CSS selector for the target element in Userpilot. 

What is a CSS selector?

Elements are simply boxes on the page identified by its HTML and CSS, Userpilot identifies the element you have selected using CSS Selectors: these are used to select and target the HTML content on your web app. There are a wide variety of CSS selectors available, allowing for fine-grained precision when selecting elements to style; CSS selectors select HTML elements according to its id, class, type, attribute, etc.

You can find the HTML content and related CSS selectors are used as a particular element by simply right-clicking and inspecting that element. We recommend asking your developers if you're missing information here.

3. Manually through Javascript

This will show a script that can be used to trigger the widget manually. 

Pro tip: Triggering the widget manually through a Javascript can be a great way to test if the Resource Center look & feel as expected without publishing it live to your end-users.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.