oofdmlnnhklkojloenkonbfopilanobo
Streamlines Adobe Analytics (AA) implementation debugging and validation, leveraging the power of Google's Gemini AI. This Chrome extension simplifies debugging and validation of your Adobe Analytics (AA) implementation. It leverages the power of Google's Gemini generative AI API as a core part of an experiment to explore how GenAI can boost productivity in technical tasks. By intercepting AA requests, parsing the payload, and validating it against user-defined rules, this extension provides immediate feedback in the browser's developer console, streamlining your workflow. The GenAI Advantage: This extension isn't just about validation; it's about exploring the potential of GenAI to automate and simplify complex tasks like creating and applying validation rules. The flexibility and intelligence of the Gemini API allow the extension to handle free-form, human-readable rules, making the validation process more efficient and intuitive. Key Features - Real-time validation of AA requests. - Customizable, human-readable rules. Experiment with different rule formats and complexities! - AI-powered validation with Google's Gemini, showcasing the potential of GenAI for productivity. - Clear and formatted results directly in the console. For details and usage instructions, please visit the following page: https://ext.rebeccandavid.com Install the extension from the Chrome Web Store. Once installed, the extension icon will appear in your browser toolbar. The extension validates your Adobe Analytics data based on rules you provide in a text file. Here's how to create and upload your rules file: Below is a recommendation of the rule structure, Gen AI can read and interpret the rules, experiment with different ways to write the rules. File Format: Create a plain text file (.txt) with your rules. Each line in the file represents a rule. Comments are supported using #. Rule Structure: Each rule follows the format FieldName: ValidationRule. Here's a breakdown: FieldName: The name of the Adobe Analytics variable (e.g., pageName, eVar1, prop2, events, products, etc.). ValidationRule: Specifies the validation criteria. Several rule types are supported: required: The field must be present and not empty. text: The field can contain any text (including empty strings). url: The field must be a valid URL. number: The field must be a number. [value1, value2, ...]: The field must match one of the listed values. Case-sensitive. (value1, value2, ...): The field is optional. If present, it must match one of the listed values. Case-sensitive. eight-digit number: Field must be an eight-digit number. uuid: The field must be a valid UUID (Universally Unique Identifier). (Optional, if present, must be a UUID) ISO 8601 timestamp: Field must be a valid ISO 8601 timestamp format. country code: Field must be a valid country code. language and locale: Field must be a valid language and locale code. begin with "some string": Field must begin with the specified string. [1 to 15]: Field must be a number between 1 and 14 (inclusive). no or eight-digit number: Field must be either "no" or an eight-digit number. - Conditional Rules: Use if statements to apply rules based on other fields. For example: v1: if pev2 is click Event then text. Supported operators include is, is not, contain, contain not. Uploading Rules: - Open the extension popup. - Click "Choose File" to select your rules file. - Click "Submit" to upload the rules. A confirmation message will appear. The extension uses Google's Gemini AI to validate the rules. To enable this: - Open the extension popup. - Check the "Enable GenAI Validation" toggle. A warning will be displayed explaining the privacy implications (your data will be sent to Google's servers). - Click "OK" on the warning to confirm. - Add/Change your GenAI API Key: - Click on "Add/Change API Key" button. - Enter your API key in the input field. - Click "Save". Your key will be stored securely. - Select the Gemini Model from the dropdown. - Click "Save Settings" to apply the API key and model settings. Important: Keep your API key secure. Do not share it publicly. Once you have uploaded your rules and enabled GenAI validation, the extension will automatically validate Adobe Analytics calls made by your website. The validation results will be displayed directly in your browser's console: - Formatted Output: The results are displayed in a clear, formatted way, showing the field name, the value sent, and whether the validation passed or failed. Error messages are provided for failed validations. - Collapsible Sections: The output is organized into collapsible sections (e.g., "eVars," "props," "Lists") for easier navigation. - Product List Validation: Product-specific rules are displayed under each product in the products array. This helps pinpoint issues with individual product data. - Validation Summary: A summary of validation errors is shown to give a quick overview. You can expand the summary to see all validation results (including successful ones). The provided rules-examples.txt (https://drive.google.com/file/d/1gJyyN48t59gTYrAFgKRdLWkfSt4pQWBB/view?usp=sharingfile) contains various examples of validation rules. You can adapt and extend these rules to fit your specific requirements. The extension currently supports a simplified text structure for the rules. Future updates may include support for more robust CSV parsing for more complex rule definitions. - Open the extension popup. - Uncheck the "Enable GenAI Validation" toggle. The setting will be saved immediately.
Activity Map v3
See where visitors are interacting with your website! Increase engagement and conversion rates by optimizing your website content, in a visual and intuitive way. Understand where visitors are interacting with your website, where those visitors come from and where they are going. Real-time page analytics Do you need to make real-time decision on your content? Are you obsessed with improving your website design? Activity Map now offers minute granularity to understand link trends. Do you market to different audiences? What is distracting visitors who reach the shopping cart but do not purchase? With Activity Map, you can create a multi-segment filter Which links are involved in conversions? How much time are visitors spending on a specific link? Activity Map lets you use all your custom Adobe Analytics metrics
Universal Adobe Debugger
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
Digital Data Viewer (DDV)
View, filter and save Adobe Analytics and Adobe Experience Manager (XDM / Alloy) data from developer tools. Digital Data Viewer (DDV) captures requests made to Adobe Experience analytics platforms (AppMeasurement + XDM) and presents the information from your digitalData data layer delivered to Adobe for page view and link click event tracking in devtools panel. - Compact view tied to each tab, for focused evaluation of data dedicated to analytics analysis. - Incorporates Tag Management System info (Adobe Launch and Tealium) including build, property, report suite into each request. - The filter mechanism allows for simple string search, as well as regexp, and filters out request so only those that include the matching value are displayed - Export all request as: CSV, TEXT, HTML, JSON -- allowing for the capture of an entire "flow" for further analysis offline. - Forward events to your endpoint to assist with Adobe Event Forwarding local development.
Adobe WebSDK Tracker
WebSDK beacon tracker with CSV export (identical functionality to original, only export format updated). The Adobe Beacon Tracker is a Chrome Extension designed for analysts, developers, and QA engineers who work with Adobe Analytics (AA) or Adobe Experience Platform (AEP) Web SDK implementations. It automatically detects and logs Adobe Analytics beacons (/b/ss/) and Adobe Experience Platform data collection calls (/v1/collect), providing a clean and exportable view of every analytics payload sent from your site. This tool helps you audit, validate, and debug beacon data in real time — without relying on Adobe Debugger or external proxy tools. Instantly detects all outgoing requests to Adobe Analytics (/b/ss/) and Adobe Web SDK (/v1/collect) endpoints. Works across all websites, including SPAs (Single Page Applications) and sites with strict CSP rules. Captures both GET and POST beacons, regardless of the transport method (fetch, XHR, sendBeacon, or Image). Collects beacons from both AppMeasurement and Web SDK in a unified format. Classifies each beacon as either “page load” or “link” based on the presence of pev2. All captured data is stored securely in your browser’s localStorage. No data ever leaves your machine. Logs can be cleared at any time with one click. Beacons are sorted by beacon type for easier QA and SDR mapping. The extension does not collect, transmit, or share any personal data. All processing happens locally in your browser. Fully transparent and open-source under permissive terms. 🧩 Why Use Adobe Beacon Tracker For Analysts Export data for SDR (Solution Design Reference) mapping and validation. For Developers Debug and verify s.t() / s.tl() calls or Web SDK event objects. Confirm beacon payloads contain the right keys, values, and structure. For QA Testers Validate that all expected analytics calls fire across page flows. Use the CSV export for documentation, regression testing, or pre-launch QA. Save hours of manual comparison with ready-to-analyze beacon data. For Implementation Consultants Audit Adobe implementations for clients without proxy tools. Generate reproducible exports for SDR mapping and team collaboration. Compare AppMeasurement and Web SDK beacons in one view. Once installed, the Adobe Beacon Tracker injects a lightweight listener script that activates when tracking is enabled. It monitors outgoing network requests to Adobe Analytics and Web SDK endpoints, logging relevant data points such as: eVars, props, events, and XDM fields Timestamp and page URL pev2 (link/page classification) The source method (fetch, XHR, sendBeacon, or Image) From the popup menu: Click Export CSV to download your data All tracking is local — nothing leaves your browser. Want to automatically convert your exported CSV into a readable SDR format with summaries and highlights? Use the companion Google Apps Script hosted here: 🔗 https://github.com/Dloliver/WEBSDKAUDITBOTAPPSCRIPT/tree/main Imports your exported CSV into Google Sheets Generates a Summary sheet showing top events, unique counts, and pev2 breakdowns Adds visual highlights and borders for readability 💡 Ideal for teams using this extension for QA, SDR documentation, or Adobe Experience Platform audits. Your privacy is fully protected: All data remains on your local device unless you export it yourself. You can clear everything anytime using the Clear Logs button. See full details in the Privacy Policy included with the extension or in its GitHub repository. CJA readiness checks — Confirm Web SDK event structures for Customer Journey Analytics. SDR mapping — Quickly align beacon variables with documentation. Client demos — Show real-time data collection for stakeholder visibility. Turn the tracker ON in the popup. Navigate through your site — every beacon is captured automatically. Click Export CSV to download the data. Open the SDR Apps Script in Google Sheets and import your CSV. Run the script to generate your SDR Output and Summary sheets. ✅ Classifies “page load” vs. “link” events ✅ Lightweight UI and toggle controls In-extension beacon viewer Column filters and search by eVar/prop The Adobe Beacon Tracker is your privacy-safe, all-in-one debugging companion for Adobe Analytics and Web SDK implementations. It streamlines analytics QA, SDR mapping, and beacon validation — all without complex setup or third-party proxies. If you work with Adobe Analytics or AEP, this is the extension you’ll wish you had sooner. Privacy Policy: Included in extension and repository Developed by: Do More Media Group LLC Author: Dennis Oliver (Dloliver)