Checklist from browser to platform
- Network tab — are
interactrequests sent to the Edge Network? - AEP Debugger — inspect the payload and the Edge trace.
- Datastream ID — the edgeConfigId in the request must match the datastream you configured.
- Datastream status — active, with the Experience Platform service enabled.
- Dataset mapping — the event dataset is selected in the datastream.
- XDM schema — payload fields match the schema.
- Identity — namespaces exist and identityMap is valid.
- Ingestion monitoring — look for failed batches or errors.
Datastream ID does not match
If a debugger shows a different datastream than the one you configured, the page is usually loading a different Tags property or environment, or the extension is configured for another environment. Check the embed code on the page, the library build and the Web SDK extension settings for each environment.
ECID missing from the request
Confirm the Web SDK extension is configured to manage identity, consent has not blocked collection, and the first request completed. Then read ECID with getIdentity (see the ECID data element guide).
Frequently asked questions
Which tool should I start with?
The browser network tab and the Adobe Experience Platform Debugger; they show whether the problem is on the page or in the platform.
Can consent block Web SDK?
Yes. If default consent is pending or out, events may be held or dropped.
Last updated: