> 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/fire-tracker.md).

# Fire Tracker

Fire a custom tracker URL silently in the background when an action is triggered.

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-e7e7feafcb29334b97373619371323fff0ab2973%2Factions-fire-tracker.png?alt=media" alt="The Interaction Properties popup with the Fire Tracker action selected"><figcaption></figcaption></figure>

The **Fire Tracker** action lets you send a tracking call without interrupting the user experience. When triggered, PLAY fires the tracker URL in the background.

This is useful for patterns like:

* Tracking taps, clicks, or other interactions
* Firing third-party tracking URLs on scene events, video ends, or game completion

### How it Works

When you select **Fire Tracker** as an action, PLAY shows a single **Tracker** URL field.

Paste the tracking URL you want to fire into this field. Every time the action is triggered, PLAY sends the request silently in the background. This includes the PLAY editor preview, so testing in preview sends real tracking calls.

Unlike [**Launch URL**](/play/general/actions/launch-url.md), **Fire Tracker** does not open a new tab or take the user out of the playable.

### Where You Can Use It

**Fire Tracker** is available anywhere **Launch URL** is available.

This includes places such as:

* Interactions
* Video or Sequence **On Finish**
* Game finish conditions
* Scene events
* Other action-supported systems throughout PLAY

### Setting Up Fire Tracker

{% stepper %}
{% step %}

### Open any action dropdown menu.

{% endstep %}

{% step %}

### Select **Fire Tracker.**

{% endstep %}

{% step %}

### In the **Tracker field,** paste your tracking URL.

{% endstep %}

{% step %}

### Save your setup as usual.

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Fire Tracker counts as a [**3rd Party Call**](/play/export/3rd-party-calls.md). This action will only work on partners that support 3PC. However, if you know your partner has whitelisted your tracking URL, the action will still fire even if 3PC is not supported, though you might still see a export warning in PLAY.
{% 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/fire-tracker.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.
