> 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/adobe-appmeasurement.md).

# Adobe AppMeasurement

This page defines the **shared event contract** that all LiSA domains (media, products, comments, stickers, etc.) build upon and explains how to consistently get those events into Adobe Analytics via AppMeasurement. The goals are:

* Provide a stable **logical alias layer** (`contextData` keys like `lsc.eventId`) so you can map those aliases to your own variables via [**Processing Rules**](https://experienceleague.adobe.com/en/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/c-processing-rules/processing-rules?utm_source=chatgpt.com).
* Ensure every event includes enough metadata for **segmentation, attribution, deduplication**, and **debugging**.
* Enable you to to **validate** your Adobe configuration with clear example payloads and expected variable flows.
* Support **extensibility** across domains without changing the core bridge: new event types add their own specific context, but all share this base schema.

### Prerequisites

The bridge sends beacons through **Adobe AppMeasurement**, which must already be present on the page — typically your existing Adobe Analytics implementation (`AppMeasurement.js`, exposing `AppMeasurement` / `s_gi` / `window.s`).

If AppMeasurement is **not** loaded on the pages that host LiSA, add your standard Adobe implementation there — the bridge does not load AppMeasurement itself.

The bridge only sets `contextData`; it never sets eVars/props/events directly, so it works with any report suite once your Processing Rules are in place.

### High-Level Flow

1. LiSA emits an event (e.g., product click, playback start) to your host application or environment.
2. Adobe AppMeasurement Bridge translates that into an Adobe Analytics beacon using AppMeasurement (setting `contextData`).
3. You configure **Processing Rules** in Adobe to map `contextData` aliases into their available eVars/props and label them with friendly names.
4. Reports/funnels use those mapped variables plus Adobe events for analysis.

### Pages

* [Embed Script](/developers/analytics/adobe-appmeasurement/embed-script.md)
* [Event Delivery](/developers/analytics/adobe-appmeasurement/event-delivery.md)
* [Guidelines](/developers/analytics/adobe-appmeasurement/guidelines.md)
* [Alias Mapping Tables](/developers/analytics/adobe-appmeasurement/alias-mapping-tables.md)
* [Event Reference](/developers/analytics/google-analytics-4/event-reference.md)
* [Test Harness / Validation Instructions](/developers/analytics/adobe-appmeasurement/test-harness-validation-instructions.md)