Adobe Experience Platform Assurance (Griffon) debugging

What this is

Adobe Experience Platform Assurance (formerly Project Griffon, generally available October 15, 2022) is a tool to inspect, proof, simulate, and validate how an app collects data or serves experiences, streaming live app events in real time over a no-proxy connection established by QR code, session link, or button tap. It covers mobile SDK implementations and, through the Experience Platform Debugger, Web SDK (Alloy) implementations, and is reached at griffon.adobe.com or experience.adobe.com/assurance (also via the Data Collection UI).

Access and session facts

Connection methods

Base URL definition: the root definition used to launch the app from a URL (the deep-linking URL); a session URL is generated from it to initiate the Assurance session.

Quick Connect minimum SDK versions

These thresholds are version-sensitive; confirm against the latest SDK release notes before relying on them.

startSession API by platform

Deep link scheme configuration

Device vs simulator connect

Views (add or remove via Configure, bottom-left → Save)

The left navigation is customizable: select Configure at the bottom-left of the window, add or remove views, and select Save. SDK events load by default in a time-sorted list, each with a detail view, and events can be searched or filtered.

Both the Analytics and Analytics Edge views include validation tabs that display validation-script results, with links to errors and the problematic events. The home overview also references Places / Location Services and Streaming Media validation; confirm the full plugin list in the live Configure panel.

Event Transactions — processing-stage columns

Indicators: a green checkmark signals successful processing; a warning sign signals a detected issue. Selecting an event opens the Event Details panel on the right with a nested tree view expandable via the + buttons. The current datastream identifier is shown in the info tooltip next to the Edge Network column header.

Analytics Edge event-detail chain (Edge requests / track events)

Ordered sections in the detail view: Event Details → Edge Bridge Request → Datastream → Edge Hit Received → Edge Hit Processed → Analytics Hit → Analytics Mapping → Analytics Response → Post-process Data.

Post-processed status values (Analytics view)

Web SDK (Alloy) key events

Minimum versions to avoid the “No Debug Flag” error

Export

On the session details page, select Export to JSON. The export respects active search filters: only the events currently displayed are exported, so searching “track” then exporting yields only track events. Sessions auto-delete after 30 days, so export before then to hand evidence to another engineer.

Gotchas

1. QR code scan does not open the app → the QR / camera or deep-link handoff is not working on the device → open the session link directly from Session Details in the device’s browser, or on iOS 11+ scan the QR code via the Photos app.
2. App will not open the session link / deep link at all → deep linking is not configured (Android App Links; iOS Custom URL Scheme or Universal Links) or startSession is not being invoked → verify the deep-link configuration, and note Android’s startSession need not be called explicitly while iOS does require Assurance.startSession(url:).
3. PIN / authentication overlay appears but the connection still fails → no device internet, the Assurance SDK is not properly installed, or the session belongs to a different ORG instance → check connectivity via a browser on the device, verify the SDK install, and confirm the session matches the link and the correct ORG.
4. Analytics hits show status “No Debug Flag” and no upstream detail → Adobe Analytics and/or the Assurance SDK are below the minimum that emits the debug flag → upgrade to iOS Adobe Analytics >2.4.0 / Assurance >1.0.0, or Android Adobe Analytics >1.2.6 / Assurance >1.0.0.
5. React Native build fails with “Module AEPAssurance not found” or header errors → a version mismatch between the Assurance RN plugin and the core plugin (v2.x pairs with react-native-acpcore; v3.x requires react-native-aepcore) → align the versions, downgrading react-native-aepassurance to v2.x if still on older Mobile Core.
6. Exported JSON is missing events you expected → Export to JSON writes only the events currently displayed, filtered by any active search → clear the search / filter before choosing Export to JSON to capture the full session.
7. An expected view (e.g. Analytics Events or Event Transactions) is missing from the left navigation → that view is not added to the session’s configured views → select Configure at the bottom-left, add the view, and select Save.

Quick recipes

Start an Assurance session on iOS from the deep-link handoff (required on iOS):

// iOS: startSession must be called explicitly
func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
    guard let deepLinkURL = URLContexts.first?.url else { return }
    Assurance.startSession(url: deepLinkURL)
}

Handle the deep link on Android (startSession need not be called explicitly, but this is the hook):

// Android: Assurance resolves the session from the deep link
fun handleDeeplink(deeplink: String) {
    Assurance.startSession(deeplink)
}

Register the custom URL scheme so the OS routes the deep link to the app:

<!-- Android: scheme + host are the Assurance-relevant values -->
<!-- iOS equivalent: Xcode > Info tab > URL Types (e.g. lumatutorialswiftui://) -->
<intent-filter>
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:scheme="lumatutorialandroid" android:host="default" />
</intent-filter>

Connect a Web SDK session by pasting the copied link (Assurance appends the session id):

# Paste the Copied Link into the browser address bar.
# Assurance appends adb_validation_sessionid automatically and starts the session:
https://luma.enablementadobe.com/?adb_validation_sessionid=SESSION_ID

Find the ECID inside an Alloy Response Handle event (drill the payload tree):

# In the Alloy Response Handle event detail, expand the Raw Event payload:
payload > 0 > payload > 0 > namespace

Pair the React Native plugins to avoid the “Module AEPAssurance not found” build error (v3.x assurance requires aepcore; v2.x pairs with acpcore):

{
  "dependencies": {
    "react-native-aepcore": "3.x.x",
    "react-native-aepassurance": "3.x.x"
  }
}

Related

• Hub: Adobe guides
• Adobe Analytics implementation QA checklist
• AEP Web SDK configuration reference

Sources

Adobe Experience League pages these values were read from:

• Adobe Experience Platform Assurance overview (read 2026-07-20)
• Using Adobe Experience Platform Assurance (create / connect a session) (read 2026-07-20)
• Implementing the Adobe Experience Platform Assurance extension (read 2026-07-20)
• Event Transactions view in Assurance (read 2026-07-20)
• Adobe Analytics Events view in Assurance (read 2026-07-20)
• Adobe Experience Platform Assurance troubleshooting guide (read 2026-07-20)
• Set up Assurance for Platform Mobile SDK implementations (read 2026-07-20)
• Validate Web SDK implementations with Experience Platform Assurance (read 2026-07-20)

Flagged rather than guessed: the canonical UI overview page (view/user-interface) and a dedicated configuration page returned HTTP 404 and appear to have been reorganized, so UI details here come from the using-assurance tutorial and individual view pages; the full catalog of views / plugins is not enumerated on any single page (Places / Location Services and Streaming Media are referenced but unverified — confirm in the live Configure panel); for Web SDK, whether a PIN is ever presented is not stated (connection is via adb_validation_sessionid, not a PIN step); the exact column labels of the default SDK event list beyond “sorted by time” are not spelled out; and the Quick Connect and “No Debug Flag” minimum versions are version-sensitive — confirm against the latest SDK release notes.