Extension application settings

Last updated:

Applications settings are accessed from subscription settings. Navigate to Settings > Subscription Settings from the bottom of the left-side menu and open the Applications tab. Then, find and open your application from the Applications list.

Depending on your subscription, an application's settings consists of the following tabs:

  • App Details, where you can view and configure basic settings for your application.
  • Raw Events, which displays a list of raw events coming into Pendo in a table view.
  • Localization Settings, where you can enable and configure support for multiple languages in your guides and Resource Center.
  • Tagging & Guide Settings, where you configure how the Visual Design Studio works for tagging and guide creation.

App Details

Display name The name you see for the application throughout Pendo. A subscription Admin can change this at any time.
Platform The type of application upon which Pendo is deployed: WebMobile, or Extension.
Extension platform type

The specific extension platform type. This can be either: SalesforceWorkdayOutreach or Other. For more information, see Add extension apps.

Websites

The domains associated with the application that you want to collect data and deploy guides on. Select Edit to add more or delete existing ones.

Selective URLs

Regular expressions used to create rules for establishing an app connection through the Pendo Launcher. This provides the ability to narrow down usage data based on specific app URLs. To configure selective URLs for your application, contact Pendo Support.

API Key

The code that identifies data sent to Pendo associated with this specific application within the subscription.

Show guide to anonymous visitors Whether anonymous visitors are included within guide segmentation. By default, this setting is turned off. If you change this setting, you must also reset the segment for each pre-existing guide that you want this change to impact. For more information, see Anonymous visitors.
Enable shadow root Prevents any custom agent implementations from affecting guides by isolating extension app guides and Resource Centers into a shadow root DOM item.
Text Capture From Events Allows Pendo to collect innerHTML text as part of automatically captured Click Events. This setting supersedes the Text capture in web applications setting at the subscription level.
Prefer BroadcastChannel for multi-frame support

Controls how the agent tries to communicate between frames. Turn off this setting in cases where the frame origins don’t match.

Use visibility API instead of unload event

To maintain compatibility with Google Chrome, removes the use of the unload browser event from Pendo.

This setting sends events during visibility changes to "hidden", which provides a more optimized approach to event handling during navigation. This improves navigation event handling in your app by opting for the "visibilitychange" event over the default "unload" event.

Attempt click capture on removed elements In some applications, Pendo can’t capture the clicks for elements that are removed before the browser’s Click Event. This setting adds functionality to intercept the remove method and generate the lost click.
Pendo Suggested Pages Generate recommended Page rules based on URLs from your event data. Use this feature to accept or delete the recommended tags to quickly create Pages in Pendo that represent URLs that your visitors have seen in the last five days. If turned on for any application, the Suggested Pages table is visible to the entire subscription.
Sibling Selectors Allow the Pendo user to tie one Feature rule to another UI element in their application.
Page Event properties Allow the ability to create Page tags when the URL isn't changing. This setting could allow you to collect personal data and send it to Pendo. Please be mindful of your company's policies regarding personal data collection and processing. For questions, contact Pendo Support.
Collect Page titles Add the <title> value of each webpage to the URL collected by the agent. The title is added as a query parameter called pendo_document_title. For example, if the title of www.example.com/home is "Welcome Page", the URL is captured as https://www.example.com/home?_pendo_document_title=Welcome+Page.

Raw Events

Pendo captures and displays user interactions with your application as raw “events” in the Events table in this tab. For more information, see Pendo data processing and visibility. The table includes the following information:

  • Browser Time. The timestamp of the raw event as captured by the visitor's browser.
  • Agent Version. The version of the Pendo agent as captured by the visitor's browser. This can be checked against your current agent version in the Agent Settings tab.
  • Visitor. The Visitor ID of the end user who created the event.
  • Account. The Account ID of the account that the visitor belongs to at the time the raw event was captured.
  • Event. The type of raw event, such as clickload, or focus.
  • Remote IP. The public IP address from which the raw event originates.
  • Browser / OS. The browser and operating system from which the raw event originates.
  • URL. The address of the page in your application from which the raw event originates.
  • App. The application from which the raw event originates.

Data Sync customers can access the raw events that Pendo collects by sending the data to a data lake or warehouse, which you can then send to various BI tools. For more information, see Overview of Pendo Data Sync.

Localization Settings

The Enable Localization setting allows you to support multiple languages for the guides and Resource Center of the application, and to display these in the language of your visitors’ preferences.

Tagging & Guide Settings

This is where you configure how the Visual Design studio works for tagging and guide creation. For more information about the settings in this tab of application settings, see Configure the Visual Design Studio for guides and tagging.

Basic Settings

Basic settings change the launch behavior of the Visual Design Studio. These include:

  • Disable Designer Launch URL Token. This is a debug setting, typically used by Pendo Support. It turns off the Launch URL token and opens a new tab with the Visual Design Studio using the window.opener method.
  • Prevent Access to Guides Code Block. Turns off access to custom code block elements on guides in your application. You must contact your Pendo representative to update this setting.
  • Disable Guide Designer Keyboard Shortcut. Turns off the standard keyboard shortcut (Alt + Shift on Windows or Option + Shift on a Mac) for launching the Visual Design Studio.

For more information, see Configure the Visual Design Studio for guides and tagging.

Custom HTML attributes

You can add custom HTML attributes and then enable automatic tagging so that Features are automatically created when elements associated with your custom HTML attributes are clicked. The relevant settings for custom HTML attributes are:

  • Collect custom HTML attributes. Add custom HTML attributes for Pendo to record in raw events, in addition to the default attributes that are already collected. For more information, see Custom HTML attributes.
  • Automatic tagging with custom HTML attributes. Automatically add Features for your custom HTML attributes when they're clicked. For more information, see Automatic Feature tagging with custom HTML attributes.

Exclusions

You can exclude specific CSS classes and IDs from the Suggested Match option in the Visual Design Studio when tagging Features and placing guides. 

  • Suggested Match Class Exclusions. Exclude specific CSS classes from the Suggested Match option in the Visual Design Studio when tagging Features and placing guides.
  • Suggested Match ID Exclusions. Exclude specific IDs from the Suggested Match option in the Visual Design Studio when tagging Features and placing guides.

For more information, see Configure the Visual Design Studio for guides and tagging.

Was this article helpful?
0 out of 0 found this helpful