Data Validation, Debugging, and QA
Verify the beacon, then verify the report
QA has two layers: client-side (is the right data sent?) and server-side (did it land in the right variable?). Use the Adobe Experience Platform Debugger and browser network tools to inspect sendEvent payloads or legacy image requests. Confirm the report suite ID, event list, eVar/prop values, and context data. Then validate in the Analytics UI or via the Reporting API that the data appears as designed. Build a QA plan from the SDR: each requirement gets a test case with expected beacon values and expected report output.
Concepts you must know
Know the Debugger's tabs (Summary, Experience Cloud, Tags, Network) and how to switch between them. Know the difference between a hit being sent and a hit being processed (latency, bot filtering, processing rules). Know how to use the Analytics real-time report and the debugger's beacon view. Understand common failure modes: wrong report suite, missing event, undefined data element, consent blocking the beacon, and duplicate hits from double-firing rules. Know regression testing after tag publishes and the value of a staging library.
Traps in questions
- Validating only in the browser and assuming the report is correct; server-side processing can drop or alter data.
- Forgetting bot filtering and IP exclusions when test hits don't appear.
- Missing consent gating, so test beacons are blocked.
- Double-firing tags that inflate metrics; check rule conditions and event listeners.
- Testing in production without a staging library or test report suite.
Rule of thumb
Every QA case states: trigger, expected beacon (suite, events, variables), and expected report. If any of the three is unverified, the test is incomplete.