Web 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 and cookies and data privacy settings for your application.
  • Agent Settings, where you can configure agent version and compatibility settings for your agent version controls, use the Pendo agent debugger tool, and set up the ability to collect custom HTML attributes in addition to Pendo's default attributes.
  • Raw Events, which displays a list of raw events coming into Pendo in a table view.
  • Install Settings, where you can access, customize, and copy your install script.
  • 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.
  • Replay Settings, where you configure your privacy settings for Session Replay and enable or disable replay capture.

App Details: Basic settings

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.
API Key

The 32-digit code used to connect your application to Pendo. It identifies data sent to Pendo to be associated with the specific application within the parent subscription.

This is relevant to any implementation using the install script, mobile SDK, Google Tag Manager, or segment.io.

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.
Track Event shared secret The key to connect Track Events to a specific app. This is only relevant for server-side or mobile Track Events. For more information, see Configure Track Events.
CNAME Displays content and data domains established during CNAME configuration. This information only displays if CNAME has been configured. For more information, see CNAME for Pendo.
Disable Feedback auto init Turns off automatic visitor identification for Pendo Feedback within your application.
Enable guide logic plugin

Turns on the use of guide logic syntax in the Visual Design Studio that allow you to implement advanced guide behaviors using basic markdown syntax. For more information, see Guides Logic.

This setting is off by default.

Count Track Events received for a visitor as time in application Allow Track Events to count toward a user’s time in your application. This setting is off by default.
Prefer MutationObserver to 500ms timer

This setting is used to troubleshoot issues with guide and badge placement on the screen by changing how Pendo guides and badges are anchored to your application. 

Use this setting to improve idle performance and functionality of your app. When activated, this allows the agent to detect changes that impact guide display eligibility more efficiently. By using a mutation observer, the agent checks visitor eligibility for new guides only when necessary, preventing automatic scans every 500 milliseconds. This ensures a smoother experience and is particularly beneficial for apps with dynamic content.

This setting is off by default.

Use MutationObserver on Shadow DOM elements

This setting only appears when the Prefer MutationObserver to 500ms timer setting is turned on.

Turn on this setting if your app uses web components or frameworks with shadow DOM elements (like Polymer or Lit). On page load, the agent runs a full document scan for shadow roots and attaches a mutation observer to all results.

Prefer BroadcastChannel for multi-frame support

If you have the agent installed on multiple frames on the page, the frames communicate using window.postMessage. If this setting is turned on, the agent uses the browser's Broadcast Channel API to communicate. This only works when all frames use the same domain. 

This setting is off by default.

Disable global CSS

Bypasses any configuration done within global CSS and rely only on the product’s standard CSS as well as the styles and themes included within the Pendo guide elements.

This setting is off by default.

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.

This setting is off by default.

Attempt click capture on removed elements

Allow Pendo to capture Click Events on elements, even if they're removed between "mousedown" and "mouseup" browser events. This setting ensures more consistent Pendo behavior in scenarios where events or guide behavior might be affected by element removal, improving Pendo's reliability in your application.

This setting is off by default.

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.
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 information about personal data in Pendo, see Data collection and compliance. 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.

App Details: Cookies and data privacy

For more information about how Pendo handles data and the steps it takes to protect privacy, see Data collection and compliance.

Cookie domain

Enable agent cookies for a specific domain or subdomain of your app. Alternatively, you can define this directly in the install script.

If you want to also share cookies across apps that share a domain, turn on the Enable cross-app agent cookies and local storage setting. For more information, see Track anonymous visitors across subdomains.

Enable cross-app agent cookies and local storage

For apps with client-side storage, support shared visitor identification across apps within the same web domain. Agent cookies are necessary to identify visitors across subdomains. This setting isn't available for extension apps. 

This setting is off by default.

Use POST requests only to send data to Pendo

Only send data back to Pendo using POST requests instead of GET requests. This setting is off by default.

Don't use cookies when local storage is unavailable

Prevent the Pendo web agent from using cookies when local storage isn't available. This setting is off by default.

By default, the Pendo web agent loads in local storage. If local storage is unavailable (for example, because it's full or isn't available with the visitor's browser type), Pendo relies on first-party cookies to load. For more information, see Agent cookies and local storage.

Disable agent user identification persistence

Remove pre-existing client-side visitor data upon agent load. This has an impact on your data collection, though typically minimal.

By default, this setting is turned off and Pendo searches browser storage to associate events with the correct Visitor ID if the Pendo agent initializes before the user’s ID is available. This setting clears browser storage and prevents this behavior from occurring in the future.

Disable client-side storage

Turn off agent cookies and local storage. This has various widespread effects, including turning off all other settings in the Cookies and data privacy section of your App Details.

This setting is off by default.

Agent Settings

The Agent Settings tab is where you:

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.

Install Settings

This is where you can find the install script needed for a direct implementation of Pendo by inserting a customized version of the code into your application. There are multiple options for implementing Pendo through the install script. For more information, see Direct installation options.

Localization Settings

This is where you enable and configure localization settings for the guides and Resource Center of a specific application in your subscription. For more information and instructions, see Localization.

Settings

Enable Localization 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.
Language Preference Metadata Allows you to specify the metadata field name that Pendo uses to identify what metadata value to use to associate with a supported language

Supported Languages

The list of languages and associated metadata values selected for guide and Resource Center translation. Add a language to make it available for translation. These languages are used when determining Missing Translation Language Behavior.

Missing Translation Language Behavior

Show Default Language if Translation is Missing allows you to control whether visitors see guides in the default language when a translated version is unavailable. 

If a translation is missing for a public guide or Resource Center, this setting ensures that the default language is shown instead. If this is off, a visitor might not see the guide or Resource Center if their language metadata doesn't match a supported language.

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.

Replay Settings

This tab only displays if you've purchased Session Replay as an add-on to your subscription.

Privacy configuration

These settings control how your application displays in replays that capture visitor interactions with your application. After you select a starting configuration option, use this section to create selector rules to further control which inputs in your app are masked, unmasked, or blocked in replays.

For more information, see Session Replay privacy.

Replay capture settings

  • Add audience: Select or create a segment to define which visitors are captured in replays.
  • Inactivity timeout: Select the length of time before a replay ends after a visitor is inactive for that period of time. By default, the maximum inactivity period is set to 30 minutes.

For more information, see Enable Session Replay.

Enable Replay

Turns Session Replay on. For more information, see Enable Session Replay.

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