Debugger for Adobe Analytics
Prints to JavaScript console what data is sent to Adobe Analytics.
Debug Adobe Experience Platform and Adobe Experience Cloud products using the Adobe Experience Platform Debugger
按已采集快照查看用户数变化。
展示最近 7 日窗口内已采集的评分快照,辅助判断近期评分是否稳定。
同口径展示 1 天、7 天、30 天的绝对增长与增长率。
查看发布时间、版本、支持语言、最近更新和抓取时间。
查看插件说明、主要功能和适用场景。
The new Adobe Experience Platform Debugger helps to debug Adobe Experience Platform and Adobe Experience Cloud products. The new Debugger includes everything you love in the previous debugger plus these new features:
Fresh-yet-familiar design
Enjoy a debugging experience that feels more intuitive and natural.
More space to debug
The new navigation bar auto-collapses when Debugger get too small to ensure you have enough space to debug.
See your data layer in action
查看最近评论和评分分布。
商店综合星级:3.0。下方星级分布只统计已同步评论正文;如果某个插件只有公开分数、没有真实评论正文,这里可能为空。
查看 Chrome 商店详情页中的相关产品。
Prints to JavaScript console what data is sent to Adobe Analytics.
Enables the developer to locally override the embedded Launch or DTM library for testing.
View key site metrics in an intuitive visual format.
Adobe Analytics, AEP & Launch debugger. Inspect Web SDK, XDM & tracking calls directly in Chrome DevTools.
Evaluate website data, tags, and events with powerful tools for seamless Tealium iQ integration and server-side enrichments.
Manage your dynamic variables for the One Adobe Tutorial on Experience League.
Could you please fix the error that is always shown in the console? "Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist." Looks like your event sending via ports is not working correctly.
Used to work (for analytics debugging). Now it doesn't The old Experience CLOUD debugger worked great. Then Adobe added new features (bloat) to create this new Experience Platform Debugger and now you have to scroll down, past all the unwanted detail to get to the actual data you're interested in (page name, eVars, props, etc). There's no filter or sort available, so just endless scrolling. Then (Sep 2023) they added a (unwanted) 'Jump to most recent' button and broke it completely. It currently doesn't record the page view on each new navigation and it regularly shows single characters for the variables so it is completely unusable.
When this extension is running, it inserts several <script> tags BEFORE the <head> tag which seems to break tags that are loaded after this happens if they are using the insertBefore() method (which most tags do). The result is half of our tags from Data Collection get loaded and the rest just silently fail. Disable the extension and they all load perfectly fine. This is unfortunate since the only thing I find useful with this extension is being able to load a specific library for testing. So I keep it around for when I absolutely need it. Then I forget it's enabled until I run into a situation where I notice a tag isn't firing. Clunky and cumbersome.
Adobe being Adobe, I use this extension almost daily and it crashes and it is super slow, it even slows me down at work because of the ineptitude of this extension. 0/10
Used to work great, stopped working in the past couple days now nothing populates the analytics
The new visualizations for hit tracing are very cool and extremely useful. Support for the Web SDK is also much appreciated.
Cleaner interface compared to the older version and I appreciate support for the Adobe Experieince Platform WebSDK. Data Layer tool for tracking changes is also very useful.
Pale comparison to the Experience Cloud Debugger Tool.... I mean it's "nice" that you decided to add in more data into the visualization, but it's mostly useless and all at the top forcing me to scroll significantly for every page to get to what I need to test... I also like that some of the bugs have been addressed from the old tool. However, the order that the parameters come through is strange, and now that you can only see content from one tab at a time (preventing proper comparison of different environments, or even testing the same environment through multiple tabs and comparing page to page - I get that they are trying to "clean up" the visualization but it's now too segmented) the tool is cumbersome and no longer suits most testing needs.... Unless this tool picks up it socks, I will continue using the old Cloud Debugger, and if this tool is still like this when the old one is deprecated I will go back to using my browser's Network panel. I would be happy to chat with the development team on my thoughts, and maybe propose more controls over what is shown and how, since I also realize that how I use the tool could be different than others so options to change the behaviour could suit everyone.
The latest update is great! I love how it shows me how my data is flowing through Adobe's servers.
Love the Edge Trace capability in the logs along with all the new features.