The Suggested Pages table automatically turns untagged URLs in your event data into a list of recommended page tags. Accept or delete the recommended tags to quickly tag the pages your visitors have seen in the last 5 days. Suggested pages provide a recommended name, application, and page tagging rule with the number of recent page views using that rule. The complete URL is provided to compare to the suggested rule. A red notification icon in the navigation menu indicates if you have new suggested pages to review. The Suggested Pages table is in Product data on the Pages List Overview page.
Tagging pages is one of the fastest ways to view data from your app in a new Pendo subscription. You can recognize user behavior patterns as they navigate your app and begin to understand how many users are using your app, where they spend most of their time, and how frequently they return. Tagging pages is a foundational step before you tag features and create guides. Feature tags can be limited to only track clicks on certain pages. For example, a save button is a common element throughout your app, but you want to identify clicks on the save button on the New Account page. The feature tag can target the save button only on the New Account page you've already tagged. Guides use tagged pages in a similar way. To set a guide to only display on a certain page, set the guide location to the tagged page instead of sitewide.
- Pendo Admin users to enable setting and accept tags
- Suggested pages enabled in App Details
Turn Suggested Pages on and off in App Details
Suggested Pages are activated for each app individually in Subscription Settings > App Details. Turning Suggested Pages on for any application makes the Suggested Pages table visible to the entire subscription. The table only recommends tags for apps with Suggested Pages turned on.
1. Navigate to Subscription Settings.
2. Select View App Details to see settings for that application.
3. Toggle Pendo Suggested Pages on and off for the app with the checkbox.
Accept or delete suggested pages
When you have pending suggested pages, a series of red notification icons appear in the UI and guide you to the Suggested Pages table. A red counter next to the Pages Overview tab indicates the number of pending suggested pages for all apps with Suggested Pages turned on. The app filter in the filter bar limits which app's pages appear in the Suggested Pages table in addition to filtering existing tagged pages.
The Suggested Pages table shows all untagged pages that appeared in your events in the previous 5 days. If a suggested page isn't used in 5 days, it's dropped from the table until it is used again. These pages have not been tagged and processed yet. They can't be used in reports or tagging and you can't see full retroactive analytics until after they're tagged and data processing is complete. After tagging a page, processing can take up to an hour and data is typically visible in the UI at the top of the hour.
Review suggested pages
Suggested page rules identify unique text in the URL and build a rule that focuses on that unique element and ignore the rest of the URL. Depending on the structure of your app, a suggested rule may tag a single page or an entire area of your application. Both are good tags that provide meaningful data but it's important to know what a tagged page is capturing. Long URLs with multiple sections may have multiple suggested pages in the table with different specificity.
1. Look at the URL, rule, and number of views. This tells you what the suggested rule is tagging on your website and how much usage that page has gotten. It may be helpful to compare number of views to other similar suggested pages to see the specificity of different tags.
2. Edit the name. Suggested pages provide a simple default name based on the URL. You can change the name to something more detailed or keep the default name.
3. Accept the suggested page. Click the Accept button at the end of the row to immediately begin processing page data. It moves into the Pages list with a processing status.
4. Delete the suggested page. This removes the suggested page from the table and does not suggest this URL and page rule again.
Understanding URLs and Suggested Page rules
Suggested page rules use basic Pendo page tagging rule syntax with forward slashes /, asterisks *, or text to define the structure of the URL. Wildcards and text define the values in the URL. The rule is used to search the URLs saved in all of your captured events and try to match the structure and values in the rule while ignoring wildcard values. Every time the rule matches the URL in a raw event, it's counted as a page view for that tagged page and all of the associated visitor, account, and feature data is tied together.
Deep dive into page tagging and more complex manual page tagging rules in the Understanding URLs for page tagging article.
Website URL anatomy
Page tagging rules match the structure of a website URL. A URL has several parts. Let's look at a simple example.
- "https://" - The scheme. This tells web servers what to do when they access a website.
- "app" - The subdomain. This buckets different parts of a website that all share a domain.
- "example.com" - The domain. The most recognizable part. This has two parts, the second-level domain and top-level domain, but they're often combined and referenced together for simplicity.
- "category/user/profile.html" - The path. Everything after the domain is the path. This identifies certain content or folders in the domain.
- "/category/" - A subfolder. Sometimes called a subdirectory or folder. It's just like a folder on your computer.
- "/profile.html" - A page. An endpoint with content. It can have different extensions for different file types or simply end with a forward slash.
Page rule anatomy
Page rules mirror this structure but they cut out the parts you don't need and identify the parts you do. Suggested page rules do this for you automatically. When you know the structure of your URL and what the rule is searching for, you can confirm that the page view data represents what you want to capture in that tag.
- The beginning of the rule always starts with //. This cuts off the scheme. The rest of the rule looks at everything after it.
- The entire domain is skipped with a wildcard //*/. All events are coming from the app where your Pendo snippet is installed and a snippet for one app isn't typically installed on multiple domains.
- This structure accounts for subdomains and other common configurations of the root URL, for example dev.pendo.io, staging.pendo.io, and app.pendo.io may all have the same Pendo snippet as code is promoted between environments, and all are simplified down to //*/ in the page tagging rule.
- You can add the the domain to a page rule for greater specificity if needed, but this is not done automatically in suggested pages.
- A unique value is identified in the path, everything else is a wildcard.
- This rule matches every page URL that ends with the user folder.
- A unique value can be identified in the middle of a path and everything after is ignored.
- This rule matches every URL with category in the path. It includes /category, /category/user, /category/user/profile.html, and any other branches on the website that fit.
There isn't a right or wrong way to tag a page. Sometimes you want to group all usage in an area of your app in a single tagged page. Other times you want usage for a single page. You can tag both to see the data you want. Overlapping or duplicate tags won't compete, they'll both tag and count the same event.
Tip: For a real world example of overlapping tags, we have Pendo installed over our Help Center. The base domain support.pendo.io is tagged as a page to track usage of the entire website as a single page. Each article is also tagged as a page to track usage of a single article. Being able to target a single Pendo page that represents usage of the entire app is a kind of Pendo shorthand that's helpful in segments and reports.