> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/preview-and-share/analytics-event-monitor.md). # Analytics Event Monitor The Analytics Monitor is a live event feed built into the Share Link and the Preview. Open it with the analytics monitor button at the top right of the page. Playables fire analytics events as viewers interact with them, and normally the only way to see those events is digging through the browser's network panel. The Monitor surfaces them in a readable feed so anyone can verify tracking behavior in real time before exporting. *** ### Totals Three running totals sit at the top of the panel: * **Sessions**. Counts once each time the playable loads or restarts. * **Total Engagements**. Counts each tap on a layer that has an interaction assigned. * **Total Captures**. Counts CTA clicks. A Capture also counts as an engagement. If a single tap fires several events at once, **Total Engagements** still only increments once. *** ### Events Each event appears under the **Events** header the moment it fires. Some events add to the totals; others are display-only context. * **Impression**. The playable loaded. Adds to **Sessions**. * **Engaged**. The viewer's first interaction. Display only, and always accompanies the first **Engagement**. * **Engagement**. A layer with an interaction was tapped, listed with the layer name. Adds to **Total Engagements**. * **Scene Started** and **Scene Ended**. Each listed with the scene name. Display only. **Scene Started** covers every scene the playable enters, the opening one included. * **Game Started**, **Game Progress** and **Game Ended**. A game layer's lifecycle, each listed with the game type. Display only — a tap on a game already appears as its own **Engagement**, so these don't add to the totals. **Game Progress** fires at most once per second while a game's score, moves or health are changing, so expect a steady run of these during play. A game layer becoming visible or hidden on the timeline is deliberately left out of the feed, and always will be — it's a timeline detail rather than something the viewer did. That is separate from **Visibility Changed** below, which is about the whole playable. * **Capture**. A CTA click, listed with the layer name. Adds to **Total Captures** and **Total Engagements**. * **Tracker Fired**. The interaction had a fire tracker action attached, listed with the layer name. Display only. * **Finished**. The viewer reached an end card. Display only. * **Visibility Changed**. The playable was hidden or shown, for example when the browser tab is switched away and back. Display only. (ex. after a CTA clicked) {% hint style="info" %} *The Monitor shows the events most useful for verifying a build. The platform fires additional analytics events under the hood that don't appear in the feed.* {% endhint %} *** ### Resetting There are two levels of reset: * The **reset** button in the panel header clears everything: the totals and the event feed. Reloading the page or leaving the Preview does the same. * The playable's **Restart** button starts a fresh session instead: it clears the event feed and adds one to **Sessions**, while **Total Engagements** and **Total Captures** keep counting. {% hint style="warning" %} *The Analytics Monitor is available for Interactive Ads. It doesn't appear on Animated Banner previews or share links.* {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.craftsmanplus.com/play/preview-and-share/analytics-event-monitor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.