Migration › Validate the payload
Step 11 of 13
85% complete
Validate the payload
Building the migration is maybe a third of the work; proving it correct is the rest, and this is where projects quietly succeed or fail. Your old debugging reflex, watching the network tab for
b/ss/ calls, now finds nothing, because data goes to the Edge, not the legacy servers. So you validate in two places first: what leaves the browser, and what the Edge does with it. The Debugger shows the exact payload before it departs; Assurance's Edge Trace shows whether the Edge accepted it or dropped it against your schema, and names the field that broke if it did.What to do
1
Browser AEP Debugger › Network[25], inspect the exact
xdm/data JSON before it leaves. Tip: lock to production and swap in your Dev library to test live, your session only.2
Edge Debugger › Logs › Edge Trace (Assurance)[26], watch the Edge validate against the schema and fan out. A schema violation is flagged and dropped, with the offending node named.
⚠ Common mistake
Validating only in the browser and assuming "it left, so it landed." A payload can leave perfectly clean and still be dropped at the Edge for a schema violation you never see in the network tab.
✓ You should see
The payload correct in the Debugger and accepted, not dropped, in Assurance.