ehadnibhemgjphdjgkallndphbghlpkn
Universal Adobe Debugger is a powerful Chrome extension for debugging Adobe Analytics, Adobe Experience Platform (AEP), Adobe Web SDK, and Adobe Launch (Tags) implementations. Built by analysts for analysts, this tool helps you validate tracking, inspect payloads, and troubleshoot Adobe Experience Cloud integrations directly from the browser console. Simply open DevTools and trigger Adobe Analytics or Web SDK calls to instantly view structured, readable debugging output. Log and inspect Adobe Analytics server calls (AppMeasurement, s.t, s.tl) directly in the console for faster troubleshooting and QA validation. Access rule execution details and implementation diagnostics to verify Launch configurations with ease. Monitor Adobe Experience Platform Web SDK requests and XDM payloads with clean, formatted console output — no more digging through nested objects. Replace Adobe Launch libraries seamlessly to test and validate implementations in real time. Access a curated collection of debugging snippets for analytics validation and consent troubleshooting. Verify Adobe Launch rules and data layer mappings Improve tracking accuracy and data quality Streamline QA workflows for analysts and developers Whether you're an Adobe Analytics specialist, AEP implementer, Launch developer, or digital analyst, Universal Adobe Debugger helps you debug smarter and ship cleaner data. Found a bug or have a feature request? Contributions and feedback are welcome. Visit our GitHub repository at https://github.com/cthae/Adobe-Launch-Debugger to report issues or suggest improvements. Changelog: 2025-04-06 -> 1.25 * [x] Add an option to disable displaying of the Target "decisioning" web sdk requests. To reduce clutter. * [x] Identify "decisioning" web sdk requests as Target rather than PV. Correct the call name. 2025-03-30 -> 1.24 * [x] Add a color picker set of settings that would allow users configure the colors of console printouts. * [x] Make a snippet shortcut to delete all cookies and local storage present on the active tab. * [x] Make OT printouts not fuzzy again. 2025-03-09 -> 1.23 * [x] CSS refactory * [x] Better bookmarks design * [x] Add an option for the light mode for the extension's UI. * [x] _satellite decided to become touchy about setDebug() using a truthy arg. Replace 1 with true. 2024-12-10 -> 1.22 * [x] Reimplementation of Adobe Experience Cloud Bookmarks * [x] Rename tabs to icons * [x] Move the redirects tab to somewhere else. To Settings and Home probably * [x] Make a New Tab for bookmarks * [x] Add a setting to choose the tab that would be opened by default when the popup renders (Home/Settings/Bookmarks) * [x] Clean up redirections. Add a message for when there's no redirections yet. 2024-11-08 -> 1.21 * [x] Change the extension icon depending on the env: * grey for when the extension hasn't yet executed all code or doesn't have the permission to do so; * green indicates that the Launch env is production; * yellow indicates that the Launch env is dev or staging; * red indicates that the Launch library is not loaded or loaded incompletely. Basically, _satellite?.environment?.stage is falsy. The rest of the functionality won't be stopped by this, however. * [x] Update the extension icon. * [x] Disable Launch UI improvements on by default. * [x] Multiple small bugfixes and refactories. 2024-10-04 -> 1.20 * [x] Add onInstalled/onStartup callbacks to set the default set of settings specifically for those who don't open the popup after installation. * [x] Support for Mozilla FF. Same extension. Cross-browsers. Seems like mostly only background will have to be reimplemented, but many APIs may be off. We'll see. 2024-10-01 -> 1.10 * [x] Appmeasurement: Prettify the product string printing. * [x] Appmeasurement: Add transaction id in the product string prettifier. * [x] Implement Launch UI improvements POC: * [x] Launch UI: Add the red indicator whenever a lib is not selected. * [x] Launch UI: Add a hint about how to change the Launch UI via Chrome flags. * [x] Add an option to print general alloy config in the snippets tab. Make sure it does so for all Alloy instances. 2024-09-02 -> 1.09.1 * [x] Rename the content-script.js to something more interesting. It's visible in the console and can be filtered by. * [x] Web SDK: Further improve the custom logging, allowing shorthands: p12/c12/v12/e12/l2. * [x] Apply all the shorthanded custom logging to Appmeasurement logging too. 2024-08-26 -> 1.09.1 * [x] Fix a bug in custom logging, in event shortcuts for the data.__adobe.analytics usecases. * [x] Fix a bug in custom logging, in prop shortcuts for the data.__adobe.analytics usecases. 2024-08-25 -> 1.09: * [x] Web SDK: Expose the event type in the logging header. * [x] Web SDK: Improve the custom logger to also check the data.__adobe.analytics object when using shortcuts. * [x] Web SDK: Make it easier for non-technical people to use the custom logging: don't require them to specify the full path to evars, props or events for xdm payloads. If users ask for evars and it's an xdm event, just add the correct path to it. * [x] Reimplement page load time to something like performance.getEntriesByType("navigation")[0]?.duration 2024-08-20 -> 1.08.1: * [x] Increased the delay at which the response is no longer expected to six seconds. Because AA can be very slow to respond. 2024-08-18 -> 1.08: * [x] Web SDK: On errors, in custom logs, add an indication that the request resulted in an error. This is for people who use filters in the console like pros. Thanks Arun for noticing. * [x] Web SDK: MVP tracking the navigator.sendBeacon() ping network requests. No access to their payloads, however, because the Chrome devteam neglects fixing related bugs. * [x] Delete requests from the map on other callbacks too to avoid misreporting calls as such that didn't receive the server response. 2024-08-14 -> 1.07.01: * [x] Increased the delay at which the response is no longer expected to two seconds. * [x] Cleanup. 2024-08-13 -> 1.07: * [x] Print the extension version, getting it from the manifest. * [x] UX improvements, CSS fixes. * [x] Add a bug submission button in info. * [x] Web SDK: Add an option to log all fields there are, giving the user the raw object. * [x] Add a callback and error logging for "cancelled" requests. That's when the browser cancels the request. And a few other types of requests. Thanks to Arun for the suggestion. * [x] Web SDK: Apply the error logging logic to Web SDK tracking too * [x] Small popup UI improvements. 2024-06-02 -> 1.06 - Byanka: * [x] Replace the counter of PVs and links with AA calls and WebSDK calls * [x] Web SDK: Improve autodebugging: indicate when linkClicks will be treated as pageviews in AA due to the web fields set. * [x] Web SDK: Surface the Edge config ids for every request, make them visible just like AA Report Suites. To ease the debugging of multi-destinational tracking. First 5 characters should suffice. * [x] Web SDK: Improve the tracking of network errors when edge network requests fail. * [x] Web SDK: Refactor logging. Make it less confusing. No more nested groups. * [x] Web SDK: Change the default logging a bit to maybe try and expand the analytics object automatically. * [x] Web SDK: Add a setting to remove the essentially useless xdm fields that are rarely useful to look at. On by default. * [x] Web SDK: Improve the logging for non-object fields. * [x] Web SDK: Add logging for the data.__adobe object. Off by default in settings. * [x] Web SDK: Reinforce the custom logging field, allow people to use the xdm. reference in the list of params. For older versions, please refer to github releases here: https://github.com/cthae/Adobe-Launch-Debugger/releases
Trello Bug Feature Colors
Colors Trello cards that have the label "Bug" or "Feature" a color based on the color of that label.
Add to LinkJoin
Organize and automatically open virtual meetings. Keep all of your links in one central location where they can be sorted, searched for, and opened from any device with just a click. Receive reminders up to 30 minutes before a meeting and automatically opens it when the time comes. LinkJoin Bookmarks store links for access from any device at any time. Add to LinkJoin streamlines this process into a two-click process in your browser. Add to LinkJoin operates in the background so you can open links or open Zoom meetings automatically without any tabs running. Share links and bookmarks with others via the LinkJoin website, transferring your saved information to them as well.
WhoFundsWho
Instantly shows you who funds the experts, politicians, think tanks and other institutions you are reading about. WhoFundsWho is a browser extension that instantly shows you who funds the experts, politicians, think tanks and other organizations that you are reading about. We rely on experts and institutions to make sense of the world. But these experts and institutions have their own biases and interests. These are typically not disclosed to the reader even though they may have an influence on what the organization or person believes or says. While you usually could find such information if you did some research, who wants to have to do that research for every person or organization they are reading about? WhoFundsWho did this research for you and makes it instantly available to you exactly when it is most relevant to you. WhoFundsWho highlights on any webpage the names of organizations and people for who it has funding information in its database. Simply click on or hover over the highlighted name to open a popup that displays that information for you. And it is not just financial information that WhoFundsWho can provide you with. It can also tell you: - what other organizations a person has worked for - how an organization is related to other organizations - who their parent or child organizations are - who they partner with - what networks they are a member of and more. How to Use In the user menu there are several options you can choose from: - on / off - Use this to turn the extension on or off. The default is 'on'. - click / hover - By default the popup will open when you hover over a highlighted name but you can also choose 'click' which opens the popup when you click on the highlighted name. The potential issue with the 'click' option is that sometimes the names that the extension finds and highlights on the webpage were already hyperlinked on the original page. And the hyperlink applied by the extension may then override the original hyperlink so that the original link is no longer accessible. This conflict is avoided by choosing 'hover' to open the popup which leaves the webpage's original click action intact. - quick / full - The 'quick' option loads the popup with only the most important information, in text format, while the default 'full' shows all available information, and it uses both text and images. - first / all - When the default 'all' is selected, all instances of each matching name found on the webpage will be highlighted whereas 'first' will highlight + hyperlink only the first two instances. The reason for this option is that if the name of an organization or person is frequently mentioned on a webpage then it may become distracting or visually unappealing if each instance of that name is highlighted + hyperlinked. Note that on twitter.com the option to highlight only the first 2 instances is not available and all instances will be highlighted. - include people - The database contains records for both organizations and people. The extension will always highlight the names of matching organizations but by checking or unchecking 'include people' you can choose whether you also want it to find matching people. - category checkboxes - You can choose one or more of up to 11 different categories of organizations & people. If for example you are only interested in information about think tanks, then check that option. If you want the extension to alert you whenever the organizations or people you are reading about are funded by the Bill & Melinda Gates Foundation or have some affiliation with the - all websites / select - By default the extension runs on all webpages but you can also specify the websites that you want the extension to run, or not run, on. Click the 'select' link to open the input form where you can specify the specific URLs. Then check the 'select' radio button, and choose whether the extension should or should not run on the websites you specified. - highlight & text - Select the highlight and text color the extension uses. Or select 'none' to to select a text color without any highlighting applied to it. Privacy WhoFundsWho performs all privacy sensitive operations locally, on the user's local machine. Upon installation the extension downloads from two Google Sheets two lists of keywords (one for organization names and one for people names) together with the (encrypted) URLs of the Airtable records they are associated with. It uses these to locally build a Bloom filter data structure which in turn it uses to perform keyword searches of the text of webpages the user visits. This works as follows: After a webpage's text content has fully loaded, the content script captures all visible text and sends it to a local service worker that performs a Bloom filter keyword search on it and returns an array with the keywords it found. The content script then highlights and hyperlinks these keywords on the webpage. Up to this point all these processes are automatic and take place only on the user's local machine. No data about the websites the user visits or the text on those websites is ever transmitted to servers in this process. It is only when the user clicks on or hovers over a highlighted name to open a popup with funding data for that organization or person, that a record retrieval request is sent to a server. The request sent to the server consists only of the (encrypted) url and two backup urls where the Airtable records associated with the name are located. The only information sent to the server is a request to see a specific record of an organization or person. No user data (e.g. IP address) is collected or logged. For all this to work, WhoFundsWho requires three permissions: Host Permission By default WhoFundsWho runs on all webpages and it runs automatically, without requiring the user to manually start the keyword search of a webpage's text. The user can change these settings in the user menu by choosing the 'off' rather than 'on' setting and then manually re-activating the search on each webpage it wants the extension to run on. The user can also specify a list of websites that the extension should or should not run on. But the default is that the extension runs automatically and on all websites. For this to work, the extension requires the '' host permission, a powerful permission that could potentially be misused. That is why all privacy sensitive actions are only performed locally, as explained above. Storage Because the extension downloads the keywords data from the two Google Sheets in order to locally build the database that it uses for the keyword searches, it needs storage permission. This permission is also needed to store the selections the user makes in the user menu so that these selections can persist between different sessions. Unlimited Storage Because the number of keywords in the database that it needs to store locally is very large (75,000+) the extension requires more than 5MB storage space, which means it requires the Unlimited Storage permission. For an FAQ & troubleshooting, as well as more information about the project, visit www.whofundswho.com
Adobe Web SDK Sniffer
When working with Adobe Experience Platform's Web SDK, have you ever found yourself wanting to validate a specific field, but that field is nested deep within the XDM, sighing as you expand thirty object keys? If so, this extension is for you. It will display only the key value pairs in the request that you want to see. Simply open the extension, input the path to the fields you want to validate, turn on listening, hit save, and open your developer console. Support for complex data types, too. Also displays full XDM for convenience.
