The Guides section will show two lists: Active Guides and Excluded Guides.Īctive Guides are all the Guides available to the current visitor based on Page and Segment.
Here is an article that goes into more detail about Urls and Page Tagging. If the Current URL does not match any of the page rules, then the page you are on with the debugger loaded, does not fit the Page you have the guide set to. Click on "Test Rule" to the right of each Page rule, and in the "Test Url" box, paste the Current URL from the debugger. You will see at least one Rule for that page. If your guide is set to a specific page, copy the Current URL in the debugger and go to the Pages page, and click on the Page your guide is set to.
The Current URL is the normalized url that Pendo is recognizing from the current page you are on.
If it does match and you have a multi-app subscription, go to the Guides page, look at the second column called "App." Find your guide in the list and see if it is registered under the app you just verified the API key.Ĥ. To crosscheck that it is the right one, go to subscription settings > view app details > and look under basic settings to see the API key. The API Key is going to be specific to your Pendo app. Remember, if the guide is in production, it will also show up in staging environments.ģ. Make sure that your guide is set to the correct environment for your current testing. It will also show you whether you are in a production or staging environment. You can also use this to find your current visitor id and create a segment that applies to just your visitor id, so you can test Guides in production without anyone else seeing them.Ģ. Make sure that the metadata values fit within the segment applied to the guide you are testing. The visitor and account metadata your application is passing into Pendo for the current visitor. The agent section shows a variety of data such as subscription settings and current visitor information, which are useful for not only guide troubleshooting, but also installation troubleshooting/verification.ġ. This article will cover Agent, Guides, Throttling, and Resource Center. The debugger will load as a side navigation bar in your browser and you will see 7 sections. You should see a small red bug in the top left hand corner of your screen. To disable the debugger later you can use pendo.disableDebugging().ģ. Find the console tab and click on it to open, and type in pendo.enableDebugging() and hit enter. This will open up the browser developer tools. In your browser window, right-click on your web app page and click "Inspect"Ģ. This help article walks you through on how to start up our handy Debugger tool and use it to troubleshoot Guide display issues. Use this article to check why your Guide might not be displaying as expected in your staging or production environment.
0 kommentar(er)
