# Custom Buttons

⚠️ Custom buttons are available for Web and Android only. They are not supported on iOS native notifications.

## Enabling Custom Action Buttons

When creating a Notification, you will see a "Custom Buttons" option within the Interactions section. First, input your Primary Landing URL as normal and then enable the switch show the `Custom Buttons` configuration section.

## Configuring Action Buttons

Every notification is required to have at least 1 button. Each button has 3 elements to configure:&#x20;

| Field      | Definition                                                                                                                                                                                                                                            |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Action** | What occurs when the subscriber clicks on the button. "Open URL" will send the subscriber to the designated page you input. "Dismiss Notification" will hide the notification and remove it from the subscriber's action center or notification tray. |
| **Label**  | The text the subscribers will see on the notification's button. Customize this button to provide the most appropriate call to action for the delivered content.                                                                                       |
| **URL**    | Where the subscriber will be delivered when they click the action button. You may choose to use the primary landing URL entered above or disable the switch to enter a URL specific to this action button.                                            |

### Modifying the First Button

When you activate Custom Buttons, the first button will have the `Open URL` action with a `Read Now` label set by default. It will also be set to direct the subscriber to the primary landing URL when the button is clicked. Each of these behaviors can be customized to provide the most relevant behavior for the notification's content.

![Button 1 uses the already configured Primary Landing URL.](/files/Wz9K3YfVuiGGyB4SxVmO)

### Adding a Second Button

Press the `Add Button` option to create a second button for customization. As you can see below, we will use a CTA of `Option 2` for this Label

After you input your Label, input the URL you wish to send subscribers to if they engage with the `Option 2` button. In this example, they will go to `landingpage-2.com/example` rather than the Primary Landing URL used.

![](/files/1ClGeItTuC7rrSCQdAjQ)

The Inline Preview will show you what your subscribers will see:

![](/files/cHyltOIc3TZTEz2kKWjo)

In the above example, if the subscriber clicks anywhere on the notification or the `Option 1` button they will be sent to `the Primary Landing URL`. If they click on the `Option 2` button they will be sent to `landingpage-2.com/example`.

### Configuring a Dismiss Behavior

If you prefer to give your subscribers the option to dismiss the notification upon clicking a button, simply change the `Action` drop-down to `Dismiss Notification` on Button 2 and update your label.&#x20;

![](/files/2iMqu1WpLmowQoND6AcJ)

## Changing the Default Button Label

The first button's label is set by your Account Manager by default. You can change this by accessing your domain settings under the `Notification tab`. There you can click  `Edit` and input a different label under the Button Defaults section.

{% hint style="danger" %}
**Remember to click the `Submit` button before closing to ensure your changes are saved.**
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.pushly.com/platform/notifications/action-buttons.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
