> For the complete documentation index, see [llms.txt](https://docs.hello-lisa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hello-lisa.com/developers/analytics/abobe-appmeasurement/test-harness-validation-instructions.md).

# Test Harness / Validation Instructions

Validate your Processing Rules and Adobe setup using the following checklist:

### Setup

1. **Staging page with AppMeasurement**: Include [`embed script`](/developers/analytics/abobe-appmeasurement/embed-script.md) specifying your report suite id in the `data-lsc-report-suite-id` attribute.
2. **Enable Debugging**: Use Adobe Debugger or browser devtools to inspect outgoing beacons (network requests).

### Validation Steps

1. **Fire a test event**\
   Simulate a LiSA shared event JSON (e.g., a generic playback event)
2. **Inspect the request**\
   Confirm the outgoing beacon includes:
   * `contextData` with expected `lsc.*` keys.
   * Correct custom event code in the `events` parameter.
3. **Processing Rules mapping**\
   In Adobe Analytics Workspace or Debug view, verify that each alias shows up in the target eVars/props you configured and that friendly labels are applied.
4. **Report-level sanity check**\
   Build a quick breakdown or funnel including the mapped `LiSA Event Type`, session/visitor IDs, and confirm that hits surface as expected.
5. **Edge cases**
   * Missing optional fields don’t break attribution.
   * UUIDs are passed but not used directly in heavy ad-hoc analysis (classification applied if needed).
   * Timestamps (`eventDate`) are present for discrepancy debugging.

### Reconciliation

Use `eventId`, `visitorId`, and `eventDate` to match Adobe hits to backend logs for troubleshooting and to verify no duplication. High fidelity correlation supports debugging complex user flows.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hello-lisa.com/developers/analytics/abobe-appmeasurement/test-harness-validation-instructions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.