# Actions
Actions determine what happens when a user interacts with your App and Web messages.
> **Note:** For actions for an [In-App Automation](https://www.airship.com/docs/reference/glossary/#iaa) or [Scene](https://www.airship.com/docs/reference/glossary/#scene), see [Actions for in-app experiences](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/).
## About actions
With actions, you gain much greater control of your users' experience with your app, and can not only provide them with more relevant, specific content, you can learn from their usage and continue to do so over time.
You set an action for all [Push Notifications](https://www.airship.com/docs/reference/glossary/#push_notification), [In-App Messages](https://www.airship.com/docs/reference/glossary/#in_app_message), and [Web Push Notifications](https://www.airship.com/docs/reference/glossary/#web_push_notification), and you associate actions with your buttons and images in [Rich Page](https://www.airship.com/docs/reference/glossary/#rich_page) content. After selecting an action, you can set up adding or removing [Tags](https://www.airship.com/docs/reference/glossary/#tag) when the user interacts with the message, button, or image. For push notifications and in-app messages, you can also emit a [Custom Event](https://www.airship.com/docs/reference/glossary/#custom_event) when a user interaction occurs.
## Supported actions: App and Web
For app and web messages, you set an action in the *Content* step of a composer. *Home* is the default, and support differs by message type.
| Action | Description and configuration | Push notifications | In-app messages | Web push notifications |
| --- | --- | :---: | :---: | :---: |
| Home | | ✓ | ✓ | ✓ |
| Adaptive Link | | ✓ | ✓ | ✓ |
| Web Page | | ✓ | ✓ | ✓ |
| Deep Link | | ✓ | ✓ | |
| Landing Page | | ✓ | ✓ | |
| Message Center | | ✓ | ✓ | |
| Preference Center | | ✓ | ✓ | |
| Share | | ✓ | ✓ | |
## Supported actions: Landing pages and Message Center
When creating landing page and Message Center content, the [editors](https://www.airship.com/docs/guides/messaging/messages/content/app/landing-pages/#choosing-an-editor) support different actions.
* **Visual editor** — Refer to the configuration information on this page.
* Deep Link
* Share
* URL (Web Page)
* **Interactive editor** — See: [Actions in the WYSIWYG editor](https://www.airship.com/docs/guides/messaging/features/wysiwyg-editor/actions/).
* No Action
* Adaptive Link
* App Rating
* Deep Link
* Preference Center
* Share
* Web Page
## Disabling actions
You can disable actions (except for *Home*) from appearing in the composers:
1. Next to your project name, select the dropdown menu (
), then **Settings**.
1. Under **Project settings**, select **Dashboard Settings**.
1. Disable **Message Center, Landing Page, Deep Link, URL, and Add Tags (Airship Actions Framework)**.
> **Important:** Actions must be enabled for [Message Center](https://www.airship.com/docs/reference/glossary/#message_center) to appear in composers.
## Configuring actions
The behavior and configuration steps for each action is described below.
### Adaptive Link
Adaptive Link opens a mobile wallet pass. Select an [Adaptive Link](https://www.airship.com/docs/reference/glossary/#adaptive_link) from the list.
### Deep Link
Deep Link opens a screen in your app or website. Select a deep link from the list.
#### Deep Link templates {#deep-link-templates}
Our Deep Link functionality supports URL templates, which expose a friendly interface to your users in our UI, while constructing the correct URL behind the scenes on the fly. You can specify substitution parameters by enclosing them in brackets. For example, if you want to define a Deep Link for a product page screen in your app (or on your mobile website), you can make the product ID number a substitution parameter. Here are example template URLs:
```text
https://yourcompany.com/products/{Product Id}
yourapp://products/{Product Id}
```
When you enter this URL in the Airship interface, the form parses it and previews the form your users see in the composer. It automatically identifies “Product Id” as the parameter name, and provides a field to substitute in the actual identifier. So if you had previously entered a product ID of 1872983490 for the above Product ID, the generated URL would be:
```text
http://yourcompany.com/products/1872983490
yourapp://products/1872983490
```
The interface treats all values for each field as a string.
### Home
*Home* opens your app's home screen. For web push notifications it opens your [Default Action URL](https://www.airship.com/docs/developer/sdk-integration/web/getting-started/#airship-setup). You can override the default URL by selecting the *Web Page* action and entering a different URL.
### Landing Page
*Landing Page* opens a [Landing page](https://www.airship.com/docs/guides/features/messaging/landing-pages/).
### Message Center
*Message Center* opens a Message Center message. See: [Message Center content](https://www.airship.com/docs/guides/features/messaging/message-center/).
### Preference Center
Preference Center opens an app preference center. Select a preference center from the list.
### Share
Share prompts the user to share your message with apps, social media accounts, and other services. Enter the text you want to accompany the share, including any promotional information, shortened links, hashtags, etc.
### Web Page
Web Page opens a web page or any valid device-level URL such as App Store or app protocol links. The web page opens in the device’s default browser. Enter a URL.