The problem
Marketing Cloud Personalization (formerly Interaction Studio) and the Data Cloud Web SDK send their events as base64-encoded payloads. When a campaign does not fire, the first question is always "what did the page actually send?", and the network tab answers it with an unreadable string. In this project "MCP" means Marketing Cloud Personalization, not the Model Context Protocol.
What it does
- Captures and decodes every event from
evergage.min.jsandc360a.min.js, and shows formatted JSON. - Event Explorer: filter by user, action, page type and SDK, group events, and zoom into a stacked chart over time.
- Exports: Markdown, JSON, an offline HTML report, and "Copy for agent" Markdown sized for an AI prompt. "Hide personal data" is on by default.
- SDK Tools: redirect a site's SDK request to another URL, or edit a copy of the SDK and serve it in place of the original, to test a sitemap change before it is deployed.
- Tools page: decode any payload, inject the SDK into a page that does not load it, and clear the SDK cookies to become a new anonymous visitor.
How it is built
The extension never authenticates against Salesforce.
It only observes the website's own SDK traffic through webRequest, and stores captured events locally.
Redirect and block behaviour uses declarativeNetRequest session rules scoped to the site and tab, so nothing leaks into other browsing.
Captured payloads are never sent anywhere.
What I learned
- Chrome caps a compiled rule regex at 2 KB. One joined regex for all SDK URLs blew the limit, so there is one rule per pattern.
- Mixed content blocks the obvious approach. An http replacement script cannot load on an https page, so replacements are fetched and served as
data:URLs. - Async rule removal races. Tab-wide rules removed asynchronously made end-to-end tests fail intermittently. Scoping rules by site fixed the flake at its cause.
- A CSP set in a
<meta>tag cannot be removed. That is documented as a limitation instead of being papered over.