> 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/launch-url.md).

# Launch URL

Open the right link for the user's device when an action is triggered: an iOS link, an Android link, or a desktop link.

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

The **Launch URL** action is the playable's call to action. When triggered, it sends the user out of the playable to one link chosen for the device they are on: an app store listing, a landing page, a sign-up or a product page.

This is useful for patterns like:

* A **Learn More**, **Shop Now** or **Install** button
* Click-through on an end card
* Sending users to a campaign landing page or store listing

### How it Works

When you select **Launch URL** as an action, PLAY shows three fields:

* **iOS** — typically your App Store listing.
* **Android** — typically your Google Play listing.
* **Desktop** — your website or landing page.

Fill in the ones you need. On a phone the player opens the matching platform link; on a desktop it opens the Desktop link. An empty field takes the [Autofill URL](https://help.craftsmanplus.com/play/settings/autofill-urls.md) for that platform first, then the other fields on the action, so a playable with only a Desktop link still opens it on mobile. If no URL can be found at all, the playable opens the CRAFTSMAN+ website.

When the action fires in an exported playable, PLAY hands the URL to the ad network, which opens it. In the PLAY editor preview, a **CTA Triggered** dialog shows the URL instead of opening it.

{% hint style="info" %}
Turn on **Autofill URLs** in the settings panel to enter the three links once for the whole playable. Every **Launch URL** action then uses them as placeholders, and a field you fill in on the action overrides the autofilled one.
{% endhint %}

{% hint style="info" %}
URL fields support macros such as `${CACHEBUSTER}`, `${TIMESTAMP}` and `${GDPR_CONSENT}`. PLAY fills them in when the action fires. [Catalogue](https://help.craftsmanplus.com/play/catalogue/quickstart.md) URL columns can also replace the URL per variant.
{% endhint %}

### Where You Can Use It

**Launch URL** is available in every action dropdown, including Interactions, Layer and Scene **On Finish**, [Scene Events](https://help.craftsmanplus.com/play/layers/scenes/scene-events.md), the [Global Timer](https://help.craftsmanplus.com/play/settings/global-timer.md), and Progression [Triggers](https://help.craftsmanplus.com/play/settings/progression/triggers.md) and [Conditionals](https://help.craftsmanplus.com/play/settings/progression/conditionals.md).

It should be triggered by a [Single Tap](https://help.craftsmanplus.com/play/properties/interactions/gestures/single-tap.md). On mobile, iOS only opens a link from a Single Tap, and devices can block click-outs from other gestures and from automatic triggers such as On Finish. Pick **Launch URL** on any other gesture and the Interaction Properties panel shows a **Device Click-Out Limitation** warning under the URL fields, and the scoring panel shows a **Non-compliant CTA Link** suggestion.

Launch URL counts as a CTA for the [Project Score](https://help.craftsmanplus.com/play/export/project-score.md) checks that every project and every end card has one.

### Setting Up Launch URL

{% stepper %}
{% step %}

### Select the layer users will tap, and add an interaction with the **Single Tap** gesture.

{% endstep %}

{% step %}

### In the action dropdown, select **Launch URL.**

{% endstep %}

{% step %}

### Fill in the **iOS**, **Android** and **Desktop** fields, or leave them empty to use the Autofill URLs.

{% endstep %}

{% step %}

### Preview and tap the layer to confirm the URL in the **CTA Triggered** dialog.

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Many ad networks control the click-out themselves and ignore the URL in the playable. On those networks, Launch URL goes to the destination set in the network's campaign. Check your [export partner](https://help.craftsmanplus.com/play/export/export-partners.md) before relying on a specific URL.
{% 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/launch-url.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.
