The Experience Platform Debugger is an extension available for Chrome and Firefox browsers which helps you see the Adobe technology implemented in your web pages. Download the version for your preferred browser:
If you’ve never used the Debugger before - and this one is different from the previous Adobe Experience Cloud Debugger - you might want to watch this five minute overview video:
Given that you’ll be loading the demo website in incognito mode, you need to make sure the Experience Platform Debugger is also available in incognito mode. To do so, go to chrome://extensions in your browser and open the Experience Platform Debugger extension.
Verify that these 2 settings are enabled:
For this exercise, you’ll be using the EXP News website.
In a new incognito/private browser tab, open https://public.aepdemo.net/.
Enter the Configuration ID you created in Module 0 and click Load Configuration.
Scroll down and click Save Configuration.
Go to Select LDAP, select your LDAP and click Save.
Next, go to Select Brand , select EXP News and click Save.
On the Admin homepage, click the logo to open the website.
You’ll now see the EXP News homepage.
Make sure you have the EXP News site open and click the Experience Platform Debugger extension icon.
The Debugger will open and show the details of the implementation created in your Launch Property. Remember that you’re debugging the Extension and rules that you have just been editing.
Click the Sign In button on the top right to authenticate. If you already have a browser tab open with the Launch interface, the authentication step will be automatic and you won’t have to enter your username and password again.
Confirm the Debugger is Connected to Home as pictured above and then click the lock icon to lock the Debugger to the demo website. If you don’t do this, the Debugger will keep switching to expose the implementation details of whatever browser tab is in focus, which can be confusing.
Next, click any random article on the EXP News homepage.
Now click AEP Web SDK in the left navigation, to see the Network Requests.
Each request contains an events row.
Click to open the events row. Note how you can see the web.webpagedetails.pageViews event, as well as other, out-of-the-box variables adhering to the AEP Web SDK ExperienceEvent Mixin format.
These types of request details are also visible in the Network tab. Filter for requests with interact to locate the requests sent by Web SDK. You can find all the details of the XDM payload in the Request Payload Headers: