> 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/general/actions/custom-event.md).

# Custom Event

Record a named analytics event every time an action is triggered, to track moments that matter to your concept.

The **Custom Event** action records a moment you define. Give the event a name, and every time the action is triggered PLAY sends one analytics event with that name.

This is useful for patterns like:

* Tracking how many viewers reach a score threshold or a game level
* Measuring how many viewers see a particular branch or scene
* Tracking any moment the built-in analytics do not cover

### How it Works

When you select **Custom Event** as an action, PLAY shows a single **Event Name** field.

Type the name you want to record, up to 25 characters. Any characters are allowed.

* The name is recorded exactly as you type it. Names are case-sensitive, so `Score100` and `score100` are two separate events.
* Use the same name on several layers, scenes or triggers to record them as one event.
* If the Event Name is empty, the action does nothing.

A custom event is its own metric. It never changes Sessions, Total Engagements or Total Captures. When a gesture triggers the action, the gesture still counts as an engagement as usual.

To check your events before exporting, open the [Analytics Event Monitor](https://help.craftsmanplus.com/play/preview-and-share/analytics-event-monitor.md) in the Preview or Share Link. Each event appears there as a **Custom Event** row with its name.

### Where You Can Use It

**Custom Event** is available everywhere **Fire Tracker** is available, directly beneath it in the action dropdown.

### Setting Up Custom Event

{% stepper %}
{% step %}

### Open any action dropdown menu.

{% endstep %}

{% step %}

### Select **Custom Event.**

{% endstep %}

{% step %}

### In the **Event Name field,** type the name of the event to count.

{% endstep %}

{% step %}

### Save your setup as usual.

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Custom Event counts as a [**3rd Party Call**](https://help.craftsmanplus.com/play/export/3rd-party-calls.md). Events are only recorded on partners that allow the playable to reach the internet. Custom events are not sent to integrated partners.
{% 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/general/actions/custom-event.md?ask=<question>&goal=<user_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.
