Application settings are accessed from subscription settings. Go to Settings > Subscription settings from the bottom of the left-side menu in Pendo 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, turn on, and turn off:
- Basic settings, such as display name, app key, suggested Pages, and Page event properties.
- Cookies and data privacy settings.
- Engineer settings.
- 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: web, mobile (for example, iOS), or extension. |
| API key |
The 32-digit code used to connect your application to Pendo. This is relevant to any implementation using the install script, mobile SDK, Google Tag Manager, or Twilio Segment. The app key identifies data sent to Pendo to be associated with the specific application within the subscription. This isn't a secret key and is unrelated to security and privacy. The app key is only used to send data to your Pendo application and doesn't provide read access to any of your data. |
| 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 is configured. For more information, see CNAME for Pendo. |
| Show guide to anonymous visitors | Controls 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. |
| 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. |
| Disable global CSS |
Bypasses any configuration done within global CSS to 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. |
| 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. Turning on this setting reveals the Collect Page titles setting. |
| Collect Page titles |
This setting is only visible when Page Event properties is turned on. Add the |
| Sibling Selectors | This setting is only visible if you turn it on through Pendo Support. It allows you to tie one Feature rule to another UI element in your application. |
| Branding |
Assign a favicon (small image) to represent this application in Pendo. By default, favicons are assigned based on the app type: a desktop computer for web apps, a puzzle piece for extension apps, and an Android or Apple logo for mobile apps (custom images not supported for mobile). To assign a favicon, select Replace, then enter the URL of the application or upload an image. Images must be 24px by 24px and under 1 MB. When assigned, the favicon appears next to the application in filters, tables, and report visualizations across Pendo. |
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 lifespan |
After a user is granted a session cookie, it typically comes with a Time To Live (TTL) on the server side, ensuring its expiration after a set duration. This setting allows you to set the maximum number of days that web browser cookies set by the Pendo agent remains valid before expiring. |
| Prevent cookie refresh |
Prevents cookies from refreshing their expiration timestamps. This means that if the value for a cookie doesn't change, it eventually expires. We don't recommend this action. |
| 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 Visitor 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. |
App Details: Engineer settings
| Application ID |
The unique identifier for the application. |
| Disable Feedback auto init |
Wait for your application to explicitly start classic Feedback using |
Prefer MutationObserver to 500ms timer |
Use the MutationObserver API to detect changes in the DOM, affecting the timing of guides. If this setting is turned off, we check changes to the DOM at a set interval of 500 ms to know what guides to display and when. |
Prefer BroadcastChannel for multi-frame support |
Use the This setting is on by default. |
| Use visibility API instead of unload event | Use the page visibility API to detect when a page becomes visible or hidden (for example, when the user switches between tabs or minimizes the window). You might turn this setting on because Chrome is depreciating the unload event. You can't use this setting if you're using legacy browsers. |
| Attempt click capture on removed elements |
Allow Pendo to attempt to detect click events on elements that have been removed from the DOM as a result of a user action, such as clicking a button that results in its own removal. |
Agent Settings
The Agent Settings tab is where you:
- Manage the version of the Pendo agent you use for your Staging Environment and your Production Environment. For more information, see Pendo agent settings.
- Enable Pendo in Production. Turning this setting off stops the Pendo agent from running, and so requires explicit confirmation from the Pendo user taking this action. This setting doesn't affect you if you're self-hosting the Pendo agent unless you download another Pendo agent. For more information, see Pendo agent settings.
- Access the Pendo agent debugger tool to troubleshoot issues with your app. For more information, see Pendo agent debugger.
-
Collect custom HTML attributes in addition to Pendo's default HTML attributes in data collection. The same setting can be accessed from the Tagging & Guide Settings tab. Custom HTML attributes can be used for:
- Tagging Features, both manually and automatically.
- Placing tooltip guides.
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 is captured.
- Event. The type of raw event, such as click, load, 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.openermethod. - 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.