Web SDK reports in Analytics while AEP rejects the same event

An implementation can look healthy in Adobe Analytics while AEP ingestion rejects records. A practitioner described exactly that split outcome: reporting worked, but some fields failed XDM type validation. If the team treats Analytics success as an end-to-end test, audiences and downstream personalization may run on incomplete data.

Find the first failing field

Capture one affected Web SDK event and the corresponding Edge or dataset diagnostic. Compare the browser payload, any Data Prep mapping, and the target XDM field type. Look for strings sent to numeric fields, string booleans, arrays replaced by objects, and fields whose meaning changed between pages. Make a small matrix of expected type, observed type, destination and failure count. Do not start by redesigning every datastream.

Separate Analytics-specific data from shared business data

Adobe's Web SDK Analytics setup recommends the data object for Analytics-specific variables. Shared event attributes needed in AEP still need a valid XDM destination, whether the browser sends them as XDM or Data Prep maps them at the Edge. Moving an invalid field into data and leaving it unmapped can make the ingestion error disappear while silently removing data from AEP.

Test both destinations with the same event

Use a controlled event with a known ID. Confirm its Analytics variables, its AEP dataset row and the type of each disputed field. Then test the fix across the pages and channels that emit that event. Record the schema owner and the contract for future changes, because a one-page correction will not prevent the next producer from reintroducing the wrong type.

Adovo’s view

One green dashboard cannot certify a shared data contract. The contract lives where the event enters every required destination. Prove the same event survives each path before calling collection complete.