MiaProva

MiaProva, by Adswerve, now inspects your Adobe Experience Platform implementation alongside Adobe Target. For years this extension has helped Adobe Target teams see which activities and experiences they are in, what Target returned and how their tests are performing. As organizations move to the AEP Web SDK and the Edge Network, the questions get bigger: Is the datastream right? Did consent arrive before data was sent? Which identity is primary? Did the decisions that came back actually display? Is the data reaching AEP, Customer Journey Analytics and Adobe Analytics clean? The new AEP Inspector answers those questions on every page you visit, automatically, from the network traffic the page already sends. No Adobe login, no configuration, and nothing to install on your site. Why it matters for teams on Adobe • One view of the whole Adobe stack. Target, Journey Optimizer, the Web SDK, Adobe Tags, identity, consent and analytics are inspected together, so problems that sit between products are visible. • Faster QA and migrations. Moving from at.js or AppMeasurement to the Web SDK? See both side by side, catch double counting and confirm parity before you switch. • Governance you can act on. Every issue comes with a plain-language explanation, what to do about it, and the exact calls behind it. • Shared evidence. Export a report or evidence pack for a ticket, a QA sign-off or a conversation with your agency, with personal data masked. FEATURES BY ADOBE PRODUCT Adobe Target • See the activities and experiences you are in on each page, delivered by at.js, mbox.js or the Web SDK, with their response tokens. • Highlight the content an activity changes, and see which activities compete for the same element. • Network view of every Target and Web SDK request, searchable, with copy and download. • Profile attributes and visitor IDs (mbox3rdPartyId, PCID, ECID) at a glance. • Turn Target delivery off for the current tab to compare against the default experience. • at.js and Web SDK compared side by side: latency, locations, parameters and Analytics for Target (A4T). • Checks for missing display notifications, slow decisions, repeated decision requests, missing response tokens and mbox3rdPartyId mapping. • For MiaProva customers: live results with lift and confidence, test ideas submitted in context, and page screenshots captured straight into a test ticket. Adobe Journey Optimizer • Web and code-based decisions shown next to Target's, with whether each was returned, displayed and clicked. • "Show on page" outlines the element a decision changes. • Flags when Journey Optimizer and Target change the same element on the same page. AEP Web SDK and Edge Network • Timeline of every Edge call in order: consent, identity, decisions, display and analytics. Expand any call in place to read its XDM, response handles, cookies and the findings attached to it. • Implementation fingerprint: datastream, runtime overrides, Web SDK version and deployment, edge domain and region. • Edge errors and warnings explained in plain language. • Checks for multiple datastreams, runtime overrides, outdated Web SDK versions and more than one SDK instance. Real-Time CDP and Identity Service • The Experience Cloud ID (ECID) on every page, with a warning when it changes. • identityMap checks: missing or multiple primary identities, plain-text or badly hashed emails, and authenticated IDs that disappear between pages. • Flags the legacy Visitor ID service running alongside the Web SDK. Consent • Consent timeline across Adobe Consent 1.0 and 2.0 and IAB TCF 2.0, decoded. • Flags events sent before the consent choice arrived, and Edge calls, legacy tags or personalization after an opt-out. Adobe Analytics and Customer Journey Analytics • Preview how Web SDK events map to Analytics variables, next to AppMeasurement hits on the same page. • Catches double counting when AppMeasurement and the Web SDK both collect. • Data quality checks on the XDM that reaches your AEP datasets and Customer Journey Analytics: personal data in any field, type changes between events, missing or custom event types, page views without page names, empty fields, oversized payloads and duplicate page views, with a field-by-field comparison of the two calls. • Custom rules: define your own pass/fail checks (for example "purchases carry an order ID"), share them as a file with your team, and see failures as findings. Adobe Tags • The Tags library and environment on each page, with a critical warning when a development or staging library runs on a live site. • Flags duplicate Tags libraries and legacy DTM. WORKS THE WAY YOU DO • Open MiaProva from the page with the launcher, or open the AEP Inspector in Chrome's side panel from the extension, the toolbar icon's right-click menu or Alt+Shift+M. The side panel stays with the tab it was opened for. • Browse normally. Each tab's calls are grouped by page, with a page picker to focus on one page or several. • Export evidence: an HTML report or a JSON evidence pack with screenshots and notes, with personal data masked, IDs hashed and cookies removed by default. • Contact us: see what MiaProva noticed about the analytics, advertising and consent tags on the current page, and reach the Adswerve team if you would like help. PRIVACY • Inspection happens in your browser, from the network requests the page already makes. MiaProva does not need access to your Adobe accounts. • What the inspector captures stays in your browser's session storage for the tab and is cleared when you close it. Nothing about the sites you inspect is sent to MiaProva or Adswerve. • Anonymous statistics about which extension features are used help us improve it; they never include the pages you visit or the data you inspect. • Signing in is only needed for MiaProva customer features (results, ideas, screenshots), which connect to your organization's MiaProva account. • Turn MiaProva off at any time, or block it on specific domains, f…